Related
/*
* I am not responsible for bricked devices, dead SD cards,
*thermonuclear war,
or the current economic crisis caused by you following these
directions.
*YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I willlaugh at you.
*/
**********************************************
I have readed lot about how to flash custom ROM or stock ROM on Android device readed some comments that many people wiped their internal storage while installing ROM.
i found a Very Safe and easy way to do this.
First of all you need these things.
1.Philz Touch recovery. OR TWRP.
For Your device
2.Flashify app from Play store
https://play.google.com/store/apps/details?id=com.cgollner.flashify
(For 1time process)
If you have PC then skip 2nd.
3.Only for PC users
https://forum.xda-developers.com/showthread.php?t=2588979
If you have ADB installed skip this also.
After downloading follow my steps.
***********************
*Mobile users NO PC*
***********************
1. Place Your ROM in Sdcard .
Flash the downloaded philz touch recovery.img OR TWRP recovery with flashify to recovery partition..>
[Caution:->Do this carefully it can harm device if you didn't flashed right partition]
2.Boot to recovery.
3.Select Clean to install new ROM. (For Philz)
For TWRP :-> Click Wipe , Advanced wipe and Select Dalvik Cache, System, Data and Cache then swipe to wipe..
Wait for completing...
4. Select install zip and select install from external sdcard.
5. Find your ROM and flash.
if you want to install Gapps.
Flash the zip file of gapps after installation of ROM .
Done
**********************************************
*****************
*For PC USERS *
*****************
1.Download ADB and fastboot drivers.
(link is given above only for Windows)
if you are using linux you can find adb and fastboot in software manager App.
And
Philz Touch Recovery.img Or TWRP recovery.img
Place in a folder and open that folder press
Shift and Right click and select open in CMD. (Without selecting anything ((click on empty place inside folder)))
2.Open CMD / terminal.
Type:-> "adb reboot bootloader"
Without quotes abd Press Enter.
[Remember device connected with usb and usb debugging turned on)
3. Type :-> " fastboot flash recovery 'Name of your recovery"
in my case it is recovery.img
So example:-> "fastboot flash recovery recovery.img"
Without quotes and Press enter.
Flashing done..
(You can skip this step if you don't want to install Custom recovery in your phone.
Simply follow 4th step)
4. Type:-> fastboot boot recovery.img
Phone will boot into Recovery.
5.Select Clean to install new ROM. (For Philz)
For TWRP :-> Click Wipe , Advanced wipe and Select Dalvik Cache, System, Data and Cache then swipe to wipe..
Wait for completing...
6.Select install and select install form external sdcard.
Choose ROM and it will flash.
if you want to install Gapps.
Flash the zip file of gapps after installation of ROM .
Needed Any Further Help feel free to comment below.
And
if you find it useful Press Thanks button.
Credits:
@Snoop05 for ADB
@cgollner for Flashify.
Very nice guide
But i have a doubt :/
How philz will work for every smartphone?
sohamsen said:
Very nice guide
But i have a doubt :/
How philz will work for every smartphone?
Click to expand...
Click to collapse
It is available for almost every phone i think.
Just need to search.
@[email protected] said:
It is available for almost every phone i think.
Just need to search.
Click to expand...
Click to collapse
i have 3 phone but no one have philz
sohamsen said:
i have 3 phone but no one have philz
Click to expand...
Click to collapse
Thread Updated for TWRP
UNOFFICIAL Omnirom
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.
*/
Instructions
* Backup everything if something goes wrong
* Wipe System, Cache and Data
* Install zip-file
* Flash oem-partition, see second post
All the source code for the os is available in the Omnirom Github repo.
What works?
Data (2g, 3g and lte)
Calling
Torch
Installation of Gapps
Camera
WIFI
Known Issues
NFC doesn't work
Downloads
My mediafire -folder
Thanks humberos, jerpelea, kholk, omnirom devs and many others.
XDA:DevDB Information
Omnirom, ROM for the Sony Xperia X Compact
Contributors
DJHasis
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2017-10-29
Last Updated 2017-12-04
Until Sony updates their Firmware to allow flashing of oem partition, this is a workaround to flash this partition thru TWRP recovery and using dd.
Download and unzip SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.zip from https://developer.sonymobile.com/open-devices/list-of-devices-and-resources/
Create a sparse oem.img from the downloaded binaries.
Code:
$ simg2img SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img oem.raw
Then flash the oem partition (workaround, until Sony updates stock image with oem partition writable)
Boot to TWRP recovery by powering off the phone completely, hold VOL-DOWN and POWER and wait for TWRP boot.
Or, fastboot boot twrp.img
Code:
$ adb root
$ adb push oem.raw /sdcard/
$ adb shell
# dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39
Thanks NielDK for the instructions https://forum.xda-developers.com/showpost.php?p=74130466&postcount=2
great job, man!!! Ill give it a try asap! thanks a lot!
Do you need to flash the OEM image to boot to system or it is just made to boot to twrp?
XperiaGUY47 said:
Do you need to flash the OEM image to boot to system or it is just made to boot to twrp?
Click to expand...
Click to collapse
To boot to system.
Sony hasn't updated the bootloader to support oreo so we need to manually update the oem partition.
DJHasis said:
To boot to system.
Sony hasn't updated the bootloader to support oreo so we need to manually update the oem partition.
Click to expand...
Click to collapse
But can i do it with adb n fastboot tool too? Or its not going to work?
XperiaGUY47 said:
But can i do it with adb n fastboot tool too? Or its not going to work?
Click to expand...
Click to collapse
I haven't much used fastboot so I don't know how well adb works with fastboot. I just booted to twrp and used adb like in the instructions.
Of course you don't need adb if you put the raw-file on the sd-card directly with your computer. Then put the card to your phone. Boot to twrp and use twrp's terminal to write "dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39" .
DJHasis said:
I haven't much used fastboot so I don't know how well adb works with fastboot. I just booted to twrp and used adb like in the instructions.
Of course you don't need adb if you put the raw-file on the sd-card directly with your computer. Then put the card to your phone. Boot to twrp and use twrp's terminal to write "dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39" .
Click to expand...
Click to collapse
Ok, but can you add the oem.raw image here because i am such a newbie. I haven't just touched the OEM stuff so i don't know much. So as i understand:
I need that oem.raw image and twrp
And then boot into twrp
Go to terminal
Write: if=/sdcard/oem.raw of=/dev/block/mmcblk0p39
Push enter
Reboot
And no sony logo stuck and boots right into omni?
(Edit) and put the oem.raw to /sdcard/
XperiaGUY47 said:
Ok, but can you add the oem.raw image here because i am such a newbie. I haven't just touched the OEM stuff so i don't know much. So as i understand:
I need that oem.raw image and twrp
And then boot into twrp
Go to terminal
Write: if=/sdcard/oem.raw of=/dev/block/mmcblk0p39
Push enter
Reboot
And no sony logo stuck and boots right into omni?
(Edit) and put the oem.raw to /sdcard/
Click to expand...
Click to collapse
So after you have backed up every thing.
You need to wipe the system and data with twrp.
Then you can install my zip-file with twrp.
Then you need to make the oem.raw file like in the instructions with your pc.
Then you can copy that file to your sd card.
After that you can boot to twrp, open the terminal and write this " dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39 ". And push enter.
After that you can reboot your phone and every thing should work .
New build uploaded.
Mainly bug fixes for kugo and parts of omnirom.
@DJHasis Some people over at the [Nougat 7.1.X][X Compact - F5321] Android Open Source Project thread were discussing the green camera issue, thought it might help you figure out the issue...
Sony has updated the Vendor image. It contains alot fixes and now camera works.
I downloaded it and converted it. Every one can download it from my mediafire-folder.
Hey, Thanks for your Work. Is it usable AS daily Driver ?
StarSix01 said:
Hey, Thanks for your Work. Is it usable AS daily Driver ?
Click to expand...
Click to collapse
I've been using for almost two weeks.
Sometimes it might crash but devs are improving the code quite fast and the latest version is quite stable.
I'm compiling a new version on semi daily basis so you'll get the latest changes quite fast.
harryharryharry said:
@DJHasis Some people over at the [Nougat 7.1.X][X Compact - F5321] Android Open Source Project thread were discussing the green camera issue, thought it might help you figure out the issue...
Click to expand...
Click to collapse
Thanks for telling me about it. I read the post and I now know that the camera issue has been fixed.
New build uploaded. More bug fixes.
Hi! After a few days using, this rom, heres my "report":
- First boot time is so long, so be patient until it finished his work.
- Camera works perfectly with the roms cam software, there are 20,3MPx and the Automata focus continously, picture taking about a minisec.. self cam works to. But, I think the pictures a little dark...
- I found an "error".. If i set up the omni alarm and choosed the alarm sound to " random music ", it cant play any mp3 from my sd card. The phones internal storage play works good, but not from sd card...
- Supersu 2.82 SR5 zip did good the root thing
- and a big headcache... Google play... I can't install any of them. I tried lot of them. OpenGapps mini, micro, pico... Every time when i try to set up my account, its just "checking info ", and nothing else, just force stop after a few minutes. I tried it after a clean install. I tried adter root. I tried immediately after omni zip + raw combination. None of them work for me...
- about battery life, i think its normal, but i used it withouth google apps... So not many sync was the background...
- wifi doesn't work, it's simple not turning on
Anyway, i like it, i think after some time, it will be good as Omni 7.1.2. Keep up the good work OmniTeam! And thanks for your homemade to!
Hey there,
Is wifi working now?
Regards, Chris
dhchris said:
Hey there,
Is wifi working now?
Regards, Chris
Click to expand...
Click to collapse
Hi!
On 11.04 the wifi doesn't turn on. Its not working. On the 11.08 I don't try it. BUT...
I've got a working gapps. I don't really know how to do that, but The steps was:
After wipe data, system, cache, etc then flashed Omnirom homemade zip, after that dd the raw image. Then before bootes up i flashed " A-GAPPS-arm64--8.0-01102017.zip ", then supersu latest SR5. After boot, the gapps setup FC. Then dirty flash homemade.zip after that another gapps, what was " open_gapps-arm64-8.0-nano-20171104.zip ", then came the supersu, and then went to reboot. Now a little more time was the boot than before. After its boot up normal i've got working google account setup, and orher google things. Why i do that now? Because until "A-Gapps" the google account setup just show "checking info" screen, and never goes on. After "A-gapps" its immadietly go to FC. Just the "a-gapps" dirty flash doeant help. The whole process again with "a-gapps" dont. Just that if i flashed second time an open nano version...
I hope its help if somebody got similar problem.
lba810701 said:
Hi!
On 11.04 the wifi doesn't turn on. Its not working. On the 11.08 I don't try it. BUT...
I've got a working gapps. I don't really know how to do that, but The steps was:
After wipe data, system, cache, etc then flashed Omnirom homemade zip, after that dd the raw image. Then before bootes up i flashed " A-GAPPS-arm64--8.0-01102017.zip ", then supersu latest SR5. After boot, the gapps setup FC. Then dirty flash homemade.zip after that another gapps, what was " open_gapps-arm64-8.0-nano-20171104.zip ", then came the supersu, and then went to reboot. Now a little more time was the boot than before. After its boot up normal i've got working google account setup, and orher google things. Why i do that now? Because until "A-Gapps" the google account setup just show "checking info" screen, and never goes on. After "A-gapps" its immadietly go to FC. Just the "a-gapps" dirty flash doeant help. The whole process again with "a-gapps" dont. Just that if i flashed second time an open nano version...
I hope its help if somebody got similar problem.
Click to expand...
Click to collapse
I installed open gapps pico and I didn't have any issues. Also I didn't install supersu, instead I installed Magisk Manager and I don't have any root issues.
Wifi doesn't work and Sony's people are working on it.
Here every one can see the situation for our phone https://developer.sonymobile.com/open-devices/current-platform-functionality/#8956
THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
Code:
/*
* 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.
*/
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
{
"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"
}
Grab these two files (Big Thanks to @mac12m99, @33bca (Offain on AFH) XDA Profile
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
Code:
adb reboot bootloader
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2. Boot up that TWRP.img file you downloaded above in this color
Type:
Code:
fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP
2a. Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Code:
fastboot flash aboot aboot_9.6.4.img
Then type:
Code:
fastboot reboot
4. Afterwards you shall go back to bootloader quickly
Type:
Code:
fastboot erase system
Type:
Code:
fastboot erase userdata
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
Code:
fastboot flash system GSI.img
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
Code:
fastboot flash userdata userdata.img
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .
reserved
Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks
GaryFisher88 said:
Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks
Click to expand...
Click to collapse
Not yet released to do so. Try the one from the dump.
Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter
It worked out the way you did.
only does not work for gcam and fingerprint reader
junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
If you have goodix fp yes need to install daisy_global_images_V9.6.11.0.ODLMIFF first but If you have fpc fingerprint no need , work in pie base stock
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse
Flavien125 said:
Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter
Click to expand...
Click to collapse
junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse
Everything works for me on RR at least
InfinityXDA said:
Everything works for me on RR at least
Click to expand...
Click to collapse
yes, for me too now
Except the notch
When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Ithao said:
When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?
Click to expand...
Click to collapse
You must completely erase system with
Code:
fastboot erase system
and
Code:
fastboot erase userdata
and then flash the new version of RR
Code:
fastboot flash system “rr.img”
and reflash the userdata.img
Code:
fastboot flash userdata “userdata.img”
Otherwise you can’t update the stock version of the ROM that came with the device unless you provide a full store of 10.0.4.0 and test RR from there
The stable version of the stock ROM for RR is 10.0.3.0.
rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
Did you switch to RR from 10.0.4.0
rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
InfinityXDA said:
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Click to expand...
Click to collapse
try Genom kernel
i had included autofix for wifi)
eremitein said:
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
try Genom kernel
i had included autofix for wifi)
Click to expand...
Click to collapse
I have no problems what so ever I went to RR from 10.0.3.0!
can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader
barumbads said:
can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader
Click to expand...
Click to collapse
Use the 10.0.3.0 userdata file.That's what i used too
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
InfinityXDA said:
THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
Grab these two files (Big Thanks to @Zerovoid from 4PDA, @Seryioo, and @mac12m99)
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Original Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2.Boot up that TWRP.img file you downloaded above in this color
Type:
It would boot into TWRP
2a.Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Then type:
4. Afterwards you shall go back to bootloader quickly
Type:
Type:
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .
Click to expand...
Click to collapse
I have installed the gsi and it's working perfectly but now i wabt to get twrp on the phone how do i do it(i don't have encryption)?
a lot of thank for that.... iam waiting for that...lots of thank you admin...
If something goes wrong can we flash stock ROM and get the phone fixed? Does resizing the system/data partition affect the process of recovering the phone?
Code:
/*
* Your warranty is now void.
*
* We're 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 recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
With data decrypt you can flash custom roms in recovery. In the near future there will be.
Notes:
* Data partition and Internal storage will be formatted (for decryption)
* Tested with latest MIUI 12.5.3.0
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* ymdzq - for OFRP builder
* [email protected] & [email protected], [email protected] & [email protected] - for DisableForceEncryption
FEATURES
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Flashlight
* Password, torch, led
* Support for Miui and Custom ROMs
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
DOWNLOADS
Github download site: OrangeFox-21.05.02-Unofficial.zip (atom also use this)
Googledrive download site: DisableForceEncryption.zip
Google download site: Android SDK Platform-tools 31.0.2
REQUIRES
* Redmi 10X 5G (atom) or Redmi 10X Pro (bomb) devices with android 10 or 11.
* Bootloader unlocked and USB debugging enabled.
* PC/Laptop with Xiaomi driver installed.
INSTALLATIONS
1. Download the OrangeFox zip to your pc. Extract and get img file.
2. Reboot device and enter into fastboot mode.
3. Connect device to pc via usb cable.
4. Extract Android SDK Platform-tools and copy img file into this folder. Run cmd...
5. Flash img file: fastboot flash recovery OrangeFox-21.05.02-Unofficial-bomb.img
6. Flash nulled vbmeta: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
7. Reboot to recovery: fastboot boot OrangeFox-21.05.02-Unofficial-bomb.img
8. If device not reboot to recovery automatically, press volume up + power at reboot.
9. Format data partion and Internal storage in OrangeFox. It will remove all your app data, gallery, sms, contacts,... Make sure backup first.
10. Copy DisableForceEncryption.zip to storage device. Install DisableForceEncryption.zip. Reboot to recovery again and check.
11. Enjoy!
Version Information
Status: Stable
Current Stable Version: R11.1
Stable Release Date: 2021-05-05
Created 2021-07-25
thank you for your great work
thanks，make custom rom
love u so much
thanks for your work. where's the vbmeta file?
joerusama said:
thanks for your work. where's the vbmeta file?
Click to expand...
Click to collapse
You can use stock vbmeta.img.
Just flash using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after flashing it. when i reboot will the recovery be fox twrp or still redmi recovery
hoangx2x said:
after flashing it. when i reboot will the recovery be fox twrp or still redmi recovery
Click to expand...
Click to collapse
when I unzip the twrp file, its name is recovery.img . do i need to rename it to "OrangeFox-21.05.02-Unofficial-bomb.img"???
hoangx2x said:
when I unzip the twrp file, its name is recovery.img . do i need to rename it to "OrangeFox-21.05.02-Unofficial-bomb.img"???
Click to expand...
Click to collapse
Does not matter the name of it.
VD171 said:
Does not matter the name of it.
Click to expand...
Click to collapse
it work , thanks , but i need rename
Hi guys, I just want to ask if this will replace the stock recovery of miui permanently, because on my previous experience, flashing custom recovery and booting to the stock rom, the stock miui recovery will replace the custom recovery .
may i ask where is the vbmeta? it keeps on saying there is no vbmeta on the directory. i dont' have the stock vbmeta. please help
SirruxKyrios said:
may i ask where is the vbmeta? it keeps on saying there is no vbmeta on the directory. i dont' have the stock vbmeta. please help
Click to expand...
Click to collapse
you can get it in the zip file of the rom
Hello, can you help me? which would be the steps to install the beta of miui and magisk without losing the recovery orengefox. I could already install the beta rom but I cannot install magisk, because when I install the beta rom it removes orangefox and I can no longer install magisk. and thanks for the great contribution
alucard2409 said:
Hello, can you help me? which would be the steps to install the beta of miui and magisk without losing the recovery orengefox. I could already install the beta rom but I cannot install magisk, because when I install the beta rom it removes orangefox and I can no longer install magisk. and thanks for the great contribution
Click to expand...
Click to collapse
I used this one, all seems good
It doesn't actually decrypt data
Thank you for your hard work, but I am not able to decrypt it in practice. The version of my device is MIUI 12.5.8.0 stable, and the Android version I am running is Android 11. Is it possible that I have to use MIUI development version?
Can you guys share which driver you're using? My 10x pro is not being detected via fastboot mode. Thanks.
it keeps saying when i try to flash recovery that the file size is too big ? plz help
not working on androind 12 causes bootloop
This guide is general guide for the installation of custom ROMs. I will also include guide to install stock ROM on devices which have been bricked or for solving various problem which you may encounter in custom ROMs. There are other guides for the same purpose but most of them are outdated and many of you seem to ignore old guide despite the fact that those guides can be helpful.
This is guide is only relevant for installation of custom ROMs which were released up to the date of posting this guide or up to android version 11. Recovering a bricked device can be done in the same way as to this one but installation instruction for devices with android version greater than 11 may differ.
DISCLAMER
Code:
I am NOT responsible for bricked devices,
thermonuclear war or for you getting fired because your alarm app failed.
Make sure the bootloader is unlocked and never lock the bootloader
How to unlock bootloader ?
>See in this thread.
Hard Brick, Soft brick, Problems in custom rom due to bad base, installation of base for switching to custom roms: windows linux
Installation of stock ROM through fastboot : The reply below
Migration from stock base to custom ROM : CLEAN FLASH
Migration between different version of same custom ROM : DIRTY FLASH
FOR SPECIFIC THREADS
Oragne Fox For Daisy
TWRP For Daisy
Magisk
CREDITS:
LInkBoi for his previous guide and TWRP
DarthJabba9 for Orange Fox Recovery
Every pros in daisy telegram groups.
EDL FLASHING (For windows only)
EDL flashing can be helpful when flashing every partition of device is needed either for clean stock base or after brick or after some failure.
EDL flashing can be the final resort when everything else fails.
PREREQUISITES
1) A good USB cable, your phone
2) A PC with either windows or linux
3) Fastboot drivers from google and edl drivers from qualcomm
4) Platform tools from google
5)Fastboot rom. This should be full rom in .tgz format.
6)Xiaomi flash tool (LATEST VERSION AVAILABLE)
Install the adb and fastboot drivers from google. If you are on windows 10 or greater then you can also use "windows update > optional updates" to update adb and fastboot drivers + edl drivers. For the installation of drivers always use trusted sources and don't turn of driver signature enforcement if you can.
Extract the platform tools in a convenient folder, we will be doing our operations from this folder for fastboot and adb opeartions. Extract the fastboot ROM and place that in convenient folder as well. And for xiaomi flash tool extract the zip and launch XiaoMiFlash.exe .
If you can access fastboot in you phone then the phone can be booted into edl mode through fastboot else you have to take out back cover and short the testpoint pins to make the device boot into edl mode (see the attached image ).
If you can access fastboot. Boot into fastboot and type the following command in terminal.
To check if device is connected properly and drivers are properly installed
If no devices is shown then connect device properly with good usb cable and check the drivers.
Code:
fastboot devices
To boot phone into edl mode. This is only possible if the bootloader is unlocked else testpoint-edl is the only option
Code:
fastboot oem edl
The device should be shown as COM device in device manager ( Windows ). If not then either drivers aren't installed properly or your phone isn't in edl mode.
Now click on refresh button in xiaomi flash tool. Your device should be recognized as com device. Set the path to the images folder ( extracted fastboot rom ). Select CLEAN ALL option . If everything is good then click
on FLASH. The flashing process should start now. After the process completes keep pressing power button to boot device into the currently installed ROM.
Just install the rom and setup once even if you're going to flash custom rom next. This reduces various problems which may come in custom ROMs.
If any error occurs then try the following:
Make sure you are using latest flash tool.
Good fastboot rom (shouldn't be corrupted )
Good USB cable and try different ports of the PC.
The flashing should be done immediately after booting to edl. If not then take out battery and reconnect it if you have back cover open(In case of hard brick). Or keep pressing power button and volume down to boot into fastboot and boot to edl mode again from the above instructions(If fastboot is accessible)
For booting to edl using testpoint:
> Take out backcover
> Disconnect battery
> Short the pins
> Flash
> Connect battery after flashing is complete
> Keep pressing power button to boot into system.
qdl flashing ( linux only )
For very detailed guide github -> bkerler edl
Thanks to DEFXZ and LinkBoi for suggesting this alternative.
Make sure you have platform tools, fastboot rom and other prerequisites to detect device properly.
clone the repository in convenient place
Code:
git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git --depth=1
change to qdl directory
Code:
cd qdl
Build qdl tool
Code:
make
Finally flash the rom
Code:
./qdl --storage emmc --include /path/to/stock/images /path/to/stock/images/prog_emmc_firehose_8953_ddr.mbn /path/to/stock/images/rawprogram0.xml /path/to/stock/images/patch0.xml
The paths are the paths to various files inside the images folder which will be obtained after fastboot rom is extracted.
For further informations:
Original github link
qdl discussion in XDA
FASTBOOT FLASHING
PREREQUISITES
FASTBOOT DRIVERS
PLATFORM TOOLS
FASTBOOT ROM
GOOD USB CABLE
PC WITH WORKING USB PORT
See this for meeting prerequisites.
Install fastboot drivers, connect device to PC via USB.
Extract platform tools into a convenient folder.
Extract fastboot ROM into a convenient folder.
Go to platform tools folder ( this will contain files and executable like fastboot.exe) and open powershell or any terminal window there
[ shift + right click and select open (powershell) window here ]
Type this command to see everything worked correctly.
Code:
fastboot devices
If not then check every step properly.
Now execute the script to flash the ROM.
Execute flash_all.bat script for windows PC.
Execute flash_all.sh script for linux PC.
If platform tools cannot be accessed system wide then.
Code:
./fastboot devices
will provide fastboot devices information.
For flashing drag and drop flash_all.bat or flash_all.sh file into the terminal.
Code:
'/media/user001/user/daisy/stock_roms/daisy_global_images_V10.0.18.0.PDLMIXM_9.0/flash_all.sh'
It will look something like this in linux and similar in windows.
If any error occurs the search for particular error. Most of the times the error is due to corrupted fastboot ROM or bad connection between phone and PC.
FINALLY! FLASHING CUSTOM ROM
STEP 0
Flash(if not flashed already) the stock base recommended by particular ROM, if the ROM doesn't recommend a specific stock base flash 10.0.18.0 from the above instructions.
PREREQUISITES
TWRP or ORANGE FOX RECOVERY
Fastboot drivers and platform tools (details above )
The ROM which you want to flash, choose from here
GAPPS package if rom is vanilla and you want to install it.
Magisk if you want to root.
As you may have known by experience, our device doesn't have recovery partition so, flashing recovery through fastboot isn't possible. For flashing recovery first we need to boot recovery image and then only we can flash it.
If you want to use twrp:
Download both twrp*.zip and twrp*.img and place it in a convenient place.
If you want to use orange fox recovery:
Download orangeFox*.zip and extract it.
Keep both the .zip and .img file in convenient place.
If you have sdcard then copy ROM file, gapps, magisk, twrp or orange fox files into sdcard.
If not then there will be further instructions.
Now, connect the phone to the PC via USB and enable usb debugging. And open terminal in the platform tools folder as in above instructions.
Check device connectivity:
Code:
adb devices
Reboot into fastboot:
Code:
adb reboot bootloader
Check device connectivity:
Code:
fastboot devices
Lets check if the bootloader is unlocked:
Code:
fastboot oem device-info
If bootloader isn't unlocked you won't be able to flash custom recovery into the device. So, first unlock the bootloader. This should be allowed in the developers option of your phone first. This will factory reset the device.
Code:
fastboot oem unlock
Now if everything is good then it's time to boot into custom recovery:
Code:
fastboot boot recovery.img
recover.img is name of image of whichever custom recovery you want to use.
Code:
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
It's like this in my case. You can drag and drop after typing fastboot boot
The phone should now boot into custom recovery. If it ask for decryption then your lockscreen password should work there.
if you want to flash recovery only then find the recovery.zip you want and flash it.
The steps further is also valid for moving between different custom roms. The term used for such process is CLEAN FLASH.
For Flashing custom ROMS :
SOMETIMES FLASHING INSTRUCTIONS MAY DIFFER SO, BE SURE TO CROSS CHECK FOR INSTRUCTION IN ROM SPECIFIC XDA THREAD OR TELEGRAM GROUP
The following action will wipe userdata if not wiped already. Be sure to backup data before these steps. Also if you encounter any future problems full backup from custom recovery may be able to solve most of the problems. So, be sure to keep full backup(including every partition) of your device.
Go to main menu > wipe > select all except internal storage and microSD.
Swipe right to perform wipe.
Install custom recovery by flashing recovery.zip
(This is done in case adb push doesn't work below and sdcard isn't available for flashing)
Again go to main menu > wipe > format data
Type yes and press enter.
If you don't have files in your sdcard then:
push rom file + gapps + other files into your device through adb push.
The command will be something like this:
Code:
adb push '/media/user001/storage (1)/daisy/posp/potato_daisy-11-20210919-dumaloo.v4.2.3+20.Community.zip' /sdcard
If adb push fails to work then you can reboot recovery and simply copy the files through file explorer.
Reboot to recovery only if you had installed recovery after wiping system else the device will soft brick
Now flash the rom.zip by selecting the file and swiping right.
Flash custom recovery if the ROM doesn't contain recovery
We have to change current slot even if we don't want to flash anymore things.
Latest recoveries changes slot automatically So, go to main menu > reboot > recovery
Now flash files which you want to flash i.e. gapps and magisk.
Again, Don't flash gapps if the ROM is of Gapps variant
Most of the roms now have implemented FBE (File Based Encryption ). So, you need to format data before rebooting to system. Again, check for specific ROM installation instruction if that is required or not. If you keep data from previous ROM that won't be considered a clean flash so, for proper clean flash format data before rebooting to system.
reboot system
MOVING BETWEEN DIFFERENT VERSION OF SAME CUSTOM ROM
Dirty flash or OTA
Most of the newer ROMs have seamless update ( even the unofficial ones ). The OTA update is simple. Just go to updater ( in settings > system or native app, depends upon the rom). If your ROM is of vanilla version then make sure gapps and/or magisk which you have installed, your ROM and custom recovery all support addon.d survival script. If they don't then you may have to flash everything again after update process is complete.
If custom recovery itself doesn't support update then you may need to choose different recovery or dirty flash ROM from the recovery. Don't worry most of the roms and both the recoveries for daisy support OTA and addon.d survival.
DIRTY FLASHThe process of flashing a ROM on top of existing one keeping the /data partition intact is known as dirty flashing. Such flashing must be done only on different builds of same ROM and it isn't recommended to flash build of lower version on top of higher version.
The steps for dirty flashing:
Download the update package.
Reboot to recovery
Enter password for decryption if encrypted.
Flash the update.zip package.
Reboot recovery, if recovery/rom doesn't support survival of recovery then flash recovery before rebooting to recovery.
If gapps and/or magisk survival isn't supported then flash gapps and magisk, make sure gapps is of the same type which was flashed before.
reboot system
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
We have to change current slot even if we don't want to flash anymore things.
Click to expand...
Click to collapse
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Execute flash_all.bat script for windows PC.
Click to expand...
Click to collapse
Is this a section i can bypass ? if not where can i get them from ?
Cheers
steve.loveday said:
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Is this a section i can bypass ? if not where can i get them from ?
Cheers
Click to expand...
Click to collapse
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
user-001 said:
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm getting confused with all the various guides all seem to want you to do it a different way.
As i'm wanting Lineage thier instructions are...
Installation:
Download the latest build from here
Download LinkBoi00's version of TWRP here
Reboot to bootloader (adb reboot bootloader)
Fastboot into TWRP recovery (fastboot boot twrp*.img)
Do a factory reset in TWRP
Flash the latest build of Lineage OS
Boot into your new phone
Click to expand...
Click to collapse
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
This guide deals with how to do something rather than what to do, meaning you should always do what particular rom suggests but the way to do this is mentioned here.
edl or fastboot flashing comes under clean flashing with new base, most of the time you aren't required to do this.
The script should be clean_all.bat or something similar just don't execute script with lock in the name(it will lock the bootloader)
And if you're already on the recommended base you don't have to flash the fastboot rom.
First of all, thank you very much for the detailed guide. What you have done here took a lot of work to do but it will help a lot of people (including me) to understand, albeit rudimentarily, the structures and functions of the devices etc.
For all that, thanks again.
When I start using the guide, I will update this post with any questions, such as :
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
why not doing below? (For those who, like me, are not very familiar with linux.)
1. > adb push <twrp.img> /sdcard or same adb push "C:\platform-tools\twrp-3.5.2_9-2-daisy-unofficial.img" /sdcard
( which means push <file> from "adb|platform-tools\ folder" (eg. C:\platform-tools\)
into the root of <internal storage> | /storage/emulated/0 )
2. Reboot from adb to fastboot:
> adb reboot bootloader
3. Boot the image from <internal storage>:
> fastboot boot /sdcard/twrp-3.5.2_9-2-daisy-unofficial.img
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
I followed your "EDL FLASHING" post (#2) and it worked exactly as you mention!
In short, I was comming from unsuccessful flashing... but this is out of topic.
For me, did not worked the first time (after restarts) but the other day worked perfect.
The point is, most of times, it's becase windowz drivers.
We have to point that windowz needs their time to take the drivers in place. So, be patient and leave windowz to (not forced) restart(s).
AntonyMan said:
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
Click to expand...
Click to collapse
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
For future references, the extracted fastboot ROM should be like this and you need to execute flash_all.bat or flash_all.sh script depending upon your OS or terminal.
user-001 said:
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
Click to expand...
Click to collapse
Of course I'm talking about something else. lol
I was talking about that 'strange' address. fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img' (explained in post #11)
There is not such a directories in my miA2Lite phone. Obviously, it's because you are on Linux or Mac (UNIX). On Windowz 'command prompt' syntax it's slightly different.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
AntonyMan said:
Of course I'm talking about something else. lol
I was talking about that 'strange' address. There is not such a directories in my miA2Lite phone.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
Click to expand...
Click to collapse
The twrp image was on my pc(linux) i was booting directly from pc's terminal. And if you use only adb(or fastboot) then the paths are pc's absolute paths.