My beef now with a FIDO xt 925:
I was on kk 4.4.2, then once the fido kk update came out yesterday, I reverted back to rtfr, orphee script and root to check the gps on it. So after i test drove it i wanted to go back to kk using ceeeuropean, and orphee combo.
I believe my mistake was rooting right after flashing the modified OTA.
After i rebooted , all i get is preflash validation failed for gpt.
The phone wont take any flash now of anything, always throwing partition name error and remote failure.
I have good battery and surprinsingly the phone is charging evenin fastboot. I can see the phone on wIN8.1 my device manager, but nothing will make it move . Tried house of moto, checked with Samu, tried flashing rogers 4.1.2, then rtfr in case that is the base . But no go. Also, it is showing BL locked code 0 AND OF COURSE my BL was unlocked. Weiiiird mess.
Any input is appreciated.
If I understand it correctly, while your phone booted fine the last time, it had the new FIDO 4.4.2 gpt and tz (flashed via OTA update when going from FIDO 4.1.2 to FIDO 4.4.2, but your gpt and tz actually going from CEE 4.4.2 to FIDO 4.4.2).
So the issue seems to be caused by the fact that your FIDO 4.4.2 gpt and tz has been "downgraded" to CEE (RTFR) 4.4.2 gpt and tz by OTA script.
So your problem could be possibly fixed by flashing gpt and tz extracted from FIDO 4.4.2 OTA, via fastboot.
yes being on fido 4.4.2, the second step was going from it to CEE rtfr 4..1.2, and i flashed Orphee modified zip as i have it on my SD. Then the prob occured. Anything i try to flash it doesnt take. do i extract the gpt and tz and falsh with fastboot? I have the OTA posted by our fellow here.
i will try once i locate the cmd.
I see tz.mbn and gpt.bin
would that be it?
am on stand by.
kabaldan said:
If I understand it correctly, while your phone booted fine the last time, it had the new FIDO 4.4.2 gpt and tz (flashed via OTA update when going from FIDO 4.1.2 to FIDO 4.4.2, but your gpt and tz actually going from CEE 4.4.2 to FIDO 4.4.2).
So the issue seems to be caused by the fact that your FIDO 4.4.2 gpt and tz has been "downgraded" to CEE (RTFR) 4.4.2 gpt and tz by OTA script.
So your problem could be possibly fixed by flashing gpt and tz extracted from FIDO 4.4.2 OTA, via fastboot.
Click to expand...
Click to collapse
Yes, gpt.bin and tz.mbn is it.
Code:
fastboot flash partition gpt.bin
fastboot flash tz tz.mbn
will report
looks as if i am booting ...isht i wasnt wrong when I thought you are capable .I am very grateful and will pay it forward.
Android is upgrading.....
I still dont grasp how the prob occured.
as i have a glitchy volume up, i can not easily boot to recovery when i flash it. Any cmd that works?
many times i tried fastboot reboot recovery
but it never works for me.
Also if you dont mind please, why is it when i flash a cmw recovery after say jelly bean , i am able to boot into it. But if i upgrade to KK, my device refuse to boot into recovery? some new security in protecting the recovery file?
kabaldan said:
Yes, gpt.bin and tz.mbn is it.
Code:
fastboot flash partition gpt.bin
fastboot flash tz tz.mbn
Click to expand...
Click to collapse
hbenz2008 said:
as i have a glitchy volume up, i can not easily boot to recovery when i flash it. Any cmd that works?
many times i tried fastboot reboot recovery
but it never works for me.
Also if you dont mind please, why is it when i flash a cmw recovery after say jelly bean , i am able to boot into it. But if i upgrade to KK, my device refuse to boot into recovery? some new security in protecting the recovery file?
Click to expand...
Click to collapse
i read this thread after i replied to the other one, glad you got it fixed.
im surprised fastboot worked. through helping to fix this error many times, i know it usually required Mfastboot to fix, thats why i made the special tool just to fix gpt errors.
i never had much luck booting into recovery with fastboot, so i just go with adb to do it "adb reboot recovery".
Hi guys!
I think I have maybe the same problem as you.
I can't flash the partition_signed of an official ROM(says invalid GPT) so I wonder how did you extract the gpt for flashing it?
if you did just like me then you can extract the one from 4.4.2 OTA canadian. let me know how you do. It is best to state how you got to where you are..
Okay!
But wait... where I can find it ^^?
edit:
i found a gpt.bin from an update of my region (Blur_Version.180.46.127.XT925.CEE-Retail.en.EU)
I will try tonight
Sounds good man, grab "tz" as well
hbenz2008 said:
Sounds good man, grab "tz" as well
Click to expand...
Click to collapse
I don't have it in the update :/
see attached
hbenz2008 said:
see attached
Click to expand...
Click to collapse
Thanks!!!
---------- Post added at 08:09 PM ---------- Previous post was at 07:57 PM ----------
Didn't Work :'(
Whats the error?
hbenz2008 said:
Whats the error?
Click to expand...
Click to collapse
I flashed the both files, but I have bootloop in the screen
Is there a trick to debug the start of the phone (for watching where it bugs)
You tried the ones from rtfr, right?
hbenz2008 said:
You tried the ones from rtfr, right?
Click to expand...
Click to collapse
yep ^^
Related
Has anyone tried to downgrade 4.4.2 to 4.3, there are problems?
LeonelRdz09 said:
Has anyone tried to downgrade 4.4.2 to 4.3, there are problems?
Click to expand...
Click to collapse
I've downgraded twice, no problems here. As long as you do it right, you should be perfectly fine :good::good::silly:
How???
SamsungAdmire said:
I've downgraded twice, no problems here. As long as you do it right, you should be perfectly fine :good::good::silly:
Click to expand...
Click to collapse
Hello, could you please tell me how you downgrade? I'm not a fan or not having WiFi!
awooga1123 said:
Hello, could you please tell me how you downgrade? I'm not a fan or not having WiFi!
Click to expand...
Click to collapse
I follow this guide to flash 4.2.2 and my WIFI works perfectly!
http://forum.xda-developers.com/showthread.php?t=2585242
when i downgraded from the repacked 4.4.2 my wifi stoped working.. there is no way to get it work again except to install the repacked 4.4.2 again
Sent from my XT1032 using XDA Premium 4 mobile app
makcode said:
when i downgraded from the repacked 4.4.2 my wifi stoped working.. there is no way to get it work again except to install the repacked 4.4.2 again
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could it be that the 4.4.2 radio is not compatible with a rom that is 4.3 or lower?
audit13 said:
Could it be that the 4.4.2 radio is not compatible with a rom that is 4.3 or lower?
Click to expand...
Click to collapse
I doubt it. I've just downgraded from 4.4.2 last night again and everything works perfect. Weird..
SamsungAdmire said:
I doubt it. I've just downgraded from 4.4.2 last night again and everything works perfect. Weird..
Click to expand...
Click to collapse
I suggested that because 4.4.2 needs the latest radio to work properly.
audit13 said:
Could it be that the 4.4.2 radio is not compatible with a rom that is 4.3 or lower?
Click to expand...
Click to collapse
i downgraded also the modem firmware. (./flashall.sh; and manual flash with ./mfastboot....)
i tried the DE UK US retail 4.3 official stock images. but no luck.
i think the repacked firmware had something changed in the partition with some wlan settings.. maybe some drivers i don't know..??
Sent from my XT1032 using XDA Premium 4 mobile app
Ok i solved my problem. Maybe it can help my solution to someone who have the same problem: I don't know why but my /persist/ folder was empty.. i had to diskdump the block of persist from my other moto g and copyed it on my briked one. then i had to edit the two bin files for bluetooth and wifi to set back the real MAC Adress (write down from the retail box)
now it works again without any problems.
Sent from my XT1032 using XDA Premium 4 mobile app
All im getting is "version downgraded for primary-gpt"
SamsungAdmire said:
I've downgraded twice, no problems here. As long as you do it right, you should be perfectly fine :good::good::silly:
Click to expand...
Click to collapse
Could you tell me HOW did you downgrade? Id like to go back to my Retail UK 4.3 ... now Im on XT1032 using US 4.4.2 ... I can flash US 4.3, thats no problem ... but when I try to flash back my original Retail UK 4.3 it says this:
Code:
d:\SORT\MotoG\STOCK_Retail_UK_4.3>flashall.bat
Motorola Mobility flashall script version 1.4
Flashing Options:
- flash persist: 0
- flash userdata: 0
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Fastboot device is ready!!
Flashing GPT and bootloader images...
Executing ".\Windows\fastboot.exe flash partition gpt.bi
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.089s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
.\Windows\fastboot.exe flash partition gpt.bin failed!!
ryanraven said:
All im getting is "version downgraded for primary-gpt"
Click to expand...
Click to collapse
michalurban said:
Could you tell me HOW did you downgrade? Id like to go back to my Retail UK 4.3 ... now Im on XT1032 using US 4.4.2 ... I can flash US 4.3, thats no problem ... but when I try to flash back my original Retail UK 4.3 it says this:
Code:
d:\SORT\MotoG\STOCK_Retail_UK_4.3>flashall.bat
Motorola Mobility flashall script version 1.4
Flashing Options:
- flash persist: 0
- flash userdata: 0
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Fastboot device is ready!!
Flashing GPT and bootloader images...
Executing ".\Windows\fastboot.exe flash partition gpt.bi
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.089s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
.\Windows\fastboot.exe flash partition gpt.bin failed!!
Click to expand...
Click to collapse
i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2542219
the primary gpt downgrade thing is normal. the first time i saw it i freaked out but still went on with it risking it.
After i did the instructions correctly, it booted up into 4.3 normally
By "went on" you mean you entered the commands manually? Because this script I wrote about before sure wont let me continue ...
michalurban said:
By "went on" you mean you entered the commands manually? Because this script I wrote about before sure wont let me continue ...
Click to expand...
Click to collapse
yup, it probably takes some 2 minutes just to put them in. Works perfect for me. :laugh:
SamsungAdmire said:
yup, it probably takes some 2 minutes just to put them in. Works perfect for me. :laugh:
Click to expand...
Click to collapse
Ok, phone seems to be running fine even with those errors (preflash validation failed + some failed signature check). Lets hope its not doing any trouble in the future ... Thanks for your assistance!
BTW what about you and kitkat (lol)? I find it sluggish and charging is slower - so I rooted and disabled the OTA upgrade ...
michalurban said:
Ok, phone seems to be running fine even with those errors (preflash validation failed + some failed signature check). Lets hope its not doing any trouble in the future ... Thanks for your assistance!
BTW what about you and kitkat (lol)? I find it sluggish and charging is slower - so I rooted and disabled the OTA upgrade ...
Click to expand...
Click to collapse
I sort of missed the blueness of 4.3 and browsers on 4.4 were annoying me since Google switched the default browser engine to chromium's engine. Then i saw some screenshots i accidently took from kitkat and missed the nice transparent bars and white icons, and now i'm sticking with kitkat.
hi guys i need help if possible my moto g is stuck on the blue m logo after the boot animation its not a boot loop just stuck on the m. i reflashed the firmware again but no change i havent erased cache and userdata is that the reason?
thanks guys in advance
erased cache and userdata after the downgrade abd it boots normal.
your downgrading lol you MUST delete the userdata and cache or you'll be forever bootloop
SamsungAdmire said:
i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2542219
the primary gpt downgrade thing is normal. the first time i saw it i freaked out but still went on with it risking it.
After i did the instructions correctly, it booted up into 4.3 normally
Click to expand...
Click to collapse
can you post the edited script for the downgrade?
I bought a Motorola XT925 on ebay branded Orange France and loaded with Jelly Bean 4.1.1 firmware.
The phone was sold to me as a 4G/LTE capable device. Not seeing an option for 4G/LTE in the phones menu, I then dug around the Orange France web portal. There it says the phone is not 4G/LTE compatible. This was confirmed by Motorola France.
So my big question: is the radio hardware in this Orange France phone the same as an XT925 that I would by from Rogers Canada, but just not initialized for 4G/LTE? Or is the actual Radio hardware different? Even Motorola France was not able to tell me over the phone about the exact hardware.
Do I have a hope to get 4G/LTE working on this phone?
I want to try a Rogers firmware on this phone, but don't want a 200,00$ paperweight.
Thanks for reading.
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
hbenz2008 said:
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
Click to expand...
Click to collapse
I have a custom recovery utility installed after rooting and unlocking the bootloader and just completed a backup on the phone. I figure since the phone is wearing jelly bean 4.1.1 I ought to be able to take the Rogers firmware jellybean 4.1.2 and flash that onto the phone. Just not sure how to make sure that the modem gets flashed when I do fastboot flash system system.img. So I am looking around to piece together the instructions on how to flash the modem or does the system image contain all I need for the modem and all else?
I kinda like the lock screen on the Orange.fr firmware -- has a sliding mute feature that might not stick around after a system flash. minor detail though as all I really want is a working LTE device.
Thanks
Rsd lite 6.1 to flash
hbenz2008 said:
Rsd lite 6.1 to flash
Click to expand...
Click to collapse
RSD Lite is a windows utility and at the present time I do not have a windows computer. I have unlocked the bootloader and flashed the recovery successfully with mfastboot for linux. So that;s where I am at. ( I find it ironic that a phone OS based oin linux should be largely dependent on a non-linux OS. Strange but true.
@hbenz2008 tell me about flashing the modem so that I can have LTE/4G access. What do I need to do?
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
hbenz2008 said:
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
Click to expand...
Click to collapse
I have downloaded the 4.1.2 Rogers firmware but to be honest I don't know exactly what or how to do with the zip file. I've opened the archive -- I even flashed the modem and all the rest of the blobs onto the phone, one by one based on a batch file from another archive. What happened was I lost my patience waiting for the phone to reboot as it appeared to be stuck on the Motorola boot logo. (Maybe it was rebuilding the cache??) I used the recovery to get the phone back. So if you can give me a clue as to what to do exactly with the firmware zip -- much appreciate your council.
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
hbenz2008 said:
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
Click to expand...
Click to collapse
I dug up an old netbook with xp on it and managed to use RDSlite it to flash the Rogers firmware and voila! Full service phone. except for one tiny snag. Earlier I had installed a custom recovery utility cwm6.2.2.8-XT925(epinter) and it worked. Now though the cwm recovery util got wiped and my subsequent attempts to re-install fail. I speak: "linux-fastboot flash recovery cwm.img. response: Max 30M sending recovery.
Weird it never progresses or finishes. Beginning to think I have the syntax wrong.
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
hbenz2008 said:
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
Click to expand...
Click to collapse
Thats what I have as a linux version (mfastboot). Got it from a link posted by @ATTACK and it worked properly before I flashed 4.1.2 today. I'll work on it at least now I have a phone that works and shows the options I was sold. Just wondering if RSDLite does something crippling when it writes the flash to the phone.
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
hbenz2008 said:
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
Click to expand...
Click to collapse
So something does seem to have changed. I no longer have permission to erase with the mfastboot utility. And I am refering to permission on the device not in my local shell. I sudo to the shell locally then run fastboot which returns the following:
gryphon platform-tools # fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.034s
gryphon platform-tools
the device status code is 3 and unlocked so I am baffled.
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
hbenz2008 said:
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
Click to expand...
Click to collapse
If you think of another possible solution let me know. As of now no fastboot utility works on my phone now.
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
hbenz2008 said:
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
Click to expand...
Click to collapse
I have the android-sdk installed and the fastboot included is known to cause problems with image files that are large. Thats where mfastboot comes in handy.
Now everytime I powercycle the phone fastboot appears on the screen and shows a failed flash notice. I'd like to clear up this issue pronto. what a pain . An adventurous pain
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
while you at it man, can you please grab "gps.conf " from system/etc and post here .It is about 2kb size. Merci
hbenz2008 said:
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
Click to expand...
Click to collapse
Good news! I got the fastboot flash failure flag cleared away and cwm recovery reinstalled. Still can't flash anything with fastboot of any stripe and I am betting this is because the image files in the sbf archive are signed. My phone is now vritualy identical to any Fido branded phone, complete with a Fido boot logo. Cute.
There ought to be a way to overwrite signed images, besides waiting for a new firmware release. The bootloader is unlocked and phone rooted yet fastboot flashing is not currently possible.
How can I unlock the signed images on my phone?
BTW heres my gps.conf. Whats your interest in this file?
Code:
#Test
#NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?
kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
So while sideloading it should I unroot as well?
jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app
pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app
No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...
If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.
I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.
jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?
I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me
pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?
I'm not sure what exactly caused it but about a week ago I lost cell service on my xt1032. When I dial *#*#4636#*#* it says the radio is off and the turn radio on button doesn't do anything. Wifi and GPS are working fine. Around that time I had updated the bootloader to 41.18 so that I could flash cm12.1 nightlies, erased modemst1 and modemst2 in fastboot, and flashed cm12.1. I had com.android.phone crashes like a few others did which they resolved by flashing backups.
I have tried to fix it by clean flashing cm12.1, flashing the latest XT1032_GPE_3112.97.00R radio, and clean flashing an old cm12 nightly but the radio remains off.
Any ideas?
I'm having the same issue. Dit you find a solution?
Have either of you tried flashing stock firmware?
Sent from my XT1031
ATTACK said:
Have either of you tried flashing stock firmware?
Sent from my XT1031
Click to expand...
Click to collapse
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?
BiggyB99 said:
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?
Click to expand...
Click to collapse
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031
ATTACK said:
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031
Click to expand...
Click to collapse
Thank you for your reply's. I'm now flashing stock rom from here (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510). Let you know in a sec
edit: still nothing Flashed the stock rom, wiped dalvik cache after. Rebooted a couple of times, but nothing seems to work.
Any other ideas?
edit2: Tried the optimized 'stock' rom, no success either. Also, I ruled out a SIM failure before, just did it agian because this is making me crazy!
Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031
ATTACK said:
Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031
Click to expand...
Click to collapse
Searching for the smiley that hits a hammer into his head. Sorry for my noobness! Flashing the firmware now.
edit: hanging on (bootloader) Preflash validation failed . Search xda learns me that that means the bootloader is locked, but the message says it is unlocked. I'll just go ahead and search some more
edit2: trying the bootloader unlocking procedure learns me that the bootloader is already unlocked: (bootloader) Device already unlocked!
What can I do next. (btw, the error comes on step 2 of the guide, where I put in: mfastboot flash motoboot motoboot.img. Everything else comes woth an OKAY. (http://forum.xda-developers.com/showthread.php?t=2542219)
You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031
ATTACK said:
You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031
Click to expand...
Click to collapse
I do not have a flash-all.bat (or something in that way) in my folder. Downloaded the firmware from the site you gave, the mfastboot from the Guide (http://forum.xda-developers.com/showthread.php?t=2542219) and I runned the commando's named there (for a xml.zip file).
edit: could it be that my bootloader is newer than the stock firmware is expecting? Running 41.18 now...
edit2: WORKED! I just kept trying to flash the stock firmware, error kept the same. Tried another recovery, did the flashing again but skipped the recovery step (error with bootloader still came up). After that I booted, and it worked! Sticking with stock 4.4.4 for now
Thanks for the help!
edit3: Working on 5.0.1 (stock) Did the OTA, failed because of my custom recovery. Flashed stock recovery, did OTA again --> works like a charm
Awesome!
Sent from my XT1031
I am being super kind and uploading stock images of the latest December patch for the Moto X Pure (NOT STYLE). These can be used to relock your bootloader or just reflash stock. HOWEVER I DO NOT HAVE THE STOCK SYSTEM.IMG, BUT I DO HAVE A DECOMPRESSED VERSION. If you can figure out how to compress it into sparse-chunks and make it work, go ahead. I have tried it and it won't flash when the bootloader is locked. I have tested all files, and all of them flash on locked bootloaders/oem lock begin command, EXCEPT FOR SYSTEM.IMG
DRIVE LINK : https://drive.google.com/open?id=0Bzrcf9ndDGw_U19EckExeWxiNG8
PayPal donations are welcome at [email protected]
Did you do it with flashfire app? @parker.stephens
dzidexx said:
Did you do it with flashfire app? @parker.stephens
Click to expand...
Click to collapse
If you're taking about flashing the files no, I use fastboot. If you're taking about how I got the files, I used dd.
There is a tool for splitting the system image into sparse chunks... I'll see if I can find the process.
Can I ask how you got this? Did you extract it from your device because the radio partitions are protected (or so I thought, haven't tried it in a long time).
Just curious how you were able to read some of these partitions...
EDIT: Found it I think: https://forum.xda-developers.com/showthread.php?t=2749797
acejavelin said:
There is a tool for splitting the system image into sparse chunks... I'll see if I can find the process.
Can I ask how you got this? Did you extract it from your device because the radio partitions are protected (or so I thought, haven't tried it in a long time).
Just curious how you were able to read some of these partitions...
EDIT: Found it I think: https://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
I used TWRP, but instead of flashing it, I send it as a boot image.
Instead of "fastboot flash recovery twrp.img", I used "fastboot boot twrp.img", which allowed me to get the partitions.
EDIT: SparseConverter gives me different sizes of chunks with MPHS24.49-18-8 with 8, and MPHS24.49-18-16 with 13. MPHS24.49-18-16 has each of the files being 262,144 KB and a total size of 3.17 GB. MPHS24.49-18-8 is only 1.98 GB. Here's the weird part. The decompressed system.img files are on KB apart. MPHS24.49-18-8 is 4,194,180 and MPHS24.49-18-16 is 4,194,304 KB. I'm not sure where things are going wrong, which is why I want someone else to try.
parker.stephens said:
I used TWRP, but instead of flashing it, I send it as a boot image.
Instead of "fastboot flash recovery twrp.img", I used "fastboot boot twrp.img", which allowed me to get the partitions.
EDIT: SparseConverter gives me different sizes of chunks with MPHS24.49-18-8 with 8, and MPHS24.49-18-16 with 13. MPHS24.49-18-16 has each of the files being 262,144 KB and a total size of 3.17 GB. MPHS24.49-18-8 is only 1.98 GB. Here's the weird part. The decompressed system.img files are on KB apart. MPHS24.49-18-8 is 4,194,180 and MPHS24.49-18-16 is 4,194,304 KB. I'm not sure where things are going wrong, which is why I want someone else to try.
Click to expand...
Click to collapse
But how did you extract the radio images? Used to be they were protected, if you tried it looked like it worked but you always got nothing but 0's in the image file for fsg and nonhlos
acejavelin said:
But how did you extract the radio images? Used to be they were protected, if you tried it looked like it worked but you always got nothing but 0's in the image file for fsg and nonhlos
Click to expand...
Click to collapse
Like I said, I used dd. I am going to flash it to my Moto X Pure and double-check it works and edit this post if it does or doesn't.
EDIT: All is well. Wi-Fi works, Cellular on Verizon gets 5 bars, and Bluetooth works also except for the reboot glitch where Bluetooth turns itself off. The command I used were fastboot flash modem NON-HLOS.bin, fastboot flash fsg fsg.mbn, fastboot erase modemst1, and fastboot erase modemst2
parker.stephens said:
Like I said, I used dd. I am going to flash it to my Moto X Pure and double-check it works and edit this post if it does or doesn't.
EDIT: All is well. Wi-Fi works, Cellular on Verizon gets 5 bars, and Bluetooth works also except for the reboot glitch where Bluetooth turns itself off. The command I used were fastboot flash modem NON-HLOS.bin, fastboot flash fsg fsg.mbn, fastboot erase modemst1, and fastboot erase modemst2
Click to expand...
Click to collapse
Awesome! My concern was that in previous devices, extraction of the radio firmware with DD was protected, it would only output all zeros in the image, seems that isn't the case anymore!
I will try to look at the system thing this weekend, I'm out of town til Sunday so i am limited at the moment. Can you put the raw system img file on drive?
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Alibaba0101 said:
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Click to expand...
Click to collapse
Because Motorola doesn't update that. The image there is from November 2015. That is the 1st marshmallow image shipped with Moto X Pure. A.K.A MPHS24.49-18. It is also not the latest.
Alibaba0101 said:
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Click to expand...
Click to collapse
parker.stephens said:
Because Motorola doesn't update that. The image there is from November 2015. That is the 1st marshmallow image shipped with Moto X Pure. A.K.A MPHS24.49-18. It is also not the latest.
Click to expand...
Click to collapse
@parker.stephens is correct, the image on Moto's website is ancient, literally the oldest Marshmallow image ever made for the Moto X. It has been reported to Moto in their official forums like 6 months ago and they said they would get it taken care of but nothing has changed.
We have official leaked factory images up to MPHS24.49-18-8... the OP is trying to get 18-16 for us to use... the one on Moto's website is MPHS24.49-18 (with NO subversion), it is labeled and dated incorrectly.
acejavelin said:
@parker.stephens is correct, the image on Moto's website is ancient, literally the oldest Marshmallow image ever made for the Moto X. It has been reported to Moto in their official forums like 6 months ago and they said they would get it taken care of but nothing has changed.
We have official leaked factory images up to MPHS24.49-18-8... the OP is trying to get 18-16 for us to use... the one on Moto's website is MPHS24.49-18 (with NO subversion), it is labeled and dated incorrectly.
Click to expand...
Click to collapse
Where is the MPHS24.49-18-8 image posted? I could only find MPHS24.49-18-4 on the FirmwareNstuff thread.
annoyingduck said:
Where is the MPHS24.49-18-8 image posted? I could only find MPHS24.49-18-4 on the FirmwareNstuff thread.
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/
parker.stephens said:
I am being super kind and uploading stock images of the latest December patch for the Moto X Pure (NOT STYLE). These can be used to relock your bootloader or just reflash stock. HOWEVER I DO NOT HAVE THE STOCK SYSTEM.IMG, BUT I DO HAVE A DECOMPRESSED VERSION. If you can figure out how to compress it into sparse-chunks and make it work, go ahead. I have tried it and it won't flash when the bootloader is locked. I have tested all files, and all of them flash on locked bootloaders/oem lock begin command, EXCEPT FOR SYSTEM.IMG
DRIVE LINK : https://drive.google.com/open?id=0Bzrcf9ndDGw_U19EckExeWxiNG8
PayPal donations are welcome at [email protected]
Click to expand...
Click to collapse
How did you get gpt.bin and bootloader.img?
yk1999 said:
How did you get gpt.bin and bootloader.img?
Click to expand...
Click to collapse
Tapa?
Post #3.
dzidexx said:
Tapa?
Post #3.
Click to expand...
Click to collapse
But there is no pertition called gpt(gpt is the partition table itself)
And bootloader.img contain pmic aboot tz etc i can get them separately using dd but can't get them in one bootloader.img
I didn't think,
Sorry. @yk1999
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
I didn't think,
Sorry.
@yk1999
is this our nougougt update!?!?
or at least the files we need to get the other ROMs stable??
abense said:
is this our nougougt update!?!?
or at least the files we need to get the other ROMs stable??
Click to expand...
Click to collapse
No, this is marshmallow.
Did anyone already perform a system restore after processing with sparse converter by any chance?