Hi, guys so I unlocked my bootloader today and downloaded Xiaomi.eu for Mi 11i/ Redmi K40 Pro+ which are the same as Mi 11X Pro. I am using a fastboot ROM, so I clicked on install with data format which was supposed to install the ROM for the device but nothing happened. Can anyone who already has flashed Xiaomi.eu on Mi 11X Pro (Haydnin) tell me how to flash it?
Just extract the fastboot rom, change haydn to haydnin in windows_fastboot_first_install_with_data_format.bat in notepad and install via cmd.
puskalregmi9 said:
Just extract the fastboot rom, change haydn to haydnin in windows_fastboot_first_install_with_data_format.bat in notepad and install via cmd.
Click to expand...
Click to collapse
Yeah, yesterday while searching for answers I found that and installed Xiaomi.eu but due to some reason in Xiaomi.eu my device heats a lot especially while gaming the temperature gets too high. Also the battery performance is very poor in Xiaomi.eu. Do you have any idea on how to fix this?
puskalregmi9 said:
Just extract the fastboot rom, change haydn to haydnin in windows_fastboot_first_install_with_data_format.bat in notepad and install via cmd.
Click to expand...
Click to collapse
termination5646 said:
Yeah, yesterday while searching for answers I found that and installed Xiaomi.eu but due to some reason in Xiaomi.eu my device heats a lot especially while gaming the temperature gets too high. Also the battery performance is very poor in Xiaomi.eu. Do you have any idea on how to fix this?
Click to expand...
Click to collapse
you have to remove nfc via abd.
How do I remove it?
puskalregmi9 said:
you have to remove nfc via abd.
Click to expand...
Click to collapse
Thanks that worked!
termination5646 said:
Thanks that worked!
Click to expand...
Click to collapse
Dude how to uninstall this nfc thing. I flashed Xiaomi eu rom yesterday on my mi 11x pro now it's heating on pubg and battery not that good like on previous Indian original rom that comes with device.
Please help me.
I did adb Shell with package uninstall commands but that didn't works. Showing error.
Please guide me.
I installed this rom for mi dialer and messaging app nd i dont want to change this rom.
Enable USB debugging and remove three packages via adb that are-
1) com.android.nfc
2) com.android.apps.tag
3) com.miui.nextpay (Reboot after removing these)
•Also give the device a few hours after doing this then everything will be fine. For me it took 2 hours for the overheating to stop and the performance to get to the right level.
While
termination5646 said:
Enable USB debugging and remove three packages via adb that are-
1) com.android.nfc
2) com.android.apps.tag
3) com.miui.nextpay (Reboot after removing these)
•Also give the device a few hours after doing this then everything will be fine. For me it took 2 hours for the overheating to stop and the performance to get to the right level.
Click to expand...
Click to collapse
While uninsalling package adb showing error of Failed 0 internal error!
Devices drivers properly installed.
Device name shows after typing faatboot devices.
Everything is fine but can't unistall nfc by adb.
anulovely said:
While
While uninsalling package adb showing error of Failed 0 internal error!
Devices drivers properly installed.
Device name shows after typing faatboot devices.
Everything is fine but can't unistall nfc by adb.
Click to expand...
Click to collapse
Factory reset once or just reflash the rom and try again.
termination5646 said:
Factory reset once or just reflash the rom and try again.
Click to expand...
Click to collapse
Tried 3 times already. Will try again on Chinese rom.
anulovely said:
Tried 3 times already. Will try again on Chinese rom.
Click to expand...
Click to collapse
Try a different cable and install adb driver from https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
Then, reboot the pc and open cmd and type
adb shell pm uninstall -k --user 0 com.android.nfc
adb shell pm uninstall -k --user 0 com.miui.nextpay
adb shell pm uninstall -k --user 0 com.android.apps.tag
termination5646 said:
Try a different cable and install adb driver from https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
Then, reboot the pc and open cmd and type
adb shell pm uninstall -k --user 0 com.android.nfc
adb shell pm uninstall -k --user 0 com.miui.nextpay
adb shell pm uninstall -k --user 0 com.android.apps.tag
Click to expand...
Click to collapse
Thanks a Lot!!
Everything now working fine on eu rom.
No heating no battery drain.
Thanks again.
But im curious to know that why nfc, nextpay, apps.tag apps making device heat n battery drain like hell.
I think its because the device doesn't have NFC.
I wanted to know which version of Xiaomi.eu are you using Stable or Beta. Also I noticed that the device didn't overheat after removing NFC but still ran hotter than Global MIUI. Is the same happening with you too?
Yeah its runs hotter ,i tried so many custom roms for 11x pro ,now again im here on stock , nothing beats stock , but i found a good improvement on sot in aosp roms, but the imagereproduction and display colours ,i like it on miui the most , but here in .eu i think its not pretty well optimised for 11 xpro ,well stock is all better now
Related
Hello, I updated my redmi note 3 to The 6.9.9 stable version:fingers-crossed:. But as there as many bugs, I tried to rollback to the previous version:silly:. But I'm now stuck on Bootloop:crying::crying:. Help me plz. ADB is not enabled, bootloader is locked & the phone is not rooted.
Use EDL mode. Search it in Google (MIUI Forum).
is EDL also used to get completly stock? i might sell my kenzo to buy a kate ... and i would like to sell with official global stable
EDL is used if your device bootloader is not unlocked.. The fastboot method is for unlocked bootloader only.. Yes, completely stock
Sorry, i should have posted whats my device status:
1. flashed global dev rom via EDL mode
2. updated to MIUI 6.9.9 6.0.1 MM
3. unlocked bootloader officialy with xiaomi tool
4. flashed ALKA TWRP
5. Did a wipe because phone encryption was on, after wipe i was able to backup all partitions
6. flashed Supersu
Now if i want to go completly stock, do i have to flash latest MIUI rom via fastboot instead of EDL?
Then everything is back to stock, even the Bootloader is locked?
It's up to you, it's same.. EDL should be fine
---------- Post added at 03:07 PM ---------- Previous post was at 03:01 PM ----------
Go flash it via fastboot
Tyuzva said:
Use EDL mode. Search it in Google (MIUI Forum).
Click to expand...
Click to collapse
EDL isn't working... While updating it stucks on 25% & says.. Not enough space.. Although the phone is empty
Da_SilentKnight said:
EDL isn't working... While updating it stucks on 25% & says.. Not enough space.. Although the phone is empty
Click to expand...
Click to collapse
Your Windows is 32Bits? If yes, use latest MiFlash tool. And check if file folder has no spaces like this C:\Users\Name\Desktop\Redmi Note\
If has space, remove all spaces. Put ROM in C:\ROM folder for example...
Da_SilentKnight said:
EDL isn't working... While updating it stucks on 25% & says.. Not enough space.. Although the phone is empty
Click to expand...
Click to collapse
use new version of mi flash tool
http://en.miui.com/thread-281979-1-1.html (i am using it)
and fastboot edl
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
and ya plz do not make log dict.
e.g D:/xyz/xyz/ahs/zhahd/fastboot rom
do like this
D:/fasboot rom
32 bit, use MiFlash beta
Tyuzva said:
32 bit, use MiFlash beta
Click to expand...
Click to collapse
It working well with windows 10 64bit without any error
Unlike old version show error
andersonaragao said:
Your Windows is 32Bits? If yes, use latest MiFlash tool. And check if file folder has no spaces like this C:\Users\Name\Desktop\Redmi Note\
If has space, remove all spaces. Put ROM in C:\ROM folder for example...
Click to expand...
Click to collapse
android_smater said:
use new version of mi flash tool
http://en.miui.com/thread-281979-1-1.html (i am using it)
and fastboot edl
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
and ya plz do not make log dict.
e.g D:/xyz/xyz/ahs/zhahd/fastboot rom
do like this
D:/fasboot rom
Click to expand...
Click to collapse
Thanks guys... My problem is solved.
Da_SilentKnight said:
Thanks guys... My problem is solved. ?
Click to expand...
Click to collapse
are you asking or telling
I DIDN'T DO THIS
Thanks to @TheDevFreak for the download link
I put it here so we can find it faster.
Here's the TWRP 3.0 version that supports SquashFS filesystem to avoid the error
Code:
NO OS INSTALLED
bootlooping when flashing Wear 2.0 ROM
Download:
-attached to this post-
http://www.mediafire.com/file/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
https://mega.nz/#!AB9BnBjC!GRVW_eLtPRezC_Jxvw9-FBn80meeZkXRemdUfukZmpE
flash it on fastboot
Code:
Fastboot flash recovery twrp-3.0.0-0-dory+squashfs.img
I dont get do you mean that it will work with AW 2.0 or is it a bug ?
I have permanent bootloop. I've already flashed my LG G Watch few times and still no luck. Do you have any advice how to boot?
[edit]
If you have permanent bootloop after factory reset of AW2, you have to reflash your watch with Mysterious Magic than update to 6.0.1 with OTA and then reflash to AW2.
I'm confused, TWRP is still reporting that there is no OS with my watch flashed to AW 2.0
ShapeShifter499 said:
I'm confused, TWRP is still reporting that there is no OS with my watch flashed to AW 2.0
Click to expand...
Click to collapse
Ignore this, that's a known bug...
It will work nonetheless
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Ignore this, that's a known bug...
It will work nonetheless
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Is it safe to try to root AW 2.0 with this version of TWRP? I only want to root in order to increase the vibration time for notifications.
ShapeShifter499 said:
Is it safe to try to root AW 2.0 with this version of TWRP? I only want to root in order to increase the vibration time for notifications.
Click to expand...
Click to collapse
Yeah, it flashes latest magisk (even beta) just fine...
You can adb install kernel adiutor to regulate vibration
You theoretically could also use SuperSU in systemless mode, imported is that changes to system won't work as the system file system (squashfs) is read only, it cannot be modified but this does not matter with systemless solutions like magisk as it only patches the kernel (hence systemless)
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Yeah, it flashes latest magisk (even beta) just fine...
You can adb install kernel adiutor to regulate vibration
You theoretically could also use SuperSU in systemless mode, imported is that changes to system won't work as the system file system (squashfs) is read only, it cannot be modified but this does not matter with systemless solutions like magisk as it only patches the kernel (hence systemless)
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'll try running magisk. I didn't even think magisk would work on AW. Also thanks for pointing out kernel adiutor.
Sam Nakamura said:
Yeah, it flashes latest magisk (even beta) just fine...
You can adb install kernel adiutor to regulate vibration
You theoretically could also use SuperSU in systemless mode, imported is that changes to system won't work as the system file system (squashfs) is read only, it cannot be modified but this does not matter with systemless solutions like magisk as it only patches the kernel (hence systemless)
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
which version of adiutor are you using, it displays much to big to navigate anything
ShapeShifter499 said:
which version of adiutor are you using, it displays much to big to navigate anything
Click to expand...
Click to collapse
You'll need to set a custom screen density
Code:
adb shell vm density 180
Default density is 240p, you can play a little what suits you best but I'm comfortable with 180 and all apps so far ran flawlessly, this command will keep the custom screen resolution across reboots, keep this in mind but as long as you can boot to bootloader you can change this to default or your liking, of course you'll need to reboot to take effect (in case you just use adb while watch is booted)
Sent from my OnePlus 3T using XDA Labs
Deleted
after selecting system reset to pair with another phone i'm stuck in a boot loop, where i get to twrp recovery no matter what i do. any idea what to do? thanks.
Jaocagomez said:
I DIDN'T DO THIS
Thanks to @TheDevFreak for the download link
I put it here so we can find it faster.
Here's the TWRP 3.0 version that supports SquashFS filesystem to avoid the error
Code:
NO OS INSTALLED
bootlooping when flashing Wear 2.0 ROM
Download:
-attached to this post-
http://www.mediafire.com/file/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
https://mega.nz/#!AB9BnBjC!GRVW_eLtPRezC_Jxvw9-FBn80meeZkXRemdUfukZmpE
flash it on fastboot
Code:
Fastboot flash recovery twrp-3.0.0-0-dory+squashfs.img
Click to expand...
Click to collapse
Hi, i have created a twrp for a pioneer tablet, but it has squashfs like your watch, do you know where can I contact to help me fix this like your twrp?
This recovery does not work anymore with the latest ota from 2017 on my lg g watch r:
NWS2.170620.003
I used the latest official image and following commands to backup my factory image:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
exit
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
also the image should be available here: https://forum.xda-developers.com/t/...003-fastboot-twrp-zip-factory-images.3405311/
madejackson said:
This recovery does not work anymore with the latest ota from 2017 on my lg g watch r:
NWS2.170620.003
I used the latest official image and following commands to backup my factory image:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
exit
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
also the image should be available here: https://forum.xda-developers.com/t/...003-fastboot-twrp-zip-factory-images.3405311/
Click to expand...
Click to collapse
You are looking in the wrong place for the TWRP recovery, this is for the LG G watch w100.
I believe you were instead looking for this: https://forum.xda-developers.com/t/recovery-lenok-twrp-3-1-1-0-touch-recovery-2017-05-19.3001890/
Have a good one!
Hi,
I don't think my phone model is so important for this question, but for completeness:
Phone: Xiaomi Mi5
ROM: MIUI International developer ROM 6.9.1
Other details: Bootloader unlocked, rooted, TWRP installed, Fastboot enabled, BUT USB debugging disabled.
So, my phone suddenly started silently installing the Facebook app (and reinstalling it on every reboot), so for reasons of stupidity I used the app Elixir 2 to disable my Packageinstaller system app. Unfortunately, this caused the phone to be unable to complete boot (maybe it tries to install on boot, then hangs because the installer app cannot respond?), leaving it with just the manufacturer logo on the screen.
I know that I could just wipe and reinstall, but I think that I could salvage this install (and all my settings) if I could just re-enable the packageinstaller system app.
Unfortunately, adb doesn't recognise the phone when hung on the bootloop or in fastboot mode (probably because USB debugging mode is disabled), and while adb does recognise the device in TWRP recovery, it will not accept packagemanager (pm) commands to enable packageinstaller. Also unfortunately, the TWRP terminal cannot run pm commands.
So... Does anyone have any suggestions for how to re-enable an app when USB debugging is disabled? Is there a file I could add or delete using the simple file manager in TWRP that could do this? Any suggestions appreciated.
Dirty Flash the ROM for now
Download+Flash "Unfreeze_all_apps_New.zip" from here https://forum.xda-developers.com/showpost.php?p=46437840&postcount=12 :good:
---------- Post added at 09:00 AM ---------- Previous post was at 08:54 AM ----------
Atopian said:
Hi,
I don't think my phone model is so important for this question, but for completeness:
Phone: Xiaomi Mi5
ROM: MIUI International developer ROM 6.9.1
Other details: Bootloader unlocked, rooted, TWRP installed, Fastboot enabled, BUT USB debugging disabled.
So, my phone suddenly started silently installing the Facebook app (and reinstalling it on every reboot), so for reasons of stupidity I used the app Elixir 2 to disable my Packageinstaller system app. Unfortunately, this caused the phone to be unable to complete boot (maybe it tries to install on boot, then hangs because the installer app cannot respond?), leaving it with just the manufacturer logo on the screen.
I know that I could just wipe and reinstall, but I think that I could salvage this install (and all my settings) if I could just re-enable the packageinstaller system app.
Unfortunately, adb doesn't recognise the phone when hung on the bootloop or in fastboot mode (probably because USB debugging mode is disabled), and while adb does recognise the device in TWRP recovery, it will not accept packagemanager (pm) commands to enable packageinstaller. Also unfortunately, the TWRP terminal cannot run pm commands.
So... Does anyone have any suggestions for how to re-enable an app when USB debugging is disabled? Is there a file I could add or delete using the simple file manager in TWRP that could do this? Any suggestions appreciated.
Click to expand...
Click to collapse
Also from TWRP go to Advanced>File Manager and navigate to /data/data and find a folder that contains "elixir" in its name (ex. com.xxx.elixir2) and delete it.
George Malas said:
Download+Flash "Unfreeze_all_apps_New.zip" from here https://forum.xda-developers.com/showpost.php?p=46437840&postcount=12 :good:
---------- Post added at 09:00 AM ---------- Previous post was at 08:54 AM ----------
Also from TWRP go to Advanced>File Manager and navigate to /data/data and find a folder that contains "elixir" in its name (ex. com.xxx.elixir2) and delete it.
Click to expand...
Click to collapse
Thank you very much! The zips worked well, and saved me hours of getting my phone back to my preferred setup after a reset.
Atopian said:
Thank you very much! The zips worked well, and saved me hours of getting my phone back to my preferred setup after a reset.
Click to expand...
Click to collapse
No problem dude. Glad I helped you ?
I just used BK package disabler. It works just fine
Sent from my SM-G950U using XDA-Developers Legacy app
Someone has already rooted the device
I tried to download all the files it mentioned .
but still I was stuck by the TWRP flashing process
because this device is using A/B partition way not same as the other android devices.
:cyclops: **** i cant send the website link
happywhd said:
Someone has already rooted the device
I tried to download all the files it mentioned .
but still I was stuck by the TWRP flashing process
because this device is using A/B partition way not same as the other android devices.
:cyclops: **** i cant send the website link
Click to expand...
Click to collapse
I am not aware of a TWRP compiled for our device yet that you can flash. If you are interested in doing it follow this guide: https://forum.xda-developers.com/showthread.php?t=1943625
happywhd said:
Someone has already rooted the device
I tried to download all the files it mentioned .
but still I was stuck by the TWRP flashing process
because this device is using A/B partition way not same as the other android devices.
:cyclops: **** i cant send the website link
Click to expand...
Click to collapse
fastboot flash boot xxxx.img
worked for me.
Max4D said:
fastboot flash boot xxxx.img
worked for me.
Click to expand...
Click to collapse
where did you get the img file?
Marco589 said:
where did you get the img file?
Click to expand...
Click to collapse
Asus forums
sorry i can't post links yet
Shakalaca has uploaded TWRP images to Mega
https(colonslashslash)wwwv(dot)asus(dot)com(slash)zentalk(slash)tw(slash)thread-362963-1-1(dot)html
https(colonslashslash)mega(dot)nz(slash)#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
Max4D said:
Asus forums
sorry i can't post links yet
Shakalaca has uploaded TWRP images to Mega
https(colonslashslash)wwwv(dot)asus(dot)com(slash)zentalk(slash)tw(slash)thread-362963-1-1(dot)html
https(colonslashslash)mega(dot)nz(slash)#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
Click to expand...
Click to collapse
TWRP
https://mega.nz/#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
I think Magisk causes bootloop. I believe there is a modded version, but I don't have a link.
Edit: I found post about Magisk - https://forum.xda-developers.com/showpost.php?p=78003101&postcount=14
Tesla74 said:
TWRP
I think Magisk causes bootloop. I believe there is a modded version, but I don't have a link.
Click to expand...
Click to collapse
You can download the modded version from Shakalaca's custom Magisk channel
ＨＴＴＰＳ://bit.ly/2NGVKqS
Max4D said:
You can download the modded version from Shakalaca's custom Magisk channel
ＨＴＴＰＳ://bit.ly/2NGVKqS
Click to expand...
Click to collapse
https://bit.ly/2NGVKqS
Thanks
If anyone is looking for fastboot:
https://devsjournal.com/download-minimal-adb-fastboot-tool.html
Max4D said:
fastboot flash boot xxxx.img
worked for me.
Click to expand...
Click to collapse
Ballanda can't get fastboot to work: https://forum.xda-developers.com/rog-phone/how-to/rog-phone-recognized-pc-fastboot-mode-t3860453
Tesla74 said:
Ballanda can't get fastboot to work: https://forum.xda-developers.com/rog-phone/how-to/rog-phone-recognized-pc-fastboot-mode-t3860453
Click to expand...
Click to collapse
I didn't install any drivers manually.
Just connected my phone to a Win 10 PC.
As for fastboot I just used my usual environment.
Has been a while so unfortunately I don't remember precisely, but I think I got it from Android SDK.
I've used the same environment to root my Zenfone 3 Deluxe before, if that makes any difference.
P.S.
Rashad83 says it doesn't return devices but can execute the command.
I've flashed TWRP but didn't use the fastboot devices command(I could try when I get home) so that might be the case.
Max4D said:
You can download the modded version from Shakalaca's custom Magisk channel
ＨＴＴＰＳ://bit.ly/2NGVKqS
Click to expand...
Click to collapse
Can you explain what to do with the json file?
Marco589 said:
Can you explain what to do with the json file?
Click to expand...
Click to collapse
The URL is for the Magisk channel
Install Normal Magisk Manager apk.
Set channel to custom, type in the URL.
Download Custom Magisk Manager.
Uninstall Normal Manager
Install custom Manager.
DL(from the channel)&install custom Magisk directly with Manager.
Max4D said:
The URL is for the Magisk channel
Install Normal Magisk Manager apk.
Set channel to custom, type in the URL.
Download Custom Magisk Manager.
Uninstall Normal Manager
Install custom Manager.
DL(from the channel)&install custom Magisk directly with Manager.
Click to expand...
Click to collapse
Thanks a lot!
All in all to root the phone:
Unlock bootloader
Flash twrp
And install magisk as you said
Right?
Marco589 said:
Thanks a lot!
All in all to root the phone:
Unlock bootloader
Flash twrp
And install magisk as you said
Right?
Click to expand...
Click to collapse
That's right.
Although in hindsight,twrp might not be necessary if u just want root, but I did it in that order.
(Was thinking of posting a guide, but since I can't post direct links yet, hopefully someone who can would
I tried 3 different cables on 8 different USB ports on 3 different Windows 10 machines, and I cannot get the phone to flash TWRP. I tried FASTBOOT DEVICES and nothing comes up. Regardless, I still tried to FASTBOOT FLASH RECOVERY TWRP.IMG, and all I get is <waiting for device>. All my other phones work fine, and I do have all of the necessary drivers installed.
Is there a way I can sideload or flash Magisk via ADB, since I can use that? I can live without TWRP.
Max4D said:
That's right.
Although in hindsight,twrp might not be necessary if u just want root, but I did it in that order.
(Was thinking of posting a guide, but since I can't post direct links yet, hopefully someone who can would
Click to expand...
Click to collapse
Great!
As soon as I receive my rog (as It got lost just right after the shipping) , I'll do It ?
I hope you guys having fastboot issues are using the official Android Studio and not the minimal adb or any other version.
Max4D said:
The URL is for the Magisk channel
Install Normal Magisk Manager apk.
Set channel to custom, type in the URL.
Download Custom Magisk Manager.
Uninstall Normal Manager
Install custom Manager.
DL(from the channel)&install custom Magisk directly with Manager.
Click to expand...
Click to collapse
Here is a direct link to the custom Magisk Manager to save a few steps:
https://www.dropbox.com/s/c8fm2ka60cmlvi6/MagiskManager-6.0.2-20181010.apk?dl=1
---------- Post added at 05:30 PM ---------- Previous post was at 05:25 PM ----------
kgptzac said:
I hope you guys having fastboot issues are using the official Android Studio and not the minimal adb or any other version.
Click to expand...
Click to collapse
https://developer.android.com/studio/
kgptzac said:
I hope you guys having fastboot issues are using the official Android Studio and not the minimal adb or any other version.
Click to expand...
Click to collapse
I tried Minimal ADB and Fastboot. ADB connects fine, Fastboot does not.
I tried the Android platform tools version of ADB and Fastboot. I 'm pretty sure that is the same thing that installs with Android Studio. ADB connects fine, Fastboot does not.
Just for fun, I did the 2 GB download and tried the full blown Android Studio version of ADB and Fastboot. Strike three.
So, same results no matter what I do. I can interact through ADB, but not Fastboot on the ROG phone. When I try to issue a Fastboot command while the phone is in Fastboot mode, all I get is "Waiting for any device".
It's never been this hard with any of the 6 devices I've owned and rooted. I am wondering if I should flash the stock firmware and start over. So far all I've done is unlock the bootloader using the ASUS unlock tool APK.
ballanda said:
I tried Minimal ADB and Fastboot. ADB connects fine, Fastboot does not.
I tried the Android platform tools version of ADB and Fastboot. I 'm pretty sure that is the same thing that installs with Android Studio. ADB connects fine, Fastboot does not.
Just for fun, I did the 2 GB download and tried the full blown Android Studio version of ADB and Fastboot. Strike three.
So, same results no matter what I do. I can interact through ADB, but not Fastboot on the ROG phone. When I try to issue a Fastboot command while the phone is in Fastboot mode, all I get is "Waiting for any device".
It's never been this hard with any of the 6 devices I've owned and rooted. I am wondering if I should flash the stock firmware and start over. So far all I've done is unlock the bootloader using the ASUS unlock tool APK.
Click to expand...
Click to collapse
What region is your phone? Maybe some region roms have fastboot disabled?
What would i Do after Unlocking Bootloader?
Please provide Required file Links
Thanks in Advance
Bump :fingers-crossed:
@blanksh07
To root Android unlocking device's boot-loader is NOT needed: You always can obtain a temporary root by patching adbd.
0
The above link didn't worked for rooting.
Anyone else tell me how to root this device or how to add it to xda device list?
@blanksh07
The Oppo K3 is based on Android 9, hence I think it has dm-verity/AVB enabled by default. As long as this lock isn't got disabled NOTHING will work as expected.
@jwoegerbauer
How can I disable this and is there any twrp available for this phone so I can flash magisk..!?
blanksh07 said:
@jwoegerbauer
How can I disable this and is there any twrp available for this phone so I can flash magisk..!?
Click to expand...
Click to collapse
1.
Code:
adb devices
adb disable-verity
adb reboot
2.
I never installed TWRP nor Magisk in order to root a phone. Yes, this may in the end lead to a positive result, but is in my opinion an unnecessary overkill with regards to get installed 1 ( ONE ) binary in Android - the su binary what is ~100 KB of size.
BTW: You compile TWRP by yourself. How-to is described here.
1. I have tried above abd commands and got an erro "verity cannot be disabled/enabled - USER build".
2. When I try to reboot to bootloader, the fastboot screen flash for 2 seconds and rebooted to system , any help with that?
you can see tutorial in here.
https://www.getdroidtips.com/root-oppo-k3/
0
No luck!