Related
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
pl4yb0y78 said:
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
Click to expand...
Click to collapse
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
edit: the all in one toolkit is great for things like this. It will put a new recovery on your phone with just a click of the button.
http://forum.xda-developers.com/showthread.php?t=1604677
tivofool said:
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
Click to expand...
Click to collapse
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
pl4yb0y78 said:
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
Click to expand...
Click to collapse
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
tivofool said:
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
Click to expand...
Click to collapse
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
pl4yb0y78 said:
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
Click to expand...
Click to collapse
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
tivofool said:
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
Click to expand...
Click to collapse
Thank you for the reply yes i am getting stressed at this and i am new had a break before i smashed the phone now ive just got to find out what my phone is s3 or s4 ? google will help
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
pl4yb0y78 said:
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
Click to expand...
Click to collapse
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
tivofool said:
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
Click to expand...
Click to collapse
yes i now have the twrp in recovery it says enter password and cancel i tried both it was the s4 one that worked so im guessing its an s4
what will the next step be? (if i need anything please could you leave a link)
thanks for all the help starting to feel i might win lol
in twrp when you press "mounts" then press "mount usb", does your computer finally see your phone?
I was looking at your first post, you say that you rooted and flashed your phone. What do you mean by that? Did you download a ROM and attempt to flash it? Or did you "fastboot flash boot boot.img"?
If you are able to access your phone via computer it is as simple as downloading a rom on your computer moving it to your phone then in twrp "install from zip". Then fastboot flash the boot.img.
http://forum.xda-developers.com/showthread.php?t=1583427
how to flash fastboot
http://forum.xda-developers.com/showthread.php?t=1752270
if you are just fed up and want your phone back to stock then you will need to run an RUU.
http://forum.xda-developers.com/showthread.php?t=2094414
To run a RUU you would need to relock your bootloader.
in console type "fastboot lock oem" or use your all in one toolkit to relock it.
if that fails you will need to put your stock recovery back. (you need to have boot loader unlocked to do this)
on the clockworkmod recovery page the stock recovery is the second download link.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
pl4yb0y78 said:
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
Click to expand...
Click to collapse
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks and yes i can do that i will try and get back to you
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
pl4yb0y78 said:
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
Click to expand...
Click to collapse
The command is:
Code:
fastboot flash boot boot.img
khan.orak said:
The command is:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
ok i try this i am only learning but getting there lol
Hi together,
I've got a Motorola Photon Q 4g LTE mobile phone and this afternoon I wanted to install CyanogemMod, but whatever I do, I stuck with the following problem:
I can't install any other Custom Recovery. I tried ClockworkMod and OpenRecovery, but I always get the s**t Motorola Bootloader, when I start in Recovery Mode. The Bootloader of my Phone is unlocked via Motorola Website, as told in many other threads.
I know that the users arrrghhh, shabbypenguin and Skrilax_CZ are great experts with firmware and such things, but I'm not allowed to write in developer's forums because I'm new here.
Has anybody got an idea for me, how to geht the Custom Recovery to work?
Btw: I tried to root the phone as well, but that wasn't posible. May be things come together or depend on each other.
Thanks for your help!
When you flash recovery (IE run the fastboot command) is it successful?
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Also, try this.
arrrghhh said:
When you flash recovery (IE run the fastboot command) is it successful?
Click to expand...
Click to collapse
When I flash recovery, I just flash the Motorola given Recovery by Motoroloa Bootloader. The Phone restarts, a logo with the Android Man is shown (stomach opend with some engeniering tools in it) and after about 5-7 Minuten, the system starts normally.
I also managed it to change the "Unlocked Message" into a Motorola Logo by using fastboot flash logo xxxx.bin and I nearly destroyed the flash by flashing an unlikely file. So the phone was shortly out of order because oder "flash failure" (fastboot mode). After that, I managed to flash the "boot.img" file of an CyanogenMod, so the flash was rebuilt and I could use the phone normally.
arrrghhh said:
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Click to expand...
Click to collapse
It shows the connected devices by showing a 8 or 9 ditigt number. It's almost the same view like I connected the phone without fastboot and use "adb devices".
arrrghhh said:
Also, try this.
Click to expand...
Click to collapse
This one I didn't tried yet, because I was so dissappointed of the mismatch with ClockworkMod & Open Recovery. Do you think, that trying this one will help, after two others failed?!
Thanks for you notice and your time. That's very helpful!
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
arrrghhh said:
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
Click to expand...
Click to collapse
Ah ja, now I'm one step closer. I did not know, that the dead Android dude is the sign for stock recovery.
I'll give it this afternoon another try and will report. A bunch of thanks to you at this time!
Hi, it's me again. I managed now the reboot to recovery, by holding the volume up button while doing the "fastboot reboot"-command with the command box. That worked and I could start Photon Q Open Recovery 2.06.
Unfortunately, I did something wrong or so and now the script re-flashed stock recovery again. Nevertheless, I now know how to operate and will do the rest by my own (hopefully).
@arrrghhh: Thank you very much for your help!
So, I finally did everyhting the right way (now with ClockworkMod Recovery), because I now have CyanogenMod running on my Motorola Photon Q
:victory:
@arrrghhh: Thank you very very much!
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049
Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.
fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7
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!
hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help
Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.
https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide
One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader