Related
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.
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...
Hi all,
I'm after some help with a 1st gen Moto G. It belonged to my mother, and was happily running CM for years before dying on her one day. She posted it back to me months ago...I failed to fix it then, and I'm not having much luck this time either.
It sits on the bootloader ok, and I can fastboot interact with it, but although attempts to revert to stock, or update TWRP etc look like they've worked, nothing ever changes. It's as if its storage has gone read-only.
CM is still there, but bootloops 9 times out of 10. Occasionally it'll start properly, before rebooting seconds later, probably because it can't write anything and it crashes out.
I can however, boot (not flash) the latest TWRP and play around with that, but even simple file operations like trying to delete anything fails ("process ended with ERROR 1"). I've tried clearing, factory resetting, reformatting, etc, but nothing has an effect. CM and the old files are all still there.
I don't need this phone, nor the files on it - it'll go in the trash if it can't be fixed - so not worried about damaging it any way in an attempt to revive it
Thanks
Everything you describe suggests Emmc corruption. Threads are created about it regularly. It's an issue that can effect any android phone, and while age could be the key factor - my launch-day Falcon has never had an issue. There is no cure.
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Everything you describe suggests Emmc corruption.
Click to expand...
Click to collapse
Ah, interesting. It's not something I've come across before, so it's good to at least know what's (probably) wrong with it.
lost101 said:
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
fastboot transfered about 26% of the file before exiting.
TWRP reported:
Code:
installing zip file '/sideload/pacakge.zip'
>>> XT1032 Retail Europe 5.1 (Untouched) <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
Updater process ended with ERROR: 7
imilne said:
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
Click to expand...
Click to collapse
Do as I instructed to remove all doubt of Emmc corruption.
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!