Related
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.
Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
I once Hard Bricked my phone. Then when I somehow recovered it and tried to install stock firmware, it went into bootloop, then I used g5 plus software to flash boot.img and it worked but after that I lost my original recovery and I have TWRP recovery instead and I can't update my software because it will hard brick again. I have tried reflashing stock Android (problem remained the same) and I am not sure but I guess I somehow modified my system and that's why I am not able to get my stock recovery back(I tried to flash that but that failed). Please help as I need to update my system because Within months Android O updates will roll out. Thanks.
Fastboot to stock. It's the only true way to get what you want.
Karlinski said:
Fastboot to stock. It's the only true way to get what you want.
Click to expand...
Click to collapse
I'm not able to. In My Fastboot it says "System status: Modified" instead of system status Official, so any idea how to get Official System status?
fastboot doesn't care about firmware status. if you want to get official, you need to relock your bootloader. There are instructions on how to do so on the forums here.
Karlinski said:
fastboot doesn't care about firmware status. if you want to get official, you need to relock your bootloader. There are instructions on how to do so on the forums here.
Click to expand...
Click to collapse
Then I'd be able to download system updates?
harshtomar1308 said:
Then I'd be able to download system updates?
Click to expand...
Click to collapse
Depends on what happened to your device when you hard bricked it in the first place and how you recovered from it.
If you recovered using the albus (Moto Z2 Play) blankflash, then I don't think you'll be able to re-flash the stock firmware completely, as you have a different bootloader to what's expected (i.e. Moto Z2 Play bootloader on a G5 Plus). You'd still be able to flash the system and modem side of the firmware, just likely not the GPT or bootloader. Thus, you're likely better off waiting for TWRP flashables of the stock Oreo ROM, which would mean you don't have to worry about your bootloader. Of course, that means you won't be able to take OTA updates again.
What device do you have and what stock firmware were you/are you running on your device? Maybe you're flashing either the wrong firmware or too old firmware for your device.
echo92 said:
Depends on what happened to your device when you hard bricked it in the first place and how you recovered from it.
If you recovered using the albus (Moto Z2 Play) blankflash, then I don't think you'll be able to re-flash the stock firmware completely, as you have a different bootloader to what's expected (i.e. Moto Z2 Play bootloader on a G5 Plus). You'd still be able to flash the system and modem side of the firmware, just likely not the GPT or bootloader. Thus, you're likely better off waiting for TWRP flashables of the stock Oreo ROM, which would mean you don't have to worry about your bootloader. Of course, that means you won't be able to take OTA updates again.
What device do you have and what stock firmware were you/are you running on your device? Maybe you're flashing either the wrong firmware or too old firmware for your device.
Click to expand...
Click to collapse
Yes, I used this method to regain my phone. I'm on XT1686 and build number is NPN25.137-15
My device is hard bricked
harshtomar1308 said:
I once Hard Bricked my phone. Then when I somehow recovered it and tried to install stock firmware, it went into bootloop, then I used g5 plus software to flash boot.img and it worked but after that I lost my original recovery and I have TWRP recovery instead and I can't update my software because it will hard brick again. I have tried reflashing stock Android (problem remained the same) and I am not sure but I guess I somehow modified my system and that's why I am not able to get my stock recovery back(I tried to flash that but that failed). Please help as I need to update my system because Within months Android O updates will roll out. Thanks.
Click to expand...
Click to collapse
I have installed the stock firmware on my Moto g5 plus and when I updated it to .67
The phone started to be updating but when the bar fills up then my phone just stucked. Please help me I cannot even go to bootloader or the fast boot. No logo nor any kind of signals are showing but no results please help me
Will i recive OTA update if i unlock the bootloader?
Androidtroll said:
Will i recive OTA update if i unlock the bootloader?
Click to expand...
Click to collapse
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise your phone should still function as if it weren't unlocked.
In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.
bazinga137 said:
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise, your phone should still function as if it weren't unlocked.
Click to expand...
Click to collapse
Yes the Same thing Happened
I had TWRP recovery and I installed the Security Patch
my Phone Stuck at TWRP
but it has One solution
First, take the data backup of all in twrp at your sd card
now install any custom Rom
Reboot your device and check the rom is working or not
do reboot and go back to your Twrp and Restore the backup
I tested it and It worked perfectly
echo92 said:
In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.
Click to expand...
Click to collapse
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom
Androidtroll said:
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom
Click to expand...
Click to collapse
Just unlocking the BL wouldn't be enough to edit system files. You'll need root privileges to do so and for that you will have to flash/boot TWRP to install a root app like magisk.
So all the useful information @echo92 posted above is significant for you.
Sent from my Moto G5 Plus using XDA Labs
Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.
Frawgg said:
Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.
Click to expand...
Click to collapse
If anything in /system or /oem is tampered like installing a camera mod (or just mounting system r/w) the only way to receive future OTA updates is flashing your current ROM incl. stock recovery via fastboot.
Sent from my Moto G5 Plus using XDA Labs
Hey. my phone was bootlooped and i recover to stock rom marshmallow 6.0. then came update 6.0.1 it was ok i installed it. after that came Nougat 7.1 update and in installation time phone won't boot. bootloader was unlocked. computer can not see phone, it says usb device not recognized. phone is moto g4 xt1622 dual sim
is there any way to survive? motherboard is dead? thanks. i can not know what to do i am so sorry i feel so bad
just there is white light phone is charging, but no switch on and no bootloader menu. nothing happens
gioyocho said:
Hey. my phone was bootlooped and i recover to stock rom marshmallow 6.0. then came update 6.0.1 it was ok i installed it. after that came Nougat 7.1 update and in installation time phone won't boot. bootloader was unlocked. computer can not see phone, it says usb device not recognized. phone is moto g4 xt1622 dual sim
is there any way to survive? motherboard is dead? thanks. i can not know what to do i am so sorry i feel so bad
just there is white light phone is charging, but no switch on and no bootloader menu. nothing happens
Click to expand...
Click to collapse
Looks like you downgraded your bootloader and then take ota = hardbrick. Have you tried that guide and read the discussion of others? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
strongst said:
Looks like you downgraded your bootloader and then take ota = hardbrick. Have you tried that guide and read the discussion of others? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
Thanks for reply! i used your link for stock rom marshmallow. but now computer can not see phone, it says not recognized. i can not get access to fastboot menu. i am going to take it to programmer, but i have no hope. so sad
gioyocho said:
Thanks for reply! i used your link for stock rom marshmallow. but now computer can not see phone, it says not recognized. i can not get access to fastboot menu. i am going to take it to programmer, but i have no hope. so sad
Click to expand...
Click to collapse
What do you see in Device Manager when your device is connected, do you see Qualcomm HS-USB 9008 or similar listed? Do you have the Motorola drivers installed on your computer, and, if you have Windows 8.1 or 10, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
I'm confused that you used the link provided by strongst to flash a MM firmware though, from what I recall reading of your post it sounded like you soft bricked but somehow managed to flash a MM firmware. However, as strongst pointed out, if you'd downgraded your device when you flashed MM, taking the OTA update would have corrupted your bootloader, leaving you with the hard brick and no fastboot mode.
EDIT - looking through your previous posts, it looked like you had formally updated to stock Nougat, then downgraded to the stock MM firmware (but still had a Nougat bootloader - you cannot generally downgrade bootloaders), then using an old Nougat OTA corrupted your bootloader. Ouch... What firmware did you download?
I'd try to install the Motorola drivers to your computer https://support.motorola.com/us/en/drivers , disable driver signature enforcement if you can and then try the blankflash from that guide. If the blankflash can communicate with your device, then it may be able to flash a basic bootloader and give you fastboot. Ensure you use your original Motorola cable or a good quality USB data cable and that the physical connection to your device is good.
I am also faced same issue ,even Motorola service centre guys won't helped me. But I did it with patience ,I sure your problem will be with Qualcomm usb driver ,so install it correctly .
echo92 said:
What do you see in Device Manager when your device is connected, do you see Qualcomm HS-USB 9008 or similar listed? Do you have the Motorola drivers installed on your computer, and, if you have Windows 8.1 or 10, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
I'm confused that you used the link provided by strongst to flash a MM firmware though, from what I recall reading of your post it sounded like you soft bricked but somehow managed to flash a MM firmware. However, as strongst pointed out, if you'd downgraded your device when you flashed MM, taking the OTA update would have corrupted your bootloader, leaving you with the hard brick and no fastboot mode.
EDIT - looking through your previous posts, it looked like you had formally updated to stock Nougat, then downgraded to the stock MM firmware (but still had a Nougat bootloader - you cannot generally downgrade bootloaders), then using an old Nougat OTA corrupted your bootloader. Ouch... What firmware did you download?
I'd try to install the Motorola drivers to your computer https://support.motorola.com/us/en/drivers , disable driver signature enforcement if you can and then try the blankflash from that guide. If the blankflash can communicate with your device, then it may be able to flash a basic bootloader and give you fastboot. Ensure you use your original Motorola cable or a good quality USB data cable and that the physical connection to your device is good.
Click to expand...
Click to collapse
Thanks for reply!
i had installed many drivers. even qualcomm and motorola, but situation is such. see file attachment. looks like my phone is in coma. i have windows 10. i will say long story short
1. i had android 8.1.0 RR, it was heating and i changed to RR 7.1.2. it worked good
2. it was also heating and i decides to change kernel and phone stop on RR logo, it was rounding but phone won't working. i had no backup or rom files
3. then i installed stock rom 6.0 marshmallow from fastboot with cmd, i downloded it from motorola's official site. i had 6.0 and bootloader unlocked. than came 6.0.1 ota and i updated it was ok. than came also ota update Nougat and installation process phone won't boot
echo92 said:
What do you see in Device Manager when your device is connected, do you see Qualcomm HS-USB 9008 or similar listed? Do you have the Motorola drivers installed on your computer, and, if you have Windows 8.1 or 10, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
I'm confused that you used the link provided by strongst to flash a MM firmware though, from what I recall reading of your post it sounded like you soft bricked but somehow managed to flash a MM firmware. However, as strongst pointed out, if you'd downgraded your device when you flashed MM, taking the OTA update would have corrupted your bootloader, leaving you with the hard brick and no fastboot mode.
EDIT - looking through your previous posts, it looked like you had formally updated to stock Nougat, then downgraded to the stock MM firmware (but still had a Nougat bootloader - you cannot generally downgrade bootloaders), then using an old Nougat OTA corrupted your bootloader. Ouch... What firmware did you download?
I'd try to install the Motorola drivers to your computer https://support.motorola.com/us/en/drivers , disable driver signature enforcement if you can and then try the blankflash from that guide. If the blankflash can communicate with your device, then it may be able to flash a basic bootloader and give you fastboot. Ensure you use your original Motorola cable or a good quality USB data cable and that the physical connection to your device is good.
Click to expand...
Click to collapse
now i changed something, disabled test mode windows and it says some qualcomm device in device manager port. what i can do now?
Omg people i survived it again. you make me day i am so happy. just there is december security patch 2016 but i feel so great. the problem was next: when i installed many drivers and applications, windows came to test mode (it was written right and down side of screen), then i go to youtube and did everything exactly run as administrator and run words, then i restarted computer and it saw my qualcomm driver 9008 or something, i used blankfish file for install bootloader and downloaded 7.0 rom for 1 april security patches. i swear that never root, or set twrp, or unlock bootloader, because it is so risky. Thanks everyone so much. admin you can close the topic
i must say something too. i do know reason why my phone was bricked, maybe main reason is that when i first time survived phone and installed stock 6.0 firmware, then i try to re-lock bootloader, and after 6.0 to 7.0 install i got bricked. i say this because now when i installed bootloader, there is written oem_locked it means bootloader locked. looks like first time i locked bootloader, but screen was and is same (when i start up phone it says bootloader unlocked won't trust wait 5 seconds). so big thanks you guys
gioyocho said:
i must say something too. i do know reason why my phone was bricked, maybe main reason is that when i first time survived phone and installed stock 6.0 firmware, then i try to re-lock bootloader, and after 6.0 to 7.0 install i got bricked. i say this because now when i installed bootloader, there is written oem_locked it means bootloader locked. looks like first time i locked bootloader, but screen was and is same (when i start up phone it says bootloader unlocked won't trust wait 5 seconds). so big thanks you guys
Click to expand...
Click to collapse
Hmm, if you previously had stock Nougat on your device, you wouldn't have been able to lock your bootloader with the marshmallow firmware ( you need the stock firmware as new or newer than your Nougat bootloader).
Regardless, it's good that you got your device working again, just as a reminder, please if you do decide to flash old stock firmware, do not use old OTA updates, they are not safe to use on downgraded devices. We're lucky to have this blankflash leaked to us. If you flash old stock firmware, only use newer stock firmware to update.
echo92 said:
Hmm, if you previously had stock Nougat on your device, you wouldn't have been able to lock your bootloader with the marshmallow firmware ( you need the stock firmware as new or newer than your Nougat bootloader).
Regardless, it's good that you got your device working again, just as a reminder, please if you do decide to flash old stock firmware, do not use old OTA updates, they are not safe to use on downgraded devices. We're lucky to have this blankflash leaked to us. If you flash old stock firmware, only use newer stock firmware to update.
Click to expand...
Click to collapse
yes i do not know. it is strange situation. example now i had 2016 december security patch. came again ota update 1 april 2018 security patch and while installing finished again boot dead. and i survive again with newest rom. when i survive first time i just downloaded older bootloder file which was in the topic and that's why there was 2016 security patch. after download lastest rom with security patch and with new bootloader, and replace with new bootloader. now there is 1 april 2018 security patch
i guess ota updates is not safe
gioyocho said:
yes i do not know. it is strange situation. example now i had 2016 december security patch. came again ota update 1 april 2018 security patch and while installing finished again boot dead. and i survive again with newest rom. when i survive first time i just downloaded older bootloder file which was in the topic and that's why there was 2016 security patch. after download lastest rom with security patch and with new bootloader, and replace with new bootloader. now there is 1 april 2018 security patch
i guess ota updates is not safe
Click to expand...
Click to collapse
I'm confused, if you flashed the Dec 2016 stock ROM, the next update you'd have received would have likely been the March 2017 security patch OTA (NPJS25.93-14-4) update. How did you get the April 2018 OTA update? If your device had been on a previously newer build of stock Nougat, using that would have been a bad idea.
If you fully updated to the April 2018 security patch stock ROM, with the bootloader at version B1:07, you may be okay taking OTA updates. Please next time, double check the firmware you need. There's many sites with various firmwares and some of them can be quite old.
echo92 said:
I'm confused, if you flashed the Dec 2016 stock ROM, the next update you'd have received would have likely been the March 2017 security patch OTA (NPJS25.93-14-4) update. How did you get the April 2018 OTA update? If your device had been on a previously newer build of stock Nougat, using that would have been a bad idea.
If you fully updated to the April 2018 security patch stock ROM, with the bootloader at version B1:07, you may be okay taking OTA updates. Please next time, double check the firmware you need. There's many sites with various firmwares and some of them can be quite old.
Click to expand...
Click to collapse
No, i did not flashed 2016 stock rom, i flashed 2018 stock rom, but bootloader file was old, because i downloded it from old topic. when i replaced 2018 stock rom's bootloader file instead of old bootloader file, now i have 2018 1 april security patch. i think i can not install ota updates if them future come, because again my phone will be bricked
one reason is that if bootloader is unlocked, you do not have pemission to change something, but yesterday i installed ota update from 6.0 to 6.0.1 or security patch i do not know exactly, and while Nougat install finishes phone was bricked
gioyocho said:
Thanks for reply!
i had installed many drivers. even qualcomm and motorola, but situation is such. see file attachment. looks like my phone is in coma. i have windows 10. i will say long story short
1. i had android 8.1.0 RR, it was heating and i changed to RR 7.1.2. it worked good
2. it was also heating and i decides to change kernel and phone stop on RR logo, it was rounding but phone won't working. i had no backup or rom files
3. then i installed stock rom 6.0 marshmallow from fastboot with cmd, i downloded it from motorola's official site. i had 6.0 and bootloader unlocked. than came 6.0.1 ota and i updated it was ok. than came also ota update Nougat and installation process phone won't boot
Click to expand...
Click to collapse
just to be clear this all happened from RR 8.1.0? why did you not just follow what i said here and start your RR 7.1.2?
https://forum.xda-developers.com/showpost.php?p=76628308&postcount=1828
You could have saved yourself all the hassle
gioyocho said:
No, i did not flashed 2016 stock rom, i flashed 2018 stock rom, but bootloader file was old, because i downloded it from old topic. when i replaced 2018 stock rom's bootloader file instead of old bootloader file, now i have 2018 1 april security patch. i think i can not install ota updates if them future come, because again my phone will be bricked
one reason is that if bootloader is unlocked, you do not have pemission to change something, but yesterday i installed ota update from 6.0 to 6.0.1 or security patch i do not know exactly, and while Nougat install finishes phone was bricked
Click to expand...
Click to collapse
I'm still confused, you mentioned the December 2016 security patch (NPJ25.93-14), is that the firmware you were on before? I'm just trying to work out what firmware you had/were flashing on your device (since you mentioned Marshmallow 6.0.1 and then mentioned April 2018, there's a lot of builds inbetween those versions...)
I'm also confused by the reasoning for using the old bootloader file with the April 2018 stock ROM, can you explain the thinking behind mixing old and new firmware files, or have I misunderstood you?
You mentioned previously with bricking on the April 2018 OTA, what firmware version were you on then, if you can remember? I'm just curious as I've not heard of bricks on the April 2018 update yet.
The safest way to use OTA updates is to have your device formally on the same security patch level. In your case, you must ensure your device has the April 2018 B1:07 bootloader/GPT/system/modem etc. Doesn't matter if your bootloader is unlocked or locked (though a locked bootloader would strictly enforce having the same firmware patch level). Mixing firmwares is not a good idea for OTA updates as you found out. When you downgraded to Marshmallow, you likely did not downgrade your bootloader (your bootloader would have blocked the flashing of an older bootloader), so you had a Nougat bootloader but a Marshmallow system. Taking a Marshmallow or old Nougat OTA would have likely corrupted your newer Nougat bootloader (as OTA updates do not appear to check your bootloader version). Hence why you hard bricked then. I'm curious as to why this may have happened with the April 2018 OTA though.
Ayan Uchiha Choudhury said:
just to be clear this all happened from RR 8.1.0? why did you not just follow what i said here and start your RR 7.1.2?
https://forum.xda-developers.com/showpost.php?p=76628308&postcount=1828
You could have saved yourself all the hassle
Click to expand...
Click to collapse
Thanks for reply. your post was after i installed another kernel and i had bootloop