I flashed TWRP and the Stock ROM from here - https://github.com/motoxplay/stock (https://github.com/motoxplay/stock/...1563_LUX_RETAIL_DS_6.0.1_MPD24.107-52.xml.zip) and it's showing No service after that.
I tried going to *#*#4636#*#* and it looks like radio is off. I've Moto X Play Dual Sim. Any ideas?
Check your IMEI.If it shows put your phone in fastboot mode and enter these commands.Use the files from stock rom
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
effingbadluck said:
Check your IMEI.If it shows put your phone in fastboot mode and enter these commands.Use the files from stock rom
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Thanks. The IMEI shows. I tried the steps you mentioned. No luck.
Probably I'm using the wrong ROM?
Hi firmware experts! I have been working on getting a Turbo 2 working after water damage for the last couple of weeks. I am not an expert on any of this, so learning is where most of the time has gone.
After the rice drying, etc, the phone was in bootloop. I tried reflashing firmware, and I finally was able to successfully flash stock 6.0.1, but the phone remained in bootloop. I took the phone apart, removed a bunch of EMI shields, and scrubbed the components with 91% isopropyl, put it back together, and it booted right up. All tested components worked perfectly, ..... that is until I tried to activate the phone on a network. That's when I realized the cellular radio isn't working (wifi and bluetooth radios are intact).
Indications that cellular radio is non-functional:
*after activation attempt, phone call attempts result in the phone telling me to turn airplane mode off when it is off already
*sim card is being read but network signal not showing in notification bar or other such places
*under sim status in the settings the 'Service state' reads "Voice: Radio off / Data: Radio off" with an active sim card in the phone, rather than "Voice: In service..." or "Voice: Out of service..." as a Turbo I used for comparison displays
I'm not ruling out that there could be water induced damage to the cellular circuitry, but it seems strange and unfortunate that that would be the only issue that would remain. I'm wondering if I messed up the modem firmware during flashing.
Here is my most recent flash sequence with 6.0.1 (I believe I downloaded from mirrors.lolinet.com):
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
I didn't have any errors.
Is there a chance that I flashed a firmware from another region (I'm US) and that is the prob? I've tried flashing earlier stock firmwares I can find, ie. 5.1.1 but I get 'preflash validation failed',presumably because by bootloader won't let me downgrade.
XT1585_KINZIE_VERIZON_6.0.1_MCK24.183-22_cid2_subsidy-DEFAULT_CFC.xml
Would it be a good idea to try 'fastboot flash modem NON-HLOS.bin' or fsg by itself? Maybe I could try to just flash the modem and fsg from another package, which I think the bootloader might let me do.
I've read that you want to have a backup of the EFS, but it doesn't seem like you can without root, which I don't think I can do with my locked bootloader? I do still have an IMEI.
I am trying everything I can to get this working, any help is greatly appreciated. If you guys say it's no chance of a software fix then I'll go back into the phone and check the antenna connector and remove the rest of the EMI shields and scrub what's underneath, but I don't want to do this until I am more sure it isn't a software issue because I don't want to take the chance of breaking things in there when it wasn't necessary.
Thanks a ton!
No Radio
implausibleg said:
Hi firmware experts! I have been working on getting a Turbo 2 working after water damage for the last couple of weeks. I am not an expert on any of this, so learning is where most of the time has gone.
After the rice drying, etc, the phone was in bootloop. I tried reflashing firmware, and I finally was able to successfully flash stock 6.0.1, but the phone remained in bootloop. I took the phone apart, removed a bunch of EMI shields, and scrubbed the components with 91% isopropyl, put it back together, and it booted right up. All tested components worked perfectly, ..... that is until I tried to activate the phone on a network. That's when I realized the cellular radio isn't working (wifi and bluetooth radios are intact).
Indications that cellular radio is non-functional:
*after activation attempt, phone call attempts result in the phone telling me to turn airplane mode off when it is off already
*sim card is being read but network signal not showing in notification bar or other such places
*under sim status in the settings the 'Service state' reads "Voice: Radio off / Data: Radio off" with an active sim card in the phone, rather than "Voice: In service..." or "Voice: Out of service..." as a Turbo I used for comparison displays
I'm not ruling out that there could be water induced damage to the cellular circuitry, but it seems strange and unfortunate that that would be the only issue that would remain. I'm wondering if I messed up the modem firmware during flashing.
Here is my most recent flash sequence with 6.0.1 (I believe I downloaded from mirrors.lolinet.com):
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
I didn't have any errors.
Is there a chance that I flashed a firmware from another region (I'm US) and that is the prob? I've tried flashing earlier stock firmwares I can find, ie. 5.1.1 but I get 'preflash validation failed',presumably because by bootloader won't let me downgrade.
XT1585_KINZIE_VERIZON_6.0.1_MCK24.183-22_cid2_subsidy-DEFAULT_CFC.xml
Would it be a good idea to try 'fastboot flash modem NON-HLOS.bin' or fsg by itself? Maybe I could try to just flash the modem and fsg from another package, which I think the bootloader might let me do.
I've read that you want to have a backup of the EFS, but it doesn't seem like you can without root, which I don't think I can do with my locked bootloader? I do still have an IMEI.
I am trying everything I can to get this working, any help is greatly appreciated. If you guys say it's no chance of a software fix then I'll go back into the phone and check the antenna connector and remove the rest of the EMI shields and scrub what's underneath, but I don't want to do this until I am more sure it isn't a software issue because I don't want to take the chance of breaking things in there when it wasn't necessary.
Thanks a ton!
Click to expand...
Click to collapse
I have the same problem, water damage, replaced the screen and now no radio. Not sure on what Rom i orginaly was before. The sim works but no signal
Had the same thing.
You're using file XT1585_KINZIE_VERIZON_6.0.1_MCK24.183-22_cid2_subsidy-DEFAULT_CFC.xml
There is a different version, for the model with an "S" in it.
Try file name: XT1585_KINZIE_VERIZON_6.0.1_MCKS24.183-22_cid2_subsidy-DEFAULT_CFC.xml
This worked for me for XT1580
i need help, same exact issue. anyone?
I have a second Moto G4 and I was curious if anyone got a fix for these issues? it happened a while back when I was trying to go back to factory image. there was a lot of errors. I cant seem ti find the screenshots of the errors that I got at the time. This was around January or so.There is no Mac Address in settings and theres no ip no way to turn data on and when I try wifi. it automatically shuts off. Doesn't detect my Sim Card or Service. says Emergency calls only
I have the same problem, I have got the sim working but no wifi or bluetooth yet.
When I load adb shell and grep the wireless module it says "WCNSS DRIVER NOT FOUND" even though it is there.
I found fix. Delete the old os completely and have the right stock os ready to adb flash. Id say google ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml .. then put it in your minimal adb and fastboot file. go to bootloader and then back to computer to do the shift right click in the file on pc and get terminal up and copy and paste this
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Fastboot flash logo logo.bin
The fastboot restart the device and you should be back with the wifi and data. I bought a new phone in feb or march because of this issue and couldn't find a fix till I googled constantly.
I had to delete the os completely and then flash the factory boot image with
AArnold2 said:
I have the same problem, I have got the sim working but no wifi or bluetooth yet.
When I load adb shell and grep the wireless module it says "WCNSS DRIVER NOT FOUND" even though it is there.
Click to expand...
Click to collapse
NeroCZA said:
I found fix. Delete the old os completely and have the right stock os ready to adb flash. Id say google ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml .. then put it in your minimal adb and fastboot file. go to bootloader and then back to computer to do the shift right click in the file on pc and get terminal up and copy and paste this
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Fastboot flash logo logo.bin
The fastboot restart the device and you should be back with the wifi and data. I bought a new phone in feb or march because of this issue and couldn't find a fix till I googled constantly.
I had to delete the os completely and then flash the factory boot image with
Click to expand...
Click to collapse
What are the proper steps to completely remove your entire OS safely? Do you mean to just overwrite the current one?
This procedure overwrites your current or completely. You will lose the contents of the internal SD card
Sent from my LG-LS980 using Tapatalk
dayne.rhoades said:
What are the proper steps to completely remove your entire OS safely? Do you mean to just overwrite the current one?
Click to expand...
Click to collapse
Save what you want and it should be safe to just completely wipe your phone cache and all no overwrite.. Then have the stock ready to flash in the file on computer and do the the above steps. Ive done it on both my moto g4's because on my main one which I'm sending off to Motorola for screen repairs, I wiped my phone without thinking about the stock os. panicked but remembered the back to stock steps and attempted them. Ive always gotten errors or wifi and data wipe from over writing with the codes. So I just flashed on the one I deleted OS off of and it worked.
tekweezle said:
This procedure overwrites your current or completely. You will lose the contents of the internal SD card
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Yeah sadly you will lose everything unless you have it all saved. I was mad about losing a lot of things but I was having screen issues and data wifi issues to try to fix. I do have data and wifi now. I just wish I saved what I could.
Would the android data recovery program recover anything? Ive been searching how to recover wiped data. Internet is full of info on how wiped data can be recovered. I just want the text messages and stuff. I had important things in some the text messages I lost
You should save to the external SD card.
Sent from my LG-LS980 using Tapatalk
Delete the old OS via twrp?
You should have made a backup with twrp. Then you could restore your os as it was.
Sent from my Moto G (4) using Tapatalk
Nope the firmware linked above caused the phone to go in to a boot loop.
AArnold2 said:
Delete the old OS via twrp?
Click to expand...
Click to collapse
Yeah that's what I did. Then I flashed the stock rom I googled. Ive been trying to update to nougat for past 2 days since I got back to proper stock rom.
you can;t flash any of the official firmwares via TWRP. You can flash a custom rom or restore a backup of your OS though.
to flash/reload an official firmware, you need ADB and fastboot running from a computer.
Exactly. Don't try with TWRP.
tekweezle said:
you can;t flash any of the official firmwares via TWRP. You can flash a custom rom or restore a backup of your OS though.
to flash/reload an official firmware, you need ADB and fastboot running from a computer.
Click to expand...
Click to collapse
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Vs1607 said:
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Click to expand...
Click to collapse
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
smog2699 said:
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
Click to expand...
Click to collapse
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it ?
.
.
.
Just curious ! ?
Vs1607 said:
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it Just curious ! ?
Click to expand...
Click to collapse
It was posted in the forum at least three times.
thorin0815 said:
It was posted in the forum at least three times.
Click to expand...
Click to collapse
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
hardythaker said:
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
Click to expand...
Click to collapse
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
hardythaker said:
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
Click to expand...
Click to collapse
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
echo92 said:
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
Click to expand...
Click to collapse
April ota is the last , but no one have it
leap_ahead said:
April ota is the last , but no one have it
Click to expand...
Click to collapse
Yeah the update note appears to be up but as you mentioned it's not been released yet to any channel. So for now the latest firmware we have is the Feb 2018 build.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
[STRIKE]fastboot erase userdata[/STRIKE]
fastboot erase customize
fastboot erase clogo
fastboot reboot
hardythaker said:
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
<Snip>
Click to expand...
Click to collapse
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Thanks mate. Am going to flash this tomorrow. Will surely let you know the outcome. Anyway if all this allow me to use my phone at least for an hour, I will take the backup of the necessary data and then will proceed with wipe data/factory reset.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
hardythaker said:
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
Click to expand...
Click to collapse
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
echo92 said:
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
Click to expand...
Click to collapse
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
hardythaker said:
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
Click to expand...
Click to collapse
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Tried with mobile data too, but still same issue. Anyway am in service center now let's see what they say.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Okay so after one-month of stupidity from service center and some other guys finally I myself resolved the issue.
1) Service center tried to flash the rom but didn't resolved the issue.
2) They changed the battery, but still the same issue.
3) They said that this is motherboard issue and it will cost 5200 INR.
Then gave my phone on yaantra .com to repair it they kept the phone for 5 days and said the same thing that it is a motherboard issue as network circuit is not working properly.
( In between this I end up buying OnePlus 6 :victory: :victory: )
Then I bought one new damaged phone in which motherboard was working fine. I replaced that motherboard with mine and still the same issue. After this I started disconnecting parts one by one which are there on display pannel. After checking speaker, vibrator, flash, when I disconnected the fingerprint sensor and rebooted the phone it was totally fine and no more reboots.
I never thought that a corrupted/damaged fingerprint scanner can do this kind of wired issue to a phone. .Now this will be a spare phone without fingerprint scanner. Thanks for your help @echo92