is now depreciated visit:
TWRP 3.0.3 with decyption support!
Your warranty is probably void. Do we care?
THIS IS NOT A FINAL RELEASE! IF ANYTHING GOES WRONG IT ISN'T MY FAULT! THIS IS NOT BUILT FROM SOURCE, IT USES RENEWED KERNEL FROM N AND EDITED FSTAB! AND DO NOT USE DATAFIX U CAN FORMAT DATA PARTITION IN ADVANCED WIPE!
HOW-TO ROOT YOUR MATE 9/P9/Honor 8
Download
Phh su r275 version and flash
Download and install Material phh apk: Release post
Done!
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Data Decryption
Battery status
Mounting Loop Devices (Kernel doesn't support this)
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status:Stable
Stable: Sort OF
Created: 2016-11-20
Something
unable to flash anything as its saying no storage
nintendolinky said:
unable to flash anything as its saying no storage
Click to expand...
Click to collapse
I noticed
You need to flash one zip
Just make sure you backup all data on your internal storage since it'll wipe it
Here it is https://mega.nz/#!SgpTiRaJ!7vLP2bLrDfbQ4eWb_Tzevlv3_Nwx2SpwvJx4iBKb9s0
You might need to wipe it after again.
Just make sure you resize the partition afterwards.
Sent from my FRD-L09 using Tapatalk
TWRP Recovery is working, SuperSU in the TWRP can not flash?
{
"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, delete Cache & Dalvik takes very long?
Formating Cache using make_ext4fs...
Hen Ry said:
TWRP Recovery is working, SuperSU in the TWRP can not flash?
View attachment 3944122 View attachment 3944123 View attachment 3944124 View attachment 3944125 View attachment 3944126 View attachment 3944127 View attachment 3944128
TWRP, delete Cache & Dalvik takes very long?
Formating Cache using make_ext4fs...
Click to expand...
Click to collapse
No you can't flash supersu for now.
I don't feel like twrp takes long time to wipe unless battery is low
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
No you can't flash supersu for now.
I don't feel like twrp takes long time to wipe unless battery is low
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
http://androiding.how/huawei-mate-8-nougat-root-twrp/ -> How to Root Huawei Mate 8 Nougat update with SuperSU
Again the B552 update.zip and the update_data_full_all_cn.zip installed in the TWRP.
Despite the factory reset (the TWRP was started), the data are still available.
The very slow formatting existed already times in an earlier TWRP version.
In the latest version for EMUI 4 / 4.1 it was very fast again.
Hen Ry said:
http://androiding.how/huawei-mate-8-nougat-root-twrp/ -> How to Root Huawei Mate 8 Nougat update with SuperSU
Again the B552 update.zip and the update_data_full_all_cn.zip installed in the TWRP.
Despite the factory reset (the TWRP was started), the data are still available.
The very slow formatting existed already times in an earlier TWRP version.
In the latest version for EMUI 4 / 4.1 it was very fast again.
Click to expand...
Click to collapse
Problem is when it tries to mount the su image it reboots.
Sent from my FRD-L09 using Tapatalk
Working in Mate 8 NXT-L29C432?
Hi Hen Ry, you mentioned 'TWRP recovery working' is on Mate 8 NXT-L29C432 please? I want to give a try.
______________________
Able to port the above TWRP on Mate 8 NXT-L29C432 successfully and boot to TWRP recovery.
SuperSU failed to flash (tried both SR3 and SR4 of SuperSU-v2.7
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Very slow formatting?
NXT-L29 with Tapatalk
Hen Ry said:
Very slow formatting?
NXT-L29 with Tapatalk
Click to expand...
Click to collapse
As I feel it. No
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Click to expand...
Click to collapse
Looking forward to it. Thank you
LastStandingDroid said:
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Click to expand...
Click to collapse
Will this fix the Bluetooth issue?
Sent from my FRD-L04 using XDA-Developers mobile app
manny18pr said:
Will this fix the Bluetooth issue?
Sent from my FRD-L04 using XDA-Developers mobile app
Click to expand...
Click to collapse
has nothing to do with the bluetooth, but yes it can apply it
could you build this for the Huawei P9? pleeaaseee! we have no working TWRP for the P9 nougat beta.
the phones are nearly identical so it should not need much adaption.
you would be our hero and your thanksmeter will explode!
Bluetooth, NFC and DUAL SIM Manager works for me.
with update_data_full_all_cn.zip
Do you have an eta for the build?
UnchartedRd said:
Do you have an eta for the build?
Click to expand...
Click to collapse
Hmm, not sure yet, still have some things i want to check first.
Hen Ry said:
Bluetooth, NFC and DUAL SIM Manager works for me.
with update_data_full_all_cn.zip
Click to expand...
Click to collapse
:good:
paratox said:
could you build this for the Huawei P9? pleeaaseee! we have no working TWRP for the P9 nougat beta.
the phones are nearly identical so it should not need much adaption.
you would be our hero and your thanksmeter will explode!
Click to expand...
Click to collapse
Sure if u have the stock recovery.img for it i can fix a fast backport
LastStandingDroid said:
Sure if u have the stock recovery.img for it i can fix a fast backport
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B9gJ44ME0ZkcSFdySTNBeTlZeTA
if you need someone to test pm me!
Related
Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
I'm getting binary update script error by flashing with TWRP
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.
iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.
housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO
Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app
truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"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 what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.
fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.
ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?
Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk
UPDATE 12/3/2016 - All builds now posted in developer forum: http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686
UPDATE 6/3/2016 - New version of TWRP has been released v3.0.0-0. See below:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
I have updated versions SM-T810 with a new build. TWRP is now v3.0.0-1
NOTE: This is a test build, I do not own this device. I need someone who knows what they are doing to test this out and report back.. A lot has changed in this version.
Features:
System image backup/restore
Factory image flashing.
F2FS support.
Supersu root option removed which would cause a bootloop on 5.1.1 and 6.0 devices.
MTP fix - MTP now finally working in recovery.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
I have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP-3.0.0-1-T810
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"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"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Nice, are you planing on releasing TWRP 3 for T710? Would rly like to have Mount working.
mk89pwnz said:
Nice, are you planing on releasing TWRP 3 for T710? Would rly like to have Mount working.
Click to expand...
Click to collapse
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
ashyx said:
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
Click to expand...
Click to collapse
Not many active 810 users. Do u have 710 yourself? or non of these devices?
mk89pwnz said:
Not many active 810 users. Do u have 710 yourself? or non of these devices?
Click to expand...
Click to collapse
I build for loads of devices I don't own. I don't have the S2.
If you are willing to test I can make a T710 build.
As for the amount of T810 owners, there has been 55 downloads since posting this the other day and NOT ONE has bothered to provide feedback. :thumbdown:
ashyx said:
I build for loads of devices I don't own. I don't have the S2.
If you are willing to test I can make a T710 build.
As for the amount of T810 owners, there has been 55 downloads since posting this the other day and NOT ONE has bothered to provide feedback. :thumbdown:
Click to expand...
Click to collapse
I would definetly test it
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
westernmg said:
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
Click to expand...
Click to collapse
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
westernmg said:
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
Click to expand...
Click to collapse
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
Please test this, it is built with the 5.1.1 kernel from the previous version: twrp_3.0.0-0_test2_t810
.
ashyx said:
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
Click to expand...
Click to collapse
??? http://forum.xda-developers.com/showpost.php?p=65197803&postcount=72
workdowg said:
??? http://forum.xda-developers.com/showpost.php?p=65197803&postcount=72
Click to expand...
Click to collapse
I changed a lot with this version, the build configuration itself is very different, kernel is built from latest source, modifications to the TWRP source code, mtp fix and hopefully even ADB working.
ashyx said:
I changed a lot with this version, the build configuration itself is very different, kernel is built from latest source, modifications to the TWRP source code, mtp fix and hopefully even ADB working.
Click to expand...
Click to collapse
Doesn't boot..
workdowg said:
Doesn't boot..
Click to expand...
Click to collapse
That's the test 2 version?
ashyx said:
That's the test 2 version?
Click to expand...
Click to collapse
The one from the OP is the only one I see....
workdowg said:
The one from the OP is the only one I see....
Click to expand...
Click to collapse
Post nr. 9
Flashing both from TWRP (using the image) and from Odin doesn't work, after restarting the recovery gets locked and unable to boot, as others wrote flashing the other TWRP from post 9 in your main TWRP thread works perfectly as far as booting, I did a couple of backups and worked fine, didn't restore the backups, so I can't tell you if restoring is fine.
Thanks for your efforts, I really appreciate them. :good:
kekinash said:
Flashing both from TWRP (using the image) and from Odin doesn't work, after restarting the recovery gets locked and unable to boot, as others wrote flashing the other TWRP from post 9 in your main TWRP thread works perfectly as far as booting, I did a couple of backups and worked fine, didn't restore the backups, so I can't tell you if restoring is fine.
Thanks for your efforts, I really appreciate them. :good:
Click to expand...
Click to collapse
Thanks, but you're confusing me, which version works? You say post #9, but that is this thread. :what:
I'm on LMY47X.T810XXU2BOJ1, the test2 is working so far.
But MTP doesn't seem to work for me.
On reboot to system it says "no OS installed ,are you sure to reboot?" but it boots fine....
ashyx said:
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
Please test this, it is built with the 5.1.1 kernel from the previous version: twrp_3.0.0-0_test2_t810
.
Click to expand...
Click to collapse
westernmg said:
I'm on LMY47X.T810XXU2BOJ1, the test2 is working so far.
But MTP doesn't seem to work for me.
On reboot to system it says "no OS installed ,are you sure to reboot?" but it boots fine....
Click to expand...
Click to collapse
It seems an issue with the kernel preventing boot to recovery with the earlier version. Not sure about the 'No OS installed' message, how can that be unless you wiped it?
Regarding MTP what actually happens?
Can you post the recovery.log on pastebin.com?
OK, it looks like TWRP is not able to mount anything.
The recovery.log cannot be written, also there is no access to the internal storage while trying to flash a zip or to restore a backup.
Got it on USB
ashyx said:
It seems an issue with the kernel preventing boot to recovery with the earlier version. Not sure about the 'No OS installed' message, how can that be unless you wiped it?
Regarding MTP what actually happens?
Can you post the recovery.log on pastebin.com?
Click to expand...
Click to collapse
I am not by any means responsable for any damage caused to your devise during this procedure!
I want to mention that I was root before the OTA. But I restore the backup that I had and updated to 6.0, I don't know if this is somehow relevant.
Things you'll need:
[TOOL] Sahara & Firehose - link
TWRP image - link
SuperSU Flashable Zip - link
Some free time.
Step 1:
Download the TWRP and follow this guide: [HOWTO] IDOL 4 6055. Installing TWRP recovery & get root access.
It is important that you make the backup of your recovery partition!
Step 2:
Hold Vol+ and PWR until you see the TWRP logo.
Tell TWRP to not touch your system partition!
Now do a Backup of "System Image" and "Boot", you can also make a backup of "EFS" if you want
Step 3:
Connect your phone to the computer and transfer the SuperSU zip
Step 4:
Go to TWRP -> Advanced -> Terminal
And type the follow code:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Step 5:
Make sure the .supersu file is in /data.
TWRP -> Advanced -> File Manager -> /data
Step 6:
Install SuperSU
TWRP -> Install
Choose the zip you downloaded and transfer in the step 3.
Step 7:
Reboot and you are done!
Remember: If something went wrong while flashing SuperSU, you can always restore your backup booting into TWRP.
[RESERVED]
Cricket stock 6.0.1
Will this work on the cricket model on stock 6.0.1
please reply as soon as you can.
Perfecto!!!
I want to confirm that this method works perfectly, I apply it to my Idol 3 5,5" 6045i (with 6.0.1 via OTA) and works like a charm!! Thank you @josehdez01 and @DeckerSU for doing this possible!!
manowar24 said:
I want to confirm that this method works perfectly, I apply it to my Idol 3 5,5" 6045i (with 6.0.1 via OTA) and works like a charm!! Thank you @josehdez01 and @DeckerSU for doing this possible!!
Click to expand...
Click to collapse
Do you think it will work the with the 6045O model? and will it reset my phone, sorry for asking so many questions.
KingLuwi said:
Do you think it will work the with the 6045O model? and will it reset my phone, sorry for asking so many questions.
Click to expand...
Click to collapse
Good question brother, maybe @josehdez01 and @DeckerSU have the answer, I´m not sure, but it will work if the method is for all 6045X. Ask them
KingLuwi said:
Do you think it will work the with the 6045O model? and will it reset my phone, sorry for asking so many questions.
Click to expand...
Click to collapse
Hello, in theory this should work for all 6045. If you follow the steps of the guide in the point one you should have a backup of your recovery partition. This way if twrp does not boot for you you just flash back the backup and nothing happened.
In the very likely case of success you shouldn't lose any data.
Anyone else tried this?
Will that work on the Idol 3 (4.7)? Any confirmations are appreciated!
KingLuwi said:
Will this work on the cricket model on stock 6.0.1
please reply as soon as you can.
Click to expand...
Click to collapse
+1
-sigh- I'm just scared i'm going to brick my phone, I've never rooted before
Bump?
Should work with all variants. I used Sahara with a 6045Y multiple times and never had a problem. Your best bet is to make a backup, try it and if it bricks (very small chance) you can always restore with Mobile Upgrade Q
KingLuwi said:
Do you think it will work the with the 6045O model? and will it reset my phone, sorry for asking so many questions.
Click to expand...
Click to collapse
KingLuwi said:
Will this work on the cricket model on stock 6.0.1
please reply as soon as you can.
Click to expand...
Click to collapse
This method works perfectly on a cricket 6045 no issues at all
I tried to this but the sahara stops responding when i try to back up my recovery
---------- Post added at 12:18 AM ---------- Previous post was at 12:15 AM ----------
allenjthomsen said:
This method works perfectly on a cricket 6045 no issues at all
Click to expand...
Click to collapse
I tried to this but the sahara stops responding when i try to back up my recovery
KingLuwi said:
I tried to this but the sahara stops responding when i try to back up my recovery
---------- Post added at 12:18 AM ---------- Previous post was at 12:15 AM ----------
I tried to this but the sahara stops responding when i try to back up my recovery
Click to expand...
Click to collapse
Thats weird because it didnt do that to me at all i backed up my recovery and flashed twrp and rebooted to recovery just fine
Sent from my 6045O using XDA-Developers mobile app
allenjthomsen said:
Thats weird because it didnt do that to me at all i backed up my recovery and flashed twrp and rebooted to recovery just fine
Sent from my 6045O using XDA-Developers mobile app
Click to expand...
Click to collapse
Do you mind telling me how many mbs the recovery.img has
Mine came out to 26.8 idk if thats correct ill redo it to make sure back to stock eith no recovery to test and make sure lolz
Sent from my 6045O using XDA-Developers mobile app
{
"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"
}
So the stock recovery comes out to 32.7MBs for 6.0.1 on cricket Idol 3
Sent from my SM-G935T using XDA-Developers mobile app
allenjthomsen said:
So the stock recovery comes out to 32.7MBs for 6.0.1 on cricket Idol 3
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the info I really appreciate it!
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
Xiaomi 8 SE *only*
** Update 1227 **
Original post:
http://www.miui.com/thread-15964692-1-1.html
Mirror:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
------------------------------------------------------------------------------------
2018.12.27 update content:
1. Update the problem of repairing the new version of rom into twrp
2018.12.17 update content:
1. Update to fix some oil can not get twrp problem, repeatedly restart into fastboot mode
2018.11.02:
1. Update support official Android 9 rom
2. Update and optimize some functions
3. Increase automatic The option to restart after the upgrade is completed. In the twrp setting, the default is automatic restart. Uncheck the box to not restart. It is convenient to perform some operations after the automatic upgrade to prevent the twrp from being overwritten, etc.
2018.9.28 update:
1. Add support to remove Dm checksum cancels the forced encryption function. The removal of the dm check function is mainly to prevent the card screen caused by the dm check and to prevent the official rec from covering the twrp.
Cancel the forced encryption function is used to permanently decrypt the data, you need to format the data, otherwise you can not enter the system, do not understand the machine is not recommended. Please be careful! !
2. Update the built-in magisk to 16.6, which is said to be the latest version of the card screen. The updated version will cause the card screen. At the same time fix the bug that the built-in magisk can't brush the module.
TWRP v3.2.3 2018.8.10 update:
1. Update to 3.2.3
2. Support new version official rom
3. Added signature boot and restore official rec and other functions
4. Built-in magisk 16.3, it is said that the high version will be card screen
5. Update the decryption data mechanism, theoretically decrypt the data more stable Some
---------------------------------------------------------------------------------------
v3.2.1 didn't work flashing treble GSI, anyone have any experience with this version?
how to update to this version
Can we resize the system, data and cache partitions with this version?
Lollipopx said:
how to update to this version
Click to expand...
Click to collapse
See q792602257's thread -
https://forum.xda-developers.com/mi-8/development/recovery-twrp-recovery-3-2-1-mi8se-t3813311
Or if you have TWRP already, just flash the new zip here from TWRP.
Hi! I don't read Chinese. Can you check if there's an update for Mi 8? Thanks!
samwise110712 said:
Hi! I don't read Chinese. Can you check if there's an update for Mi 8? Thanks!
Click to expand...
Click to collapse
Mirror：https://drive.google.com/file/d/17AhL4J4qTyfp6djM_CetU3Y-gpmyifel/view?usp=drivesdk
TWRP 3.2.3-0806 for mi 8
Everythings work fine but language is set to Chinese. Here's just the way i change to English. FYI.
https://www.hellpc.net/how-to-change-language-in-twrp-recovery-to-english/
When this thread will be moved to Mi 8 SE Forum?
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
isn't there any guide on how to flash?
t.me/joinchat/AAAAAEyDBlEI7z1R7HsXZw
danielwright said:
See q792602257's thread -
https://forum.xda-developers.com/mi-8/development/recovery-twrp-recovery-3-2-1-mi8se-t3813311
Or if you have TWRP already, just flash the new zip here from TWRP.
Click to expand...
Click to collapse
Is that possible to ask the author to make one TWRP for Mi 8 EE(Ursa)??
wching02 said:
Is that possible to ask the author to make one TWRP for Mi 8 EE(Ursa)??
Click to expand...
Click to collapse
You can Use the TWRP from MI8 and then you only have to edit the updater script in the custom.rom.zip
0. Use "MI8 TWRP" on "MI8 Explorer Edition" and install custom ROM
1. open downloaded custom "rom.zip"
2. go to -> \xiaomi.eu_multi_MI8Explorer_V10.0.4.0.OEHCNFH_v10-8.1.zip\META-INF\com\google\android\
3. edit -> updater-script
4. change -> getprop("ro.product.device") == "ursa" to getprop("ro.product.device") == "dipper"
5. enjoy
I use this recovery to flash new rom but now i can't find rise to wake any rom i flash.
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"
}
Someone could post last September build?
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
blu33agl3 said:
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
Click to expand...
Click to collapse
it worked, //fastboot boot & flash recovery
test on miui8.11.1(cn)
blu33agl3 said:
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
Click to expand...
Click to collapse
Tested on 8.11.1 from MIUI.EU to install root, it works!thanks!:highfive:
blu33agl3 said:
new one for Android pie support.
Not test yet
Click to expand...
Click to collapse
I test it and its works perfect. I Like wzsxr150 work.
Please help...
Everytime i install TWRP im never able to boot a new rom... ive tried miui.eu and others because i want global but the phone is stuck on the roms screen loading but never starts... no bootloop though...
other than the recovery do u install anything else? any other steps?
ty
manucas said:
Please help...
Everytime i install TWRP im never able to boot a new rom... ive tried miui.eu and others because i want global but the phone is stuck on the roms screen loading but never starts... no bootloop though...
other than the recovery do u install anything else? any other steps?
ty
Click to expand...
Click to collapse
Did you run in twrp data wipe? This is required in the first installation for the xiaomi, eu version
blu33agl3 said:
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
Click to expand...
Click to collapse
Thanks it works with xiaomi.eu_multi_MI8SE_8.11.1_v10-9
the only workin magisk with this is only up to 16.6 any up version above give bootloop