ROOT Huawei P10 Plus (VKY-***) y DM-Verity-OFF SuperSU - Huawei P10 Plus ROMs, Kernels, Recoveries, & Other

{
"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 root are universal (for any ROM/Build), it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device, this file are ported from Huawei Mate 9, and tested from me, it's fully working, included Kang-Vip ROM's
Requisites:
Bootloader Unlock
Custom Recovery
Installation Method:
Download file
Copy to External SD Card
Reboot to Recovery
Backup your actual BOOT
Install downloaded .zip
Rebot device
Profit!!
*In case of no appear SuperSU app download from Google Play*
Compatibility:
Huawei Mate 9
Huawei P10
Huawei P10+
Download:
2.79: https://mega.nz/#!BY91gIBZ!CjhTxoJIIHjNh_B3Hbmj477qxQ7fZE9VWeItnOgrmfk
Regards

Thanks for this mate; illa try when I get home

Not sure if the OP has English, limitation but the above file and method WORKS on VKY-L29 P10 Plus.
FYI:
* Download the ZIP file (don't unzip) and place on the root of your SD card
* Boot into TWRP (hold up and power buttons for ~6 secs)
* Select INSTALL and navigate to the .ZIP file on the root of your SD card
* After approx 1 or 2 mins, REBOOT the phone
If done successfully like me, it should boot normal. Make sure to go to GOOGLE PLAY and install PHH's Superuser. I've then selected "Superuser Access" over APPS and ADB. I then grant Superuser access to the app itself. Just to verify, i downloaded ROOT CHECKER app and verified successfully.
RoOSTA

Hey mates, I really didn't get it.
Does this method grant a REAL ROOT (system-editing ROOT), or not?
I need to know it before do everything: I don't want to root my device without become THE GOD OF TEH DEVICE

you read?
"it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device"
mocassino said:
Hey mates, I really didn't get it.
Does this method grant a REAL ROOT (system-editing ROOT), or not?
I need to know it before do everything: I don't want to root my device without become THE GOD OF TEH DEVICE
Click to expand...
Click to collapse

mocassino said:
Hey mates, I really didn't get it.
Does this method grant a REAL ROOT (system-editing ROOT), or not?
Click to expand...
Click to collapse
To clear up the confusion... If you were to push a system ROM update via Huawei, for example, it will likely REMOVE root and possibly relock the boatloader.
On an older stock ROM, I was boot unlocked with TWRP installed. After a OTA update though, TWRP was removed and boot relocked. So yeah. You can edit the system, but it's not 100% permanent if you were to flash an update.
Really just want to Xposed now!
RoOSTA

BadWolfYe said:
you read?
"it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device"
Click to expand...
Click to collapse
then ok, finally I get it. Thanks
---------- Post added at 08:55 AM ---------- Previous post was at 08:52 AM ----------
roosta said:
To clear up the confusion... If you were to push a system ROM update via Huawei, for example, it will likely REMOVE root and possibly relock the boatloader.
On an older stock ROM, I was boot unlocked with TWRP installed. After a OTA update though, TWRP was removed and boot relocked. So yeah. You can edit the system, but it's not 100% permanent if you were to flash an update.
Really just want to Xposed now!
RoOSTA
Click to expand...
Click to collapse
well, actually it's seems peculiar to me that I can push an official update via OTA having the device rooted (or not? It's my first Huawei, on other phones I couldn't update with a modifyed device)

OTA or via firmware finder. Either way

BadWolfYe said:
Compatibility:
Huawei P10
Download:
2.79: https://mega.nz/#!BY91gIBZ!CjhTxoJIIHjNh_B3Hbmj477qxQ7fZE9VWeItnOgrmfk
Regards
Click to expand...
Click to collapse
Great, it works. We have full access to the system. Thank you.

roosta said:
Not sure if the OP has English, limitation but the above file and method WORKS on VKY-L29 P10 Plus.
FYI:
* Download the ZIP file (don't unzip) and place on the root of your SD card
* Boot into TWRP (hold up and power buttons for ~6 secs)
* Select INSTALL and navigate to the .ZIP file on the root of your SD card
* After approx 1 or 2 mins, REBOOT the phone
If done successfully like me, it should boot normal. Make sure to go to GOOGLE PLAY and install PHH's Superuser. I've then selected "Superuser Access" over APPS and ADB. I then grant Superuser access to the app itself. Just to verify, i downloaded ROOT CHECKER app and verified successfully.
RoOSTA
Click to expand...
Click to collapse
What do you mean with PHH's?
Wasn't it clearly stated as a SuperSU root (chainfire?) I'm confused...

BadWolfYe said:
This root are universal (for any ROM/Build), it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device, this file are ported from Huawei Mate 9, and tested from me, it's fully working, included Kang-Vip ROM's
Requisites:
Bootloader Unlock
Custom Recovery
Installation Method:
Download file
Copy to External SD Card
Reboot to Recovery
Backup your actual BOOT
Install downloaded .zip
Rebot device
Profit!!
*In case of no appear SuperSU app download from Google Play*
Compatibility:
Huawei Mate 9
Huawei P10
Huawei P10+
Download:
2.79:https://mega.nz/#!BY91gIBZ!CjhTxoJIIHjNh_B3Hbmj477qxQ7fZE9VWeItnOgrmfk
Regards
Click to expand...
Click to collapse
Thanks its working fully root.
P10 PLUS VKY-L29

it requires SD card?

juntulis said:
it requires SD card?
Click to expand...
Click to collapse
In instructions i say : "Copy to External SD Card"

BadWolfYe said:
In instructions i say : "Copy to External SD Card"
Click to expand...
Click to collapse
Because internal storage doesn't work?

Jesus man, just follow instructions. If there was a more easy option, i'm sure it was mentioned.
Thanks by the way for this thread! worked perfectly!

nbyz said:
Jesus man, just follow instructions. If there was a more easy option, i'm sure it was mentioned.
Thanks by the way for this thread! worked perfectly!
Click to expand...
Click to collapse
Jesus dude, not everyone has "External SD card". All i'm asking is it possible to install from internal storage?
I don't need this drama.

juntulis said:
Jesus dude, not everyone has "External SD card". All i'm asking is it possible to install from internal storage?
I don't need this drama.
Click to expand...
Click to collapse
No it's POSSIBLE.
No data in RECOVERY.

juntulis said:
Jesus dude, not everyone has "External SD card". All i'm asking is it possible to install from internal storage?
I don't need this drama.
Click to expand...
Click to collapse
Yes, it's possible to root even if you don't have an external SD.
For me, I can't access Internal storage from TWRP to navigate to the SuperSU zip because it's encrypted for me.
You can flash it from your PC using ADB. Connect your phone to PC and open up CMD from the folder where you have ADB and Fastboot.
Boot into TWRP on your P10. Go over to Adcanced > ADB sideload > Swipe to start sideload.
Now, go over to CMD on your PC and type in "adb sideload (FILE NAME).zip"
Also guys chill. There is no instruction for Internal storage, that's why juntulis is asking

For anyone who rooted their phone : does Viper4Android work with this ?

Please tell me where to take the original oeminfo TWRP backup to P10 plus VKY AL00C00?

Related

[GUIDE] Root Acer Iconia Tab 8 - One 8

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Credits
@social-design-concepts for his great work and exploit for Intel Tab Devices
@vampirefo for CWM binary for Intel devices + Linux scripts
@vache for the full Repacked CWM image
Devices Compatible
A1-840FHD
A1-840 (HD)
A1-830
B1-810
A1-850
A1-860
B1-820
A3-A30
Requirement
Install the official Generic Google USB Drivers on your Desktop (http://developer.android.com/sdk/win-usb.html) - Also available in the TOOLKIT Package
Enable USB Debug on your Device
Guide 1 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.042_AV0K1_RV0MRC02_WW_GEN1 and older)
A1-830
Download
myKIT_BATCHv1.1.2.7z available at http://forum.xda-developers.com/showthread.php?t=2681783
myKIT_BATCHv1.1.2d_PATCHKIT.7z at http://forum.xda-developers.com/showthread.php?t=2681783
INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z at http://forum.xda-developers.com/showpost.php?p=51090059&postcount=3
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip myKIT_BATCHv1.1.2.7z and move myKIT_BATCHv1.1.2d_PATCHKIT.7z & INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z in the mykit-downloads directory
Start run-me.bat and type ACCEPT, press Enter. The toolkit is upgraded to 1.1.2d.
Close it, plug your Tab with USB Cable and start run-me.bat again
Type ACCEPT, press enter, type "2", press enter,
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
On your deskop, the script should auto detect the Tab like this :
{
"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"
}
Type A2, press enter, type 1 for INTEL_TRIAL_TETHERED_CWM_PKGKIT and press enter
Type ACCEPT, press enter
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 2 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.057_AV0K1_RV0TRC01_WW_GEN1 or more recent)
A1-840 (HD)
B1-810 [confirmed by @alexys77]
A1-850 [confirmed by @Darrian]
A1-860 [confirmed by @edotcom]
Download
IntelAndroid-FBRL.7z available at http://forum.xda-developers.com/showpost.php?p=57505512&postcount=2375 thx to @social-design-concepts
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip IntelAndroid-FBRL.7z
Plug your Tab with USB Cable and start launcher.bat
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
Type ACCEPT ont the cmd screen, press enter
On your deskop, the script should auto detect the Tab like this (device status online + color blue) :
Type "T3", press enter
Note: if the T3 exploit doesn't work on your device, you can try T2 or T1
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
/!\ Please note that the tethered CWM has just boot, it has not be flashed, we can't flash a custom recovery while our bootloader are locked. /!\
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 3 - Boot Tethered CWM or TWRP
Compatible with
B1-820 (LP 5.0)
A3-A30 (LP 5.0.2) confirmed by @paugustin
Procedure
Follow all steps described by @social-design-concepts on his updated thread :
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Advice/FAQ for Acer Tab Device : :
You should use the CWM recovery and the T4 exploit
TWRP boots, but no touch available
CWM runs fine, but cannot mount internal storage or /data, you MUST use an external SDCard
Flashing SuperSU and Installing Xposed Framework for LP is working great on B1-820 !
Guide 4 - Flash CWM Recovery (permanent)
vache said:
CWM for A1-840 FHD (only) based on Dell Venue 8 one. (http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925)
Tested successfully.
ADB_Fastboot.zip for Intel Devices (use this to flash)
CWM-v6.0.3.7_A1-840FHD.img.zip
stock_recovery.zip
To flash it :
Code:
fastboot flash recovery CWM-v6.0.3.7_A1-840FHD.img
Then use droidboot menu to reboot in recovery.
Click to expand...
Click to collapse
Thx @vache & @vampirefo
Firmwares
Flashable via (stock) Recovery
A1-830
SDs_Acer_AV0K0_A1-830_1.007.00_WW_GEN1.zip
SDs Acer_AV0K0_A1-830_RV01RC02_WW_GEN1.zip
SDs_Acer_AV0K0_A1-830_RV01RC05_WW_GEN1.zip
A1-840
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0ERC02_WW_GEN1
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0LRC01_GC_GEN1
SDs_Acer_AV0K1_A1-840_RV0XRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840_RV0ZRC03_WW_GEN1.zip
A1-840FHD
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0BRC01_WW_GEN1.zip
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0MRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840FHD_RV0TRC01_WW_GEN1.zip
B1-810
SDs Acer_AV0K0_B1-810_RV02RC03_WW_GEN1.zip
SDs_Acer_AV0K0_B1-810_RV02RC04_WW_GEN1.zip
A1-850
SDs Acer_AV0K0_A1-850_RV00RC01_WW_GEN1.zip
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
stari_alca said:
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
Click to expand...
Click to collapse
We can't flash it for now
This exploit only can boot it
We need to unlock the tab to be able to flash something
Envoyé de mon A1-840FHD en utilisant Tapatalk
Great Guide!
Unfortunately it doesn't work with the very similar A1-840HD:
http://forum.xda-developers.com/showpost.php?p=56580827&postcount=2158
Hi there,
How did you guys manage to install the MTP device drivers (the one that pops up in Device Manager when you enable the USB debbugging)? I´m on a Windows 7 (32 bits) and the folder we are instructed to download and unzip apparently does not contain the required files/driver.
Any help is appreciated as I can´t manage to pass that initial point.
Thanks in advance,
Mix
EDIT: I eventually got it to install correctly by using the USB Driver package from Acer:
http://global-download.acer.com/GDF...ep3=A1-840FHD&OS=ALL&LC=en&BC=ACER&SC=EMEA_27
I used the option in the toolkit which installs the drivers. If I remember correctly once you run the .bat file and ACCEPT you are given this option. I used 32 bit version of Win 7 as well.
Sent from my A1-840FHD using XDA Free mobile app
Works on A1 830
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
retroben said:
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
Click to expand...
Click to collapse
Did you try this guide?
I'm not sure I understand your post and what you want to do.
My product and safety information booklet says FHD on it despite mine only having 1GB of RAM.
Is there a root method working on the A1-840HD?
I may try Kingo since they still get updates and just added an exploit for Nexus Android 4.4.4 as well.
I hope it has support for this device.
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
borisgregoris said:
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
Click to expand...
Click to collapse
Well... I don`t have this tablet but think of buying one and I think that this could be done.
CWM has backup feature so I think that you could try backup current ROM and after you did that then root your device and if the problem pops you load CWM again and then restore original state.
If you already rooted then I think that someone that hasn`t rooted the device could make backup of ROM and upload it somewhere on the Internet.
Here is a full UPDATE zip ROM for A1-840 only (not compatible with A1-840FHD), flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
borisgregoris said:
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
Click to expand...
Click to collapse
It means that my image is older than yours (which make sense, it's not the latest firmware)
But I think you can get some file from it and make your tab working fine again.
If it doesn't work, you can try to full flash the update zip to "downgrade" to a stable version (and then, you should get some OTA updates to get back to the latest version)
Here is some OTA manual download if needed :
Code:
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0TRC01 227,47MB http://global-download.acer.com/GDFiles/Application/OTA/635537141647405935_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0RRC02 227,33MB http://global-download.acer.com/GDFiles/Application/OTA/635526789434977662_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0BRC01_AV0K1_RV0MRC02 45,86MB http://global-download.acer.com/GDFiles/Application/OTA/635490499381942196_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV09RC01_AV0K1_RV0MRC02 49,69MB http://global-download.acer.com/GDFiles/Application/OTA/635469761667577586_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0JRC02_AV0K1_RV0MRC02 42,13MB http://global-download.acer.com/GDFiles/Application/OTA/635469757626803549_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV08RC01_AV0K1_RV09RC01 37,53MB http://global-download.acer.com/GDFiles/Application/OTA/635402969903280635_OTA_Acer_1.0_AV0K1_A.zip
Enjoy
Hi, thanks for the image. Custom recovery fails for me:
assert failed: getprop("ro.product.model") == "A1-840"
Error in /cache/sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
stari_alca said:
Hi, thanks for the image. Custom recovery fails for me:
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Click to expand...
Click to collapse
Hi, same error here.
After flashing in stock recovery give me the assert failed error.
Its secure to flash the OTA files? I'm curious if they send me the same error that the update.zip. I'm afraid to brick the tab .
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Shreps said:
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Click to expand...
Click to collapse
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
borisgregoris said:
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
Click to expand...
Click to collapse
You should also set the right permissions and owner to the files like other file in the same directory.
Envoyé de mon One+

[TUT][HOW-TO] How to root Xiaomi Redmi2 and install CWM

ARE YOU SEARCHING TO ROOT YOUR REDMI 2 ?​
DISCLAIMER:​DO THIS ON YOUR OWN. I'M NOT RESPONSIBLE FOR ANYTHING HAPPENS TO YOU AND YOUR DEVICE.​PLEASE DONOT MIRROR THE LINKS​
CLICK HERE FOR NATIVE ROOT​
IF YOU ARE GETTING STOCK RECOVERY EVEN AFTER FLASHIN CWM, SEE THIS POST​
STEP 1- FLASHING CWM ON YOUR PHONE
1.At first, you'll need the "adb" and "fastboot" tools. Get them HERE
2.Extract them into a folder, let's name it "Redmi2" (You can give your own name to the folder. That doesn't matter here.)
3.Now get the CWM .img file from HERE
You can use Philz Touch recovery also. Get HERE
4.Rename cwm.img or philz.img you downloaded above and as "recovery.img" and place it in the Redmi2 folder.
Now the folder will look like this-
{
"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"
}
5.Press and hold "shift" button and right click in the blank area of the folder and click on "open command promt window here". The command prompt will open.
6.Now turn off your Redmi2. Wait until it vibrates. After it's vibrated press and hold "Volume down and Power" keys together until it boots into "fastboot mode". Now connect the Redmi2 to your PC/Laptop through USB cable in fastboot mode itself.
7.Get to the command prompt now.
Now type: " fastboot devices " (without these- " " )
Like this-
8.Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command
9.Now enter the next command: " fastboot flash recovery recovery.img "
Like this-
10. Now this ends...
Type the last command: " fastboot reboot "
Like this-
11.Now your phone will reboot with ClockWorkMod(CWM) installed. CHEERS...
STEP 2- ROOTING YOUR PHONE
1. Firstly get the SuperSU.zip from HERE
2. Now copy the downloaded zip to your sdcard (not in any folder just in sdcard)
3. Boot into CWM recovery by turning off the phone and pressing "Volume UP and Power" button together after the phone vibrates.
4. Once CWM main menu is displayed, select "Install from zip" and browse to the zip that you downloaded earlier and select it.
5. Install the zip. If you get any warning, ignore and proceed.
6. After the installation is complete, reboot your device. (I think you can do that)
7. VOILA..!!! YOU ROOTED YOUR REDMI2
PLEASE HIT THANKS​
JOIN OUR FACEBOOK GROUP HERE​
CREDITS:
1. I don't claim any credit for "adb and fastboot tools" and the "recovery.img" and "SuperSu.zip"
2. Thanks to @subhrajiNath on Miui english forums who wrote the original guides.
Thread link is here and here​
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
postadelmaga said:
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
Click to expand...
Click to collapse
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
? not flashing ?
noobpremium said:
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
Click to expand...
Click to collapse
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
postadelmaga said:
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
Click to expand...
Click to collapse
get "Flashify" app from playstore and first take backup of stock recovery and then flash the cwm with it. Thats it..
Actually I didn't knew this method before i made this guide..
Anyway, fastboot gives us a different feel, doesn't it? :v
wait I don't know flashify but it looks it needs root to flash the recovery ... but I think I need cwm to root ... so I think this is not gonna work ...
Ok got it, this may be useful to anybody face the issue with recovery:
I discovered you can workaround the issue in this way:
Temporary boot into CWM:
HTML:
fastboot boot recovery.img
Root the device using CWM
Flash CWM using flashify
[ CWM when you log out ask you for root so maybe it is not necessary to use the zip file ( but I'm not very expert so maybe I'm wrong)]
You can install GAPPS with CWM `gapps-kk-20140606-signed .zip` but be careful, whenever you update MIUI you will look all software installed using CWM. ( superSu and GAPPS for example )
thanks
thanks!
eienkisu said:
thanks!
Click to expand...
Click to collapse
Pleasure
Okay bro :good:
I'll update the OP
I confirm #postadelmaga the CWM recovery does not stay, the only way to do access it is the fastboot boot recovery.img Here's how I succeeded with two phones now.
power on, start wifi, do Miui updates
install ADB or the files above on PC
reboot to fastboot with voldown+pwr
now comes fastboot boot recovery.img
in CWM, sideload SuperSu and Gapps
connect you preferred VPN (if in China)
install and update all Google apps needed
delete most Chinese apps
hey i m unable to flash recovery plzz help
Device version 2014818
Sent from my 2014818
Hi buddy could you plz port touchwiz from galaxy prime?
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
not working.
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
godwintgn said:
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
Click to expand...
Click to collapse
Are you on win7? I got this same issue on my win7... try on win8 it works flawlessly
Please hit thanks if done
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Shrihari007 said:
Hi buddy could you plz port touchwiz from galaxy prime?
Click to expand...
Click to collapse
TW sucks man.. why do you want it :/ anyways I'll try
leuk_he said:
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
Click to expand...
Click to collapse
Thanks to you bro.. I'll update the OP for those who are facing some issues with my guide's precedure..
OP Updated
I've updated the OP with the other guide's link.. please check it out if you're having some issues with this one
godwintgn said:
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Click to expand...
Click to collapse
Try on some friend's PC or something

[GUIDE] Gain Root Access v3 (3 Methods!)

Hello people,
This is for Mi Note Pro (leo)
Disclaimer:
I'm not responsible for any devices being bricked, your device blowing up or world war 3 starting! You are doing this at your own risk.
Click to expand...
Click to collapse
A lot of people ask how to gain root on the Mi Note Pro without actually searching the posts so I decided to make a quick tutorial on how to do it. This is the way I have done it and I have found it to be the easiest way!
1st Method (THE EASIEST AND SAFEST!)
1. Go to http://en.miui.com/download-273.html and download the Developer ROM
{
"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"
}
2. If you have downloaded the file through your phone it will be in the Download folder, if not plug your phone into the PC and move the .zip file over to your device.
3. Open Updater app, tap on 3 dots to open the menu and tap on Choose update package
4. Navigate to where you have put in the zip file and click on it and let the phone update. (This will wipe all your data apart from pictures etc.)
5. Once it has loaded go through the setup. Open Security app > Permissions > Root Access.. There you are all done
Make sure you open an app that requires root access first before going to Security app as it will not show up on there.
2nd Method (Advanced Users!)(Temporary TWRP Recovery)
Requirements:
fastboot driver (Link attached)
twrp.img - https://mega.nz/#!nR0jHZqL!2cksl ... 5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3. Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot boot twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with Stock Recovery and Stable ROM!
3rd Method (Advanced Users!)(Permanent TWRP Recovery)
Requirements:
fastboot driver
twrp.img - https://mega.nz/#!nR0jHZqL!2ckslQxV-ODWnswRYpfDCp2M5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3.Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot flash recovery twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with TWRP recovery, the only problem is that your OTA updates will break. You can flash them manually, when Updater downloads an update go into TWRP>Install and navigate to downloaded_rom folder
In case you need to go back to stock Recovery because you have flashed TWRP Permanently please follow instructions on this thread.http://en.miui.com/thread-124319-1-1.html
GREAT! EASY!
Need to wipe cache or data?
Nope no need to do that
nice thanks for the advice
I followed ur step but no show root access...
Did I miss anything?
Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Yea step 5
Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Well their Root Access works a bit different to SuperSU instead of popping up with a box promting you to give root access what you have to do is open the app the requires root access, do an action that needs root access then you go to Security > Premissions > Root Access and you have to grant it then.
Is only way to root to do a full wipe?
Can we still do normal updates after installing this developer rom?
Yup you get newest weekly updates and they work perfectly fine! I'm on 5.7.2 currently
Updated.
Is it equally safe to flash the latest 1.0.0 supersu from chainfire? Is there any compatibility constraints? or are all version compatible with all devices? thanks for shedding some light into this
Can you use Flashify and install twrp and supersu or is supersu not needed using method 1? ?
sent from mobile thingy
Super su is not needed using method 1 as they use their own root manager.
Kahun said:
Super su is not needed using method 1 as they use their own root manager.
Click to expand...
Click to collapse
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.
deddo86 said:
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.
Click to expand...
Click to collapse
Just flash stable ROM.
Added a permanent recovery method but "might" break OTA
Problem with Method 1
Hi People /Mr. Kahun ,
I'm absolutely new but i would like to root my :
Mi Note Pro
Android 5.0.2.
MIUI 66.55.44.00
because some original programs make me creasy . I tried method 1. I followed your steps, i downloaded different DEVELOPER Rom (5.9.10 and 5.9.17) , but i had always with the step 4 the message GETTING INFO ..... and this is the end of the process .....
PLEASE PLEASE tell ma what can i do to root the device .
Thank you in advance
Try installing HappyMIUI rom from the android development section.
i don't know how to install .....i will try method 2.
thank you Kahun!
where can i find the fastboot driver (Link is NOT attached)

Tutorial How to root ZTE z835 (Maven 3) with Magisk.

DISCLAIMER: I AM NOT RESPONSIBLE FOR WHAT MAY HAPPEN TO YOUR DEVICE, DO THIS AT YOUR OWN RISK.
Before I start: everything I'm going to post here, I learned from this thread: https://forum.xda-developers.com/maven-3/help/zte-maven-3-z835-root-t3705687/page9
VERSION OF MAGISK FLASHEAD v17.1 (Unfortunately no one has flashed version v18.1)
What we need (they will be in the links at the end):
-ZPST for AT&T (with this program we are going to flash the modified boot.img)
-Drivers: QDLoader, ZTE AndroidUSB and ZTE_V889F (in case the previous Zte driver does not work).
-Modified boot.img that are already flashed with Magisk, only the following versions are available:
-Z835V2.0.0B10
-Z835V2.0.0B12
-Z835V1.0.0B13
-Magisk Manager version compatible with v17.1
EVERYTHING YOU NEED IS IN A LINK AT THE END OF THE POST.
Let's get started.
I recommend to do a hard reset before starting, however, in one of my devices I did it having data and applications installed, if you have used kingroot or any other software in your phone, erase all trace of it so you do not have problems.
We download all the contents of the folder, install all drivers included, and the ZPST for AT&T.
Starting to flash:
WE NEED AT LEAST 50-60% of Battery
Turn off the phone and turn on pressing Vol Down + Power Button, the phone will start in FTM mode.
Open ZPST for AT&T and select version Z835
{
"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"
}
WARNING, remove the usim and sd card
Once inside the software we proceed to connect the cell phone.
1. You will see if the phone was recognized by the com port.
2. Download, this is where we will enter to download the firmware
3. You will see your information imei and so on.
This is how it will look once connected (Let's go to the download tab)
1. Let's select the firmware (it has to be the same as the cell phone otherwise it can corrupt the imei)
2. We chose where to keep a small log to check if everything went well.
3. HIT THE DOWNLOAD BUTTON!!!!!
WARNING: wait for the device to restart at least 2 or 3 times, one of them will be in FTM mode again, so do not panic, it will take a while in 3% or 5%.
When the phone starts normally, if you did a hard reset configure everything again, otherwise, we will proceed to install the magisk.
DO NOT INSERT THE SD CARD YET!
Magisk asks if I want to update to the latest version, press NO THANKS.
Proceed to uninstall
Now let's install the version of magisk manager we downloaded (com.topjohnwu.magisk_6.1.0-165_minAPI21(nodpi)_apkmirror.com.apk)
When the installation is finished we enter Magisk and this will ask us if we want to upgrade to the latest version, PRESS NO!
Now we will see that magisk is installed correctly.
We see that we can use all its functions.
We will proceed to verify if we have root access.
Download root checker
And Voila!
MEGA link: https://mega.nz/#F!ud8VwKRJ!-cJr7EJyhb1PkziNx5KvLQ
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
nvizync said:
Root
Click to expand...
Click to collapse
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
deadman96385 said:
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
Click to expand...
Click to collapse
Would love to see that, thanks for the reply! :good:
rickastillo said:
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
Click to expand...
Click to collapse
You can install titanium backup, twrp is not possible at this point, no one has done it yet, you can delete system apps through adb, using
Code:
adb shell pm uninstall -k --user 0 packagename
But i haven't figured out yet how to get rw permission on system/apps so i can delete system apk's.
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V1.0.0B13 (Magisk 18.1) Link: https://mega.nz/#F!88IiFapI!6Peah7woOOaIhusfYCAEcw
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root tutorial
Alijosekt said:
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root guide
Click to expand...
Click to collapse
I totally forgot it, yeah, you deserve most of the credit, I linked the original thread, but I'm planning including all the credits.
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
Ok my way
nvizync said:
Ok my way
Click to expand...
Click to collapse
not boot twrp
Alijosekt said:
not boot twrp
Click to expand...
Click to collapse
Did you tried it
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
nvizync said:
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
Click to expand...
Click to collapse
Done, i managed to enter in normal mode and use flashify to flash stock recovery.img.
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
penn462 said:
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
Click to expand...
Click to collapse
Are you using the custom boot.img listed in mega's folder?
nvizync said:
Are you using the custom boot.img listed in mega's folder?
Click to expand...
Click to collapse
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
penn462 said:
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
Click to expand...
Click to collapse
Thats odd, try this: download another folder B12 or B10, and just paste the B13 boot.img, maybe that could work, one of the devices i rooted was B13.
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Update: not bricked. Gonna try again.
penn462 said:
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
Click to expand...
Click to collapse
Fear not, that happened to me also, just keep in ftm and make a stock boot.img flash, provided in the mega folder. Paste the boot stock image inside the b13 folder
Placed stock boot.img into B13 folder in place of custom boot.img. The process failure point is now back to the missing sbl1.mbn problem. I can get the phone to start, however, so it's not bricked. Whew!

ADB push not working/TWRP

I accidentally flashed the Universal SafetyNet Fix 1.1.0 via TWRP and had to start from scratch (flash MIUI via MIUI flash tool)
I installed TWRP and now want to copy files to the phone. I hence copy the file (gapps.zip) into the adb folder and run
adb push gapps.zip /sdcard
However, I end up with an error:
adb: error: failed to copy 'gapps.zip' to '/sdcard/gapps.zip': remote couldn't create file: No such file or directory
gapps.zip: 0 files pushed.
The device itself is detect:
adb devices
xxxxxxx recovery
I would highly appreciate some help here, this has been driving me nuts.
Update: Not sure if I properly flashed TWRP. I cannot boot into recovery, even though
fastboot flash recovery C:\Users\user\Downloads\mi\twrp.img
successfully runs
WTF is wrong with flashing TWRP?
flel said:
I accidentally flashed the Universal SafetyNet Fix 1.1.0 via TWRP and had to start from scratch (flash MIUI via MIUI flash tool)
I installed TWRP and now want to copy files to the phone. I hence copy the file (gapps.zip) into the adb folder and run
adb push gapps.zip /sdcard
However, I end up with an error:
adb: error: failed to copy 'gapps.zip' to '/sdcard/gapps.zip': remote couldn't create file: No such file or directory
gapps.zip: 0 files pushed.
The device itself is detect:
adb devices
xxxxxxx recovery
I would highly appreciate some help here, this has been driving me nuts.
Update: Not sure if I properly flashed TWRP. I cannot boot into recovery, even though
fastboot flash recovery C:\Users\user\Downloads\mi\twrp.img
successfully runs
WTF is wrong with flashing TWRP?
Click to expand...
Click to collapse
Leave off the /
adb push gapps.zip sdcard
What android are you on? 10, 11, etc.
Tulsadiver said:
Leave off the /
adb push gapps.zip sdcard
What android are you on? 10, 11, etc.
Click to expand...
Click to collapse
android 11, kernel version 4.4, miui 12.5
adb push is not working, showing error
also twrp can't read the internal storage, no file there, and it is not also 0 mb, amount of storage is okay but but twrp can't read the zip file I inserted, what to do? please help me
shafi1885 said:
android 11, kernel version 4.4, miui 12.5
adb push is not working, showing error
also twrp can't read the internal storage, no file there, and it is not also 0 mb, amount of storage is okay but but twrp can't read the zip file I inserted, what to do? please help me
Click to expand...
Click to collapse
Just drag and drop it in file manager/explorer/etc (whatever is on the OS you're using)
TWRP acts as an MTP device, so you can see the internal storage of the phone when it's booted to TWRP and connected to a PC. Why make life complicated using adb commands when it's easier to drag and drop.
Robbo.5000 said:
Just drag and drop it in file manager/explorer/etc (whatever is on the OS you're using)
TWRP acts as an MTP device, so you can see the internal storage of the phone when it's booted to TWRP and connected to a PC. Why make life complicated using adb commands when it's easier to drag and drop.
Click to expand...
Click to collapse
{
"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"
}
bro, this is the condition of internal storage, both in pc and twrp, and it also saying this: "unmodified system partition" "keep system read only?" then it is written: swipe to allow modification. I swiped but no modification I think took place, Misgk.zip is not showing, ADB push not working, and you can see in ss the condition of internal storage in pc.
I read about date encryption, saw 1 youtube video (not available any), they all say that internal storage showing 0 mb. but my internal storage is not showing 0 mb. it is showing 92 gb which is free currently, and each time after rebooting, twrp is gone, though after flashing, I hold on to power+volume up. Now please tell me the easiest solution. I gave a lot of effort in last 3 days, It's really depressing brother. But thank you for letting me know that twrp also work as MTP media.
shafi1885 said:
View attachment 5285045
bro, this is the condition of internal storage, both in pc and twrp, and it also saying this: "unmodified system partition" "keep system read only?" then it is written: swipe to allow modification. I swiped but no modification I think took place, Misgk.zip is not showing, ADB push not working, and you can see in ss the condition of internal storage in pc.
I read about date encryption, saw 1 youtube video (not available any), they all say that internal storage showing 0 mb. but my internal storage is not showing 0 mb. it is showing 92 gb which is free currently, and each time after rebooting, twrp is gone, though after flashing, I hold on to power+volume up. Now please tell me the easiest solution. I gave a lot of effort in last 3 days, It's really depressing brother. But thank you for letting me know that twrp also work as MTP media.
Click to expand...
Click to collapse
When starting TWRP, it must ask you for (your Android screen unlock pin/password or pattern) - without, TWRP cannot temporarily decrypt the file system and you see the garbage as on your screenshot for Data and Internal memory
If you switched the ROM, you HAD to FORMAT (not Wipe) Data.
Without, TWRP does not ask for that (unlock) pin/pass (or asks but fails to decrypt) and you have the garbage.
Didn't try but that must be also the reason for side-load failure
If you didn't switch ROM (and if you can boot to Android), go to Settings and reset the screen unlock pin/pass/pattern
zgfg said:
When starting TWRP, it must ask you for (your Android screen unlock pin/password or pattern) - without, TWRP cannot temporarily decrypt the file system and you see the garbage as on your screenshot for Data and Internal memory
If you switched the ROM, you HAD to FORMAT (not Wipe) Data.
Without, TWRP does not ask for that (unlock) pin/pass (or asks but fails to decrypt) and you have the garbage.
Didn't try but that must be also the reason for side-load failure
If you didn't switch ROM (and if you can boot to Android), go to Settings and reset the screen unlock pin/pass/pattern
Click to expand...
Click to collapse
brother, I haven't swtiched ROM and disabled my screen lock, facelock and fingerprint too. Yet ,twrp started with unmodified system partition.
shafi1885 said:
brother, I haven't swtiched ROM and disabled my screen lock, facelock and fingerprint too. Yet ,twrp started with unmodified system partition.
Click to expand...
Click to collapse
System partition is ro=read only in /vendor/etc/fstab.qcom and even if you would try to make it writeble through that question in TWRP, it will remain read only
But scrambled Data and Internal memory has nothing with read only /system - again, it is because of TWRP must use the Android screen unlock/pin pass.
Try to set the unlock pin to something (not empty) in Android Settings, and test again
Sorry, I'm not following now who stated what above in his earlier posts, I'm not on Pro but plain Mi 9T, with Xiaomi.eu MIUI 12.6 A11 beta, TWRP 3.5.2-9, and everything works for me as described.
Also at the time of switching to Xiaomi.eu I of course had to Format Data
And immediately after flashing TWRP I always reboot to TWRP (somebody also debated about):
fastboot oem reboot-recovery
Screenshots from TWRP attached. Observe that TWRP decrypts user space 0 (default user) but fails to decrypt 999 (second user) - that is still not supported by TWRP. Because of that, backing up Data partition fails unless I delete (from the rooted Android or from TWRP) /data/extm folder (although it's empty I have to delete the folder) before backing up /Data in TWRP
zgfg said:
System partition is ro=read only in /vendor/etc/fstab.qcom and even if you would try to make it writeble through that question in TWRP, it will remain read only
But scrambled Data and Internal memory has nothing with read only /system - again, it is because of TWRP must use the Android screen unlock/pin pass.
Try to set the unlock pin to something (not empty) in Android Settings, and test again
Sorry, I'm not following now who stated what above in his earlier posts, I'm not on Pro but plain Mi 9T, with Xiaomi.eu MIUI 12.6 A11 beta, TWRP 3.5.2-9, and everything works for me as described.
Also at the time of switching to Xiaomi.eu I of course had to Format Data
And immediately after flashing TWRP I always reboot to TWRP (somebody also debated about):
fastboot oem reboot-recovery
Screenshots from TWRP attached. Observe that TWRP decrypts user space 0 (default user) but fails to decrypt 999 (second user) - that is still not supported by TWRP. Because of that, backing up Data partition fails unless I delete (from the rooted Android or from TWRP) /data/extm folder (although it's empty I have to delete the folder) before backing up /Data in TWRP
Click to expand...
Click to collapse
brother, twrp still not reading my internal storage even after I just gave one pin lock as you said. then , I flashed magisk 22.0 using OTG(pendrive). twrp showed done as same as youtube xda video. but, after rebooting, magisk manager is not there, only magisk app which was not opening. I installed root checker to check root and it said, device is not rooted. Please tell me brother what to do
I have just discovered, in magisk app, it says NO RAMDISK
so, I followed the official magisk website, it instructed to read instructions in xda, i came to xda, xda sent me the same page saying read the instructions there :'(
shafi1885 said:
brother, twrp still not reading my internal storage even after I just gave one pin lock as you said. then , I flashed magisk 22.0 using OTG(pendrive). twrp showed done as same as youtube xda video. but, after rebooting, magisk manager is not there, only magisk app which was not opening. I installed root checker to check root and it said, device is not rooted. Please tell me brother what to do
I have just discovered, in magisk app, it says NO RAMDISK
so, I followed the official magisk website, it instructed to read instructions in xda, i came to xda, xda sent me the same page saying read the instructions there :'(
Click to expand...
Click to collapse
First and foremost Format (not Wipe) the Data, and then also Wipe Cache. If you don't like, continue on your own and good luck
zgfg said:
First and foremost Format (not Wipe) the Data, and then also Wipe Cache. If you don't like, continue on your own and good luck
Click to expand...
Click to collapse
brother, if I format all the data, will it clear my rom too? or it's like factory reset? I am asking to know if I can boot back to my normal stock MIUI 12.5 .
and brother, I am sorry you felt like that, actually I meant I couldn't understand about "patching images" because my ramdisk is NO. I didn't understand the technical details of it. could you please help me?
brother, what will I do without XDA, I learnt a lot from XDA in last couple of days. I unlocked my bootloader, I installed twrp, without XDA, I can't survive on my own. Love this community and the people here.
shafi1885 said:
brother, if I format all the data, will it clear my rom too? or it's like factory reset? I am asking to know if I can boot back to my normal stock MIUI 12.5 .
and brother, I am sorry you felt like that, actually I meant I couldn't understand about "patching images" because my ramdisk is NO. I didn't understand the technical details of it. could you please help me?
brother, what will I do without XDA, I learnt a lot from XDA in last couple of days. I unlocked my bootloader, I installed twrp, without XDA, I can't survive on my own. Love this community and the people here.
Click to expand...
Click to collapse
It's like a factory reset.
Personal storage data and user installed apps will be deleted. The ROM itself will be untouched.
Try renaming the Magisk apk and change the file extension to .zip. Then flash the renamed file in TWRP.
shafi1885 said:
brother, if I format all the data, will it clear my rom too? or it's like factory reset? I am asking to know if I can boot back to my normal stock MIUI 12.5 .
and brother, I am sorry you felt like that, actually I meant I couldn't understand about "patching images" because my ramdisk is NO. I didn't understand the technical details of it. could you please help me?
brother, what will I do without XDA, I learnt a lot from XDA in last couple of days. I unlocked my bootloader, I installed twrp, without XDA, I can't survive on my own. Love this community and the people here.
Click to expand...
Click to collapse
Please take your time, do your homework, read guides here on XDA, read other Q)A threads here on XDA, all these things about formatting data (previously TWRP, etc) are described and snswered already in many orher posts
So this is really the last time I will respond you (unless I see something that I consider is really out of scope of the 'regular' knowledge that can be learned around).
Btw, when I obtained my Mi 9T, I spent full three weeks googling, reading and learning before I asked/posted my first question and started to bother the others
Hence, you can continue asking the basic things, but let somebody else answer you, I will ignore
Data is not System and by formatting Data you don't loose ROM but you loose all your apps, settings, configurations, personal files incl. photos, etc. Android will boot as the first time once again.
Hence do some backups (photos to PC, WhatsApp can be backed up from its Settings, etc) - again, google about if you are not familiar about backing up
1. ADB push does not work on production releases (MIUI).
2. Do "Format" and not "Wipe" the Data partition from twrp , it will fix your problem but you will lose all data on the phone.
Got the same problem, found a simple solution.
On your phone go to TWRP - Advanced - ADB sideload.
On your pc type
Code:
adb sideload something.zip
.

Categories

Resources