Related
I got my HTC One for 8 months now, i unlocked and flashed it with Andoird Reolution HD 12.0 back then, now as i wanted to perorm an update to 52.0 i tried to do it as usual, download the zip moved it to the "SD"-Card of the Phone and installed it via Clockwerkmod (latest Version). As the installation was complete i wanted to reboot the device and now im stuck in loading screen. If I turn the Phone off i can press recovery in the bootloader menu but it doesnt load in to Clockwerkmod. Does somebody have a solution to this Problem? What happens if I just perform a factory reset in the Bootloader?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: i tried to flash the recovery manually using fastboot while using the manual from androidforums (cant post the actual link as im new to xda)
I followed the steps but now im stuck in cmd where its searching for devices, but it wont find one. as my phone is ****ed up and i dont have a working OS i did not turn off the Fastboot option in the settings.Is this the reason why its not working? Appreciate any ideas. :S
Wiztard101 said:
I got my HTC One for 8 months now, i unlocked and flashed it with Andoird Reolution HD 12.0 back then, now as i wanted to perorm an update to 52.0 i tried to do it as usual, download the zip moved it to the "SD"-Card of the Phone and installed it via Clockwerkmod (latest Version). As the installation was complete i wanted to reboot the device and now im stuck in loading screen. If I turn the Phone off i can press recovery in the bootloader menu but it doesnt load in to Clockwerkmod. Does somebody have a solution to this Problem? What happens if I just perform a factory reset in the Bootloader?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: i tried to flash the recovery manually using fastboot while using the manual from androidforums (cant post the actual link as im new to xda)
I followed the steps but now im stuck in cmd where its searching for devices, but it wont find one. as my phone is ****ed up and i dont have a working OS i did not turn off the Fastboot option in the settings.Is this the reason why its not working? Appreciate any ideas. :S
Click to expand...
Click to collapse
I'm not sure about CWM, but I know you need the latest versions of TWRP to work with KitKAt Roms. If you can get fastboot getvar all to work pls post so we can see where the phone is at.
If it's searching for devices, try removing and reinstalling the htc sync drivers. Get the newest version as well.
mb_guy said:
I'm not sure about CWM, but I know you need the latest versions of TWRP to work with KitKAt Roms. If you can get fastboot getvar all to work pls post so we can see where the phone is at.
If it's searching for devices, try removing and reinstalling the htc sync drivers. Get the newest version as well.
Click to expand...
Click to collapse
It is indeed searching for devices, i dont have sync manager installed and already manually updated the drivers.
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.
Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
knijntjes said:
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
Click to expand...
Click to collapse
At the moment I am trying to find a way to install TWRP without an OS installed and OEM locked. In research I recognized this as the easiest way to install a new ROM. The only thing I need TWRP now.
If I were you, I'd flash the phone using the unbrick method and unlock the bootloader, so you won't lock yourself out in the future
TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
This might help:
http://www.oneplusbbs.com/thread-3203158-1-1.html
I can translate this for you if you need.
You need to flash a special build of Oreo beta to be a more to downgrade to Nougat according to the thread here below.
https://forums.oneplus.net/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
But since you've deleted everything your best bet now is the Qualcomm factory restore recover method.
https://www.google.se/amp/s/forum.x...ick-unbrick-tutorial-oneplus-3t-t3515306/amp/
TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
Some things you've missed:
1. Your first screenshot shows that ADB connects successfully to your phone because it shows the device ID. So drivers and ADB are ok.
2. ADB reads files from the directory it is invoked in. Your command shell is starting in c:/windows/system, so that's the directory ADB is looking in for OP.zip. you can either cd to the correct directory or specify the full path of the OP.zip file.
So, if you reboot your phone into recovery and select install from ADB then start ADB and verify its connected then run the sideload command pointing to the correct director it should flash the ROM successfully.
Sent from my OnePlus3T using XDA Labs
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..
Are you using minimal or full sdk (by Google) platform tools?
Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha
I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird
A different pc solved the issue.. wtf.. thank you..
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..
So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
EDIT: AFTER SEEING SOME POSTS HERE ON XDA I MANAGED TO USE XIAOMI MI FLASH TOOL WITH SUCCESS!, I NEEDED A USB HUB AND CONNECT THE PHONE IN FASTBOOT AND THEN APPLY THE STOCK IMAGES!, ANYONE WHO NEEDS HELP THIS SOLUTION CAN WORK ( ALL MY 3 USB PORTS DIDN'T WORK, WITH HUB IT WORKED )
ClaudioG123 said:
So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
Click to expand...
Click to collapse
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
tsongming said:
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
ClaudioG123 said:
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
Click to expand...
Click to collapse
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
ClaudioG123 said:
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
Click to expand...
Click to collapse
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
Will try soon as im home, if i get waiting for device should i wait?
Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
I can try to see if he works with xiaomitoolv2, and will try what you said and post here
tsongming said:
you do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also it seems that you missed some of the steps outlined in the install instructions for the pixel rom ( i assume the pixel 3 q rom?)
you must install magisk on that rom, you must use recommended twrp,
i haven't used ubuntu for flashing roms recently so i can't provide solid recent steps on ubuntu.
so i would suggest using a pc , ( surely you know someone with a pc) enter fastboot, then you can verify that the phone actually can enter fastboot by checking device manager, or by verifying that the phone is seen by adb
if you are unable to access fastboot, you will need to go into edl mode. Once in edl
download fastboot dipper images rom, and use flashall.bat method to restore the phone.
download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 but it has to be a fastboot rom and not a recovery rom
unpack the rom twice on your desktop
you will be left with a folder and inside you will see batch files and a image folder.
doubleclick flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in recovery mode, fastboot or edl
flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
you should then setup rom
afterwards install twrp and root then create a full twrp backup and save to your pc.
this way you will have a quick solution if you ever need it again in the future.
enjoy a working phone
rom link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
any images fastboot rom will work, you can use the one i listed above or you can use the recent 10.3.5 stable images rom, just find the link via google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
i used this solution but i go i connected the phone in a usb hub!
ClaudioG123 said:
i used this solution but i go i connected the phone in a usb hub!
Click to expand...
Click to collapse
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
Your solution worked with the phone in fastboot, but i had to try a usb hub, that's all, has for roms, experienced both of pixelrom3 and havoc and didn't conviced me enough, i find miui 11 of xiaomi.eu more good looking and doesn't have bugs, and thank you, you are a lifesafer, if it wasn't for that i would have never flashed stock rom back
tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
ClaudioG123 said:
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
Click to expand...
Click to collapse
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
tsongming said:
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
Click to expand...
Click to collapse
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
ClaudioG123 said:
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
Click to expand...
Click to collapse
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
tsongming said:
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
Click to expand...
Click to collapse
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had the issue back with miui 10 stock
Liked the fact that they boosted sound
ClaudioG123 said:
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had+ the issue back with miui 10 stock
Liked the fact that they boosted sound
Click to expand...
Click to collapse
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
tsongming said:
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
Click to expand...
Click to collapse
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
harnkalkn said:
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
Click to expand...
Click to collapse
I am using the weekly Xiaomi.Eu beta rom, averaging 7 hours and 15 minutes SOT and no real issues.
mi 8 bricked
i bricked mi 8 when i try to re-lock bootloader. now i only received a main menu and red massage "this miui version can't be installed on this device". anyone can help me?