Any idea where I can download firmware files for the xt1625 with build #MPJ24.139-64 or newer? I flashed my phone with the firmware from xt1624 thinking it would work, but now it can't get past recovery. I'm able to flash oem.img for MPJ24.139-48, but when I attempt to flash gpt.bin, I get the following error:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.055s
If it helps, here's the output for getvar:
Code:
C:\Users\aaron_000\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223H2GWK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x93
(bootloader) uid: DE8F6B0100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354124072012644
(bootloader) meid:
(bootloader) date: 08-17-2016
(bootloader) sku: XT1625
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 19 10:15:49 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_amz/athene:6.0.1/M
(bootloader) ro.build.fingerprint[1]: PJ24.139-48/48:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.31.48.athene_amz.
(bootloader) ro.build.version.full[1]: amz.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70009.08.03.45R ATHENE_RETUSA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g06a4fb5 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld35) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sun Jun 5 11:16:49 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: amz
all: listed above
finished. total time: 0.256s
-48 and -49 are the only two available for the US model
xtermmin said:
-48 and -49 are the only two available for the US model
Click to expand...
Click to collapse
And where can I find this? I have looked in all of the places it is supposed to be but have had no luck locating it. Doesn't seem to be available at this time.
stkpxl said:
I just posted the link for -49....
Click to expand...
Click to collapse
I don't have -49. My phone has -48. I would like to find a copy of the original firmware so I can return to stock if necessary.
UPDATE: Disregard the above. I found it.
stkpxl said:
I don't think it's been released for our model yet. I've been checking everyday. If you need to restore the stock firmware, use this one: https://androidfilehost.com/?fid=24591023225178637
Click to expand...
Click to collapse
is it work on xt1625 retail mpj 24.139 64/65 athene
i stuck in recovety since awhile .. if it works .. how to flash .. need it kindly .. im anew moto g4 user
---------- Post added at 02:42 PM ---------- Previous post was at 02:19 PM ----------
pastorbob62 said:
I don't have -49. My phone has -48. I would like to find a copy of the original firmware so I can return to stock if necessary.
UPDATE: Disregard the above. I found it.
Click to expand...
Click to collapse
whats the difference between 48 and 49 and whats the factory stock for this model 1625 mjp 24-139 retail 64/65
herakikoly said:
is it work on xt1625 retail mpj 24.139 64/65 athene
i stuck in recovety since awhile .. if it works .. how to flash .. need it kindly .. im anew moto g4 user
---------- Post added at 02:42 PM ---------- Previous post was at 02:19 PM ----------
whats the difference between 48 and 49 and whats the factory stock for this model 1625 mjp 24-139 retail 64/65
Click to expand...
Click to collapse
The -49 version is for the XT1635 not the XT1625. I have no idea if it will work with the XT1625, but experience has taught me that you should never flash any version except the one intended for your specific model. These forums are filled with people who didn't follow that simple rule and they are now bricked.
Here is a link to the -64 version for the XT 1625:
http://www.filefactory.com/file/3sq...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Here is a link to the filefactory repository with all versions for all G4 phones:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
pastorbob62 said:
The -49 version is for the XT1635 not the XT1625. I have no idea if it will work with the XT1625, but experience has taught me that you should never flash any version except the one intended for your specific model. These forums are filled with people who didn't follow that simple rule and they are now bricked.
Here is a link to the -64 version for the XT 1625:
http://www.filefactory.com/file/3sq...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Here is a link to the filefactory repository with all versions for all G4 phones:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Click to expand...
Click to collapse
thanks alot
last thing .. how to flash it ?
the link named xt1644 not 1625 .. is it normal ?
thanks for your help .. i just anew user and dont know anything .. hope u patient and for the 3rd time thank u
herakikoly said:
thanks alot
last thing .. how to flash it ?
the link named xt1644 not 1625 .. is it normal ?
thanks for your help .. i just anew user and dont know anything .. hope u patient and for the 3rd time thank u
Click to expand...
Click to collapse
The link I posted is for the XT1625 and the XT1644 firmware.
Here is a link to flashing the firmware from Fastboot. Be sure you have the correct firmware before you flash. Read the instructions very carefully and be sure you understand BEFORE flashing. If you still have questions, ASK!
http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
pastorbob62 said:
The link I posted is for the XT1625 and the XT1644 firmware.
Here is a link to flashing the firmware from Fastboot. Be sure you have the correct firmware before you flash. Read the instructions very carefully and be sure you understand BEFORE flashing. If you still have questions, ASK!
http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
Click to expand...
Click to collapse
flashed it but after it's been flashed still stuck in recovery .. tried also another old version like 48 and 49 but they failed during flashing .. may be cause it cant downgraded but the version u gave me was able to flash 64 65 but after finishing no good news
any help
herakikoly said:
flashed it but after it's been flashed still stuck in recovery .. tried also another old version like 48 and 49 but they failed during flashing .. may be cause it cant downgraded but the version u gave me was able to flash 64 65 but after finishing no good news
any help
Click to expand...
Click to collapse
Stop trying to flash older versions of the ROM. It won't work for the reason you stated. When you flashed the -64 ROM did you get any errors at all? When you reboot, do you get the warning about your phone being unlocked? You should if everything flashed correctly. Also, you are certain you had the XT1625 with 139-64? Did you flash directly from fastboot entering the commands one at a time? Or did you use Flashstock.bat? I always do the commands individually so I can verify each one is successful. It takes more time and you need to be more careful but I prefer that method.
When you say you are stuck in recovery, do you mean the bootloader or stock recovery? I am assuming you mean the bootloader since you were able to flash the ROM using Fastboot. When you are in the bootloader, press the volume control until START is displayed next to the power button. Then press the power button. it should boot the phone. If it doesn't then I have no idea what to suggest.
Let me know what happens.
pastorbob62 said:
Stop trying to flash older versions of the ROM. It won't work for the reason you stated. When you flashed the -64 ROM did you get any errors at all? When you reboot, do you get the warning about your phone being unlocked? You should if everything flashed correctly. Also, you are certain you had the XT1625 with 139-64? Did you flash directly from fastboot entering the commands one at a time? Or did you use Flashstock.bat? I always do the commands individually so I can verify each one is successful. It takes more time and you need to be more careful but I prefer that method.
When you say you are stuck in recovery, do you mean the bootloader or stock recovery? I am assuming you mean the bootloader since you were able to flash the ROM using Fastboot. When you are in the bootloader, press the volume control until START is displayed next to the power button. Then press the power button. it should boot the phone. If it doesn't then I have no idea what to suggest.
Let me know what happens.
Click to expand...
Click to collapse
1st of all thanks for help
no errors happened due to flashing the room
all commands finished successfully
tried to flash one commend after one and also flashed once using rsd
the result of twice was the same
after finished successfully it make a reboot but its open on the stock recovery , and what i do after it opened i press on reboot sys boot loader to get the start icon to press put its start again on the recovery .. so i don't know what to do .. if u kindly know how to survive please heeeelp
herakikoly said:
1st of all thanks for help
no errors happened due to flashing the room
all commands finished successfully
tried to flash one commend after one and also flashed once using rsd
the result of twice was the same
after finished successfully it make a reboot but its open on the stock recovery , and what i do after it opened i press on reboot sys boot loader to get the start icon to press put its start again on the recovery .. so i don't know what to do .. if u kindly know how to survive please heeeelp
Click to expand...
Click to collapse
I'm sorry but I am out of suggestions. I didn't have any problem flashing this firmware. It must be something that happened when you first attempted to update. You might try to flash TWRP and see if you can flash a custom ROM. Other than that I am out of ideas.
I wish you luck my friend.
herakikoly said:
1st of all thanks for help
no errors happened due to flashing the room
all commands finished successfully
tried to flash one commend after one and also flashed once using rsd
the result of twice was the same
after finished successfully it make a reboot but its open on the stock recovery , and what i do after it opened i press on reboot sys boot loader to get the start icon to press put its start again on the recovery .. so i don't know what to do .. if u kindly know how to survive please heeeelp
Click to expand...
Click to collapse
From recovery try wiping data and cache then do reboot. May help
thanks all .. problem is solved
herakikoly said:
thanks all .. problem is solved
Click to expand...
Click to collapse
What did you do to fix it? Just wipe data and cache? There may be others who have the same problem and could use advice on how to get back to a working phone.
herakikoly said:
thanks all .. problem is solved
Click to expand...
Click to collapse
Once again, what did you do to get it up and running? Sharing information and fixes is one of the many features that makes these forums successful.
pastorbob62 said:
Once again, what did you do to get it up and running? Sharing information and fixes is one of the many features that makes these forums successful.
Click to expand...
Click to collapse
flashed amazon version .. and it works
herakikoly said:
flashed amazon version .. and it works
Click to expand...
Click to collapse
Hmmmm, interesting. I don't recall you ever saying you had the Amazon version. Knowing that would have saved me wasting a lot of time offering help with the retail version.
herakikoly said:
flashed amazon version .. and it works
Click to expand...
Click to collapse
Hi, can you help me? I have the same problem, where did you get the amazon version? :S
scotolive said:
Hi, can you help me? I have the same problem, where did you get the amazon version? :S
Click to expand...
Click to collapse
Here is a link to the filefactory repository with all versions for all G4 phones:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Be certain you download the correct version for your phone.
Related
I just got my xt1644 (G4 Plus, US version) yesterday and was trying to get root.
I got through successfully:
1) Unlocking bootloader.
2) Flashing TWRP.
3) Flashing the boot.img from the Root-motog4-athena-xt1641-xt1643.zip file (maybe a mistake, but read on).
4) Flashing SuperSU.
So then, I HAD root, but no WiFi. Seemingly others had this problem, so I added the ro.securestorage.support=false to the build.prop.
Nope. Still no WiFi. So I tried to change the build.prop BACK by deleting that line. Then, on the next boot, it stays in the "Your bootloader is unlocked" screen and does not boot to system.
I DO have bootloader access, and TWRP still works.
So, if anyone has:
1) A stock build.prop for the xt1644, or
2) New ideas, or
3) Access to the stock rom for the xt1644, which I cannot fiind,
PLEASE let me know.
Thanks!
J
http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
Posted this in a bunch of stock ROM topics.
For root, there is no need to flash a new boot.img. Just unlock bootloader, flash or boot TWRP, type in the command to tell SuperSU to flash in systemless mode, flash SuperSU, and reboot.
Guide: http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
xtermmin said:
http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
Posted this in a bunch of stock ROM topics.
For root, there is no need to flash a new boot.img. Just unlock bootloader, flash or boot TWRP, type in the command to tell SuperSU to flash in systemless mode, flash SuperSU, and reboot.
Guide: http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
THANK YOU!
I'm d/ling now and will follow your guide!
J
jogawa said:
THANK YOU!
I'm d/ling now and will follow your guide!
J
Click to expand...
Click to collapse
Yay! I got the phone back by flashing the stock ROM, then rooted using the guide, and I'm happy.
Thank you for pointing that stuff out xtermmin! I never thought to look for a ROM file with a name other than one that started with xt1644, and couldn't figure out how to search the directory.
You saved me.
Thanks again!
J
Filefactory link is acting very strangely. Its just loading the basic html, no css.
Could someone give me a mirror? Im as stuck as OP was without it.
EDIT: It took a few minutes but filefactory loaded enough of the css to get the download button. I may reupload somewhere and post a link when I get it downloaded.
http://www.filefactory.com/file/28u...PJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip
Enviado desde mi Moto G (4) mediante Tapatalk
So i did the same thing as you by flashing the xt143 file, and now my adb will no longer work. The phone will not give me an RSA key prompt. I've deleted the .pub file in data/user/android. Any tips would be appreciated.
jogawa said:
Yay! I got the phone back by flashing the stock ROM, then rooted using the guide, and I'm happy.
Thank you for pointing that stuff out xtermmin! I never thought to look for a ROM file with a name other than one that started with xt1644, and couldn't figure out how to search the directory.
You saved me.
Thanks again!
J
Click to expand...
Click to collapse
I'm getting a "could not find 'meta-inf/com/google/android/update-binary'" error when I try installing zip with TWRP and when I try sideloading. Any idea why?
acharlest said:
I'm getting a "could not find 'meta-inf/com/google/android/update-binary'" error when I try installing zip with TWRP and when I try sideloading. Any idea why?
Click to expand...
Click to collapse
Which zip? The stock ROM zip? You can't flash it via TWRP. You have to boot into bootloader mode, connect to a computer, and flash via fastboot or one of those "easy flasher" tools.
jogawa said:
I just got my xt1644 (G4 Plus, US version) yesterday and was trying to get root.
I got through successfully:
1) Unlocking bootloader.
2) Flashing TWRP.
3) Flashing the boot.img from the Root-motog4-athena-xt1641-xt1643.zip file (maybe a mistake, but read on).
4) Flashing SuperSU.
So then, I HAD root, but no WiFi. Seemingly others had this problem, so I added the ro.securestorage.support=false to the build.prop.
Nope. Still no WiFi. So I tried to change the build.prop BACK by deleting that line. Then, on the next boot, it stays in the "Your bootloader is unlocked" screen and does not boot to system.
I DO have bootloader access, and TWRP still works.
So, if anyone has:
1) A stock build.prop for the xt1644, or
2) New ideas, or
3) Access to the stock rom for the xt1644, which I cannot fiind,
PLEASE let me know.
Thanks!
J
Click to expand...
Click to collapse
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578
Luniz2k1 said:
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578
Click to expand...
Click to collapse
Read post #2.
Also, "ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip" is not for the US models. It's for the Indian model.
guys help me i have moto g4 plus 32 gb(india) and i flashed this firmware but now my fingerprint doesnt work and network also i have to erase the modem1 &2 then i flash modem NON-HLOS.bin after that my network works but no fingerprint ???
\XT1626-XT1640-XT1641_ATHENE_6.0.1_MPJ24.139-23.1_cid50_subsidy-DEFAULT_CFC\
w Folder>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2238ZFWQ
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 3559230000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Aug 7 21:45:14 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-23.1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.24.1.athene.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband[0]: M8952_70004.04.03.32R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld52) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Apr 28 13:04:48 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
Luniz2k1 said:
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578
Click to expand...
Click to collapse
Any way of knowing if the file that was just uploaded on Oct 20 is for XT1644?
Based on the name it seems to be the one that I am using now in my XT1644. But I got my file from the other place...
I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL
doctor_evil said:
I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL
Click to expand...
Click to collapse
Hope is not that one that the owner was over here trying every possible solution without success...
doctor_evil said:
I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL
Click to expand...
Click to collapse
Did you use PayPal? If the owner didn't warn you about the problem and listed it as a working phone then you can get a refund and return it. If you didn't use PayPal you may be stuck with it.
SoNic67 said:
Hope is not that one that the owner was over here trying every possible solution without success...
Click to expand...
Click to collapse
The seller appeared to specialize in used phones, possibly a pawn broker, or a cell phone reseller that does trade-ins. Those are usually the best kind of sellers, as they know enough to see there is a problem and will document it and price it accordingly, but they don't have the time or patience to fool with actually trying to fix the issue.
I will post back with my success or failure. I caused a original Gen Moto G to behave in the exact same fashion when I flashed the wrong firmware on it, and I was able to fix that one with a little trial and error. I learned a valuable lesson on being more careful, and that it was possible to just flash the radio from the firmware zip files instead of flashing everything.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
pastorbob62 said:
Did you use PayPal? If the owner didn't warn you about the problem and listed it as a working phone then you can get a refund and return it. If you didn't use PayPal you may be stuck with it.
Click to expand...
Click to collapse
The issue was documented in the ebay listing, with photos showing the blank IMEI info. I've had success in fixing this exact issue on a original gen Moto G after I accidentally flashed the wrong version of the firmware on it. I wound up using the UK radio for it to unbrick that one's cell radio.
Yeah, it needs to be the exact same radio.
Moto has a backup partition for bootloader and radio, and on flashing wrong ones it restores the "correct" one when booting with factory Android firmware. That's why after flashing TWRP, booting all the way into stock Android, it will be reverted to the normal bootloader. That's why we can flash LA.BR (Latin America / Brasil) firmware on our US phones - the baseband is "corrected" at the boot time.
But if you boot with a different that stock firmware, after flashing the wrong radio, than the "backup" capability is lost and subsequent firmwares need to have the exact original radio. And the "repair flash" of the baseband (radio) needs to be done with NON-stock firmware, because that one will "revert" the firmware to the old, wrong, one.
Don't forget, besides the software differences between models, there are also hardware ones.
I got it in the mail today. I flashed it with the ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml version of the firmware, and it fixed the issue. It did give me an error about flashing the recovery, which leads me to believe that it probably had a slightly newer version of the firmware installed. It did come minus the back cover. Does anyone know a good US seller with OEM replacement back covers for the XT1644? I ordered one from a chinese seller on ebay but it's going to take a long time to get here. I bought a nice looking Hybrid case to put on it, but not sure if it would be safe to use it without the back in the hybrid case. I worry about moisture getting into the phone. I do carry my phones in a holster on my belt instead of keeping them in a pocket though. So far I really like the Moto G4 Plus it's much nicer than my 2nd Gen Moto X, and much thinner and lighter.
Hi all,
i've to revert to stock my ultra, but i can't find any 2PZFIMG_OCEAN_NOTE_UHL_N70_SENSE80GP_HTC_EUROPE file around.
only us and asia . not working for my htc from uk,
Please, can someone post a link with european ruu??
Solved with Ruu same as mine version : 1.62
Is this what you are looking for?
https://drive.google.com/file/d/0B149q2R2Q43ZYUZ6MklZa0R0S2M
sabpprook said:
Is this what you are looking for?
Hi , first of all thank you for posting the ruu, i'm downloading it and i will try this evening... it seems that any ruu i try is not working so i'm becoming crazy by hours .... if you have any other ruu that i can try (uk ) please post the link .. i will let you know!
UPDATE : tryed one minute ago but everytime this error with many ruu :
C:\Users\Me\Downloads>htc_fastboot flash zip ruu.zip
sending 'zip'... (1859179 KB) OKAY
sending time = 92.671 secs
writing 'zip'... (bootloader) HOSD CL#925380
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAILED (remote: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i)
Execution time is 96(s)
someone can help me????
C:\Users\Me\Downloads>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA72H1701772
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 355166080180920
(bootloader) version-main: 1.62.401.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__001
Click to expand...
Click to collapse
tuygu said:
sabpprook said:
Is this what you are looking for?
Hi , first of all thank you for posting the ruu, i'm downloading it and i will try this evening... it seems that any ruu i try is not working so i'm becoming crazy by hours .... if you have any other ruu that i can try (uk ) please post the link .. i will let you know!
UPDATE : tryed one minute ago but everytime this error with many ruu :
C:\Users\Me\Downloads>htc_fastboot flash zip ruu.zip
sending 'zip'... (1859179 KB) OKAY
sending time = 92.671 secs
writing 'zip'... (bootloader) HOSD CL#925380
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAILED (remote: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i)
Execution time is 96(s)
someone can help me????
C:\Users\Me\Downloads>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA72H1701772
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 355166080180920
(bootloader) version-main: 1.62.401.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__001
Click to expand...
Click to collapse
RUU flashing condition is device's main version must equal or lower than RUU's.
But your device's main version is "1.62.401.1", RUU is "1.15.401.12", so it cause such of this error.
You can try to erase the main version text data through TWRP recovery after that it might be allowed you do RUU downgrading.
Text me on skype if you need some helps, my skype id "abpprook".
Click to expand...
Click to collapse
sabpprook said:
tuygu said:
RUU flashing condition is device's main version must equal or lower than RUU's.
But your device's main version is "1.62.401.1", RUU is "1.15.401.12", so it cause such of this error.
You can try to erase the main version text data through TWRP recovery after that it might be allowed you do RUU downgrading.
Text me on skype if you need some helps, my skype id "abpprook".
Click to expand...
Click to collapse
For my fault i relocked OEM . And now i cant enter in twrp or flash It. So the phone is locked and s-on . I can only go on bootloader Mode. Download mode and ruu mode. The system dont let me flash any recovery .
Please help
Click to expand...
Click to collapse
tuygu said:
sabpprook said:
For my fault i relocked OEM . And now i cant enter in twrp or flash It. So the phone is locked and s-on . I can only go on bootloader Mode. Download mode and ruu mode. The system dont let me flash any recovery .
Please help
Click to expand...
Click to collapse
Is it able to boot into android system?
If not the device is soft-brick now, must flash RUU to revive it but unfortunately there is no latest RUU for you.
Click to expand...
Click to collapse
sabpprook said:
tuygu said:
Is it able to boot into android system?
If not the device is soft-brick now, must flash RUU to revive it but unfortunately there is no latest RUU for you.
Click to expand...
Click to collapse
Ok. I Will wait ... Thank u very much for everything !
Click to expand...
Click to collapse
Is possibile to modify a ruu file to make believe the phone that i am installing
sabpprook said:
tuygu said:
Is it able to boot into android system?
If not the device is soft-brick now, must flash RUU to revive it but unfortunately there is no latest RUU for you.
Click to expand...
Click to collapse
Is possibile to modify a ruu file with 1.5 to make believe the phone that i am installing the 1.62.401.1 ??
Click to expand...
Click to collapse
tuygu said:
sabpprook said:
Is possibile to modify a ruu file with 1.5 to make believe the phone that i am installing the 1.62.401.1 ??
Click to expand...
Click to collapse
This won't be allowed if your device is S-ON, and i guess that the RUU file will be leak on easy-firmware in few days.
Click to expand...
Click to collapse
Download the File, rename it to 2PZFIMG.zip, copy it to your external SD card, boot phone into download mode, it will automatically pick it up and ask you to flash it. Be warned it will completely format your phone and internal storage
manasgirdhar said:
Download the File, rename it to 2PZFIMG.zip, copy it to your external SD card, boot phone into download mode, it will automatically pick it up and ask you to flash it. Be warned it will completely format your phone and internal storage
Click to expand...
Click to collapse
Dome...but same problem with fastboot . The phone start to flash from sd but end in error for not correct version of firmware
tuygu said:
Dome...but same problem with fastboot . The phone start to flash from sd but end in error for not correct version of firmware
Click to expand...
Click to collapse
then you need a different firmware.
manasgirdhar said:
then you need a different firmware.
Click to expand...
Click to collapse
Yes i m waiting for 1.6 ruu... Easy firmware is still on 1.5 ......
tuygu said:
Yes i m waiting for 1.6 ruu... Easy firmware is still on 1.5 ......
Click to expand...
Click to collapse
Shouldn't really matter, I have flashed lower versions without issues
manasgirdhar said:
Shouldn't really matter, I have flashed lower versions without issues
Click to expand...
Click to collapse
With s-on ?
tuygu said:
With s-on ?
Click to expand...
Click to collapse
yes, U ultra doesn't have S-off
manasgirdhar said:
yes, U ultra doesn't have S-off
Click to expand...
Click to collapse
Do u have a link with a version that did u flash please?
tuygu said:
Do u have a link with a version that did u flash please?
Click to expand...
Click to collapse
I think I have the RUU somewhere, Are u on Single Sim and UK Variant?
manasgirdhar said:
I think I have the RUU somewhere, Are u on Single Sim and UK Variant?
Click to expand...
Click to collapse
Yes .. uk single ! Thank u!
tuygu said:
Yes .. uk single ! Thank u!
Click to expand...
Click to collapse
Do you have a membership to easy-firmware?
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
Start up failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
Click to expand...
Click to collapse
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4D
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Toshiba REV=07 PRV=00 TYPE=57 PNM=032G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ZY223MG4VS
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 16C4F0001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 358195071196980
(bootloader) meid:
(bootloader) date: 11-08-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 31 20:42:21 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.4D-0-g3d9d261
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.466s
Click to expand...
Click to collapse
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
C:\Users\Flia Boquense\Desktop\motox>fastboot flash partition gpt.bin
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.097s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.816s
BOOTLOADER LOG: "version downgraded for primary_gpt"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash boot boot.img
target max-download-size: 512MB
sending 'boot' (40960 KB)...
OKAY [ 1.142s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.857s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash recovery recovery.img
target max-download-size: 512MB
sending 'recovery' (41040 KB)...
OKAY [ 1.143s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.858s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash system system.img
target max-download-size: 512MB
sending sparse 'system' (509631 KB)...
OKAY [ 15.608s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.565s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot
invalid PIV signed system image"
Click to expand...
Click to collapse
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Your bootloader is locked? It appears so...
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
Click to expand...
Click to collapse
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
acejavelin said:
Your bootloader is locked? It appears so...
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
Click to expand...
Click to collapse
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
pizza_pablo said:
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
Click to expand...
Click to collapse
Sorry, my bad, i have the Pure edition, XT1575. I will try to do that hoping to have some luck.
lcn23 said:
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
Click to expand...
Click to collapse
Any other way to unlock? Nope, impossible actually.
Basically, you need to contact Moto... because you are still locked and stock it can be repaired, either in or out of warranty. Once the bootloader has been unlocked Moto won't even look at it. And that "Software Repair Assistant" was Verizon specific I guess (weird, right), but you can try it https://www.verizonwireless.com/support/knowledge-base-209216/ since it seems to have support for Moto Z Force (it's in the sample picture) so who knows, might work.
Motorola doesn't release firmware images, except for what is on their webpage (which is old for all models listed) and even their requirements are for an unlocked bootloader. The only firmware images we have are ones that are leaked, and that source has reported that it is very difficult (almost impossible) to access these builds now... I would speculate it in part goes back to Moto's pattern of planned obsolescence, but at the same time these images affect such a small number of individuals that they probably don't care anyway.
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
I just realized this is in the old Moto X 2013 area... I will request a Mod to move it.
MY wife somehow made it power on today in the morning. I guess that's the only hope as I wait for the Motorola Support to give me an answer. Impossible to send it to them for repair as i'm from Argentina and i bought it in USA.
Sorry about the misplacement.
Is there any recovery image I could somehow install bypassing the locked status?? The Windroid application "installs" a TWRP and it somehow manages to switch the CID from 0xDEAD to 0x0009, whatever that means.
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
Will try! Thank you!
dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
No man, not working. I only got something different when trying to flash partition gpt.bin. The new error message is this one:
C:\Users\Flia Boquense\Desktop\motox\rom16>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.091s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.963s
Click to expand...
Click to collapse
Your phone still is dead?
Try to flash only boot & system. @lcn23
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
Are you using the newest minimal adb...?
https://devs-lab.com/download-minimal-adb-fastboot-tool.html
UPDATE: Somehow the fastboot changed, the buttons with the options turned into a menu with options inside a light blue bubble and an image of the android pet with his belly open appeared. Seeing this, I tried to flash the gpt bin dzidexx gave me and it worked, but after that I tried to flash the bootloader and it didn't work. I guess I will try again later, because now I'm leaving to work. I will try what you told me later dzidexx. Thanks.
UPDATE 2: After that happened and i rebooted the phone, now its status switched from "stuck at fastboot" to "doesn't power up". I guess I screwed up. How can I fix that? When I plug it to the computer, the PC makes the sound of something being connected to one of her USB ports, but other than that there's nothing I get, it doesn't even appear in Windows Explorer as a connected device. @dzidexx
Nothing you can do in home.
I think the motherboard is broken(before you asked here) - memory.
Sometimes it happens.
Only warranty repair or other GSM service(motherboard replacement). @lcn23
I guess it has something to do with the aboot, because that was the only thing that got installed when flashing bootloader.img.
With locked BL you cannot check/repair it. @lcn23
Then I guess I hard fkin bricked it, damn me.
@acejavelin any ideas of how can I take it out of QHSUSB state??
lcn23 said:
@acejavelin any ideas of how can I take it out of QHSUSB state??
Click to expand...
Click to collapse
Nope... Bootloader is gone if it's going QLoad mode, nothing can be done now but get Moto to fix it. We don't have the necessary files to flash in this state.
lcn23 said:
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Click to expand...
Click to collapse
Go here, https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863, and flash recovery. Then tell us if it works.
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
____Mdd said:
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
yes I had tried it but it is not working
yshiv666 said:
yes I had tried it but it is not working
Click to expand...
Click to collapse
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.
____Mdd said:
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.
Click to expand...
Click to collapse
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD
yshiv666 said:
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD
Click to expand...
Click to collapse
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying ?
____Mdd said:
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying?
Click to expand...
Click to collapse
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........
yshiv666 said:
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........
Click to expand...
Click to collapse
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till than you can try blank flash again, with replacing gpt and bootloader from ROM's zip.
____Mdd said:
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till then you can try blank flash again, with replacing gpt and bootloader from ROM's zip.
Click to expand...
Click to collapse
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Wait, December's !
You got your device back is good thing, but remain stuff will be of September's patch..
Now if you get update notification for December's patch dont take it... It will brick your device again.
You will have to wait for fastboot ROM of December's patch..
Till then, keep your phone on September...
Don't take OTA...
When December's patch build is available flash it with fastboot...
yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Good to hear you got your device working. As ____Mdd has mentioned, I would strongly recommend you wait for the Dec 2017 stock ROM to flash. Looking at your bootloader details, since you've got a Dec 2017 GPT, a June/September 2017 bootloader and a marshmallow baseband, you likely cannot safely take OTA updates.
Because you've downgraded from Nougat to marshmallow, taking OTA updates runs a high risk of hard bricking again and our current blank flash may not work on your device now you've flashed the Dec 2017 GPT. Thus, do not take OTA updates until you flash the Dec 2017 Nougat stock ROM (which isn't available yet), and if you later downgrade again, do not accept OTA updates. Else the OTA updates may corrupt your newer bootloader again (bootloaders do not downgrade) with no recourse except to wait for a newer blankflash or a 8000+ rupees repair.
I have the same case and it sends me an error in the boot.
Can somebody help me
Turning OEM on without phone turning on
al3al3al3jandr0 said:
I have the same case and it sends me an error in the boot.
Can somebody help me
Click to expand...
Click to collapse
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.
qjzxvkw said:
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.
Click to expand...
Click to collapse
why doesn't it boot??? What were you doing before this happened. Please give the details
Heeth21 said:
why doesn't it boot??? What were you doing before this happened? Please give the details
Click to expand...
Click to collapse
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.
qjzxvkw said:
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.
Click to expand...
Click to collapse
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.
yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
make sure your bootloader is unlocked. and let me know.
echo92 said:
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.
Click to expand...
Click to collapse
Thanks for the response: Here is everything you asked:
I am sure there was no update notification as I always download any update that is released as soon as I see it. So I might have updated already.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223BGGD2 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223BGGD2
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 6E23DD0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *************
(bootloader) meid:
(bootloader) date: 06-06-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:52: 3 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (208)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.244s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Thanks. It was indeed a hardware problem. Motherboard was broken in two pieces just below camera position.
Morning,
I have a Motorla G4 plus UK model XTN1642 I rooted this and installed TWRP when I first bought it several months back.
Yesterday, I got the 'update is avaialble' notification and follishly I allowed it to download and then install which failed, now the phone will only boot to the TWRP screen each time it restarts.
However, If I boot into bootloader then manually click 'Start' the phone will boot normally, but this is not ideal.
The phone is running stock Android 7.0 build number NPJS25.93-14-4, i've tried reading the forum but there is quite a lot that I don't understand and I don't want to make it worse by killing it completely and then not having a phone to use.
Can anyone give me a straight forward way to get the phone to boot up normally without having to go through bootloader and then manually click start?
I'm hoping that it is something simple, I don't have any backups of the device either!
Look, with twrp installed there's no way to update via ota. That's why I reflashed stock rom for getting the ota update. Although I planned to flash 6.0 M stock initially, I managed to flash 7.0 N stock ROM since it was available on this forum.
The version I have at the moment is 25.93.14.10 which is the September 2017 security patch. My another G4 absolutely untouched received ota today from 14.4 March patch to 14.13 December patch. I am not quite sure what happened to my 14.10 September patch. Why there is no ota? Maybe because this ROM was found on the G4+ forum?
Back to your question, find a stock ROM to flash, don't install twrp as it will modify the recovery. For install ota you will need to keep the ROM completely untouched.
Hi,
Yes, I am aware of that now but at the time I wasn't or else I wouldn't have done it.
But, after reading through teh forum, I followed this https://forum.xda-developers.com/moto-g4/help/ota-upgrade-7-0-twrp-installed-t3727807 after which the device booted normally again.
I should have left it at that, but again, I was notified of the update, so having read the thread above, let it go ahead, it download the update and rebooted., I then tried to root again and install twrp and elementalx and now it doesn't boot just get a black screen, I can still get into twrp and bootloader though.
Here is what I get from fastboot getvar all
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: E492B10000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ****************
(bootloader) meid:
(bootloader) date: 05-30-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:53:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.01R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.562s
I've blanked out the IMEI and Serial number in the above
I guess I should have left it ater getting it back and booting, but it sort of made sense to do the update then I needed to root it again.
What now?
right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !
ffrlr said:
right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !
Click to expand...
Click to collapse
How are you rooting, and what software are you using?
The general order for rooting is to:
1)Flash/boot TWRP. Either the official TWRP (3.2.1 - https://dl.twrp.me/athene/ ) or shreps' TWRP should suffice: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
2)In TWRP, backup your stock ROM and make a separate copy of your kernel (boot) partition.
3)Flash ElementalX or another custom kernel. Ensure this happens before you root else you'll bootloop. ElementalX v1.04 or v2.0 is here: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
3a)Wipe cache and Dalvik. At this point, you may wish to boot and check your device is working. If so, proceed to 4)
4)In TWRP (or boot back to TWRP), flash the root manager of your choice, either SuperSU v2.8.2 SR5 https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 or magisk 14/15. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Do not mix and match root managers without fully uninstalling and flashing the stock kernel again (hence the separate backup you made in 2)).
5)Wipe cache and Dalvik if not done in 3a) and reboot.
6)Any issues, revert to your backup made in 2).
This should give you a device booting with the latest stock ROM and rooted. This procedure is working on a XT1642 with NPJS25.93-14-13 (same firmware as you have now) and ElementalX v2.0 and magisk 15.3. As I linked in the other thread you've seen, you may wish to disable the Motorola updater to stop you from getting into another TWRP bootloop.
Hope that helps.
EDIT - have a look at this thread too: https://forum.xda-developers.com/moto-g4/how-to/guide-how-to-root-moto-g4-magisk-stock-t3725712/
Hi
thank you for the reply, very much appreciated, I'm keen to get my phone rooted again as I use 'timed toggles' to switch the phone into aeroplane mode when i'm asleep etc.
When I last rooted it after I bought it, I used magisk from what I recall, but I amnot really fussy to be honest.
Yesterday, I bravely attempted several times to install twrp in fact it was the shreps version which I found a link to, but for some reason I cannot get it to install.
I boot the phone using volume down button and power, then connect to the pc, then type fastboot flash recovery twrp-3.1.1-athene_shreps.img.
during the flash, I get the following
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
I then immediately boot to recovery using the volume keys and power button, after the device reboots, I don't get TWRP, justa dead android lying on it's back with a red exclamation mark above it, beneath is written no command.
I've had about four goes, but each time I get the same, am I missing something?, i've followed various threads and tutorialsd to no avail.
Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.
ffrlr said:
Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.
Click to expand...
Click to collapse
Good to hear it worked I'm glad that it worked on your other computer - Windows 10 appears to cause some headaches on flashing - I don't know if it's to do with the driver signature enforcement, that I don't think Windows 7 has. I've not had issues with Windows 10 flashing for the most part, though I do have a computer with a BIOS and not UEFI - though that being said, last time I flashed TWRP (shrep's TWRP), it didn't stick and required another re-flash, so maybe it's to do with the updated B1:07 bootloaders in both cases?
By the way, that 'image not signed or corrupt' message when flashing TWRP is normal and expected. TWRP is not cryptographically signed with the keys that the system/fastboot is expecting, so it's simply a message to alert you.
Have fun with your new root powers (please use responsibly )