Related
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e94557, 2013-05-24 14:49:34)
eMC Info: Size 8GB
Device is LOCKED, Status Code 0
Battery OK
Transfer Mode:
USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
Click to expand...
Click to collapse
Anyone got any ideas what might have caused this, and what can be done to fix it?
Leraeniesh said:
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
Anyone got any ideas what might have caused this, and what can be done to fix it?
Click to expand...
Click to collapse
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
ATTACK said:
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
When flashing anything via fastboot (or mfastboot)
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32KB)...
OKAY [ 0.074s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.383s
Click to expand...
Click to collapse
Leraeniesh said:
When flashing anything via fastboot (or mfastboot)
Click to expand...
Click to collapse
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
ATTACK said:
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
Click to expand...
Click to collapse
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
EDIT: Was able to get it to flash using HouseofMoto's RSD XML.
All good
Leraeniesh said:
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
Click to expand...
Click to collapse
And you tried to restore 98.30.1? I know with the leak, it is a two part flashing process. It will reboot after part 1, then you need to reboot into recovery to start part 2. You may need to wait until there's a FXZ to fix it.
This is scary. Ive just RSD'd back to stock and am about to update my phone with all the OTA's. Perhaps ill stop for now.
EDIT: And the OTA process just failed from Stock update. FML.
Maybe try this? This is sourced from Moto's website
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620
If anyone else experiences something similar, you can follow jimyv's post regarding setting up RSD to flash (despite something going wonk with the partition table)
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
techfellow said:
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
Click to expand...
Click to collapse
How did "everything fail?" Just need more details.
xKroniK13x said:
How did "everything fail?" Just need more details.
Click to expand...
Click to collapse
I've been trying this for the past 2 days. I just tried it again so I can give you details, and it worked without any issues, so I'm good.
Thanks to all the previous posters, and the house of moto maker.
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.
TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:
UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.
strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?
strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.
whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?
strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?
strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
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 userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
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 userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"fastboot oem lock begin
fastboot oem lock begin
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 lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks
MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...
Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.
UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.
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