How to flash cm13 with fp scanner version (both official/unofficial)
Requirements:
- TWRP Alka (Download here, just extract the .img and flash it via your current TWRP )
1. BACKUP!BACKUP!BACKUP!!
Before Flashing anything to your device, we need to backup our full ROM. This can be done by using the TWRP Alka i gave you. steps are in the following:
- Boot Into TWRP
- Go to Backup
- check all the partitions you have (see below)
{
"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"
}
- backup all and wait until its finished (approx 5-10 mins)
For safety purpose store the backup in sdcard or have a copy of it in your PC
2. FLASHING
CAUTION! THIS WILL RELOCK YOUR BOOTLOADER ( Irrespective of if you unlocked officially or unofficially in stock ROM it will get locked and flashing this ROM won't brick your phone or cause bootloops) TWRP will still continue to function normally with all its functions
okay now that we have already backed up all our partitions, we can flash the rom.
- go back to TWRP Main screen (suggesting that you didnt reboot after backing up) and chose Wipe
- Wipe system, Dalvik, Cache, Data
- after its done, go back to TWRP main screen.
- Install the ROM
- Install GAPPS (6.0.1 arm64)
- Reboot.
First boot takes around 5 minutes and it'll initially welcome you in the setup screen.
3. RE-UNLOCKING
Now you know that your Bootloader got relocked. But that's fine, even at a LOCKED state, your TWRP is still functioning as it should be (flashing, restoring, backup, wipe).
So its up to you if you want to unlock or not. Both options are fine and wont affect you in any way.
To unlock your bootloader you have to:
- Boot into Fastboot
- Reunlock Using MiUnlockTool
- reboot.
4. RESTORING to MIUI lollipop or older cm13 builds
if you encounter problems with the rom (stuffs doesnt work, something FC, not a daily use worthy) you can easily go back to where you were before flashing this build.
- Boot into TWRP
- Tap Restore
- check all the partitions and restore
- wait until it finished and reboot.
you should now be in your previous rom (whether its MIUI or AOSP or CM) and the bootloader should've stayed unlock.
Reserved
reserved
Thanks for the tuto. Can we flash miui roms without flashing patched boot.img or else with this recovery ?
the next updates of CM lock bootloader or one-time?
Enviado desde mi XRN3P.
Great tutorial!
One question, I converted my SD to be internal (big mistake). Is there a way for twrp to see the SD and back stuff there?
Or otherwise revert back to external without losing all the data?
Sent from my Redmi Note 3 using Tapatalk
Great! I wanna install this asap!!!
Enviado desde mi Redmi Note 3 mediante Tapatalk
ASAP, for sure! Thanks for your work, Santosh!
There's no emmc-backup in the list in twrp, I flashed the twrp mentioned in op, what's wrong?
Edit: Here's a screenshot, there are a lot things to backup, but no emmc
https://app.box.com/s/mitdohqzvyfql6yf6s3ma8ig24um7ecq
Thank's for guide, working perfect, after full restore I have unlocked bootloader. I had go back to MIUI, there still is no sim card bug for me if in slots is only one SIM and is no trigger to turn off one of them, also camera is working really bad, even colours are bad yelow/black when trying to do a shot.
Sent from my Redmi Note 3 using Tapatalk
Great Job!
Enviado desde mi Redmi Note 3 mediante Tapatalk
Try it or die said:
There's no emmc-backup in the list in twrp, I flashed the twrp mentioned in op, what's wrong?
Edit: Here's a screenshot, there are a lot things to backup, but no emmc
https://app.box.com/s/mitdohqzvyfql6yf6s3ma8ig24um7ecq
Click to expand...
Click to collapse
Facing the same problem. There are a ton of things to backup, yet no EMMC backup. Not sure what's wrong here. Flashed your TWRP via the one I already had and now getting this.
Cristal clear. Eating release to flash. Thanks to dev
Enviado desde mi Redmi Note 3 mediante Tapatalk
nadavar said:
Great tutorial!
One question, I converted my SD to be internal (big mistake). Is there a way for twrp to see the SD and back stuff there?
Or otherwise revert back to external without losing all the data?
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
just go to internal stor-3 dots- migrate data.that would help you.
Sent from my Redmi Note 3 using XDA-Developers mobile app
I am ready to move onto MM. Those who cannot will ask for fix that wont come. So decide. Our dev already gave a detailed instruction. Thanks dev.
Sent from my Redmi Note 3 using XDA-Developers mobile app
same issue[or not an issue],but no emmc ..maybe it is for miui stock and i am on AOSP,..btw flashed twrp and waiting for new update
M.Carter said:
Thanks for the tuto. Can we flash miui roms without flashing patched boot.img or else with this recovery ?
Click to expand...
Click to collapse
I don't know about that but you can't flash any miui lollipop rom after you flash this cm13 and lock your bootloader. You will first have to restore to cm13(older) or aosp with unlocked bootloader and only then you can flash miui.
Or you can also unlock bootloader on the new rom and the flash miui. Correct me if I'm wrong about the last part, Santosh.
Sorry for the messed up (the ss isnt twrp alka, but another recovery) in twrp Alka the emmc backup is aboot and aboot.bak (it has different names for other partitions, but if you backup them all it wont have any problems) ill edit the post rightaway with the proper twrp
Windslash31 said:
Sorry for the messed up (the ss isnt twrp alka, but another recovery) in twrp Alka the emmc backup is aboot and aboot.bak (it has different names for other partitions, but if you backup them all it wont have any problems) ill edit the post rightaway with the proper twrp
Click to expand...
Click to collapse
I flashed mokee ROM (which I know will lock my bootloader) but before that I backup everything using the TWRP alka. And as expected , upon restoring the backup everything is working as they were working before. Bootloader is still unlocked.
the right screenshots are added on the other thread, sorry for the ****ed up
Got understand all steps except 4. How to reunlock the bootloader with mi flash tool. I before unlock bootloader via mi flash tool by flashing full 7.1.8 rom with replace emcc file and then give fastboot command. So now how to reunlock it.
Sent from my kenzo using XDA-Developers mobile app
Related
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
{
"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"
}
This is only for Huawei P9 Plus (VIE)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-vie.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_vie/releases/download/3.1.1-1/twrp-3.1.1-1-vie.img"][U]download twrp-3.1.1-1-vie.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9+ models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9 Plus
Contributors
OldDroid, surdu_petru, xepeleato
Version Information
Status: Stable
Created 2017-04-04
Last Updated 2017-06-11
Reserved
any working twrp for emui 4,1 with decryption support?
Thx bro
Thx for this nice work @OldDroid
This twrp works fine and root too....
VIE-L29C185 does it work?
I think model device is convenient. is it correct? I will be happy if you give me information.
goksemozkan said:
I think model device is convenient. is it correct? I will be happy if you give me information.
Click to expand...
Click to collapse
It is working good on my VIE-L29C185B360! Go ahead, use it and enjoy....
Addymore said:
It is working good on my VIE-L29C185B360! Go ahead, use it and enjoy....
Click to expand...
Click to collapse
my friend. What supersu have you uploaded, give a link.
https://forum.xda-developers.com/p9/...t3565703/page4
DL: http://filestore.to/?d=B9J55H6X9F link empty
goksemozkan said:
my friend. What supersu have you uploaded, give a link.
https://forum.xda-developers.com/p9/...t3565703/page4
DL: http://filestore.to/?d=B9J55H6X9F link empty
Click to expand...
Click to collapse
For root, I flashed this supersu for emui5....in twrp provided up! Working like a charm...! Thx to @OldDroid
Addymore said:
For root, I flashed this supersu for emui5....in twrp provided up! Working like a charm...! Thx to @OldDroid
Click to expand...
Click to collapse
Thanks to all my friends, now root and supersu are working perfectly.
And I will definitely enjoy :good::good::good:
Now, start nel custom rom
Works perfectly on VIE-L29C636 , thank you!
Thank you so much man
successfully got TWRP and root on VIE-L29C185
Good job my friend
Hi,
How can I flash twrp in emui 7? I've tryed several tutorials but I can't do it.
Best Regards
SuperTamagochi said:
How can I flash twrp in emui 7? I've tryed several tutorials but I can't do it.
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Hi guys. Sombody help me. How can i flash magisk on my p9 plus, i try many twrp, but everytime i see loop?
New release is up - TWRP 3.1.1-0 for P9 Plus.
Kernel should now support loop from b381 onwards.
Check OP for download link and github for more information!
P9 Plus Releases + Changelog
Regards
I'm sorry for the inconvenience but i forgot to exclude the special directory inside the /data partition during wipe/factory reset.
I've re-uploaded the fixed release, so everyone who had already installed 3.1.1-0 should now re-download and re-install.
Best regards
I'm sorry if this question has been asked somewhere else before, but can I flash an OTA update (extracted .zip) using TWRP, while keeping TWRP and SU?
It's quite bothersome to go back to full-stock, lock the bootloader, run the update, unlock the bootloader and root again, just for a minor update like B360 to B370.
I'm currently on B360 with TWRP 3.1.0 and SuperSU (rooted).
Rupert van da Cow said:
I'm sorry if this question has been asked somewhere else before, but can I flash an OTA update (extracted .zip) using TWRP, while keeping TWRP and SU?
It's quite bothersome to go back to full-stock, lock the bootloader, run the update, unlock the bootloader and root again, just for a minor update like B360 to B370.
I'm currently on B360 with TWRP 3.1.0 and SuperSU (rooted).
Click to expand...
Click to collapse
Hi, I can tell you in advance that NO, at least with an earlier version and that in principle it is only for normal P9.
Actually, you could only install that recovery, but with that I do not know what to tell you.
Anyway, due to the internal form of Huawei updates, they can not be installed since twrp, at least I have not been able to, nor anyone I know.
Sorry for my bad English, I do not know, and I use a translator.
Enviado desde mi VIE-L09 mediante Tapatalk
{
"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!
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Now you can flash SuperSU or Magisk and incremental OTA's without any hustles. Use the built-in SuperSU/Magisk option for rooting your device.
{
"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"
}
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you are really sure that you followed the installation process correctly then send us a log or screenshot and we will look at it.
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.This recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.
ATG Droid said:
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
[SIZE="3! You can use this recovery in any ROM.
Click to expand...
Click to collapse
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Androbots said:
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
Click to expand...
Click to collapse
Can I flash this on 2gb ram variant?
lordsh said:
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Look at the thread in the development section.. Here is the feature list. Anyway the main difference here is that RedWolf is based on the latest TWRP base and it also support AOSP 8.0.0 based ROMs
rohan_45 said:
Can I flash this on 2gb ram variant?
Click to expand...
Click to collapse
Yup
In ZCX the system img file (size more than 1 gb) is stored in sdcard. Do RedWolf also stores the system img file in sdcard ? (for incremental ota updates)
What if i edit build.prop...will i still be able to update incremental updates??
is that really ota update working on it??anyone tested??
umang0712 said:
What if i edit build.prop...will i still be able to update incremental updates??
Click to expand...
Click to collapse
Depends on what will you edit.
I can't save my custom settings, like reverse nav bar, system time etc. It is auto defaulted after every reboot. How can I save them?
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
kg hggggg tightly said:
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
Click to expand...
Click to collapse
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
dudemathai said:
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
Click to expand...
Click to collapse
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
kg hggggg tightly said:
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
Click to expand...
Click to collapse
I don't think you need to flash it when you change roms,what I know is that lazyflasher bypasses miui so that you won't be stuck in bootloop while you flash anything into miui
otyg said:
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
Click to expand...
Click to collapse
What problem are you facing? This recovery seems better and updated than ZCX.
Sent from my Redmi Note 3
can i use magisk with this?
rs168 said:
can i use magisk with this?
Click to expand...
Click to collapse
Yes
is this support with newest miui 9..?
xerocracker said:
is this support with newest miui 9..?
Click to expand...
Click to collapse
Yes
Sent from my Redmi Note 3 using XDA Labs
First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE
Thank you very much bedwa!
Kdz link updated!
Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.
Keeping me honest, I swear I'll remember them next time.
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:
help me
{
"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"
}
i had this issues when i try to flash it i already use uppercut
solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.
I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?
Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.
Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?
No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.
New security patch update alert