Related
Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.
ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.
kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.
kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style
Failed all the way.
kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.
I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:
Did you try the manual steps that I posted in my links?
i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.
What do you mean with recovery?
kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.
Keeps saying it can't mount anything.
kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen
Hello all.
I rooted my Razr HD after the most recent update (prior to KitKat), so I'm rooted but not unlocked. In my ultimate wisdom, I completely removed (did not merely freeze) some bloatware apps, and only today am learning they are necessary to receive OTA updates.
A factory reset did not restore the apps.
Is it possible to get these bloatware apps back onto my device, or am I pretty much screwed?
If there is a way to restore them, am I screwed anyway due to having previously rooted my device and not having a way to flash a ROM?
My apologies if these questions are dumb; I've been looking for information regarding this for a couple hours and have come up empty so far.
Depending on what version you are currently on, you will need to get the correct FXZ image to fastboot onto your device to return it to stock.
Go here to fix you right up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Sent from my Nexus 7 using Tapatalk
Thanks a lot for the advice and the links. The process seems to work ok up until it tries to flash system.img.ext4, at which point it returns the message "Phone returned FAIL.; phone connected". If I remove that one line from the XML file, everything else goes through with no issues, so that seems to be the last thing holding me back.
When I attempt to boot the phone, I receive the following:
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Click to expand...
Click to collapse
I will double-check some things and try one more thing before I declare myself stuck again.
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
A little help..
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Worked for me
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
froyton said:
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
Click to expand...
Click to collapse
Eustace2 said:
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
Click to expand...
Click to collapse
Glad it helped.
---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------
moodaddy said:
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Click to expand...
Click to collapse
Go back to the following link and get the latest FXZ generator. SamuriHL has been updating it as people have been reporting issues:
http://www.droidrzr.com/index.php/topic/45349-rsd-script-generator/
He updated it yesterday to handle issues for your phone (XT907) and the XT926s as well. See if that fixes your issue. Otherwise, I'm not sure how else to help you.
So the usual things has happened.. I have looked many different places, forums, and posts and the closest thing I have found was this thread.
http://forum.xda-developers.com/showthread.php?t=2423716
However it didnt help me at all so now I am posting this to see if there is an angel out there that can help me.
He is the problem.
1. It will show this if I plug it in to my PC but I cant turn on the device by its self.
"AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure"
2. It doesnt charge.. I dont think
3. When I hold the Vol- and PWR for 10 ten then add the Vol+ it sometimes will go to the bootloader and then it will boot.
Can I fix this to not show this message every time?
Thanks for your time
-Avethepizzaman
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
K I have it charged..
Avethepizzaman said:
K I have it charged..
Click to expand...
Click to collapse
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
bweN diorD said:
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
Click to expand...
Click to collapse
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Avethepizzaman said:
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Click to expand...
Click to collapse
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
bweN diorD said:
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
Click to expand...
Click to collapse
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Avethepizzaman said:
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Click to expand...
Click to collapse
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
bweN diorD said:
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
Click to expand...
Click to collapse
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
That's a lower version. Unless you unlocked your bootloader, which it appears you haven't, you cannot downgrade from 182.46.15. If you didn't unlock your bootloader (which I'm assuming because in your first post, you showed that the status said "locked" in fastboot mode), then you have no way to root, unlock the bootloader nor downgrade. You can only reflash the latest which is 182.46.15.
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
ok, i was tired and forgot about the "tz".
to avoid any further confusion, download the firmware from here and replace the xml file with this one. i already edited it. then flash again.
now that we have all the facts straight, and files in line, it should go fine this time.
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Avethepizzaman said:
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Click to expand...
Click to collapse
wow, your phone is being a pita lol
follow the instructions here to fix that.
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Avethepizzaman said:
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Click to expand...
Click to collapse
np! happy to help
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!