Related
***RESTORE TO STOCK 4.4.4 SAFELY***
This guide is only for those who have entered into the world of "Customization" after getting the 4.4.4 update via OTA, before unlocking their bootloaders, or for those whose devices were shipped with 4.4.4.
After watching so many members of XDA going ahead, skipping important steps while trying to Restore their Moto E to stock 4.4.4, and ultimately ending up failing to do so, or in the worst case a BRICK, it's time I put in a few words here...
If you follow the steps correctly, you WON'T BRICK your device, and will be able to enjoy the fully restored firmware.
1) gpt.bin (WARNING: DO NOT flash this file)
Fastboot command :
mfastboot.exe flash partition gpt.bin
This is the file which contains all the partition information of your phone. It gets updated with each OTA update, and you CANNOT DOWNGRADE the partition table. If you somehow end up flashing the file, either the remaining commands may succeed, or fail... And when, you accept OTAs,!!!BRICKED!!!
2) motoboot.img (WARNING: DO NOT flash this file)
Fastboot command :
mfastboot.exe flash motoboot motoboot.img
This is your bootloader. I have very little info on how it gets flashed through each update... The bootloader is the bios of your phone. If you mess up this file, GOD knows what will happen!!! You won't be able to boot up your device, not even to the bootloader mode (or fastboot mode as some other people call it).
IF ANY ONE OF THE ABOVE FILES ARE MESSED UP, YOU CAN SAY GOODBYE TO YOUR PHONE FOREVER!!
Now, the commands which you should execute are listed below:
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
Now, Check inside your firmware zip for the numbers (system.img_sparsechunk.0, system.img_sparsechunk.1 etc.). If they are 0,1,2 then follow the steps above then type in:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
Or , if you have like 1,2,3 then type:
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
Now type in:
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
You MUST execute the commands in the order given above, to safely restore to KitKat 4.4.4.
All the best!!! :good:
This is a working tutorial to get and install the 5.1 OTA.
unrooting
when I run the first command ("mfastboot flash partition gpt.bin") in minimal adb...it showing ""mfastboot" is not recognized as an internal or external command" ..please tell me what i missed?
dijusg said:
when I run the first command ("mfastboot flash partition gpt.bin") in minimal adb...it showing ""mfastboot" is not recognized as an internal or external command" ..please tell me what i missed?
Click to expand...
Click to collapse
Why the hell are you trying to do so....?
Does reading my full post waste a lot of time?
Please ELI5 to me:
My condition right now:
Bootloader: 5.1
Bootlock: UNLOCKED
OS: 5.1 Optimized
Root: ROOTED
Can I restore to 4.4.4 by skipping that 2 command?
If so please reword your introduction to:
This guide is only for those who
- Have entered into the world of "Customization" after getting the 4.4.4 update via OTA, before unlocking their bootloaders.
- Device shipped with 4.4.4
- Device that updated to 5.x stock
And your device is
- Unlocked / Locked / Doesn't matter
- Rooted / Not roooted / Doesn't matter
- TWRP-ed / Original recovery intact / doesn't matter
Click to expand...
Click to collapse
Because I'm confused with your introduction.
Rohitagni said:
Why the hell are you trying to do so....?
Does reading my full post waste a lot of time?
Click to expand...
Click to collapse
well not everyone knows how to execute the commands (i dont know it too)
so can you please write us how to execute it?
adjayanto said:
Please ELI5 to me:
My condition right now:
Bootloader: 5.1
Bootlock: UNLOCKED
OS: 5.1 Optimized
Root: ROOTED
Can I restore to 4.4.4 by skipping that 2 command?
If so please reword your introduction to:
Because I'm confused with your introduction.
Click to expand...
Click to collapse
Yes you can do so... Just follow the tutorial.... You can get back to stock safely....
1) Make sure you clear all partitions from your phone except ur sd card... Do this via TWRP
2) Now you have a clean system.... You are ready to enter the commands
MAKE SURE YOU EXECUTE ALL OF THEM IN SEQUENCE (Except the ones I have told to leave out namely gpt and motoboot).
You are done!
Mondop said:
well not everyone knows how to execute the commands (i dont know it too)
so can you please write us how to execute it?
Click to expand...
Click to collapse
Okay... I'm sorry for being harsh...
First of all download the following:
1) Minimal ADB and Fastboot from Here
2) mfastboot.exe from Here
3) Motorola Drivers from Here
4) Kitkat 4.4.4 OS from Here
Download and install 1) and 3) and then tell me.
Rohitagni said:
Okay... I'm sorry for being harsh...
First of all download the following:
1) Minimal ADB and Fastboot from Here
2) mfastboot.exe from Here
3) Motorola Drivers from Here
4) Kitkat 4.4.4 OS from Here
Download and install 1) and 3) and then tell me.
Click to expand...
Click to collapse
already done im trying to update to Lollipop i was following this:
http://forum.xda-developers.com/showthread.php?t=2759495
http://forum.xda-developers.com/moto-e/general/solution-stuck-bootlogo-flashing-5-1-t3168109
and eveything was working fine except that im stucked at boot animation :/
---------- Post added at 11:17 AM ---------- Previous post was at 11:08 AM ----------
well, trying to find on internet why im stucked, i left my device to continue on booting and magically, after 10mins, android jumped on so im happy Lollipop owner :3
Mondop said:
already done im trying to update to Lollipop i was following this:
http://forum.xda-developers.com/showthread.php?t=2759495
http://forum.xda-developers.com/moto-e/general/solution-stuck-bootlogo-flashing-5-1-t3168109
and eveything was working fine except that im stucked at boot animation :/
---------- Post added at 11:17 AM ---------- Previous post was at 11:08 AM ----------
well, trying to find on internet why im stucked, i left my device to continue on booting and magically, after 10mins, android jumped on so im happy Lollipop owner :3
Click to expand...
Click to collapse
Well I am happy to hear that...
Always remember one thing:
HAVE PATIENCE!
Rohitagni said:
Well I am happy to hear that...
Always remember one thing:
HAVE PATIENCE!
Click to expand...
Click to collapse
yop, thaks for your time but i have rly one problem... after installing Lollipop, i cant connect to any mobile operator. is that problem caused by fact, lollipop i installed is from Brozail or whatever? is there any fix for that?
nope your tutorial bricked my phone :/ it will not help when you will not flash gpt.bin
just restored back, updated and boom bricked... your guide does not help
not working
Hi, I did everything as per post.
After rebbot I am shown old boot menu for some time.
But then I am back into lolipop .... Please advise if I missed something.
I just followed your instructions. They seem to have worked well. Thanks!
One comment- I understand that the first two commands are not to be followed, but perhaps it would be wiser to not give the full command that will brick the phone? That way people who just see the number and the command won't just be bricking their phone when they don't read the full instructions. Just say "don't use any command that includes gpt" or something like that instead of giving them the command.
LeiraHoward said:
I just followed your instructions. They seem to have worked well. Thanks!
One comment- I understand that the first two commands are not to be followed, but perhaps it would be wiser to not give the full command that will brick the phone? That way people who just see the number and the command won't just be bricking their phone when they don't read the full instructions. Just say "don't use any command that includes gpt" or something like that instead of giving them the command.
Click to expand...
Click to collapse
I like your suggestions... But I made this post for those who wanted to downgrade.
I hope u understand that downgrading is a very risky process, and EVERYONE SHOULD READ EVERY SINGLE LINE prior to trying to mess with their phone. Some told me to write the full commands so that they can clearly understand, while some like you are telling me to be more precise
Well, it's too tough for me to step on two boats at the same time. But still, I will try to be more precise for my next tutorial
Mondop said:
nope your tutorial bricked my phone :/ it will not help when you will not flash gpt.bin
just restored back, updated and boom bricked... your guide does not help
Click to expand...
Click to collapse
I told not to flash the gpt, AS WELL AS THE MOTOBOOT... It has been proved by other devs here at XDA, that these two will brick ur phone, and not the other ones!!!
So, don't blame me. You must have done something that was not mentioned here, that was responsible for the brick.
Mondop said:
nope your tutorial bricked my phone :/ it will not help when you will not flash gpt.bin
just restored back, updated and boom bricked... your guide does not help
Click to expand...
Click to collapse
How did the phone get bricked if you booted it successfully to lollipop? I think I must be making a mistake as in the earlier post, u said u were a "happy lollipop owner"????
rahul1042 said:
Hi, I did everything as per post.
After rebbot I am shown old boot menu for some time.
But then I am back into lolipop .... Please advise if I missed something.
Click to expand...
Click to collapse
Can u give me the link of the firmware? I think something is wrong with the files....
Else you can directly flash the 5.1 fresh by following the instructions from here
Rohitagni said:
I told not to flash the gpt, AS WELL AS THE MOTOBOOT... It has been proved by other devs here at XDA, that these two will brick ur phone, and not the other ones!!!
So, don't blame me. You must have done something that was not mentioned here, that was responsible for the brick.
Click to expand...
Click to collapse
I DID NOT flashed gpt as well MOTOBOOT
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
Rohitagni said:
How did the phone get bricked if you booted it successfully to lollipop? I think I must be making a mistake as in the earlier post, u said u were a "happy lollipop owner"????
Click to expand...
Click to collapse
I flashed to Lollipop succesfully but since this is POST for restoring back to stock, i used it to go back to Kit Kat and thats where my mobile was bricked
Mondop said:
I DID NOT flashed gpt as well MOTOBOOT
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
I flashed to Lollipop succesfully but since this is POST for restoring back to stock, i used it to go back to Kit Kat and thats where my mobile was bricked
Click to expand...
Click to collapse
So... In that case tooo? Did u leave out the bootloader and the partition?
Warning: some people have said following these instructions on Nougat bricks your phone. I have done them to restore stock after upgrading to Nougat and have had no issues but you may want to conduct further research before attempting.
I had trouble finding the correct instructions for restoring the stock firmware when I needed it a few months ago so I decided to make a simple guide to help people that may be having the same issues I was.
Firstly, ensure your bootloader is unlocked and USB debugging is enabled in developer options. I'd assume this is already the case if you're needing to restore to stock.
Download the stock firmware for your update channel from https://mirrors.lolinet.com/firmware/moto/addison/official/
Extract the zip file into a directory of your choice
Right click and "Open command window here"
Execute, line by line:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 (repeat up to 10)
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Reboot device
Thank you! This is very helpful restoring the device. Is there also command to re-lock the bootloader to enable OTA? The info is so fragmented... Many thanks
Yes same question. Is it possible to relock the bootloader after that? If so how to do this?
slainer68 said:
Yes same question. Is it possible to relock the bootloader after that? If so how to do this?
Click to expand...
Click to collapse
I dont remember who tell this "once you unlock your device, you can never ever lock it again."
Sent from my XT1635-02 using XDA Labs
There's a lot of devices that you can relock...
fastboot oem lock
should relock the bootloader...
Relock usually does make no sense. Unlock does not prevent OTA update. Relocked is "locked again", but won't help you in any way.
Under which circumstances do you fear that someone gets access to your device and flashes something? This is what gets prevented by relock.
Relock works only if we have a signed firmware. Without that there is no way to relock the bootloader.
tag68 said:
Relock usually does make no sense. Unlock does not prevent OTA update. Relocked is "locked again", but won't help you in any way.
Under which circumstances do you fear that someone gets access to your device and flashes something? This is what gets prevented by relock.
Click to expand...
Click to collapse
Relock to use Android Pay
In NOUGAT your script flash MM brick phone
Remove
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Donwgrade Bootloader Brick Phone
You really should add a warning. This breaks your phone if you already upgraded to Android N (specifically, the bootloader).
This other thread helped me downgrade the right way
https://forum.xda-developers.com/mo...irmware-downgrade-t3558118/page2#post71404455
Specifically the version of the script in the comments by -=MoRpH=-
graphitenexus said:
I had trouble finding the correct instructions for restoring the stock firmware when I needed it a few months ago so I decided to make a simple guide to help people that may be having the same issues I was.
Should this be unzipped in the ADB folder?
Click to expand...
Click to collapse
marsisabar said:
You really should add a warning. This breaks your phone if you already upgraded to Android N (specifically, the bootloader).
This other thread helped me downgrade the right way
https://forum.xda-developers.com/mo...irmware-downgrade-t3558118/page2#post71404455
Specifically the version of the script in the comments by -=MoRpH=-
Click to expand...
Click to collapse
I've restored to it from N without issue
Jimi Mack said:
I had trouble finding the correct instructions for restoring the stock firmware when I needed it a few months ago so I decided to make a simple guide to help people that may be having the same issues I was.
Firstly, ensure your bootloader is unlocked and USB debugging is enabled in developer options. I'd assume this is already the case if you're needing to restore to stock.
Download the stock firmware for your update channel from https://mirrors.lolinet.com/firmware/moto/addison/official/
Extract the zip file into a directory of your choice
Right click and "Open command window here"
Execute, line by line:
Should this be unzipped in the ADB folder?
Click to expand...
Click to collapse
Not necessary if you have ADB added to your path
graphitenexus said:
Not necessary if you have ADB added to your path
Click to expand...
Click to collapse
Thank you, but sorry I do not understand., an old guy here and the whole thing with command lines confuse me.
---------- Post added at 11:28 AM ---------- Previous post was at 11:06 AM ----------
I have all the files in the ADB folder, I keep getting "Slot Counts not found" on the 2nd entry on the list. All want to do is flash my screw up back to stock.... LOL.
I do not even have an "oem fb_mode_set" in the folder, I have an "oem.img"
Jimi Mack said:
Thank you, but sorry I do not understand., an old guy here and the whole thing with command lines confuse me.
Click to expand...
Click to collapse
Don't worry about path then. Unzip to platform-tools in the ADB folder then shift+right click and select open command window here. Then run the commands in the OP
graphitenexus said:
Don't worry about path then. Unzip to platform-tools in the ADB folder then shift+right click and select open command window here. Then run the commands in the OP
Click to expand...
Click to collapse
I am running the commands one by one but the 2nd one get me stuck as I noted above. The no slot think has be confused, what should I see after entering each command?
---------- Post added at 12:10 PM ---------- Previous post was at 11:44 AM ----------
Got It
graphitenexus said:
I've restored to it from N without issue
Click to expand...
Click to collapse
In the future... when you receive a "new" OTA you may brick your phone... (ghost user experience)
CsR0501 said:
In the future... when you receive a "new" OTA you may brick your phone... (ghost user experience)
Click to expand...
Click to collapse
Original Moto X, had one and loved it and yes lots of bricks.
graphitenexus said:
Relock to use Android Pay
Click to expand...
Click to collapse
I've never had that problem? My bootloader was unlocked on my Moto X Pure and the only time Android pay didn't work was when I rooted. I reverted back to complete stock and it worked fine.
SixShots said:
I've never had that problem? My bootloader was unlocked on my Moto X Pure and the only time Android pay didn't work was when I rooted. I reverted back to complete stock and it worked fine.
Click to expand...
Click to collapse
Unlocked bootloader now breaks safetynet
Hi everybody.
I'm very upset with my Moto X Style (XT1572, retail EU, bought in Italy though I live in South America).
Some days ago I received Android 7.0 OTA. Everything was fine until I had some problems with file management, which I had some months ago. So, I did a factory reset. Nothing improved, though I tried many times, so today I tried to flash a factory image of 6.0.1 using this image:
XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5
I did it multiple times, with different guides, because everytime I turn on the phone (no problem with that) to set it up, I can't detect any Wi-Fi access. If I skip the initial set up and go to Configuration/Wi-Fi, if i turn it on it automatically turns off after one or two seconds, never listing any access.
Most guides I followed where amost identical, maybe changing one or two fastboot cmd lines. What I can tell you is that with "fastboot flash partition gpt.bin" I get a failure, which I've been told happens because I want to flash an older system number. I get the same failure when doing "fastboot flash modem NON-HLOS.bin".
I really need to make it work, guys. The help I'm asking for is for:
1) Which image should I go for? I repeat, my last official system was 7.0, after unlocking went for a 6.0.1.
2) Idiot-proof fastboot cmd line in order (maybe I'm doing it wrong).
3) If you can tell me how to relock after it, I'd be very grateful.
4) Anything else is appreciated.
Finally, one thing I forgot: the first time I flashed it I forgot the eleventh system chunk and got on a bootloop, but I could start again.
Thank you!
Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 @FernandoAmado
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
Relock is impossible so far.
dzidexx said:
Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 @FernandoAmado
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
Relock is impossible so far.
Click to expand...
Click to collapse
I really want to thank you for your help. With your comment and the guide you gave me, I was able to flash that image, update to the next and last 6.0.1 and I'm downloading OTA 7.0 right now.
I have two questions I hope you (or anybody else) could help me with:
1) When I finally get back to 7.0, will that partition file which gave me trouble coincide with the system number? So I can forget about that issue?
2) Are you sure there isn't a way to relock it and bring it to status 2? I know it's not a problem, leaving it unlocked, but I'd like to relock it anyway, and then flash a fresh logo that doesn't point out it was unlocked.
Again, I'm very grateful for your help. You have no idea the stress I've got with this issue. I'm never going to unlock a phone, ever again.
The funny thing is, I did all this mess because Android stopped reading a particular selection of my music's metadata. Some Beach Boys album (it even left some BB albums untouched) and I couldn't sort it out doing a hard reset nor formatting the SD card. Funny and painful experience.
1. You will see.
2. There isn't the newest 6.0.x and 7.0 roms for fastboot. BL cannot be locked after update to it.
Users on Lolipop or early 6.0 can relock.
You can flash modified logo.bin, is what to choose:
https://forum.xda-developers.com/moto-x-style/themes-apps
" Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin "
Yes Yes
I had the same problem with same Build and your turtorial helps me !
Now everithing is OKAY
Thanks @dzidexx !
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
kidbao said:
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
Click to expand...
Click to collapse
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
madbat99 said:
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
Click to expand...
Click to collapse
Hi thanks for responding! I have the E4 XT1765. It's Qualcomm. MetroPCS. I tried the PERRY_METROPCS_C and PERRY_METROPCS_C_7.1.1 from from here: firmware. center/firmware/Motorola/Moto%20E4/Stock/
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Flash aokp latest build
beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
Yeah same. I tried everything :\
nayan deka said:
Flash aokp latest build
Click to expand...
Click to collapse
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
kidbao said:
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
Click to expand...
Click to collapse
There's an unofficial one here in the forum
https://forum.xda-developers.com/mo...aokp-rom-oms-substratum-t3748033/post75529247
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
kidbao said:
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
Click to expand...
Click to collapse
I don't know. I was just pointing out that we had one, lol. Not sure it will help you.
I see you "solved" it, lol
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
Not for me. As we've said, re-installing stock ROM doesn't seem to solve the problem for some people, but it's cool it did for you. Other forums are peppered with people experiencing the same SIM issue, some even apparently happening at random.
beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin...
Scholeggo said:
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
Click to expand...
Click to collapse
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
Scholeggo said:
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin..
Click to expand...
Click to collapse
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
beachfl said:
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
Click to expand...
Click to collapse
So, basically, to get back to original ROM, flash the following:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Compared to the original:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
Yup, that list all looks exactly like what I did.
'sudo -s' .... no, you don't include that when running fastboot from Windows, it's a Linux thing. I'm not sure you have to, but I do always run adb/fastboot from a command prompt with admin priveleges when I'm using WIndows. which is kinda the same thing as 'sudo' on Linux.
Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Go to Android programs and scroll down to rsdlite 6.2.4
Edit: link corrected
madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Davey126 said:
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Click to expand...
Click to collapse
For sure. Comfort in fastboot is a must
madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Like some others, RSDLite couldn't see my E4 from Windows 10
Didn't want to post because I thought I would solve the issue with a simple MiFlash restore to stock, but oh well, here I go:
Due to my excitement about the Pie update (Beta), I got a fastboot flashable zip that was posted on a thread and attempted to flash it myself, manually.
Commands I executed (one by one, not through the bat script):
Code:
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot set_active a
I probably should never have flashed all this but I will explain what happened in case someone more savvy knows exactly what happened and lends a helping hand.
So all the commands passed fine, except for the fastboot flash system ones. I executed the first one and it flashed parts of 500mb or so on the partition, around 6 times. Same on the system_b.
I suppose that these flash onto the different slots (A/B), correct me if I'm wrong. Then rebooted and it would bootloop (don't blame anyone since I f'd up) and I was like "Okay then, guess I will restore with MiFlash.
Well I did. First weird thing to notice, it would only take around 213 seconds, while it would normally take around 300 seconds so I suspected I might have messed up. Note that I always restore to the April security patch to be able to enable Camera2API. Booted fine, then it was time for me to input my SIM's PIN. I do so, and a message shows up saying "SIM PIN operation failed" and after that it would close and re-open the PIN prompt, basically every time I tried to type the PIN. It basically wouldn't even let me input the PIN itself. Sometimes, if I'm fast enough I can successfully submit it but it's still messed up and doesn't work properly.
I know, I shouldn't have flashed the thing in the first place (since it's also supposed to be confidential), but I did and I regret doing so. For anyone interested, the bootloader is unlocked and I can enter fastboot mode normally. Didn't try flashing a different stock image since this is the one I always use and it works.
If anyone has got any idea about what happened here and if there's any solution, I would be really thankful.
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
michkost858 said:
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
Click to expand...
Click to collapse
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
apexashwin said:
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
Click to expand...
Click to collapse
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Why flash April update? You can enable camera2api on any ota update! :/
WhatzIt2Ya said:
Why flash April update? You can enable camera2api on any ota update! :/
Click to expand...
Click to collapse
I don't think it's what matters at the moment.
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
WhatzIt2Ya said:
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
Click to expand...
Click to collapse
Just to be clear. I wasn't trying to flash any extra firmware after failing to install the Pie Beta flashable. I tried rolling back to stock.
Also, I was in the latest November update, before flashing the Pie beta flashable, so that's not what's wrong.
About the reason I flash the April update, it's just so I don't get wipes when I lock/unlock the bootloader on the process of enabling Camera2API.
Right now, I just want to get back to stock, didn't try flashing the Pie beta a second time after I failed and I won't.
Also my IMEIs are correct, if that matters in any way. I believe something got corrupted in the partitions (might be bsing) but yeah. Now whatever version I'm on (7.1,8.0,8.1) the issue still persists.
So I'd like to make a full restore, from the ground up, I suppose.
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
nitroax said:
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
Click to expand...
Click to collapse
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
michkost858 said:
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
Click to expand...
Click to collapse
I had a similar problem. Solved restoring persist and EfS backup.
sipollo said:
I had a similar problem. Solved restoring persist and EfS backup.
Click to expand...
Click to collapse
Hmm, I don't have such a backup. Is there a way to restore one?
michkost858 said:
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Click to expand...
Click to collapse
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
michkost858 said:
Hmm, I don't have such a backup. Is there a way to restore one?
Click to expand...
Click to collapse
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
Yes this is a known bug. This should fix pin issue
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
.:Addicted:. said:
Yes this is a known bug. This should fix pin issue
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. Will be watching over the thread linked.