ROOT(Magisk) + OEM Fix + Busybox + EFS Backup
Pie
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option
3.Download and copy Pie_G955F_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP for S8 from official page https://twrp.me
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card - Pie_G955F_Root_for_OEM_issue_devices_V*.zip, you have copied earlier
15.Once Magisk flash successfully, Reboot to System
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
Oreo
PS : This guide is for Oreo and will be updated for Pie, when Pie will be out officially.
This is for Stock ROM/Kernel only If you have custom kernel, read below.
Here is guide and tool to Root S8/S8+ + Busybox + OEM Fix + Data mount fix
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy G955FD_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP latest TWRP (Edit : Latest TWRP is already fixed for data mount error, so you won't require to select data mount fix in aroma)
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card - G955FD_Root_for_OEM_issue_devices_V*.zip, you have copied earlier, select desired option (You must select Root option if you are on stock kernel/ROM else device won't boot) and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
15.Once flash successfully finish, Reboot to System
Magisk app may appear in drawer after one reboot.
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
For custom Kernel, you need to flash modified recovery that doesn't require data mount fix
YOU MUST BACKUP EFS AS SOON AS ROOT DEVICE, and copy it to safer place,
EFS Backup Tool
As soon as you root device, you must make backup of EFS and must store a copy of backup to safer place like on cloud and on a PC
XDA version - Free version, complimentary tools for XDA users.
Play Store version - You can buy from Play store to support us.
Both version make same form of backup and have no difference, Paid version have additional function to make Auto Backup when you change the ROM
Credits : @Chainfire @topjohnwu @jesec @BlackMesa123 for OEM fix@osm0sis and some International forum discussion for original idea
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download
Click to expand...
Click to collapse
It will be that this file, may help in the situation below:
https://forum.xda-developers.com/galaxy-s8/development/twrp-internal-storage-0mb-s8-t3769199
costafabiof said:
It will be that this file, may help in the situation below:
https://forum.xda-developers.com/galaxy-s8/development/twrp-internal-storage-0mb-s8-t3769199
Click to expand...
Click to collapse
Yes that will help in situation you have mentioned.
dr.ketan said:
Yes that will help in situation you have mentioned.
Click to expand...
Click to collapse
For the above procedure would I function before FORMAT DATE? Right?
Well just by trying to install the bug!
costafabiof said:
For the above procedure would I function before FORMAT DATE? Right?
Well just by trying to install the bug!
Click to expand...
Click to collapse
No need to format data, just flash from ext SD
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download
Click to expand...
Click to collapse
very very much very very much very much very much very very much very very much THANK YOU.
It worked. I just had to learn to read
"- Reboot to system (Must)"
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download[/URL]
Click to expand...
Click to collapse
Wow! That really solved the issue, Thank you!!
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download
Click to expand...
Click to collapse
Thank you so much
I tried it on s8 plus & when system start after formatting Stuck on language choose !! Then i flashed nougat again!
Also tried it on S8+ but without formatting, i'm stuck on the lockscreen it seems like the touch screen isn't responding anymore after i flashed it. I restored from a back up to make my phone work again. Any news about this issue with S8+?
Bofahad said:
I tried it on s8 plus & when system start after formatting Stuck on language choose !! Then i flashed nougat again!
Click to expand...
Click to collapse
Marioabirached said:
Also tried it on S8+ but without formatting, i'm stuck on the lockscreen it seems like the touch screen isn't responding anymore after i flashed it. I restored from a back up to make my phone work again. Any news about this issue with S8+?
Click to expand...
Click to collapse
This if for S8 only
You can try my latest fix for N8, that may work cross device too. if that doesn't work then I will make for s8+
https://forum.xda-developers.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928
dr.ketan said:
This if for S8 only
You can try my latest fix for N8, that may work cross device too. if that doesn't work then I will make for s8+
https://forum.xda-developers.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928
Click to expand...
Click to collapse
I just tried it but the N8 zip failed, the S8 one worked better it showed internal storage size in TWRP but i couldn't use my touchscreen. I think we need one just for S8+.
dr.ketan said:
This if for S8 only
You can try my latest fix for N8, that may work cross device too. if that doesn't work then I will make for s8+
https://forum.xda-developers.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928
Click to expand...
Click to collapse
Thank you waiting S8+ one
Marioabirached said:
I just tried it but the N8 zip failed, the S8 one worked better it showed internal storage size in TWRP but i couldn't use my touchscreen. I think we need one just for S8+.
Click to expand...
Click to collapse
Oh ok got it
I will fix now and posting here in op, check first post after half an hr
You might got msg, device not supported right?
dr.ketan said:
Oh ok got it
I will fix now and posting here in op, check first post after half an hr
You might got msg, device not supported right?
Click to expand...
Click to collapse
Yes I did on the N8 zip
I have updated first post of this thread, it should work on both S8 and S8 + also added support for SuperSU
Test on S8+ and report back so this thread can move to crisscross development
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
As many users are facing issue because of data mount issue with TWRP on oreo, till it get fixed here is temporary solution.
Download file according root method you are using
1. For Magisk
2. For SuperSU
Installation :
- Flash downloaded file from recovery - Ignore if any message with red color regarding data mount while flashing
- Reboot to system (This step is Must)
- Done !
Now again you can reboot to recovery to check for data mount fix.
This can be use with any working TWRP/Kernel for S8/S8+
Credits : Credits : @[email protected]@osm0sis and some International forum discussion for original idea
Click to expand...
Click to collapse
Unfortunately it also said device not supported
Marioabirached said:
Unfortunately it also said device not supported
Click to expand...
Click to collapse
Open build prop and check what is device name
Or send me build.prop
dr.ketan said:
Open build prop and check what is device name
Or send me build.prop
Click to expand...
Click to collapse
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=R16NW
ro.build.display.id=R16NW.G955FXXU1CRB7
ro.build.version.incremental=G955FXXU1CRB7
ro.build.version.sdk=26
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.0.0
ro.build.version.security_patch=2018-02-01
ro.build.version.base_os=
ro.build.version.security_index=1
ro.build.date=Mon Feb 19 23:23:54 KST 2018
ro.build.date.utc=1519050234
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD6016
ro.build.tags=release-keys
ro.build.flavor=dream2ltexx-user
ro.product.model=SM-G955F
ro.product.brand=samsung
# ro.build.product is obsolete; use ro.product.device
ro.build.product=dream2lte
ro.product.name=dream2ltexx
ro.product.device=dream2lte
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-GB
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=dream2ltexx-user 8.0.0 R16NW G955FXXU1CRB7 release-keys
ro.build.fingerprint=samsung/dream2ltexx/dream2lte:8.0.0/R16NW/G955FXXU1CRB7:user/release-keys
ro.build.characteristics=phone,emulator
# Samsung Specific Properties
ro.build.PDA=G955FXXU1CRB7
ro.build.official.release=true
ro.config.rm_preload_enabled=1
ro.build.changelist=12993656
ro.product_ship=true
ro.chipname=exynos8895
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=universal8895
ro.board.platform=exynos5
# end build properties
#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=88
ro.hwui.layer_cache_size=58
ro.hwui.path_cache_size=16
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.shape_cache_size=4
ro.hwui.gradient_cache_size=2
ro.hwui.drop_shadow_cache_size=6
ro.hwui.r_buffer_cache_size=8
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=4096
ro.hwui.text_large_cache_height=2048
#
# from device/samsung/dream2lte/system.prop
#
#
# system.prop for universal8895
#
ro.arch=exynos8895
ro.kernel.qemu=0
ro.kernel.qemu.gles=0
persist.demo.hdmirotationlock=false
# read DS/SS property
import /efs/factory.prop
#Enable S.LSI USB settings
dev.usbsetting.embedded=on
#RILD debug level setting
ro.debug_level=0x494d
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product.first_api_level=24
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.opengles.version=196610
debug.slsi_platform=1
debug.hwc.winupdate=1
af.fast_period_size=192
af.fast_track_multiplier=1
ro.hdcp2.rx=tz
keyguard.no_require_sim=true
ro.carrier=unknown
vendor.sec.rild.libpath=/vendor/lib64/libsec-ril.so
vendor.sec.rild.libpath2=/vendor/lib64/libsec-ril-dsds.so
persist.radio.sib16_support=1
ro.security.icd.flagmode=multi
security.mdf.result=None
security.mdf=None
ro.security.mdf.ux=Enabled
ro.security.mdf.ver=3.1
ro.security.wlan.ver=1.0
ro.security.wlan.release=1
ro.security.mdf.release=1
ro.security.fips.ux=Enabled
ro.security.fips_bssl.ver=1.2
ro.security.fips_skc.ver=1.8
ro.security.fips_scrypto.ver=2.0
ro.security.fips_fmp.ver=1.2
security.ASKS.policy_version=000000
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
camera.disable_treble=1
ro.config.ringtone=Over_the_Horizon.ogg
ro.config.notification_sound=Skyline.ogg
ro.config.alarm_alert=Morning_Glory.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.ringtone_2=Basic_Bell.ogg
ro.config.notification_sound_2=S_Charming_Bell.ogg
ro.build.scafe.version=2018A
ro.sf.lcd_density=420
ro.sf.init.lcd_density=560
ro.error.receiver.default=com.samsung.receiver.error
sys.config.activelaunch_enable=true
ro.wsmd.enable=true
ro.frp.pst=/dev/block/persistent
ro.multisim.simslotcount=2
ro.config.dha_cached_min=6
ro.config.dha_cached_max=19
ro.cfg.dha_cached_max=24
ro.config.dha_empty_min=8
ro.config.dha_empty_init=24
ro.config.dha_empty_max=24
ro.cfg.dha_empty_init=32
ro.cfg.dha_empty_max=32
ro.config.dha_th_rate=2.0
ro.config.dha_lmk_scale=1.0
ro.config.dha_pwhitelist_enable=1
ro.config.dha_pwhl_key=7938
ro.config.fall_prevent_enable=true
security.mdpp.mass=skmm
ro.hardware.keystore=mdfpp
ro.security.vpnpp.ver=2.1
ro.security.vpnpp.release=1.0
sys.use_fifo_ui=0
persist.sys.tcpOptimizer.on=1
sys.config.amp_perf_enable=true
ro.config.systemaudiodebug=abox&codecdsp
ro.security.vaultkeeper.feature=1
ro.gfx.driver.0=com.samsung.gpudriver.S8MaliG71_80
ro.hardware.egl=mali
ro.zygote.disable_gl_preload=true
ro.com.google.clientidbase=android-samsung
ro.opa.eligible_device=true
ro.control_privapp_permissions=log
ro.setupwizard.wifi_on_exit=false
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=8.0_r5
ro.build.version.sem=2601
ro.build.version.sep=90000
ro.treble.enabled=false
ro.build.selinux=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=exynos-m2
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
dalvik.vm.isa.arm.features=default
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=3.0
ro.config.iccc_version=3.0
ro.config.dmverity=true
ro.config.rkp=true
ro.config.kap_default_on=true
ro.config.kap=true
ro.kernel.qemu=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0xeaeafdd6573569bb96963e3e34597057321ea845000000000000000000000000
Marioabirached said:
# begin build properties
Click to expand...
Click to collapse
Test V2 and report
Related
here is a mini guide:
what`s you need:
1. a root phone
2. root explorer installed
3. go to system/build.prop
START ROOT EXPLORER
go to system
press r/o button you must see r/w
open the file build.prop with a text editor (long pressover the file)
replace your buil.prop number with 1238-8536 what`s a german number (i think is in tree places)
shutdown and start you phone.. 2 times...
conect to pc companion
to obtain root access
go to: http://forum.xda-developers.com/showthread.php?t=824788
download adb and superoneclickv1.apk
replace the content of superoneclick folder with adb
in your phone go to config, aplications, development and select usb depuration mode
conect your phone with the pc and start superoneclick then see how its work, if stuck or the software dont work in one step select and deselect USB depuration mode repeteadly 2 times.
maybe you need to try many times
sudenly it will work, then go to:
http://forum.xda-developers.com/showpost.php?p=7827223&postcount=88
and folow steps to correct your keyboard
you can see what layout works for you
Check the folder Layouts inside the keyboard-config folder open each file and see how was the layout then replace like the example in the post
boilaa
work flawless, i can play angry birds, the icons see like compressed but the game works very good,
some minor changes like more colors and darker interfase, i see the photos a little better and the video has autofocus..
my android market dont want to work but after few configurations like enable non secure apk i can instal all good
few more widgets: market, on off conections and things, small views for webs, data traffic and youtube
and facebook update photos with contacts
when you select an user you can send email and do other things
pablo lara melcher said:
work flawless, i can play angry birds, the icons see like compressed but the game works very good,
some minor changes like more colors and darker interfase, i see the photos a little better and the video has autofocus..
my android market dont want to work but after few configurations like enable non secure apk i can instal all good
few more widgets: market, on off conections and things, small views for webs, data traffic and youtube
and facebook update photos with contacts
when you select an user you can send email and do other things
Click to expand...
Click to collapse
Really the video has autofocus ??? Fantastic ! And what about the menu of the camera options ? it's the same? Other improvements?
Thank you very much, it's really work!
Now we need to find out how to fix they keyboard ... as I ended up with scandinavian layout.
I have same problem .. well, not scadinavian, but german .. obviously. Everything else is working just perfect. Even localisation is fine.
Lweek said:
I have same problem .. well, not scadinavian, but german .. obviously. Everything else is working just perfect. Even localisation is fine.
Click to expand...
Click to collapse
Scandinavian for sure not german. My phone has German physical layout, I would have loved to have a german layout. But this update has letters as "a med ring" and is definitely a QWERTY and not german QWERTZ.
I have a problem with the keyboard too. I notice some changes in the keyboard. I hope this might help you.
1. Full stop ( . ) moves to the "?" key
2. Question mark ( ? ) moves to the full stop key ( . )
3. ' mark (Sorry I don't know what-its-called) move to the letter "e" (To type ', you need to activate the blue key first)
4. Semicolon ( ; ) moves to the letter "d" (To type ; , you need to activate the blue key first)
5. Comma ( , ) moves to the letter "c" (To type comma, you need to activate the blue key first)
6. Colon ( : ) moves to the "?" key (To type : , you need to activate the blue key first)
Here is how to fix they keyboard :
http://forum.xda-developers.com/showthread.php?t=824941
pablo lara melcher said:
here is a mini guide:
what`s you need:
1. a root phone
2. root explorer installed
3. go to system/build.prop
open the file with a text editor (long pressover the file)
replace your buil.prop number with 1238-8536 what`s a german number (i think is in tree places)
shutdown and start you phone..
conect to pc companion
boilaa
Click to expand...
Click to collapse
hi I live in uk .if I change the build prop would it effect any of my phone features example 3g connection, keyboard layout, I'm happy with the english layout.will I have english. also I use arabic language for txting does 2.1 have arabic language support.
Thanks.
i got error when rooting
Device Was Not Rooted
FAILED
hi there, i change the numbers and save the file but PC Comapanion and SEUS say "your phone is up to date", i am still with 1.6, my MINI PRO is from Claro Chile (Chilian build file)
heres is my original build.prop (for future use if anyone need the build number from Chile)
Code:
##### Final patch of properties #####
ro.build.product=SonyEricssonU20a
ro.build.description=U20a-user 1.6 1.2.A.1.181 413 test-keys
ro.build.display.id=1.2.A.1.181
ro.product.brand=SEMC
ro.product.name=U20a_1239-0006
ro.product.device=SonyEricssonU20a
ro.product.board=delta
ro.build.version.incremental=9
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/U20a_1239-0006/SonyEricssonU20a/delta:1.6/1.2.A.1.181/9:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1239-0006
ro.semc.version.cust_revision=R12A
ro.semc.ecclist.num=1
ro.semc.ecclist.type.0=Police
ro.semc.ecclist.number.0=133
ro.semc.ecclist.plmn.0=730 03F
ro.semc.max_digits_match=8
ro.voicemail.dialing-number=*20
ro.semc.disableSPN=false
ro.semc.enable.fast_dormancy=true
#########################################################################
ro.config.ringtone=sony_ericsson.ogg
ro.config.notification_sound=notification.ogg
ro.semc.content.number=PA8
################# Updating of the SW Version #################
ro.semc.version.fs_revision=1.2.A.1.181
ro.build.id=1.2.A.1.181
##### Values from product package metadata #####
ro.product.model=U20a
ro.semc.ms_type_id=AAD-3880071-BV
ro.semc.version.fs=WORLD-1-2-5
ro.semc.product.name=X10 mini pro
# begin build properties
# autogenerated by buildinfo.sh
#ro.build.id=1.2.A.1.181
#ro.build.display.id=1.2.A.1.181
#ro.build.version.incremental=413
ro.build.version.sdk=4
ro.build.version.codename=REL
ro.build.version.release=1.6
ro.build.date=Fri Jul 2 13:25:20 2010
ro.build.date.utc=1278069920
ro.build.type=user
ro.build.user=SEMCUser
ro.build.host=SEMCHost
#ro.build.tags=test-keys
#ro.product.model=mimmi
#ro.product.brand=generic
#ro.product.name=mimmi
#ro.product.device=mimmi
#ro.product.board=mimmi
ro.product.cpu.abi=armeabi
ro.product.manufacturer=Sony Ericsson
ro.product.locale.language=en
ro.product.locale.region=GB
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
#ro.build.product=mimmi
# Do not try to parse ro.build.description or .fingerprint
#ro.build.description=mimmi-user 1.6 1.2.A.1.181 413 test-keys
#ro.build.fingerprint=generic/mimmi/mimmi/mimmi:1.6/1.2.A.1.181/413:user/test-keys
# end build properties
#
# system.prop for mimmi
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
wifi.interface = tiwlan0
ro.semc.fm_service=1
ro.semc.def_screen_orientation=sensor
ro.semc.timescape_keys=X10_mini_pro_key
ro.sf.lcd_density=120
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.cust.tel.eons=1
persist.ro.ril.sms_sync_sending=1
DEVICE_PROVISIONED=1
# Constant values for Battery test in Service menu.
ro.semc.batt.capacity=950
ro.semc.batt.test.consumption=150
ro.semc.batt.test.z_threshold=50
ro.semc.batt.test.min_level=60
ro.qualcomm.proprietary_obex=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
#ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.clientidbase=android-sonyericsson
ro.com.google.clientidbase.yt=android-sonyericsson
ro.com.google.clientidbase.am=android-sonyericsson
ro.com.google.clientidbase.vs=android-sonyericsson
ro.com.google.clientidbase.gmm=android-sonyericsson
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gms_preload_version=1.6_r16
ro.drm.active.num=4
ro.drm.active.0=semc,1
ro.drm.active.1=cmla,0
ro.drm.active.2=viaccess,0
ro.drm.active.3=marlin,1
ro.drm.whitelist.num=4
ro.drm.whitelist.domain.0=roap.drm.coremedia.com
ro.drm.whitelist.domain.1=.teslan.com
ro.drm.whitelist.domain.2=selddrmt02.teslan.com
ro.drm.whitelist.domain.3=.inovatel.com
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#ro.semc.version.fs_revision=1.2.A.1.181
pablo lara melcher said:
here is a mini guide:
what`s you need:
1. a root phone
2. root explorer installed
3. go to system/build.prop
open the file with a text editor (long pressover the file)
replace your buil.prop number with 1238-8536 what`s a german number (i think is in tree places)
shutdown and start you phone..
conect to pc companion
NEW:
to obtain root access
go to: http://forum.xda-developers.com/showthread.php?t=824788
download adb and superoneclickv1.apk
replace the content of superoneclick folder with adb
in your phone go to config, aplications, development and select usb depuration mode
conect your phone with the pc and start superoneclick then see how its work, if stuck in one step select and deselect USB depuration mode repeteadly
sudenly it will work, then go to:
http://forum.xda-developers.com/showpost.php?p=7827223&postcount=88
and folow steps to correct your keyboard
you can see what layout works for you
Check the folder Layouts inside the keyboard-config folder open each file and see how was the layout then replace like the example in the post
boilaa
Click to expand...
Click to collapse
Hi
Thanks for the guide....
I have problem to save build.prop file. it says the file is read only. I have rooted my phone and have done exactly like you decription. what to do???
rehan_i said:
Hi
Thanks for the guide....
I have problem to save build.prop file. it says the file is read only. I have rooted my phone and have done exactly like you decription. what to do???
Click to expand...
Click to collapse
Mount your file system as read/write in Root explorer.
Does this only work with pro?
Hello
I have a x10 mini (NOT A MINI PRO!), would this guide / fw work?
I've heard that this only works with mini PRO, is that correct?
Thanks
Hi, mine says 'You already have the latest software' when i try and update with pc companion. I have a rooted phone, ive edited the build.prop, ive restarted the phone, ive connected it via usb and click on the 'support zone' and then on update. This is when it gives me the error.
As far as i know i have a UK phone.
Any help is appreciated, thanks.
Model No. U20i
Firmware Version: 1.6
Kernel version: 2.6.29
Build No. 1.1.A.0.8
EDIT: I have a mini pro if it wasn't clear.
Exactly same situation here....
I cant seem to find NORDIC firmware for x10mini (not pro)
Skeldave said:
Hi, mine says 'You already have the latest software' when i try and update with pc companion. I have a rooted phone, ive edited the build.prop, ive restarted the phone, ive connected it via usb and click on the 'support zone' and then on update. This is when it gives me the error.
As far as i know i have a UK phone.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
Skeldave said:
Hi, mine says 'You already have the latest software' when i try and update with pc companion. I have a rooted phone, ive edited the build.prop, ive restarted the phone, ive connected it via usb and click on the 'support zone' and then on update. This is when it gives me the error.
As far as i know i have a UK phone.
Any help is appreciated, thanks.
EDIT: I have a mini pro if it wasn't clear.
Click to expand...
Click to collapse
Mine is an x10 mini
Exact same here. My phone was bought in Ireland, but I assume it's a UK handset.
btw u should state many people dont know...
when u in root explorer go to system and click mounted r/w
ok, enough is enough.
i can't wait any longer and i'm going to try this. it's no german number for sure, 'cause i got german-unbranded mini pro and no update is available.
Because sometime, somehow, the offical german update is coming out, i have following question:
when i want to flash the "right" 2.1 to my phone, do i only need to root it again (as i read its possible with 2.1) and change the number back to my default one, start Companion/SEUS and do a reset/repair? is it then going to download the german update, that war originally thought to be on this phone?
edit: oh well, doesnt work for me at all with the changed number. so, nevermind my question - like you allready did
edit: was about to give up, then it worked. changed all the numbers, not just the first appearing
This is development thread for CM11 building on Samsung GalaxyTab3 10.1 devices, based on Intel Clover Trail platform. (x86)
Device tree: https://github.com/Angel666/android_device_samsung_santos103g
CM11 source repo:
Code:
[FONT=Arial]repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0[/FONT]
Patches for CM source needed to build rom. Made by HazouPH:
https://github.com/HazouPH/android_device_motorola_smi/tree/jellybean/patch
Working for now:
hardware accel (with some bugs)
storages and mtp mounting
Ril (partially)
Lights and buttons
Houdini service
anything else I can forgot..
Not working for now:
Wi-Fi (can not obtain mac)
BT (can not obtain mac)
Camera (service works, app can't connect)
SeLinux security (disabled)
Sound (Samsung lib won't work)
Basic CM Launcher3 is glitchy! I don't know why. Third-party launcers works well (testing by GOlauncher)
anything else I can forgot..
Images for testing: >DOWNLOAD< 3g version only for now!
WARNING! This images are for testing purposes only! Don't flash it if you don't know what you doing! Rom is almost UNUSABLE for enduser! Work in progress....
0.Unpack zip's.
1. Flash boot by Odin
2. Flash recovery by Odin
3. Enter to recovery and Wipe cache, dalvik, system and data.
4 Flash system by Odin
I appreciate any possible help (testing, donations, devs and experienced users advices). Let's speedup the process!
Impressive work done so far!
Thanks a lot Angel_666 ?
Sent from my HTC One
I'll be on for testing as soon as the images are uploaded!
Sent from my MB886 using xda app-developers app
Zachisimo said:
I'll be on for testing as soon as the images are uploaded!
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Good. But i must warning all who want to test image. After flash it erase all you data! It means, that only /data/media folder is staying alive.
@Angel_666 I donated you a little bit of money to congrat you for your work
Sent with PotatOS, the new experience of Potatoes
@Angel_666 are the test builds for the p5210 also?
Sent from my GT-P5210
Hey do you think there would be any chance of building this with the abyssplug governor? Or would the fact that hyperthreading is present screw things up? And is it possible to overclock? Thanks for all your work @Angel_666, been following the twrp and manifest threads for a while now, Great progress, just wanted to say thanks.
woopdedoda said:
Hey do you think there would be any chance of building this with the abyssplug governor? Or would the fact that hyperthreading is present screw things up? And is it possible to overclock? Thanks for all your work @Angel_666, been following the twrp and manifest threads for a while now, Great progress, just wanted to say thanks.
Click to expand...
Click to collapse
As about CPU - I don't find any information that it can work stable more than 1.6Ghz. But our GPU runs at 400Mhz and can be overclocked to 533 i think.
First post updated.
OK, didn't know that. That's the same chip that's in the i9500 right? Would comparing the gpu code for that help with hardware acceleration?
I'm now testing CM11
@Angel_666
I flashed the Images and I cant boot CM
I'm always stuck at "Samsung Galaxy Tab 3"
I can only boot to TWRP and Download
logcat doesn't work.
superboom said:
I'm now testing CM11
@Angel_666
I flashed the Images and I cant boot CM
I'm always stuck at "Samsung Galaxy Tab 3"
I can only boot to TWRP and Download
logcat doesn't work.
Click to expand...
Click to collapse
flash boot again, flash recovery, go to advanced wipe in recovery and check ALL options exept last (microSD). After process done, flash system img. Try and tell me.
P.S. "samsung logo" it not a bootloop. In your case system does not even run init process. (cm logo). Just checked all uploaded files on my tab p5200. All ok. CM logo, then system start. Before flashing i formatted my device and it was clean like a baby.
Formatting tried also, doesnt work in my p5210 @Angel_666
Sent with PotatOS, the new experience of Potatoes
For me it failed after wiping /system. I restored it from backup, wiped cache/data, flashed again, it worked.
With pimpdroid, not yet tested with cm11, but the issue is the same.
Gesendet von meinem GT-I9100G mit Tapatalk
Setialpha said:
For me it failed after wiping /system. I restored it from backup, wiped cache/data, flashed again, it worked.
With pimpdroid, not yet tested with cm11, but the issue is the same.
Gesendet von meinem GT-I9100G mit Tapatalk
Click to expand...
Click to collapse
Don't understood - CM works or not? Your device is p5210?
Ok now. I setup stock samsung firmware, and then repeat all process step by step. Will post results later.
Angel_666 said:
Don't understood - CM works or not? Your device is p5210?
Ok now. I setup stock samsung firmware, and then repeat all process step by step. Will post results later.
Click to expand...
Click to collapse
That should have been a reply to superboom.
Gesendet von meinem GT-I9100G mit Tapatalk
Setialpha said:
That should have been a reply to superboom.
Gesendet von meinem GT-I9100G mit Tapatalk
Click to expand...
Click to collapse
Ah. Sorry.
Ok. I flash my device by stock samsung firmware. Then, i flash CM11 as described at first post. CM boots OK and setup wizard turn on. My device is p5200 (3g).
Angel_666 said:
Ah. Sorry.
Ok. I flash my device by stock samsung firmware. Then, i flash CM11 as described at first post. CM boots OK and setup wizard turn on. My device is p5200 (3g).
Click to expand...
Click to collapse
What needs to be altered for it to boot on p5210.
I downloaded cm11 source last night and am gonna try put a build together.... Just need to figure out local manifests to sync your github :thumbup: thanks for that BTW.
Quick question.... How come you are having to flash via Odin? Thought that they could be flashed by recovery. Have you tried any gapps yet
Sent from my GT-I9300 using xda app-developers app
pug1 said:
What needs to be altered for it to boot on p5210.
I downloaded cm11 source last night and am gonna try put a build together.... Just need to figure out local manifests to sync your github :thumbup: thanks for that BTW.
Quick question.... How come you are having to flash via Odin? Thought that they could be flashed by recovery. Have you tried any gapps yet
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
As for img files via odin - "make otapackage" return some errors to me. That's why i use img. As for CM boot on p5210 - give me your build.prop from stock firmware - i'll tru to fix this.
Angel_666 said:
As for img files via odin - "make otapackage" return some errors to me. That's why i use img. As for CM boot on p5210 - give me your build.prop from stock firmware - i'll tru to fix this.
Click to expand...
Click to collapse
Here is the build.prop for the P5210
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.P5210UEUAMK1
ro.build.version.incremental=P5210UEUAMK1
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Tue Nov 26 14:28:02 KST 2013
ro.build.date.utc=1385443682
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0210-17
ro.build.tags=release-keys
ro.product.model=GT-P5210
ro.product.brand=samsung
ro.product.name=santos10wifiue
ro.product.device=santos10wifi
ro.product.board=clovertrail
ro.product.cpu.abi=x86
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=clovertrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=santos10wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=santos10wifiue-user 4.2.2 JDQ39 P5210UEUAMK1 release-keys
ro.build.fingerprint=samsung/santos10wifiue/santos10wifi:4.2.2/JDQ39/P5210UEUAMK1:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=P5210UEUAMK1
ro.build.hidden_ver=P5210UEUAMK1
ro.build.changelist=850131
ro.product_ship=true
ro.chipname=clovertrail
# end build properties
#
# system.prop for santos10 wifi
#
ro.carrier=wifi-only
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
# System property for Default Brightness
ro.lcd_brightness=118
# System property for Min Brightness
ro.lcd_min_brightness=10
# System Property for Intel MDS
ro.mds.enable=true
ro.kernel.qemu=0
persist.sys.storage_preload=1
# System property for Font Clarity
persist.sys.font_clarity=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.sf.lcd_density=160
ro.hdcp2.rx=tz
ro.secwvk=144
ro.sec.fle.encryption=true
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
persist.tel.hot_swap.support=true
drm.service.enabled=true
ro.com.google.apphider=off
ro.com.google.gmsversion=4.2_r3
ro.ril.status.polling.enable=0
ro.product.cpu.abi2=armeabi-v7a
ro.config.personality=compat_layout
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
hfase said:
Here is the build.prop for the P5210
Code:
ro.product.model=GT-P5210
ro.product.name=santos10wifiue
ro.product.device=santos10wifi
ro.build.product=santos10wifi
Click to expand...
Click to collapse
I think i need to change boardconfig.mk for wi-fi version
[Q] [Help] "Mann Zug A18" android version 4.3 boot welcome and black screen
I'm newbie and sorry for my English Language
Spec Model Mann zug3 android 4.3 quard core ram 1 gb screen 480x800
My model don't root
1.I try to change bootanimation.zip on my device by adb command , It all OK , when boot then welcome screen and then animation screen that I create and go to main display
2.I try to change Product Name by pull build.prop then edit and push to system and reboot , Problem! my device boot Welcome then go to black screen cannot touch active, so I go to recovery mode and wipe data and patition by hole power + volume down and reboot again , but still the same problem
I don't know how to do next step, please help me or suggest me please :crying:
this is file build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JLS36C
ro.build.display.id=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.version.incremental=W992.6.01.01
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Tue Jul 22 12:28:06 CST 2014
ro.build.date.utc=1406003286
ro.build.type=userdebug
ro.build.user=root
ro.build.host=redhat6.2
ro.build.tags=release-keys
ro.product.model=A18
ro.product.brand=A18
ro.product.name=A18
ro.product.device=A18
ro.product.board=MSM8610
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=A18
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8610
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A18PLUS_CR
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.fingerprint=MANN/A18PLUS_CR/A18PLUS_CR:4.3/JLS36C/W992.6.01.01:userdebug/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for msm8610
#
# Use reference RIL for initial bringup
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
persist.radio.msgtunnel.start=false
persist.radio.atfwd.start=false
# Start in wcdma+gsm mode
ro.telephony.default_network=0,1
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
persist.dsds.enabled=true
ro.multi.rild=true
#persist.env.spec=ChinaUnicom
#
# system props for the cne module
#
persist.cne.feature=0
# system prop for override memlimit to enable cne
persist.cne.override.memlimit=1
# Skip /sys/power/wait_for_fb_* nodes and
# force FB to be always on
debug.sf.fb_always_on=1
debug.composition.type=dyn
debug.gralloc.map_fb_memory=0
debug.hwc.dynThreshold=1.5
dev.pm.dyn_samplingrate=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=96m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=5m
ro.hdmi.enable=true
tunnel.decode=false
#8x10 does not support tunnel av playback
#this prop should be set to false all the time
tunnel.audiovideo.decode=false
lpa.decode=false
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
mm.enable.qcom_parser=130815
# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOlogs 7:AllLogs
vidc.debug.level=1
#
# system props for widevine
#
persist.gralloc.cp.level3=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
#telephony.lteOnCdmaDevice=1
telephony.lteOnCdmaDevice=0
# simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hmct.sdcard.change=1
persist.sys.hmct.primary.st=internal
ro.hmct.TFcard.supported=true
ro.hmct.hasRealPhoneStorage=false
#
# System prop for enabling the cdrom feature
#
persist.service.cdrom.enable=1
#
# System prop for default USB configuration
#
persist.sys.usb.config=diag,serial_smd,serial_tty,rmnet_bam,mass_storage,adb
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=fluence
# Reduce Background apps limit
ro.sys.fw.bg_apps_limit=20
# System property for cabl
# zhaolinhu modified from 1 to 0
ro.qualcomm.cabl=0
# Enable Fast Dormancy 103
persist.env.fastdorm.enabled=true
#system props for restore modem_pref support
persist.radio.restore_mode_pref = 1
#
# dirty ratio value when enable UMS
#
ro.sys.umsdirtyratio=20
# Enable RST packet drop
persist.data.tcp_rst_drop=true
# system prop for NFC DT
# ro.nfc.port=I2C
#
#DASH video streaming
#Specify max allowed resolution/bandwidth for representations
#Set allowed avsync window during playback
#
persist.dash.max.rep.resolution=1280*720
persist.dash.max.rep.bandwidth=4000000
persist.dash.avsync.window.msec=100
tunnel.audio.encode = false
#PPPOE config enable
#
ro.config.pppoe_enable=1
# system prop for storage test
ro.external.sd.path=/storage/sdcard1
#modified by QKD 20131017 ro.hmct.sdcard.change
ro.hmct.sdcard.change=1
persist.sys.hmct.primary.st=internal
#
# Version of hardware and software.
#
ro.hardware.version=V1.00
ro.software.version=A18_plus_SW_A18_E_V01_140718
ro.hmct.sw.internal.version=A18_plus_SW_A18_E_V01_140718
#ro.hmct.ota.product=A18PLUS
#default not roaming
ro.com.android.dataroaming=0
ro.sms.8X10=1
ro.hmct.sms.max.capacity = 2000
ro.hmct.sms.nobox = true
#modem version
ro.hmct.modem.version=M8612AAAAANLYD193517BA
#add by huyan
ro.sf.lcd_density=240
# hisense style for shutdown dialog
ro.hmct.hisense.style=0
#tianhaiyan add for new card propt
persist.env.phone.newsim = true
#jingnannan add for active dualmode-card on dsds product.
persist.env.phone.autoprovision = true
ro.hmct.product.operator = export
ro.export = true
#timezone
persist.sys.timezone=Africa/Casablanca
#add by xiaoqian for UI2.0
persist.hmct.origin.style=1
#adb auth
ro.adb.secure=1
#add by huangzengzhi
# add by xiaoqian for bootanim
ro.product.unicom=1
#add by dingchao for usb
ro.hmct.bicr.yes=yes
#fm volume add by zouyanfei
persist.sys.hmct.fm.vol=2500
#add by zouyanfei for volumepannel
persist.sys.hmct.volpannel.vol=100
#add by libing for camera preview
camera.hmct.optm.prev=1
ro.hmct.mvno.mcc=208
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=World.ogg
ro.config.notification_sound=Pizzicato.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=1
ro.qc.sdk.izat.service_mask=0x5
ro.gps.agps_provider=1
Spec Model Mann zug3 android 4.3 quard core ram 1 gb screen 480x800
My model don't root
Click to expand...
Click to collapse
just try VROOT
additional - maybe interesting: corresponding branch @Russian board 4PDA (only Russian language! - that's why look at "911 - Quick help for English speaking users"
same problem
You're English is good, better than my Russian. I bought the same phone, Mann Zug 3 with snapdragon 200 msm8212, and bricked it the day I got it. Similar problem, boot loop thanks to a custom boot screen I installed after rooting it (thanks geohot for the towelroot). I got lucky the first time and it eventually rebooted with me inserting the USB and hitting the volume buttons randomly trying to get it into bootloader mode (I know think it can't be done with out an app). Because I'm a slow learner, I then went on to try and install cwm from a similar phone makeup and bricked it again. I still have stock recovery, for all the good it does me, and I couldn't get Odin to recognise it or flash tool. I cant even find a rom to flash from the sd recovery that works. There's one more option of holding down the power and both volume buttons that leads to Chinese and English saying that the "Int SD card failed, hold the power button to reboot". Any help from all you brilliant devs would be so gracious.
Cheers
Patrick Futch said:
I bought the same phone, Mann Zug 3 with snapdragon 200 msm8212,
Click to expand...
Click to collapse
can provide the link (to the seller page) where did you obtain (buy) your phone?
Patrick Futch said:
There's one more option of holding down the power and both volume buttons that leads to Chinese and English saying that the "Int SD card failed, hold the power button to reboot".
Click to expand...
Click to collapse
that is something like "Factory mode" -- for flashing with special type of ROM (NOT *.zip file, but "folder with files")
there are ROM for the similar device (MANN Zug3 A18 --- but only with 512MB RAM & GPU Adreno 203);
Mann Zug A18Plus (Falcon) - its device with 1GB RAM & GPU Adreno 305 (i.e. "302"))
// & acc. to build.prop at first post of this thread -- this thread is about Mann Zug A18Plus (Falcon)
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JLS36C
ro.build.display.id=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.version.incremental=W992.6.01.01
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Tue Jul 22 12:28:06 CST 2014
ro.build.date.utc=1406003286
...
ro.build.product=A18PLUS_CR
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.fingerprint=MANN/A18PLUS_CR/A18PLUS_CR:4.3/JLS36C/W992.6.01.01:userdebug/release-keys
....
#
# Version of hardware and software.
#
ro.hardware.version=V1.00
ro.software.version=A18_plus_SW_A18_E_V01_140718
ro.hmct.sw.internal.version=A18_plus_SW_A18_E_V01_ 140718
#ro.hmct.ota.product=A18PLUS
...
#modem version
ro.hmct.modem.version=M8612AAAAANLYD193517BA
Click to expand...
Click to collapse
& that's why (because of inconsistent GPU) after flashing this ROM to Mann Zug A18Plus (Falcon) - there is "grey lines" only on the screen
so I DO NOT recommend you to flash this ROM;
&& maybe you can ask your seller to share the ROM for you phone (?)
DX.com
I got the phone from dealextreme.com (now dx.com). I found what I think is the producers' (Mann) website but it was more concerned with advertising graphics than support or even instructions. I keep hoping for a universal unbrick method, but none that i've found seem to work with a phone in bootloop and no fastboot/download/bootload mode. And yeah, that double volume and power button thing seems to be manufacturer input method.
---------- Post added at 07:18 PM ---------- Previous post was at 07:05 PM ----------
Cant read it for a while. Excited by the content. Thanks a ton.
Patrick Futch said:
... There's one more option of holding down the power and both volume buttons that leads to Chinese and English saying that the "Int SD card failed, hold the power button to reboot".
Click to expand...
Click to collapse
there is the firmware for flashing with this mode
I have the same problem - bootloop
I just got this phone (falcon edition) and it worked fine the first time I booted.
Then I put in a new sd card and sim and since then it won't boot. I always an image of the green andorid on its back with the middle open and a big red triangle.
After a while it will try to reboot itself only to get to the same image.
I've also tried pushing all the buttons to get into some kind of recovery but nothing works.
Anyone have any suggestions?
Thanks
that is recovery mode (locked)
spidersilver said:
an image of the green andorid on its back with the middle open and a big red triangle.
Click to expand...
Click to collapse
that is recovery mode (locked)
just try to press soft keys ( "home" or "back" or "menu")
--- than appear normal recovery items
then make wipe data / factory reset
MANN zug 3 Flacon
Hi , im new in the xda community , I'm french and i'm sincerly sorry for my so bad english ...
I've just bought my new phone MANN zug 3 A18+ , he got MSM8212 Qualcomm QuadCore 1.2Ghz , 1 GB ram , 4GB ROM (so the falcon one)
Yesterday i found a path to root him ( take rootGenius.exe , for Ascend G6 and it works) but i'm don't sure if it was completly rooted.
And like a andro-geek i tried so much possibilities with that !
But after flashed a boot.img , for install TWRP recovery via Flashify (the app) my phone bootloop with a white screen , i can go to "fastboot downloading" mode , original recovery and a mode which i don't know (vol + , vol - and power) with chinease letters and a message "no update on TF card" !
So , i need to restore my phone , unbrick him , install the stock rom or an other rom ?
I tried to read the topics in russian on "4PDA" but .. I didn't learn russian and google traduction is really ... approximatif , so , Vladimir i need you're help x) !
Thanks very much
Flash stock ROM Zug 3 Falcon (FTM(?) mode)
Papaya59 said:
But after flashed a boot.img , for install TWRP recovery via Flashify (the app) my phone bootloop with a white screen , i can go to "fastboot downloading" mode , original recovery and a mode which i don't know (vol + , vol - and power) with chinease letters and a message "no update on TF card" !
Click to expand...
Click to collapse
there is an archive on MEGA with many req. files for MANN Zug 3 Falcon
0. assure that your device is really MANN Zug 3 Falcon -- check if battery capacity is 2930 mAh (look above cover ))
1. download and unpack archive "a18plus.v1.zip" from MEGA::\\ROM\stock
2. copy unpacked folder "a18plus.v1" archive to 'root' of clean SD card
3. insert SD card into device
4. boot device into "mode which you don't know (vol + , vol - and power) with chinease letters"
... &the flashing is ROM have to start automatically
(/if something wrong - try to rename folder on SD-card into ""a18plus" (without ".v1")
//src of instr.
###############addit.
it looks like bootloader is 'locked from flashing' on MANN Zug 3 Falcon
that's why simple flash boot is impossible;
have try before:
Code:
d:\MANN_ZUG3\MEGA\recovery>fastboot flash recovery Philz_Touch6.57.9MANN_ZUG3Falcon_portedFROMc230w.img
target reported max download size of 515899392 bytes
sending 'recovery' (8316 KB)...
OKAY [ 0.327s]
writing 'recovery'...
[COLOR="Red"]FAILED (remote: partition table doesn't exist)[/COLOR]
finished. total time: 0.334s
but
Code:
d:\MANN_ZUG3\MEGA\recovery>fastboot boot Philz_Touch6.57.9MANN_ZUG3Falcon_portedFROMc230w.img
downloading 'boot.img'...
OKAY [ 0.314s]
booting...
OKAY [ 0.089s]
finished. total time: 0.404s
Flash stock ROM Zug 3 Falcon
Hey Wladimir ! Sorry for the time , i had internet problems !
I tried to do what you said but it doesn't worked , my phone already looks like this (picture)
I tried to put the rom on differents memory cards but , again it doesn't worked , i tried to delete ".v1" but it doesn't worked can you help me again ?
It looks like no update file in TF card :/
Thanks again , bye !
problem with my Mann Zug 3
I write from Italy (sorry for my bad English). In the last April I has buy on internet Mann smartphone model Zug 3. For the first month the zug 3 was perfect. But three week ago he began with the problem with the network connection. Now, I have tried to check the smartphone with android app for search the problem, I have tried to check imei code....but I don't have solved the problem. Do you have a solution?
Please wake up one phone to download the original file recovery
Please do help me the phone I'm looking for the original recovery
Hi
Need firmware/stock ROM for an unbranded tablet. Tablet got broken and it is a blank screen now and it is not booting, Trying to rebuild and fix the issue for this tablet. I bought this tablet through WISH. unable to get the firmware from the seller. Please help.
Model: KT107
Android Version: 6.0
Android Security patch level: 2016-01-01
Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2016/06/17 13:38
Kernel version: 3.10.72+ [email protected] #1
Build number: KT107_V01
Custom build version: KT107_MID-2017
Ram: 4GB
Internal Storage: 64GB
It is an unbranded tablet with 11.6 Inch screen, with a dual sim card. I think Chipset is MT6580.
Maybe wiping user data can help?
jeyaayyanar said:
Hi
Need firmware/stock ROM for an unbranded tablet. Tablet got broken and it is a blank screen now and it is not booting, Trying to rebuild and fix the issue for this tablet. I bought this tablet through WISH. unable to get the firmware from the seller. Please help.
Model: KT107
Android Version: 6.0
Android Security patch level: 2016-01-01
Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2016/06/17 13:38
Kernel version: 3.10.72+ [email protected] #1
Build number: KT107_V01
Custom build version: KT107_MID-2017
Ram: 4GB
Internal Storage: 64GB
It is an unbranded tablet with 11.6 Inch screen, with a dual sim card. I think Chipset is MT6580.
Click to expand...
Click to collapse
I have a similar tablet, and accidentally softbricked it by doing fastboot oem unlock (I think...). In my case though, the screen did not stay black, but the Android Logo showed forever, and the user's screen never appeared.
What got it working again was locking it again using fastboot oem lock and then wiping user data.
Proceed as follows:
1. Make sure tablet is off
2. Press power and Volume down simultaneously
3. Hold "Volume down", until you see the factory menu
4. Use "Volume down" to navigate to "Clear eMMC"
5. Use power button to select.
However, if you find replacement firmware somewhere, I'd be interested too, as mine was sold with an Android Lollipop 5.1 doctored to look like 7.0. I think I should be able to at least get Android 6.0 for this tablet.
After the reset bootloop, I need this flash file for me.
Please could you help?
Alk142 said:
I have a similar tablet, and accidentally softbricked it by doing fastboot oem unlock (I think...). In my case though, the screen did not stay black, but the Android Logo showed forever, and the user's screen never appeared.
What got it working again was locking it again using fastboot oem lock and then wiping user data.
Proceed as follows:
1. Make sure tablet is off
2. Press power and Volume down simultaneously
3. Hold "Volume down", until you see the factory menu
4. Use "Volume down" to navigate to "Clear eMMC"
5. Use power button to select.
However, if you find replacement firmware somewhere, I'd be interested too, as mine was sold with an Android Lollipop 5.1 doctored to look like 7.0. I think I should be able to at least get Android 6.0 for this tablet.
Click to expand...
Click to collapse
Please I have the same kind of device but mine is stuck on a guest user account and my notification, Developer options and a lot of stuff doesn't work.
Please I would be so grateful if you could dump your stock ROM for me so I could flash mine. Please bro, i have searched everywhere for the ROM but without success until I stumbled on this thread.
***Beware, not all KT107 are compatible with each others, make a backup first if you can and use at your own risk***
****This is for MT6580 with kernel:3.10.72+ , do not even try if you have different kernel or cpu****
I opened the casing of my tablet, here are the models number written on the mainboard:
directly on the board :
KT961C12_80_216_V3.0
on the sticker:
KT107_1+16_D2_31PIN_20170424
BOM:KT107C12_80_216_V3.0_1G 16G_RDA_GSM
四频_NB1_无按體_NDR_最产BOM_N20180928
*There might be mistakes in the chinese characters*
I have a full TWRP backup and the stock images files from a functional tablet with the same device number. My device was working but here's what I did:
1: Root with KingoRoot
KingoRoot: https://www.kingoapp.com/
2: Install Flashify
Flashify : https://play.google.com/store/apps/d...shify&hl=en_US
3: Download this TWRP build :
TWRP : https://mega.nz/#!27QUFQ5J!nj5WNmD8yMTULrS2lc90bk1qWhRs-xY6b_ou229BgYM
4: Install the TWRP image to recovery with flashify
5: Reboot to recovery ( on my device I hold "vol up" + "pwr" to get to the bootloader menu, then choose recovery)
6: Copy the stock twrp backup to your device and restore
Stock TWRP backup : https://mega.nz/#F!jJ83Fabb!raIOtZSsqyMboVbb_5sDVQ
***You won't be able to use this backup without TWRP installed***
If you need the stock img to try to restore from fastboot I have those too:
system.img:
https://mega.nz/#!qY0RlIBI!lxsxP2Jn7bdQW_0zKQ8eoEcsadj0w7kru_CKqqnM_bc
recovery.img:
https://mega.nz/#!mAEiASpD!lJAMH1OilJ68vSdeGuP_wBWT9roDQfEyokqILFnr_Fg
boot.img:
https://mega.nz/#!zAFQlAiK!RMzjBvFZFjdkqwDdJvk_V63hGBgT7fDKUegFls-YGiA
SP Flash Tools Compatible ROM and scatter file:
https://mega.nz/#!rB8T1KjS!qya-pScSPdAV5cWLfmD-KN1nlxgb0yzo2vVmGATXjRo
Thanks a lot, please could you make the scatter file?
fueg said:
I have a full TWRP backup and the stock images files from a functional tablet with the same device number. My device was working but here's what I did:
Thanks a lot Fueg, you have no idea how much I appreciate your sending these files, though I am yet to Flash them.
Please as I understand, the spflash tool requires the scatter file to be able to flash a ROM. Please could you make a scatter file for the phone too? I could have used fastboot to flash but my bootloader is not unlocked and I don't have access to my developer options to enable me unlock it neither could I install any apps on my phone as it is stuck in guest user mode.
I am just a novice in this stuff but if you have any other ways I could flash the ROM without needing a scatter file please could you tell me please?
Thanks you very again!!!
EDIT: Please all the links to the files are not working. It's asking for a decryption key saying the provided key is invalid and I should ask the link creator for the decryption keys. Please check and rectify.
Could you also share me your build.prop file for your phone as well for comparison with mine just to be sure I have similar specs.
Click to expand...
Click to collapse
Please all the links to the files are not working. It's asking for a decryption key saying the provided key is invalid and I should ask the link creator for the decryption keys. Please check and rectify.
Could you also share me your build.prop file for your phone as well for comparison with mine just to be sure I have similar specs.[/QUOTE said:
I updated the download links in my previous post it should hopefully work now.
If you need to flash a version that you can flash with SP Flash Tool I found one that works (everything works but my display is flipped 180 degree, that's an easy fix). I will add a link for it in my previous post with all the other files.
I don't have access to the buil.prop file right now but it is pretty much useless to check the tablet specs anyway because the chinese changed all they can to make it look better than it is :
Reported CPU: MT 6580 : 8 core # 2.5 Ghz
Real CPU: MT 6580 : 4 core # 1.3Ghz
Reported Storage : 64Gb
Real Storage : 16Gb (about 12Gb available)
Reported RAM : 4Gb
Real RAM : 1Gb
Reported Android Version : 6.0
Real Android Version : 5.1
The ROM for SP Flash Tool mostly fixes the fake infos except the Android version, it still reports Android 6.0 when in reality it is Android 5.1
Click to expand...
Click to collapse
Please so sorry, but the download link for the TWRP build still don't work.
fueg said:
I updated the download links in my previous post it should hopefully work now.
If you need to flash a version that you can flash with SP Flash Tool I found one that works (everything works but my display is flipped 180 degree, that's an easy fix). I will add a link for it in my previous post with all the other files.
I don't have access to the buil.prop file right now but it is pretty much useless to check the tablet specs anyway because the chinese changed all they can to make it look better than it is :
Reported CPU: MT 6580 : 8 core # 2.5 Ghz
Real CPU: MT 6580 : 4 core # 1.3Ghz
Reported Storage : 64Gb
Real Storage : 16Gb (about 12Gb available)
Reported RAM : 4Gb
Real RAM : 1Gb
Reported Android Version : 6.0
Real Android Version : 5.1
The ROM for SP Flash Tool mostly fixes the fake infos except the Android version, it still reports Android 6.0 when in reality it is Android 5.1
Click to expand...
Click to collapse
Thank you so very much Fueg, but please so sorry for being so disturbing but the download link for the TWRP build still don't work. All the others now work except the Link for only the custom TWRP recovery build which is the third Link counting from the top. I really need that custom TWRP recovery because the stock recovery is lame.
Please if you could just correct that too, I would finally get out of your hair hopefully!
Thanks again my friend.
EDIT: Please also add the link for the display 180 degree flipped fix you mentioned, I couldn't find it.
Thanks again for your assistance.
Aloydonez said:
Thank you so very much Fueg, but please so sorry for being so disturbing but the download link for the TWRP build still don't work. All the others now work except the Link for only the custom TWRP recovery build which is the third Link counting from the top. I really need that custom TWRP recovery because the stock recovery is lame.
Please if you could just correct that too, I would finally get out of your hair hopefully!
Thanks again my friend.
EDIT: Please also add the link for the display 180 degree flipped fix you mentioned, I couldn't find it.
Thanks again for your assistance.
Click to expand...
Click to collapse
No problem, I added the twrp img as attachment below. For the orientation fix you just have to change a line in build.prop
Look for the line "ro.sf.hwrotation=180"
Change it for "ro.sf.hwrotation=0" if your display is rotated 180 degrees
The first twrp works wit the first "stock" files and with the twrp backup, if you use the SP Flash Tools files you will need the second twrp
Please help, I just ran into serious trouble
fueg said:
No problem, I added the twrp img as attachment below. For the orientation fix you just have to change a line in build.prop
Look for the line "ro.sf.hwrotation=180"
Change it for "ro.sf.hwrotation=0" if your display is rotated 180 degrees
The first twrp works wit the first "stock" files and with the twrp backup, if you use the SP Flash Tools files you will need the second twrp
Click to expand...
Click to collapse
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Aloydonez said:
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Click to expand...
Click to collapse
Do you know the exact brand and model you have? There is a lot of variation under the name KT107 and they are not all compatible with each others. If you really want to be sure you can try to open the device and check the number written on the pcb, mine was on a sticker on the main board. If you are willing to do that send me the information and I can try to find a suitable ROM.
Did you make a backup of you device in SP Flash Tools before you flash the ROM, if you did you can try to restore it...
You can also try this firmware:
https://yadi.sk/d/Gis_kl1y3UjJQC
It's a ROM for another KT107 variant...
Thanks Fueg, this is the information you requested
fueg said:
Do you know the exact brand and model you have? There is a lot of variation under the name KT107 and they are not all compatible with each others. If you really want to be sure you can try to open the device and check the number written on the pcb, mine was on a sticker on the main board. If you are willing to do that send me the information and I can try to find a suitable ROM.
Did you make a backup of you device in SP Flash Tools before you flash the ROM, if you did you can try to restore it......
Click to expand...
Click to collapse
No I couldn't make any backup at all because I was stuck in guest user mode on the phone, so developer options wasn't available to me and MTKdroid tools could not detect the tablet.
Below are all the information I could get about the device. Thank you so very much for all your patience and assistance.
_____________________________________
(Below is what I found on the label on one of the heat sinks on the motherboard.)
TD_KT107_D2_1+16 31PIN-HNHBOE_M1D50-901
BOM:KT107C_A_V1.0_1G+16G_GSM B1_31PIN
MTKL20170818395
_____________________________________
( This below was printed on the PCB)
KT961C-V1.0 2016.07.29
_____________________________________
OS Properties
KERNEL: Linux version 3.10.72+ ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Nov 9 18:16:15 CST 2016
CODENAME: REL
Mainboard: unknown
Bootloader: unknown
Manufacturer: JTY
BRAND: Padking
Model: Padking
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: KT107
DISPLAY: Padking_V01
FINGERPRINT: alps/full_KT107_NL/KT107_NL:5.1/LMY47I/1477364172:user/test-keys
Release= 6.0
HARDWARE: mt6580
ID: LMY47I
TAGS: test-keys
Radio= MOLY.WR8.W1449.MD.WG.MP.V23, 2016/03/18 15:22
_________________________________'_'___
(This below is the build properties)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47I
ro.build.display.id=Padking_V01
ro.build.version.incremental=1477364172
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.version.security_patch=2016-01-01
ro.build.version.base_os=
ro.build.date=2016年 10月 25日 星期二 10:57:29 CST
ro.build.date.utc=1477364249
ro.build.type=user
ro.build.user=azhuo
ro.build.host=azhuo-desktop
ro.build.tags=test-keys
ro.build.flavor=full_KT107_NL-user
ro.product.model=Padking
ro.product.brand=Padking
ro.product.name=KT107
ro.product.device=KT107
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=JTY
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt6580
# ro.build.product is obsolete; use ro.product.device
ro.build.product=KT107
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=full_KT107_NL-user 5.1 LMY47I 1477364172 test-keys
ro.build.fingerprint=alps/full_KT107_NL/KT107_NL:5.1/LMY47I/1477364172:user/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/vsun/KT107_NL/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp
# USB BICR function
ro.sys.usb.bicr=no
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
# temporary enables NAV bar (soft keys)
qemu.hw.mainkeys=0
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=0
#ro.kernel.qemu.gles=0
ro.opengles.version=131072
#ro.boot.selinux=disable
# Disable dirty region for Mali
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=210
ro.mtk_default_ime=com.sohu.inputmethod.sogou.SogouIME
persist.sys.timezone=
ro.jty.version.release=Padking_MID-2016
ro.jty.showdev=true
ro.elink.gemini=true
#ro.operator.optr=CUST
ro.build.screen_size_inches=10.1
#lqh add for romtool
ro.romtool.jtynetworkType=2G
ro.romtool.homepage=www.google.com
ro.romtool.front.picturesize=1600x1200
ro.romtool.back.picturesize=2560x1920
ro.jty.data.expandNum=0.5
ro.jty.fat.expandNum=1.5
#ro.romtool.fake_userdata=4.00
#ro.romtool.fake_pcstorage=8.00
ro.romtool.fake_memory=1
ro.romtool.fake_lcd=1280x800
ro.romtool.cpu_platform=MT6580
ro.romtool.cpu_corenumber=4
ro.romtool.cpu_frequency=1500.00
ro.romtool.showAddInfo=false
ro.romtool.fontsize=1.08
ro.romtool.screenbrightness=170
ro.romtool.screenofftimeout=60
ro.romtool.hlimit=true
ro.romtool.fat.name=Padking
#lqh add end
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.mediatek.chip_ver=S01
ro.mediatek.version.release=KT107_L1_20160428
ro.mediatek.platform=MT6580
ro.telephony.sim.count=2
persist.radio.default.sim=0
persist.radio.multisim.config=dsds
persist.md.perm.checked=to_upgrade
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=270
ril.current.share_modem=2
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
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
mediatek.wlan.chip=CONSYS_MT6735
mediatek.wlan.module.postfix=_consys_mt6735
ril.radiooff.poweroffMD=0
ro.frp.pst=/dev/block/platform/mtk-msdc.0/by-name/frp
ro.mediatek.version.branch=L1.MP6
ro.mediatek.version.sdk=4
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r2
ro.com.google.clientidbase=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.ms=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.yt=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.am=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.gmm=alps-full_KT107_NL-{country}
ro.mtk_gemini_support=1
ro.mtk_audio_profiles=1
ro.mtk_audenh_support=1
ro.mtk_lossless_bt_audio=1
ro.mtk_besloudness_support=1
ro.mtk_bessurround_support=1
ro.mtk_gemini_enhancement=1
ro.mtk_wapi_support=1
ro.mtk_bt_support=1
ro.mtk_wappush_support=1
ro.mtk_agps_app=1
ro.mtk_voice_ui_support=1
ro.mtk_voice_unlock_support=1
ro.mtk_voice_contact_support=1
ro.mtk_wlan_support=1
ro.mtk_gps_support=1
ro.mtk_omacp_support=1
ro.mtk_search_db_support=1
ro.mtk_dialer_search_support=1
ro.mtk_dhcpv6c_wifi=1
ro.have_aacencode_feature=1
ro.mtk_fd_support=1
ro.mtk_oma_drm_support=1
ro.mtk_cta_drm_support=1
ro.mtk_widevine_drm_l3_support=1
ro.mtk_eap_sim_aka=1
ro.mtk_fm_recording_support=1
ro.mtk_audio_ape_support=1
ro.mtk_flv_playback_support=1
ro.mtk_fd_force_rel_support=1
ro.mtk_wmv_playback_support=1
ro.mtk_send_rr_support=1
ro.mtk_rat_wcdma_preferred=1
ro.mtk_tb_call_speaker_on=1
ro.mtk_emmc_support=1
ro.mtk_tetheringipv6_support=1
ro.mtk_enable_md1=1
ro.mtk_flight_mode_power_off_md=1
ro.mtk_pq_support=2
ro.mtk_miravision_support=1
ro.mtk_miravision_image_dc=1
ro.mtk_wifi_mcc_support=1
ro.mtk_system_update_support=1
ro.mtk_sim_hot_swap=1
ro.mtk_thumbnail_play_support=1
ro.mtk_bip_scws=1
ro.mtk_world_phone_policy=0
ro.mtk_perfservice_support=1
ro.mtk_cta_set=1
ro.mtk_mobile_management=1
ro.mtk_antibricking_level=2
ro.mtk_cam_mfb_support=0
ro.mtk_cam_mav_support=1
ro.sim_refresh_reset_by_modem=1
ro.mtk_live_photo_support=1
ro.mtk_motion_track_support=1
ro.mtk_privacy_protection_lock=1
ro.mtk_bg_power_saving_support=1
ro.mtk_bg_power_saving_ui=1
ro.have_aee_feature=1
ro.sim_me_lock_mode=0
ro.mtk_dual_mic_support=0
ro.mtk_is_tablet=0
ro.mtk_voice_extension_support=1
wfd.dummy.enable=1
ro.mediatek.project.path=device/vsun/KT107_NL
persist.mtk.wcn.combo.chipid=-1
service.wcn.driver.ready=no
ro.com.android.mobiledata=false
persist.radio.mobile.data=0,0
persist.meta.dumpdata=0
persist.sys.dex2oat_white_list=com.isoftdimension.co.id.sixpay:com.instagram.android:
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=div
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Aloydonez said:
No I couldn't make any backup at all because I was stuck in guest user mode on the phone, so developer options wasn't available to me and MTKdroid tools could not detect the tablet.
Below are all the information I could get about the device. Thank you so very much for all your patience and assistance.
. . .
. . .
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
maybe this:
https://cloud.mail.ru/public/4XAT/4nnv5t5WY
or this one
https://drive.google.com/file/d/19pCWODtS3BdN-PGRQVXt26taGboBJCsp/view
you can also try those:
http://4pda.ru/forum/index.php?showtopic=803557&st=0#Spoil-58377265-8
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware, I have not been able to find an exact match...
Anyway if you keep trying different firmware chances are that you will eventually find one that is compatible with your device (in my case I had to try about 10 and the one that works was not an exact match but it still works 100%)
you can also try those:
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware said:
Thank you so much for your assistance. Now I will get to work.
I will let you know if I am successful. Thanks!
Click to expand...
Click to collapse
Aloydonez said:
you can also try those:
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware said:
Thank you so much for your assistance. Now I will get to work.
I will let you know if I am successful. Thanks!
Click to expand...
Click to collapse
Best of luck to you, I hope something works!
Click to expand...
Click to collapse
Aloydonez said:
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Click to expand...
Click to collapse
The display drivers are indeed contained within the ROM. Apparently your display is not the same then the one I have. If you have a backup of your previous firmware you can look for a tutorial on haw to extract the files you need (inside boot.img and system.img), and another tutorial on how to port ROM for mediatek 6580.
If you don't have a backup you will have to try to find a ROM with the display working to have the drivers you need ..
flashing twrp
hello fueg
thank you for your efforts
well i need to flash twrp file but i could not root my tablet. this give me one option ;to use sp flash tool. my questions to you
1- i review the scatter file you submitted and compare it to the one i see when i connect my device; there are many differences in start address and size; so which one i should use?
2- since iam flashing only the twrp file in recovery.img section; do i need to includes other sections in the scatter file?
Disclaimer : I don’t take any responsibility for any error/Damage/Losing data on your Xiaomi Redmi Note 9 Pro Max. If you are responsible for any mistakes, follow the flashing guide for the files. Some functions don’t operate properly and can cause serious damage to your Device.
Basic Pre-Requirements
- Enable USB Debugging on your Xiaomi Redmi Note 9 Pro Max
- Turn on the adb and fastboot.
- Unlock the bootloader of Xiaomi Redmi Note 9 Pro Max. : follow this from official MI website : External link of Official MI website
– Download and Manually Install Android USB Drivers on your PC
- Download TWRP (Unofficial) : Download
How to install TWRP on Xiaomi Redmi Note 9 Pro Max
First, Switch Off your Smartphone
Open your Mobile Fastboot
Using power off your Device and then hold the Volume Down + Power button
Now, Open the ADB folder on your PC and Laptop.
Then, Select the Address Bar in the ADB File
Type Cmd and hit the Enter button
Type the command in Cmd (Inside “Filename,” You can drag the file directly to the CMD instead of Typing.)
NOTE : Filename is the name of TWRP you downloaded above, replace the name with that.
adb Reboot Bootloader
Fastboot Devices
Fastboot Flash Recovery “TWRP filename.img” and Hit Enter
Then After Type “Fastboot reboot” and Hit Enter.
Congratulations, you have successfully installed the TWRP File on Xiaomi Redmi Note 9 Pro Max
How to Root Xiaomi Redmi Note 9 Pro Max
Download Magisk Zip and Download No verity opt encrypt.zip and Move to Mobile Storage
Then Switch your Phone
Turn On your at Recovery Mode (hold the Volume Down + Power button)
TWRP Recovery, Select INSTALL
Then Browse and Select the saved file of Magisk.Zip
Now Click Install Button
Finally, Reboot Your Device
Congratulations, you successfully Rooted your Device
supersu??
or is it magisk???
kindly correct
Then Browse and Select the saved file of SuperSU Zip
Click to expand...
Click to collapse
and i thought magisk canary build is required for android 10???
this recovery appears to be for 9s or 9 pro devices
look at the default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.actionable_compatible_property.enabled=false
ro.postinstall.fstab.prefix=/system
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
debug.atrace.tags.enableflags=0
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.usejit=true
dalvik.vm.usejitprofiles=true
dalvik.vm.dexopt.secondary=true
dalvik.vm.appimageformat=lz4
ro.dalvik.vm.native.bridge=0
pm.dexopt.first-boot=extract
pm.dexopt.boot=extract
pm.dexopt.install=speed-profile
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.ab-ota=speed-profile
pm.dexopt.inactive=verify
pm.dexopt.shared=speed
dalvik.vm.dex2oat-resolve-startup-strings=true
dalvik.vm.dex2oat-max-image-block-size=524288
dalvik.vm.minidebuginfo=true
dalvik.vm.dex2oat-minidebuginfo=true
ro.iorapd.enable=false
tombstoned.max_tombstone_count=50
persist.sys.usb.config=adb
#
# ADDITIONAL VENDOR DEFAULT PROPERTIES
#
ro.vndk.version=29
ro.vndk.lite=true
ro.zygote=zygote64_32
ro.logd.size.stats=64K
log.tag.stats_log=I
ro.bionic.arch=arm64
ro.bionic.cpu_variant=generic
ro.bionic.2nd_arch=arm
ro.bionic.2nd_cpu_variant=cortex-a9
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
ro.minui.pixel_format=BGRA_8888
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Thu May 7 00:47:33 CST 2020
ro.system.build.date.utc=1588783653
ro.system.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.system.build.id=QQ1D.200205.002
ro.system.build.tags=test-keys
ro.system.build.type=eng
ro.system.build.version.incremental=eng.wzsx15.20200507.004808
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=Redmi
ro.product.system.device=curtana
ro.product.system.manufacturer=Xiaomi
ro.product.system.model=Redmi Note 9S
ro.product.system.name=curtana
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ1D.200205.002
ro.build.display.id=omni_redmiNote9s-eng 10 QQ1D.200205.002 eng.wzsx15.20200507.004808 test-keys
ro.build.version.incremental=eng.wzsx15.20200507.004808
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2023-12-01
ro.omni.version.security_patch=2020-02-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=2020年 05月 07日 星期四 00:48:44 CST
ro.build.date.utc=1588783653
ro.build.type=eng
ro.build.user=wzsx150
ro.build.host=wzsx150-virtual-machine
ro.build.tags=test-keys
ro.build.flavor=omni_redmiNote9s-eng
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=zh-CN
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=curtana
# Do not try to parse description or thumbprint
ro.build.description=curtana_global-user 10 QKQ1.191215.002 V11.0.7.0.QJWMIXM release-keys
ro.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.omni.device=redmiNote9s
# end build properties
#
# from device/twrp/redmiNote9s/system.prop
#
#
#start system.prop
#
ro.secure=0
ro.adb.secure=0
ro.build.date.utc=1420041600
persist.sys.timezone=Asia/Shanghai
ro.sf.lcd_density=440
# for device
ro.treble.enabled=true
vendor.gatekeeper.disable_spu=true
ro.boot.init_rc=/init.rc
#end system.prop
#
# end of device/twrp/redmiNote9s/system.prop
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
ro.kernel.android.checkjni=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.image-dex2oat-filter=verify-at-runtime
net.bt.name=Android
ro.boot.dynamic_partitions=true
ro.vendor.build.security_patch=2023-12-01
ro.vendor.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist64=arm64-v8a
ro.product.board=curtana
ro.board.platform=atoll
ro.hwui.use_vulkan=
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.vendor.build.date=Thu May 7 00:47:33 CST 2020
ro.vendor.build.date.utc=1588783653
ro.vendor.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.vendor.build.id=QQ1D.200205.002
ro.vendor.build.tags=test-keys
ro.vendor.build.type=eng
ro.vendor.build.version.incremental=eng.wzsx15.20200507.004808
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=Redmi
ro.product.vendor.device=curtana
ro.product.vendor.manufacturer=Xiaomi
ro.product.vendor.model=Redmi Note 9S
ro.product.vendor.name=curtana
# end common build properties
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Thu May 7 00:47:33 CST 2020
ro.bootimage.build.date.utc=1588783653
ro.bootimage.build.fingerprint=Redmi/omni_redmiNote9s/redmiNote9s:10/QQ1D.200205.002/wzsx15005070047:eng/test-keys
#
# ADDITIONAL VENDOR BUILD PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.carrier=unknown
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.odm.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.odm.product.cpu.abilist32=armeabi-v7a,armeabi
ro.odm.product.cpu.abilist64=arm64-v8a
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.odm.build.date=Thu May 7 00:47:33 CST 2020
ro.odm.build.date.utc=1588783653
ro.odm.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.odm.build.id=QQ1D.200205.002
ro.odm.build.tags=test-keys
ro.odm.build.type=eng
ro.odm.build.version.incremental=eng.wzsx15.20200507.004808
ro.odm.build.version.release=10
ro.odm.build.version.sdk=29
ro.product.odm.brand=Redmi
ro.product.odm.device=curtana
ro.product.odm.manufacturer=Xiaomi
ro.product.odm.model=Redmi Note 9S
ro.product.odm.name=curtana
# end common build properties
#
# ADDITIONAL ODM BUILD PROPERTIES
#
#
# ADDITIONAL PRODUCT PROPERTIES
#
ro.build.characteristics=default
ro.com.google.clientidbase=android-google
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.build.selinux=1
persist.sys.disable_rescue=true
ro.opa.eligible_device=true
net.tethering.noprovisioning=true
ro.control_privapp_permissions=enforce
ro.config.ringtone=omni_ringtone1.ogg,omni_ringtone1.ogg
ro.config.notification_sound=omni_notification1.ogg
ro.config.alarm_alert=omni_alarm1.ogg
ro.services.whitelist.packagelist=com.google.android.gms
ro.modversion=OmniROM-10-20200507-redmiNote9s-HOMEMADE
ro.omni.version=10-20200507-redmiNote9s-HOMEMADE
#
# RECOVERY UI BUILD PROPERTIES
#
Click to expand...
Click to collapse
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
i.snehal.kiran said:
supersu??
or is it magisk???
kindly correct
this recovery appears to be for 9s or 9 pro devices
look at the default.prop
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
Click to expand...
Click to collapse
It's for magisk, SuperSU refers to magisk we're installing.
Yes, it's not official TWRP, so it's not updated as desired but keeping in mind that both devices have same CPU, it's a workaround until real thing comes. (Official TWRP),, and yes it works,, tried myself and worked,.
i.snehal.kiran said:
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
Click to expand...
Click to collapse
Have you tried that method in your link ?
coolvipcandy said:
Have you tried that method in your link ?
Click to expand...
Click to collapse
no i havent tried . my friend has pro max .
i am just searching for stable rooting method for him.
i will tell him to try your method then.
thanks
coolvipcandy said:
Disclaimer : I don’t take any responsibility for any error/Damage/Losing data on your Xiaomi Redmi Note 9 Pro Max. If you are responsible for any mistakes, follow the flashing guide for the files. Some functions don’t operate properly and can cause serious damage to your Device.
Basic Pre-Requirements
- Enable USB Debugging on your Xiaomi Redmi Note 9 Pro Max
- Turn on the adb and fastboot.
- Unlock the bootloader of Xiaomi Redmi Note 9 Pro Max. : follow this from official MI website : External link of Official MI website
– Download and Manually Install Android USB Drivers on your PC
- Download TWRP (Unofficial) : Download
How to install TWRP on Xiaomi Redmi Note 9 Pro Max
First, Switch Off your Smartphone
Open your Mobile Fastboot
Using power off your Device and then hold the Volume Down + Power button
Now, Open the ADB folder on your PC and Laptop.
Then, Select the Address Bar in the ADB File
Type Cmd and hit the Enter button
Type the command in Cmd (Inside “Filename,” You can drag the file directly to the CMD instead of Typing.)
NOTE : Filename is the name of TWRP you downloaded above, replace the name with that.
adb Reboot Bootloader
Fastboot Devices
Fastboot Flash Recovery “TWRP filename.img” and Hit Enter
Then After Type “Fastboot reboot” and Hit Enter.
Congratulations, you have successfully installed the TWRP File on Xiaomi Redmi Note 9 Pro Max
How to Root Xiaomi Redmi Note 9 Pro Max
Download Magisk Zip and Download No verity opt encrypt.zip and Move to Mobile Storage
Then Switch your Phone
Turn On your at Recovery Mode (hold the Volume Down + Power button)
TWRP Recovery, Select INSTALL
Then Browse and Select the saved file of SuperSU Zip
Now Click Install Button
Go again to install Button, then Browse and Install No verity opt encrypt.zip and confirm install
Finally, Reboot Your Device
Congratulations, you successfully Rooted your Device
Click to expand...
Click to collapse
what is the use of this file "No verity opt encrypt.zip"
i.snehal.kiran said:
supersu??
or is it magisk???
kindly correct
and i thought magisk canary build is required for android 10???
this recovery appears to be for 9s or 9 pro devices
look at the default.prop
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
Click to expand...
Click to collapse
ayepandey said:
what is the use of this file "No verity opt encrypt.zip"
Click to expand...
Click to collapse
dm-verity helps prevent persistent rootkits that can hold onto root privileges and compromise devices.
No-verity helps here to suppress dm-verity.
Anyone rooted n installed custom recovery on pro max with miui 12? I tried last week and made a huge out of my phone.. bricked multiple times and finally went back to miui fastboot rom.. if anyone successfully done it, can you please give me the steps..
Is there an official TWRP for this set now?
Is the No verity opt encrypt.zip needed and if I have to use it, should it be flashed with TWRP? Is booting up safe without flashing No verity opt encrypt.zip? I'm thinking of buying this device.
Supermatt01 said:
Is the No verity opt encrypt.zip needed and if I have to use it, should it be flashed with TWRP? Is booting up safe without flashing No verity opt encrypt.zip? I'm thinking of buying this device
Click to expand...
Click to collapse
I use to flash No verity immediately after flashing TWRP on my Redmi Note 4 to avoid bootloop and brick. Don't know for Redmi Note 9.
How many of you rooted Redmi Note 9 Pro Max?
Please hit LIKE button (please be honest).
I badly want to buy it but I did not find many ppl rooted or successfully with Twrp.