Hi, Im new here. Just Bought my Xiaomi A2, which is weird cause i first order a Mi6X and the box is Mi6X. But the phone model says A2 (same phone at least as i search) and running on Android One 8.1.0 w/ security patch from september 2018.
{
"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"
}
The problem is it won't update via OTA (which is weird, cause it's a brand new android one). So im deciding i should do an image flash of newest MiA2 Android One (from xiaomi web ofc).
After installing all the drivers and adb.
First i try
Code:
C:\Users\user\ADB>fastboot oem unlock
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
then
Code:
C:\Users\user\ADB>fastboot flashing unlock
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
and also
Code:
C:\Users\user\ADB>fastboot flashing unlock_critical
FAILED (remote: 'Command not support: the display is not enabled')
fastboot: error: Command failed
none of them works. I already makesure to "enable usb debugging" and "OEM Device Unlock" in Devs Opt.
Did i wrong or skip something ?
PS : FYI, im doing it w/ the usb cable from the box to my ASUS TUF running on windows 10 via USB hub on USB2.0 ports (as i read and try the adb and fastboot having some trouble with windows 10 and USB3.0 ports).
also incase needed here the getvar all
Code:
C:\Users\user\ADB>fastboot getvar all
(bootloader) crc:1
(bootloader) anti:4
(bootloader) token:bvoohI51kPc6EvH/sxlzxDhsjLM=
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3894
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1A46BF7E00
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:8e84cc34
(bootloader) product:wayne
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.050s
Thanks Before.
UPDATE :
I Tried to install twrp and just flash from recovery mode. It won't
Code:
C:\Users\user\Fastboot_edl-v2>fastboot flash recovery twrp-3.3.1-0-wayne.img
target reported max download size of 536870912 bytes
sending 'recovery' (37620 KB)...
OKAY [ 1.163s]
writing 'recovery'...
FAILED (remote: Anti-rollback check failed)
finished. total time: 1.167s
Booting TWRP image from fastboot also can't do a thing
Code:
C:\Users\user\Fastboot_edl-v2>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.170s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.247s
Also tried using MiUnlocker. It says my phone aren't bound to my account (i guess you can't link non MIUI phone to Mi account)
Also tried flashing in edl mode. It won't even enter edl mode
Code:
C:\Users\user\ADB>fastboot oem edl
FAILED (remote: 'Device is already locked!')
fastboot: error: Command failed
Code:
C:\Users\user\Fastboot_edl-v2>fastboot reboot-edl
rebooting into edl...
FAILED (remote: Device is already locked!)
finished. total time: 0.004s
Well your getvar output mentions product as Wayne which is 6x. So it should update to MIUI rather than Android One ROM. Did you buy it from official channel or some third party retailer ? (I suspect some device tampering but that may be untrue)
Tianhe said:
Well your getvar output mentions product as Wayne which is 6x. So it should update to MIUI rather than Android One ROM. Did you buy it from official channel or some third party retailer ? (I suspect some device tampering but that may be untrue)
Click to expand...
Click to collapse
Well, i bought it online via an e-commerce app. But once it arrive all the writing are in chinese, even the tax tag. I guess it somekind of black market phone tho :/
rrdio said:
Well, i bought it online via an e-commerce app. But once it arrive all the writing are in chinese, even the tax tag. I guess it somekind of black market phone tho :/
Click to expand...
Click to collapse
If you bought it off Aliexpress/Banggood website and it doesnt mention the global or international version then maybe its Wayne. Not sure but i think MIUI (Wayne i.e. 6X) has two versions - China ROM and international ROM. You can try updating through MIUI. Just remember to read all documentation including ARB !
Or third party reseller could have tampered with China factory ROM for making it look like International/Global ROM. It is very difficult to say and you will have to try several options to update.
Tianhe said:
If you bought it off Aliexpress/Banggood website and it doesnt mention the global or international version then maybe its Wayne. Not sure but i think MIUI (Wayne i.e. 6X) has two versions - China ROM and international ROM. You can try updating through MIUI. Just remember to read all documentation including ARB !
Or third party reseller could have tampered with China factory ROM for making it look like International/Global ROM. It is very difficult to say and you will have to try several options to update.
Click to expand...
Click to collapse
Unfortunately mine is installed with android one not MIUI I guess it is, i guess some third party messed up the ROM, as i read online it's not just me who got MI6X with Android one.
https://forum.xda-developers.com/mi-a2/how-to/guide-convert-mi-a2-to-mi-6x-t3896802
Try the "convert back to A2 method"
(Alternative) You can use MiFlash Tool 2016 64Bit to convert back.
Select A2 stock rom folder.
Put phone to edl mode (fastboot oem edl).
Flash Rom when its done, power up the phone to fastboot (vol down + power ) and flash rom again. (for solving any camera wifi etc issue)
Click to expand...
Click to collapse
Also be sure to use an USB 2.0 port, fastboot is useless in USB 3.x ports
DiYei said:
https://forum.xda-developers.com/mi-a2/how-to/guide-convert-mi-a2-to-mi-6x-t3896802
Try the "convert back to A2 method"
Also be sure to use an USB 2.0 port, fastboot is useless in USB 3.x ports
Click to expand...
Click to collapse
Already try that one too can't even enter edl mode
Code:
C:\Users\user\ADB>fastboot oem edl
FAILED (remote: 'Device is already locked!')
fastboot: error: Command failed
I think your last option could be EDL by test point
DiYei said:
I think your last option could be EDL by test point
Click to expand...
Click to collapse
i guess so
too bad that i should open upp some fresh phone from the box :")
I guess the problem lies within the locked bootloader.
But since it's a combination of 6X and A2. so it wont just unlock by "oem unlock" neither by MiUnlock :")
Let me know if you guys here find a solution, beside open up my phone to test point
have you tried to flash miui 10? just be sure it is patched to avoid anti rollback, then you can try to unlock the bootloader
first of all your device is not a2 it is 6x. They just converted it to a2. on arb4 triggered devices you have to flash some kind of dummy thing to bypass it (check 6x forum for that). for converting back to 6x download latest 6x fastboot rom from xiaomi's website(chinese) and flash it via qfil. if you cant manage to get into edl mode best method is testpoint
edit: if you have any chance to return phone, it is best case for you.
DiYei said:
have you tried to flash miui 10? just be sure it is patched to avoid anti rollback, then you can try to unlock the bootloader
Click to expand...
Click to collapse
Well i start to loving the android one features instead of MIUI. But i guess theres, no other way, gotta try what i can do.
q0kHaN said:
first of all your device is not a2 it is 6x. They just converted it to a2. on arb4 triggered devices you have to flash some kind of dummy thing to bypass it (check 6x forum for that). for converting back to 6x download latest 6x fastboot rom from xiaomi's website(chinese) and flash it via qfil. if you cant manage to get into edl mode best method is testpoint
edit: if you have any chance to return phone, it is best case for you.
Click to expand...
Click to collapse
thanks ! will try to flash the MIUI 10 first and convert it to lastest A2 Android One afterwards. Do you think its a good idea or should i just stay put with the MIUI ?
Yeah, i will try contact the distributor to get some return.
rrdio said:
thanks ! will try to flash the MIUI 10 first and convert it to lastest A2 Android One afterwards. Do you think its a good idea or should i just stay put with the MIUI ?
Yeah, i will try contact the distributor to get some return.
Click to expand...
Click to collapse
If you manage to convert and boot miui, just forget about android one. It's better to flash custom roms. In your situation converting back is a real risk
q0kHaN said:
If you manage to convert and boot miui, just forget about android one. It's better to flash custom roms. In your situation converting back is a real risk
Click to expand...
Click to collapse
Olright then. thanks btw !
Do you have any recommendation of custom ROM that light and simple like android one ?
rrdio said:
Olright then. thanks btw !
Do you have any recommendation of custom ROM that light and simple like android one ?
Click to expand...
Click to collapse
Havoc & AOSP Extended, both are good. You will find yourself at home with them.
Related
Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte
Linte said:
Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte
Click to expand...
Click to collapse
There is a Guru reset here
http://www.htc1guru.com/downloads/stock-rom-downloads/
Read the instructions on how to flash
http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Thanks for the fast reply.
The problem is: I cannot get into recovery. I tried to flash the the recovery and the boot via fastboot from the corrospending
Guru, but I'll only get an "signature verify fail" error. I hoped for the fitting RUU- version for my 1.29.111.16, because it seems
to me that it may be the easiest solution for my problem.
Greetings,
Linte
Hi. Can you post your actual command and output?
SaHiLzZ said:
Hi. Can you post your actual command and output?
Click to expand...
Click to collapse
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\adb>fastboot flash recovery rec.zip
error: cannot open 'rec.zip'
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.062s
C:\adb>fastboot flash rom Guru.zip
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4D.14.3250.26
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.111.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4252mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
C:\adb>
Click to expand...
Click to collapse
First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.
Seanie280672 said:
First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.
Click to expand...
Click to collapse
Again sorry for the late reply, business struck again. :l
To your points: Already installed the latest HTC drivers from their homepage more than four times so far. Im pretty sure I have the latest version and after installing, I deinstalled the Sync Manager, like you told me to do. Still no changes.
I cannot see any developer options, simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Also I got the latest fastboot and adb from the (SDK- Manager) Android Developer Tools- Bundle. That's why I am so clueless about my phone not getting recognized by my PC with "adb devices". Strange thing is, I get the ID of my phone in "fastboot devices"...
Later this da I will try to connect my phone to my new, clean Laptop, with the lastest HTC Drivers and adb/fastboot. Maybe this will help.
Thanks so far!
Linte
Edit: tried it with a clean Laptop, latest ADB, latest HTC Sync (installed and deinstalled) and different USB- slots. No success. Adb sill only says
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
Absoluteley no clue where I go wrong here... :l
Linte said:
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
Click to expand...
Click to collapse
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
bored_stupid said:
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Hmm...nope. So far I have only used Windows 7. But like I said, no progress at all. Everythings updated, even on a freshly installed system. Different USB- Ports and so on. No success... :l
Tried to get S-OFF and use another RUU
Click to expand...
Click to collapse
You need a working rom to s-off the phone.
simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Click to expand...
Click to collapse
Linte said:
Code:
C:\adb>[B][COLOR="Red"]adb devices[/COLOR][/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
ADB commands only works from a booted OS with usb debugging ON or from custom recovery. So ADB will never output your device is connected if you are not in the OS or in custom recovery. From bootloader, use FASTBOOT commands
i.e:
Code:
fastboot devices
Code:
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED[B][COLOR="Red"] (remote: signature verify fail)[/COLOR][/B]
finished. total time: 2.062s
Click to expand...
Click to collapse
Looks like your bootloader is locked, you need an unlocked bootloader to flash the recovery partition
Code:
[COLOR="Red"][B]C:\adb>fastboot flash rom Guru.zip[/B][/COLOR]
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
This one is a custom rom (reset rom). You can't flash custom rom from fastboot. You can only flash custom rom from custom recovery.
from fastboot, all you can do is
flashing a custom recovery (with bootloader unlocked)
flashing a RUU.zip in ruu mode
flashing a firmware.zip in ruu mode
all roms (except RUUs) are flashed from custom recovery, including guru reset roms.
btw, there is no RUU for your phone.
unlock bootloader
flash twrp recovery 2.6.3.3
download and save this file to the same folder you have adb and fastboot in
open a cmd prompt from you fastboot/adb folder and boot your phone in bootloader mode (fastboot usb)
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb push the guru reset rom to your /sdcard/ from twrp recovery
download this guru reset rom: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/ and save it to your adb/fastboot folder
boot phone in twrp recovery
open a cmd prompt form your adb/fastboot folder
Code:
adb push guru_reset_m7_2.24.111.3.zip /sdcard/
wait for the file to transfer (5-10 min, there is no progress bar, just wait until adb says it complete)
install the reset rom using twrp
Wow! Thanks a lot!
After unlocking my bootloader again I was able to get into recovery. From there it was easy going to install the Guru.zip via sideload ("Install zip" didnt work for some reason, said something similiar to "Couldn't mount /sdcard/". But sideload worked fine.). Updated everything and my phone runs now like it always had!
Again: really, really thanks a bunch! Thought I somehow ruined my phone, but thanks to you all I got it done. I really appreciate your effort in helping me! You guys are awesome.
Greetings,
Linte
PS: I won't do anything stupid with my phone again, learnd this the hard way.
So I think I've pretty much bricked my phone here. Where do I start?
I can only go into Bootloader. I have S-On and its relocked.
I can't S-off because I'm stuck in boot loader ....
I can't Unlock because I'm stuck in boot loader....
I can't even flash an RUU because its S-ON
The ONLY thing I can do is fastboot commands....Is there any way I can fastboot command to s-off? Any solutions? I was trying to make this stock to give the phone to my mom but I think I'm screwed
fifaman said:
So I think I've pretty much bricked my phone here. Where do I start?
I can only go into Bootloader. I have S-On and its relocked.
I can't S-off because I'm stuck in boot loader ....
I can't Unlock because I'm stuck in boot loader....
I can't even flash an RUU because its S-ON
The ONLY thing I can do is fastboot commands....Is there any way I can fastboot command to s-off? Any solutions? I was trying to make this stock to give the phone to my mom but I think I'm screwed
Click to expand...
Click to collapse
You can run a RUU with S-ON! The big question is there a RUU for your phone? Post a fastboot getvar all except for imei and serialno!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main 4.19.401.11
(bootloader) version-misc: PUT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097
majmoz said:
You can run a RUU with S-ON! The big question is there a RUU for your phone? Post a fastboot getvar all except for imei and serialno!
Click to expand...
Click to collapse
fifaman said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main 4.19.401.11
(bootloader) version-misc: PUT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097
Click to expand...
Click to collapse
Here is a RUU 4.11.401.11.zip that you can flash in fastboot. If you have an issue running the RUU then flash this firmware 4.11.401.11 first. These are the commands to flash both the RUU & firmware after booting into bootloader/FASTBOOT USB:
Code:
fastboot oem rebootRUU
Should see silver HTC logo
Code:
fastboot flash zip <name of file.zip>
The first time you issue this command merely sets up phone to receive the RUU or firmware, it will fail you have to issue the exact command again.
Code:
fastboot flash zip <name of file.zip>
The green status bar may not go all the way to 100%, if it is complete in the cmd window wait a few seconds then proceed.
Code:
fastboot reboot
majmoz said:
first. These are the commands to flash both the RUU & firmware after booting into bootloader/FASTBOOT USB:
Code:
fastboot oem rebootRUU
Should see silver HTC logo
Code:
fastboot flash zip <name of file.zip>
The first time you issue this command merely sets up phone to receive the RUU or firmware, it will fail you have to issue the exact command again.
Code:
fastboot flash zip <name of file.zip>
The green status bar may not go all the way to 100%, if it is complete in the cmd window wait a few seconds then proceed.
Code:
fastboot reboot
Click to expand...
Click to collapse
So I tried what you said (including the stock wipe firmware) but every time it says:
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 85.644s
I don't know why but I seem to keep getting this 12 signature verify fail....
fifaman said:
So I tried what you said (including the stock wipe firmware) but every time it says:
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 85.644s
I don't know why but I seem to keep getting this 12 signature verify fail....
Click to expand...
Click to collapse
Let try this version RUU 5.11.401.10.zip and firmware.
majmoz said:
Let try this version
Click to expand...
Click to collapse
This may be a dumb question but just to confirm, you want me to flash the firmware first, THEN the RUU right?
@majmoz
Hey so I tried the firmware, and it worked! Flashed it BUT when I tried your RUU file, it said the same 12 signature verify fail
fifaman said:
This may be a dumb question but just to confirm, you want me to flash the firmware first, THEN the RUU right?
Click to expand...
Click to collapse
They may not run since you are S-ON and I don't know if they are signed. I am trying to find a RUU.exe for you. Failing that, do you have a linux machine or MAC? If not, you can run linux off a USB FAQ Q5. Linux doesn't do all of the check that Win performs.
@majmoz
I have a Mac which would be much easier and I don't have Linux.... but I can create a USB Linux based on what I see from that link...
Which one should I use?
fifaman said:
@majmoz
I have a Mac which would be much easier and I don't have Linux.... but I can create a USB Linux based on what I see from that link...
Which one should I use?
Click to expand...
Click to collapse
Since you have a Mac use it. Just use the information from Q#3 in the guide to get the correct syntax.
@majmoz
hey so I tried it on my mac, did it all correctly.
But it comes down to this again:
(boot loader) signature checking...
FAILED (remote: 12 Signature verify fail)
fifaman said:
@majmoz
hey so I tried it on my mac, did it all correctly.
But it comes down to this again:
(boot loader) signature checking...
FAILED (remote: 12 Signature verify fail)
Click to expand...
Click to collapse
Since the firmware worked did you try to reboot the phone?
I'm not clear on what caused your issue? What rom was the phone on before you decided to go back to stock? Did you perform the unlock procedure the first time? If so, do you still have the Unlock_code.bin? If not, according to the procedure you need mostly fastboot to unlock your phone.
@majmoz
Yes I did reboot the phone using the command when I used the first firmware.
I was on Cyanogenmod 11 before. I did perform the unlock procedure the first time and YES I do still have the unlock_code.bin
Right now its on Relocked...
Is there any way I can use this unlock_code.bin to Unlock it? I tried on my mac and it said <error: cannot load 'token'> when I tried to <./fastboot flash unlock token Unlock_code.bin>
Sorry for giving you so much trouble...
@majmoz
So maybe I could be doing this wrong or perhaps the RUU file is the wrong one?
Because I'm able to flash the firmware fine and when I enter the reboot command....it reboots but doesn't go into boot loader, its just a black screen. Then I hold down the power and volume down and it goes into boot loader mode....And I repeat the process for the RUU you gave me and it says the same 12 signature verify fail.
What exactly is supposed to show when I flash the initial firmware? because my phone seems to turn off....and I have to hold down power and volume down for 15 seconds (the home and back button flashes a few times, then it goes into boot loader)
fifaman said:
@majmoz
Yes I did reboot the phone using the command when I used the first firmware.
I was on Cyanogenmod 11 before. I did perform the unlock procedure the first time and YES I do still have the unlock_code.bin
Right now its on Relocked...
Is there any way I can use this unlock_code.bin to Unlock it? I tried on my mac and it said <error: cannot load 'token'> when I tried to <./fastboot flash unlock token Unlock_code.bin>
Sorry for giving you so much trouble...
Click to expand...
Click to collapse
You might have to go through the procedure again since you changed your firmware.
So, I guess the phone is working but you want to go back to stock? If you can get it unlocked again, then you could install TWRP and flash this Guru Reset 5.11.401.10. This will get you back to stock, at the end it will ask if you want to root or not choose do not root and it will install the stock recovery. Then you could relock the bootloader and you are done!
@majmoz
OH MY GOD! I Unlocked it!! It worked holy hell you're amazing!
Now I've downloaded TWRP...How do I install this?
majmoz said:
You might have to go through the procedure again since you changed your firmware.
So, I guess the phone is working but you want to go back to stock? If you can get it unlocked again, then you could install TWRP and flash this Guru Reset 5.11.401.10. This will get you back to stock, at the end it will ask if you want to root or not choose do not root and it will install the stock recovery. Then you could relock the bootloader and you are done!
Click to expand...
Click to collapse
fifaman said:
@majmoz
So maybe I could be doing this wrong or perhaps the RUU file is the wrong one?
Because I'm able to flash the firmware fine and when I enter the reboot command....it reboots but doesn't go into boot loader, its just a black screen. Then I hold down the power and volume down and it goes into boot loader mode....And I repeat the process for the RUU you gave me and it says the same 12 signature verify fail.
What exactly is supposed to show when I flash the initial firmware? because my phone seems to turn off....and I have to hold down power and volume down for 15 seconds (the home and back button flashes a few times, then it goes into boot loader)
Click to expand...
Click to collapse
When you run the firmware and you use the fastboot reboot command the phone should reboot into the OS. If you use the fastboot reboot-bootloader command the phone should reboot into the bootloader.
Did the black screen have a red triangle in it?
Cyanogenmod 11 does a job on the phone and unfortunately it sometimes takes a RUU to correct it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
fifaman said:
@majmoz
OH MY GOD! I Unlocked it!! It worked holy hell you're amazing!
Now I've downloaded TWRP...How do I install this?
Click to expand...
Click to collapse
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery <name of recovery.img>
fastboot erase cache
fastboot reboot-bootloader
@majmoz
Okay so you're amazing. I installed TWRP and it works, which gives me some relief. Now the only problem is, how do I get the Guru Reset on my phone? I can't seem to drop it in using android file transfer. Any solutions?
fifaman said:
@majmoz
Okay so you're amazing. I installed TWRP and it works, which gives me some relief. Now the only problem is, how do I get the Guru Reset on my phone? I can't seem to drop it in using android file transfer. Any solutions?
Click to expand...
Click to collapse
Here is the entire procedure you have already got most of it complete.
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
hi
After turning on the device, I noticed that Rom Mi A1
Then flash rom eu rom
The device gave this warning
Do not flash with miflash
{
"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"
}
2 things:
1.Where u buy this phone? He comes with mi5x box or mi A1 box?
When u start,he started with android one splash or miui spash?
2.Ur second screenshot is before or after brick?
U can enter on fastboot?
xemisxu said:
2 things:
1.Where u buy this phone? He comes with mi5x box or mi A1 box?
When u start,he started with android one splash or miui spash?
2.Ur second screenshot is before or after brick?
U can enter on fastboot?
Click to expand...
Click to collapse
i have this problem.
After the purchase mi5x i see rom of phone is android one.i installed TWRP on my mi 5x and after flashing miui pro rom on it after rebooting my device showing mi logo and fast turn off.my device can going to fastboot:crying::crying:
on my box phone writing mi 5x and i checked imei it on imei.com it say phone is mi 5x
Ur bootloader was unlocked and u lock it,u need to unlock it or reflash official miui with mi flash,be carefull!!
I recomend u see a lot of post for mi5x and flash with mi phone
xemisxu said:
Ur bootloader was unlocked and u lock it,u need to unlock it or reflash official miui with mi flash,be carefull!!
I recomend u see a lot of post for mi5x and flash with mi phone
Click to expand...
Click to collapse
thanks bro.yes my device at the first boot showing " unlock " .do you have idea for do it?
and can i unlock bootloader in fastboot without usb debugging?
i tried unlocking BL but in 99% failed.do you have idea?
and
as regards my device first with mi a1 frimware can i flashing miui rom of mi 5x on it?
best regard:good:
Yes, same problem with my phone.. I bought it from everbuying. Came with Android One, with unlocked bootloader. Now, I tried to flash MIUI global ROM, and now I am stuck with MI logo. When enter fastboot, tried to unlock bootloader with MI Unlock it said: "Current account is not bound to this account.", and then "Add your account and device in MIUI,s settings>Developer options>MI unlock status"
But, now I can not boot system, and can not enter Developer options...
In Fastboot mode I can not flash TWRP (because locked bootloader) to recover backuped system.
Is there any chance to fash official ROM?
P.S. In fastboot mode, after typr "fastboot getvar all", I can see it is product:tiffany
nesorsba said:
Yes, same problem with my phone.. I bought it from everbuying. Came with Android One, with unlocked bootloader. Now, I tried to flash MIUI global ROM, and now I am stuck with MI logo. When enter fastboot, tried to unlock bootloader with MI Unlock it said: "Current account is not bound to this account.", and then "Add your account and device in MIUI,s settings>Developer options>MI unlock status"
But, now I can not boot system, and can not enter Developer options...
In Fastboot mode I can not flash TWRP (because locked bootloader) to recover backuped system.
Is there any chance to fash official ROM?
P.S. In fastboot mode, after typr "fastboot getvar all", I can see it is product:tiffany
Click to expand...
Click to collapse
I'm with the same problem. Did you fixed this? How you solved?
thiagoliveira said:
I'm with the same problem. Did you fixed this? How you solved?
Click to expand...
Click to collapse
-Hello, I'm in the same problem.
-I Buyed a MI 5X from Banggood.com
-It came with an alternative Android One
-I tried to flash 5X MIUI EU
-I received the message "the system has been destroyed"
-Bootloader now its locked but I can enter in the fastboot mode
-I tried to flash all Rom's in the official MI website (TGZ and ZIP) but nothing. The correctly Rom flash's at 1 second.
-I turned on in the DL mode and changed the driver but another error appears saying its missing files when I try to flah any Rom.
I am facing exactly the same problem guys. Did any of you manage to solve this issue??
Try to boot in fast boot mode..Flash twrp and go to reboot button..There have two slot in your phone..Choose other slot and reboot... Actually can get back to normal.
I have the same problem. Got the phone from teknistore which came unlocked. After installing eu rom the phone becomr locked again and the info the system had been destroyed.
In fastboot twrp can not be loaded because the phone is locked. Alsi mi flash is not working becausr is the lock.
How to solve this ?
any solution?, same error here
C:\adb+twrp-boot-protect\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) slot-active:b:no
(bootloader) slot-active:a:yes
(bootloader) slot-unbootable:b:no
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:b:no
(bootloader) slot-successful:a:no
(bootloader) current-slot:_a
(bootloader) slot-suffixes:_a,_b,
(bootloader) slot-count:2
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4199000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:le-xxhdpi-v4/rank_7.png
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x58bb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system:
(bootloader) crc:1
(bootloader) serialno:5891b1cd0604
(bootloader) kernel:lk
(bootloader) product:tissot
all:
finished. total time: 0.322s
Hello everyone,
I unlocked BL, flashed twrp and a xiaomi.eu rom. Booted all fine. Afterwards I flashed havoc os, but now my phone doesn't boot into android or twrp. It just boots into fastboot mode or shows me the redmi logo over and over. I've already tried to flash this rom: https://forum.xda-developers.com/k20-pro/how-to/rom-miui-10-3-1-0-global-eea-fastboot-t3962880 with fastboot. Accidentally chose "clean all and lock" ,but luckily that didn't work I guess, because when I type "fastboot oem device-info" I get this: \
c:\adb> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.008s]
Finished. Total time: 0.008s
So when I try to flash the room with the flash tool I get an error after approximately "flash crclist error". Tried a few times and it flashed, but the phone still doesn't boot into android.
What should I do now?
Please help
Have you tried using a short folder name for the unzipped rom? Like C:\Mi. I had a fastboot bootloop yesterday too and all guides said you should use a short path.
After having problems restoring my Lineage OS (TWRP Restore), I found a guide that recommended to do a "fastboot flashing lock" and "fastboot flashing unlock" to delete the data partition. In a fit of mental derangement I did exactly did that. Well, at least the the first part. Stupid move - really. Now I'm stuck with a locked bootloader. I can't unlock it via fastboot commands:
c:\fastboot flashing unlock
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Same results for "fastboot oem unlock".
Fyi:
c:\fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
The Mi Unlock tool gives me a charming "Please add your account in MIUI's Settings > Developer options > Mi Unlock status." Which isn't possible because I had Lineage OS running and I can only get into Fastboot now. If I try to boot regularly the phone says "The system has been destroyed".
Well, I almost accepted that I have to dismantle the phone to get into EDL mode, but then I discovered hints that I might need some kind of authorization to update the phone via EDL mode. And a lot of shady offers to do exactly that ...
Did I brick my phone for good, or is there any hope to fix it?
Thanks a lot!
Hi, did you solved it?
If not, try to ut the phone in fastboot mode, then download exactly stock firmware (global, india, china,...etc) version for this phone, then flash it via Miflash.