Hello, I have a big problem
I unlocked my HTC One, everything went well
I installed the recovery
and after trying to install the rom (revolution)
The phone has been launched in htc screen when I turn.
He restarted well bootload but not to access recovery.
I tried to reflash the recovery via fastboot command on the pc
But still no result.
It remained or bootload screen or htc home
I leave in charge that night and it's even worse: '(
the bootload no longer works
It will only restart in htc home screen.
When I reboot and press volume down ... The screen remains black with the red LED on or restarts on htc screen.
It is there another way to find / reinstall the recovery or ROM?
Thank you very much in advance I lost
Bonjour , j'ai un gros probleme
J'ai unlocked mon HTC One , tout c'est bien passé
J'ai installé le recovery
et après avoir voulu installer la rom (revolution)
Le téléphone est resté en écran de lancement htc quand je l'allume.
Il redémarré bien en bootload mais impossible d'accèder à recovery.
J'ai essayé de reflasher le recovery via le la commande fastboot sur le pc
Mais toujours pas de résultat.
Ça resté ou bootload ou écran d'accueil htc
Je l'ai laisser chargé cette nuit et la c'est encore pire :'(
le bootload ne fonctionne plus
Il ne redémarre que en écran d'accueil htc.
Quand je le redémarre et appuie sur volume down ... L écran reste noir avec la led rouge allumé ou redemarre sur l'ecran htc.
Il y a t il un autre moyen de retrouver / réinstaller le recovery or ROM ?
Merci beaucoup par avance je suis perdu
Have you tried with flash of the boot.img of rom with fastboot?
If not, try it:
- Extract from the zip the file called: boot.img
- Put it into your fastboot folder
- Connect the phone at the pc in fastboot mode
- Flash the boot with
Code:
fastboot flash boot boot.img[/url]
- Make an erase cache [code]fastboot erase cache
- Reboot the phone
Code:
fastboot reboot[/url]
However, your battery is charge?
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 ?
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.