{
"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"
}
Resurrection Remix Oreo
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.
*/
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters
-INSTALLATION INSTRUCTIONS-
Code:
[CENTER][B]- Download the latest build
- Download Gapps (ARM 8.1 Pico/Nano/Other)
- Take a nandroid backup
- Recommended - Full wipe and factory reset
- Flash ROM using latest TWRP 3.x Recovery
- Flash Gapps
- Reboot.
- Enjoy![/B][/CENTER]
DOWNLOADS
RR OFFICIAL
Gapps Link :- OpenGapps ( Use Pico/Nano)
SOURCES
Device Tree
Kernel Source (LineageOS)
CREDITS
Maaz Muzammil
theHari08
Special Thanks to Mah bruh @dev_harsh1998:highfive:
XDA:DevDB Information
[ROM][FINAL][OFFICIAL]Resurrection Remix v6.0.0 [8.1.0]Jalebi][11/13], ROM for the Yu Yunique
Contributors
iamsj7
Source Code: https://github.com/ResurrectionRemix/
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Current Stable Version: v6.0.0
Stable Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-11-12
Smart pixel option is available?
Rup_R said:
Smart pixel option is available?
Click to expand...
Click to collapse
yes
prabhjot368 said:
yes
Click to expand...
Click to collapse
Yeah.. i found it.. but still battery draining too much
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
Can you provide any kernel for this problem?
Flashing ends with Error 7 in Twrp 3.0.3.0
I tried to flash the New RR-O-V6.0.0 yesterday in my phone ( Yu Yunique) through Twrp latest version but the flashing ends with an error code "error 7".
I also tried deleting the asserts file from update-script and then another error pops up saying corrupt file.
Please help .
Current ROM - RR-N-v5.8.5 Final.
remove lines from Update script
No.1708 said:
I tried to flash the New RR-O-V6.0.0 yesterday in my phone ( Yu Yunique) through Twrp latest version but the flashing ends with an error code "error 7".
I also tried deleting the asserts file from update-script and then another error pops up saying corrupt file.
Please help .
Current ROM - RR-N-v5.8.5 Final.
Click to expand...
Click to collapse
To Fix:
Open the Lineage OS ROM zip using any archiving software like 7zip, WinRAR, etc… You can also open it on your device.
Now, you need to navigate to this path: META-INF » com » google » android » updater-script.
Open the file updater-script in a text editor. You’ll see a bunch of lines with the command assert and the model name of the device next to it.
updater script lineage os
If there’s a mismatch with the codename of the device in the script, you’ll get Error 7 while flashing.
So, just either edit the code to match your device’s codename or delete all the lines having the code “assert & getprop”
Save the file.
Try to install the ROM now.
http://www.lineageosdownloads.com/fix-error-7-lineage-os/
No.1708 said:
I tried to flash the New RR-O-V6.0.0 yesterday in my phone ( Yu Yunique) through Twrp latest version but the flashing ends with an error code "error 7".
I also tried deleting the asserts file from update-script and then another error pops up saying corrupt file.
Please help .
Current ROM - RR-N-v5.8.5 Final.
Click to expand...
Click to collapse
Extract rom in a folder . go to META-INF , com , google , android , updater script.
open updater script using Notepad ++ , ( because other apps like word pad does not detect line numbers and you get error while flashing, so use notepad++), delete the first line and compress again.
RoHiTkUmArShArMa said:
Extract rom in a folder . go to META-INF , com , google , android , updater script.
open updater script using Notepad ++ , ( because other apps like word pad does not detect line numbers and you get error while flashing, so use notepad++), delete the first line and compress again.
Click to expand...
Click to collapse
How to do all this without PC ??
Is their offline charging problem in this rom?
Guys I successfully flashed rom RR V6 and gaaps 8.1 without any error but phone is stuck at boot animation and boots to recovery after some time. I upgraded from cm13 and facing this problem for every rom I install,but if I revert to cm13 everything works fine.kindy suggest a solution.
download rom again, or make sure you delet all words before this, ui_print("Target
download rom again, or make sure you delet all words before this, ui_print("Target
stuck at google logo...
RoHiTkUmArShArMa said:
Extract rom in a folder . go to META-INF , com , google , android , updater script.
open updater script using Notepad ++ , ( because other apps like word pad does not detect line numbers and you get error while flashing, so use notepad++), delete the first line and compress again.
Click to expand...
Click to collapse
It shows invalid file format every time .. i tried it on several other roms too. Any sol. or specific compressor to use??
ShivamNagi said:
It shows invalid file format every time .. i tried it on several other roms too. Any sol. or specific compressor to use??
Click to expand...
Click to collapse
You use Notepad++ for this or not.
Because only Notepad++ is detecting the lines correctly.
Extract the zip in separate folder.
Now select updater script from META-INF , com , google , android , updater script.
Delete the first line and go to start of 2nd line and hit backspace .Now your 2nd line now first line .
Now go to folder where to extract the ROM files .
Select all files and folders such as Install,META-INF,boot.img,system.bat,etc, (select everything ) , Right click , and compress these files to zip.
i think you are compressing the folder which contain these extracted files, thats why you are getting the error.
RoHiTkUmArShArMa said:
You use Notepad++ for this or not.
Because only Notepad++ is detecting the lines correctly.
Extract the zip in separate folder.
Now select updater script from META-INF , com , google , android , updater script.
Delete the first line and go to start of 2nd line and hit backspace .Now your 2nd line now first line .
Now go to folder where to extract the ROM files .
Select all files and folders such as Install,META-INF,boot.img,system.bat,etc, (select everything ) , Right click , and compress these files to zip.
i think you are compressing the folder which contain these extracted files, thats why you are getting the error.
Click to expand...
Click to collapse
Thanks for the help. I was zipping the folder because when i compressed the files by selecting them my mac's default will make different zips for each file/folder. I used winrar and it went fine..
Update 2018-11-13
ROM : \RR-O-v6.2.1-20181112-jalebi-OFFICIAL.zip
-merged Nov patches
-merged kernel cve pathes
-added device Network types
-kernel compiled on gcc linaro 7.1.2
-update gps overlays
-moved configs to vendor
-gps: Enable GLONASS
- add textclassifier's smart selection
- cleaned up sepolicy
- added all recording
- and source updates
unable to download bro.. site says secure connection failed
iamsj7 said:
Update 2018-11-13
ROM : \RR-O-v6.2.1-20181112-jalebi-OFFICIAL.zip
-merged Nov patches
-merged kernel cve pathes
-added device Network types
-kernel compiled on gcc linaro 7.1.2
-update gps overlays
-moved configs to vendor
-gps: Enable GLONASS
- add textclassifier's smart selection
- cleaned up sepolicy
- added all recording
- and source updates
Click to expand...
Click to collapse
Thanks for still keeping this device alive.
Hey Thank you for this ROM .
Will you be able to provide me with a link for installation guide for this ROM.
I'll be grateful.
Keep up the good work.
battery stats + screenshots
The AndroidGuy said:
Thanks for still keeping this device alive.
Click to expand...
Click to collapse
.......
.
Related
Tool Aces Present..
Universal PA Porter
About the tool:
This tool can be used to port the great Paranoid Android ROMs from any device. It's based on the guide of adityalahiri13. Thank him too.
How to use:
Make sure you that both the ROMs(Base and PA) have the same resolution. I recommend taking CM as base. Also make sure that the android versions of base and PA ROM matches. Try to use port from a device of same manufacturer, though it may not matter much.
Steps-
1. Place base ROM zip in CM folder.
2. Place PA ROM zip in PA folder.
3. Now click on Main.bat the tool will do some steps.
4. After this it will ask for your device resolution. Choose one among 5.
5. Then it will open build.prop and another file. Copy the lines from another text file to the build.prop below ro.modversion= and write the PA version you are porting infront of ro.pa.version=
6. Save and exit.
7. Now it will open updater-script and another file. Copy the line from another file and paste it to your updater-script below this line:
Code:
set_perm(1000, 1000, 0644, "/system/etc/paranoid/properties.conf");
8. Then it will ask for your android version. Choose ICS or JB, then it will zip the ROM, select name as desired and find your ROM in /PORT folder.
Congrats on your newly ported ROM.
Downloads:
Download the tool from here.
Screenshot:
{
"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"
}
FAQs:
Q. Well I ported this accordingly but it's stuck in bootloop. How to solve it?
A. In some cases this happens. Simply run bootloop.bat and see if it works. If it still doesn't works then run bootloop2.bat. Make sure to check if the ROM boots after running bootloop.bat, if still stuck on bootloop then only run bootloop2.bat
Q. Why you recommend porting from same manufaturer?
A. Well you can port from others also but in some of them you might need some framework modding and also need to do some modding in kernel. But in most cases even from other manufacturers the ROM should work.
Q. How can I help?
A. Pressing THANKS button would be enough.
Click to expand...
Click to collapse
Credits:
1.adityalahiri13- For such a great guide. Thank him too
2. Paranoid Android Team- For such great efforts on such great ROM.
Reserved
Sent from my ST21i2 using xda premium
wow it will try this, if heped i ll press thanks
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Diablo67 said:
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Click to expand...
Click to collapse
Sorry can't get ur error properly can u send some screens? Also I've tested it and it works ok.. but still I'll try my best to help u out
Press THANKS if I helped,
Best Regards,
AJ
alokbina is now Abhinav2
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Try hypercam to record or press prnt scrn fast...I do the same..
Press THANKS if I helped,
Best Regards,
AJ
alokbina is now Abhinav2
If the tool isn't running at all for you guys, you are either trying to run the .bat file from within the zip, or you extracted the zip file wrong.
Extract the zip with Winrar.
Just right click the file and select "Extract Files..." than click OK.
I haven't tried porting this yet but the tool itself works just fine.
m4nu4l said:
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Click to expand...
Click to collapse
Extract files to just to short path, for example to "c:\porting\" or "d:\porting\".
This problem shows when .bat is deep in folder.
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
aiinjylls said:
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
Click to expand...
Click to collapse
Now after so many reports I think there's some fault with the tool...though I checked it..still if u can try to get the error it's best..anyways I'll try to fix this today itself
Best Regards,
AJ
alokbina is now Abhinav2
Is this still alive? Just curious, thx.
Sent from my Smooth(ROM) Kindle Fire
Diablo67 said:
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Click to expand...
Click to collapse
m4nu4l said:
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Click to expand...
Click to collapse
aiinjylls said:
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
Click to expand...
Click to collapse
I'm really sorry guyz it was my mistake....fixed the tool now Please forgive me if possible guyz....Enjoy :good:
Cheers,
AJ
Do we redownload?
I took a look at main.bat ( noticed a spelling error in command goto del *it said delco* )
I think Bootloop2.bat may have errors. I get system cannot find specified file
Sent from my Galaxy Nexus using xda premium
Getting SOrry error porting.Please Check you have done everything properly
aiinjylls said:
Do we redownload?
I took a look at main.bat ( noticed a spelling error in command goto del *it said delco* )
I think Bootloop2.bat may have errors. I get system cannot find specified file
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes I fixed the errors and now it will work
nlygamz said:
Getting SOrry error porting.Please Check you have done everything properly
Click to expand...
Click to collapse
I've checked it thrice man...just tell me in detail wat all happens....
Cheers,
AJ
stuck in bootloop....damn man.....the PA logo just goes on and on
I redownloaded and it runs through completely without errors
- it skips the build.prop prompt though
The Bootloop.bat runs smoothly
The Bootloop2.bat always gives me "file not found"
I have not successfully booted a ROM, but its working for me
Sent from my Galaxy Nexus using xda premium
nlygamz said:
stuck in bootloop....damn man.....the PA logo just goes on and on
Click to expand...
Click to collapse
Please run the bootloop batch scripts and then try to do a logcat.
Cheers,
AJ
ran bootloop and bootloop2 ....it runs fine now....just need to do some manual handwork in it! Thanx man! Appreciate your help
---------- Post added at 09:37 AM ---------- Previous post was at 09:18 AM ----------
http://postimg.com/image/138000/paport-137438.jpg <<< Check this out @Abhinav2
Disclaimer: I am not responsible for anything bad that may occur from the use of this zip, but I will take all the credit you can give if it works for you.
{
"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"
}
ExtSD Fix
Download latest stable - MD5 checksumDownload latest dev - MD5 checksum
In KitKat, Lollipop and Marshmallow, policies on writing permissions for external SD cards have been changed. This flashable recovery file automatically appends the correct permissions to the file as explained in many tutorials on the web (here or here) or as what many apps do (here).
Advantages
The advantage of this flashable zip over the other methods is that:
you don't need to install any apps,
you can revert by reflashing (not tested for marshmallow),
it does not require you to have root (needs to be confirmed),
[*]you don't need a custom recovery (needs to be confirmed).
Installation
It can insert and remove the permission to write on the external sdcard. To install follow these steps:
Turn off phone,
Boot into recovery,
Backup your system and data partition,
Flash this zip file once,
Reboot phone normally.
To revert the changes, follow the same steps again. This means that flashing it twice will have no effect.
Marshmallow is not supported yet, implementation is in progress.
Note: On Marshmallow, busybox will be installed if not already present. It can also be installed as a standalone app. You should an also add init.d support to your phone if not already available using an app.
How to report a bug
Check if someone else reported that it did/didn't work,
Backup, clean flash, reinstall all apps and then flash ExtSD Fix,
Submit a bug report here with both the original and modified packages.xml and the recovery log file as suggested here.
Changelog
v2.9b - 2016-06-09
Added double flashing revert for MM.
v2.8b - 2016-06-09
Added more logging to:
during flashing: /data/ExtSD_Fix_RW_inst.log
during boot: /data/ExtSD_Fix_RW_initd.log
v2.7b - 2016-06-08
Renamed script,
Changed permissions.
v2.6b - 2016-06-07
Changed permissions.
v2.5b - 2016-06-07
Changed permissions,
Added support for limited backup files.
v2.4b - 2016-06-05
Corrected bugs.
v2.3b - 2016-06-02
Included debug messages.
v2.2b - 2016-06-02
Corrected bugs. "ERROR:2" should be fixed.
V2.1b - 2016-05-19
Implemented solution from here and here.
V1.9b - 2016-05-04
Implemented solution from here. PLEASE TEST AND REPORT.
V1.8b - 2016-02-04
Corrected bug for Marshmallow.
V1.7b - 2016-02-02
Added support for Marshmallow.
V1.6b - 2016-01-27
Added revert on second run.
V1.5b - 2016-01-26
Corrected bug in check for API version.
V1.4b - 2016-01-26
Changed format of backed up filename.
Added check for API version ( 19<= API <= 22 ).
V1.3b - 2016-01-22
Backed up file is renamed with time and date.
V1.2b - 2016-01-21
Moved code into update-binary.
V1.1b - 2016-01-19
Removed testing commands.
V1.0b - 2016-01-18
Initial submission
XDA:DevDB Information
ExtSD Fix, Tool/Utility for all devices (see above for details)
Contributors
rufus.wilson
Version Information
Status: Testing
Current Beta Version: v2.9b
Beta Release Date: 2016-06-09
Created 2016-01-18
Last Updated 2016-06-15
Tested devices and systems
When you have tested it could you report your experience with the device model and the android version you used.
I will summarize here the success and failures.
Success
OnePlus X - CM 12.1
N4 w/TW 6.0.1 MM
sony z3c concept rom(mm)
Samsung Galaxy Express 2 with CM13
Xperia M with CM13
Sony Z3 .570 stock
asus zenfone 2
Asus ZenFone 4 - Stock v7.4.4 (Lollipop) (all opened apps had FC on reboot)
asus zenfone 5 XOSP rom
Sony Xperia Z3 (Sometimes is overwritten)
SM-G910F Rom ALEXNDR COJ3 Deodexed
Samsung galaxy s5 g900f stock marshmallow
z3c with rom slimm 1.5
Galaxy S7 SM-G930FD 6.0.1 Rooted Xposed
Xiaomi Redmi 1S RR 5.6.8 which is a CM13(R28)
Sony Z3 D6653 running on RXSW Marshmallow Edition [3.0.0] [12/04/16] [6.0.1]
LG L90 D415
Redmi 1s using OctOS M ROM
xt907 JBBL- cm13, 01-05-2016
Redmi 2, CM 13.1-20160417-SNAPSHOT
z3 570 rxsw
LG G3 VS985 variant running CM 13 6.0.1 nightlies. Using 777 Kernel & TWRP 3.0.2
z3 dual d6633 running marshmallow 6.0.1 official
Oppo find 7a x9006 on 6.0.1 rooted with twrp 3.0
Failure
LG D855 32 Gb with CM13 2016-05-10 and TWRP 3.0.0.0 recovery
Sony z3 MM
g900f blisspop 6.01
Samsung N7105T, unofficial wilson3q cm 13
Reserved
not work with my device
zenfone 4
here is my recovery log
hiimpig1 said:
not work with my device
zenfone 4
here is my recovery log
Click to expand...
Click to collapse
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
rufus.wilson said:
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
Click to expand...
Click to collapse
im using twrp 2.8.7.0
hiimpig1 said:
im using twrp 2.8.7.0
Click to expand...
Click to collapse
I have uploaded a new version. Could you test that one?
rufus.wilson said:
I have uploaded a new version. Could you test that one?
Click to expand...
Click to collapse
i flashed, after that all my apps got FC
but its worked
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
hiimpig1 said:
i flashed, after that all my apps got FC
but its worked
Click to expand...
Click to collapse
Was a reboot enough to solve the problem?
phoberus said:
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
Click to expand...
Click to collapse
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
chmod 0644 platform.xml
rufus.wilson said:
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
Click to expand...
Click to collapse
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
rufus.wilson said:
Was a reboot enough to solve the problem?
Click to expand...
Click to collapse
no its not
phoberus said:
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
Click to expand...
Click to collapse
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
hiimpig1 said:
no its not
Click to expand...
Click to collapse
Can it be a permission problem? Look here.
rufus.wilson said:
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
Click to expand...
Click to collapse
Didn't work for me, but I have a backup :good:
phoberus said:
Didn't work for me, but I have a backup :good:
Click to expand...
Click to collapse
Which version of android do you use?
hiimpig1 said:
no its not
Click to expand...
Click to collapse
Which ROM are you using?
rufus.wilson said:
Which ROM are you using?
Click to expand...
Click to collapse
im using stock rom 7.4.4 from asus
hiimpig1 said:
im using stock rom 7.4.4 from asus
Click to expand...
Click to collapse
Do you still have the FC?
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?
Hello Guy today I want to teach you how to fix WiFi region code problem on Nought and Oreo roms
FIX FOR NOUGHT ROMS AND OREO ROMS(ONLY FOR BUILDS BEFORE 19/1/2018)(NOT FOR cypherOS)
If you are on builds after 19/1/2018 or cypherOS go down ; there is a way with xposed to fix the problem
reqierments :
1. knowing how decompile .jar files (you can use This tool)
2. notepad ++(for editing some files)
3. "telephony-common.jar" from rom (you can find it in "system -> framwork)
4. framwork-res.apk of rom (you can find it in "system -> framwork)(the process may work without it)
** if you see this mark on TUT it means "if you use the tool that is on first requierments"
Steps :
1. install the "framework-res.apk" for apktool (** copy it to "in" folder of tool
then choose " 1 " and choose the "framwork-res.apk" of rom)
2. decompile the "telephony-common.jar" file and go the folder of the decompiled file (** copy the file to "in" folder open the tool and choose " 2 " then choose the "telephony-common.jar" and continue the process to complete decompile and then you can find the folder of decompiled file in "out" folder)
3. After you go to the folder of decompiled file go to " smail -> com -> android -> internal -> telephony " then search for " MccTable " and open it with "notepad ++"
4. on " notepad ++ " search for " setWifiCountryCode " and you will find three lines with it
go to first line
under it you will see " .locals 5 " change it to " .locals 13 "
( as you can see in picture )
first line
{
"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"
}
then go to second line
go a little upper and found (here is .line 199)(but the line number may change duo to rom)
:cond_1
Click to expand...
Click to collapse
and change the line below of it to
goto :goto_0
Click to expand...
Click to collapse
( as you can see in picture )
second line
there is no need to touch the third line
5. save the file and close " notepad ++ "
6. now recompile the file (** choose " 3 " to recompile the file and choose "telephony-common.jar" and then press NUM "4" option (Recompile, Sign And Then Zipalign)and continue the process to complete recompile )
6.1 ( ** you can find the file on " done " folder)
7. after the recompile completed copy the file to your phone
8. on your phone replace old " telephony-common.jar " with the new one and set permissions and reboot phone
P.S. after the reboot the phone may not boot at the first time (dont worry) just force shutdown your phone ( by press and holding "power button" and "volume up" and phone will vibrate 3 times ) then turn on your phone again
and you will see the problem of region code is gone :good:
FIX FOR all Nought and OREO BUILDS (LOS & RR & CARBON & CYPHER OS)
first of all thanks to @ali6944 for finding this xposed modules
you just need xposed for it and install this modules then active it and reboot your phone and problem is gone :good:
Cool to see it nicely put in an easy to follow format, Good job!:highfive:
I have done exactly what you did with the same tool, but only in step 6 when recompiling, I am getting four options :
Recompile "telephony-common.jar"
1 - Only Recompile
2 - Recompile And Then Sign
3 - Recompile And Then Zipalign
4 - Recompile, Sign And Then Zipalign
I chose the first one and I got the file in "done" folder but in zip format like this telephony-common.zip
I changed the extension to .jar and copied it to phone, replaced the old one and gave permissions, powered off the device (force shut down) and turned it on but I didn't get a working WIFI, I am on RR 5.8.5 BTW, thanks for the help.. hope you can reply soon..
Dr.TheMaster said:
I have done exactly what you did with the same tool, but only in step 6 when recompiling, I am getting four options :
Recompile "telephony-common.jar"
1 - Only Recompile
2 - Recompile And Then Sign
3 - Recompile And Then Zipalign
4 - Recompile, Sign And Then Zipalign
I chose the first one and I got the file in "done" folder but in zip format like this telephony-common.zip
I changed the extension to .jar and copied it to phone, replaced the old one and gave permissions, powered off the device (force shut down) and turned it on but I didn't get a working WIFI, I am on RR 5.8.5 BTW, thanks for the help.. hope you can reply soon..
Click to expand...
Click to collapse
yes you are right i have forgot to say anything about that four option
i choose " 4 " ( Recompile, Sign And Then Zipalign )
and i dont know why it was in zip format
and another thing is i did this for carbon rom which has no option to change wifi region code i dont know if it works on RR
BTW try again with the NUM 4 option and if it didnt worked send the telephony-common.jar file to me to see what can i do
I got it working for RR using this..
raminta said:
yes you are right i have forgot to say anything about that four option
i choose " 4 " ( Recompile, Sign And Then Zipalign )
and i dont know why it was in zip format
and another thing is i did this for carbon rom which has no option to change wifi region code i dont know if it works on RR
BTW try again with the NUM 4 option and if it didnt worked send the telephony-common.jar file to me to see what can i do
Click to expand...
Click to collapse
After doing exactly as you showed, but instead of recompiling using this tool I recompiled the file using the APKTOOK that was installed previously on my computer using this command (after opening CMD in the out folder)
Code:
apktool b -f -d telephony-common.jar
after that I copied the output file from the dist folder (telephony-common.jar\dist) and replaced it with permissions and it worked perfectly (RR 5.8.5), thanks for helping and keep it up for more tutorials :highfive:
Newest Carbon rom build has 410byte dummy version of telephony-common.jar, this fix cannot be enabled.
jjanggukin said:
Newest Carbon rom build has 410byte dummy version of telephony-common.jar, this fix cannot be enabled.
Click to expand...
Click to collapse
Sorry im a little bussy (with exam) i will look at it tomorrow
jjanggukin said:
Newest Carbon rom build has 410byte dummy version of telephony-common.jar, this fix cannot be enabled.
Click to expand...
Click to collapse
It's because the rom is not deodexed, I've spent a lot of time searching for a way to deodex and found out that android 8.1 moved to .vdex instead of .odex so there isn't yet a way to deodex to apply this fix, you can learn more about this here: https://github.com/JesusFreke/smali/issues/498
ali6944 said:
It's because the rom is not deodexed, I've spent a lot of time searching for a way to deodex and found out that android 8.1 moved to .vdex instead of .odex so there isn't yet a way to deodex to apply this fix, you can learn more about this here: https://github.com/JesusFreke/smali/issues/498
Click to expand...
Click to collapse
For linux you can use this: https://github.com/anestisb/vdexExtractor
for windows: https://github.com/Furniel/Apk-Changer
i successfully deodexed the whole framework but there's something wrong!
if you removed oat and arm folders then flashed the deodexed framework you will enjoy with the lovely bootloop, if you flashed without removing oat and arm folders it's fine but not effects for any modded jars!! so basically the deodexed framework is useless!!
here is the file which you need already deodexed and patched and if you find anyway to get it working please let me know because i miss some mods since the latest build
rocker00 said:
For linux you can use this: https://github.com/anestisb/vdexExtractor
for windows: https://github.com/Furniel/Apk-Changer
i successfully deodexed the whole framework but there's something wrong!
if you removed oat and arm folders then flashed the deodexed framework you will enjoy with the lovely bootloop, if you flashed without removing oat and arm folders it's fine but not effects for any modded jars!! so basically the deodexed framework is useless!!
here is the file which you need already deodexed and patched and if you find anyway to get it working please let me know because i miss some mods since the latest build
Click to expand...
Click to collapse
Nice work, will keep on the case, can't stand being on an obsolete build forever!
ali6944 said:
Nice work, will keep on the case, can't stand being on an obsolete build forever!
Click to expand...
Click to collapse
Latest build of Lineage and CypherOS is the same, so that's might be the new style and i think it's better if we can find a solution for that rather than using old builds!
rocker00 said:
Latest build of Lineage and CypherOS is the same, so that's might be the new style and i think it's better if we can find a solution for that rather than using old builds!
Click to expand...
Click to collapse
You are absolutely right, also it's a universal thing with all the new 8.1 roms, even the Pixel phone OTAs have it so a lot of effort is being but into this right now, I'll keep trying, I'm even using the latest build of carbon right now, it's a bit inconvenient having to reboot the phone every time you disconnect from WiFi, but this motivates me to try even further!
@rocker00 can you try installing vdex extractor, you can find it compiled and ready here:
https://www.dropbox.com/s/cbqs5e8nwy...actor.exe?dl=0
it didn't want to install on my PC for some reason, if you can get it working try using it on boot-telephony-common.vdex from framwork/arm and see what comes up
ali6944 said:
@rocker00 can you try installing vdex extractor, you can find it compiled and ready here:
https://www.dropbox.com/s/cbqs5e8nwy...actor.exe?dl=0
it didn't want to install on my PC for some reason, if you can get it working try using it on boot-telephony-common.vdex from framwork/arm and see what comes up
Click to expand...
Click to collapse
Link doesn't work(404)
raminta said:
Link doesn't work(404)
Click to expand...
Click to collapse
Here it is on Google Drive: https://drive.google.com/open?id=13PLmXstJs5GfrJT5ji4-yuE_8WjaA8Xj
ali6944 said:
@rocker00 can you try installing vdex extractor, you can find it compiled and ready here:
https://www.dropbox.com/s/cbqs5e8nwy...actor.exe?dl=0
it didn't want to install on my PC for some reason, if you can get it working try using it on boot-telephony-common.vdex from framwork/arm and see what comes up
Click to expand...
Click to collapse
This is not an app to install, it's like command line, also it doesn't make any sense to try this because the tool i mentioned for windows also based on vdexextractor, it's just implemented for windows.
now am confused more and more, i flash deodexed patched services.jar (aka superuser mod) and it worked! then i tried to remove services.vdex from oat/arm and it worked also!! so why it worked with or without .vdex from oat/arm and the other mods based on arm folder doesn't work and if you removed boot-......vdex for any jar you will have bootloop!!
rocker00 said:
This is not an app to install, it's like command line, also it doesn't make any sense to try this because the tool i mentioned for windows also based on vdexextractor, it's just implemented for windows.
now am confused more and more, i flash deodexed patched services.jar (aka superuser mod) and it worked! then i tried to remove services.vdex from oat/arm and it worked also!! so why it worked with or without .vdex from oat/arm and the other mods based on arm folder doesn't work and if you removed boot-......vdex for any jar you will have bootloop!!
Click to expand...
Click to collapse
here is a thread that i found helpful: https://forum.xda-developers.com/pi...lly-deodex-stock-oreo-systemui-t3685034/page3
It seems like even the gods of deodexing are having the same issues, you can deodex pretty much anything including services.jar, but you can't touch any other framework file without causing a bootloop, if i got the conclusion right then i think we need to wait for jesusfreake to update smali and backsmali to support vdex
ali6944 said:
here is a thread that i found helpful: https://forum.xda-developers.com/pi...lly-deodex-stock-oreo-systemui-t3685034/page3
It seems like even the gods of deodexing are having the same issues, you can deodex pretty much anything including services.jar, but you can't touch any other framework file without causing a bootloop, if i got the conclusion right then i think we need to wait for jesusfreake to update smali and backsmali to support vdex
Click to expand...
Click to collapse
Yeah, the latest post in the thread you mentioned exactly the same issue i have, looks like we are out of luck now!
I can't believe I forgot about this, but while I was looking for a fix for nougat months ago I found this xposed module that fixes the issue, but since I got WiFi working before that, I totally forgot about it, I just tried it with the latest Carbon rom and it works! Can't believe it was right there for so long
Here it is http://repo.xposed.info/module/android.wifiregionalfix
ali6944 said:
I can't believe I forgot about this, but while I was looking for a fix for nougat months ago I found this xposed module that fixes the issue, but since I got WiFi working before that, I totally forgot about it, I just tried it with the latest Carbon rom and it works! Can't believe it was right there for so long
Here it is http://repo.xposed.info/module/android.wifiregionalfix
Click to expand...
Click to collapse
added to first post thanks alot
Do you want to create your own firmware files from MIUI ROMs without depending on Xiaomi Firmware Updater? Then you need the new tool!
Xiaomi Flashable Firmware CreatorPart of Xiaomi Firmware Updater project
{
"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"
}
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 tool
* 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.
*/
Xiaomi Flashable Firmware Creator is a tool that generates flashable firmware-update packages from official (or non-official?) MIUI ROMS.
It supports creating untouched firmware, non-arb firmware, firmware + vendor flashable zip and firmware-less ROMs.
Features:
CLI and GUI version.
Easy-to-use interface.
Supports local and remote zip files.
Easy to integrate with other Python scripts.
Multilanguage support (more than 25 languages!). Thanks to our community members!
Screenshots:
Here, or Here.
GUI Usage:
Make sure that you have Python3 installed on your device.
Install the tool.
Code:
pip3 install xiaomi_flashable_firmware_creator_gui
Run the tool.
Code:
xiaomi_flashable_firmware_creator_gui
Select MIUI zip, or drop it to the box.
Choose the output type you would like to create.
Click on create button.
CLI Usage:
You need python 3 installed on your device, or you can get the compiled executable from here.
Install the tool using the following command:
Code:
pip3 install xiaomi_flashable_firmware_creator
- Creating normal (untouched) firmware:
Code:
xiaomi_flashable_firmware_creator -F [MIUI ZIP]
- Creating non-arb firmware (without anti-rollback):
Code:
xiaomi_flashable_firmware_creator -N [MIUI ZIP]
- Creating firmware-less ROM (stock untouched ROM with just firmware removed):
Code:
xiaomi_flashable_firmware_creator -L [MIUI ZIP]
- Creating normal vendpr+firmware:
Code:
xiaomi_flashable_firmware_creator -V [MIUI ZIP]
- Using executable files:
On Linux:
Code:
./create_flashable_firmware -F [MIUI ZIP]
On Windows:
Code:
create_flashable_firmware.exe -F [MIUI ZIP]
Detailed Guide:
Check [Guide] How to edit Miui ROMs to flash without bootloader by @AL_IRAQI
Ready-made firmware files:
If you're lazy or looking for ready-made firmware files for whatever Xiaomi device, check my Xiaomi Firmware Updater project. It provides automatically generated Xiaomi firmware flashable zip files for every MIUI new update!
Support and Contact:
Having trouble with firmware files? You can open a new issue on Github repository or just write here in a reply, and I’ll help you sort it out.
Also If you want to add a new feature or fix any problem, feel free to push a PR.
Donations:
My works are free and open-source, that cost money, time and many efforts.
If you want to make a donation, you can use:
- Paypal
- Pateron
- LiberaPay
XDA:DevDB Information
Xiaomi Flashable Firmware Creator V2, Tool/Utility for the Android General
Contributors
yshalsager
Source Code: https://github.com/XiaomiFirmwareUpdater/xiaomi-flashable-firmware-creator
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-10-17
Created 2018-11-24
Last Updated 2020-10-17
in windows 10 give error after make new zip rename.
edit py file with text editor.
Find
Code:
def make_zip():
rom, process = arg_parse()
with open("out/META-INF/com/google/android/updater-script", 'r') as i:
codename = str(i.readlines()[7].split('/', 3)[2]).split(':', 1)[0].replace('_', '-')
print("Creating " + process + " zip from " + rom + " for " + codename)
make_archive('firmware', 'zip', 'out/')
if path.exists('firmware.zip'):
if process == "firmware":
rename('firmware.zip', 'fw_' + codename + "_" + rom)
elif process == "nonarb":
rename('firmware.zip', 'fw-non-arb_' + codename + "_" + rom)
elif process == "firmwareless":
rename('firmware.zip', 'fw-less_' + codename + "_" + rom)
print("All done!")
rmtree("tmp")
rmtree('out')
else:
print("Failed!" + '\n' + "Check out folder!")
Replace this
Code:
def make_zip():
rom, process = arg_parse()
with open("out/META-INF/com/google/android/updater-script", 'r') as i:
codename = "NEW"
print("Creating " + process + " zip from " + rom + " for " + codename)
make_archive('firmware', 'zip', 'out/')
if path.exists('firmware.zip'):
if process == "firmware":
rename('firmware.zip', 'fw_' + codename + "_.zip")
elif process == "nonarb":
rename('firmware.zip', 'fw-non-arb_' + codename + "_.zip")
elif process == "firmwareless":
rename('firmware.zip', 'fw-less_' + codename + "_.zip")
print("All done!")
rmtree("tmp")
rmtree('out')
else:
print("Failed!" + '\n' + "Check out folder!")
V1.1 is here
I was reported that there's some firmware unmounting errors with some devices like mido.
Code:
unmount of /firmware failed; no such volume
mount: failed to mount /dev/block/bootdevice/by-name/sec at /firmware: Invalid argument
It was because of inaccurate grepping of lines with "firmware" in it.
Also, there's a missing line which caused temporary updater-script to be added in firmware zip.
These issues are fixed now. You can get the new update from here:
Py script: https://github.com/XiaomiFirmwareUpdater/xiaomi-flashable-firmware-creator
Executable files: https://github.com/XiaomiFirmwareUpdater/xiaomi-flashable-firmware-creator/releases/tag/V1.1
A new update is here 02-01-2019!
I've added an option to create firmware + vendor flashable zip which is good for treble devices
https://github.com/XiaomiFirmwareUpdater/xiaomi-flashable-firmware-creator.py
Link to executable files is down
Hi,
the link to the executable files is down.
Can you fix it, please.
Thanks...
poas12 said:
Hi,
the link to the executable files is down.
Can you fix it, please.
Thanks...
Click to expand...
Click to collapse
Here you are
https://github.com/XiaomiFirmwareUpdater/xiaomi-flashable-firmware-creator.py/releases/latest
TWRP: Error 6
Hi,
thanks for your fast support but when i try to install firmware-less.zip I get an error 6 from twrp.
Can you help me, please?
poas12 said:
Hi,
thanks for your fast support but when i try to install firmware-less.zip I get an error 6 from twrp.
Can you help me, please?
Click to expand...
Click to collapse
Can you give some details?
What's the device? Which ROM did you use?
Also attach twrp log after flashing.
TWRP: Error 6
Here the informations:
Xiaomi redmi Note 5 Pro (whyred)
TWRP 3.2.1.3 or TWRP 3.2.3.2
original ROM: miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip
modified ROM: fw-less_whyred_miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip
Message from twrp:
Installing zip file '/data/media/0/fw-less_whyred_miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Updater process ended with Error: 6
Error installing zip file '/data/media/0/fw-less_whyred_miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip'
poas12 said:
Here the informations:
Xiaomi redmi Note 5 Pro (whyred)
TWRP 3.2.1.3 or TWRP 3.2.3.2
original ROM: miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip
modified ROM: fw-less_whyred_miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip
Message from twrp:
Installing zip file '/data/media/0/fw-less_whyred_miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Updater process ended with Error: 6
Error installing zip file '/data/media/0/fw-less_whyred_miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip'
Click to expand...
Click to collapse
In order to know what went wrong I need to check twrp log. Please attach it.
TWRP: Error 6
Here's the log:
https://paste.tinyw.in/index.php/view/33616024
poas12 said:
Here's the log:
https://paste.tinyw.in/index.php/view/33616024
Click to expand...
Click to collapse
Can you try with official twrp or any other recovery?
TWRP: Error 6
But I have an official twrp for the Redmi Note 5 Pro (whyred).
https://eu.dl.twrp.me/whyred/
poas12 said:
But I have an official twrp for the Redmi Note 5 Pro (whyred).
https://eu.dl.twrp.me/whyred/
Click to expand...
Click to collapse
Are you using Windows or Linux?
The python script or the executable?
@yshalsager
A little unralated question.
Do you know if the firmware update folder inside Xiaomi EU roms is the firmware of the day or is a custom made by them?
Example: 9.1.10 Xiaomi EU Rom, inside the firmware update folder is from 9.1.10 China rom?
Or should i flash the firmware myself?
I couldn't get this awnser from them.
inouext said:
@yshalsager
A little unralated question.
Do you know if the firmware update folder inside Xiaomi EU roms is the firmware of the day or is a custom made by them?
Example: 9.1.10 Xiaomi EU Rom, inside the firmware update folder is from 9.1.10 China rom?
Or should i flash the firmware myself?
I couldn't get this awnser from them.
Click to expand...
Click to collapse
Yes, it's the same official firmware of that day.
You don't have to flash firmware as long as you use miui, whatever it was.
poas12 said:
Hi,
thanks for your fast support but when i try to install firmware-less.zip I get an error 6 from twrp.
Can you help me, please?
Click to expand...
Click to collapse
After doing some investigations, seems it's the windows who is making issues
Can you try this version?
https://hastebin.com/axufenuroj.py
V1.1.1 released
Changes:
- Fix files created on windows can't be flashed bug. It was because of the newlines endings on windows.
Windows users please update to latest versions of python script or the executable
TWRP: Error 6
With your new version 1.1.1 everything works fine! :good:
Thanks...
XiaomiFirmwareUpdater first anniversary!
An important announcement regarding the project.