Database Develop

TWRP .img from phone?

I've recently dumped my desktop. I'm using my company's laptop despite of being very restricted.
So... because of this, i can't use adb or moto x toolkit to install TWRP. I had it installed on my phone but somehow i've messed it up. I've an unlocked bootloader, and my phone is rooted. Now i have only the .img file and no way to install it. I've tested some apps from the store, but none of them work.
Any way to install TWRP .img file from the phone itself?

pintasmapila said:
I've recently dumped my desktop. I'm using my company's laptop despite of being very restricted.
So... because of this, i can't use adb or moto x toolkit to install TWRP. I had it installed on my phone but somehow i've messed it up. I've an unlocked bootloader, and my phone is rooted. Now i have only the .img file and no way to install it. I've tested some apps from the store, but none of them work.
Any way to install TWRP .img file from the phone itself?
Click to expand...
Click to collapse
Since you say you are already rooted, try FLASHIFY from the market. It should flash TWRP Recovery for you (assuming you are indeed rooted already).
Good Luck.

if you can install the moto device drivers on the PC, you can then try to download and unzip this -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip and try mfastboot from there.

samwathegreat said:
Since you say you are already rooted, try FLASHIFY from the market. It should flash TWRP Recovery for you (assuming you are indeed rooted already).
Good Luck.
Click to expand...
Click to collapse
Thanks for your help. Tried it but it doesn't work.
KidJoe said:
if you can install the moto device drivers on the PC, you can then try to download and unzip this -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip and try mfastboot from there.
Click to expand...
Click to collapse
I can't install drivers on a restricted pc. That's my main problem.

pintasmapila said:
Thanks for your help. Tried it but it doesn't work.
I can't install drivers on a restricted pc. That's my main problem.
Click to expand...
Click to collapse
Bummer.
No one has made a flashable zip for TWRP for Moto X yet....mostly because fastboot is so much easier. In the past (on other devices), you could often flash the recovery zip file from the bootloader - this would make fastboot unnecessary.
Since we don't have a flashable zip (only the .img), I can only suggest that you use a different computer that isn't restricted. Sorry, but it seems that will be your only option.
And lastly, when you DO find a computer that you're able to use, be sure to flash the recovery with 'mfastboot' and not the standard 'fastboot'.

samwathegreat said:
Bummer.
No one has made a flashable zip for TWRP for Moto X yet....mostly because fastboot is so much easier. In the past (on other devices), you could often flash the recovery zip file from the bootloader - this would make fastboot unnecessary.
Since we don't have a flashable zip (only the .img), I can only suggest that you use a different computer that isn't restricted. Sorry, but it seems that will be your only option.
And lastly, when you DO find a computer that you're able to use, be sure to flash the recovery with 'mfastboot' and not the standard 'fastboot'.
Click to expand...
Click to collapse
Yeah, i guess you're right.
Thanks man

Revert to stock after MOFO Root

To revert completely back to stock
The rootjunkysdl website. http://rootjunkysdl.com/?device=Droid Turbo&folder=Firmware
It's in the firmware section for the Droid Turbo
Download it, unzip it, run the .bat file while in fastboot mode, wait for the magic.

kevinmr82 said:
To revert completely back to stock
The rootjunkysdl website. http://rootjunkysdl.com/?device=Droid Turbo&folder=Firmware
It's in the firmware section for the Droid Turbo
Download it, unzip it, run the .bat file while in fastboot mode, wait for the magic.
Click to expand...
Click to collapse
Thanks, what firmware does this flash? It shows "21.128-15" in the file name so I am just wondering. The latest is 21.44.12.quark_verizon.en.us.

21.21.15 The original firmware from the October, 2014 release

kevinmr82 said:
21.21.15 The original firmware from the October, 2014 release
Click to expand...
Click to collapse
Oh yeah, thanks! I just downloaded it and opened it up. This will flash literally everything from radios to the bootloader to system. Thanks now I have it just in case.
Edit: bootloader stays modified...

where can i find 21.44.12?
Edit: do i flash through rsdlite or mofo?

I have been unable to find that version myself. You don't use RSD or MOFO. After you unzip the file look for the .bat file. Put your phone in recovery mode and open the .bat file. It will flash on its own.

kevinmr82 said:
I have been unable to find that version myself. You don't use RSD or MOFO. After you unzip the file look for the .bat file. Put your phone in recovery mode and open the .bat file. It will flash on its own.
Click to expand...
Click to collapse
Thanks for the reply... I actually messed up my recovery file so I couldnt go that route... luckily it was easy as fastboot flash recovery recovery.img after getting the correct file

Is there any way to get an unrooted system.img to flash with mofo? I'm trying to 'unroot' my phone and keep the modifications I have made, so I can continue using the apps that don't allow me to use them when I'm rooted (Barclays Mobile Banking and Pingit)

That I'm unsure of, have you tried any of the root cloaking apps in the Play Store?

kevinmr82 said:
That I'm unsure of, have you tried any of the root cloaking apps in the Play Store?
Click to expand...
Click to collapse
Yes, they don't work. I tried removing su and superuser.apk, but still no luck. It won't probably work, but I'd like to try, see the differences between a rooted and an unrooted system.img, also see if these apps work on a 'flashed' system.img that is unrooted...
I'll keep trying to convert the system.img_sparsechunk* from the stock rom into a mofo flashable system.img... If I can't do it then I'll open a thread asking for a dd from an unrooted system partition

Unable to boot into recovery unless I flash TWRP into "boot"...

Hello!
I rooted my phone early on in it's lifetime, but lost the DRM keys right away (didn't check that TA-Backup actually backed the keys before I rooted).
Then, at some point, I flashed a stock ROM (5.0 or something) and have been using that for a year or so now.
Now I decided I wanted Marshmallow, so I followed this guide since I've already lost my DRM key.
First question: Am I wrong to assume that I can follow this less complicated guide if I've lost the key, instead of flashing the older ROM and using the exploit as this guide suggests?
So I flashed the .291 FW on my Z3 Compact (D5803 as I'm from Sweden), locked the bootloader, started it up (the guide says to update to the latest, but since this is the latest FW there are only app-updates, correct?), put the "SuperSU 2.76" and "THSxEXR DRM Fix" in the internal storage, unlocked bootloader.
(I also put the xposed-v86 zip there too, but I'm unsure what that one actually does and if I need it so I probably won't install it)
So far so good, correct?
Now, I downloaded the latest TWRP, 3.0.2 for z3c, and renamed it to recovery.img.
And I've tried every combination here:
fastboot flash recovery recovery.img
fastboot boot recovery.img
and also
fastboot flash boot recovery.img
The top two does not work, it seems. When I boot into recovery, I simply get a black screen (with backlight, as if the screen was on) and nothing else.
But, if I flash "boot" with recovery.img, I am able to access TWRP. Ofcourse, I'm not able to boot normally at this point but it seems weird to me.
Any help here?

Fooughhy said:
Any help here?
Click to expand...
Click to collapse
Have you tried Flashfire. It can flash roms and zips without recovery

No, but since I can't get into recovery, I can't flash SuperSU and get root. And from what I can tell, Flashfire requires root access.

Try flashing it to FOTAKernel using fastboot

No, I haven't. The website seems a bit confusing to me and I can't seem to figure out what to download...
But all files seem to be recovery.img, so am I supposed to simply flash recovery with that image?
I downloaded from the hammerhead folder, as from a quick glance that seemed to newest recovery release of twrp on that site. But "sirius" seems to be the actual newest. Do you know what I should download?
In this thread, the OP expects you to know how to do things, but gives a basic example of the ADB commands. Can I use those commands?
As you can see, I'm quite inexperienced with this bit I'd like to learn!

Hello,
i'm having a similar issue. I upgraded to MM, flashed Kernel 575, installed TWRP, installed SuperSU and Xposed, flashed back kernel 291 and everything works fine (still have my DRM keys). Only it is impossible to boot to recovery. Only once right after the installation it went to TWRP.
Since I haven't found any other information on this and this is the only case where someone has the same problem AND installed xposed-v86... could it be related to xposed?

Fooughhy said:
No, I haven't. The website seems a bit confusing to me and I can't seem to figure out what to download...
But all files seem to be recovery.img, so am I supposed to simply flash recovery with that image?
I downloaded from the hammerhead folder, as from a quick glance that seemed to newest recovery release of twrp on that site. But "sirius" seems to be the actual newest. Do you know what I should download?
In this thread, the OP expects you to know how to do things, but gives a basic example of the ADB commands. Can I use those commands?
As you can see, I'm quite inexperienced with this bit I'd like to learn!
Click to expand...
Click to collapse
Hammerhead? Isn't that the codename for the Nexus 5?
As well the codename for the Z3c is Aries

AFAIK "hammerhead" is the codename for Nexus 5X not for Z3C which is Aries. It seems you may have downloaded a wrong version of TWRP which might be the reason for you to get a black screen when you boot into TWRP. After you download the correct version of the TWRP and renaming it to "recovery.img", try doing this through ADB:
fastboot flash recovery recovery.img
fastboot reboot recovery
It should boot into TWRP.
EDIT: Also you have followed the procedure for the "CONCEPT ROM", not the Stock one. .291 is Stock Marshmallow, while the link you provided directs us to the Concept unlocking etc.

marshalpear said:
AFAIK "hammerhead" is the codename for Nexus 5X not for Z3C which is Aries. It seems you may have downloaded a wrong version of TWRP which might be the reason for you to get a black screen when you boot into TWRP. After you download the correct version of the TWRP and renaming it to "recovery.img", try doing this through ADB:
fastboot flash recovery recovery.img
fastboot reboot recovery
It should boot into TWRP.
EDIT: Also you have followed the procedure for the "CONCEPT ROM", not the Stock one. .291 is Stock Marshmallow, while the link you provided directs us to the Concept unlocking etc.
Click to expand...
Click to collapse
Hammerhead is actually Nexus 5, but nevertheless that doesn't change the fact that he downloaded wrong one Or did he? In OP he wrote he downloaded TWRP for z3c so I assume that it was the correct one. But I'm just not sure that it's as simple as that to flash TWRP and root device with LB without any extra step before or in between.
Seeing that he already lost TA partition, it would be much easier to go with UBL and loading TWRP/rooting. I don't understand the re-locking part But then again, he indeed followed the wrong thread

How to Flash 6.0.1 MM

can someone give me steps or link how to flash MM?
I am on 6.0.1 without twrp and just want to factory flash image
thanks

fromgeorgia said:
How to Flash 6.0.1 MM
can someone give me steps or link how to flash MM?
I am on 6.0.1 without twrp and just want to factory flash image
thanks
Click to expand...
Click to collapse
You are already on 6.0.1 Marshmallow. You said it yourself. You said you even still have stock recovery. So, seems like you don't need to do anything?
Maybe you wrote something wrong or left something out? Please clarify, and we'll be glad to help if we can.

ChazzMatt said:
You are already on 6.0.1 Marshmallow. You said it yourself. You said you even still have stock recovery. So, seems like you don't need to do anything?
Maybe you wrote something wrong or left something out? Please clarify, and we'll be glad to help if we can.
Click to expand...
Click to collapse
you are right i am, but phone crashes and when receiving phone calls and restarts sometimes so i want to try to reflash it. thanks

fromgeorgia said:
you are right i am, but phone crashes and when receiving phone calls and restarts sometimes so i want to try to reflash it. thanks
Click to expand...
Click to collapse
OK, then you need to flash this via RSDLite or ADB.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
You can google how to download/use RSDLite or ADB. But that's the most recent stock firmware you need to flash with either of those tools.

ChazzMatt said:
OK, then you need to flash this via RSDLite or ADB.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
You can google how to download/use RSDLite or ADB. But that's the most recent stock firmware you need to flash with either of those tools.
Click to expand...
Click to collapse
i've tried RSDLite but it was unable to detect the phone(drivers was right and phone was in recovery).
i will try ADB than. with ADB should i flash every partition manually?

fromgeorgia said:
i've tried RSDLite but it was unable to detect the phone(drivers was right and phone was in recovery).
i will try ADB than. with ADB should i flash every partition manually?
Click to expand...
Click to collapse
As far as I know you need to be on the bootloader screen, not recovery screen. Maybe that was your problem? RSDLite just automates a bunch of stuff ADB does.
Also, sometimes you need to use msfastboot instead of fastboot commands. I sort of remember why, but I don't want to state anything incorrectly. But try msfastboot if fastboot doesn't work.
For ROMs I use TWRP, so I'm not an ADB expert -- but I have used it. However, it's been over two years since I've had to flash a full firmware image via ADB (but I have flashed individual elements since then like modems, boot logos, etc.), so I'm just going to say yes flash every partition manually.

ChazzMatt said:
As far as I know you need to be on the bootloader screen, not recovery screen. Maybe that was your problem? RSDLite just automates a bunch of stuff ADB does.
Also, sometimes you need to use msfastboot instead of fastboot commands. I sort of remember why, but I don't want to state anything incorrectly. But try msfastboot if fastboot doesn't work.
It's been over two years since I've had to flash a full firmware image via ADB (but I have flashed individual elements since then), so I'm just going to say yes flash every partition manually.
Click to expand...
Click to collapse
thanks you're good man :good::laugh:

Deleted OS

Hey guys,
I was trying to unlock my phone and install a custom ROM so I installed TWRP and everything was going smooth until I tried installing a custom ROM. In TWRP I hit "Install" and click the zip file for the ROM I want (PureNexus) and it says "Invalid zip file format! Error installing zip file '/sdcard/PureNexus.zip"
Does anyone know what the problem is? I can't figure this out. This is the first time I'm doing anything from the bootloader so I'm a bit of a newb. I would be fine going back to stock everything if it means my phone will turn on. I tried installing the official image from google (7.1.1) and I get the same zip error.
So where I'm at is I do not have an OS installed on but I do have access to TWRP. In the command prompt on my desktop it recognizes my phone when I type 'adb devices' but it doesn't do anything when I type 'fastboot devices'.
Any help is greatly appreciated. I'm scared.

Okay, so I figured out what fastboot was and I was able to install Google's 7.1.1 stock image using the command prompt. I was freaking out for a few hours and even though I didn't get the custom ROM I wanted I'm really happy I didn't brick my phone. I've never done anything like this on my phone so it was a fun learning experience
I'm still curious what I did wrong and why TWRP couldn't unzip any of the zip files (PureNexus, Google Stock, etc). If anyone knows I'm still interested in learning what I did wrong.

Unheard7 said:
... why TWRP couldn't unzip any of the zip files (PureNexus, Google Stock, etc).....
Click to expand...
Click to collapse
TWRP: wrong version or damaged;
ZIP: damaged or incomplete download.
Latest version TWRP is 3.2.1.0.

NLBeev said:
TWRP: wrong version or damaged;
ZIP: damaged or incomplete download.
Latest version TWRP is 3.2.1.0.
Click to expand...
Click to collapse
Yes, and the Google factory image isn't meant to be flashed that way. I guess the Google OTA image might be flashed from TWRP, but I haven't tried it.

TWRP will flash an image (. img) file if you set it to by tapping the img button. If you don't have that set and try to flash an image it will error. If you have it set to img and try to flash a zip it will also error.

1. Unlock the bootloader.
2. Install the latest TWRP recovery.
3. Wipe.
4. Install the required ROM.
To go back to stock firmware, just download the relevant factory firmware zip, extract it and run the script. I think a readme file is provided in the zip explaining how to go about it.
Cheers! Happy New Year!