{
"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"
}
OrangeFox Recovery UNOFFICIAL
By @iamshubh69
Fw: Realme UI 2.0
Download: Click here
Changelog:
- build for Realme ui 2.0
Bugs:
- For working of OTG, plug it before booting to recovery
- Decryption in a12
Notes:
Only for Realme UI 2.0 Firmware
Guide to flash:
1. Unlock bootloader using the Realme UI 2.0 Deeptest tool
2. Enable usb debugging
3. adb reboot bootloader
4.fastboot --disable-verification flash vbmeta vbmeta.img (vbmeta 4KB)
5. fastboot flash recovery recovery.img
Credits:
Thanks to @sarthakroy2002 for trees and help
What do you mean by "Decryption in a12"? Like the OS fails to read an encrypted partition, resulting in a brick if we encrypt our drive? Or rather it refuse to decrypt the drive in case you don't want to be encrypted anymore? Or something else? Wasn't it already denied widely to unencrypt an Android installation from when it has been done?
The phone would not the able to perform any OTG anymore if we don't plug it to the computer before the booting preceding the installation of this recovery? Or an OTG function into this recovery will not work for the session if not plugged before booting? Or something else?
Can you add a part who warn about potential data loss? And redirect to tutorials about how to backup the most possible of the phone (app data and settings, android data and settings, kernel, RAM/ROM, phone personal identification files, anything that could help in case of brick and that could help restoring as most as possible thing like before any manipulation)?
dd
pingopower said:
What do you mean by "Decryption in a12"? Like the OS fails to read an encrypted partition, resulting in a brick if we encrypt our drive? Or rather it refuse to decrypt the drive in case you don't want to be encrypted anymore? Or something else? Wasn't it already denied widely to unencrypt an Android installation from when it has been done?
The phone would not the able to perform any OTG anymore if we don't plug it to the computer before the booting preceding the installation of this recovery? Or an OTG function into this recovery will not work for the session if not plugged before booting? Or something else?
Can you add a part who warn about potential data loss? And redirect to tutorials about how to backup the most possible of the phone (app data and settings, android data and settings, kernel, RAM/ROM, phone personal identification files, anything that could help in case of brick and that could help restoring as most as possible thing like before any manipulation)?
Click to expand...
Click to collapse
dude can you just email me on [email protected] I am tired of reading this long threads
iamshubh69 said:
dd
dude can you just email me on [email protected] I am tired of reading this long threads
Click to expand...
Click to collapse
Sure thing, but I think people maybe have those questions too. I don't ask them just for me
Bro link not working
Related
I've MeLE A200 HTPC (single core A10S SoC, FW Android 4.0.4 v1.2b rooted, Board HMC-G41A03WL). Recently after installing a small app, something went wrong, the box Internal Storage changed from 10% full to 0.0B, meaning its not mounted anymore on device reboot. I've no access to previously installed packages, and can't install any new package that requires access to Internal Storage ( Data partition) or root access. I tried soft recovery from Settings and Hard recovery by pressing the device button, but they didn't fix the issue.
I earlier installed CWM ROM Manager, but was unable to find Recovery image for this device. Wanted to re-install original firmware, but official links are dead. Mele Support never answers any emails, and they block registration emails on the company forum, so no way to ask a question on the forum. They posted an updated firmware v1.3 for "A200 upgraded version" device on the forum, but that device hardware has 1GB RAM, and mine only 512MB, and there may be other differences. So I'm not sure, it will boot, and if it doesn't I'll get a brick.
I installed Terminal package, and can access the box partitions from PC using ADB via Wi-Fi, since USB Recovery option is not showing in the device Settings, and Mele provides no USB Windows driver. I can see that Data, Cache, and probably some other partitions are not mounted. I mounted them OK manually, but lost Wi-Fi access after that, probably because the device lost access to Data folder on root it was using instead of Data partition on NAND.
This picture has proper links, since I can't post them here so far:
{
"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"
}
My questions are:
1. Can anyone point to a link to A200/A210 original firmware? I need:
A200_Mele_HTPC_20130117_V1.3.1
A200 Mele_HTPC_ Home _20121220_V1.2
2. What are my chances to get a brick, if I flash the above mentioned v1.3 for "A200 upgraded version" device? Can I unpack & modify that firmware to fit my device - how?
A200升级版_A10_SDK1.6_V1.3_20140715.img
3. If I flash that FW to the device, will it erase original Recovery partition? If Yes, and the device can't boot after flash, could I recover it by pressing Hard Recovery button? Does it mean, Hard Recovery partition is stored separately in NAND, and never erased when a new FW is flashed from SD Card?
4. May be I can change some automount rules via ADB? So far, I found that /etc/vold.fstab has no automount rules for any system partitions, only for SD Card and USB partitions. So what file contains automount rules for Data and Cache?
5. What else can lead to Data not being mounted, what else can I check or do to fix the device? I can post some debug and dmesg logs saved by the system if needed. How I can fully backup or recover the device from full backup in this situation?
Update: the only resolution I found was reinstalling factory firmware procured from Mele upon request.
Does your device have a custom recover? Flash a new rom
This is the Xiaomi Mi 9T and Xiaomi Redmi K20's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
good work
Thank you for the effort
i love your twrp mi 9T, please update for ever
Can this actually unlock the bootloader with out waiting for xiaomi??
awsan said:
Can this actually unlock the bootloader with out waiting for xiaomi??
Click to expand...
Click to collapse
Unfortunately not.
does unlocking bootloader takes time and does it require mi account?
mona356 said:
does unlocking bootloader takes time and does it require mi account?
Click to expand...
Click to collapse
Yes to both, at least a week and a mi account and also you need mobile data because Xiaomi won't let request a BL unlock with WiFi for some reason
adb unauthorized when plug in, what to do guys? pls help
Kheppy said:
adb unauthorized when plug in, what to do guys? pls help
Click to expand...
Click to collapse
Just accept from the phone the authorization
can it flash stock recovery?
hey there.
so here i am, after purchasing a box/dongle of sort , which allowed me to read and backup the partition that i had on the phone i received while not booting.
the phone is an MTK xiaomi redmi note 4 .
i did backup all the partitions before flashing it.
the phone was constant boot looping , was not solved by flashing it (not cn dev firmware or any other firmware) it did not even went to fastboot.
i have heard that after android 5? the userdata.bin were encrypted .
1, im not to sure if the rumors are true.
2, how its possible to decrypt it ?
3, if i flash the same partition to a working phone, would i be able to read the data out of it ? (note that the answer to that question was yes after asking some one, however it seems difficult to understand how, i mean if there is a key to decrypt the partition shouldnt be in the phone itself who encrypt it ?) hope u guys can clarify if its possible to so , or its just BS.
now if the keys are somewhere can i extract them some how and decrypt the partition so i can get the data out ?
i did try to open it with 7z , ftk imager ..
nothing could open this up.
this is how it looks like
{
"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"
}
alot of the partitions are fill with
Code:
G..Â.ªÕ.E)ÎJØÁõV
Code:
470305C290AAD5154529CE4AD8C1F556
i mean i can clearly see that its encoded and see the partern .
i did try to flash twrp, but that did not work (because fastboot does not comes up.)
anyhow , this is it.
thanks for the help in advanced .
(in short how can i save the data of this phone, cheers)
@doesitburn
I think a convenient way to remove the encryption from your Android phone is
Go to Settings-->Security
Then under "Credential Storages" click on "Clear all credentials"
jwoegerbauer said:
@doesitburn
I think a convenient way to remove the encryption from your Android phone is
Go to Settings-->Security
Then under "Credential Storages" click on "Clear all credentials"
Click to expand...
Click to collapse
im not sure u read my post ;D
its boot looping and wont turn on properly so cant do that .
doesitburn said:
im not sure u read my post ;D
its boot looping and wont turn on properly so cant do that .
Click to expand...
Click to collapse
It was just a hint for everyone how to avoid the mistake you made. :laugh:
It is the whole point of disk encryption to prevent unauthorized booting. A once encrypted disk/img can't get decrypted by external means as you are trying to do now. May be FBI has the appropriate tools ... That's probably also the reason why Google will, as announced in spring 2019, in the end, remove adb backup/restore from Android.
IMHO you have no chance.
what about flashing the backup into a new phone tho ?
will this help me ?
??
@doesitburn
Propably not
Sent from my Willeyfox Swift using Taptalk
Hi,
Newbie here so go easy!
Ive been changing the settings on an imported chinese tablet such as boot image, remove bloatware, download apps required, etc and it works great. However, I want to be able to create a full image of one tablet and transfer that to other tablets I buy so I dont have to manually do this every time. Basically a full backup and restore of everything on the tablet.
Can anyone assist on the best process to do this.
Thanks
If device's Android got rooted then you can perform a full NANDroid backup by means of either TWRP or FlashFire. FYI: ROOT is required for mounting all partitions as RW.
TWRP:
{
"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"
}
Flashfire:
Full article here:
How to Backup Android Device Completely 2023 (Updated)
If you plan to unlock bootloader or want to flash custom ROM, this guide is for you. In today's article, I will show you how to Backup Android Device
www.rootingsteps.com
Hi,
Thanks for the help.
The device is rooted but im struggling to get a TWRP recovery image for this tablet as its a chinese import. However, its a Rockchip RK3288 tablet. Any help with where to find correct version?
Also when I down loaded flash fire its starts up but crashes after a few seconds?
duckett100 said:
Also when I down loaded flash fire its starts up but crashes after a few seconds?
Click to expand...
Click to collapse
Do a LOGCAT to get the reason why.
[Tutorial] How To Logcat
Here's how to use logcat: There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app: Here are two good examples are either: aLogcat or Catlog I prefer...
forum.xda-developers.com
Hi, I worked out why flash fire was crashing, but some of the items in the app are greyed out so it doesn't allow a back up. I think its because I still have the standard recovery that came with the tablet instead of something like TWRP. And I cant find one online that will work.
Are there any other ways to do a full back up programmatically?
Hey,
Recently I was able to extract the boot.img and recovery.img from the boot.img itself, by understanding its system. I managed to build a TWRP for it, but stuck on the logo screen. ADB shell can be accessible with root.
Device Tree: https://github.com/Malvik298/hoki_twrp_device_tree
Feel free to suggest changes to the device tree. Its still not perfect
EDIT: Issues Fixed. Download Below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixed. Managed to build the twrp.
Here is the TWRP Image.
Bugs:
Internal Storage not detected.
You tell.
Goodjob.. hope we will having more development soon
Is the sideload working?
And when in twrp, able to transfer file from pc?
My build have this bugs
nelikp said:
Is the sideload working?
And when in twrp, able to transfer file from pc?
My build have this bugs
Click to expand...
Click to collapse
Had some issues while dumping partition. But magisk installed successfully.
nelikp said:
Is the sideload working?
And when in twrp, able to transfer file from pc?
My build have this bugs
Click to expand...
Click to collapse
Haven't tried all this yet, had some issue with my adb on ubuntu. Internal storage is not detected yet, will try to fix that first at sometime. Dont have much time right now to properly develop it. If Possible can you share your configs you used to build your twrp ?
Mine oppo watch ( beluga )
Could you provide a step-by-step guide how to unlock bootloader / installing TWRP on it and/or building TWRP images for the fossil gen 6 to reproduce your steps ?
did the dirty-pipe exploit work on gen 6 ?
BlackTec87 said:
Could you provide a step-by-step guide how to unlock bootloader / installing TWRP on it and/or building TWRP images for the fossil gen 6 to reproduce your steps ?
did the dirty-pipe exploit work on gen 6 ?
Click to expand...
Click to collapse
The bootloader unlock and recovery flashing steps are same as the android phone devices. Install the required drivers for accessing fastboot and fastboot binaries to interact with the device bootloader. For building images, u can refer to guides available on the forum. For device tree, clone the repo given above. and for twrp use can you https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni (Android/twrp 9 branch). Haven't tried the exploit yet.
was any hardware intervention/case opening required for the initial access ? of you've just used standard cable ?
Used the standard cable