Wifi wont turn on on moto x style - X Style (Pure) Q&A, Help & Troubleshooting

so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.

Having same issue. Restored stock and without root it works. After installing root the same problem occurred

search the site for the firmware. Download the firmware page and look for the file non-hlos.bin. Do the fastboot method but UNCAPS it. The file is in CAPS, rewrite the thing in lower case.

You may also have to flash the NON-HLOS.bin multiple times, it took me 3 flashes to get it to finally flash properly (There is no way to determine if it worked without booting android).

Go to your fastboot files folder
Open notepad
Paste this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
Save it like flashmodem.bat in adb folder
Take from original decompressed ROM
NON-HLOS.BIN & fsg.mbn and copy those files in adb folder with the bat file.
Run it
Enjoy
Remember to remove your sim card

nitros12 said:
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Click to expand...
Click to collapse
zakoda said:
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
Click to expand...
Click to collapse
Restore your stock backup and flash SuperSU 2.62 this should give you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.

[email protected] said:
Restore your stock backup and flash SuperSU 2.62 this should gif you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
Click to expand...
Click to collapse
Forgot to update my post, solved by flashing the stock ROM and then flashing whatever I wanted on top

Related

UPDATE Verizon Soak Test Does Break Root in regard to PWNMYMOTO

According to Droid Life, the Verizon Soak Test that just came out today doesn't break root.
heres the link
http://www.droid-life.com/2013/10/2...o-x-rolling-out-to-testers-doesnt-break-root/
WARNING DO NOT UPDATE IF YOU ARE USING PWNMYMOTO, some people are confirming bootloops. I believe this "keeping of root" is in relation to motoroot, but as always, do so at your own risk.
looks like the editor of droid life was rooted via motoroot and it kept that. I believe we have seen that with other OTAs. maybe not as exciting.
Glad to hear this. Of course, I un-rooted when I got the invite a week ago because I figured I either wouldn't get the OTA or it wouldn't install if I stayed rooted. I wonder if I can root again.
Tried to update with PwnMyMoto installed
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
tyguy829 said:
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
Click to expand...
Click to collapse
I would try to clear your cache, hopefully that works for you
Sent from my XT1060 using Tapatalk
Can't Clear Cache
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
tyguy829 said:
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
Click to expand...
Click to collapse
would
fastboot erase cache
command not work in the bootloader?
tyguy829 said:
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
Click to expand...
Click to collapse
I believe you can also clear cache through TiBu
Be careful according to JCase the soak does break root. Check his twitter.
I'm in the same boat as above. Phone stuck in a bootloop. If anyone figures it out I'll be in your debt. Also rsdlite doesn't detect my phone so I can't even restore it that way. I'm hoping there's at least a way to restore to factory through adb but Google is coming up empty.
- Nathan
tyguy829 said:
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
Click to expand...
Click to collapse
After your phone reboots hold down vol down + power to get into the bootloader. Now you can flash recovery through fastboot. Get the fastboot files from here if you don't already have it and the FXZ file for your carrier here. Now you can either just flash the recovery or flash the entire rom. If you just flash the recovery then the next time you boot it will reboot into recovery and run the update. If you choose to flash the entire rom then you will be wiping everything. To flash using fastboot you will first need to make sure the contents of the FXZ file are in the same folder as the fastboot files. Next open a command prompt and change the directory to the folder with your fastbboot files (eg. cd C:\). Now use the following commands to flash the FXZ files. If you choose to just flash the recovery then skip all the other commands except the command to flash recovery.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
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 oem fb_mode_clear
fastboot reboot
Thank you so much!! Worked like a charm as far as restoring my phone to defaults. The update is no longer showing in the software update section but that's ok. :good::good:
Dark9781 said:
After your phone reboots hold down vol down + power to get into the bootloader. Now you can flash recovery through fastboot. Get the fastboot files from here if you don't already have it and the FXZ file for your carrier here. Now you can either just flash the recovery or flash the entire rom. If you just flash the recovery then the next time you boot it will reboot into recovery and run the update. If you choose to flash the entire rom then you will be wiping everything. To flash using fastboot you will first need to make sure the contents of the FXZ file are in the same folder as the fastboot files. Next open a command prompt and change the directory to the folder with your fastbboot files (eg. cd C:\). Now use the following commands to flash the FXZ files. If you choose to just flash the recovery then skip all the other commands except the command to flash recovery.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
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 oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Anyone know how to cancel the reminder on the update? My phone downloaded the update, when I click install later it makes me set a time to be reminded. Don't really want to lose root for this update. Any ideas?
Sent from my GT-N8013 using Tapatalk 4
whitlecj said:
Anyone know how to cancel the reminder on the update? My phone downloaded the update, when I click install later it makes me set a time to be reminded. Don't really want to lose root for this update. Any ideas?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
delete the download through Tibu and then freeze the ota apk in Tibu
what i did to keep root with pwnmymoto was make sure my phone was 100% stock then root using pwnmymoto boot into recovery and back up root with ota rootkeeper. then i temp unroot and reboot to bootloader and flashed the original recovery back and installed the update which aborted near the end so i did it again and it did the same thing. after rebooting it was the new software update with no root so i flashed the boot.img into the recovery partition and booted back to recovery to restore root which you may have to grant a app su permisions for it to stick when you reboot. so far its running good. idk if the update applied properly but it booted up and runs great
FeaR_x_KhAoS said:
what i did to keep root with pwnmymoto was make sure my phone was 100% stock then root using pwnmymoto boot into recovery and back up root with ota rootkeeper. then i temp unroot and reboot to bootloader and flashed the original recovery back and installed the update which aborted near the end so i did it again and it did the same thing. after rebooting it was the new software update with no root so i flashed the boot.img into the recovery partition and booted back to recovery to restore root which you may have to grant a app su permisions for it to stick when you reboot. so far its running good. idk if the update applied properly but it booted up and runs great
Click to expand...
Click to collapse
anyone know if safestrap will be available after the ota (assuming we apply the update as you mentioned)?
has anyone tried rooting via motoroot 1.1 after doing the OTA from an unrooted device?
jayboyyyy said:
delete the download through Tibu and then freeze the ota apk in Tibu
Click to expand...
Click to collapse
Thanks for the response. Where do I find the download using tibu?
Sent from my GT-N8013 using Tapatalk 4
whitlecj said:
Thanks for the response. Where do I find the download using tibu?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
check out here. It is a big list but i think it has what things to freeze for the OTA. there is just one maybe two i think.
http://forum.xda-developers.com/showthread.php?t=2432729
just checked that he only disabled motorola OTA. i am on Vzw and don't have an OTA yet so im not sure thats all you need to freeze. I read some where to freeze updater.apk as well. maybe its either or. I don't have updater.apk frozen but if motoOTA doesn't fix it then do updater as well
jayboyyyy said:
check out here. It is a big list but i think it has what things to freeze for the OTA. there is just one maybe two i think.
http://forum.xda-developers.com/showthread.php?t=2432729
just checked that he only disabled motorola OTA. i am on Vzw and don't have an OTA yet so im not sure thats all you need to freeze. I read some where to freeze updater.apk as well. maybe its either or. I don't have updater.apk frozen but if motoOTA doesn't fix it then do updater as well
Click to expand...
Click to collapse
You have to.freeze the update.apk and if you've downloaded the update its in your cache.

Can not flash non-hlos.bin by RSD

My device is Droid turbo 2 . I flashed by RSD but it showed that Failed flashing process. 17/26 flash modem"NON-HLOS.bin" -> Phone returned FAIL.
HELP!
kaisam573 said:
My device is Droid turbo 2 . I flashed by RSD but it showed that Failed flashing process. 17/26 flash modem"NON-HLOS.bin" -> Phone returned FAIL.
HELP!
Click to expand...
Click to collapse
Have you tried flashing manually with fastboot? fastboot flash modem NON-HLOS.bin
Flash modem NON-HLOS.bin manually with fastboot, twice. I don't know why it doesn't work with RSD, but it doesn't.
rodrigoger said:
Flash modem NON-HLOS.bin manually with fastboot, twice. I don't know why it doesn't work with RSD, but it doesn't.
Click to expand...
Click to collapse
Did you have to take out NON-HLOS in order to flash back to stock in RSD? Im having that problem on my Moto X Pure returning to stock Marshmallow.
Use mfastboot
Kir6y said:
Did you have to take out NON-HLOS in order to flash back to stock in RSD? Im having that problem on my Moto X Pure returning to stock Marshmallow.
Click to expand...
Click to collapse
Do not use RSD. Use mfastboot commands (or Minimal ADB and Fastboot), and flash it manually, ok? Follow the order, but the Non-HLOS need to be flashed twice.
rodrigoger said:
Do not use RSD. Use mfastboot commands (or Minimal ADB and Fastboot), and flash it manually, ok? Follow the order, but the Non-HLOS need to be flashed twice.
Click to expand...
Click to collapse
Ok Thanks
rodrigoger said:
Do not use RSD. Use mfastboot commands (or Minimal ADB and Fastboot), and flash it manually, ok? Follow the order, but the Non-HLOS need to be flashed twice.
Click to expand...
Click to collapse
This solved my problem. Thanks dude!:good::good:

Tried restoring to Stock/Unrooted and now stuck in Bootloop - Please help

Ok I messed up pretty bad this time.
I used my Moto X Pure 2015 for a couple months. Unlocked bootloader, rooted it and used a couple diff ROMs. My father liked the phone, so wanted to give it to him after restoring it to stock, meaning unroot, lock bootloader, restore to factory ROM. But somewhere along the way I messed up and dont know how. I may have tried to flash 5.1.1 when my phone was already updated OTA to 6.0 but I am not sure.
Now I am stuck in a bootloop. The Moto Android logo comes up and it keeps looping there. I can enter bootloader but cannot enter recovery. It goes back to the loop when I attempt to go to recovery mode. I tried flashing (with the Flash-All.bat) packages lying out there, but my device isnt recognized. It says device not found. I cant even restart bootloader through the adb command. I type adb devices in cmd and it says ADB devices attached, but I dont see my device displayed. But Device Manager lists my phone as Motorola ADB Device.
I took a chance and sent it to Motorola......................... surprise surprise...../s , they refused to fix it coz of the unlocked bootloader(even with a fee).
So, now I cant flash anything, I cant go to recovery, nor can get the phone to boot up.
Have I lost the device completely? I dont have any nandroid backups either.
Any help is greatly appreciated.
Ok. I made some progress. I Uninstalled my device drivers, reinstalled from the Motorola website. I am able to flash things from fastboot.
I did the following for MM6.0
adb reboot-bootloader
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
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Everything was successful.
Now I can boot into the OS.
But now my WIFI isnt working. I go to settings and try to turn it on, but it doesnt.
Can someone help me here>?
nikhilnagaraj24 said:
Ok. I made some progress. I Uninstalled my device drivers, reinstalled from the Motorola website. I am able to flash things from fastboot.
I did the following for MM6.0
adb reboot-bootloader
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
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Everything was successful.
Now I can boot into the OS.
But now my WIFI isnt working. I go to settings and try to turn it on, but it doesnt.
Can someone help me here>?
Click to expand...
Click to collapse
are you sure you flashed everything correctly?
I don't know directions or anything, but I can tell you from other posts on the moto x pure forum that your not the first to lose wifi after restoring stock. To my knowledge you need to down grade to the original factory Android version, not just 5.1 or whatever, it HAS to be the original Android version, AND original baseband and system version, then upgrade from there. Hour that helps a bit, but do some searching and I'm sure you will find what I mean.
Thanks for your reply guys. I eventually fixed it. I now am running the TruPure ROM and everything seems to be working fine.
Except the the MicroSD card that I had 'adopted' is now write protected. I am not finding any luck trying to salvage that. I dont care about my data on it, just want it to be usable. I read somewhere that the card, once adopted, will only work on that ROM that it was originally adopted on. I even tried flashing the other ROM (OrionOS) but no go. My phone doesnt recognize the card except in Recovery. Computer recognizes it but I cant do anything since it is write protected. I tried DISKPART, the regedit fix and a bunch of other stuff. Didnt help. Its a brand new card, so I dont believe the card has gone faulty. Any idea on how to fix it?
nikhilnagaraj24 said:
Thanks for your reply guys. I eventually fixed it. I now am running the TruPure ROM and everything seems to be working fine.
Except the the MicroSD card that I had 'adopted' is now write protected. I am not finding any luck trying to salvage that. I dont care about my data on it, just want it to be usable. I read somewhere that the card, once adopted, will only work on that ROM that it was originally adopted on. I even tried flashing the other ROM (OrionOS) but no go. My phone doesnt recognize the card except in Recovery. Computer recognizes it but I cant do anything since it is write protected. I tried DISKPART, the regedit fix and a bunch of other stuff. Didnt help. Its a brand new card, so I dont believe the card has gone faulty. Any idea on how to fix it?
Click to expand...
Click to collapse
if you had an sd card to pc adapter so you can format it from the pc?_?

Moto X Pure XT1575 Stuck at bootloader unlocked screen and stuck at twrp logo

So i was recording a video, when it entered a state where I had to reboot the phone. I did so, and it got stuck. I did a hard reset. The phone then gets stuck at bootloader unlocked. I entered fastboot, selected recovery, and it gets stuck at the twrp logo. Any ideas? I also re-flashed twrp and it still get stuck.
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
acejavelin said:
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
Click to expand...
Click to collapse
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
thebaconbox said:
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
Click to expand...
Click to collapse
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
acejavelin said:
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
Click to expand...
Click to collapse
How do I do that?
thebaconbox said:
How do I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
thebaconbox said:
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
Click to expand...
Click to collapse
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
acejavelin said:
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
Click to expand...
Click to collapse
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
thebaconbox said:
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
Click to expand...
Click to collapse
Yes
acejavelin said:
Yes
Click to expand...
Click to collapse
Alright, I flashed everything and my cell service now works flawlessly.
thebaconbox said:
Alright, I flashed everything and my cell service now works flawlessly.
Click to expand...
Click to collapse
Awesome!
hy,
my purenexus rom was running perfectly but today i was installing spotify and it hanged and then i had to retsart but now it stucks on bootloader warning screen .recvory also stucks on twrp logo . now what should i do .i googled and found this thread.please guide me which thread do i need to follow ..will my bootloader get locked again ? where do i have to start it from? i also have nandroid backup of previous custom rom which is truepure rom. please guide me.
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
dzidexx said:
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
Click to expand...
Click to collapse
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
azzammalik said:
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
Click to expand...
Click to collapse
Only with twrp you can save your data.
What version did you used? Try with another, maybe don't flash - only boot.
"fastboot boot NameOfTwrp.img"
If it boot copy your data to pc.
Stock you can flash with fastboot, here is "how to", download and flash the highest version for you model:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Read carefully, don't lock bootloader.

FYI: recovered G5 XT 1676 to stock and updated. :)

Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan

Categories

Resources