Hi, I want to relock the bootloader in the Moto G5 Plus and the problem is that there is no download available for the full NPNS25.137-93-8 firmware, and I can't relock the bootloader if I flash an older version than what the phone currently has. I need to relock so that the phone passes SafetyNet, as I want to give it to my mother so she can use it without any trouble. Can anyone upload the firmware? Thanks.
Xharos said:
Hi, I want to relock the bootloader in the Moto G5 Plus and the problem is that there is no download available for the full NPNS25.137-93-8 firmware, and I can't relock the bootloader if I flash an older version than what the phone currently has. I need to relock so that the phone passes SafetyNet, as I want to give it to my mother so she can use it without any trouble. Can anyone upload the firmware? Thanks.
Click to expand...
Click to collapse
You can flash an older stock firmware, I already done last week with NPN25.137-33.
The phone is rooted? If yes, have you unrooted correctly?
Already tryed to relock? How and with what kind of result?
nicolap8 said:
You can flash an older stock firmware, I already done last week with NPN25.137-33.
The phone is rooted? If yes, have you unrooted correctly?
Already tryed to relock? How and with what kind of result?
Click to expand...
Click to collapse
It's unlocked but not rooted. When flashing an older firmware it will complain that the security patch version is lower, then refuse to lock when I try to do so, with something like "still need signed boot.img".
Can you give me a step by step process of how exactly you flash an older firmware than the current one and then relock the bootloader? I'd really appreciate it.
Search this sub-forum for "relock"!!!
nicolap8 said:
Search this sub-forum for "relock"!!!
Click to expand...
Click to collapse
If the opening poster formally updated their device to NPNS25.137-93-8, then you need that firmware build or newer to re-lock, else the bootloader would reject the re-lock (the flashing firmware is too old to re-lock the device). Furthermore, although you can re-flash older stock firmware, attempting to flash NPN25.137-33 onto such a device (with the March 2018 firmware update) would be a bad idea, as attempting to use OTA updates would likely cause a hard brick.
To the opening poster, I've not seen the NPNS25.137-93-8 firmware on Android FileHost or firmware.mirror, hopefully someone can capture the firmware or newer firmware (now the April patch appears to be out too) and upload it to XDA.
echo92 said:
If the opening poster formally updated their device to NPNS25.137-93-8, then you need that firmware build or newer to re-lock, else the bootloader would reject the re-lock (the flashing firmware is too old to re-lock the device). Furthermore, although you can re-flash older stock firmware, attempting to flash NPN25.137-33 onto such a device (with the March 2018 firmware update) would be a bad idea, as attempting to use OTA updates would likely cause a hard brick.
To the opening poster, I've not seen the NPNS25.137-93-8 firmware on Android FileHost or firmware.mirror, hopefully someone can capture the firmware or newer firmware (now the April patch appears to be out too) and upload it to XDA.
Click to expand...
Click to collapse
Yep, this is exactly what's happening to me. Hopefully now that the April update is out someone can get that one...
echo92 said:
If the opening poster formally updated their device to NPNS25.137-93-8, then you need that firmware build or newer to re-lock,
Click to expand...
Click to collapse
Why???
Him already have this firmware, is untouched! Only unlocked.
I read some people saying that you need to reflash but I don't trust...
Furthermore, although you can re-flash older stock firmware, attempting to flash NPN25.137-33 onto such a device (with the March 2018 firmware update) would be a bad idea, as attempting to use OTA updates would likely cause a hard brick.
Click to expand...
Click to collapse
I've done this with my RETEU at least 3 times! In november, in january and last week and every time after the flash of original firmware (found in this forum) I applied successfully ALL available OTAs.
To the opening poster, I've not seen the NPNS25.137-93-8 firmware on Android FileHost or firmware.mirror, hopefully someone can capture the firmware or newer firmware (now the April patch appears to be out too) and upload it to XDA.
Click to expand...
Click to collapse
I've a backup of every partition of that firmware (both RETEU and RETAPAC) both are near 5GB. I'm not sure which partitions you need because I dont want to relock so can't try
N
nicolap8 said:
Why???
Him already have this firmware, is untouched! Only unlocked.
I read some people saying that you need to reflash but I don't trust...
I've done this with my RETEU at least 3 times! In november, in january and last week and every time after the flash of original firmware (found in this forum) I applied successfully ALL available OTAs.
I've a backup of every partition of that firmware (both RETEU and RETAPAC) both are near 5GB. I'm not sure which partitions you need because I dont want to relock so can't try
N
Click to expand...
Click to collapse
Look, this is what happens if I try to downgrade and lock:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seriously, it won't let me unless it's an equal or newer version. If you really have a backup of that firmware, you'd basically save my life if you uploaded it. I'd basically need every partition, and I guess it should be in .img format (and the system in img_sparsechunk). If you did that... I wouldn't know how to express my gratitude. Really.
Xharos;76341060Seriously said:
I continue to think that you are doing something wrong: if you only unlocked the phone the partitions are good as if it was not unlocked!
In any case you must say the "RETxxxx" distribution of your phone, I'm not sure of the compatibility!
Click to expand...
Click to collapse
nicolap8 said:
I continue to think that you are doing something wrong: if you only unlocked the phone the partitions are good as if it was not unlocked!
In any case you must say the "RETxxxx" distribution of your phone, I'm not sure of the compatibility!
Click to expand...
Click to collapse
XT1685
I bought it in Amazon Spain.
Thanks!
nicolap8 said:
Why???
Him already have this firmware, is untouched! Only unlocked.
I read some people saying that you need to reflash but I don't trust...
I've done this with my RETEU at least 3 times! In november, in january and last week and every time after the flash of original firmware (found in this forum) I applied successfully ALL available OTAs.
I've a backup of every partition of that firmware (both RETEU and RETAPAC) both are near 5GB. I'm not sure which partitions you need because I dont want to relock so can't try
N
Click to expand...
Click to collapse
Generally, you'd have to re-flash with the stock firmware with the OEM lock commands if you want to re-lock your bootloader, which would wipe your data in re-locking your bootloader.
Hmm, that's curious though - can I ask for the full build name of the firmware you're using to flash and what your getvar info is please?
To get the getvar info:
Boot your device to the bootloader, attach to your computer via USB.
In the ADB terminal, type 'fastboot devices' without quotes.
If you get a serial response, then type 'fastboot getvar all' without quotes.
Post the output here without your IMEI.
The getvar info should show you your device details, I'm just curious about your device and how you can flash the older stock firmware without issue.
nicolap8 said:
I continue to think that you are doing something wrong: if you only unlocked the phone the partitions are good as if it was not unlocked!
In any case you must say the "RETxxxx" distribution of your phone, I'm not sure of the compatibility!
Click to expand...
Click to collapse
In case you need more info:
Don't worry, if your files brick my phone I have a EFS backup and I'll just flash the version that I have. It won't let me lock the bootloader with it, but it does let me flash it.
The reason I need the latest firmware is because otherwise the lock command doesn't work. The lock command asks you to flash an official ROM, and refuses to work if said official ROM is not equal OR newer to the latest you have had on your phone. I know it sounds convoluted and weird but it works that way. If you tried to lock the bootloader you'd see it. Flashing works, locking the bootloader doesn't. So if you can give me the .img files for the March or April firmware you'll save me.
echo92 said:
Generally, you'd have to re-flash with the stock firmware with the OEM lock commands if you want to re-lock your bootloader, which would wipe your data in re-locking your bootloader.
Hmm, that's curious though - can I ask for the full build name of the firmware you're using to flash and what your getvar info is please?
To get the getvar info:
Boot your device to the bootloader, attach to your computer via USB.
In the ADB terminal, type 'fastboot devices' without quotes.
If you get a serial response, then type 'fastboot getvar all' without quotes.
Post the output here without your IMEI.
The getvar info should show you your device details, I'm just curious about your device and how you can flash the older stock firmware without issue.
Click to expand...
Click to collapse
Very interested in this too.
Sent from my Moto G5 Plus using XDA Labs
Related
Small update to build SU4TL-49. Not Marshmallow. Claims "security patches and improved network performance."
How to Update with an Unlocked Bootloader
The update will only work if you have a 100% unmodified stock rom and recovery menu. If you're on CF's rom and you want to update to the latest version of that, see his page for details on how to do that.
1. Backup all data. Just in case. Definitely do this if you're coming from CM13 or RR. I don't remember if the OTA wipes your data or not.
2. Download this SU4TL-44 100% stock flashable zip here: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
3. Download the SU4TL-44 stock recovery menu here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8
4. Boot into TWRP.
5. Flash the file you downloaded in step 2 by selecting Install and browsing to the file.
6. In TWRP, select Install, followed by install image, and select the recovery image that you downloaded in step 3. Tell it to flash it to recovery, and flash it.
7. If you're coming from CM13 or RR, do a factory reset in TWRP. If you're coming from a modified stock rom, I still recommend this, but it's not mandatory.
8. Reboot to recovery to confirm that you see the stock recovery menu (a dead android with the words "no command").
9. Boot the phone normally.
10. The OTA update should appear. Take it and let it do its thing.
You now have a 100% stock, bootloader still unlocked, SU4TL-49 phone. If you want TWRP back so you can start flashing stuff again, keep reading.
11. Download and install Sunshine from here: http://theroot.ninja/
12. Download your preferred version of TWRP. The current stable version is here: https://dl.twrp.me/quark/. If you want baybutcher27's modded version that includes lots of handy additional features, you can get that here: http://forum.xda-developers.com/showpost.php?p=66877208&postcount=116
13. Download Flashify from the play store.
14. Open Sunshine and follow the instructions until it gains temp root. Disregard the message that says it isn't compatible with SU4TL-49.
15. Open Flashify, select Recovery Image, then browse to the version of TWRP that you downloaded in step 11. Flash it.
16. Reboot to recovery. You should see TWRP's lovely smiling face staring back at you.
How to Install the SU4TL-49 Modem Only
1. [HIGHLY RECOMMENDED] Flash the modded TWRP I mentioned earlier, select backup, backup only your modem.
2. Flash Computerfreek274's modem package that you can get here: https://www.androidfilehost.com/?fid=24545070682210570
3. If you have GPS or other modem-related issues, try flashing this to fix them: https://www.androidfilehost.com/?fid=24531035584725320
4. If you decide you don't like the new modem, restore the backup you made in step 1.
Troubleshooting
Issue: You followed all of the steps, but you still get an error when you try to take the OTA.
Solution: Backup your data and perform a factory reset using the stock recovery menu. You can do this by rebooting to recovery like you do when you want to boot TWRP, and when you see the "no command" screen, hold the power button and press volume up. Then select factory reset and do it.
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
lukappaseidue said:
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
Click to expand...
Click to collapse
He just said it won't lock your bootloader
lukappaseidue said:
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
Click to expand...
Click to collapse
Taking the update is perfectly safe as long as you are unlocked. However, if you are rooted, the update will fail. You must first flash a completely unmodified stock rom.
This will take you back to full stock: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
Thank you. I think it is worth waiting for MM, or full updated rom
grazie
Original Motorola DROID Turbo receives a security update from Verizon
http://www.phonearena.com/news/Orig...ceives-a-security-update-from-Verizon_id81089
Original Motorola DROID Turbo receives a security update from Verizon
3 May 2016, 18:19, by Alan F.
We hate to take all of the fun out of your life, but if you happen to own the Motorola DROID Turbo and you receive the update from Verizon that is heading your way, the phone is not receiving Android 6.0. Better that we shoot down all hopes now before you start believing that the new files contain the latest Android build.
The update brings the latest Android security software to the DROID Turbo and it also adds improvements to call performance. Just because this is the OG Turbo doesn't make it totally irrelevant. Verizon still offers the device as a mid-range handset priced at $480.
Verizon suggests that after receiving the notification that your Turbo has received the update, you make sure that the phone is connected to a Wi-Fi network or a strong Verizon cellular signal before starting the updating process. Also, your battery should be fully charged before you start the update.
On Motorola's support page, it says that the Motorola DROID Turbo is still slated to receive Android 6.0 "pending partner support." Which means that if you still own this phone, you need to keep pushing Verizon to support an update to Android 6.0.
Click to expand...
Click to collapse
Whose done this and any difference?
Sent from my XT1254 using XDA-Developers mobile app
This update appeared to have disabled VoLTE.
molanjami said:
This update appeared to have disabled VoLTE.
Click to expand...
Click to collapse
VoLTE still working fine for me.
Sent from my XT1254 using XDA-Developers mobile app
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Did a restore of the modem backup provided, rebooted phone and everything working as it should. sadly didnt improve my signal any, but thats what happens living in the boonies.
Flashed it on Resurrection Remix 5.6.8 05/08 build
It went fine for me but I backed up my SU44 Modem to be safe, and I wanna remind everyone to do the same, its always wise to be safe
TheSt33v said:
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Click to expand...
Click to collapse
I ran Stagefright Detector after the update and it reported CVE-2015-6602 as a vulnerability.
Sent from my Droid Turbo using Tapatalk
helobubba88 said:
I ran Stagefright Detector after the update and it reported CVE-2015-6602 as a vulnerability.
Click to expand...
Click to collapse
Wow. Now that's lazy.
TheSt33v said:
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1254 using XDA-Developers mobile app
Nitefire77 said:
Did a restore of the modem backup provided, rebooted phone and everything working as it should. sadly didnt improve my signal any, but thats what happens living in the boonies.
Flashed it on Resurrection Remix 5.6.8 05/08 build
It went fine for me but I backed up my SU44 Modem to be safe, and I wanna remind everyone to do the same, its always wise to be safe
Click to expand...
Click to collapse
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
quantum tao said:
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
Click to expand...
Click to collapse
Extract the zip to /sdcard/TWRP/backups/[your phone's serial number]. Then boot twrp, select restore, and restore the backup.
quantum tao said:
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
Click to expand...
Click to collapse
^What St33vo said. Just restore modem from the extracted zip in your twrp folder. Keep it in the Sut49 folder once unzipped so you can select it under restore.
You don't need to wipe caches or anything. Just restore and reboot
TheSt33v said:
Extract the zip to /sdcard/TWRP/backups/[your phone's serial number]. Then boot twrp, select restore, and restore the backup.
Click to expand...
Click to collapse
Nitefire77 said:
^What St33vo said. Just restore modem from the extracted zip in your twrp folder. Keep it in the Sut49 folder once unzipped so you can select it under restore.
You don't need to wipe caches or anything. Just restore and reboot
Click to expand...
Click to collapse
thanks, that worked. i guess i'm too tired to do simple file operations. i thought it was an installable zip.
lukappaseidue said:
Thank you. I think it is worth waiting for MM, or full updated rom
grazie
Click to expand...
Click to collapse
Seen VZ update the razr hd to close a unlock and never released another update again. Still hoping this is not the case.
BBB
add two
Sent from my XT1254 using Tapatalk
realbbb said:
Seen VZ update the razr hd to close a unlock and never released another update again. Still hoping this is not the case.
BBB
add two
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Well very shortly before this update was released, people were talking about getting soak test invites. If the soak test was for this update, that's the shortest soak test in human history, and why would you need a soak test for such a tiny update? I'm still hopeful that we'll see a marshmallow soak leak relatively soon.
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
Let me start out by saying I have spent hours searching and reading about this subject, and can't find straight answers to what I'm asking here.
So search wasn't my friend on these questions.
1)I am not clear on whether or not to install su.zip (arm) after unlocking bootloader and installing latest lineage version. In rahulsnair's post, he has a link for su.zip (arm) download, but then he says a few lines down: don't install any superuser packages.
2)I can't find a clear recent link on what package to install to get the stock N image and modem, the only one I found was dated October 2016 by sam sundar (Blur_Version.24.31.64.athene.retail.en.US.zip), is this the right one?
3)Do I even need to install that, or will the phone auto update to Nougat (moto xt1644)?
4) Will I be able to tether with this rom? (I am still on a legacy Verizon unlimited plan) rahulsnair also said in his post "Go to Settings>Developement Settings>Root access and select "Apps Only"", will this allow tether too?
Thanks in advance.
bovineyard said:
Let me start out by saying I have spent hours searching and reading about this subject, and can't find straight answers to what I'm asking here.
So search wasn't my friend on these questions.
1)I am not clear on whether or not to install su.zip (arm) after unlocking bootloader and installing latest lineage version. In rahulsnair's post, he has a link for su.zip (arm) download, but then he says a few lines down: don't install any superuser packages.
2)I can't find a clear recent link on what package to install to get the stock N image and modem, the only one I found was dated October 2016 by sam sundar (Blur_Version.24.31.64.athene.retail.en.US.zip), is this the right one?
3)Do I even need to install that, or will the phone auto update to Nougat (moto xt1644)?
4) Will I be able to tether with this rom? (I am still on a legacy Verizon unlimited plan) rahulsnair also said in his post "Go to Settings>Developement Settings>Root access and select "Apps Only"", will this allow tether too?
Thanks in advance.
Click to expand...
Click to collapse
Someone feel free to correct me on any of these
1) Flash SU.zip or SuperSU (or your root manager of choice) if you desire root. The history seems to be that CM14.1/early days of Lineage OS had root built-in (hence the warning towards the end of the post), but sometime in January the official Lineage team removed built in root access and moved it to a flashable separate zip, meaning you have to install it as an addon.
2)Looks like that file was the soak test from October, I wouldn't recommend installing it as although you get Nougat, it's a dead end upgrade path. You've got a couple of options:
a)Flash the fastboot NPJ25.93-14 Nougat stock update (v7.0, Dec 2016 security update) from https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369. This is as far as I can tell a complete ROM that appears to be signed by Motorola.
b)You could look at flashing the TWRP radio and Nougat files from here https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147, seems they work.
3) Depends on how long you're willing to wait for Nougat to arrive in the US, there are a few reports of a soak test in the US occurring! https://forum.xda-developers.com/moto-g4-plus/how-to/nougat-update-apparently-rolling-t3566271
4)No idea about tethering, seems from the official thread it worked for XT1642 (EU/UK Plus) but wasn't on XT1644 devices. You could try though with the newest build. Also, check robot_head's thread on suggestions on how to get Wi-Fi tethering working. https://forum.xda-developers.com/moto-g4-plus/help/wifi-tether-xt1625-t3543061 I think you have to uninstall SuperSU or other root managers if you wish to use Magisk for this, as Magisk takes over root management (as I recall!).
As always, good luck
I'm assuming bootloader needs to be unlocked to use this method? If so, is there a way to apply the latest xt1644 nougat update before unlocking bootloader? Thanks
bovineyard said:
I'm assuming bootloader needs to be unlocked to use this method? If so, is there a way to apply the latest xt1644 nougat update before unlocking bootloader? Thanks
Click to expand...
Click to collapse
Which method were you referring to? If it's the update to Nougat, bootloader status doesn't really matter (OTAs may still install if you have a stock recovery/kernel/system with an unlocked bootloader, and the fastboot method will also install if your bootloader is unlocked). For everything else, yes you will need an unlocked bootloader (and thereby voiding your warranty).
You could either wait until the Nougat update arrives and then update via OTA, then unlock, or flash the fastboot ROM before or after unlocking, honestly up to you. So long as your bootloader is the only thing that's been modified, OTAs should be okay - anything else and a fastboot ROM may be required.
Okay, so I got the bootloader unlocked, and I have got the latest Nougat firmware installed (NPJ25.93-14), flashed through fastboot, and I can't get TWRP to install through fastboot, Ive tried two different downloads, please see screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bovineyard said:
Okay, so I got the bootloader unlocked, and I have got the latest Nougat firmware installed (NPJ25.93-14), flashed through fastboot, and I can't get TWRP to install through fastboot, Ive tried two different downloads, please see screenshot.
Click to expand...
Click to collapse
You've got the TWRP recovery installed, those errors are normal (I imagine because we don't have the right cryptographic keys). At the end of each command, you'll note [OKAY] is present, so the flash worked, ensure you reboot into recovery after flashing to prevent the stock recovery overwriting. Afterwards, TWRP should persist on your device. You may wish to use the adb command 'adb reboot recovery' to accomplish this or boot into recovery via the bootloader.
Got this ROM running, working great! Thanks for all of the efforts!
One but one but I have is: in Phone-settings-calls, when you select calls (to setup voicemail, etc.,), com.android.phone force closes. My device is the xt1644, rom is the Lineage March 06 build. Latest modem (Dec 2016) and firmware were flashed before flashing Lineage. Verizon is the service provider.
One request I have is the ability to turn off Album art on the lock screen. Had that I my Nexus 6 with the Pure Nexus Substratum Rom by Beanstown and others.
Completely Re-Written in C#
This version is actually up to date, sorry for the long time between releases, I had to learn c# before creating the C# version...
Anyways, you know the schpeel
I am not responsible for anything that happens to your device, or computer as a result of you using my toolkit. You are responsible for your own devices, don't be stupid.
Please note, this program is in it's early days, due to me not knowing a lot of c#. Please be patient if it is buggy, comment and join my telegram channel for support at https://t.me/a2_gui_toolkit
The features include:
Reboot options
Reboot to EDL mode
Common Links used in the forums
IMG flasher (beta)
Stock rom downloader and flasher (beta)
No install TWRP launcher
No install TWRP zip installer
Auto Root
Auto Update Checker.
Other features to come
Easter egg, can you find it?
Future features
Backup/Restore
Convert to Mi 6X
Mi 6x Support
Rom installer
Hex Kernel Installer
Possible Suggestions
Camera 2 enabler
OTA installer for rooted users
Some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Release Notes
Version 1.0.2
Added auto-root functionality
Fixed random crashes and bugs
Added new UI elements for parts currently being worked on
Converted to use a c# adb api
added dropdown for noob mode
updated instructions and order of certain processes
added json support for twrp api (in the future will automatically download latest twrp version)
probably more I am forgetting
Version 1.0.1
fixed TWRP zip flashing on reboot
Fixed settings not saving correctly on certain systems
Fixed many misc bugs
Updated dialogs to be more convienient and guiding
Created disabled butttons to show future implimentations
Added backup via ADB backup, restore is not yet implimented
Please ensure you have .net version 4.6.1 or later! It can be downloaded here if not already installed.
https://dotnet.microsoft.com/download/dotnet-framework/net461
Download Toolkit Here
https://github.com/da-ha3ker/Jarvinator-A2-Toolkit-Release
Can you provide some screenshots or tutorial? Thank you in advance!
Can you provide the same tool for Mi A2 Lite ?
Thank you
8 no. revert to stock rom
if i use this will my bootloader unlocked a2 will revert to stock rom with bootloader locked?
Syed Shahriar said:
8 no. revert to stock rom
if i use this will my bootloader unlocked a2 will revert to stock rom with bootloader locked?
Click to expand...
Click to collapse
No. It will only flash the stock rom, your bootloader will still be unlocked. I will add re-lock bootloader as an option in future updates
Daha3ker said:
No. It will only flash the stock rom, your bootloader will still be unlocked. I will add re-lock bootloader as an option in future updates
Click to expand...
Click to collapse
flash rom with august patch?
and will stock rom be downloaded from the commands ?
No 4 installs the patches boot image right? No 5 install the original one? Do i have to install the unpatched image (unroot) before ota?
bartoloandre98 said:
No 4 installs the patches boot image right? No 5 install the original one? Do i have to install the unpatched image (unroot) before ota?
Click to expand...
Click to collapse
No 4 and 5 is correct. You will have to have an unrooted device to install ota's, so if you run the unroot it should work; So as long as your device's system hasn't been modified (eg busybox or non systemless modifications) you should be good to install the ota.
Syed Shahriar said:
flash rom with august patch?
and will stock rom be downloaded from the commands ?
Click to expand...
Click to collapse
The version is stated in the description. So yes, the August patch. The stock rom is in the Stock_images folder. So it is downloaded when you download the program.
Ahmed_hassan95 said:
Can you provide the same tool for Mi A2 Lite ?
Click to expand...
Click to collapse
I do not have an A2 lite, if you or someone you know would like to, you can port this to the lite version. It should not be too hard, I just don't have any way to test what would work and what would not.
I've my A2 already unlocked (BootLoader unlocked)
if i want simply to root it, have i simply to use 4. Root Device ?
does this install also TWRP ?
have i to launch 4 option with phone in faastboot, or in normal mode ?
webmasterone said:
I've my A2 already unlocked (BootLoader unlocked)
if i want simply to root it, have i simply to use 4. Root Device ?
does this install also TWRP ?
have i to launch 4 option with phone in faastboot, or in normal mode ?
Click to expand...
Click to collapse
You must run OEM unlock, unlock flashing and unlock critical, then run 4 to root the device. TWRP will cause a bootloop, so follow the instructions in option 6 to avoid it. TWRP is able to be used, but not permanetly installed.
No spiking english, how relock bootloader? Help me please!
Nestor0rtiz1 said:
No spiking english, how relock bootloader? Help me please!
Click to expand...
Click to collapse
fastboot oem lock
AhanafTanvir said:
fastboot oem lock
Click to expand...
Click to collapse
Could you explain me please?
Nestor0rtiz1 said:
Could you explain me please?
Click to expand...
Click to collapse
boot to fastboot mode in ur phone, connect via usb, open fastboot from pc. type
fastboot oem lock
tell me what happens
I really want to install GCAM and camera2API on my A2, but also, I don't want to lose OTA updates, banking funcionatility and don't want to keep bootloader unlocked.
Can I have this? Or am I dreaming too high?
kadu20es said:
I really want to install GCAM and camera2API on my A2, but also, I don't want to lose OTA updates, banking funcionatility and don't want to keep bootloader unlocked.
Can I have this? Or am I dreaming too high?
Click to expand...
Click to collapse
You won't lose data when locking the bootloader, only unlocking. You can OTA update, if you open magisk manager and uninstall (restore the original boot.img). I didn't test this myself, but I will as soon as the next OTA is available.
hugopg said:
You won't lose data when locking the bootloader, only unlocking. You can OTA update, if you open magisk manager and uninstall (restore the original boot.img). I didn't test this myself, but I will as soon as the next OTA is available.
Click to expand...
Click to collapse
Cool! When you get done, please, share your experience. If you can, share the process of restoring of the original "boot.img"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Version:RMX1931EX_11.A.06
Release time:14/11/2019
Size:3.06GB
md5:14e2ea74751fd499394263c441f97400
link: sorry I cant post link because of account, pls go to eu realme website -> support -> software update
Is anyone can try Chinese version flash to EU version?
hmmm I may attempt to flash on my x2 pro once it arrives,unless someone else tries and says it fails
link:https://download.c.realme.com/osupdate/RMX1931EX_11_OTA_0060_all_iomsumMA73CO.ozip
Hey Guys how we can install that on chinese rom?
---------- Post added at 03:33 PM ---------- Previous post was at 02:54 PM ----------
I just tried to install it on my x2 pro chinese rom and I followed their method on the website, putting the software on the phone storage and I got installation failed or decompression error message. Anybody know a way?
i got CN version, im gonna try this and hope it will work :fingers-crossed:
realmayar said:
i got CN version, im gonna try this and hope it will work :fingers-crossed:
Click to expand...
Click to collapse
Please keep us informed I'm in the same case
unfortunately i got installation error. i hope somebody finds a way to make it work.
realmayar said:
unfortunately i got installation error. i hope somebody finds a way to make it work.
Click to expand...
Click to collapse
So basically it is not able to install EU rom on a device with CN rom ?
im wondering why the file ends in .ozip vs .zip maybe thats why?
EDIT: I didn't realize that is a oppo specific update extension,so im not sure why it wouldnt work
maybe unlocking bootloader then flashing via recovery will work?
rosztrade said:
So basically it is not able to install EU rom on a device with CN rom ?
Click to expand...
Click to collapse
I would have thought this was expected? The same was the case with the X2. Unless you can fool the recovery somehow in to thinking you're on a global version I would imagine it's unlikely this method would work.
I assume flashing through TWRP with an unlocked bootloader would work but that's not going to work with this proprietary ozip.
I don't think anyone has tried a full twrp system backup and restore from a global phone to a china one though. I'm interested in how that would play out.
Ozip to zip is easy. Done.
BUT, both fastboot flashing and twrp flashing giving errors, because new (EU) system.img and vendor.img is larger than CN versions.
I can go further, try to flash EU recovery and flashing ozip rom. BUT I'm afraid if device is bricked, I don't want to wait for months hoping for a unbrick rom
os_man said:
Ozip to zip is easy. Done.
BUT, both fastboot flashing and twrp flashing giving errors, because new (EU) system.img and vendor.img is larger than CN versions.
I can go further, try to flash EU recovery and flashing ozip rom. BUT I'm afraid if device is bricked, I don't want to wait for months hoping for a unbrick rom
Click to expand...
Click to collapse
so i was able to get rid of the stock launcher , but not being able to use google messages is really crappy. even after deleting the stock messaging app its asking me to login to verify my identity before it will send messages via google messages
os_man said:
Ozip to zip is easy. Done.
BUT, both fastboot flashing and twrp flashing giving errors, because new (EU) system.img and vendor.img is larger than CN versions.
I can go further, try to flash EU recovery and flashing ozip rom. BUT I'm afraid if device is bricked, I don't want to wait for months hoping for a unbrick rom
Click to expand...
Click to collapse
ozip update is normal that means is a oppo realme update even the CN version ends with ''ozip''
But yeah can't install it in ''normal way''
is there a way to unlock the bootloader and intall twrp? I didn't see anything ''official''
Otherwise how to guys?
os_man said:
Ozip to zip is easy. Done.
BUT, both fastboot flashing and twrp flashing giving errors, because new (EU) system.img and vendor.img is larger than CN versions.
I can go further, try to flash EU recovery and flashing ozip rom. BUT I'm afraid if device is bricked, I don't want to wait for months hoping for a unbrick rom
Click to expand...
Click to collapse
1. ozip decrypting
2. compatibility.zip must be delete
3. sign zip and flash (but I think recovery will flash to eu version so it may cause some problem)
henrym1203 said:
ozip update is normal that means is a oppo realme update even the CN version ends with ''ozip''
But yeah can't install it in ''normal way''
is there a way to unlock the bootloader and intall twrp? I didn't see anything ''official''
Otherwise how to guys?
Click to expand...
Click to collapse
"is there a way to unlock the bootloader and intall twrp?"
Are you serious ?
os_man said:
"is there a way to unlock the bootloader and intall twrp?"
Are you serious ?
Click to expand...
Click to collapse
I'm asking if there is an offcial and functional way so yes I'm serious
henrym1203 said:
I'm asking if there is an offcial and functional way so yes I'm serious
Click to expand...
Click to collapse
Hi
I'm in the same situation as you are. Should get my X2 pro these days and am collection information about safe ways to root, because I need my phone as working phone and unfortunately can't take the risk ofbricking the phone or have an unstable installation. As far as I know for shure:
Unlocking bootloader
You need the tool "In-Dept test Tool" on your phone. Read this . You will find a download link there.
Installing TWRP
There is a pre-release version from honorable @mauronofrio. I don't know how big the risk ist to install this. I haven't read anything about people who have experience with this. For instructions read this .
Rooting
Now we are on the tricky point. I have not read anything about succesful rooting. Neither with Magisk nor with SuperSU.
If anyone has additional info or newer info please let me/us know.
Sir Backe said:
Rooting
Now we are on the tricky point. I have not read anything about succesful rooting. Neither with Magisk nor with SuperSU.
If anyone has additional info or newer info please let me/us know.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80955651&postcount=72
Sir Backe said:
Hi
I'm in the same situation as you are. Should get my X2 pro these days and am collection information about safe ways to root, because I need my phone as working phone and unfortunately can't take the risk ofbricking the phone or have an unstable installation. As far as I know for shure:
Unlocking bootloader
You need the tool "In-Dept test Tool" on your phone. Read this . You will find a download link there.
Installing TWRP
There is a pre-release version from honorable @mauronofrio. I don't know how big the risk ist to install this. I haven't read anything about people who have experience with this. For instructions read this .
Rooting
Now we are on the tricky point. I have not read anything about succesful rooting. Neither with Magisk nor with SuperSU.
If anyone has additional info or newer info please let me/us know.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...lme-x2-pro-t3997879/post80955651#post80955651
Extracted EU rom to system.img + vendor.img + other partitions. BUT the system.img is 5.1GB, CN version is 4.4GB, same for vendor.img, is bigger. Now both fastboot flashing and twrp flashing are giving errors, that there is no space for flashing.
I need help, is there any way to resize those partitions ? (twrp resize does not work).