Related
Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta
You are the man!
Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.
Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.
I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?
its totally a new dev rom! the best out there! Love this rom!
How to add other languages, for example, russian?
So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
For some odd reason Tapatalk doesn't work on this ROM for me.
How do we root? Anyone know?
I've found this YOUTUBE link, but didn't test yet
EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?
Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.
This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.
All Praise and All Thanks To God
Things Required: Unlocked bootloader, TWRP file, Disable_Dm-Verity_ForceEncrypt.zip file, External SD card, adb and fastboot drivers installed in pc
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
2. Copy Disable_Dm-Verity_ForceEncrypt.zip in your External SD Card. Power off your phone by pressing power button, after your phone is powered off ,hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your external sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6. Install the Disable_Dm-Verity_ForceEncrypt.zip using twrp
7 .Reboot, Done!
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Please Note:
1. There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
2. Don't relock bootloader after flashing twrp, it might brick your device. (Don't use fastboot flashing lock)
3. You cannot restore preloader_a and preloader_b partitions using twrp, only you can backup the two partitions, so always uncheck these two partitions before performing a twrp restore.
4. Please don't use minimal adb and fastboot tool, use Latest ADB and Fastboot Installer tool , link is provided below.
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Links:
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Disable_Dm-Verity_ForceEncrypt.zip: https://zackptg5.com/android.php#disverfe
Latest ADB and Fastboot Installer: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
A. From adb:
adb reboot recovery
adb shell reboot recovery
B. From fastboot mode:
fastboot oem reboot-recovery
C. There is no way to boot to recovery using power + vol down button after unlocking your bootloader. Only above two methods will work. (Don't relock bootloader after flashing twrp, it might brick your device)
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
@osm0sis for his system_root mount support in AK3 which Disable_Dm-Verity_ForceEncrypt.zip uses
Nice Work
I will test soon
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
KSUBROTO said:
It didn't work
Click to expand...
Click to collapse
dont be stupid nova customizer you dont have rm3 phone all developer from realme device they know you scammer !!
Will we still see blank screen after 2 minutes of loading, or anything else?
Sounak Biswas said:
Will we still see blank screen after 2 minutes of loading, or anything else?
Click to expand...
Click to collapse
When twrp boots, it will be blank screen, so don't panic.
you have to wait for atleast 2 minutes before executing the next commands
Has anyone been able to flash supersu.zip through shell yet?
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Jion This https://t.me/joinchat/HrjmCBBex1F5cy9q0m7cQg
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Use magisk, https://forum.xda-developers.com/realme-3/how-to/rooting-guide-realme-3-t3927028
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Superuser on magisk .
I need scatter file
Make scatter file for realme 3 my rm3 is deadboot
johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
Please Download The Stock Rom inside You Get Scatter File Ok
johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
If it's soft brick or bootloop see this guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
if it's hard brick go to service center.
I am not sure how scatter file will help you recover from hard brick.
Here is the scatter file for mt6771 chipset:
https://drive.google.com/file/d/1pjIkb9xuq4WRFVh72V3V6eNfzdhRTk8L/view
Thanks Sir
jeffalaiza said:
Thanks Sir
Click to expand...
Click to collapse
Welcome sir
Work on ROM A.18 sir ?
hi sir, wolud you help me
what step should i do I got HARDBRICK realme 3?
I'm a newbie
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
CreateProcess failed: the system cannot find the file specified. (2)
error: Cannot generate image for userdata
Click to expand...
Click to collapse
Any advice or solution to rectify this problem?
TwelveMoon said:
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
Any advice or solution to rectify this problem?
Click to expand...
Click to collapse
Use adb platform tools..
I want to unlock the bootloader but in the application step I have waited more than 1 hour and the server has not shown success.
Can you share a link of video tutorial please.
fawazahmed0 said:
All Praise and All Thanks To God
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. power off your phone by pressing power button, now hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp-3.3.1-0-RMX1821.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6a. Copy and install Disable_Dm-Verity_ForceEncrypt_Quota_.zip in your phone using:
adb push Disable_Dm-Verity_ForceEncrypt_Quota_.zip /
adb shell twrp install Disable_Dm-Verity_ForceEncrypt_Quota_.zip
or
b. copy the Disable_Dm-Verity_ForceEncrypt_Quota_.zip in sdcard and install using twrp touch interface, then wipe dalvik, cache, data and format data.
6. Done!
There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
Disable_Dm-Verity_ForceEncrypt_Quota_.zip: https://www.androidfilehost.com/?fid=6006931924117924278
or download the latest version from here: https://zackptg5.com/android.php#disverfe
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
From adb:
adb reboot recovery
adb shell reboot recovery
From fastboot mode:
fastboot oem reboot-recovery
If you want to boot to recovery using power + vol down button, then you have to lock the bootloader using:
fastboot flashing lock
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
Click to expand...
Click to collapse
ROM manager shows that TWRP is my current recovery but I can't boot into TWRP recovery, I don't understand the issue.
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and
customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to
mash. The GUI is also fully XML driven and completely theme-able. You can change just about
every aspect of the look and
Click to expand...
Click to collapse
Prerequisites:
Code:
. Unlocked Bootloader
Installation instructions:
Recovery Install Method:
Simply download the TWRP-3.7.0_12-0 from twrp website and boot it using fastboot mode, steps are mentioned below
Fastboot Boot Method:
You will need the platform-tools from the Android SDK on your computer. Download only the platform-tools according to your device to get adb and fastboot binaries.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the twrp boot image from the link given below, and copy twrp.img file into the same folder as your adb and fastboot binaries and type:
Code:
fastboot boot twrp.img
You will be booted to TWRP, from there go to advanced and then click on "Flash Current TWRP"
REMEMBER: if the device waspreviously rooted, then root has been overwritten, you need to flash the magisk zip again to retain root
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Device Changelog
Version:3.7.0_12-0:
Initial Official Release
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads
Official TWRP Website
My Telegram TWRP Support Group:
https://t.me/pocof4_recoveriesCredits:
- TWRP Team
Sources
TWRP: https://github.com/TeamWin/android_bootable_recovery
Device Tree: https://github.com/TeamWin/android_device_xiaomi_munch
Kernel Tree: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/munch-s-oss
Status: Stable
TWRP: 3.7.0_12
reserved 1
reserved 2
Build will be live on twrp.me soon
Wow nice!
Build is live
Decrypting working? Will working on future Android 13 with decrypting? I know that dev received Android 13 already
Yes decrypting working fine, even on Android 13
When I updated yesterday, I immediately flashed it without losing data. For today's update, why doesn't it turn on, you have to turn on the new data format, is there the same or a solution
Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).
dreamdrake said:
Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).
Click to expand...
Click to collapse
If you already have your magisk_patched.img, you can choose which method you want:
1. with Fastboot + TWRP (temporary)
fastboot boot [drag and drop recovery.img]
flash your magisk_patched.img in boot partition + check "Flash to both slots"
reboot to system
2. only Fastboot
fastboot flash boot_a [drag and drop magisk_patched.img]
fastboot flash boot_b [drag and drop magisk_patched.img]
fastboot reboot
What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?
dreamdrake said:
What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?
Click to expand...
Click to collapse
When you check "Flash to both slots" TWRP will flash the makisk_patched.img to boot_a and boot_b.
I'm not sure, but if you don't check the box, TWRP will maybe flash to inactive slot and you are NOT rooted.
Edit: You can check which slot is active with adb shell getprop ro.boot.slot_suffix
Is it possible to make a backup of the installed rom with relative restore using this official twrp? If yes, which files to select
ok... i can't access to internal storage via pc. I formated data (type yes), rebooted to recovery again and my pc sees internal storage but there is no info about size and i can't copy files to it. It shows message something like "this device is disconnected". I tried to reinstall adb drivers, tried to restart my pc and it's not working. I used adb sideload to falsh ROM and after i booted to ROM, rebooted to recovery I can access internal storage via TWRP.
Runs super laggy with kernel compiled with gcc which is very strange and annoying.
Can't access storage with PC... Disabled and enabled MTP multiple times...
I had to flash ROM via OTG...
Hello community, first of all I clarify that I am using the google translator.
As the title says, my poco f3 has a hard brick, I was trying to flash the miui global rom via fastboot(stock rom was global miui for turkey) but an error occurred in the process (the same as attached in the image), at that moment I got scared because the phone did not start the system.
The bootloader was obviously unlocked, I tried to recover with XiaoMitool but nothing, I couldn't flash super.img either in Xiaomiflash, then I decided to download its stock rom and redo the process but it failed.
Before all this I had tried to install TWRP or OrangeFox but none could be installed, I only got to the TWRP boot but the option to flash the current TWRP did not appear and it did not recognize the internal memory and the OTG with the zip. Right now it only shows the POCO logo and goes directly to fastboot mode.
I'd appreciate your help.
Edit: It does not have the recovery stock
edixon2021 said:
Hello community, first of all I clarify that I am using the google translator.
As the title says, my poco f3 has a hard brick, I was trying to flash the miui global rom via fastboot(stock rom was global miui for turkey) but an error occurred in the process (the same as attached in the image), at that moment I got scared because the phone did not start the system.
The bootloader was obviously unlocked, I tried to recover with XiaoMitool but nothing, I couldn't flash super.img either in Xiaomiflash, then I decided to download its stock rom and redo the process but it failed.
Before all this I had tried to install TWRP or OrangeFox but none could be installed, I only got to the TWRP boot but the option to flash the current TWRP did not appear and it did not recognize the internal memory and the OTG with the zip. Right now it only shows the POCO logo and goes directly to fastboot mode.
I'd appreciate your help.
Edit: It does not have the recovery stock
Click to expand...
Click to collapse
try booting twrp via fastboot and then format data.
Obviously you'll lose your data, but it might give you access to your phone back.
Good morning.
Try to enter with quiet fastboot mode, both in twrp and orange fox, it's the same process. Put the phone in fastboot mode and then open minimal adb.
1. Put the fastboot devices command, the serial number of your mobile should appear on the command screen.
2. Put the command fastboot boot orangefox.img or twrp.img, take a good look at the file you have downloaded, to make the boot easy, it has to be an .img image and not a zip file.
3. If you can get into both fastboot and orangefox, please format the data.
4. Try to flash the miui stock rom with the same process where the error appeared, remember that this rom (it worked for me) has to be the rom for the poco f3 fastboot, since there are 2 versions (I think I have seen this) one which is fastboot and another which is not.
LUCK!
ShAnGoS said:
Good morning.
Try to enter with quiet fastboot mode, both in twrp and orange fox, it's the same process. Put the phone in fastboot mode and then open minimal adb.
1. Put the fastboot devices command, the serial number of your mobile should appear on the command screen.
2. Put the command fastboot boot orangefox.img or twrp.img, take a good look at the file you have downloaded, to make the boot easy, it has to be an .img image and not a zip file.
3. If you can get into both fastboot and orangefox, please format the data.
4. Try to flash the miui stock rom with the same process where the error appeared, remember that this rom (it worked for me) has to be the rom for the poco f3 fastboot, since there are 2 versions (I think I have seen this) one which is fastboot and another which is not.
LUCK!
Click to expand...
Click to collapse
Hello, i had already tried to boot with twrp.img but without success, the good news is that I have already recovered it and the solution was as simple as taking the flash_all.bat from the rom and it could already be in any version of miui.
What I don't understand is why it hadn't worked with XiaoMitool and Xiaomiflash, and I still can't install TWRP because it doesn't recognize internal memory and OTG.
Anyway thanks for your help.
edixon2021 said:
Hello, i had already tried to boot with twrp.img but without success, the good news is that I have already recovered it and the solution was as simple as taking the flash_all.bat from the rom and it could already be in any version of miui.
What I don't understand is why it hadn't worked with XiaoMitool and Xiaomiflash, and I still can't install TWRP because it doesn't recognize internal memory and OTG.
Anyway thanks for your help.
Click to expand...
Click to collapse
Glad you got it sorted, When installing a MIUI stock rom remember to put the Firm wear folder on your C: Drive and remove any spaces from title,
As for TWRP & Orangefox recoverry, i installed these in fast boot mode and use "Temporary Recovery" by downloading RUN_TWRP-Orange Fox FIXED.bat /unzipping/ and running the "RUN_TWRP-Orange Fox FIXED.bat File, once in temporary OF Recovery you can choose to make OF Recovery permanent by installing current version of OF from within OF, Check my post on the EVO-X Thread post 20,
you will also find my post regarding OTG issues,
--------------------------------------------------------------------------
OTG is no longer Now working with Orangefox recovery.
To overcome the OTG showing 0MB or .., remove the OTG adaptor,
reboot into OF Recovery, re-connect your OTG adaptor and
tap ☰ in the bottom right of the main screen to open the MENU,
open Mount, tap USB-STORAGE (wait 5 seconds) the (USB-STORAGE background will turn black), shortly after the check box will enabled, many thanks to Rafsf for the Workaround.
I hope this helps a bit
johnr64 said:
Glad you got it sorted, When installing a MIUI stock rom remember to put the Firm wear folder on your C: Drive and remove any spaces from title,
As for TWRP & Orangefox recoverry, i installed these in fast boot mode and use "Temporary Recovery" by downloading RUN_TWRP-Orange Fox FIXED.bat /unzipping/ and running the "RUN_TWRP-Orange Fox FIXED.bat File, once in temporary OF Recovery you can choose to make OF Recovery permanent by installing current version of OF from within OF, Check my post on the EVO-X Thread post 20,
you will also find my post regarding OTG issues,
--------------------------------------------------------------------------
OTG is no longer Now working with Orangefox recovery.
To overcome the OTG showing 0MB or .., remove the OTG adaptor,
reboot into OF Recovery, re-connect your OTG adaptor and
tap ☰ in the bottom right of the main screen to open the MENU,
open Mount, tap USB-STORAGE (wait 5 seconds) the (USB-STORAGE background will turn black), shortly after the check box will enabled, many thanks to Rafsf for the Workaround.
I hope this helps a bit
Click to expand...
Click to collapse
Thank you very much friend you deserve heaven, finally I was able to install OF permanently.