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.
Hallo ich habe das Problem das ich den bootloader unlocked bekommen habe allerdings weder twrp noch root flashen konnte da ich im FRP gelocked bin. Und sobald ich usb debugging im System aktiviere und versuche im fastboot Modus was zu machen bekomme ich den Fehler "command Not allow". Muss allerdings dabei sagen das egal in welcher Weise ich in den fastboot Modus wechsel sich usb debugging einfach wieder deaktiviert. Es bleibt nur aktiviert solange ich in den Entwickleroptonen bin. Selbst raus und wieder rein reicht zum deaktivieren...
Habe bereits mehrere factory resets, Bypass Methoden und sonstiges ausprobiert aber irgendwie will gar nichts mehr funktionieren... Bootloader Status ist auch unbekannt.
Model ist VTR-L09
Build B150
Englisch wurde von Google übersetzt sorry.
Hello, I have the problem that I got the bootloader unlocked however neither twrp nor root flashen could as I am in the FRP lured. And as soon as I debugging usb debugging in the system and try to make in fastboot mode what I get the error "command Not allow". Must however thereby say the no matter in what way I in the fastboot mode change usb debugging simply deactivated again. It remains only activated as long as I am in the Developeroptonen. Even out and back again is enough to disable ...
Property already several factory resets, bypass methods and other tried but somehow does not want anything more ... Bootloader status is also unknown.
Model is VTR-L09
Build B150
English was translated by Google sorry
To disable FRP you have to go in the Developer menu and then chose Enable OEM unlock.
Factory Resets bringen dich da nicht weiter.
Wie @Harlock1978 bereits sagte, ist der OEM Lock in den Entwicklereinstellungen aktiv. Wenn du den nicht entsperren kannst, probiere im Fastboot den Befehl "fastboot oem relock BOOTLOADERCODE". Dann sollte dein bootloader wieder gesperrt und in den Entwicklereinstellungen kannst du den OEM Lock entfernen. Dann kannst den Bootloader wieder entsperren und der FRP lock ist auch raus.
---------- Post added at 12:06 PM ---------- Previous post was at 12:06 PM ----------
Factory Resets bringen dich da nicht weiter.
Wie @Harlock1978 bereits sagte, ist der OEM Lock in den Entwicklereinstellungen aktiv. Wenn du den nicht entsperren kannst, probiere im Fastboot den Befehl "fastboot oem relock BOOTLOADERCODE". Dann sollte dein bootloader wieder gesperrt und in den Entwicklereinstellungen kannst du den OEM Lock entfernen. Dann kannst den Bootloader wieder entsperren und der FRP lock ist auch raus.
Das Problem ist aber das oem unlock grau hinterlegt ist und ich im bootloader "command is Not allowed" bekomme selbst wenn ich ihn wieder sperren will. Kommt mir vor wie ne Fehler Schleife irgendwie..
Hat sich erledigt hab alles hinbekommen... Hätte einfach nochmal unlocken müssen... Und nach jedem fastboot Befehl Handy Neustarten.
hallo @Jannomag,
bin eigentlich auf NOUGAT l29c432b360. habe das handy wohl zerstört.
jetzt wollte ich bootloader wieder sperren damit ich dieses blöde frp lock wegbekomme.
jetzt habe ich den fehler phone ist relocked und frp ebenfalls locked.
wenn ich jetzt per fastboot wieder öffnen will bekomme ich die meldung:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock EW*******
...
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: Command not allowed)
finished. total time: 0.031s
bekomm das smartphone nicht mehr gestartet.
was ebenfalls nicht geht ist per erecovery eine stock firmware übers wlan zu ziehen
Schucha said:
hallo @Jannomag,
bin eigentlich auf NOUGAT l29c432b360. habe das handy wohl zerstört.
jetzt wollte ich bootloader wieder sperren damit ich dieses blöde frp lock wegbekomme.
jetzt habe ich den fehler phone ist relocked und frp ebenfalls locked.
wenn ich jetzt per fastboot wieder öffnen will bekomme ich die meldung:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock EW*******
...
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: Command not allowed)
finished. total time: 0.031s
bekomm das smartphone nicht mehr gestartet.
was ebenfalls nicht geht ist per erecovery eine stock firmware übers wlan zu ziehen
Click to expand...
Click to collapse
Nougat und B360 passen nicht zusammen. B360 ist Oreo.
Spielt jetzt aber keine Rolle mehr, mit locked bootloader hast du ohne FunkyHuawei keine Chance, wenn offizielle Huawei Methoden nicht funktionieren.
Anleitung gebe ich dafür nicht, die haben aber alles sehr gut beschrieben, kostet nur Geld. Der Support ist auch gut.
Das einzige, was vielleicht noch gehen kann, ist der Firmware Finder. Funktioniert wie FunkyHuawei, aber dafür gibt's keine richtigen Tutorials.
Hi,
tried to go back to stockrom using this article (2. guide):
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
When I write adb reboot edl in the command prompt and klick enter, nothing happens in QFil, the phone makes a normal reboot und goes to startscreen.
What's wrong?
Regards Robert
robert_b said:
Hi,
tried to go back to stockrom using this article (2. guide):
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
When I write adb reboot edl in the command prompt and klick enter, nothing happens in QFil, the phone makes a normal reboot und goes to startscreen.
What's wrong?
Regards Robert
Click to expand...
Click to collapse
Go into recovery adn then try adb reboot edl or inside the twrp use terminal to reboot edl.
Starchm said:
Go into recovery adn then try adb reboot edl or inside the twrp use terminal to reboot edl.
Click to expand...
Click to collapse
Thank you. I don't know much about adb. What's recovery adn?
or is it a mistake und simply means "and"? Sorry
robert_b said:
or is it a mistake und simply means "and"? Sorry
Click to expand...
Click to collapse
its an and*
sorry, doesn't work. Can't boot into EDL and not into bootloader too, even the phone shows unlock status.
May be I made a mistake when flashing other baseband and kernel??
Flashed this kernel https://forum.xda-developers.com/zuk-z2-pro/development/pro-plus-f1xy-kernel-t3866779 and this baseband https://forum.xda-developers.com/zuk-z2-pro/development/radio-modem-basebands-zuk-z2-pro-t3715835
The phone works with RR 6.2.1 but makes some problems, i.e. with Titanium Backup and skips pin-query for simcard. So I intended to go back to stockrom and then start once more from the beginning.
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,
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.