my sk17 (bootloader unlocked using flashtool) worked perfectly fine. I could flash kernels and ftf files fine on windows 7. Now my computer is running on windows 8 consumer preview (32 bit) and I've got a BUNCH of problems.
1. PC Companion recognizes my phone as Xperia Arc (LT15). The build prop file shows my phone as SK17i.
Merging of the /util/data/semc_kernel_time_stamp.prop file ##### ro.build.date=Tue Apr 24 11:57:09 2012 ro.build.date.utc=1335261429 ro.build.user=BuildUser ro.build.host=BuildHost
### ## Final patch of properties ##### ro.build.product=SK17i ro.build.description=SK17i-userdebug 4.0.4 4.1.B.0.431 UL5_3w test-keys
ro.product.brand=SEMC ro.product.name=SK17i_1247-1046 ro.product.device=SK17i ro.build.tags=release-keys ro.build.fingerprint=SEMC/SK17i_1247-1046/SK17i:4.0.4/4.1.B.0.431/UL5_3w:userdebug/release-keys
### ############## Updating of the SW Version ################# ro.semc.version.fs_revision=4.1.B.0.43 1 ro.build.id=4.1.B.0.431 ro.build.display.id=4.1.B.0.431
### ## Values from product package metadata ##### ro.semc.product.model=SK17i ro.semc.ms_type_id=AAD-3880097-BV ro.semc.version.fs=WORLD-1-8 ro.semc.product.name=Xperia Mini Pro ro.semc.product.device=SK17 ro.product.model=SK17i
# begin build properties # autogenerated by buildinfo.sh ro.build.version.incremental=UL5_3w ro.build.version.sdk=15 ro.build.version.codename=REL ro.build.version.release=4.0.4 ro.build.type=userdebug ro.product.board= ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=Sony Ericsson ro.product.locale.language=en ro.product.locale.region=GB ro.wifi.channels= ro.board.platform=msm7x30 # ro.build.product is obsolete; use ro.product.device # Do not try to parse ro.build.description or .fingerprint ro.build.characteristics=default # end build properties # # system.prop for mango
2. When I try to run flashtool, it says that drivers for my phone are not installed. When I try to install flashtool drivers, the installation fails at the device driver installation wizard.
3. When I try to manually install the drivers from device manager (after using advanced startup to disable driver signing), I get an error message about Windows not finding the file specified for Android ADB Interface.
I'm using kamarush's rom and his kernel. And I can access my sd card on my pc just fine. But I can't flash any kernel (because the drivers are not installed according to flashtool) and I can't manually install the drivers because of the adb interface. I've searched for DAYS and nothing has worked so far. Any help would be appreciated.
Maybe flashtool n drivers not compatible for win 8.
Sent from Hubble Telescope
What happens when you connect your phone in fastboot mode and connect it to the pc? Does it ask for drivers?
Make sure you are using flashtool for 32bit and not 64
Rudjgaard said:
What happens when you connect your phone in fastboot mode and connect it to the pc? Does it ask for drivers?
Make sure you are using flashtool for 32bit and not 64
Click to expand...
Click to collapse
The led light is blue but it doesn't ask for drivers. And I'm sure I'm using the right flashtool version.
i too had a hard time to use fastboot in windows 8... When you install the drivers from the drivers folder of the flashtool, then it will not install the fastboot drivers, soo when we connect our phone in fatboot mode, the pc cannot detect our phone... there is a guide somewhere in the xda which says how to install fastboot drivers in windows 8.. hope you can do a gentle search..
See link
Androxyde wrote: disable driver signature check from windows 8 and you will be able to install fastboot drivers.
I have no idea why but disabling driver signature doesn't help at all. It doesn't install the drivers. I guess I won't be flashin any of those jellybean roms anytime soon.
Download vmware if you don't already have it, download any os img and use that, this could be a workaround if nothing else works..
Related
I8160XXLK5 (CSC: I8160BTULK5) PRE-ROOTED
United Kingdom, 2012 November, Android 2.3.6
The warranty will be kept (i.e binary counter remains untouched).
Download: http://d-h.st/Bg4
To install a custom kernel without avoiding your warranty just use a dd command:
Code:
su
dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
reboot
More info
build.prop:
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXLK5
ro.build.version.incremental=XXLK5
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Thu Nov 15 17:09:29 KST 2012
ro.build.date.utc=1352966969
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-49
ro.build.tags=release-keys
ro.product.model=GT-I8160
ro.product.name=GT-I8160
ro.product.device=GT-I8160
ro.product.brand=samsung
ro.product.board=codina
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I8160XXLK5
ro.build.hidden_ver=I8160XXLK5
ro.build.changelist=1211379
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=ux500
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I8160
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I8160-user 2.3.6 GINGERBREAD XXLK5 release-keys
ro.build.fingerprint=samsung/GT-I8160/GT-I8160:2.3.6/GINGERBREAD/XXLK5:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I8160XXLK5
ro.build.hidden_ver=I8160XXLK5
ro.build.changelist=1211379
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Click to expand...
Click to collapse
Available system languages:
Samsung keyboard languages:
Swype languages:
what about performances than I8160XXLI2?
thanks
mkel91,
Nothing miraculous in this part, it will not bring 2 extra cores or something like
More or less the same as in previous firmwares.
Superuser works well or you must install superSU?
I've just installed it, everything is working well..
antsm said:
I8160XXLK5 (CSC: I8160BTULK5) PRE-ROOTED
[
To install a custom kernel without avoiding your warranty just use a dd command:
Code:
su
dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
reboot
Click to expand...
Click to collapse
wanted to know;
where do i perform these commands? ADB on Windows? or in Terminal Emulator via phone?
a little noobie steps would be great
yethz said:
where do i perform these commands? ADB on Windows? or in Terminal Emulator via phone?
Click to expand...
Click to collapse
Both methods are acceptable, choose on your own.
yethz said:
a little noobie steps would be great
Click to expand...
Click to collapse
Simply put kernel.bin to /sdcard and perform the commands, nothing more
antsm said:
Both methods are acceptable, choose on your own.
Simply put kernel.bin to /sdcard and perform the commands, nothing more
Click to expand...
Click to collapse
where is this kernel.bin from? I download your CWM Kernel from your other threads but it is .tar.md5 format...
yethz said:
where is this kernel.bin from? I download your CWM Kernel from your other threads but it is .tar.md5 format...
Click to expand...
Click to collapse
You have to remove an *.md5 extension and extract kernel from the *.tar file. Or just use Odin (it's a simplier way) if you don't want to care about the warranty
antsm said:
You have to remove an *.md5 extension and extract kernel from the *.tar file. Or just use Odin (it's a simplier way) if you don't want to care about the warranty
Click to expand...
Click to collapse
Oww.. Thank you. that clear things out more
Yeah Odin is more easier and these steps for not loosing warranty is more helpful..
hi
I uninstall some Sony Apps via Titanium Backup and i think i deleted some important Apps accidentialy.
When i'm trying to reset my device i get an error.
When i'm trying to root my device the screen with the "restore my data" doesn't come any more, so an rooting is not possible.
When i'm trying to install a zip via recovery i get a Error because my SKU seems not to be the same like in the zip.
What can i do?
Thanks!
hmonadjem said:
hi
I uninstall some Sony Apps via Titanium Backup and i think i deleted some important Apps accidentialy.
When i'm trying to reset my device i get an error.
When i'm trying to root my device the screen with the "restore my data" doesn't come any more, so an rooting is not possible.
When i'm trying to install a zip via recovery i get a Error because my SKU seems not to be the same like in the zip.
What can i do?
Thanks!
Click to expand...
Click to collapse
have you applied "rescue-backdoor" before any system modification?
what region is your device?
Hi,
i used your AIO Tool.
I didn't apply anything like rescue-backdoor manually ...
The Device is German (only WiFi) but i changed it to US and changed it back to German ...
This is a part of my build.prop on the device right now:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0R0110
ro.build.display.id=TISU0R0110
ro.build.version.incremental=120803055
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Aug 3 20:53:29 JST 2012
ro.build.date.utc=1343994809
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_017
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SYS_017-user 4.0.3 TISU0R0110 120803055 release-keys
ro.build.fingerprint=Sony/SYS_017/nbx03:4.0.3/TISU0R0110/120803055:user/release-keys
ro.build.characteristics=tablet
I don't know if this can help .... i hope so.
Thanks!
hmonadjem said:
Hi,
i used your AIO Tool.
I didn't apply anything like rescue-backdoor manually ...
The Device is German (only WiFi) but i changed it to US and changed it back to German ...
This is a part of my build.prop on the device right now:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0R0110
ro.build.display.id=TISU0R0110
ro.build.version.incremental=120803055
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Aug 3 20:53:29 JST 2012
ro.build.date.utc=1343994809
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_017
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SYS_017-user 4.0.3 TISU0R0110 120803055 release-keys
ro.build.fingerprint=Sony/SYS_017/nbx03:4.0.3/TISU0R0110/120803055:user/release-keys
ro.build.characteristics=tablet
I don't know if this can help .... i hope so.
Thanks!
Click to expand...
Click to collapse
try this fw via recovery, if it will fail, then there is no way to fix it now.
you will have to wait for R5 to be released - maybe in middle of december
br
condi
Thanks,
i tried it, but it failed.
Is it possible to install the deleted APKs manually?
Thanks!
hmonadjem said:
Thanks,
i tried it, but it failed.
Is it possible to install the deleted APKs manually?
Thanks!
Click to expand...
Click to collapse
if you would have adb shell access - then yes.
Hi,
i have adb shell access very good!
How can i get the apk files? I would download the android 4.0.3 SDK and extract all APKs ... than i would have the most important apps. Is this ok? Or do i have to get the original Sony 4.0.3 Stock APKs?
Thanks!
hmonadjem said:
Hi,
i have adb shell access very good!
How can i get the apk files? I would download the android 4.0.3 SDK and extract all APKs ... than i would have the most important apps. Is this ok? Or do i have to get the original Sony 4.0.3 Stock APKs?
Thanks!
Click to expand...
Click to collapse
gooood DO NOT wipe device! you will loose adb.
ok, so run AiO go to tweaks, use "rescue-backdoor" function.
then use update firmware which I gave you before.
Hi,
but i have no root any more ... because i wiped it yesterday.
hmonadjem said:
Hi,
but i have no root any more ... because i wiped it yesterday.
Click to expand...
Click to collapse
wipe doesnt remove root. so once again - you've got no adb shell access?
Hi,
i had root!
I wiped my device and i got an error from the device itself that this wipe was not completly successfull.
I habe adb access and when i make the command "adb shell" i get access to the shell. But i have no "su" command or something like that. and no superuser app is installed on my device.
hmonadjem said:
Hi,
i had root!
I wiped my device and i got an error from the device itself that this wipe was not completly successfull.
I habe adb access and when i make the command "adb shell" i get access to the shell. But i have no "su" command or something like that. and no superuser app is installed on my device.
Click to expand...
Click to collapse
most probably you've been switched to 2nd system partition.
you could try to make few wipes, it could get back to the 1st,
but after that you will loose adb shell access for sure..
the best way would be wait few days, when new update will be rolled out. info here
br
condi
Hi,
i see there is R5A now out. But the Problem is, when i clock on "Update System" in the Device Settings, my Device Crashes.
I think you are right, it switched to 2nd partition because there is no recovery.log or /tmp. i wiped the device about 10 times.
I have adb shell access but don't know wthat to do now ...
hmonadjem said:
Hi,
i see there is R5A now out. But the Problem is, when i clock on "Update System" in the Device Settings, my Device Crashes.
I think you are right, it switched to 2nd partition because there is no recovery.log or /tmp. i wiped the device about 10 times.
I have adb shell access but don't know wthat to do now ...
Click to expand...
Click to collapse
From the looks of it, it was java.lang.NullPointerException java error due to the system updater is not there anymore.
Sent from my Sony Tablet S using xda premium
Hi,
i don't know, but what can i do now?
Thanks!
hmonadjem said:
Hi,
i don't know, but what can i do now?
Thanks!
Click to expand...
Click to collapse
ok, now update with this firmware, and post results
Worked! Thank you!
1/15/2015 UPDATE: So it looks like I have a few ideas so far ..
* version of SDK does not matter long as its JB +
* the APKs are all basicly the same what I think is tripking me up is wrong or old play store or google servbices , google games,services framework etc ... if you install google games it asks for update then says it can't because the device is not supported ... so i still have the issue with the play store not having jack @#$% on it .. build.prop seems to take no effect too..I still think its more a google issue then Clash of clans APK blocking SDK's etc ...IE CoC is trying to hook google and it dies because of incompat device or wrong versionts of google sdks ...
10:37 PM 12/22/2014 UPDATE: So build.prop seems to have NO ****ING effect on google play store ... I have tried http://apcmag.com/how-to-fake-an-android-device.htm with verious builds and even after time and deleting the userdata-qemu.img userdata.img cache.img / reboot still nothing ...
I have spent about 3 full days now ****ing with this .. and the only thing that still appears to work is bluestacks pile of ****... I have also copied bluestacks build.prop stings and also removed/changed them to match my build and no ****ing effect ... its almost like build.prop is no doing anything I also tried to remove the last part of the build.prop in BS still it works fine so its nothing that I can tell in the 2nd part of build.prop ...
I have go the Market Helper to work and actually install Clash of Clans but the game *****es about needing to be reinstalled ... I got it to work on NON X86 arm build some how ..... but with HAXM I get **** ... maybe my gapps ? gapps-jb-20130812-signed
* I have tried wiping data from playstore
* removed userdata-qemu.img userdata.img cache.img
* rebooted and setup google play and still no Clash of clans or any games for that matter ... its like its not even listing to the build.prop ?
* google plays still says clash of clans is incompatible.
* I also tried "market Helper" with no luck
* I have tried forcing run of from working build on real phone and it works so its build.prop ... or something else...
* not going to use Bluestacks or any other pile of crap like Jarofbeans ( jar of beans has the same @#$ing issue with no games in play store )... see my prev post http://forum.xda-developers.com/chef-central/android/google-play-store-filtering-bypass-wtf-t2927108
* is it more then just build.prop ? IE I have seen some edits to hardware excel etc .. ?
* notes /ref http://www.androidtablets.net/threads/lets-settle-the-google-play-compatible-issue.46327/
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MASTER
ro.build.display.id=cm_ancora_tmo-userdebug 4.1.2 JZO54K eng.camcory.20121126.063112 test-keys
ro.build.version.incremental=495790
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Tue Oct 9 20:03:51 UTC 2012
ro.build.date.utc=1349813031
ro.build.type=eng
ro.build.user=android-build
ro.build.host=vpbs30.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=SGH-T679
ro.product.brand=Samsung
ro.product.name=cm_ancora_tmo
ro.product.device=ancora_tmo
ro.product.board=ancora_tmo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-T679-user 2.3.6 GINGERBREAD UVLE1 release-keys
ro.build.fingerprint=samsung/SGH-T679/SGH-T679:2.3.6/GINGERBREAD/UVLE1:user/release-keys
ro.build.characteristics=default
ro.cm.device=ancora_tmo
# end build properties
#
# system.prop for ancora_tmo
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
So I am the only person with this issue .. BUMP
I found a workaround for now using NOX app player ... but I tried ripping the build.prop from it and it's more then that .. it has dll's and stuff I think its a portable vbox image and some custom dll's etc .. I can't figure it out ... NOX seems a bit China for me but works for testing apps so I dont care too much ..
Hi - so I am only posting as a last result and 4 days of stumbling around rooting, ROMs, and different devices I've finally reached a wall.
I have several LG Aristo 2's that I use on an ESX server for various development machines. They work terrific for what I have them for but the problem is I have particular phones for particular servers and I cannot pick one out of 8 devices because they are all named the same. For the past year or so I have kind of limped but now my environments are a bit more fluid and I need to be able to pick an offending perp out of the line up.
So I have been hacking around on a test phone for the past few days and have driven myself crazy trying to get the model number to change. I have tried several different ROMs, assuming this might be a problem but I just can't seem to change the model name that the devices connects over USB with.
I have updated the build.prop and changed model name, device name, and even added ro.mtp.label and ro.ptp.label.
About to give up thinking this is impossible I had a spare Blu Vivo sitting around and I went through the same process and have been successful in renaming the device doing the things in the line above.
Is this just not possible on the LG Aristo 2?
Android Version: 8.1.0
Model Number: LM-X210MA
Here is a section of my build.prop
Can anyone point me in the right direction? Beer money will be sent!
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OPM1.171019.026
ro.build.display.id=OPM1.171019.026
ro.build.version.incremental=1832618554af2
ro.build.version.sdk=27
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.1.0
ro.build.version.security_patch=2018-11-01
ro.build.version.base_os=
ro.build.date=Thu Nov 22 18:55:26 KST 2018
ro.build.date.utc=1542880526
ro.build.type=user
ro.build.user=jenkins
ro.build.host=LGEACI6R1
ro.build.tags=release-keys
ro.build.flavor=cv1_lao_com-user
ro.build.ab_update=false
ro.product.model=HulkHappy
ro.product.brand=lge
ro.product.name=HulkHappy
ro.product.device=cv1
# 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=LGE
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=cv1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=cv1_lao_com-user 8.1.0 OPM1.171019.026 1832618554af2 release-keys
ro.build.fingerprint=lge/cv1_lao_com/cv1:8.1.0/OPM1.171019.026/1832618554af2:user/release-keys
ro.build.characteristics=default
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=QC_Reference_Phone
ro.board.platform=msm8937
ro.vendor.product.manufacturer=LGE
ro.vendor.product.model=LM-X210
ro.vendor.product.brand=lge
ro.vendor.product.name=cv1_lao_com
ro.vendor.product.device=cv1
ro.ptp.label=HulkHappy
ro.mtp.label=HulkHappy
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
@jwoegerbauer
Awesome, thank you for the information. I had been using a version of the first one and it did not get me as far along as what you just shared. So using
Code:
adb shell settings put secure global device_name "device name"
I have now at least been able to differentiate on the direct server what device is connected. In my ESX host it still shows the Model LG LM-X210G. I'd share some images but I guess my n00b status, rightly so, won't allow that.
But using my eyes:
ESX shows the USB device as: LG LM-X210G
Easy Tether shows the devices as: LMX210G1db3... (stripping the rest, but guessing its part of the serial)
Windows shows the device as: HulkHappy
... since HulkSmash destroyed the first phone I was trying this on.
Is there any where else I can look? My biggest desire is to get my ESX host in line.
jwoegerbauer said:
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
Click to expand...
Click to collapse
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.