Database Users

[Q] flashing cwm recovery

I have flashed skrilax v8 unlocked BL with v8pubA50 recovery
I flashed it using blackthund3r ATX flashtool
My question is
1. Why I can't enter boot recovery, it's just show green robot with exclamation at its body
2. How I can flash cwm recovery since it's extension is .Img
(fyi). I use UNroot A501 with stock HC 3.2.1
Thanks
Sent from my A501 using xda app-developers app

Help help :'(

gigacats said:
Help help :'(
Click to expand...
Click to collapse
IF you are sure you have the v8 bootloader installed, you should be able to install a recovery.
You must have an ICS rom installed, or on the Ext SD card, have an ICS rom ready to flash.
If you currently have a stock ICS rom installed, then you need to be rooted, and delete the "boot recovery" file (or similar name). Or else when you boot your tab, the custom recovery gets overwritten.
You can look at Civato's Bootloader and Recovery guide for the exact name of the file.
Note that v8 bootloader and ICS recoveries, DO NOT work well with HC based roms. You must have an ICS Rom.
MD

I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app

gigacats said:
I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
View attachment 1218774
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
1) the robot is the 'stock recovery.img'
2) you must be rooted before you can flash 'anything'
3) The only way to do this (on HC) is by installing a custom pre-rooted rom
4) If you want ICS your tab should update itself, you will need acer enhancement app from the market. then Settings>About Tablet>System Update
5) you can install a stock or custom ICS rom BUT you must have root to update to the patched bootloader which some of the custom roms require.
6) you cannot "open" recovery.img.

Ok, so please stop posting the same issue in other threads, or you will never get your problem solved.
Now. You say you have Skirlax_cz's V8 bootloader installed. Correct? If so, you should be able to boot into the menu system of it (vol+ and PWR). If you get the bootloader menu, good.
Now, you will need the Android SDK (google it and download and install it). After installation, go to c:\windows\program files (x86)\android\android-sdk\platform-tools. Open a command window here. (it may be installed in program files)
Boot your tablet like I described above, and at the bootloader menu, select "fastboot". The tablet should say fastboot mode.
Now, copy your recovery.img (or whatever you named it) into the platform tools folder on your PC. It has to be in the same folder as fastboot.exe
Now, make sure you have the rom you want to install on your EXT SD Card.
Next, plug in your tab to the USB (I always make sure in device manager that the tab is recognized as a fastboot device)
In the command window you opened earlier, type in the following;
fastboot flash recovery recovery.img
Remember, if your recovery image is named "public-recovery.img" for example, that is what you should type in the command above.
Once the recovery is successfully flashed, then turn tab off.
Unplug from USB
Hold PWR and Vol- untill you see the message "booting recovery kernel", then release both. You should boot into the custom recovery now. Then you can do your wipes and stuff as per the rom install instructions.
Of course, this is ONLY if you have the V8 bootloader running.
Also, I posted a better rom. Evil Alex Unleashed, so you should install this. It has problems fixed.
MD

OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts

gigacats said:
OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts
Click to expand...
Click to collapse
Wow! It worked!!!!!!!!!!!!
Damn, better than I thought.
Gotta love Skirlax_CZ and putting flashboot in the bootloader v8. Throw a thanks at him when you get the chance please. And if you used EZTerry's public recovery, please throw a thanks at him also. And anybody else who helps you. That's how it works here.
I hope you installed Evil Alex. She's much better than Alex V. Alex V is a good girl, but she need the wakelock app from the market. Evil Alex hopefully does not. After all, these are Acer leaks. AKA "beta". So we really don't know what to expect. And things "will" change in the next month, and new builds "will" be released.
Am glad you got it running.
And Dibbs, throw a thanks to him also His instructions were after all, correct (he didn't know your V8 was working).
Any issues, please put them in my rom thread.
MD

[Q] Problem with my A500

Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...

Vipe.teo said:
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Click to expand...
Click to collapse
You need to unlock your bootloader and flash a recovery

blackthund3r said:
You need to unlock your bootloader and flash a recovery
Click to expand...
Click to collapse
Thanks for your reply, can you recommend threads to teach me how to go about doing it?
I believe Mlopik page did mention if I follow correctly, I would have already unlocked my bootloader, am I right?

First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD

Moscow Desire said:
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Click to expand...
Click to collapse
Hi, thanks for coming to my aid, sorry for PM-ing U asking for help.... but I'm a super noob for this....:silly:
1) I have a boot screen by Skrilax_cz, but how do I fastboot a CWM recovery via a command prompt window?
2) A few min ago, I tried to use AfterOTA it got stuck at [3/4 flashing recovery] for a long time..... (Force restart)
3) I saw a solution <Click Here> then after downloading the recovery.img and running the code... It say done but after i restart nothing happen.
4) I continue using AfterOTA, again it got stuck at [3/4 flashing recovery] for a long time.....(Force restart)
I out of option....

erm... Help ???

Use fastboot to do a complete wipe.
Run ICSROOT. Zip to get rid of the boot.p file.
Reflash the v8 and cwm using apxflash tool
Boot straight to cwm and flash yr rom.
Do not use any type of rom manager apps to flash roms
Sent from my GT-I9300 using Tapatalk 2

FIXED !!!
Yeah !!! Got It to work !!!
Big THANKS to all who have help and spend time answering my noob questions...
THANK !!!!

LG Spirit H440n general thread

Welcome to the general thread for LG Spirit H440n/H420 and it's other variants.
Feel free to share any information you have about this device. I will include everything important at the op.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifications
You can find LG Spirit specs here.
USB Drivers:
You can find drivers for your device through LG mobile support tool.
Also, there are the universal LG USB drivers.
Stock kdz files
You can find the stock firmware for LG Spirit variants here.
Root
You can root any Lollipop version with KingRoot.
Here is how to replace KingRoot with SuperSU.
You can root any version (Lollipop or Marshmallow) by unlocking the bootloader and installing a custom recovery first.
Bootloader Unlock
You can unlock the H440n bootloader with the method provided here.
For unlocking the H420/H422 bootloader (patched uboot) refer to the Notes section of this post.
Custom Recoveries
CWM H440n
TWRP H440n thread, maintained by @Fobos531
Refer to the Notes section of this post for H420/H422 custom recovery flashing.
Notes
Note1: You can install the Lollipop kdz files with LG Flash Tool. Also, here are some details on how to install the Marshmallow kdz.
Note2: LG Spirit source code can be found here.
Note3: It seems that in order to use ADB you have to set the USB connection type to:
1. MTP in windows
2. PTP in linux
Note4: LG H422 users, find everything about your device in detail here (4pda thread) and here (xda thread). You can find infromation on how to unlock the bootloader (uboot patch), root, flash a custom recovery and stock or custom roms.

screen on
hello there, just bought this phone. It's fine. But why doesn't it switch the screen on when a notification arrive? do you have any solution or suggestion? thanks!

giamanto said:
hello there, just bought this phone. It's fine. But why doesn't it switch the screen on when a notification arrive? do you have any solution or suggestion? thanks!
Click to expand...
Click to collapse
Hello. You' re right I notice it too. I think you can try the app "Screen notifications" from the Play Store but I haven't tested it yet.

polfrank said:
Note 4: It seems like our device's source code can be found here: http://opensource.lge.com/osSch/list?types=ALL&search=h440 (Correct me if I'm wrong). I wish I knew how to build Cyanogenmod..
Click to expand...
Click to collapse
I'll check it out when I get to my work computer. No linux at home...
At least CWM Recovery would be nice to have.
Edit:
http://pastebin.com/06QGsZgh

polfrank said:
Hello. You' re right I notice it too. I think you can try the app "Screen notifications" from the Play Store but I haven't tested it yet.
Click to expand...
Click to collapse
thank you! it works PERFECTLY!

If I have done everything right, I have extracted the kdz file (T-mobile Croatia) and here we have recovery.img and boot.img attached to this post!
I post them because someone may be able to build CWM recovery for us, so I would like to make his life easier if he decides to do so.

polfrank said:
If I have done everything right, I have extracted the kdz file (T-mobile Croatia) and here we have recovery.img and boot.img attached to this post!
I post them because someone may be able to build CWM recovery for us, so I would like to make his life easier if he decides to do so.
Click to expand...
Click to collapse
Buddy you are my hero! Now I can get some stuff done with syncing CM12 sources to build CWM and after that hopefully TWRP with one buddy from BUG Forums. For now on, priority is CWM and hopefully CM12(.1 is optional). I tested out with extracting boot.img and recovery.img directly from phone and didn't had success with it (failed to do some stuff with creating .mk files for phone).
Also thanks to OP for .kdz file, it shall work on any other network because it is very much clean ROM (Croatian T-Mobile, only have few apps which can be uninstalled without root).
Peace from owner which had this phone rooted.

midzan21 said:
Buddy you are my hero! Now I can get some stuff done with syncing CM12 sources to build CWM and after that hopefully TWRP with one buddy from BUG Forums. For now on, priority is CWM and hopefully CM12(.1 is optional). I tested out with extracting boot.img and recovery.img directly from phone and didn't had success with it (failed to do some stuff with creating .mk files for phone).
Also thanks to OP for .kdz file, it shall work on any other network because it is very much clean ROM (Croatian T-Mobile, only have few apps which can be uninstalled without root).
Peace from owner which had this phone rooted.
Click to expand...
Click to collapse
Nice! If you compile a working cwm for a start, YOU are a hero! Feel free to ask for anything else I can do to help you with (but I know only little stuff).
I just want to mention that the thanks for the .kdz file goes to the guys I mention at the credits!

Seems that bootloader is locked. Fastboot oem unlock didn't work and didn't have luck with loki or bump either.

manakeri said:
Seems that bootloader is locked. Fastboot oem unlock didn't work and didn't have luck with loki or bump either.
Click to expand...
Click to collapse
You mean you wanted to flash recovery and the locked bootloader prevented you? If this is the case try the app "flashify" from Play Store.
If you just mention it, well, it's good to know. :good:

I flashed the recovery, that's not the problem, booting into it is.
Someone else with more experience about unlocking bootloaders (and time) could have a try.
I'll upload the CM device files to the github tomorrow.

manakeri said:
I flashed the recovery, that's not the problem, booting into it is.
Someone else with more experience about unlocking bootloaders (and time) could have a try.
I'll upload the CM device files to the github tomorrow.
Click to expand...
Click to collapse
Actually there isn't problem with booting in recovery you just need to do this button combination
Power + vol down and when lg logo apears press combination again
This is how LG G3 goes to recovery and it should work here too
Edit: I should upload also CM device files and kernel to my github next week at collège so we should have all files on one github

You can reboot to recovery with apps that offer an advanceed reboot menu, too. Like Link2sd.
Though, I don't know if @manakeri is talking about something else like: try boot to recovery but the locked bootloader prevents you..

polfrank said:
Though, I don't know if @manakeri is talking about something else like: try boot to recovery but the locked bootloader prevents you..
Click to expand...
Click to collapse
Exactly that. There is verification that the recovery's certificate matches original or something like that.

Here is new firmwares
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW79RCO032ESAYF6BB4BMEM/H440n10e_00.kdz - LG H440N 10E HUNGARY
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW48UI40323XARJB234BLAO/H440n10b_00.kdz - LG H440N 10B Poland PLUS

Well seems that our bootloader isn't locked if I look via this app. Would give a try with CWM (currently building up from stratch, need some time to compile it) and see would it boot up somehow (key combo and this app)

http://www.mediafire.com/download/51nnmacvkqm5df9/recovery.img

manakeri said:
http://www.mediafire.com/download/51nnmacvkqm5df9/recovery.img
Click to expand...
Click to collapse
That is CWM you built or it is TWRP?

CWM

Working? How instaled this?

Thread closed

Install CM14 for OnePlus X (The Unofficial)
** How to Install TWRP for the 3.1.0 version you installed Oxygen.
B1: Starting Fastboot mode by turning off the power on. Then hold down + to the source.
Step 2: Install the driver and connect to the computer (HD drivers installed on the network to find it)
B3: Run cmd (run -> cmd) command fastboot boot attachments and enter this download Mod edit link removed
B4: boot into TWRP Self.
** The Stock 2.2.2 ROM you are using the network attempt to open up the OEM and then down Flashfy unbootloader install TWRP on CM ROMs directly or similar 13 and then into TWRP always offline.
** Note: Back up your data before doing us avoid errors arising restore offline.
** Download ROM CM 14: Mod edit link removed
** Link Download Grapps:Mod edit link removed
** Conducted into TWRP and wipe data, cache partitioning, Dalvik Cache. Flash ROM + Grapps and restart.
This is an experiment with me what errors arise not responsible. For those you love to dabble and discourage those you do not know and do not understand anything. People are already getting a bit bored Android does not dabble to dabble like new. : D
Path: Mod edit link removed
Vietnamses : Mod edit link removed

downloading, will report back soon.

Cam on
Thanks much

Post some screenshots.

failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too

Well, this is interesting.. The step-by-step guide is a bit confusing though. I will download and try the 'ol good method of flashing ROM, gapps and supersu. Hope it works!

namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app

be_are said:
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
here you go: https://drive.google.com/file/d/0B_Km0FbYnea1aDdIaTEydElhUkk/view?usp=sharing

twrp has not made it to 3 ox you have to use a downgrade to get a fresh start using unbrick method, (keep flashable backup via flashify) get twrp installed with the new (old) boot loader, flash cm14+ext. and you are done.
if you had cm13 or the likes, please confirm if you CAN upgrade to 14 before ox people start trying to install without knowing if it even has android 6 (last update i saw on the branch was from june 7 so idk)
teamwin does not have twrp for the ox 3 on oneplus x yet (on their releases anyway) so you have to follow some other process to downgrade to a twrp'able os (and a backup) before trying yo install this
if i see any info from people who have been able to update (and if it has android 7) i'll try to make a video on the process (in white, Texan english)

Please remove this page.

namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.

ksigit said:
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.
Click to expand...
Click to collapse
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

namquang93 said:
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
Click to expand...
Click to collapse
Looks like a successful install to me. Could you provide twrp logs?

With whose permission did you post this build here ? Don't you think there was a reason that even after a complete build of CM14 it was still not posted to the forums ?
I am asking you, as politely as possible, to remove the links and this fake procedure, when N is ready, it will be shared, you might find phony builds or legit but non working ones on the interweebz, that doesn't mean it gives you the right to share it just because you think its cool, because its not.
Take it down.
EDIT: Sure, if you build yourself and want to share it then you're more than welcome.

And then they will cry if things are broken !! Take it down folk !
Sent from my ONE E1003 using XDA-Developers mobile app

This Build was just a test build, what made u think that i will not post it here on xda if the rom booted? We, the team are working to make it work but yeah dont post the builds from afh here, will update u all for sure when its done. I think it was my mistake to not to make that build private. -_-

It flashes successfully but doesn't boot, goes back into recovery. Still, great work.

congrats for succesfull starter build
hats off !!!!! to you guys ([/B]developers off this rom) :good:

Flashed with/without gapps. Doesn't boot - goes back 2 recovery

foster095 said:
Flashed with/without gapps. Doesn't boot - goes back 2 recovery
Click to expand...
Click to collapse
Kindly refer to the developer's post, POST #16

[Recoveries]TWRP Recovery For Meizu M2 Mini

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Requirements
Root+Bootloader Unlocked
Flashing Instructions
After Unlocking Bootloader (If you dont know how to do it then go here)
[url]https://forum.xda-developers.com/meizu-m2-mini/how-to/guide-unlock-bootloaderinstall-twrp-t3390799[/URL]
Enter In fastboot.Then type.
"fastboot flash recovery recovery.img"
wait a minute turn off the phone. and enter recovery (Power + vol up until vibration)you'll Be in TWRP
Download Links
Old Recovery Version 2.8
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlMXd3YzJhTnUxeVU[/URL]
Mid Recovery 3.10 Latest
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlYnpCaXhSOUxjX0E[/URL]
New Recovery 3.1.1
[url]https://drive.google.com/file/d/0Bz6Fq2POoJTlRjh4ZkppWUJ4Qm8/view?usp=drivesdk[/URL]
Latest Recovery 3.2.1
[url]https://drive.google.com/file/d/1ftYtD2Tm0MdKBv_ZtVQHGJEcCuflb6Oe/view?usp=drivesdk[/URL]
Don't Forget To Press Thanks if you like it :good: :good:
Regards~
Murtaza Piplod

what's news bro?

ADIB27 said:
what's news bro?
Click to expand...
Click to collapse
updated with latest features of the latest recovery released by TWRP read changelogs at there TWRP site

heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.

maxisgsm said:
heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.
Click to expand...
Click to collapse
Try clear dalvik and cache.

adarshm4you said:
Try clear dalvik and cache.
Click to expand...
Click to collapse
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......

maxisgsm said:
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......
Click to expand...
Click to collapse
I think there will be some mess in installed os reflash it after taking a backup.

adarshm4you said:
I think there will be some mess in installed os reflash it after taking a backup.
Click to expand...
Click to collapse
my phone hang while i do a format storage.

maxisgsm said:
my phone hang while i do a format storage.
Click to expand...
Click to collapse
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.

adarshm4you said:
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.
Click to expand...
Click to collapse
every time the phone boot into twrp, it only go back to last state and keep fail then reboot...... it will cycle until battery die. i cannot go anywhere in twrp .....
now i at fastboot state, when i try to flash stock rom, it gave me the error
G:\adbFire>fastboot flash update update_8.zip
sending 'update' (1115283 KB)...
OKAY [ 88.153s]
writing 'update'...
FAILED (remote: partition table doesn't exist)
finished. total time: 88.237s

Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:

adarshm4you said:
Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:
Click to expand...
Click to collapse
adb cannot detect my devices ..... if i not mistake, last time i unlcock my OnePlus one without any problem, and adb can detect my phone,
now cannot detect ....

@murtaza1326
TWRP 3.2.1.0 is out!
Update the post

rushiranpise said:
@murtaza1326
TWRP 3.2.1.0 is out!
Update the post
Click to expand...
Click to collapse
post updated new latest 3.2.1 TWRP is added @Dinolek TWRP is alread there in his post so I don't think i should repost it here ??
Regards~

how to recovery install meizu m2 mini flyme 6.2.0.0g

thanks sir.. i wanna install this twrp

Pretty good!