Related
Guys really need some help.
Bought an unlocked Razr HD from the web, and ungraded via OTA from 4.0.4 to 4.1.2. Then I rooted using dan's method, ran the script, phone was rooted. Then i decided to install TWRP, same way, in fastboot mode, ran the cmd 'fastboot flash recovery twrp-2.5.0.0-recovery-vanquish.img' then rebooted, but what essentially happened after, i was never able to boot the phone in recovery and every single time i ended up with fastboot reason" flash failure.
Then i was able to recovery from falsh failure by running 'empty_radio.img', after rebooting, the phone started up normally, but stock recovery was still corrupt, every single time i used to get the 'red triangle dead andriod', so booted back into fastboot, performed a clean wipe with fastboot -w and booted back normally, and flash failure was gone, and i was was able to reboot the phone normally.
Then i decided to unlock the bootloader, was was successful using Dan's method; my goal was to install 4.2 from recovery. Then i installed DroidUtility and decided to perform an clean install wiping all data. The problem was at every step i got the FAILED (remote failure) line, soon after phone got stuck with fastboot reason: 'Sticky bit fastboot'.....every single time i reboot phone gets stuck in the initial screen ' WARNING BOOTLOADER UNLOCKED' and thats it....i can't do anything...stuck....screen stays on for 10mins, then reboots back to this screen and keeps on looping.
Please help guys!! i hope i haven't bricked the phone.
eomahos said:
Guys really need some help.
Bought an unlocked Razr HD from the web, and ungraded via OTA from 4.0.4 to 4.1.2. Then I rooted using dan's method, ran the script, phone was rooted. Then i decided to install TWRP, same way, in fastboot mode, ran the cmd 'fastboot flash recovery twrp-2.5.0.0-recovery-vanquish.img' then rebooted, but what essentially happened after, i was never able to boot the phone in recovery and every single time i ended up with fastboot reason" flash failure.
Then i was able to recovery from falsh failure by running 'empty_radio.img', after rebooting, the phone started up normally, but stock recovery was still corrupt, every single time i used to get the 'red triangle dead andriod', so booted back into fastboot, performed a clean wipe with fastboot -w and booted back normally, and flash failure was gone, and i was was able to reboot the phone normally.
Then i decided to unlock the bootloader, was was successful using Dan's method; my goal was to install 4.2 from recovery. Then i installed DroidUtility and decided to perform an clean install wiping all data. The problem was at every step i got the FAILED (remote failure) line, soon after phone got stuck with fastboot reason: 'Sticky bit fastboot'.....every single time i reboot phone gets stuck in the initial screen ' WARNING BOOTLOADER UNLOCKED' and thats it....i can't do anything...stuck....screen stays on for 10mins, then reboots back to this screen and keeps on looping.
Please help guys!! i hope i haven't bricked the phone.
Click to expand...
Click to collapse
Seeing how the phone is now updated to latest ota try Matt's Utility for the Droid RAZR HD i used this to get my phone is working condition then i did some adb and fastboot commands using some files to get rid of the sticky bit fastboot.
Heres a link to the RAZR HD utility: http://forum.xda-developers.com/showthread.php?t=2239425
Heres a link to get rid of the sticky bit fastboot menu (if you do end up getting this menu):http://forum.xda-developers.com/showthread.php?t=2260105
Hope this helps and good luck bro.
P.S if you did brick your phone its not the end of the world. the epic devs of XDA figured out how to fix problems like this. I bricked my phone by installing beats audio app ( worst mistake ever) came here for help and next thing i know my phone up and running like a charm ^^
well i did try matt's droid utility, and that's what put me in this state in the first place, since my stock recovery was corrupt, i decided to just clean install JB from Matt, but all the steps failed, it said remote failure at every step....and that was it! fastboot reason: flash failure,if i hold +/- and power, the phones boots up and gets stuck on the first screen..in this case since the bootloader is unlocked, it gets stuck on the WARNING message.
Also did try to fastboot with these commands:
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
same, gets stuck on WARNING screen after reboot.
eomahos said:
well i did try matt's droid utility, and that's what put me in this state in the first place, since my stock recovery was corrupt, i decided to just clean install JB from Matt, but all the steps failed, it said remote failure at every step....and that was it! fastboot reason: flash failure,if i hold +/- and power, the phones boots up and gets stuck on the first screen..in this case since the bootloader is unlocked, it gets stuck on the WARNING message.
Also did try to fastboot with these commands:
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
same, gets stuck on WARNING screen after reboot.
Click to expand...
Click to collapse
Have you tried flashing the phone with rsd lite?
Oh boy!! i made a major error, i someone didn't read the version...and used matt's utility xt912 on my xt925. is there a link for xt925? what can i do now? Can i use matt's xt926 on my 925?
eomahos said:
Oh boy!! i made a major error, i someone didn't read the version...and used matt's utility xt912 on my xt925. is there a link for xt925? what can i do now? Can i use matt's xt926 on my 925?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2241788 from what i heard it works both on xt925 and xt926
oh wow....it did work. But now the problem is not sure if it locked the phone or not, but it's not recognizing my SIM. it said stock rom for both xt925/926. it seems that this is a verizom ROM, and on the device info it's listed at xt926. Not sure if that is the issue or not? can flashing the ROM lock the phone?
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
eomahos said:
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
Click to expand...
Click to collapse
Why dont you just flash twrp. Have it the same directory as the fastboot files from Hashcodes page on goo. Im. Cd to the directory with a command prompt and type faatboot flash recovery then the name of the file. Should overwrite your stock recovery and allow you to flash whatever you want.
Sent from my Transformer TF101 using xda premium
eomahos said:
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
Click to expand...
Click to collapse
I know you've stated that you can't get RSD to install, however if you can; perhaps borrow a friends computer to do it, then there's a variety of stock XT925 ROMs on this page http://sbf.droid-developers.org/vanquish_u/list.php
and instructions for flashing here http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html which states its for the XT926 however I restored my 925 using my carrier's ROM from the first link and the tool and instructions on the second link. I only had one line with getvar in it to remove from the xml file. I've actually flashed both my carrier's ROM and then a generic one for my locale.
If you go this route, borrowing a friends computer, make sure you download the ROM from your carrier (assuming its there) with the higher version number or you'lle be attempting to flashing ICS and there's some post floating around that implies a downgrade from 4.1.2 to ICS causes problems.
The instructions look a little daunting but the xml files I saw, in both ROMs, were very short. Just be sure to use notpad when you edit. The other thing to be sure of, which isn't otherwise stated, is that RSDlite runs for a while even after the phone reboots. I made the mistake of pulling the cable when I got to the setup screen the first time I did it and thought it was a problem with the ROM or the flash of it. The reality, I think, after looking more carefully the second time, is that RSD is still running and doesn't say finished for a little bit after the boot and until I was still filling out the thing for the intial phone setup... Google acount, Google Plus, etc.
Link to a thread on the subject (also heavily 926 implied) http://forum.xda-developers.com/showthread.php?t=2211234
Since your'e unlocked you no longer need to use any exploit to gain root. Get a flashable supersu.zip on the phone, install a recovery and root you will have; just install the zip...
Have a full battery when starting the ROM flash.
thanks alot buddy, i'll start reading into it. So, i did finally manage to install TWRP, and did manage to flash the ROM with stock 4.2, tried both xt926/925, however, now the issue is i dont get any reception, nothing at all, everytime i search, it comes back with no network found. Can you please advise? i was able to bypass the corrupt recovery, install a clean 4.1.2 xt926 ROM, but i never got any reception, installed TWRP, then tried 4.2 ROMs. No, i get nothing...miss i mess up the radio?
eomahos said:
thanks alot buddy, i'll start reading into it. So, i did finally manage to install TWRP, and did manage to flash the ROM with stock 4.2, tried both xt926/925, however, now the issue is i dont get any reception, nothing at all, everytime i search, it comes back with no network found. Can you please advise? i was able to bypass the corrupt recovery, install a clean 4.1.2 xt926 ROM, but i never got any reception, installed TWRP, then tried 4.2 ROMs. No, i get nothing...miss i mess up the radio?
Click to expand...
Click to collapse
Hi, I tried replying to your PM however the server isn't reporting it sent or is having troubles sending or whatnot. Let me know if you got it or not.
In any case, of most relevance, who was your carrier when your phone did work? That is going to hopefully be the starting point, I believe.
...also, please quote my text if responding so that I get an email notification, otherwise I'll forget XDA exists for days at a time...
Well, first thanks for listening, and please have patience, haha.
I have a Moto G XT1033, my cousin, he tried to unlock the bootloader and the process has not been finalized (I think) because the phone does not turn over, just stood in the LOGO screen.
I tried to reinstall the ROM Stock, but unfortunately I did not succeed
I tried several things and nothing.
I've tried:
1- reinstall the original ROM XT1033 4.4.4
2- install the original ROM XT1033 4.4.2
3- Install the ROM XT1032 4.4.4
4- Install the ROM XT1033 5.0.2
and nothing happened :'( .
so I tried to unlock the Bootloader to see if I could get into recovery mode, to be able to WIPE Cache and Factory. But that was when I discovered that even reinstalling the ROM's and clearing the caches, was not affecting anything on the phone, I was in the Install from SDcard and all folders were there (Whatsapp, PicsArt ...)
I can not install Custom Recovery and not install any ROM since it is not installing anything !!!
and when I Wipe cache it restarts on its own and does not delete anything!
I am Brazilian and I used Google translator to write this text, I hope to help me! Thank you for listening! <3
I have a Moto G XT1032 with unlocked bootloader, custom recovery TWRP and android 5.0.2 via adb, no problem
Can you boot into fastboot? Does it say the bootloader is unlocked?
So you are able to flash a stock ROM without errors?
Can you get into stock recovery to wipe?
audit13 said:
Can you boot into fastboot? Does it say the bootloader is unlocked?
So you are able to flash a stock ROM without errors?
Can you get into stock recovery to wipe?
Click to expand...
Click to collapse
Yes, but nothing works, the adb process of all "Okay" but when rebooting, it is only on screen logo and does not start, and after about 2 minutes it restarts again.
audit13 said:
Can you boot into fastboot? Does it say the bootloader is unlocked?
So you are able to flash a stock ROM without errors?
Can you get into stock recovery to wipe?
Click to expand...
Click to collapse
You can boot into fastboot? - Yes said the bootloader is unlocked? - yes
So you are able to flash a ROM stock without errors? - Yes and no XD (in adb shows that installs but does not actually install anything)
You can get in stock recovery to clean? yes and no (the screen shows that wiped but not actually cleaned anything, the fiction folders all there in the same place, whatsapp etc ...)
You are using ADB or fastboot to flash stock ROM? Fastboot commands only work when the phone is in fastboot mode.
audit13 said:
You are using ADB or fastboot to flash stock ROM? Fastboot commands only work when the phone is in fastboot mode.
Click to expand...
Click to collapse
good, I do not know a lot of things, but change ROM's and those kinds of things I can do, you see, is that what's going on I've never seen, practically the cell turned into a zombie, he's dead just not hahaha.
I'm using the ADB and Fastboot the in the same folder, and installed the ROM's in fastboot mode (vol - + Power)
it's OKAY in the installation process, only it does not actually install anything.
already tried deleting the cache but he n erases anything already gave factory reset and nothing happens: '(
researched two days and a half on the subject to try to solve it, but I was out of options, so I posted here in the forum, takes a lot to help me with this!
in the process with my phone got everything worked unlock the good bootloader, install custom recovery and rom lollipop
since my cousin was not so lucky
he screwed the phone in bootloader unlocking process (if I'm not mistaken)
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
After trying for over three hours, reading what seems like all threads on the whole of xda and some other sites... i am ready to eat my phone. Ok, must get myself together :-/ . Here we go.
Specs:
Moto G 4g on dutch carrier (vodafone), XT1039
Situation:
Came from completely stock lollipop system, then succesfully unlocked phone via motorola website using the fastboot proces. Intending to install custom rom, first need a recovery. I am now stuck at this step. When booting i now get a screen "warning bootloader unlocked" before the moto splash begins, this is normal as far as i understand.
Problem:
Unable to boot into recovery. Directly after flashing any recovery (with fastboot) and choosing "recovery" from the bootloader i get the message "boot up failed"
After restarting the phone and choosing "recovery" from the bootloader i get the android on its back picture stating "no command"
Already tried:
installed the android sdk, fastboot and mfastboot.
Am able to send commands to phone with (m)fastboot. Flashing works.
I flashed: openrecovery twrp 2850 xt1032, clockwork 6047 falcon, philz touch 6587 falcon, twrp 2870 falcon m stock, twrp 2801 titan v2 and twrp 2860 xt1032
all give exact same result
"fastboot boot NAME of IMAGE"
"fastboot erase userdata & cache"
"fastboot erase recovery"
did the above things in any imaginable combination
I hope someone has some fresh suggestions for me? Thanks for your time.
Bro as far as I know the recovery is not installed u should install twrp from this thread the one on the official site gave me soft brick
Now about the dead android with no command shows that you are on stock recovery and u have booted into it successfully to go further into stock u have to press power and volume up at the same time (like u lock ur phone) but it won't help in installing anything try the recovery I linked (first format your phone complete data and cache wipe from stock recovery not necessary actually) install it through fastboot command and let me know if it worked (with thanks button) BTW what's ur bl ver
thanks for your fast response faizxy, as stated i already tried the one from that thread (i did not use the identical interpunction to describe it but to be clear it is twrp-2.8.7.0.-falcon_M_STOCK.img)
Where do i find my bootloader version? It is the one that came with the device, factory issue...
Some extra info, that might anwser faiz' question: when i boot the bootloader it shows:
"AP Fastboot Flash Mode (S) 41.1A (sha-80481ae, 2015-04-10 14:30:28)
Hope you guys will forgive me for bumping a bit soon, but I really hope some one has a solution! Tomorrow I have time to tinker some more
Have you tried at least one recovery that is actually for your phone (peregrine)?
_that said:
Have you tried at least one recovery that is actually for your phone (peregrine)?
Click to expand...
Click to collapse
Ah. I guess not. Did not know that there where recovery's specifically for the peregrine/xt1039. I searched for "moto g" but apparently is wrong model. DOH!
Thanks for helping out! My problem is solved.
For future reference; finding working pergerine recovery was quite difficult; most mirrors are down. I found one here: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine and then under header "installing recovery.." under step 2 the download link (i avoid deeplinking)
This one seems to work for me. Now lets find a nice custom rom!
The ones listed here http://forum.xda-developers.com/moto-g/4g-development/progress-twrp-2-7-1-0-source-t2807585 dont work for me. One gives black screen, the other one shows an unlock slider which is unresponsive.
Hi,
Try this one... With encryption abilities or without, your choice...
http://forum.xda-developers.com/showthread.php?t=2996266
Well, long story short, I've managed to f*ck up my Moto G. I was having problems with the SD Card ejecting itself on the modified stock 6.0.1 Rom found here so I decided to go full stock again to have a good base to go to, and flash again TWRP, and Turbo or another rom. I had one stock rom downloaded, so I tried that one, I applied that with RSD Lite without noticing that wasn't for XT1542, but for XT1040, aka Moto 1st gen LTE. Needless to say that I received a black screen with red letters tell me that the kernel failed to load. I tried flashing again with stock 5.1.1 in RSD Lite and manually since the XT1040 rom was a 5.1.1, and I can't, gpt.bin fails to flash (preflash validation failed), so I skipped it, and skipped the bootloader like it was a downgrade from 6.0 to 5.1.1, and it worked, the OS boots, and I was able to flash 5.1.1 and 6.0 again, but can't flash anything else stock, like I was on a locked bootloader, even when it says "Device is UNLOCKED" and the "oem unlock {key}" says that the command doesn't work in the device in that state (unlocked) and I can't relock (it asks me to fully flash stock, which I can't do), and I can't manual flash anything else since gives the "preflash validation failure" error.
TL;DR: Flashed wrong stock full rom into G 2015, semi fixed it, phone works but now can't flash own device full stock roms. Send halp.
Did you Flash the bootloader from xt1040?
Have you tried fastboot erase? Erase all partitions and then fastboot flash. I had the same issue when I had Moto G1 and had to erase the partitions before fastboot flashing stock rom.
Śūnyatā said:
Have you tried fastboot erase? Erase all partitions and then fastboot flash. I had the same issue when I had Moto G1 and had to erase the partitions before fastboot flashing stock rom.
Click to expand...
Click to collapse
NO!!! Never do a 'fastboot erase all' - this is really bad, it will wipe the hidden partition that hold the IMEI and other special information, which may not be recoverable at all.
Fastboot flash the bootloader, then reboot to bootloader again, then proceed to flash each piece manually, should be OK. If you can't flash the bootloader, you are pretty much screwed.
HelpMeruth said:
Did you Flash the bootloader from xt1040?
Click to expand...
Click to collapse
I suppose so. Because the rom I flashed, I did it via RSDLite, and the flashing process wasn't interrupted in at any time.
acejavelin said:
NO!!! Never do a 'fastboot erase all' - this is really bad, it will wipe the hidden partition that hold the IMEI and other special information, which may not be recoverable at all.
Fastboot flash the bootloader, then reboot to bootloader again, then proceed to flash each piece manually, should be OK. If you can't flash the bootloader, you are pretty much screwed.
Click to expand...
Click to collapse
Thanks! I'll try that.
Update: Finally fixed it. I had to use another official stock rom (I deeply thank the guys that put together the stock rom images in the General section, true saviors there), this time the operator 'branded' rom (Personal Argentina) that came with the phone, because the Latin American Retail found here didn't work at all, and gave all that flashing errors. With that and RSD Lite flashed successfully, no errors whatsoever, and the OTA worked great so now my bootloader screen reads "Software status: Official" again. Thanks to everyone that replied.