Related
I have switched to a new device and no longer use this phone but i see many others facing this issue as well so I am keeping this thread open, please do not message me regarding the solution to this issue cause all i did to get out of this mess was getting a new phone.
Hello !
Due to some error while flashing stock rom on Moto G4 Plus XT-1643 my Moto G4 Plus has changed into Moto G4 but the model no shown in the "About Phone" section is correct.
I have lost one Imei no. fingerprint option is no where sim or mobile network doesn't work other than that the phone is fully functional(WiFi,Camers,Audio etc)
There are multiple threads on the same issue but no solution is available I would be highly grateful if anyone could find out any solution to this issue.
P.S : I have tried flashing multiple ROMs available on the forum specific to XT-1643 i.e Indian Version
Also I flashed the OTA file for the Android 7.0 Soak Test due to which I cannot relock the bootloader.
I am currently on Stock Marshmallow 6.0.1 139-63 Rooted&TWRP installed
The phone is basically an iPod without fingerprint sensor
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
this happened to my phone (1640 - brazilian moto g 4 plus), and I tried every single rom out there for moto g 4 plus, and it is only identified as Moto G 4, without fingerprint or any modem activity.
i still cannot recover previous bootloader, because it don't downgrade bootloader version. nothing worked for me so far.
i'll be watching this thread to see if anyone comes with any alternative.
sabithmk said:
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
Click to expand...
Click to collapse
Umm, so according to you too it's a software issue and not a hardware one right ?
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
if you flashed android 7.0 and then downgraded to android 6.0.1 then expect some bugs because your bootloader gets updated you have to do clean flash but you cannot actually completely downgrade to android 6.0.1 after you updated to 7.0 soak test bootloader still remains updated and your phone will brick when you click update after you receive 7.0 official OTA i warned you this happened to lot of moto x users do some research before you do anything if the phone is your primary device
Soureen said:
Umm, so according to you too it's a software issue and not a hardware one right ?
Click to expand...
Click to collapse
I think so. May be if we flash a wrong modem, the right one never flashes correctly. I don't know how do they managed to flash it correctly.
For me its a software issue... looks like it messed with the bootloader, and since you cannot rollback to an older bootloader, the phone works like an iPod Touch. haha
I hope that when Motorola releases the final 7.0 version for 1640, I'll be able to flash again the right bootloader and that will fix the phone.
SoNic67 said:
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
Click to expand...
Click to collapse
I did a full flash of an older 6.0.1 ROM, and it still doesn't work. Since the only thing that I couldn't flash is the bootloader, and the phone identify itself as Moto G 4 (and not Moto G 4 Plus) my guess is that the problem is with the bootloader.
I guess i'll have to wait for the official 7.0 for my specific phone (1640) to fully replace this broken bootloader.
Yeah, that's why I didn't upgrade to the N yet, I was sure that the bootloader will be different.
I also have saved the partitions with Partitions Backup & Restore app, after rooting.
Did you try the ElementalX kernel?
http://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
I was also having same issue,got my bootloader locked and went to service center and they replaced the motherboard for free????
Lucky you
Has anyone found a solution to get the plus (fingerprint) back to the phone?
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
That's a bummer but there might be some solution. The phone version number shouldn't be that hard to find if you'd knew witch file that flashes it.
How do you do these backups for they don't look at all as twrp backups so I guess twrp is second best to something. But what?
What is the different with 7.0 coming up? Can't you just relock a backup?
Soureen said:
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
Click to expand...
Click to collapse
I have the same issue, I have seen people with XT1643 having athene_f in build fingerprint but I have only athene. Which one is correct, could this be the issue?
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
m.swastik said:
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
Click to expand...
Click to collapse
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-63/64:user/release-keys
Click to expand...
Click to collapse
l2o88j said:
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
Click to expand...
Click to collapse
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
m.swastik said:
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
Click to expand...
Click to collapse
I found this trick early and I am using it now. I thought you cracked the last part (fingerprint sensor) which my post was about. I think that the issue is with gpt bin as I tried different bootloader versions along with all possible combinations. Gud to see someone else is working on the same. Will update if found any.
find the correct firmware for the device and flash it else it would lead to such errors
I downgraded to marshmallow from nougat and vibrate broke. Motor beeps (yes, motor, not speaker) when it tries to vibrate. Can this be really software issue? I Flashed stock firmware again with Odin and smart switch.
It seems hardware problem, but strange that it appeared just when I downgraded...
Can't be a hardware problem as I have the exact same problem. I too was running the beta program Nougat and decided to leave. Flashed a BTU rom and now I too have lost vibrate. Just a faint beep coming from the earpiece when I go into vibrate mode. Anyone any ideas on what to do ?
Have you tried nougat again?
SUPERHAMSTERI said:
Have you tried nougat again?
Click to expand...
Click to collapse
I installed the Nougat rom today via Odin and vibrating is working fine... I really need to downgrade again with vibrating working as I'm looking to sell the phone.. lol
SUPERHAMSTERI said:
Have you tried nougat again?
Click to expand...
Click to collapse
Like I said in previous post I had installed the Nougat rom via Odin.. I then plugged the phone into my PC and started the Smart Switch app.. It told me there was a newer version of the OS available (which is actually the current Marshmallow version), and I let it install it, and vibrating still works.. So maybe you could try that.. Seemed to work for me anyway.
timinireland said:
Like I said in previous post I had installed the Nougat rom via Odin.. I then plugged the phone into my PC and started the Smart Switch app.. It told me there was a newer version of the OS available (which is actually the current Marshmallow version), and I let it install it, and vibrating still works.. So maybe you could try that.. Seemed to work for me anyway.
Click to expand...
Click to collapse
Thanks! Worked!
If you downgrade from 7.0 to 6.0 you need to downgrade your BL and CP too not just the rom. Hope it helps.?
Fixed
SUPERHAMSTERI said:
I downgraded to marshmallow from nougat and vibrate broke. Motor beeps (yes, motor, not speaker) when it tries to vibrate. Can this be really software issue? I Flashed stock firmware again with Odin and smart switch.
It seems hardware problem, but strange that it appeared just when I downgraded...
Click to expand...
Click to collapse
This fixed it for me...
Temporarily upgrade to Android 7 to fix the vibration issue then use odin to flash final version of android 6.0.1. You must flash all 4 files contained in the extracted (unzipped) firmware package but ignore the home_CSC file. IMPORTANT...tick the option in odin "phone bootloader update". This process will wipe all data on the phone but will give you a fully functioning galaxy s7 with Android 6.0.1 marshmallow!
Djwhitegold said:
This fixed it for me...
Temporarily upgrade to Android 7 to fix the vibration issue then use odin to flash final version of android 6.0.1. You must flash all 4 files contained in the extracted (unzipped) firmware package but ignore the home_CSC file. IMPORTANT...tick the option in odin "phone bootloader update". This process will wipe all data on the phone but will give you a fully functioning galaxy s7 with Android 6.0.1 marshmallow!
Click to expand...
Click to collapse
Thanks for sharing.
It`s working. But a single issue. *#06# code is not working .
any idea ?
Djwhitegold said:
This fixed it for me...
Temporarily upgrade to Android 7 to fix the vibration issue then use odin to flash final version of android 6.0.1. You must flash all 4 files contained in the extracted (unzipped) firmware package but ignore the home_CSC file. IMPORTANT...tick the option in odin "phone bootloader update". This process will wipe all data on the phone but will give you a fully functioning galaxy s7 with Android 6.0.1 marshmallow!
Click to expand...
Click to collapse
For me, upgrading back to Nougat didn't fix it. Did you upgrade to Nougat using Odin and the "phone bootloader update" or did you just use the official install method?
dowgrade to Marshmallow today , everythig is working fine except the camera "camera failed" error .. tried all solutions given on internet .. any fix ?
Same Camera not working. PLease help
extracted firmware not what we expected
chinhe said:
If you downgrade from 7.0 to 6.0 you need to downgrade your BL and CP too not just the rom. Hope it helps.
Click to expand...
Click to collapse
Hi, I tried to downgrade from android 7 to 6, but after i extract the firmware, it has 8 files, which most of them look like a cd pictures. Not the file that we expected like BL, CP, etc. None of them like those 4 files that they should be. So I can not continue to use odin, because the extractted files is totally different. Any idea what happen?.
Thanks
No vibration s7 edge after downgrade
Hello i downgraded s7 edge from nougat helios custom rom to marashmallow decent ultralite 5.0 custom . Now my vibrator is not working. I tried flash bootloader via odin it says fail . Please help
i found solution for no vibrator after downgrade nougat to marshmallow
i found solution for no vibrator after downgrade nougat to marshmallow
i found solution for no vibrator after downgrade nougat to marshmallow
S7 edge is not vibrating after downgrade nougat to marshmallow, it is because you are using nougat bootloader in Marshmallow, you just have to flash with odin the correct MARSHMALLOW bootloader and CP and the vibrator will work just fine.
https://androidfilehost.com/?w=files&flid=54002
6 december 2018, i extremely recomend use Decent ultralite 5.0 MARSHMALLOW ROM in samsung S7, it is very fast and stable, S7 is designed for marshmallow.
https://forum.xda-developers.com/s7-edge/development/08-08-decent-debloated-dd1-addons-mods-t3435516
My vibrate problem is because I updated to oreo. Any solutions for this?
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
inFiniTyz_Z said:
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
Click to expand...
Click to collapse
If you wish to simply re-lock your bootloader, the easiest thing is to flash this fastboot stock ROM (which is Nougat) and use the locking script as directed in the first post. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this may wipe your data - so back up, and the relocking may or may not work, in which case you may have to wait for a more up to date fastboot stock ROM to become available.
If you were to downgrade to Marshmallow, you cannot downgrade your bootloader and GPT partitions, at best, your existing bootloader would try to prevent you from downgrading those partitions. At worst, you'll brick your device again if you were to flash those - though we've got possible ways of fixing that, it's not a route I'd want to go down. Flashing the rest of Marshmallow is no problem, however, ensure you have the correct MM firmware for your device and territory.
Will this version work for my country(Germany) without OTA trouble?
inFiniTyz_Z said:
Will this version work for my country(Germany) without OTA trouble?
Click to expand...
Click to collapse
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
echo92 said:
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
Click to expand...
Click to collapse
THANK YOU IT WORKED AND THE WARNING DISAPPEARED. I am on Nougat, locked and its working like a charm
I WOULD KISS YOUR BUTT IF ITS HAVE TO BE
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
stock boot.img ?
Spaceminer said:
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
Click to expand...
Click to collapse
Sounds good, one question thought, where is stock boot.img on j727p firmware for odin? BP,CSC,CP, or AP.
J727P
Spaceminer said:
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
Click to expand...
Click to collapse
One question is this fore real ?
Yes I ask this because I was on stock firmware three days ago an I checked for the update an there wasn't one ! Maybe Verizon gets the update first I will check again in a day or two !
---------- Post added at 12:32 AM ---------- Previous post was at 12:00 AM ----------
lamike said:
Sounds good, one question thought, where is stock boot.img on j727p firmware for odin? BP,CSC,CP, or AP.
Click to expand...
Click to collapse
Boot img is in the AP file !!
peter couniaz said:
One question is this fore real ?
Yes I ask this because I was on stock firmware three days ago an I checked for the update an there wasn't one !
Click to expand...
Click to collapse
Yes. It's just not officially released yet. I've been scouring the web for a leak. This means Oreo has been built for our device already and the official release coming. If you're curious about WiFi Alliance, wikipedia has good information about them.
J737P
Spaceminer said:
Yes. It's just not officially released yet. I've been scouring the web for a leak. This means Oreo has been built for our device already and the official release coming. If you're curious about WiFi Alliance, wikipedia has good information about them.
Click to expand...
Click to collapse
Ok thank you an let me know if you find anything more about this !
peter couniaz said:
Ok thank you an let me know if you find anything more about this !
Click to expand...
Click to collapse
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
J727P
Spaceminer said:
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
Click to expand...
Click to collapse
Yes the 8.0 update is up for this phone I'm on stock firmware an I don't know if I will do the update until I see root for it ! I will let you what I decide !
J727P update
peter couniaz said:
Yes the 8.0 update is up for this phone I'm on stock firmware an I don't know if I will do the update until I see root for it ! I will let you what I decide !
Click to expand...
Click to collapse
I'm going to take the update to 8.0 an hope someone cames up with a Root process ! an it is the U4 bootloader so backdating the firmware should work if I don't like it !
peter couniaz said:
I'm going to take the update to 8.0 an hope someone cames up with a Root process ! an it is the U4 bootloader so backdating the firmware should work if I don't like it !
Click to expand...
Click to collapse
I'm already running Oreo. TWRP has problems with it. I can't make a backup of the OS. You can restore a back up, but you have to flash the BL file from ARG2 then wipe everything in TWRP first. SuperSU 2.82-SR5 will cause a boot loop. I'm going to try magisk 17.1. Honestly, I'm very disappointed with Samsung's Oreo... It's almost the exact same as Nougat, and the new camera sucks, very bad. They gave us Nougat, with Oreo 8.1 as the base firmware. That's my literal take on it. I'm definitely getting a Moto G6 after seeing this, and I'm going back to my stock build.
J727P update
Spaceminer said:
I'm already running Oreo. TWRP has problems with it. I can't make a backup of the OS. You can restore a back up, but you have to flash the BL file from ARG2 then wipe everything in TWRP first. SuperSU 2.82-SR5 will cause a boot loop. I'm going to try magisk 17.1. Honestly, I'm very disappointed with Samsung's Oreo... It's almost the exact same as Nougat, and the new camera sucks, very bad. They gave us Nougat, with Oreo 8.1 as the base firmware. That's my literal take on it. I'm definitely getting a Moto G6 after seeing this, and I'm going back to my stock build.
Click to expand...
Click to collapse
You haven't tried flashing back to nougat then !
peter couniaz said:
You haven't tried flashing back to nougat then !
Click to expand...
Click to collapse
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
J727P update
Spaceminer said:
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
Click to expand...
Click to collapse
Thank you for the info on downgrading back to nougat !
peter couniaz said:
Thank you for the info on downgrading back to nougat !
Click to expand...
Click to collapse
I've got 3 of 4 firmware files uploaded. The AP file is giving me trouble cause my WiFi sucks, and it keeps failing before it finishes. I did put together a full stock Oreo ROM but its got problems. You can only flash it using TWRP if you have the ARG2 bootloader, but, the ARG2 bootloader, won't allow Oreo to boot up no matter what. We'd need a custom boot.img and I can't make one. The ROM can't be flashed with the Oreo bootloader installed either, because it prevents TWRP from copying/writing to the data or system partitions. If it tries to, it'll reboot half way through. Magisk 17.1 will also lose root after awhile. We need a custom boot, or we need a modified root method and an updated TWRP to have any fun with it. SMH at Samsung right now. They gave us Oreo, with no milk, and a slap in the face. Nougat everything, running on Oreo 8.1 firmware... I'll never get over that. I'm running an ARG2 build cause everything works, and largely looks the same. I swear, they didn't even try. They just reskinned some Nougat apps and put them in an Oreo system. I will never buy another Samsung product after seeing this half hearted Oreo they gave us.
J727P update
Spaceminer said:
I've got 3 of 4 firmware files uploaded. The AP file is giving me trouble cause my WiFi sucks, and it keeps failing before it finishes. I did put together a full stock Oreo ROM but its got problems. You can only flash it using TWRP if you have the ARG2 bootloader, but, the ARG2 bootloader, won't allow Oreo to boot up no matter what. We'd need a custom boot.img and I can't make one. The ROM can't be flashed with the Oreo bootloader installed either, because it prevents TWRP from copying/writing to the data or system partitions. If it tries to, it'll reboot half way through. Magisk 17.1 will also lose root after awhile. We need a custom boot, or we need a modified root method and an updated TWRP to have any fun with it. SMH at Samsung right now. They gave us Oreo, with no milk, and a slap in the face. Nougat everything, running on Oreo 8.1 firmware... I'll never get over that. I'm running an ARG2 build cause everything works, and largely looks the same. I swear, they didn't even try. They just reskinned some Nougat apps and put them in an Oreo system. I will never buy another Samsung product after seeing this half hearted Oreo they gave us.
Click to expand...
Click to collapse
You are using the latest twrp try going back 2 builds on the twrp an see if that will stick on the full 8.1.0 firmware don't know if it will work but if you have the full 8.1.0 firmware give it a shot an let us all know if it does ! Or when you get the full firmware uploaded send me a link an I will try it ! Thank you !!
I have posted the oreo firmware here https://forum.xda-developers.com/galaxy-j7/how-to/sm-j727p-oreo-8-1-firmware-t3841778
HELP FLASH BACK J727P to nougout
i need some help, every time i try to downgrade to android 7 in this phone j727p, i get errors flashing modem, ive tried combination firmware, and full flash 4arg2 im currently 8.1.0 4brh5 and cant flash back to nougout
---------- Post added at 07:09 PM ---------- Previous post was at 07:04 PM ----------
Spaceminer said:
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
Click to expand...
Click to collapse
sr ive been trying to flash back the nougout firmware arg2 but still problems, the cp box in z3x uncheck, but still got errors with csc, i need to downgrade from brh5 and it wont let me, if you could be more specific how did you do the process
Galaxy J7 Perx (Boost) on J727PVPU4BRH5
Spaceminer said:
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
Click to expand...
Click to collapse
Dear Sirs;
Having had to replace my originally bought (Nov 17, 2017) J7 Perx from Boost, then bricking it and replacing it with a Galaxy S6 refurb from Boost, which was then STOLEN by a "friend" of 6(six) years, has been replaced by a NEWER J7 Perx. This device received at lest 3, if not 4 OTA updates, one of which was a supplemental firmware/software update. About Phone (and Samsung INFO app) NOW reveal the following detail:
HARDWARE VERSION; J727P.02
Mfg date; 03/15/2018
Software Version; J727PVPU4BRH5
Android Version; 8.1.0
Samsung Experience; 9.5
Baseband Version; J7272PVPU4BRH5
Build Number; M1AJQ.J727PVPU4BRH5
Android Security Patch; August 1, 2018.
If given instruction and link to necessary utility to extract the firmware from my device to my PC, I would be more than pleased to provide the files(s) procured from that process.
I look forward to hearing more about possible deodexed firmware to ROOT my newest device.
A custom ROM would be nice, too.
---------- Post added at 15:23 ---------- Previous post was at 15:14 ----------
Guess I should have browsed a few more posts before posting.
I found the link to all the 8.x firmwares for the various models, and must say "Bravo!" for the Herculean effort expended to collect, upload and make all that available.
Thanks!
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Thanks for the response
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
psychopac said:
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Click to expand...
Click to collapse
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
kash664 said:
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
Click to expand...
Click to collapse
Make sure to follow the flashing instructions mentioned by the thread OP properly
psychopac said:
Make sure to follow the flashing instructions mentioned by the thread OP properly
Click to expand...
Click to collapse
Yes. Hope everything turns out fine
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
I hope i can help !!
vishalrickz said:
I hope i can help !!
Click to expand...
Click to collapse
Sure sir