Related
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
jaed.43725 said:
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
Click to expand...
Click to collapse
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
luiseteyo said:
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
Click to expand...
Click to collapse
Ok. So what I did was kinda following your setup here. I had to get the Android SDK first. Then extract that into C:/. Then I got the 4.3 like you said and extracted that C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools. Then because of the new SDK I put the phone into the first 3-button mode. I then ran flash-all. And after a minute I had stock 4.3.
Hello, since i had gps issues i've reflashed the modem on adb and then erased modemst like this:
mfastboot flash modem [email protected]@[email protected]@NON-HLOS-64bit.bin
fastboot erase modemst1
fastboot erase modemst2
So the gps seems to be ok now, but the phone data is stuck on edge, and if i force 3g from the settings it doesn't connect at all
so i've putted stock recovery , wiped all data and installed a complete stock update but with no luck.
anyone have some idea?
EDIT: i've noticed that i don't have imei anymore... how to restore it?
reddevilx said:
Hello, since i had gps issues i've reflashed the modem on adb and then erased modemst like this:
mfastboot flash modem [email protected]@[email protected]@NON-HLOS-64bit.bin
fastboot erase modemst1
fastboot erase modemst2
So the gps seems to be ok now, but the phone data is stuck on edge, and if i force 3g from the settings it doesn't connect at all
so i've putted stock recovery , wiped all data and installed a complete stock update but with no luck.
anyone have some idea?
EDIT: i've noticed that i don't have imei anymore... how to restore it?
Click to expand...
Click to collapse
This is only a theory.
You need to else another rooted device ze550kl.
Commands for new device:
adb shell
su
cat /dev/block/mmcblk0p16 > /mnt/sdcard/modemst1.img
cat /dev/block/mmcblk0p17 > /mnt/sdcard/modemst2.img
Commands for old device:
adb reboot bootloader
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
The way to "/dev/block/mmcblk0p16" and "/dev/block/mmcblk0p17" is for a device ze500kl. I do not know to way for your device ze550kl.
Thank you Muminek111,
i've tried but with no luck, i've copied and flashed mmcblk0p16 and mmcblk0p17, the files exists but it doesn't change anything.
reddevilx said:
Thank you Muminek111,
i've tried but with no luck, i've copied and flashed mmcblk0p16 and mmcblk0p17, the files exists but it doesn't change anything.
Click to expand...
Click to collapse
I do not know if your device ze550kl has "modemst1" partition name "mmcblk0p16". It's the name for ze500kl device. You have to search in folder dev/block/............ I have the names in folder dev/block/platform/soc.0/7824900.sdhci/by-name.
You can flash back modem partition if you will know the name. The name of my modem partition is mmcblk0p38.
I don't understand;
this is the /dev/block/platform/7824900.sdhci
http://pastebin.com/Ebit7VFJ
this is /dev/block/platform/7824900.sdhci/by-name
http://pastebin.com/fx8FbBdU
modem is p35, modemst1 is p36 and modemst2 is p37?
i think i'm making a mistake because doing so i have a huge modemst2
i also don't understand why restoring a full twrp backup doesn't solve it
reddevilx said:
I don't understand;
this is the /dev/block/platform/7824900.sdhci
http://pastebin.com/Ebit7VFJ
this is /dev/block/platform/7824900.sdhci/by-name
http://pastebin.com/fx8FbBdU
modem is p35, modemst1 is p36 and modemst2 is p37?
i think i'm making a mistake because doing so i have a huge modemst2
i also don't understand why restoring a full twrp backup doesn't solve it
Click to expand...
Click to collapse
I think that the twrp recovery doesn't backs up all partitions.
This are my screenshots the folders from an apk Total Commander.
https://drive.google.com/file/d/0B7F3ZXr565GkYWJJT1ByX0VqQTQ/view?usp=drivesdk
https://drive.google.com/file/d/0B7F3ZXr565GkdXFxSVluSHAzUXM/view?usp=drivesdk
But everything shows to the folder dev/block/
Therefore is the command cat /dev/block/.......... > /mnt/sdcard/modemst1.img
OK, so now with total commander i found that
Modem is 41
Modemst1 is 18
Modemst2 is 19
i've flashed the new ones but i'm still with null imei.
Thank you anyway i've learned something new
You should back up the partition before every command erase partition.
I've made a backup from a working phone but it doesn't work, i think that the board may be faulty.
Thank you anyway
Hi all,
By mistakenly i run the command "fastboot clear all" on my moto x play (XT1562) Dual Sim,
Now IMEI number showing 0 so i am not able to register to a network because of this no calls/sms.
I done research on this and tried with by flashing custom ROM nothing works, then i went to moto x play service center they said need to change motherboard so i came back.
now i am fully confused
please anyone help me how to get back my IMEI number. and i run the getvar command in the information i am able to see my original IMEI number but when i dial *#06# both the IMEI number shows 0.
please plz... help me how i can solve this.
Thanks
About ur imei soln
Nmurthy2692 said:
Hi all,
By mistakenly i run the command "fastboot clear all" on my moto x play (XT1562) Dual Sim,
Now IMEI number showing 0 so i am not able to register to a network because of this no calls/sms.
I done research on this and tried with by flashing custom ROM nothing works, then i went to moto x play service center they said need to change motherboard so i came back.
now i am fully confused
please anyone help me how to get back my IMEI number. and i run the getvar command in the information i am able to see my original IMEI number but when i dial *#06# both the IMEI number shows 0.
please plz... help me how i can solve this.
Thanks
Click to expand...
Click to collapse
i hav similar problem few days back(moto x play xt 1562 imei 0)....moto care said i want to replace my motherboard which is very costly. so one of my frnds frnd resolve this problem..u cn whtsapp me on +918381086001 for further details..like to help u bye
Nmurthy2692 said:
Hi all,
By mistakenly i run the command "fastboot clear all" on my moto x play (XT1562) Dual Sim,
Thanks
Click to expand...
Click to collapse
First of all: don't listen anyone about replacing mainboard e.t.c.
Try to reflash your phone with latest factory firmware via RSD Lite or manually in fastboot mode. Then perform a factory reset and boot your smartphone into Android.
Hope it will help you.
Follow flashing instructions in this thread:
https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Download stock firmware here:
https://github.com/motoxplay/stock
Good luck!
summer.cat said:
First of all: don't listen anyone about replacing mainboard e.t.c.
Good luck!
Click to expand...
Click to collapse
Hi Thank you for your valuable time providing to solve my problem.
I tried flashing custom rom as you suggested ,
ROM Version which i download : XT1562_LUX_RETASIA_DS_6.0.1_MPDS24.107-52-5.xml
flashed it on fastboot mode still not showing any network and IMEI also 0.
I re-flash the modem by running these commands
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
then also same problem.
by the way while flashing 1st time i removed sim card from the phone and after flashing ROM i inserted sim card.
2nd time i did not removed sim card from the phone and tried flashing stock rom both the ways not working for me.
Please help me whats happening with my phone.
Thank you.
Nmurthy2692 said:
Hi Thank you for your valuable time providing to solve my problem.
I tried flashing custom rom as you suggested ,
ROM Version which i download : XT1562_LUX_RETASIA_DS_6.0.1_MPDS24.107-52-5.xml
flashed it on fastboot mode still not showing any network and IMEI also 0.
I re-flash the modem by running these commands
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
then also same problem.
by the way while flashing 1st time i removed sim card from the phone and after flashing ROM i inserted sim card.
2nd time i did not removed sim card from the phone and tried flashing stock rom both the ways not working for me.
Please help me whats happening with my phone.
Thank you.
Click to expand...
Click to collapse
Try these
http://www.androidbrick.com/ultimat...agon-xiaomi-mi5-imei-and-baseband-repair-fix/
http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/
Solution
Nmurthy2692 said:
Hi Thank you for your valuable time providing to solve my problem.
I tried flashing custom rom as you suggested ,
ROM Version which i download : XT1562_LUX_RETASIA_DS_6.0.1_MPDS24.107-52-5.xml
flashed it on fastboot mode still not showing any network and IMEI also 0.
I re-flash the modem by running these commands
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
then also same problem.
by the way while flashing 1st time i removed sim card from the phone and after flashing ROM i inserted sim card.
2nd time i did not removed sim card from the phone and tried flashing stock rom both the ways not working for me.
Please help me whats happening with my phone.
Thank you.
Click to expand...
Click to collapse
Can u reach me..if ur problem does not get solved I cn help feel free to contact 9975877687..bye
I have a similar unsolved problem here:
https://forum.xda-developers.com/mot...mei-0-t3857049
---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------
Has a definitive solution been found to all this?
I also accidentally run the ****ing command "fastboot erase all"
Motorola could not make protected partitions as on other phones to avoid these accidents? holy ****..
Use the following commands and flash the stock given in the below link.
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 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
Link:- https://github.com/motoxplay/stock
Is this issue solved ?
I know the thread is old but I believe i can help.
adukale said:
Is this issue solved ?
I know the thread is old but I believe i can help.
Click to expand...
Click to collapse
Hey, I've been trying to fix my imei on my mxp, but I've tried the solutions in this thread already and it doesn't seem to work. Can you please help me?
I lost my baseband & IMEI due to wrong flashing and unlocking methods. I did 10-15 flashings and try some methods but none of them worked.
So I found myself another method and grabbed some files that are required to recover IMEI.
Requirements:
Unlocked bootloader(Official or unofficial). You get unofficial methods to unlock bootloader on the internet.
Process:
Step 1:
Download the attachment given below.
Extract it somewhere.
Boot your device into fastboot mode and make sure it's unlocked.
Open extracted folder and run command prompt mode and run following fastboot commands:
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
After successful flashing of above files reboot your device and check your IMEI.
You can now see 0 infront of IMEI.
Step 2:
Enable debugging mode and connect your device to PC.
Check is your device connected or not via adb devices
Now run following commands:
Code:
adb shell
su
setprop sys.usb.config diag,adb
Now open WriteDualIMEI(W+G_eMMC).exe included in the attachment given below.
Your can see COM port in the open dialog box.
Enter your IMEI and press START
Now reboot your device & you will have your IMEI & baseband back as factory mobile.
prashantvrm said:
I lost my baseband & IMEI due to wrong flashing and unlocking methods. I did 10-15 flashings and try some methods but none of them worked.
So I found myself another method and grabbed some files that are required to recover IMEI.
Requirements:
Unlocked bootloader(Official or unofficial). You get unofficial methods to unlock bootloader on the internet.
Process:
Step 1:
Download the attachment given below.
Extract it somewhere.
Boot your device into fastboot mode and make sure it's unlocked.
Open extracted folder and run command prompt mode and run following fastboot commands:
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
After successful flashing of above files reboot your device and check your IMEI.
You can now see 0 infront of IMEI.
Step 2:
Enable debugging mode and connect your device to PC.
Check is your device connected or not via adb devices
Now run following commands:
Code:
adb shell
su
setprop sys.usb.config diag,adb
Now open WriteDualIMEI(W+G_eMMC).exe included in the attachment given below.
Your can see COM port in the open dialog box.
Enter your IMEI and press START
Now reboot your device & you will have your IMEI & baseband back as factory mobile.
Click to expand...
Click to collapse
After doing step 1, my device is soft bricked again.
The device is not going past mi logo
I tried flashing in fastboot mode and edl mode both, no result.
Samip12 said:
The device is not going past mi logo
I tried flashing in fastboot mode and edl mode both, no result.
Click to expand...
Click to collapse
If you are still on that then:
How did you unlocked your bootloader?
prashantvrm said:
If you are still on that then:
How did you unlocked your bootloader?
Click to expand...
Click to collapse
I had unlocked via mi unlock tool, then I wrote the step 1 commands in fastboot , then I tried to reboot my device , it stopped at mi logo..
After that, I have flashed ROM through fastboot mode, edl mode but my device is not going past mi logo
prashantvrm said:
I lost my baseband & IMEI due to wrong flashing and unlocking methods. I did 10-15 flashings and try some methods but none of them worked.
So I found myself another method and grabbed some files that are required to recover IMEI.
Requirements:
Unlocked bootloader(Official or unofficial). You get unofficial methods to unlock bootloader on the internet.
Process:
Step 1:
Download the attachment given below.
Extract it somewhere.
Boot your device into fastboot mode and make sure it's unlocked.
Open extracted folder and run command prompt mode and run following fastboot commands:
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
After successful flashing of above files reboot your device and check your IMEI.
You can now see 0 infront of IMEI.
Step 2:
Enable debugging mode and connect your device to PC.
Check is your device connected or not via adb devices
Now run following commands:
Code:
adb shell
su
setprop sys.usb.config diag,adb
Now open WriteDualIMEI(W+G_eMMC).exe included in the attachment given below.
Your can see COM port in the open dialog box.
Enter your IMEI and press START
Now reboot your device & you will have your IMEI & baseband back as factory mobile.
Click to expand...
Click to collapse
Where can I find the files for kate
Samip12 said:
I had unlocked via mi unlock tool, then I wrote the step 1 commands in fastboot , then I tried to reboot my device , it stopped at mi logo..
After that, I have flashed ROM through fastboot mode, edl mode but my device is not going past mi logo
Click to expand...
Click to collapse
Goto MIUI official forum and ask someone to give all possible ideas on how to fix your device. I was in same position as you and made 10-15 attempts to fix my device. And it was 4 years ago and I don't have that chinese mobile anymore.
Tip: After you got your device fixed just remove the MIUI ROM and use a clean ROM.
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