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!
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...
Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.
I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively
Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!