Related
{
"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"
}
Latest OTA from V.7.3.1.0 to V.7.5.2.0
BLAZING FAST PERFORMANCE
A ROM by rsbaviskar for Micromax Canvas Knight.All Rights Reserved.All other trademarks are property of their respective owners.
Features :
-Based on Android 4.4.2
-Ported from Redmi NOTE 3G Global ( Beta Version )
-Pure MIUI
-Latest Version Es Explorer
-Titanium Backup
-GAPPS included
-Antivirus
-System & Memory Cleaner
-Record FM and Calls
-Privacy Management
-Power Management
-Data Saver Feature
-Block unwanted calls and messages
-Burst and HDR Modes in Camera
-One Handed Mode
-Guest Mode
-Brand New Headphones setting added.
-GOD OF CUSTOMIZATION :angel:
-New MIUI 7 Themes
-Redesigned App Icons
-New Settings Arrangement
-Better Toggle Style
-Notification Blocking in Notification Shade
-Improved System Performance
Read FAQ :
Please don't ask noobish questions, first read the FAQ
MIUI 7.5 Global Stable ROM Fulll Changelog
Messaging
Optimization - Accessibility in Messaging. Buttons for a call back and contact details, voice-over for attachments. (03-15)
Lockscreen, Status Bar, Notification Bar
Fix - Viewing Daily lock screens sometimes led to black screen (02-23)
Fix - Screen lit up multiple times after receiving a notification (03-10)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Delete - (For security reasons) "Forgot password" option for lock screen (03-04)
Delete - Manage guest access to notification shade (03-18)
Music
New - Dragging songs to rearrange playlist order (03-08)
New - Saving current playlist as a new playlist (03-08)
New - Shortcut for recently played songs (03-08)
Backup
Optimization - Mi Mover transfer speed (05-09)
Fix - Interruptions or unsuccessful file transfers in Mi Mover in some cases (03-01)
Fix - "Select app" page in Mi Mover sometimes didn't respond (03-10)
Fix - Errors with transferring files containing "%" in the name (03-10)
Fix - In some cases Mi Mover transfers interrupted and the app didn't respond (03-11)
Fix - In some cases Mi Mover stopped working after the connection was established (03-18)
Weather
New - New white design (04-27)
Permissions Manager
New - A security prompt will appear when an app is installed via USB to prevent unwanted installations (03-08)
Optimization - Preventing apps which have permissions to read notifications from starting automatically (03-16)
Clock / Calculator
New - Long press alarm to select and delete multiple alarms (03-29)
Mi Account
Optimization - Simplified sign-in process and creating Mi Account (04-19)
Cleaner
New - New design for Cleaner (04-27)
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
Security
New - Fingerprint unlock for custom apps (03-15)
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
Optimization - Improved performance for status bar (02-23)
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
Installation Instructions :
Code:
[SIZE="4"]-To Enable & Enjoy Latest Version OTA all you need to be on MIUI 7 ROM v.7.3.1.0 Global Stable.
-Start Recovery Mode. ( Use only PhilzTouch Recovery V3 provided in the given link below )
-Take full NANDROID backup Via recovery of previous or stock ROM .(In case of any problem)
-Then reboot recovery.
-Wipe data or factory reset.
-Wipe cache partition.
-Wipe Dalvik Cache.
-Clean to Install ROM
-Install MIUI 7 GLOBAL V.7.3.1.0 ROM followed by--->Latest OTA V.7.5.2.0--->Sound Enhancement patch.
-do set up your device without inserting SIM nor Connecting to WIFI on 1st boot.
-You Can Flash Dolby zip later on
[/SIZE]
Credits :
worstenbrood - For his Dolby Atmos.
XIAOMI & MIUI -For Providing the ROM.
Dr.Rahul(ME) & My Lovely Brother Dr.Rohan-For Endless Efforts.
DON'T FLASH ANY KERNEL
Note :
-IMPORTANT: FLASH AT YOUR OWN RISK. We are not responsible for any bricked phones or damages caused due to the ROM. You lose
warranty when you root/flash ROMS on your phone.
-BATTERY: Keeping at 100% charged is recommended before flashing.
-BACKUP: Take BACKUP from recovery, useful in case you mess up. Or try Titanium to backup all data and apps.
-Please do not mirror without permission.
-Do not port without permission
-Please read the FAQ first as it might help you.
-Please don't send PM. Ask queries in the thread only.
-Please do not send request to add any app / themes.
-This ROM will be kept as as close to pure MIUI to give a rich experience.
-Please don't ask for when will you update the ROM.
-I won't guarantee anything about my ROM. If you like it keep it otherwise the most simple thing you can do is switch to some other ROM.
DOWNLOAD SECTION
Download MIUI 7 Global Stable V.7.3.1.0 ROM For V3(Latest) : CLICK HERE
Download MIUI 7 Global Stable OTA from V.7.3.1.0 to V.7.5.2.0 For V3(Latest) : CLICK HERE
Download Philz Touch Recovery for V3 Micromax A350 : CLICK HERE
Download Sound Enhancement Patch : CLICK HERE
Download Dolby Atmos V6.5 : CLICK HERE
Download MIUI 7 Global (Dev) V.5.8.22 ROM For V2(unmerged partition) :CLICK HERE
Download MIUI 7 Global (Dev) V.5.9.25 ROM For V3 : CLICK HERE
Download OTA1 V.5.8.28 :CLICK HERE
Download OTA2 V.5.10.15 : CLICK HERE
Download OTA3 V.5.11.6 : CLICK HERE
Download EBR FOR 4GB APP STORAGE : CLICK HERE
Download EBR FOR 8GB APP STORAGE : CLICK HERE
Download EBR FOR 13GB APP STORAGE : CLICK HERE
Download EBR FOR REVERT TO V2 APP STORAGE : CLICK HERE
Download Philz Touch 6.47.7 KK for V2 Micromax A350 : CLICK HERE
Google Services & Login Error Fix : CLICK HERE
MIUI8 FOR A350 FORUM LINK : CLICK HERE
Hit thanks if you like my work :good:
FAQ :
Q1. How to move apps to Internal Storage ?
Ans. Moving apps to Internal storage does not works on MIUI.
Q2. How to Turn ON flash light from Lock Screen ?
Ans.The lock screen on the MIUI V7 had a few extra functions than the standard unlocking and shortcuts. One of them is turning flashlight On directly from the lock screen. For that, while the screen is active but locked, you just need to long press the home button and the torch / flashlight turns on. It would not turn off until you prompt it although the screen would go blank in a few seconds.
Q3.How to Change the look of Multitasking / Recent Menu ?
Ans.By default, when you press the Recent key (the left bottom one), the recent apps show up, and it is just the App icon that is seen. But, you can make it look like the iOS multitasking screen where large thumbnails are shown, with the preview of what is going on in the app. You can change that by pinching out on the empty area in the multitasking screen. Pinching in / out is what changes the look, basically.
Q4.How to Enable or Change Notification Light Color ?
Ans.There is an option that allows you to change the change the notification light as well as turn it off completely. To do that you have to go to Additional Settings section, and tap on notification light. There you would find four option, first would allow you to switch ON or OFF the Pulse Notification light while other options allow you to change colors for notifications, calls, as well as messages. You can choose only 2 colors ( GREEN OR RED ), which will appear in the LED present just below the home button.
Q5.Facebook Messenger pop-up head does not appears , what to do ?
Ans.Go to Security icon on the homscreen > Permissions > Again Permissions > Open Messenger > Enable Display pop-up window.
You can follow the same method for other apps as well which have the feature of pop-up head notification.
Q8.My Screen Orientation takes longer time than usual ?
Ans.Download Advance Tools app, go to sensors ,you will find total 9 sensors with info, keep you device on horizontal & Steady surface & press reset button by selecting individual sensors...
XDA:DevDB Information
MIUI 7 Global Stable Edition for Micromax A350, ROM for all devices (see above for details)
Contributors
rsbaviskar, rohanbaviskar530, Mr.AK, worstenbrood
Source Code: https://github.com/tpruvot/MT6592-KK-KERNEL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.4.2-V2 with EBR mods available & V3(merged storage)
Based On: MIUI
Version Information
Status: Stable
Current Stable Version: 7.3.1.0 & 7.5.2.0
Stable Release Date: 2016-07-25
Created 2015-09-04
Last Updated 2016-07-27
Great work!!! A flawless ROM!! No bugss found!!!
Note: I flashed it with cmw recovery, took 5 mins to flash, 5 mins to boot, have patience!!! Don't worry it will boot but take time.
Apk not getting updated over play store showing update on WiFi only: goto tool-->download> setting-> click unlimited. .... Done
Thanks again Dr......
@Praful Pradhan Thanks a lot bro for sharing your experience
Dr Rahul,
Many thanks for your efforts! Working flawless since last 2 days.
1) Just curious about the camera MPixel size as the default camera app doesn't show size options by MPixels . The Picture Quality options (High/Standard/Low) works fine.
2) Does both SIM cards work on 3G? (not sure if stock device has both 3G enabled)
3) Slight mis-alignment on slide up/slide down screens like in clock-alarm, Download limit setting type of pages. (can be ignored though)
4) USB Mass storage mode is missing (only Camera and MTP modes) even though this is for un-merged storages
Thanks
Vipin
Great Rom,Even Beter than miui6....REally Awesome Work Buddy...
Thanks AK,will add Screen shot soon
Downgrade to install miui 7
Praful Pradhan said:
Great work!!! A flawless ROM!! No bugss found!!!
Note: I flashed it with cmw recovery, took 5 mins to flash, 5 mins to boot, have patience!!! Don't worry it will boot but take time.
Apk not getting updated over play store showing update on WiFi only: goto tool-->download> setting-> click unlimited. .... Done
Thanks again Dr......
Click to expand...
Click to collapse
Hi Praful,
Need your kind help.
Using Micromax_A350_SW_V6.0_HW_V1.4_231214 rom and am not able to downgrade to v2 in order to activate partitions.
Downloaded Micromax_A350_V2_040614_KitKat but after doing Format all+Download in Smart Phone flash tool the phone doesnt boot.
After above step if flash the rom V6.0 with Format all + Download the phone works.
Is it the error with the V2 rom am i flashing it in a wrong way...
Please help cant wait to use Miui 7 rom.
Thanks in advance
Vaibhav
buntys82 said:
Hi Praful,
Need your kind help.
Using Micromax_A350_SW_V6.0_HW_V1.4_231214 rom and am not able to downgrade to v2 in order to activate partitions.
Downloaded Micromax_A350_V2_040614_KitKat but after doing Format all+Download in Smart Phone flash tool the phone doesnt boot.
After above step if flash the rom V6.0 with Format all + Download the phone works.
Is it the error with the V2 rom am i flashing it in a wrong way...
Please help cant wait to use Miui 7 rom.
Thanks in advance
Vaibhav
Click to expand...
Click to collapse
Silly Mistake Buddy,U Need To select Upgrade Frimware in Sp Flash tools Install OF Format All...
If Any other problems msg me here on whatsapp +919468519959
Mr.Ak said:
Silly Mistake Buddy,U Need To select Upgrade Frimware in Sp Flash tools Install OF Format All...
If Any other problems msg me here on whatsapp +919468519959
Click to expand...
Click to collapse
Imei lost...so no phone working...will surely add you once my starts..
Did Upgrade firmware but the phone wasnt booting..
getting below error..on trying v1 BROM ERROR.
Main error is due to ur using same file again and again of mmx350.
The ROM file u downloaded I.e. zip file... Extract it again... And use it in SP tool as fresh one....or use wiko highway v19 file... Remove sim while flashing.. Restore imei..with the help of mtk tool..
Best of luck
Hits thanks if like...
Sent from my Micromax A350 using XDA Free mobile app
worked very fine in my.
No bugs till now.
The only thing that I found is that miui has a new update that doens't work.
Thanks for this rom!
Yes true updates downloaded but not applied due to phone build issue... As it is not xiomi phone...
Sent from my Micromax A350 using XDA Free mobile app
Error details
Starting recovery on Mon Sep 7 22:59:04 2015
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1080 x 1920)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 21.09.2013 13:16:45
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p5 (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /sdcard vfat /dev/block/mmcblk0p8 (null) 0
5 /external_sd vfat /dev/block/mmcblk1p1 (null) 0
6 /boot emmc /dev/bootimg (null) 0
7 /recovery emmc /dev/recovery (null) 0
8 /uboot emmc /dev/uboot (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
persist.sys.usb.config=mass_storage
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.build.id=JDQ39
ro.build.display.id=ALPS.JB9.MP.V1.4
ro.build.version.incremental=37
ro.custom.build.version=S9320_Agua_Infinity_20140304_V10
ro.internal.build.version=S9320_MP_PH_MYP_16_16
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Fri Mar 21 20:49:53 CST 2014
ro.build.date.utc=1395406193
ro.build.type=user
ro.build.user=android
ro.build.host=HTSVR7
ro.build.tags=release-keys
ro.product.model=MyPhone Agua Infinity
ro.product.brand=MyPhone
ro.product.name=MyPhone_Agua_Infinity
ro.product.device=MyPhone_Agua_Infinity
ro.product.board=MyPhone Agua Infinity
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=MyPhone
ro.product.locale.language=en
ro.product.locale.region=PH
ro.wifi.channels=
ro.board.platform=
ro.build.product=MyPhone Agua Infinity
ro.build.description=s9320ae-user 4.2.2 JDQ39 37 release-keys
ro.build.fingerprint=MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/release-keys
ro.build.flavor=
ro.build.characteristics=default
ro.mediatek.version.release=ALPS.JB9.MP.V1.4
ro.mediatek.platform=MT6592
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB9.MP
ro.mediatek.version.sdk=1
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
wifi.interface=wlan0
ro.mediatek.wlan.wsc=1
ro.mediatek.wlan.p2p=1
mediatek.wlan.ctia=0
wifi.tethering.interface=ap0
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=300m
dalvik.vm.heapsize=300m
ro.sys.usb.mtp.whql.enable=0
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
ro.sys.usb.bicr=no
ro.sys.usb.charging.only=yes
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
net.tinno.bt.name=S9320
net.change=net.bt.name
persist.lcd.pq.pqparam=30gggggggg
persist.sys.timezone=Asia/Manila
persist.wifi.firmware=1
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=1
ro.sf.lcd_density=180
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=MTK_CONNSYS_MT6592
mediatek.wlan.module.postfix=_mtk_connsys_mt6592
ril.radiooff.poweroffMD=0
ter.service.enable=0
persist.sys.display.clearMotion=1
persist.clearMotion.fblevel.nrm=255
persist.clearMotion.fblevel.bdr=255
ro.config.ringtone=MyPhone_Online_Pop.ogg
ro.config.notification_sound=MyPhone_Tune.ogg
ro.config.alarm_alert=RingingAlarm.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.2_r3
persist.sys.skin=/system/framework/theme-res-mocha.apk
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.adups.fota.oem=MTK88_92
ro.adups.fota.device=MyPhone Agua Infinity
ro.adups.fota.version=ALPS.JB9.MP.V1.4
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6592
ro.revision=0
ro.emmc=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Signature Check: Enabled
-- Installing: /sdcard/update.zip
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
Installation aborted.
-- Installing: /sdcard/downloaded_rom/update.zip
Finding update package...
I:Update location: /sdcard/downloaded_rom/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Updating package '/sdcard/downloaded_rom/update.zip' ...
__bionic_open_tzdata: couldn't find any tzdata when looking for Asia/Manila!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting updater on Mon Sep 7 23:00:28 2015
============= emmc ===============
name: HBG4e
manfid: 0x000090
date: 09/1997
cid: 90014a4842473465040201a2d9349069
csd: d02701320f5903ffffffffef8a4040d3
oemid: 0x014a
erase_size: 524288
preferred_erase_size: 524288
stat: 477 1395 93752 1270 21 23 360 4740 0 3850 6010
============= prop ===============
ro.build.fingerprint=MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/release-keys
ro.build.version.release=4.2.2
ro.build.version.incremental=37
ro.build.product=MyPhone Agua Infinity
ro.product.device=MyPhone_Agua_Infinity
ro.product.mod_device=unknown
ro.miui.ui.version.name=unknown
Warning: No file_contextsscript aborted: Package expects build fingerprint of Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.22:user/release-keys or Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.28:user/release-keys; this device has MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/release-keys.
Package expects build fingerprint of Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.22:user/release-keys or Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.28:user/release-keys; this device has MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/releasdevice name: /[email protected]
Filesystem volume name: <none>
Last mounted on: /system
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem flags: unsigned_directory_hash
Filesystem features: has_journal ext_attr resize_inode filetype recover extents sparse_super large_file gdt_csum
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem os type: Linux
Inode count: 131072
Block count: 524032
Reserved block count: 0
Free blocks: 339260
Free inodes: 128174
First block: 0
Block size: 4096
Reserved GDT blocks: 127
Blocks per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Mon Sep 7 23:00:28 2015
Last write time: Mon Sep 7 23:00:28 2015
Mount count: 2035
Maximum mount count: 65535
Last checked: Thu Jan 1 00:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 1225 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
E:Error in /sdcard/downloaded_rom/update.zip
(Status 7)
Installation aborted.
My bateri now lives for 2 days! awesome!
Thanks a lot @profetaii,hope u r enjoying MIUI 7.M currently working on some other project ,but also trying to provide latest OTA Update of MIUI 7 V.5.8.28 Soon..as m able to successfully modify OTA files as per device.soon provide screenshots guys
Very very Thanks!!!
rsbaviskar said:
Thanks a lot @profetaii,hope u r enjoying MIUI 7.M currently working on some other project ,but also trying to provide latest OTA Update of MIUI 7 V.5.8.28 Soon..as m able to successfully modify OTA files as per device.soon provide screenshots guys
Click to expand...
Click to collapse
Thanks for your efforts for providing such a great bug Free ROM!!!!
Can you make it with V3 - (merged storage ROM) of MMX350!!!
Best of luck for your efforts!!
Miui7 an tu tu score 31k... Not happy....as 32k was for wiko highway v19!!!
Sent from my Micromax A350 using XDA Free mobile app
can we flash this rom on Micromax gold
Just to update following things for this ROM!!1
Roaming working fine for both the sim!!! - took 5 mins to search network but finally OK
Data in Roaming working Fine !!!
One major issue I'm facing is security apk updates!!!
There is no automatic update!!!
Any one plz help!!
In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
Here is for sharing of experiences and discussions.
There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there.
Known Issues:
1. AOSP Camera App The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that. 2. "E:unknown command [log]" If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP. 3 Please report.
Tips:
1. DT2W At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results. 2. Built-in File Explorer There is an built-in file explorer in AOSP. We can explore the files as well as installing apks.
Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)Change log:
Code:
[COLOR="Blue"]2017/5/3[/COLOR]
- Android-7.1.2_r11 (NHG47L)
[COLOR="Blue"]2017/4/9[/COLOR]
- Android-7.1.2_r5 (N2G47J)
- PerformanceControl: boot up settings fixed
- Fix Wifi hotspot
- Performance patches
[COLOR="Blue"]2017/3/8[/COLOR]
- Android-7.1.1_r28 (N6F26U)
[COLOR="Blue"]2017/2/8[/COLOR]
- Android-7.1.1_r21 (NOF26W)
[COLOR="Blue"]2017/1/6[/COLOR]
- Android-7.1.1_r13 (N6F26Q)
- Camera: Fix video recording
[COLOR="Blue"]2016/12/16[/COLOR]
- Android-7.1.1_r6 (NMF26Q)
- SEPolicy update
[COLOR="Blue"]2016/12/7[/COLOR]
- Android-7.1.1_r4 (NMF26O)
- Fix the Camera
[COLOR="Blue"]2016/11/11[/COLOR]
- Android-7.1.0_r7 (NDE63X)
[COLOR="Blue"]2016/10/24[/COLOR]
- Android-7.1.0_r4 (NDE36P)
- Remove every recovery related resources
[COLOR="Blue"]2016/10/14[/COLOR]
- Android-7.0.0_r14 (NBD90Z)
- Shield the occasional crash in MTP Document provider
- USB and Bluetooth Tethering support enabled
[COLOR="Blue"]2016/9/23[/COLOR]
- Android-7.0.0_r6 (NRD90U)
- latest DC kernel (Android-7.0 branch)
- PerformanceControl: version 2.1.6
- Find a way to fix the hwcomposer for video/audio playback, need to review later
- A few sepolicy patches for Gapps and Mediaserver
- SELinux: Enforcing
Downloads: :highfive:
Hosts: Android File Host MEGA mirror: 百度网盘
Note: I only tested it in TWRP 3.0.2.
PerformanceControl app requires ROOT access.
Root access can be obtained by the systemless SuperSU from @Chainfire.
Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested
Sources:
Sources in github
Credits: :good:
** Definitely the AOSP
** The AndroidFielHost provide a FREE host with no limits and expiration.
** All the developers who help the Nexus 7 (2012) development
** All those who donate and/or help the developers. Giving us the resources and reason to carry on.
Donations: :angel:
{
"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"
}
Discussions
Anyone has any idea are welcome to post here
DT2W
Sometimes it won't wakeup after a long DEEP_SLEEP
When volume buttons are also enabled for wakeup. It won't work too. Seems there are situations "soft pwr button press" won't work.
Fail after reboot
Code:
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
Some of you might encounter the above message after reboot. I never encountered before but there is definitely something wrong.
@millosr found that it was the recovery being replaced. I think that make sense and I want to study why.
I looked into the source. In the original AOSP, an OTA might come with a recovery patch. Stated in the build/core/Makefile "boot.img + recovery-from-boot.p + recovery-resource.dat = recovery.img"
It would generate the "recovery.img by the above formula itself. Custom ROMs usually won't carry a recovery and this part was usual ignored.
There is a warning in TWRP before reboot. Some of you might not read clearly and slide to continue immediately. In that case, the above mentioned recovery.img will be generated and flashed to the /recovery partition. Everything seems normal but after reboot.
When the script kick in, it would execute the "new" recovery. As a normal recovery, it would load the fstab and try to mount the partitions. The current fstab version is API 3. Almost all ROMs (no matter how close to AOSP) would have F2FS support. When we open a typical fstab:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,nodiratime,discard,inline_xattr,inline_data,inline_dentry wait,check
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,journal_async_commit,errors=panic wait,check
Note that the second line is the declaration for the /cache in f2fs. Stock AOSP recovery doesn't support f2fs. That's why the above error shown. Since it fail to mount /cache, the last_locale is not loaded and recovery would hang.
How to recover?
Naturally, you have to flash TWRP again.
First of all, you need to boot into bootloader (fastboot mode)
Some init.xxx.rc might start adbd earlier and in this case "adb reboot bootloader" would do the job.
If adbd was not started before the hang, the command won't work. In this case you can only use the pwr+vol. down combination.
If it is still hanging, the buttons might not work. Press the power button continuously might lead to repeatedly reboot. It is better to make sure the device is OFF first.
1. Connect to a charger.
2. Press the power button until you see the charging image
3. Release the power button immediately.
4. After that, press the volume down button first, and then the power button.
It would go to the bootloader.
Note: /system is not really formatted during flashing. To make sure no residue left in /system, it is better to wipe the /system before flashing.
For ROM builders, there is a flag BOARD_USES_FULL_RECOVERY_IMAGE. Set it to true will stop the generation of recovery-resource.dat (in /system/etc) and break the above formula.
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Nintonito said:
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Click to expand...
Click to collapse
obviously.
---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------
@daniel_hk good to see a separate thread. Will test this build this weekend as i am already on grouper.
：手指划线：
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
ho0o0o11111 said:
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
Click to expand...
Click to collapse
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
daniel_hk said:
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
Click to expand...
Click to collapse
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
ho0o0o11111 said:
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
Click to expand...
Click to collapse
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
daniel_hk said:
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
ho0o0o11111 said:
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
Click to expand...
Click to collapse
Which version? eariler version might have a wrong fstab which have issue on f2fs.
Make sure you got the latest version 3.0.2
You can't go to boot loader?
That means you press pwr+vol down and it won't reboot to bootloader?
That's strange.
"adb reboot bootloader" only work if the adbd is up. That means you can use "adb devices" to check the existance of your device.
You may try this:
1. connect to the charger
2. pressing the pwr button for > 8 seconds.
See if the tablet reboot. If yes, it would boot into charging mode. Pwr+vol down again would work.
If it doesn't reboot after you pressed say 20 seconds, you need to remove the battery.
Good luck!
@daniel_hk
Thanks for the new AOSP build Daniel. Nice work fixing the hardware decoder, my Netflix is now working and I was able to play one of my MP4 movies with BS Player in HW mode. I've been changing back and forth between your first AOSP 7 build and your DU 7 build with dirty flashes. With this build I decided to clean flash and at first things were very sluggish but settled down after a reboot and probably after Google finished whatever it does in the background. LOL Aside from a few occasional random force closes, it's running pretty well.
A couple of observations:
As mentioned, I did a clean install with this build. I'm using official TWRP 3.02 and installed the rom and 7.0 Open Gapps nano 20160915 at the same time and when it booted up for the first time, there were no gapps installed. I powered down and then went back into TWRP and reflashed the gapps, this time they were there upon reboot. Surprisingly, I didn't have to set permissions for Google Play or Play Store, as they were already correctly set??? I did run into a snag when trying to download apps from PS, clearing the data for the download manager app solved that problem for me.
I installed a camera app (HD Camera) from Play Store and it works but when I use my phone's camera, it reminds me how crappy the N7 camera is. LOL
After setting things up, I wanted to try phhsuperuser (no Magisk) to root and it went fine. All of my apps that require root worked...except Titanium Backup. I tried uninstalling/reinstalling both phhsuperuser and Titanium but couldn't get it to work. I rely on Titanium quite a bit, so I flashed Supersu 2.78 and all's well.
Thanks again.
Mike T
Do games work on this rom?
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
paasoares said:
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Click to expand...
Click to collapse
In any case, it's a good practice to read the console after flash anything. There might already be essential messages which not necessarily in red.
I also experience SuperSU need to flash again. I just found out something that might help. Seems SuperSU would use the cache to start a checking process in the next boot. I don't know if it would help gapps too.
1. Try factory reset before flashing.
2. Flash ROM+Gapps+SuperSU
3. After that don't do wipe cache/d-cahce again. (factory reset already include this action)
Good luck!
3yan said:
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Click to expand...
Click to collapse
I think you meant "Enforcing". Yes, it is enforcing. Only some Custom ROM would show this in About but not AOSP.
There is a shell command "getenforce" which you can check the SEPolicy status.
If you read the OP, you would know its an AOSP without any mod/tweak, just porting. You can get the manifest and all the helps in https://source.android.com.
Good luck!
fat-lobyte said:
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
Click to expand...
Click to collapse
Chrome has many versions and it should not be an untrusted app. I'm testing the CarbonROM which has a bloated Chrome and being treated as isolated app. It might take time for those UID's being properly handled.
I already included some extra permissions which would be include in my later builds.
Anyway, we would encounter denials more often in apps. That's what newer Android intent to do.
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
I wanted to try this 'Sept 23' ROM as it should play video OK: in the end I got it to work, and I can now indeed play video in some video based apps that did not work before. I used the older DU ROM and also the nAOSP ROM of millosr. There video does not work yet.
But with this Sept23 ROM I had a fight with Gapps to get it to work... First the Gapps I normally use failed to install in TWRP. At least, that is what I think I saw: the progress bar suddenly jumps ahead as if the install process was broken off somehow. So I again clean wiped all and now used opengaps-pico. That installed fine, but on first boot, no gapps. So I again installed opengapps and now finally I had working playstore. Strange, I never ran into something like this before (I am mostly active on Xperia S with nAOSP).
But the story ends well, as my video now works: great job !
fat-lobyte said:
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
Click to expand...
Click to collapse
Did you set "keep wi-fi on during deep sleep" to NEVER?
My tablet drain 5% during this night (about 8 hours), so i guess this is normal/acceptable
Poison Kitchen IDE
Development preview
{
"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"
}
Description
A powerful IDE for android ROM development
Runs native on WINDOWS, MacOS themed.
Its powered by my XanderUI class library for the .net framework
Currently Development preview builds are only available, meaning things may be broken, behave incorrectly or other
Click to expand...
Click to collapse
Features
-Full GUI coded in C# for fast runtime
-XanderUI based controls(My C# class library)
-Based on .net 4.5
-Support for every single android version
-Unpack rom from (.zip, .tar, .md5, .img, aml_upgrade_package)
-Pull all required files from device(root needed to copy kernel block)
-Adb, fastboot and drivers installater
-ROM information
-Explorer
-Deodexing(4.4.4 and lower ATM)
-Unpacking the kernel
-Converting file_contexts.bin to standard text
-Kernel explorer
-Repacking kernel
-Logging
-Auto-generating updater-script
-Use generic symlinks if files detected
-Use generic file contets if the kernel does not contain file_contexts
-/data/app auto transition to new rom(somewhat working)
-Wipe data excluding /data/media(/sdcard path)
-Auto kernel block detection
-Auto mounting /system and /data
-Packing rom
-Signing rom
-Updater-script editor
-Extansion support
-Emulated exension scripts(applied via C#)
-Degapps extension
-Deknox extension
-Custom emoji extension
-Enable sony apps extension
Click to expand...
Click to collapse
Features not yet implemented
-root via magisk(systemless) and superSU(standard)
-init.d
-deodexing 5.0 and up
-adbd insecure
-init.d tweaks
-build.prop tweaks
-change display I.D
-add sysrw/ro binary
-logging needs tweaking
-loading rom information updated in the background
-Unpacking RUU as project(HTC)
-Unpacking TFT as project(SONY)
-Unpacking system.dat(sparse)
-Setting your actual device as the project and apply changes in realtime
-/data/app auto transition to new rom
-Kernel may not unpack
-Convert line endings in explorer context menu
-Inbuilt file editor(with EOL auto-detection)
-Boot animation player/changer
-Auto flash rom with ORS(TWRP)
-Bluestacks as rom
Click to expand...
Click to collapse
Settings
Load settings()
-Set default startup project or startup menu
-Enable/disable logging
-Stop logger from detecting files or folders added, deleted, changed or moved
Installation settings()
-Change romname
-Change installation type(autodetect on unpack, User generated, Tool generated)
-Change file contexts method(Auto, extracted from kernel, assumed)
-Enable/disable safewipe
-Enable/disable data/app auto transition
-Enable/disable autodetect ernel blockpath(add path below)
Pack settings()
-Change compression level
-Add signing method(pack into presigned, sign on zip, none)
-Change java heapsize
-Exclude files and folders from being packed/detected by IDE
Default program settings()
Change default program to open image files
Change default program to open video files
Change default program to open audio files
Change default program to open prop files
Change default program to open archive files
Change default program to open jar/apk files
Change default program to open other type files
Current version and updates()
Cleanup settings()
Click to expand...
Click to collapse
License
GNU GPL V3
Downloads
Downloads page
XDA:DevDB Information
Poison Kitchen IDE, Tool/Utility for the Android General
Contributors
Ricky Divjakovski
Version Information
Status: Testing
Created 2018-04-19
Last Updated 2018-04-19
Creating extensions and documentation
Code:
Description -
As extensions are a great adittion to the IDE, whats the use if you cant make your own for automated building?
Information you need to know -
The tool looks for the file "extension.info".
In the extension.info file you will specify the extension name, description and the poison shell script file(.psh).
Package the folder containing the extension as a zip archive
------------------------------------------------------------------
Entension index
------------------------------------------------------------------
Sample extension -
https://github.com/Ricky310711/Poison-Kitchen-Extension-Example
extension.info -
Lines will only be read if starting with "Name", "Description" or "Run"
-------------------- code exmpla
# this sets the extension name
Name:Fake optimizer
# this sets the extension description
Description:Do not apply this to rom, its a fake extension to show an example
# this is the poison script to run(must be in same directory)
Run:FakeOpt.psh
------------------------------------------------------------------
Scripting language(.psh file)
------------------------------------------------------------------
Information
-Must be linux EOL(\n)
-Anything but recognised 1st args are ignored
-Any errors will be ignore by the shell
-Use full paths asif you are in the root(/)
Extracting content to rom
---------- code example
EXTRACT|myFolder
1st arg states we are extracting(copying) a folder to the rom
2nd arg is the folder to extract(must be in same directory as extansion)
NOTE: This will extract the folder to the root of the rom
Changing a line in a file
---------- code example
CHANGE|START|/system/build.prop|ro.product.device=|THIS IS STARTS TEST
1st arg specifies we are changing a file
2nd arg specifies where on a line to search for the string(arg4)
3rd arg specifies the file to change
4th arg specifies the string to look for
5th arg is what you would like to replace the line with
The second arg can be START, CONTAINS or END
Appending a file
---------- code example
APPEND|TOP|/system/build.prop|# A TEST FOR APPENDING TOP
1st arg specifies we are appending a file
2nd arg specifies if we are appending at the TOP or BOTTOM
3rd are is the file to append
4th arg is the content to append
Remove a line from a file
---------- code example
REMOVE|/system/build.prop|# end fota properties
1st arg states we are removing a line from a file
2nd arg specifies the file
3rd arg is the string to look for in the line
Delete a file or folder
---------- code example
DELETE|/system/preinstall
Pretty straight forward, will delete a file or folder called "preinstall" from /system/
Create a file or folder
---------- code example
CREATE|DIRECTORY|/preinstall
arg 1 states we are creating something
arg 2 specifies if a FILE or FOLDER
arg 3 is the file or folder to create
Rename a file or folder
---------- code example
RENAME|/system/bin/am|amRenamed
1st arg specifies we are renaming a file or folder
2nd arg is the file or folder
3rd arg is the new name
Changelog
Development preview 2
-Added pull rom from device in setup
-Smoother nvigation
-XanderUI 1.6.0 integration
-Message boxes are now themed like the app
-Extensions now show progress upon running
-Deodexing up to Android 4.4.4 implemented
Development preview 1
-initial release
reserved3
supports all versions of android and all devices, no manual input needed.
dev preview 3 possibly tommorow
Yay now I can at least try to build my own g6 ROMs. Nice work.
development on hold until the 30th as im on holiday, i have been dedicating little time to this as internet here is extremely slow
Magisk and SU support added aswell as deodexing 5.x > 6.0
Also working on disabling signature verification, adding sysrw(as binary)
hi, im trying out the program, it never completes the extraction, and the progress icon starts at 53% do i need to do anything when trying to start the program.
i haVE TRIed running as administartor and without running as admin.
thanks
Twisted714 said:
hi, im trying out the program, it never completes the extraction, and the progress icon starts at 53% do i need to do anything when trying to start the program.
i haVE TRIed running as administartor and without running as admin.
thanks
Click to expand...
Click to collapse
A dialog will more then likely poppup requesting permission to run imgextractor.exe, be sure to accept that to complete the process
Ricky Divjakovski said:
A dialog will more then likely poppup requesting permission to run imgextractor.exe, be sure to accept that to complete the process
Click to expand...
Click to collapse
i am attaching some pics to what happens.
please advise. thanks
there are a couple more that are insignificant
Twisted714 said:
i am attaching some pics to what happens.
please advise. thanks
there are a couple more that are insignificant
Click to expand...
Click to collapse
Could you please PM me with pics of the firmware your selecting or even a link?
I've gone ahead and tried this. I pointed the app to my system.img (not the fastboot zip) and ended up with "error extracting". Tool looks promising. ROM is available for download here:
http://en.miui.com/download-333.html
I extracted it and used the images/system.img
oreo27 said:
I've gone ahead and tried this. I pointed the app to my system.img (not the fastboot zip) and ended up with "error extracting". Tool looks promising. ROM is available for download here:
http://en.miui.com/download-333.html
I extracted it and used the images/system.img
Click to expand...
Click to collapse
Im going to test now, if the firmware has system.transfer.list, and system.dat, it will not be able to be unpacked until i make a native library or extension to perform the operation as i think it would be extremely stupid for the need to have python installed to run.
The only reason i havent rebuilt smali/baksmali etc is 1. Would take me months, 2. we are modifying a system that relies on java to operate.
in future, hefty operations like unpacking etc, will be coded in ASM/C code for faster operation, Im planning on making the whole project open source to allow changes and fixes submitted by other developers, So if anyones interested let me know and ill upload the source code(Written in C# for the .net 4.5 framework)
Ricky Divjakovski said:
Im going to test now, if the firmware has system.transfer.list, and system.dat, it will not be able to be unpacked until i make a native library or extension to perform the operation as i think it would be extremely stupid for the need to have python installed to run.
The only reason i havent rebuilt smali/baksmali etc is 1. Would take me months, 2. we are modifying a system that relies on java to operate.
in future, hefty operations like unpacking etc, will be coded in ASM/C code for faster operation, Im planning on making the whole project open source to allow changes and fixes submitted by other developers, So if anyones interested let me know and ill upload the source code(Written in C# for the .net 4.5 framework)
Click to expand...
Click to collapse
Not sure if this helps but I've run Imgextractor directly on my system.img with this result:
Code:
Mi-A1-Repository>Imgextractor Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img
ImgExtractor version 1.3.6 <Created by And_PDA (Based on sources ext4_unpacker)>
Extractor for images in EXT2\EXT3\EXT4\YAFFS2\CRAMFS filesystem formats
support SPARSE\SIN\MOTO structure formats
Open image file Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img (size 3221225472 bytes) successfull...
Analize format of file. Please wait...
Found SPARSE FORMAT
Found EXT4 FORMAT
free space in image 188895232 bytes
Extract started. Please wait...
Extract 750 folders and 6306 files successfull
Found 386 symlink files
File stats (uid, gid, permission) save to Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system__statfile.txt
Extract finish success
Press Enter to continue...
oreo27 said:
Not sure if this helps but I've run Imgextractor directly on my system.img with this result:
Code:
Mi-A1-Repository>Imgextractor Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img
ImgExtractor version 1.3.6 <Created by And_PDA (Based on sources ext4_unpacker)>
Extractor for images in EXT2\EXT3\EXT4\YAFFS2\CRAMFS filesystem formats
support SPARSE\SIN\MOTO structure formats
Open image file Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img (size 3221225472 bytes) successfull...
Analize format of file. Please wait...
Found SPARSE FORMAT
Found EXT4 FORMAT
free space in image 188895232 bytes
Extract started. Please wait...
Extract 750 folders and 6306 files successfull
Found 386 symlink files
File stats (uid, gid, permission) save to Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system__statfile.txt
Extract finish success
Press Enter to continue...
Click to expand...
Click to collapse
Found the error, the img file is of a wierd format, as its named system.img, it actually contains files from the root, so within the system.img the the root of the image is actually the root of the device rather then the root of the system partition, its extremely odd but none the less extremely simple to fix
Issue is already fixed and will be included in dev preview 3, that is expected for public release in a day or so with much more additions
Ricky Divjakovski said:
Found the error, the img file is of a wierd format, as its named system.img, it actually contains files from the root, so within the system.img the the root of the image is actually the root of the device rather then the root of the system partition, its extremely odd but none the less extremely simple to fix
Issue is already fixed and will be included in dev preview 3, that is expected for public release in a day or so with much more additions
Click to expand...
Click to collapse
Yeah. I found it odd that the system.img had a /system directory in it. Awesome! Can't wait
Ricky Divjakovski said:
Could you please PM me with pics of the firmware your selecting or even a link?
Click to expand...
Click to collapse
its on mega.
https://mega.nz/#!dCA2mAYS!-GrKWuuTNODaYEbt3LWiw4LJzxkrz5wI3T94mQ4PU90
it is a android 6 to android 7 full update. its installed, but i am trying to learn cobble together a rom. this img is for a zoomtak upro, i have found today an image for the uplus/vplus. it has much more stuff in it.
thanks
Twisted714 said:
its on mega.
https://mega.nz/#!dCA2mAYS!-GrKWuuTNODaYEbt3LWiw4LJzxkrz5wI3T94mQ4PU90
it is a android 6 to android 7 full update. its installed, but i am trying to learn cobble together a rom. this img is for a zoomtak upro, i have found today an image for the uplus/vplus. it has much more stuff in it.
thanks
Click to expand...
Click to collapse
I will check it when i get home, if its an upgrade package, i cannot ad support for it..
Welcome to the one and only, the original, universal,
System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac
Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW, F2FS-2-RW, EROFS-2-EXT4-CONVERTER, F2FS-2-EXT4-CONVERTER, Super Resizer/Flasher, SYSTEM-RW / PRODUCT-RW / VENDOR-RW / ODM-RW, root enhancer, real root, FULL ROOT, RW MULTI TOOL and many more aliases!
(NOTE: Full F2FS-RW support coming in 1. quartal 2023 ! Get your Samsungs ready!)
The prophecy has finally been fulfilled.
Making Android ten years younger!
Inspiring a whole generation of talented developers and empowering the open source community.
The Pandora's Box has been fully unlocked at last!
The genie has been unleashed from within the bottle!
Sesame! Open up now!
Let the Olympic Android System Modding Games (OASMG) begin!
The power is now in YOUR hands! And don't forget:
With great power comes great responsibility!
Creation date: February 2021
Updated: January 2023
Requirements:
rooted STOCK Android 10 or newer
at least 10+ GB free space on phone for dumping data
Description:
A script for all Android power users that wish to make their read-only Android 10+ system read/write-able again to remove bloatware and make more thorough customizations to their device.Script only modifies super and vbmeta partitions. /data partition is not affected. It's only used for dumping data and for storing script files.In a nutshell this is what the script is doing:
Spoiler: What is the script doing under the hood?
dumps your existing super partition
extracts embedded read-only sub-partitions (system, system_ext, odm, vendor, product...) from specified super image
makes these sub-partitions read/write-able using the one and only original MakeRW/ro2rw algorithm
joins everything back together to new super.img
flashes read/write-able patched super image back to device using the super fast Kolibass technique (only available in recovery mode)
NOTE:
The script can be run both inside custom recovery and inside Android operating system.
If you run script in Android mode you will need to fastboot flash the patched image(s) manually!
To check whether or not the script worked correctly you can run this code:
Bash:
adb shell
su
mount -o remount,rw /
mount -o remount,rw /odm
mount -o remount,rw /product
mount -o remount,rw /system_ext
mount -o remount,rw /vendor
mount | grep dm- | head -5
Manual installation:
Spoiler: Manual installation
Extract flashable.zip and copy sysrw_*VERSION* folder into /data/local/tmp/
run this command to make the script executable:
chmod +x /data/local/tmp/sysrw_*VERSION*/sysrw
Automatic installation:
Spoiler: Automatic installation
Installation of the script has never been this easy!Download the flashable.zip below, do NOT enable zip signature verification and simply install it in your custom recovery (works in TWRP, OrangeFox and PBRP!)The update binary will auto-detect the arguments in config.ini and launch the script accordingly
Flashable zip custom usage:
Spoiler: Flashable zip custom usage
You can easily modify the custom script execution arguments in the included config.ini file. Simply extract the flashable.zip, edit the included config.ini file with notepad and then save the file. Next compress the sysrw_*VERSION* and META-INF folders again as a new flashable .zip and install it in recovery. Have fun playing around with your config.ini
Script usage:
Simply execute the program from the terminal shell with or without custom argumentsOptional script arguments:
Spoiler: Optional script arguments
Replace x with your custom value
in=x
Specify existing super image as input [OPTIONAL]
Omitting this parameter is equivalent to using [email protected] which is equivalent to using your super block device as input
out=x
Specify patched super image output file path [OPTIONAL]
Omitting this parameter is equivalent to using [email protected] and the patched super image will be saved as ./img/super_patched.bin by default
size=x
Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL]
Omitting this parameter is equivalent to using [email protected] which will activate the auto-resize feature
-r
Specify whether or not the patched super image should be output in raw file format [OPTIONAL]
Omitting this parameter will create a sparse patched super image by default
Usage examples:
Bash:
adb shell
su
cd /data/local/tmp/sysrw_1.33
chmod +x ./sysrw
# Run program with default settings [RECOMMENDED]
./sysrw
# Specify existing super image as input [OPTIONAL]
./sysrw in=./img/super_original.img
# Specify patched super image output file path [OPTIONAL]
./sysrw out=./img/super_patched_new.img
# Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL]
./sysrw size=15
# Specify whether or not the patched super image should be output in raw file format [OPTIONAL]
./sysrw -r
# EXPERT EXAMPLE (Warning! This command could potentially corrupt your system. Only use at your own risk in recovery mode!)
./sysrw in=img/super_original.bin out=`realpath /dev/block/by-name/super` -r
Uninstallation:
Spoiler: Uninstallation
To free up space and keep script as well as r/w capability you can simply delete /img subfolder at /data/local/tmp/sysrw_*VERSION*/img
To delete script and keep r/w capability you can simply delete whole script folder at /data/local/tmp/sysrw_*VERSION*
To undo all changes performed by the script you can simply reflash original stock read-only super image and re-enable dm-verity and verification either through adb/fastboot or with the included avbctl binary.
Troubleshooting:
Spoiler: Troubleshooting
If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeniERROR 73: Troubleshooting repair script instructions@harpreet.s slot switching workaroundIf you get any errors from the update-binary in your custom recovery during installation of the flashable .zip then please send me this log file /tmp/recovery.logand a screenshot of your error. Thanks! Make sure the script folder was correctly extracted to:/data/local/tmp/sysrw_*VERSION*If you can't run the script try making the file executable like this: chmod +x ./sysrwIf you still can't get it to work run which sh in your shell and replace the shebang in the first line of the script with the output of that command. Don't remove the first two #! symbols though. Then save the file and try again.Make sure you've got full read / write access to the /data/local/tmp directory and that the containing files are not encrypted in custom recovery!If you get a bootloop after successfully creating and flashing super_patched.bin then that's probably because you didn't properly disable your dm-verity and verification.To undo any bootloop simply re-flash original stock read-only super image and re-enable dm-verity and verification with the included avbctl binary or through adb/fastboot. Those are the only changes performed by the script. If you have any more questions just ask in this thread. Good luck!
About:
Spoiler: About
I did not come up with all this by myself. After searching for a solution for countless days without success, going even as far as learning hex editing - I accidentally came across a couple of very interesting threads burried deep inside the new forum interface where this method has been described by various rw enthousiasts (links can be found in the credits section below). Therefore most credit goes to these rw enthousiasts. I'm only the amateur who put it all together into a compact script so that everybody can enjoy an Android system that's read/write-able again. Just like it used to be in Android 9 or earlier. Before these annoying 'shared_blocks' and 'EROFS' read-only features were implemented.
Credits:
Huge thanks to @Brepro1 for allowing me to use his awesome tutorial and make it into a script. Without your tutorial guiding me I couldn't have created this script.Huge thanks to @Kolibass for allowing me to use his partition tools for Android. Without your tools this script would not work on the Android platform!Big thanks @munjeni for allowing me to use his amazing superunpack V1 tool in the initial version. It helped me to understand how these super images work.Thanks @AndyYan your great tutorial also helped me a lot for automating the script especially the lpdump part.Thanks @bynarie for making available his otatools package! A part of it was bundled with the initial version which helped me to create this universal version. It's still part of the troubleshooting repair script to fix error 73.Thanks @HemanthJabalpuri for assisting me in optimizing the underlying algorithm!
Disclaimer:
Spoiler: Disclaimer
#Disclaimer v3.0This open source software is provided as is without any kind of warranty or support whatsoever.By using and viewing this software you agree to the following terms:
Under no circumstances shall the author be held responsible for any damages that may occur from the (inappropriate) use of this software (or parts thereof).
All responsibility, liability and risk lies with the end-user. You hereby agree not to abuse this software for illegal purposes.
Please don't steal, hack, crack, mod, hex-edit, decompile, rebrand and / or abuse this software or parts thereof. Thank you!
This software can be re-uploaded to 3rd party websites indefinitely as long as the software itself (or any parts thereof) were not modified by unauthorized 3rd parties without the original author's prior knowledge and explicit written consent
This software (or parts thereof) were provided for free only for non-commercial, educational, personal, legal purposes
To use this software (or parts thereof) for commercial purposes, please rent a commercial usage license
Thank you very much for your support! Thanks to your amazing support I can continue working on this project and other interesting projects like this.
Enjoy debloating and customizing your fully read/write-able next-gen Android device!
Please post your feedback, suggestions and your Olympic Android System Mods (OASMG) @ the official SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac links below. Thanks
https://forum.xda-developers.com/t/...tition-converter-resizer-by-lebigmac.4247311/
https://forum.xda-developers.com/t/...n-converter-erofs-rw-ext4-rw-f2fs-rw.4536821/
{
"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"
}
Confirmed working on these devices:
Spoiler: Device list
Xiaomi Poco X3 NFC
Xiaomi Poco X3 Pro
Xiaomi Poco X2 - Android 10/11
Xiaomi Poco X2 - Android 11
Xiaomi Poco F2 Pro - Android 11
Xiaomi Mi 10 T Lite - Android 11
Xiaomi Mi 10 T lite - Android 11
Xiaomi Mi 10 - Android 11
Xiaomi Mi 10 Ultra - Android 11
Xiaomi Mi 10i 5G (gauguin) - Android 11
Xiaomi Mi Note 10 Lite - Android 11 - OrangeFox
Xiaomi Redmi Note 12 5G - Android 12 - latest MIUI 13.0.3
Xiaomi Redmi 9 - Android 10
Xiaomi Redmi 9 - Android 10
Xiaomi Redmi Note 9 Pro joyeuse - Android 10
Xiaomi Redmi Note 9 Pro gauguin (China) - Android 10
Xiaomi Redmi Note 9S - Android 11 - MIUI Global 12.5.3 Stable (RJWEUXM)
Xiaomi Redmi 9T - Android 11
Xiaomi Redmi K30 - Android 10
Xiaomi Redmi K30S Ultra(China), Android 11
Asus ROG Phone 3 - Android 10
Asus ROG Phone 5 - Android 11
OnePlus Nord - Android 11
OnePlus 8T - Android 11
Doogee S96Pro - Android 10
F150 model B2021 - Android 10
Realme C12 - Android 11
Realme GT 5G - Android 12
Pixel 4a (sunfish) - Android 11
Google Pixel 4 XL (coral) - Android 10
and many more!
NOTE: Please post your feedback in this thread (with screenshot as proof that you are RW) if you want your device to be included in this list
Download
current status: experimental
If you like this project and want to support further development of it & the creation of more amazing projects like this then please feel free to donate to the original developer lebigmac by clicking the button below. Thanks! Your support is very much appreciated!
Donate
If the script works on your device please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/
And please write your phone model - Android version - firmware version
Then I can add you to the list of successful devices and it will be helpful for further development. Thank you!
doesn't work for me!
You're supposed to run this on the phone
This universal version is different from the previous Linux only version!
Please follow the instructions in the first post or in the comment section of the script itself!
It looks like I'll have to make a flashable zip out of this. Please give me a day or two to learn more about flashable zip's!
I just wanted to release it as soon as possible because I know many people were waiting for the new universal version
lebigmac said:
you're supposed to run this on the phone
Please follow the instructions in the first post or in the comment section of the script itself!
Click to expand...
Click to collapse
you mean terminal of twrp?
Thanks for your hard work. So I just need to copy the file to my storage and run it with TWRP ( I use orangefox) and nothing more?
Manual installation:
Extract BUNDLE.zip
Extract flashable.zip
Copy systemrw_1.32 folder into /data/local/tmp/
It should look like this:
/data/local/tmp/systemrw_1.32
Please keep in mind I have not tested this in orangefox but only in twrp so you will be the first person to do so!
Is orangefox an engineer build like twrp? You can check this by doing
Code:
getprop ro.build.type
when I run " getprop ro.build.type" the answer is "eng"
lebigmac said:
yes but the makesysrw_1.15 folder containing the script should go into /data/local/tmp/
so it should look like this:
/data/local/tmp/makesysrw_1.15
Also if you have orangefox you can simply replace the TWRP check at line #303 with this:
Code:
if ( whoami>/dev/null ); then
Please keep in mind I have not tested this in orangefox but only in twrp so you will be the first person to do so!
If orangefox is anything like twrp it should work! Is orangefox an engineer build like twrp?
you can check this by doing
Code:
getprop ro.build.type
Click to expand...
Click to collapse
If I try to access the link it says "
403 Forbidden"
Download link updated
It works. Device: Xiaomi Redmi Note 9 Pro joyeuse
uvzen said:
IT WORKS! Device: Xiaomi Redmi Note 9 Pro joyeuse
Click to expand...
Click to collapse
You've got to be kidding me!
Thanks for your feedback uvzen. I think you were the first one to try it. Congratulations
Can you please tell me do you have a super partition on your device? What Android version?
And how did you like the flashing process? Was it smooth and fast?
Thanks to a suggestion by user @Kolibass the flashing is now super fast in this new version!
lebigmac said:
You've got to be kidding me!
Thanks for your feedback uvzen. I think you were the first one to try it. Congratulations
Can you please tell me do you have a super partition on your device? What Android version?
And how did you like the flashing process? Was it smooth and fast?
Thanks to a suggestion by user @Kolibass the flashing is super fast in this new version!
Click to expand...
Click to collapse
Device: Xiaomi Redmi Note 9 Pro joyeuse Android 10 MIUI 12.0.1
I have a super partition and the process took about 5 minutes
So is your system read-write now? Did you use any special arguments when calling the script such as size=100 to give extra free space to your partitions? That's useful so you can copy stuff to system. Otherwise you can only delete stuff...
lebigmac said:
So are you read-write now? Did you use any special arguments when calling the script such as size=100 to give extra free space to your partitions? That's useful so you can copy stuff to system. Otherwise you can only delete stuff xD
Click to expand...
Click to collapse
I used ./makesysrw.sh size=300 but that's not enough and now I will try with size=1000
1 GB (1024 MB) is probably too much
Did you try copy stuff into /system yet to see if it's read write?
In your favorite root file manager you can click the remount as R/W button on top.
You can also try mounting your partition(s) as read/write manually like this:
I mean 300MB is not enough for me xD
Please post an instructional video
can't access to tmp because it is encripted in twrp, any help please
@walid77dz did you try to boot into android, set a PIN code and then reboot to TWRP and decrypt everything by entering your PIN code?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 7a devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
New Release:
May 19, 2023 v5.0.0.1 release
#75 Bug fix, when device is in bootloader, type error.
#74 Added Support for Pixel 7a (lynx)
Configuration option to define the file manager to use on Linux (default: Nautilus)
Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
Support for additional types of Factory / ROM files.
Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
New advanced option, ability to choose the patching method (with recommendations).
Added Recovery Image patching option.
Advanced option to enable the use of busybox shell (default off).
Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
#66, when checking the patched files internal SHA1, provide a confidence rating.
Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
Added fastbootd testing to Dry Run.
Added Github actions to build all the targets on Github.
Code refactoring, bug fixes and improvements
New Release:
May 25, 2023 v5.1.0.0 release
Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3
Temp workaround to avoid selecting root method patching when Magisk Delta is detected.
Nicer looking / clearer manual patching dialog.
When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.
Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.
Boot image list box now displays the applied PixelFlasher patch method.
Auto-resize boot image list box columns for better readability.
Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.
#77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).
Bug fixes and improvements.
Update:
Patch Release:
v5.1.0.1 release
Exception handling when device is not in the listed Pixel devices.
v5.1.0.2 release
Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
Thank you so much for this awesome software! When trying to trying to patch the int.boot from the factory image I run into the following error "Detected Unsupported firmware, with payload.bin". Is this truly unsupported or am I doing something wrong?
I also tried extracting the payload.bin to manually pull out int.boot and patch it, which I think worked, but in the console field said something about a low confidence match and aborted the flash.
Any help would be greatly appreciated.
I downloaded the following build from google: lynx-ota-tq2b.230505.005.a1-766dbd16
Using: platform-tools_r34.0.3-windows
Pixel Flasher: v5.1.0.2 release
Gp3322 said:
Thank you so much for this awesome software! When trying to trying to patch the int.boot from the factory image I run into the following error "Detected Unsupported firmware, with payload.bin". Is this truly unsupported or am I doing something wrong?
I also tried extracting the payload.bin to manually pull out int.boot and patch it, which I think worked, but in the console field said something about a low confidence match and aborted the flash.
Any help would be greatly appreciated.
I downloaded the following build from google: lynx-ota-tq2b.230505.005.a1-766dbd16
Using: platform-tools_r34.0.3-windows
Pixel Flasher: v5.1.0.2 release
Click to expand...
Click to collapse
You are selecting an OTA image instead of firmware image.
If you click on that green button on the left of firmware selection, it should open a download link for your device, download that and process that.
Manually extracting init_boot from payload.bin is ok for patching, which you did the first time around, and it create a proper patch.
But then you proceeded to trying to patch the patched file, why would you do that?
That's when PF aborted with low confidence level.
You are 100% correct! I was using the OTA instead of the full image. Once I found the correct file, everything fell into place.
New Release:
June 01, 2023 v5.2.0.0 release
Update build workflows
Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
Added rules engine code to better / easier management of the UI widgets enabling / disabling.
Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
Bug Fix Release:
June 01, 2023 v5.2.0.1 release
Bug fix #78 Error when opening a shell console on Linux / Mac
Update:
June 03, 2003 v5.2.0.2 release
#76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
New Release:
June 06, 2003 v5.3.0.0 release
Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.
PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's ), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.
When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.
If there was a way to pre-load odin with the extracted files, flashing could also be automated.
I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
New Release:
June 16, 2003 v5.3.1.2 release
Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.
Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.
Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.
Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.
Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
Thank you. Work like a champ.
tim1aust said:
2 questions in re. PixelFlasher and P7a.. a) is P7a supported yet? (seems like yes) b) is PixelFlasher from AUR for Manjaro *at the same build level* (it has 5.3.1.2 in lower left)as the one from Github, et.al?
I figured it would be easier to just have a supported AUR package, so I installed that. But when I tried to use it for P7a with latest Full image, it couldn't patch the file (said it couldn't find boot.img). Of course, for P7 & P7a, it should firstly be looking for init_boot.img. Could it be due to the fact that this was a new phone which didn't yet have Magisk installed? (I guess that's 3 questions Anyway, I wound up gettng Magisk installed from scratch, so my P7a now has it installed. I'm hoping to use PixelFlasher from AUR next time.
TIA,
Tim
Click to expand...
Click to collapse
Original Post:
@tim1aust
I'm answering you in here to keep the Magisk thread clean of PF specific discussions.
Yes, PF supports Pixel 7a (lynx)
If you provide a support file, I could check what might have happened.
Thanks for answering, and pointing me to correct thread.
Unfortunately, I don't have a support file, unless the tool automatically saved one and I wasn't paying attention.
tim1aust said:
Thanks for answering, and pointing me to correct thread.
Unfortunately, I don't have a support file, unless the tool automatically saved one and I wasn't paying attention.
Click to expand...
Click to collapse
Yes, the tool creates logs, and when you click on the support button, it processes them and redacts sensitive information and creates a zip file for upload.
All you have to do is launch PF, and hit the button and share the file.
Great, attaching it here. Thanks for your help!
tim1aust said:
Great, attaching it here. Thanks for your help!
Click to expand...
Click to collapse
Thanks
Sorry I'm confused, you reported an issue with Pixel 7a (Lynx), but all I see is logs regarding Pixel 7 (Panther).
You mentioned about failed patching.
But I see nothing wrong with patching.
Code:
Creating a patch ...
Cleaning up...
- Unpacking boot image
Parsing boot image: [/sdcard/Download/init_boot_bea42eca.img]
HEADER_VER [4]
KERNEL_SZ [0]
RAMDISK_SZ [2068178]
PAGESIZE [4096]
CMDLINE []
RAMDISK_FMT [lz4_legacy]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Patching ramdisk
- Pre-init storage partition device ID: REDACTED
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Add entry [overlay.d/sbin/stub.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/stub.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/sdcard/Download/init_boot_bea42eca.img]
HEADER_VER [4]
KERNEL_SZ [0]
RAMDISK_SZ [2068178]
PAGESIZE [4096]
CMDLINE []
RAMDISK_FMT [lz4_legacy]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER [4]
KERNEL_SZ [0]
RAMDISK_SZ [2528130]
PAGESIZE [4096]
CMDLINE []
PATCH_SHA1: 081f1391
PATCH_FILENAME: magisk_patched_26100_bea42eca_081f1391.img
Cleaning up ...
Checking patch log: /data/local/tmp/pf_patch.log ...
Getting file content of /data/local/tmp/pf_patch.log on the device ...
Return Code: 0
Deleting /data/local/tmp/pf_patch.log from the device ...
Return Code: 0
Looking for magisk_patched_26100_bea42eca_081f1391.img in /storage/emulated/0/Download ...
Checking for /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img on the device ...
File: /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img is found on the device.
Pulling /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img from the phone to: magisk_patched_26100_bea42eca_081f1391.img ...
Pulling remote file: /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img from the device to: "/home/REDACTED/.local/share/PixelFlasher/tmp/magisk_patched_26100_bea42eca_081f1391.img" ...
Return Code: 0
Getting SHA1 of /home/REDACTED/.local/share/PixelFlasher/tmp/magisk_patched_26100_bea42eca_081f1391.img ...
SHA1 of magisk_patched_26100_bea42eca_081f1391.img file: 081f1391b700afb8ef5b28b4dce6db0bdb6d5d38
Getting SHA1 of source init_boot.img ...
Source init_boot.img's SHA1 is: bea42eca0a4e06eac0e876c2e7b9f518ade87874
Extracting SHA1 from magisk_patched_26100_bea42eca_081f1391.img ...
SHA1 embedded in /home/REDACTED/.local/share/PixelFlasher/tmp/magisk_patched_26100_bea42eca_081f1391.img is: bea42eca0a4e06eac0e876c2e7b9f518ade87874
Comparing source init_boot.img SHA1 with SHA1 embedded in bea42eca0a4e06eac0e876c2e7b9f518ade87874 (they should match) ...
Good: Both SHA1s: bea42eca0a4e06eac0e876c2e7b9f518ade87874 match.
Magisk Version: 26.1:26100
Patch time: 5 seconds
The attempt was made yesterday.. 6-20. Is there a log from that date? The ones for panther were when I was using PF for my P7.
--tim
tim1aust said:
The attempt was made yesterday.. 6-20. Is there a log from that date? The ones for panther were when I was using PF for my P7.
--tim
Click to expand...
Click to collapse
OK I see it now.
What is this file? where did it come from?
lynx-factory-23410002.zip
Code:
Selected Firmware lynx-factory-23410002.zip SHA-256: 033c2d0381aec8e4538a393baa9fdd86bfc7f24578fa8e4db9f7d9ea49756948
I have a bookmark in my browser for getting OTA updates ( which I've been doing forever, before PF).. Anyway, there is a link at the top left of the page for Factory images, that's what I downloaded. URL is https://developers.google.com/android/images