After using rsdlite to flash telstra Australia over FR jellybean leak, my phone is now bricked because it says at 16/19: no valid PIV block in SP for system. Piv validation failed (system).*So I tried to re flash the FR Vodafone ica stock through rsd and then it fails at 16/19 and says phone read failed.*Now my phone can't get into recovery, and is stuck at fast boot..*What can I do??
The PIV error means the image you tried to flash wasn't properly marked and signed (not sure about the details, but there is some magic header missing I'm the file...), you may need an unlocked bootloader and/or fastboot instead of rsdlite, or something else, to flash that.
If you can get into fastboot mode, you should be able to unbrick it, with a properly signed image, like the one coming from a leak or official fastboot.
Make sure you're not running rsd lite from a virtual machine like virtual box, as that will fail. I had virtual box with win xp running on my macbook and it won't work, I had to use a real windows machine, or fastboot.
If you're comfortable with the command line, get the system image out of the zip file and try with fastboot instead:
fastboot flash system system.img.ext4
If you still get errors, with either rsdlite or fastboot, post the exact error then we'll see.
Sent from my XT907 using xda app-developers app
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
royalbloodvi said:
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
Click to expand...
Click to collapse
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
aslomagic said:
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
Click to expand...
Click to collapse
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
and ends up being fastboot reason: sticky bit factory_fastboot
do u happen to have the boot.img of stock ics? maybe thats the reason..
&
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
royalbloodvi said:
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
Click to expand...
Click to collapse
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
aslomagic said:
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
Click to expand...
Click to collapse
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
as a side note: i accidentally flashed the CWM backup boot.img to my phone in my other post: http://forum.xda-developers.com/showthread.php?p=35045589#post35045589
is this the reason it keeps failing now when it should not? i flashed this command halfway during the rsd lite process..
royalbloodvi said:
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
Click to expand...
Click to collapse
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
aslomagic said:
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
Click to expand...
Click to collapse
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
royalbloodvi said:
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
Click to expand...
Click to collapse
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
aslomagic said:
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
Click to expand...
Click to collapse
unfortunately its not dev edition, device is locked.. =(
but i will try the JB method and see what happens now
royalbloodvi said:
sorry it is a locked bootloader.
Click to expand...
Click to collapse
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
aslomagic said:
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
Click to expand...
Click to collapse
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
I am in the exact same boat as you... No success and I have tried everything!
royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
Well, at this point, I really don't know ... if it happened to me, I'd be in "trial and error mode" now
Have you tried wiping the cache partition (fastboot erase cache, I think)?
Also, you didn't say if you managed to flash back a known-good boot.img, as well ...
I unbricked my phone, had to mix and match system files between telstra and Vodafone fr, and get it to boot up to the Motorola logo.
If you so manage to get to logo, it can be re stored just take it to Motorola service centre and they will flash their software and Walah.. Costed me 55$ but but better than a expensive junk
Sent from my XT925 using xda app-developers app
Paying is not an option. I'm currently fixing my Atrix HD. Not that hard once you find the right file. Mine failed in RSDlite on step 1/23 and I just hit it again and it went through all the way. You should've tried that. Next time, because there WILL be a next time, just send through the xml file again through rsdlite.
My phone just finished booting up as I typed this.
Hey guys I have somewhat of a problem. I'm experienced when it comes to rooting phones (by no means an expert), but this problem has me stumped. You see, I was helping my friend to root his phone Photon XT897 and showing him how to do it. We got the device unlocked, installed CWM and rooted the device, all without issue. Anyways, I had to leave to go to work and he decided that he knew enough that he wanted to install TWRP recovery. According to him he did that by flashing an image of TWRP via fastboot, and everything was fine... except his wifi would no longer turn on. He then proceeded (and God alone knows why he thought this would help) but he formatted the modem in recovery and now, obviously he gets NO data connections whatsoever. I've scoured this site and everything I've been able to find online to fix this with no result; can somebody please help me? So what I need to know is this:
1. Has anyone else experienced wifi issues (i.e. the wifi no longer turning on) when flashing TWRP?
2. Is there any way to restore the modem?
3. Can I trade my friend in for a smarter version or at least store credit?
Thank you!!
No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here: http://sbf.droid-developers.org/asanti_c/list.php
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin
hfase said:
No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here:
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin
Click to expand...
Click to collapse
Thank you for the suggestion, but I tried both of those and neither one produced any results. I can't flash the NON-HLOS.bin in fastboot becuase it says:
F:\Scottys Droid ****\Devices\Motorola\Photon XT897\android-sdk-windows\platform
-tools>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'NON-HLOS.bin': No error
I can't flash the entire file with RSD because at first it throws the error:
getvar not found or something to that effect which I understand; getvar isn't a fastboot command. I then googled that problem and somebody with a similar issue with another phone said merely removing the line of code in the xml that calls for "getvar" fixed their problem. I tried that and now I get the error:
Flashing process failed flash sbl1 "sbl1.bin" -> phone returned fail.
Any other suggestions?
Are are the files extracted to folder you are running that command in?...
If not you will need to call the file with its absolute location. In ubuntu that looks like the following:
fastboot flash modem /home/hfase/Desktop/modem.bin
Hence the ". /" shown in my earlier example. Meaning "same dir" in linux. these will of course be different on Winblows.
If you cant get fastboot to flash just that try backing your system/data up with TWRP and just flash it with RSD. (using the edited XML found around here...) Basically for RSD to work you need to delete the getvar's in the XML.
If you look at my posts I posted a thread showing the XML file you need with the getvars edited so it works,, and even added the steps to relock the bootloader if you are interested lol
Sent from my XT897 using Tapatalk 2
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
I'd love to... how?
arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
Actually, RSD Lite is suddenly working now... but I didn't do anything different so I don't understand why its cooperating. Well, there is one thing different that I did: I restored a TWRP backup that my friend made before the phone went down. You see, after he wiped the modem partition he installed a ROM (the Evervolve ROM), which didn't boot. He did this in an attempt to fix his mistake, thinking that the ROM carried a modem file in it. When I learned of this backup, I restored it and got into the phone; obviously the modem still wasn't working, but then I figured I would try the RSD flash again. So I removed the "getvar" lines of code from the "asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml" and it worked.
So the modem issue is now fixed, but wifi issue is not. I'm unclear as to whether I should close this thread because it's main issue has been solved, or if we can now take a look at the wifi issue. Basically, after flashing the TWRP recovery through Goo Manager that I downloaded from the market (I did this in the app by choosing the "install script" option, as I was instructed to by another of XDA''s threads) I then rebooted the phone only to find that the wifi didn't work. Whenever I go to turn the wifi on, the switch immediately goes back to the off position, but in the window below the switch it still says "turning on wifi." Please advise if I need to open a new thread, or if not, how we can perhaps solve this wifi problem. Thank you.
OK, glad you got the phone booting again.
Have you tried just doing a 'factory reset' in TWRP since you got the phone back to a functional state?
What kernel is flashed?
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!
Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.
My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!