Hello,
I hope I am in the right category here.
I bought a Xiaomi Mi 11 (12GB / 256GB) with Chinese firmware and now I want to install the Xiaomi EU Rom.
Bootloader is already unlocked, OEM unlock and USB debugging are also set correctly.
Now I have the following problem:
In normal FASTBOOT mode (volume key down + power button) the Mi 11 is not recognized by Minimal ADB & Fastboot. I have already installed all possible drivers.
ADB recognizes my device and when I write there adb reboot fastboot my Mi 11 boots in FASTBOOTD. There it is also recognized by Minimal ADB & Fastboot, however when I flash TWRP I get the following error:
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (129320 KB)...
OKAY [ 2.824s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.832s
Why is my Mi 11 not recognized in normal FASTBOOT or why can't I flash TWRP in FASTBOOTD?
I hope that someone can help me. Thanks a lot!
Mi 11 is delivered with Android R. So it's using Virtual A/B slot and there's no more recovery partition. Use
Code:
fastboot boot image.img
To get into twrp and then do what you want.
For more about Virtual A/B: Overview of Virtual A/B
Raymond.William said:
Mi 11 is delivered with Android R. So it's using Virtual A/B slot and there's no more recovery partition. Use
Code:
fastboot boot image.img
To get into twrp and then do what you want.
For more about Virtual A/B: Overview of Virtual A/B
Click to expand...
Click to collapse
Unfortunately I get this message:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.828s]
booting...
FAILED (remote: Unrecognized command boot)
finished. total time: 2.828s
When I type in ADB adb reboot fastboot my Mi 11 boots in FASTBOOTD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In FASTBOOTD my Mi 11 is recognized by Minimal ADB & Fastboot, however I get these errors when I want to flash/boot TWRP.
I get into FASTBOOT with the Volume Down button and the Power button, but my Mi 11 is not recognized there by Minimal ADB & Fastboot. I have already installed all possible drivers.
Did you checked the device manager in your PC?
Sometimes it needs you manually define which driver should system use for this device.
afaik it should use "Android bootloader interface" driver.
jere2611 said:
Unfortunately I get this message:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.828s]
booting...
FAILED (remote: Unrecognized command boot)
finished. total time: 2.828s
When I type in ADB adb reboot fastboot my Mi 11 boots in FASTBOOTD.
View attachment 5366873
In FASTBOOTD my Mi 11 is recognized by Minimal ADB & Fastboot, however I get these errors when I want to flash/boot TWRP.
View attachment 5366875
I get into FASTBOOT with the Volume Down button and the Power button, but my Mi 11 is not recognized there by Minimal ADB & Fastboot. I have already installed all possible drivers.
Click to expand...
Click to collapse
you only want to boot TWRP right ?
then you dont need FASTBOOTD
just use regular FASTBOOT
FASTBOOTD only for flashing GSI
dont use minimal adb
search in google platform tools for updated adb
Raymond.William said:
afaik it should use "Android bootloader interface" driver.
Click to expand...
Click to collapse
I did that as you can see in the attachments. Unfortunately fastboot does not recognize my device at all. I tried several Xiaomi oder Google drivers. Moreover it says that "The specified request is not a valid operation for the target device.". And yes, I booted Windows without driver signatures.
kmzway000 said:
dont use minimal adb
search in google platform tools for updated adb
Click to expand...
Click to collapse
I tried platform tools as well, but the same problems :/
jere2611 said:
I did that as you can see in the attachments. Unfortunately fastboot does not recognize my device at all. I tried several Xiaomi oder Google drivers. Moreover it says that "The specified request is not a valid operation for the target device.". And yes, I booted Windows without driver signatures.
View attachment 5367399View attachment 5367401
I tried platform tools as well, but the same problems :/
Click to expand...
Click to collapse
I always use the Minimal ADB tools myself and everything works smoothly. I would uninstall the driver, connect the Mi 11 to a different USB port, preferably not a hub, and reinstall the driver (or have it installed).Then it should actually work.
pittrich said:
I always use the Minimal ADB tools myself and everything works smoothly. I would uninstall the driver, connect the Mi 11 to a different USB port, preferably not a hub, and reinstall the driver (or have it installed).Then it should actually work.
Click to expand...
Click to collapse
In the past, I have not had any bad experiences with Minimal ADB & Fastboot either. I was able to flash TWRP on my Lenovo Z6 Pro and OnePlus 6T without any problems.
However, I have problems with the Mi 11. I have uninstalled all drivers - no success on the new attempt. I even used another PC. As soon as I am in FASTBOOT (not FASTBOOTD), my Mi 11 is simply not recognized.
jere2611 said:
In the past, I have not had any bad experiences with Minimal ADB & Fastboot either. I was able to flash TWRP on my Lenovo Z6 Pro and OnePlus 6T without any problems.
However, I have problems with the Mi 11. I have uninstalled all drivers - no success on the new attempt. I even used another PC. As soon as I am in FASTBOOT (not FASTBOOTD), my Mi 11 is simply not recognized.
Click to expand...
Click to collapse
My experiences are similar to yours. In addition to Pixel devices, I've also unlocked OnePlus, Samsung and Huawei devices. My first Mi 11 worked right from the start. Unfortunately it broke and I got a brand new replacement device. Initially, this was not recognized at all on the USB port. Not even after turning on USB debugging. Only in fastboot mode. So I just completely reset it. Now it is shown as unauthorized in ADB mode and correct in Fastboot. Unfortunately I have to wait until August 1st to unlock it. So my tip is to reset the Mi 11 and start over. Maybe it helps
@jere2611 you can try to delete old drivers with USB Deview, and then try installing Universal ADB Drivers.
pittrich said:
My experiences are similar to yours. In addition to Pixel devices, I've also unlocked OnePlus, Samsung and Huawei devices. My first Mi 11 worked right from the start. Unfortunately it broke and I got a brand new replacement device. Initially, this was not recognized at all on the USB port. Not even after turning on USB debugging. Only in fastboot mode. So I just completely reset it. Now it is shown as unauthorized in ADB mode and correct in Fastboot. Unfortunately I have to wait until August 1st to unlock it. So my tip is to reset the Mi 11 and start over. Maybe it helps
Click to expand...
Click to collapse
For me, unfortunately, it's the other way round. I have now also reset my Mi 11 to factory settings. Unfortunately, the problem is still the same. MiFlash etc. no longer recognise the device as soon as it is in fastboot.
b0nebreaker said:
@jere2611 you can try to delete old drivers with USB Deview, and then try installing Universal ADB Drivers.
Click to expand...
Click to collapse
I have done that once now. Unfortunately, it still has no effect.
jere2611 said:
For me, unfortunately, it's the other way round. I have now also reset my Mi 11 to factory settings. Unfortunately, the problem is still the same. MiFlash etc. no longer recognise the device as soon as it is in fastboot.
I have done that once now. Unfortunately, it still has no effect.
Click to expand...
Click to collapse
jere2611 said:
For me, unfortunately, it's the other way round. I have now also reset my Mi 11 to factory settings. Unfortunately, the problem is still the same. MiFlash etc. no longer recognise the device as soon as it is in fastboot.
I have done that once now. Unfortunately, it still has no effect.
Click to expand...
Click to collapse
Which MIUI version is installed?
pittrich said:
Which MIUI version is installed?
Click to expand...
Click to collapse
Unfortunately MIUI 12.04 Global 12.0.4 Stable - RKBEUOR. The device is from Trading Shenzen with Unlocked Bootloader. But this Rom does not receive any Updates.
jere2611 said:
Unfortunately MIUI 12.04 Global 12.0.4 Stable - RKBEUOR. The device is from Trading Shenzen with Unlocked Bootloader. But this Rom does not receive any Updates.
Click to expand...
Click to collapse
Then Trading Shenzhen seems to have installed the Global ROM via Fastboot. Updates should then actually be possible. Have you already contacted Trading Shenzhen?They should actually be able to / have to help you.
pittrich said:
Then Trading Shenzhen seems to have installed the Global ROM via Fastboot. Updates should then actually be possible. Have you already contacted Trading Shenzhen?They should actually be able to / have to help you.
Click to expand...
Click to collapse
There are also OTA updates. However, this is a Rom from the provider Orange, which has not yet released a newer update. Therefore, I would now like to switch to the EU Rom myself.
jere2611 said:
There are also OTA updates. However, this is a Rom from the provider Orange, which has not yet released a newer update. Therefore, I would now like to switch to the EU Rom myself.
Click to expand...
Click to collapse
And trading Shenzhen? What do they say?
pittrich said:
And trading Shenzhen? What do they say?
Click to expand...
Click to collapse
At the time of the order, the EU Rom was not yet available, so the orange variant was chosen to ensure the German language. What I do with the device now is my business.
jere2611 said:
At the time of the order, the EU Rom was not yet available, so the orange variant was chosen to ensure the German language. What I do with the device now is my business.
Click to expand...
Click to collapse
Es geht nicht darum, welche ROM Trading Shenzhen installiert hat, sondern was die Fastboot Problematik angeht.
Wenn du Treiber neu installiert und auch einen anderen USB Port ausprobiert hast, eventuell sogar einen anderen Rechner benutzt hast, muss das Problem ja am Handy mit genau dieser ROM selbst liegen
Ich vermute mal, dass du auch andere USB Kabel probiert hast? Mein original Xiaomi Kabel zB hat nicht funktioniert.
----------
MOD EDIT: English Translation Below
It's not about which ROM Trading Shenzhen has installed, but about the Fastboot problem.
If you have reinstalled drivers and tried a different USB port, possibly even used a different computer, the problem must be with the mobile phone with exactly this ROM itself
I guess you tried other USB cables too? My original Xiaomi cable, for example, did not work.
pittrich said:
Es geht nicht darum, welche ROM Trading Shenzhen installiert hat, sondern was die Fastboot Problematik angeht.
Wenn du Treiber neu installiert und auch einen anderen USB Port ausprobiert hast, eventuell sogar einen anderen Rechner benutzt hast, muss das Problem ja am Handy mit genau dieser ROM selbst liegen
Ich vermute mal, dass du auch andere USB Kabel probiert hast? Mein original Xiaomi Kabel zB hat nicht funktioniert.
----------
MOD EDIT: English Translation Below
It's not about which ROM Trading Shenzhen has installed, but about the Fastboot problem.
If you have reinstalled drivers and tried a different USB port, possibly even used a different computer, the problem must be with the mobile phone with exactly this ROM itself
I guess you tried other USB cables too? My original Xiaomi cable, for example, did not work.
Click to expand...
Click to collapse
Dann werde ich mich wohl nochmal an die wenden... Tatsächlich habe ich mehrere USB-Kabel probiert, da ich bei einem anderen Beitrag schonmal gelesen hab, dass das mitgelieferte nicht ging.
----------
MOD EDIT: English Translation Below
Then I would probably turn to them again ... In fact, I tried several USB cables, because I read in another post that the one supplied did not work.
jere2611 said:
Dann werde ich mich wohl nochmal an die wenden... Tatsächlich habe ich mehrere USB-Kabel probiert, da ich bei einem anderen Beitrag schonmal gelesen hab, dass das mitgelieferte nicht ging.
----------
MOD EDIT: English Translation Below
Then I would probably turn to them again ... In fact, I tried several USB cables, because I read in another post that the one supplied did not work.
Click to expand...
Click to collapse
Das würde ich dir auf jeden Fall empfehlen
Irgendwas scheint ja beim flashen der ROM schief gelaufen zu sein.
----------
MOD EDIT: English Translation Below
I would definitely recommend that to you
Something seems to have gone wrong when flashing the ROM.
Related
Hello guys. I'm having a problem with my old Nexus One, I slept on it while I was in Australia so maybe it got overheated or something. Now it's stuck on the X.
The phone was totally stock before this happened.
The bootloader is unlocked.
Now I tried to restore it via PASSIMG.zip with "PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed" without any other result. Still got stuck on X.
Can't get in to recovery mode, just reboots and get stuck on the X.
I can get in to the bootloader on the phone, but won't find it with adb commands in cmd prompt.
I can find it with "fastboot devices" command. I didn't have usb-debugging activated on the phone while it ****ed up if it would matter.
I've searched on the internet till I got dizzy but didn't get any brighter with this. So I hope someone could tell me where to start.
Thanks in advance, Superbravo.
If everything else fails, this might just work. Download a recovery and place it in the folder where you have blackrose (or fastboot.exe)
Then open CMD and navigate to that folder and type "fastboot boot recovery recovery.img"
That way, you can boot a custom recovery (instead of the one you have installed and then try wiping that way and then install a ROM.
Thanks for the fast answer! I thought I needed to have usb-debugging on to be able to boot a custom recovery (like Amon Ra's), or should I download a "stock" recovery and try to boot that one first?
Superbravo said:
Thanks for the fast answer! I thought I needed to have usb-debugging on to be able to boot a custom recovery (like Amon Ra's), or should I download a "stock" recovery and try to boot that one first?
Click to expand...
Click to collapse
Poängen är alltså att du skall boota en extern recovery än den du har i mobilen. Det tror jag skall fungera fint. Dock har jag inte testat det, så jag vet inte.
I don't know if it works, though, as I haven't tried it.
Tried booting recovery-RA-passion-v2.2.1.img with the command "fastboot boot recovery-RA-passion-v2.2.1.img". The phone just restarts and nothing more happens.
I also tried the "fastboot flash recovery recovery-RA-passion-v2.2.1.img"-command and same for that. Just rebooting and get stuck on the X. Also tried those commands with and without the SD-card attached.
i think you need usb debugging selected
the second recovery line command is correct if that is the exact name of the recovery you put in your fastboot.exe folder--which for me is cd android/android-sdk-windows/tools
rugmankc said:
i think you need usb debugging selected
the second recovery line command is correct if that is the exact name of the recovery you put in your fastboot.exe folder--which for me is cd android/android-sdk-windows/tools
Click to expand...
Click to collapse
Oh thats not too good. Are there anyone of roundpassing this usb-debugging thingy?
Yeah I had it in my fastboot folder.
Are there any way I could flash a rom without wiping the system?
Thanks
If PASSIMG didn't work for you, and you can't boot to recovery you're flashing - then your phone is dead.
Hello all,
i've got a big problem:
<long story..>
I tried to get my KFHD in Fastbootmode with "idme bootmode 4002" but won't worked after reboot.
In another forum, they said »use "idme bootmode 5000"« (now i know: no good idea).
Now i know that bootmode 5000 is recovery.
If i power on the kindle:
1) "kindle fire" (yellow white) logo appers
2) "fastboot kindle fire" logo appers for ~2-3 seconds
3) blackscreen for ever...
How can i get out?
Factory cable won't work
I don't find the usb-boot points.
Can i get out with usb-boot? If yes, can anyone show me where they are?
All hardware is orginal, i haven't modified anything, but i already opened the back cover.
Please help!
Sorry for my bad english, hope its good enough for XDA.
And i hope i've posted in the correct section, and it's a question..
Greetings from germany
TheXorg
TheXorg said:
Hello all,
i've got a big problem:
<long story..>
I tried to get my KFHD in Fastbootmode with "idme bootmode 4002" but won't worked after reboot.
In another forum, they said »use "idme bootmode 5000"« (now i know: no good idea).
Now i know that bootmode 5000 is recovery.
If i power on the kindle:
1) "kindle fire" (yellow white) logo appers
2) "fastboot kindle fire" logo appers for ~2-3 seconds
3) blackscreen for ever...
How can i get out?
Factory cable won't work
I don't find the usb-boot points.
Can i get out with usb-boot? If yes, can anyone show me where they are?
All hardware is orginal, i haven't modified anything, but i already opened the back cover.
Please help!
Sorry for my bad english, hope its good enough for XDA.
And i hope i've posted in the correct section, and it's a question..
Greetings from germany
TheXorg
Click to expand...
Click to collapse
If you still have access to fastboot...
Code:
fastboot -i 0x1949 idme bootmode 1
@soupmagnet
no, i havent. Its always booting recovery. :thumbup:
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
TheXorg said:
@soupmagnet
no, i havent. Its always booting recovery. :thumbup:
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
Click to expand...
Click to collapse
Turn the device completely off, unplug it, enter the command, then plug it back in.
TheXorg said:
Hello all,
i've got a big problem:
<long story..>
I tried to get my KFHD in Fastbootmode with "idme bootmode 4002" but won't worked after reboot.
In another forum, they said »use "idme bootmode 5000"« (now i know: no good idea).
Now i know that bootmode 5000 is recovery.
If i power on the kindle:
1) "kindle fire" (yellow white) logo appers
2) "fastboot kindle fire" logo appers for ~2-3 seconds
3) blackscreen for ever...
How can i get out?
Factory cable won't work
I don't find the usb-boot points.
Can i get out with usb-boot? If yes, can anyone show me where they are?
All hardware is orginal, i haven't modified anything, but i already opened the back cover.
Please help!
Sorry for my bad english, hope its good enough for XDA.
And i hope i've posted in the correct section, and it's a question..
Greetings from germany
TheXorg
Click to expand...
Click to collapse
Can you confirm that you have the correct drivers installed on your pc ?
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
@itouchables
Yes, windows has a *device pluggenld in - device plugged out* loop, linux gives me an error on tty1 and sometimes has a *texas instruments* device in lsusb
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
Did you try to do what soupmagnet suggested by entering the command on the pc, the rebooting the kindle then plugging it in (in hopes to issue the command during the couple of seconds before.it leaves fastboot)
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Yes, i tried with linux, but:
No sorry, its too short.
Linux is *spamming* the following error:
[ XXX.XXXXXX] usb 1-1: >unable to get BOS descriptor
Is Windows faster with fastboot?
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
From my experience Linux is always faster than windows. Especially when dealing with a device being plugged in, it will recognize and load up its module way faster them windows ever does for me. Also, that error may be related to you using a USB 3.0 port, don't use 3.0, use a 2.0 port.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I'm using a Eeepc 1015P, its only got USB 2.0...
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
TheXorg said:
Yes, i tried with linux, but:
No sorry, its too short.
Linux is *spamming* the following error:
[ XXX.XXXXXX] usb 1-1: >unable to get BOS descriptor
Is Windows faster with fastboot?
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
Click to expand...
Click to collapse
Are you running your fastboot commands as root?
i can still run fasboot commands using a usb 3 port, so thats mostly likely not the problem....
@soup
Nope. Does it matter?
@itouchables
havent got a pc with usb 3.0
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
TheXorg said:
@soup
Nope. Does it matter?
Click to expand...
Click to collapse
Unless you have the proper udev rules set up, it absolutely matters.
soupmagnet said:
Unless you have the proper udev rules set up, it absolutely matters.
Click to expand...
Click to collapse
Soupmagnet, isn't it always by default in root ?...for some reason..my is
It would ask for root password, if its always starting as root. Say if i am wrong
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
itouchables said:
Soupmagnet, isn't it always by default in root ?...for some reason..my is
Click to expand...
Click to collapse
No distros (if any at all) will not log you in automatically as the root user by default. It is a huge security risk, and logging in as the root user should be avoided whenever possible. There are commands like 'sudo' and 'su' which can give a normal user elevated privileges when needed.
Yes yes, i know. Im not a linux noob... But you can disable password question in sudo with visudo.... But not more here in this thread
Btw i use Mint, any tips with fastboot or the error spamming?
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
soupmagnet said:
No distros (if any at all) will not log you in automatically as the root user by default. It is a huge security risk, and logging in as the root user should be avoided whenever possible. There are commands like 'sudo' and 'su' which can give a normal user elevated privileges when needed.
Click to expand...
Click to collapse
starnge, my ubuntu workstation at home always hast the # sign at the prompt....you are right i should use sudo su to gain admin privileges......wonder what i did to cause this permanent root on my workstation..............
---------- Post added at 01:41 PM ---------- Previous post was at 01:38 PM ----------
TheXorg said:
Yes yes, i know. Im not a linux noob... But you can disable password question in sudo with visudo.... But not more here in this thread
Btw i use Mint, any tips with fastboot or the error spamming?
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
Click to expand...
Click to collapse
yeah lets not go of topic... btw is your pc 64 bit or 32 bit...and if so, which ver of the distro did you install.
itouchables said:
starnge, my ubuntu workstation at home always hast the # sign at the prompt....you are right i should use sudo su to gain admin privileges......wonder what i did to cause this permanent root on my workstation..............
Click to expand...
Click to collapse
If i remember right, maybe youre member of the group adm or something like this. Then your user is like root.
Send from my LGE610 CM 10.1
Gesendet von meinem LGE610 CM 10.1
Hello All,
I am having an XT1068 running with Android L 5.0.2 on it. I want to root my phone hence tried below.
* First I unlocked boot loader from Motorola website. Its Unlocked now. I can verify it on screen.
* Then I tried to flash below recoveries
- TWRP 2.7.1.1.img
- CWM_Touch_Titan_v2.img
- TWRP2801-titan-motog-2014.img
I used the command as fastboot.exe flash recovery CWM_Touch_Titan_v2.img
Now the problem is, my phone is not getting booted in recovery mode. I tried a lot of time with above mentioned recoveries but dont know what is the issue. Once recovery will work fine, i can root the phone but I am stuck at this stage.
Please advise. Anticipating swift response.
Do you have motorola drivers installed?
stevalder said:
Do you have motorola drivers installed?
Click to expand...
Click to collapse
Do you mean Motorola Drivers installed in my laptop ?? I guess Yes, thats why I am able to push the recovery.
Still as you asked, I will re-install to ensure nothing is missing in terms of drivers, will re-check and update you in some time.
Thanks
Recovery
ich habe dasselbe Problem. Ich habe auch mittlerweile drei verschiedene Recoverys ausprobiert aber ohne Erfolg. Ich komme nicht rein und kann somit den SuperUser nicht installieren
Hilfe?
Gruß,
Adrian.
stevalder said:
Do you have motorola drivers installed?
Click to expand...
Click to collapse
Hi I checked with updating my Motorola device manager (drivers) and flashed recovery again. on my phone screen below is the result.
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:009e6000
cmd: flash:recovery
Above is the same result with all three recovery. CMD (command prompt) cofirms as below.
s>fastboot.exe flash recovery CWM_Touch_Titan_v2.img
target reported max download size of 536870912 bytes
sending 'recovery' (10136 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.297s]
finished. total time: 0.641s
Is there something wrong with filesize ??
Still no luck,. Experts please advise !!
Regards,
I'm no expert ...more noob :silly: looks like it flashed ok?
if your still having trouble you can try this... http://forum.xda-developers.com/showthread.php?t=2499926
ubumanadrian said:
ich habe dasselbe Problem. Ich habe auch mittlerweile drei verschiedene Recoverys ausprobiert aber ohne Erfolg. Ich komme nicht rein und kann somit den SuperUser nicht installieren
Hilfe?
Gruß,
Adrian.
Click to expand...
Click to collapse
Hey Mate,
Try below. I got solution from another thread.
Which version of TWRP do you use? Like @doppelhelix wrote,the latest (and stable) is 2.8.5.0.
The filesize message is normal imho,because the filesize of every custom recovery isn´t equal to the stock one.
The process is finished without a "failed message" ,so you should be able to boot into recovery. Try "adb reboot recovery" in cmd and when you see the dead android you´ll have to press the following combination:
press the VOL UP + VOL DOWN KEY together + POWER KEY .
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to SELECT
Press the power button and tap the vol up button to enter recovery.
TWRP Link : http://teamw.in/project/twrp2/275
Hit thanks if it worked.
succeed!
Hi,
i've been succesfull! I used the philz Recovery but it worked only with the Moto ToolKit. Strange!
Many Thanks,
Adrian.
How To Close Thread ?
How To Close Thread ?
Hi @All
At First sorry für my Bad Englisch
My Z2 pro Boot automatikli in the (i Thing) Fastboot
I Thing Something goes wrong when i was updating twrp
Aniway.
When i Push some buton IT Reboot and goes to the fastboot and dosnt Boot to the system aniway whitch Menu i click.
In cmd have i Something Whit Port 5037?
Can me someone Help? PLZ.
owczarek1987 said:
In cmd have i Something Whit Port 5037?
Click to expand...
Click to collapse
Yes, that's normal. It just says on which port ("door") adb is listening to. Don't worry about that, that's totally fine.
owczarek1987 said:
My Z2 pro Boot automatikli in the (i Thing) Fastboot
Click to expand...
Click to collapse
You think it's fastboot?
Try this and you'll know:
Code:
fastboot devices
If the output is empty, your device isn't being recognized.
owczarek1987 said:
When i Push some buton IT Reboot and goes to the fastboot and dosnt Boot to the system aniway whitch Menu i click.
Click to expand...
Click to collapse
Which button did you press?
Did you try a force reboot using your hard keys? Try one of the following:
Vol.up+power
Vol.down+power
1 should boot into recovery, 2 into fastboot. Can you tell us what happens if you try these buttons?
owczarek1987 said:
I Thing Something goes wrong when i was updating twrp
Click to expand...
Click to collapse
Well, if so you should try to reflash your boot.img (recovery.img if that applies to your device). If you have an update of your partitions, just reflash this update.
Else you have to find your (stock) rom and reflash it.
Besides: If you didn't do a backup, you maybe want to do it in the future. Since I know what it means to search very long for OS'/recoveries for a device, I really want to recommend you to backup your partitions. Always. And better each one, not only those you wan't to modify.
Hi user699
Thx for the fast anwere!
Yes IT IS fastboot Mode but nothing works,
The zuk is Off for example i Push the Power butten (only) or the vol+ AND Power or vol- and Power and IT Boot in the Fastboot (the picture what i was uploading)
I can choose restart bootloader, Recovery Mode,Power Off and Boot to FFBM
No matter what i choose IT Boot to the fastboot again and in cmd IT no responds
(I Think) when in was tipping ADB devices Ther only stand "LIST OF DEVICES ATTACHED"
i remember that there must some With Numbers stand? (Devices serial of Something)
Stay healthy
owczarek1987 said:
Yes IT IS fastboot Mode but nothing works,
The zuk is Off [...] IT Boot in the Fastboot (the picture what i was uploading)
I can choose restart bootloader, Recovery Mode,Power Off and Boot to FFBM
Click to expand...
Click to collapse
Okay. When you're in fastboot, what happens if you enter the following into cmd?
Code:
fastboot devices
Does it display your device or is its output empty?
Please make sure that you actually type "fastboot" if you're in fastboot since adb isn't available once you boot into fastboot mode. That means adb devices wouldn't recognize your phone.
owczarek1987 said:
i remember that there must some With Numbers stand? (Devices serial of Something)
Click to expand...
Click to collapse
Yes, numbers and letters are valid. You should get a similar outut using fastboot devices
If that doesn't work for you you should check your drivers (you're using windows, right?). I cannot help you with the driver part, however, since I'm using linux (I never had to install drivers, thus it always worked) but you should find something on the net or here in xda.
Yes i use Windows.
The ZUK is Off and when in Connect zu the Laptop it Turn on and IT go automatikli to the fast Boot nur Windows make a conecting Sound
Uff drivers ....
Okay i install some Driver from Here.
Okay ich will bei Test some driver.
When IT goes can U Tell me what Inhaber too do?
Is it okay when i Reinstall twrp ober fastboot?
Done
owczarek1987 said:
Yes i use Windows.
The ZUK is Off and when in Connect zu the Laptop it Turn on and IT go automatikli to the fast Boot nur Windows make a conecting Sound
Uff drivers ....
Okay i install some Driver from Here.
Okay ich will bei Test some driver.
When IT goes can U Tell me what Inhaber too do?
Is it okay when i Reinstall twrp ober fastboot?
Click to expand...
Click to collapse
Hello.
Sorry, I am a bit busy in the moment an didn't log into xda.
So, yes, you can try to reinstall twrp as long as your device is being recognized.
And if you can flash twrp, then maybe search for stock ROM (or custom if you whish) and install that.
This should unbrick your device.
Hello everyone.
Instructions for root Oneplus 10 Pro Color OS - Oxygen OS.
1. Open Settings on your OnePlus 10 Pro and go to the ‘About Phone’ option.
Look for the Build Number and tap 7-8 times on it. It will display ‘You are now a developer.’
Go back to the main Settings then go to System > Developer Options.
2. In Developer Options, you need to enable OEM Unlocking & USB Debugging
3. Connect phone to PC and choice transfer file.
4. Start adb and write adb reboot bootloader
5. Unlock bootloader (fastboot flashing unlock)
6. Need patched boot color os or Oxygen OS
7. Then fastboot boot boot (magisk).img
8. Start system
9. Install latest magisk canary and tap to install automatically.
10. Excellent
Download: Repo AFH (Color - Oxygen OTA-Kernel) Mega Repo (Color - Oxygen Kernel)
Ps. Of course, you must have the correct drivers installed adb (Google to the rescue)
UPD: Install drivers
Open Settings > Windows Update > Advanced options > Optional updates > see drivers when device connected
Spoiler: ADB MODE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: FASTBOOT MODE (BOOTLOADER)
Spoiler: FastbootD MODE
VovaHouse said:
Hello everyone.
Instructions for root Oneplus 10 Pro Color os.
1. Open Settings on your OnePlus 10 Pro and go to the ‘About Phone’ option.
Look for the Build Number and tap 7-8 times on it. It will display ‘You are now a developer.’
Go back to the main Settings then go to System > Developer Options.
2. In Developer Options, you need to enable OEM Unlocking & USB Debugging
3. Connect phone to PC and choice transfer file.
4. Start adb and write adb reboot bootloader
5. Unlock bootloader (fastboot flashing unlock)
6. Need patched boot color os a07 or a08
7. Then fastboot boot boot (magisk).img
8. Start system
9. Install latest magisk canary and tap to install automatically.
10. Excellent
Ps. Of course, you must have the correct drivers installed adb (Google to the rescue)
Click to expand...
Click to collapse
Thanks, works here
I had a04 out of the box and update was too slow,
I did boot on patched a07 and repatched with magisk (gotta do it fast as you may get random reboot due mismatch of boot img) but it works.
Just adding value.
Danz17 said:
I had a04 out of the box and update was too slow,
I did boot on patched a07 and repatched with magisk (gotta do it fast as you may get random reboot due mismatch of boot img) but it works.
Just adding value.
Click to expand...
Click to collapse
The main thing is that everything works, the instruction is written from personal experience and I hope that it will help a lot of people
Hey VovaHouse,
Can you help me? just got the OnePlus normally i'm good with rooting been doing it for years.
i followed the steps and all i get is a CMD command list no bootloader unlock.
i tried the standard Fastboot OEM unlock but doesnt work either just says unknown command
what can i do?
Johnstan725 said:
Hey VovaHouse,
Can you help me? just got the OnePlus normally i'm good with rooting been doing it for years.
i followed the steps and all i get is a CMD command list no bootloader unlock.
i tried the standard Fastboot OEM unlock but doesnt work either just says unknown command
what can i do?
Click to expand...
Click to collapse
need fastboot flashing unlock
VovaHouse said:
need fastboot flashing unlock
Click to expand...
Click to collapse
Cheers i tried that some reason it kept saying command doesn't exist i rebooted the PC and ran an ALL IN ONE TOOLKIT from my laptop instead of PC and worked. Thanks!
Johnstan725 said:
Cheers i tried that some reason it kept saying command doesn't exist i rebooted the PC and ran an ALL IN ONE TOOLKIT from my laptop instead of PC and worked. Thank
Click to expand...
Click to collapse
Good
Johnstan725 said:
Cheers i tried that some reason it kept saying command doesn't exist i rebooted the PC and ran an ALL IN ONE TOOLKIT from my laptop instead of PC and worked. Thanks!
Click to expand...
Click to collapse
Where can I find the All in one toolkit?
Call_Me_Creep said:
Where can I find the All in one toolkit?
Click to expand...
Click to collapse
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
Gör man allt med telefonen lr använder man dator till något? efter man laddat ner ditt paket.
.Jag får min mobil imorgon och tänkte förbereda.
zelma83 said:
Gör man allt med telefonen lr använder man dator till något? efter man laddat ner ditt paket.
.Jag får min mobil imorgon och tänkte förbereda.
Click to expand...
Click to collapse
Hett tips är att skriva på engelska i detta forumet =)
Robsjo said:
Hett tips är att skriva på engelska i detta forumet =)
Click to expand...
Click to collapse
Ok, är helt ny på forumet
Hello guys i came all the way until unlocking bootloader command ,but whichever command i try , i only get "waiting for device " nothing else , any ideas?
Adb or fast
Trickster69 said:
Hello guys i came all the way until unlocking bootloader command ,but whichever command i try , i only get "waiting for device " nothing else , any ideas?
Click to expand...
Click to collapse
Adb or fastboot?
Check drives in device manager
yeah , i just installed oneplus drivers and disabled signed applications to make it work , unlocked bootloader . now trying to figure out how to install the Indian version of oxygen os 12 for oneplus 10 pro Zip file
VovaHouse said:
Adb or fast
Adb or fastboot?
Check drives in device manager
Click to expand...
Click to collapse
its ADB
Trickster69 said:
yeah , i just installed oneplus drivers and disabled signed applications to make it work , unlocked bootloader . now trying to figure out how to install the Indian version of oxygen os 12 for oneplus 10 pro Zip file
its ADB
Click to expand...
Click to collapse
Oneplus 10 Pro Global Rom India / eu
✧ Oxygen OS 12.1 A11 IND full OTA.zip • Link 1 : Here • Link 2 : Here ✧ Oxygen OS 12.1 A11 EU full OTA.zip • Link 1 : Here • Link 2 : Here ◆ Instructions : • Unlock bootloader : fastboot flashing unlock • Flash payload.bin via fastbootD Here...
forum.xda-developers.com
what about oneplus 10 pro global release with OOS?
akeshma said:
what about oneplus 10 pro global release with OOS?
Click to expand...
Click to collapse
boot_OOS_A11.rar
drive.google.com
On Monday I'll receive my OP10pro, EU-version, unlocked. Can anyone tell how to root this thing?