Sony Xperia Z5 TWRP Help Needed - Xperia Z5 Q&A, Help & Troubleshooting

Hello Everyone
I need some assistance with my Z5 and getting a working solution around twrp, now I have read tons of different forums and posts and have followed the steps but still can't seem to get twrp working on my device.
I have done as follows :
Just some extra information, current my phone is on FW 32.1.A.1.185. I have tried kernel version v30. As for TWRP I have tried multiple v3.0.2 versions.
1. Unlocked Bootloader
2. Flashed the Andro Kernel (I have tried multiple versions of the kernel even)
3. Flashed TWRP ( Again I have tried multiple versions).
All that keeps happening when I try and boot into recovery is a black screen with a green led on. I can't seem to get TWRP to "Work" and advice/assistance would be greatly appreciated as I just don't know where to go from here.
Regards
Inslightza

Try the command ''fastboot boot twrp.img'' and try flashing from there.
Also, decribe your procedure more in detail, as in e.g. (I used the command fastboot flash 'x' 'name of img')
-Aero

aerostride said:
Try the command ''fastboot boot twrp.img'' and try flashing from there.
Also, decribe your procedure more in detail, as in e.g. (I used the command fastboot flash 'x' 'name of img')
-Aero
Click to expand...
Click to collapse
Hi Aero
Thank you for the reply, I managed to get it working. Just flashed stock rom and tried everything from scratch again.

Related

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

[HELP] Black Screen Even after Restoring to stock firmware & Cannot relock Bootloader

[HELP] Black Screen Even after Restoring to stock firmware & Cannot relock Bootloader
My phone - Moto G XT1033 Asia Dual Sim
I updated my phone to 5.0.2 official via OTA.. And then unlocked by bootloader...
Everything was working fine, after few days, phone suddenly stopped working.
I restarted my phone and after that, every time after moto boot animation, it always gets stuck at a black screen, showing nothing
I tried all the tutorial of Reverting back to stock firmware.. I tried flashing following files via both fastboot and mfastboot... Everything gets flashed successfully without any error.
First I tried 5.1. file named - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml
Then 5.0.2, ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml
Then 4.4, ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
Still same problem persists.. Phone does not starts after moto boot animation and stucks at a black screen..
I tried to downgrade to 4.3, tried to flash this file fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar, but it always show prevalidation of firmware failed.
Screenshots of my bootloader and the blackscreen have been included....
Also I tried relocking my bootloader several times.. But after flashing a stock firmware, there comes a screen where is it written locked and when I reboot to the bootloader, it still shows unlocked..
This is how my bootloader looks right now http://postimg.org/image/4w8zrwgrp/
Bootloader Unlocked Warning http://postimg.org/image/o76nd4qux/
Moto boot animation works perfectly http://postimg.org/image/m3w85gr21/
And then this black screen comes and phone stucks here. http://postimg.org/image/5775d1ji1/
Fastboot results in Cmd after flashing Stock 5.0.2 http://postimg.org/image/a6ksy5nyv/
http://postimg.org/image/uf86jvn9z/
http://postimg.org/image/5zzyitod3/
Please please please help me now... I have been asking since a long time.. And have described my problem clearly this time..
Is there anyone who can help me
Somebody please help me
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
happiy91 said:
Today I tried restoring to the stock firmware 5.1.1 ( Moto g XT1033 Asia Retail, which my phone had before going dead). I flashed all the files correctly with mfastboot... Everything went right...
Click to expand...
Click to collapse
Post a full console log of your fastboot commands and the corresponding output.
happiy91 said:
I have unloacked bootloader.. And I think since before going dead usb debugging was not on,, I am unable to flash custom recoveries.
Click to expand...
Click to collapse
USB debugging affects only Android and is not required for flashing custom recoveries.
Finally. Somebody replied.. Thanks a lot..
I will just upload the console output and other things in detail tomorow morning..
_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
I have updated the details.. PLease check it now.. And help me please
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
_that said:
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
Click to expand...
Click to collapse
My phone is not bricked... Output of fastboot commmands in Command prompt have been already included in the post.. I have included the screenshots..
flash custom recoery and rom
if you by any chance downgraded the bootloader (fastboot flash motobot......) in your previous flash attempts there is a chance you have hard bricked your device.
and there is no point locking/unlocking bootloader (fastboot oem unlock/lock) once its unlocked. the only reason you are able to flash stuff you have is because the bootloader is unlocked. and i'm not sure how well you can lock a bootloader thats unlocked.
incase you have hard bricked your device refer; https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788

[Q] [HELP] Unable to succesfully install ANY recovery

After trying for over three hours, reading what seems like all threads on the whole of xda and some other sites... i am ready to eat my phone. Ok, must get myself together :-/ . Here we go.
Specs:
Moto G 4g on dutch carrier (vodafone), XT1039
Situation:
Came from completely stock lollipop system, then succesfully unlocked phone via motorola website using the fastboot proces. Intending to install custom rom, first need a recovery. I am now stuck at this step. When booting i now get a screen "warning bootloader unlocked" before the moto splash begins, this is normal as far as i understand.
Problem:
Unable to boot into recovery. Directly after flashing any recovery (with fastboot) and choosing "recovery" from the bootloader i get the message "boot up failed"
After restarting the phone and choosing "recovery" from the bootloader i get the android on its back picture stating "no command"
Already tried:
installed the android sdk, fastboot and mfastboot.
Am able to send commands to phone with (m)fastboot. Flashing works.
I flashed: openrecovery twrp 2850 xt1032, clockwork 6047 falcon, philz touch 6587 falcon, twrp 2870 falcon m stock, twrp 2801 titan v2 and twrp 2860 xt1032
all give exact same result
"fastboot boot NAME of IMAGE"
"fastboot erase userdata & cache"
"fastboot erase recovery"
did the above things in any imaginable combination
I hope someone has some fresh suggestions for me? Thanks for your time.
Bro as far as I know the recovery is not installed u should install twrp from this thread the one on the official site gave me soft brick
Now about the dead android with no command shows that you are on stock recovery and u have booted into it successfully to go further into stock u have to press power and volume up at the same time (like u lock ur phone) but it won't help in installing anything try the recovery I linked (first format your phone complete data and cache wipe from stock recovery not necessary actually) install it through fastboot command and let me know if it worked (with thanks button) BTW what's ur bl ver
thanks for your fast response faizxy, as stated i already tried the one from that thread (i did not use the identical interpunction to describe it but to be clear it is twrp-2.8.7.0.-falcon_M_STOCK.img)
Where do i find my bootloader version? It is the one that came with the device, factory issue...
Some extra info, that might anwser faiz' question: when i boot the bootloader it shows:
"AP Fastboot Flash Mode (S) 41.1A (sha-80481ae, 2015-04-10 14:30:28)
Hope you guys will forgive me for bumping a bit soon, but I really hope some one has a solution! Tomorrow I have time to tinker some more
Have you tried at least one recovery that is actually for your phone (peregrine)?
_that said:
Have you tried at least one recovery that is actually for your phone (peregrine)?
Click to expand...
Click to collapse
Ah. I guess not. Did not know that there where recovery's specifically for the peregrine/xt1039. I searched for "moto g" but apparently is wrong model. DOH!
Thanks for helping out! My problem is solved.
For future reference; finding working pergerine recovery was quite difficult; most mirrors are down. I found one here: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine and then under header "installing recovery.." under step 2 the download link (i avoid deeplinking)
This one seems to work for me. Now lets find a nice custom rom!
The ones listed here http://forum.xda-developers.com/moto-g/4g-development/progress-twrp-2-7-1-0-source-t2807585 dont work for me. One gives black screen, the other one shows an unlock slider which is unresponsive.
Hi,
Try this one... With encryption abilities or without, your choice...
http://forum.xda-developers.com/showthread.php?t=2996266

Trying to flash TRWP Moto Z recovery - not working

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!

Can't flash twrp

Hey. Following issue: I used to have my phone rooted and wanted to update it. Since I couldn't get a zip file from the official OnePlus webpage I used the download button from the system update and got it from there. Of course it also automatically removes your root so I had to try to flash twrp again. My bootloader is still unlocked (debugging and oem both activated) so that wasn't any issue. I got the newest enchilada and tried the flash boot command with the twrp enchilada image, however after a short message including hoot and and an ok at the end my phone goes into the fastboot icon and is stuck there until I restart it. Twrp doesn't start whatsoever. I also tried the fastboot --set-active= command but that didn't help as well. Adb is also on the newest version and I also got the newest enchilada. Any ideas?
P.S: already searched a lot on the forum but none of the aforementioned solutions did anything thanks for any help regardlessly
Gosick1337 said:
Hey. Following issue: I used to have my phone rooted and wanted to update it. Since I couldn't get a zip file from the official OnePlus webpage I used the download button from the system update and got it from there. Of course it also automatically removes your root so I had to try to flash twrp again. My bootloader is still unlocked (debugging and oem both activated) so that wasn't any issue. I got the newest enchilada and tried the flash boot command with the twrp enchilada image, however after a short message including hoot and and an ok at the end my phone goes into the fastboot icon and is stuck there until I restart it. Twrp doesn't start whatsoever. I also tried the fastboot --set-active= command but that didn't help as well. Adb is also on the newest version and I also got the newest enchilada. Any ideas?
P.S: already searched a lot on the forum but none of the aforementioned solutions did anything thanks for any help regardlessly
Click to expand...
Click to collapse
What version rom is currently installed
MrSteelX said:
What version rom is currently installed
Click to expand...
Click to collapse
Oxygenos 10.3.0 on my oneplus6.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 has everything you need to install twrp

Categories

Resources