Database Develop

Rooting Problems

Hi guys I'm sure you've seen this type of thread a million times.
Anyway I tried to root my phone everything was going fine had TWRP ask if I wanted to install SU said yes and then got stuck on the dreaded boot loop.
After probably pressing things I shouldn't of I appear now to have no OS on my phone.
I found a video that said I can download an RUU but I can't find a link that works for the one I need.
I also found a video that suggested using ADB but that doesn't detect my phone when I use ADB Device in a command prompt.
Any help would be appreciated It might need dumbing down for me
I can get into fastboot and recovery from my phone and I can't seem to get my phone by USB to allow access to folders.
Small update when I select ADB Sideload from TWRP it detects my device not sure if that helps.

Slay3rx said:
Hi guys I'm sure you've seen this type of thread a million times.
Anyway I tried to root my phone everything was going fine had TWRP ask if I wanted to install SU said yes and then got stuck on the dreaded boot loop.
Click to expand...
Click to collapse
What version of twrp are you suing and what firmware and software version is/was installed on your phone? Post the output of "fastboot getvar all" (do not post your imei and serialno)
After probably pressing things I shouldn't
Click to expand...
Click to collapse
Be more precise here please. Did you wiped data? system? factory reset? format data?

The guide I used I can't link too.
I managed to get a ROM on my phone through side loading it.
However the ROM I put on needed an update since then my phone won't allow options for fast boot, recovery etc.
I initially ran into issues with the guide when it came to the SU stuff.
The version provided was out of date so I got a more up to date version and this is when I ran into issues.
When I went to exit TWRP is noticed I didn't have SU installed so I clicked for it to install, when this didn't work I tried factory reset which didn't work so formatted from within the advance options which is when I think it deleted by OS.

Slay3rx said:
The guide I used I can't link too.
I managed to get a ROM on my phone through side loading it.
However the ROM I put on needed an update since then my phone won't allow options for fast boot, recovery etc.
I initially ran into issues with the guide when it came to the SU stuff.
The version provided was out of date so I got a more up to date version and this is when I ran into issues.
When I went to exit TWRP is noticed I didn't have SU installed so I clicked for it to install, when this didn't work I tried factory reset which didn't work so formatted from within the advance options which is when I think it deleted by OS.
Click to expand...
Click to collapse
Ok so you have formatted data. You'll need to push and flash a rom to your phone. Before I would appreciate if you could answer my questions, see below quote.
alray said:
What version of twrp are you using and what firmware and software version is/was installed on your phone? Post the output of "fastboot getvar all" (do not post your imei and serialno)
Be more precise here please. Did you wiped data? system? factory reset? format data?
Click to expand...
Click to collapse

TWRP version is 2.6.3.0 the software I pushed is called Guru_Reset_M7_3.22.1540.1
Just a quick update, if I now load and hold down volume button I get the options fastboot, recovery etc.
I ran the command and got:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3483mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b9b91ef9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
Hope that helps and thanks for been so helpful and patient.

Slay3rx said:
TWRP version is 2.6.3.0 the software I pushed is called Guru_Reset_M7_3.22.1540.1
Just a quick update, if I now load and hold down volume button I get the options fastboot, recovery etc.
I ran the command and got:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3483mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b9b91ef9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
Hope that helps and thanks for been so helpful and patient.
Click to expand...
Click to collapse
Your TWRP version is outdated hence why rooting using it resulted in a bootloop (SU binaries that comes with this version aren't compatible with android Lollipop).
Flashing the latest supersu.zip would have probably solved your issue but its too late now that you have formatted data and flashed the wrong rom (see below).
The rom you have flashed (Guru_Reset_M7_3.22.1540.1) is an old version of the developer edition M7 and not for your phone.
What you should do now imo, is to relock your bootloader, flash the 7.18.161.21 RUU so your phone will be running the right OS version, unlock the bootloader again, flash the latest TWRP and root the phone (re-locking the bootloader is required to flash the RUU).
relock the bootloader:
Code:
fastboot oem lock
flash the 7.18.161.21 ruu. You can find your ruu in this thread. The file you need is at post #2, instructions how to flash it (using htc_fastboot) at post #1:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
htc_fastboot reboot-bootloader
unlock the bootloader again (refer to instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
submit your token to htcdev.com/bootloader so you get a new Unlock_code.bin by e-mail. Once received, flash the Unlock_code.bin:
Code:
fastboot flash unlocktoken Unlock_code.bin
Flash latest twrp recovery
Code:
fastboot flash recovery twrp-2.8.7.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
boot in recovery (twrp) then exit recovery and select "yes" when asked if you want to root the phone. Note that the first boot after flashing the RUU can take much more time than usual. Phone will sit at the white HTC screen for a while and then at "updating android" screen. Just wait it will boot eventually.

So I locked the phone as suggested.
I then ran fastboot oem rebootRUU and have a white HTC logo on my phone.
I assume from the instructions this is when I flash the Ruu file next ?
When I try to use the command line fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
I get a reply of error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip'
Any idea if I'm doing something wrong?

Slay3rx said:
So I locked the phone as suggested.
I then ran fastboot oem rebootRUU and have a white HTC logo on my phone.
Click to expand...
Click to collapse
It should be a black screen with silver htc logo.
I assume from the instructions this is when I flash the Ruu file next ?
Click to expand...
Click to collapse
Yes
When I try to use the command line fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
I get a reply of error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip'
Any idea if I'm doing something wrong?
Click to expand...
Click to collapse
Cannot load = can't find file. Make sure the ruu is in the same folder where adb and fastboot are installed. And don't forget you need to use the fastboot version provided in the ruu collection thread, the normal fastboot will not work to flash the ruu.

I downloaded the fast-boot in the thread but when i go to run it, it flashes on my screen and just disappears as I understand that the one you mention is for HTC.
Can I just have it in the folder with the Ruu and then run a command prompt screen within windows?
Again thanks for your advice so far and your continued patience.
{
"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"
}
This is how I have it set.

Slay3rx said:
I downloaded the fast-boot in the thread but when i go to run it, it flashes on my screen and just disappears as I understand that the one you mention is for HTC.
Can I just have it in the folder with the Ruu and then run a command prompt screen within windows?
Again thanks for your advice so far and your continued patience.
This is how I have it set.
Click to expand...
Click to collapse
Ok I have got a little further but I now get the message Cannot open file PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
So it obviously knows the file is there but can't open it for some reason.

Slay3rx said:
Ok I have got a little further but I now get the message Cannot open file PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
So it obviously knows the file is there but can't open it for some reason.
Click to expand...
Click to collapse
save the htc_fastboot.exe in the same folder you have adb.exe and fastboot.exe
htc_fastboot also need the dll included in that folder.
To open a command window, just hold your left shift and right click a blank space in the folder. Then in the contextual menu, select 'open a command windows here". When you need to use fastboot.exe, then start your commands with "fastboot" when you need to use htc_fastboot.exe, like for flashing the ruu, start your commands with "htc_fastboot".
You can also use the Tab key to auto-complete file name so you'll be sure not doing any typo:
e.g:
Code:
htc_fastboot flash zip pn07
then hit the Tab key and the command will auto-complete:
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
If you have more than 1 file starting with "pn07" in your fastboot folder, just keep pressing tab until the right one is displayed.
This way you'll be 100% sure the file name is correct and you shouldn't have any more "cannot load" error.

Finally making progress Thank you so much for your help I'll be sure to donate once paid.
Just waiting for the green bar to fill up I guess before moving on to the next step.

Slay3rx said:
Finally making progress Thank you so much for your help I'll be sure to donate once paid.
Just waiting for the green bar to fill up I guess before moving on to the next step.
Click to expand...
Click to collapse
You don't need to flash twice, when it saying "flash zip complete" just reboot the phone using "htc_fastboot reboot" The green bar will not reach 100%

alray said:
You don't need to flash twice, when it saying "flash zip complete" just reboot the phone using "htc_fastboot reboot" The green bar will not reach 100%
Click to expand...
Click to collapse
The last line the command prompt put up think it's because it was the last command I put in.
I've now rebooted updating apps again thanks I can't express my gratitude enough

Slay3rx said:
The last line the command prompt put up think it's because it was the last command I put in.
I've now rebooted updating apps again thanks I can't express my gratitude enough
Click to expand...
Click to collapse
Wouldn't update the apps yet since you must unlock the bootloader again to flash twrp and root. unlocking the bootloader will perform factory reset so you'll have to re-update all your apps again. You should proceed with the next steps (3-4-5) before setting up your phone.

Hudge problem one HTC one m7

HI evry one i'm french so excuse my english, I'm gonna try to do my best
First let me explain the situation.
A friend give me an htc one m7 from bouygues telecom.
The phone won't boot up when he give me the phone and that probably the reason why he do this.
The bootloader is locked
{
"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"
}
and when i boot up the phone it still on the first screen and do nothing
some times when it boot, it goes to the second screen and play the start melody and after five minute it restart.
I can charge the phone and acces easily to the bootloader and to fastboot mode.
I try to unlock the boot loader bot after the screen where i have to choose yes or no one the phone it restart and stuck on the first screen as before.
When i try to acces to the recovery it takes too much time and i get some errors
but after 4:07 min the recovery appear.
i try wipe data and fartory reset and wipe cache it takes 25 minute to wipe all the data and i'm not shure the data is wipe of.
when i wipe the cache it get stuck after three minute.
the computer recognise the phone when it is in fastboot mode and i can comunicate with the phone vias fastboot command but i can't flash a new rom or recovery beacause the bootloader verify the signature and refused the flashing.
I know it's a bit long but please help me

sfos37 said:
HI evry one i'm french so excuse my english, I'm gonna try to do my best
First let me explain the situation.
A friend give me an htc one m7 from bouygues telecom.
The phone won't boot up when he give me the phone and that probably the reason why he do this.
The bootloader is locked
and when i boot up the phone it still on the first screen and do nothing
some times when it boot, it goes to the second screen and play the start melody and after five minute it restart.
I can charge the phone and acces easily to the bootloader and to fastboot mode.
I try to unlock the boot loader bot after the screen where i have to choose yes or no one the phone it restart and stuck on the first screen as before.
When i try to acces to the recovery it takes too much time and i get some errors
but after 4:07 min the recovery appear.
i try wipe data and fartory reset and wipe cache it takes 25 minute to wipe all the data and i'm not shure the data is wipe of.
when i wipe the cache it get stuck after three minute.
the computer recognise the phone when it is in fastboot mode and i can comunicate with the phone vias fastboot command but i can't flash a new rom or recovery beacause the bootloader verify the signature and refused the flashing.
I know it's a bit long but please help me
Click to expand...
Click to collapse
Hi, welcome to XDA.
Since you still have access to Fastboot on that device, can you please post the outputs of these commands:
Code:
fastboot getvar all
Remove the IMEI and SerialNo strings before posting
Code:
fastboot oem dmesg
Code:
fastboot oem last_dmesg
And finally check if the phone can boot in RUU mode (black screen with silver HTC logo) when doing
Code:
fastboot oem rebootRUU

yes, excuse me i forgot i was busy
for : fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.1020.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT343W913199
(bootloader) imei: 354436053717789
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 4168mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-52da1b55
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
for : fastboot oem dmesg
the text is here beacause if i post the response in the thread it takes too much place https://drive.google.com/open?id=0B26p_awmt-WBMERBc1VQNVlJWVk
for : fastboot oem last_dmesg
it's here https://drive.google.com/open?id=0B26p_awmt-WBY0FHTUxxN2tWYzQ
and finaly for : fastboot oem rebootRUU
I already try to update with the corect ruu but when it try to reboot in bootloader it fail and stuck on the first screen with htc logo, the sama thing appear with the command, the (black screen with silver HTC logo) do not appear. it just do a boot loop.
and for information when i wipe data and factory reset the phone go to "android starting, launch application" but it stay like this for 30 min then i shut it down.

sfos37 said:
I already try to update with the corect ruu but when it try to reboot in bootloader it fail and stuck on the first screen with htc logo, the same thing appear with the command, the (black screen with silver HTC logo) do not appear. it just do a boot loop.
and for information when i wipe data and factory reset the phone go to "android starting, launch application" but it stay like this for 30 min then i shut it down.
Click to expand...
Click to collapse
Both symptoms (not being able to reboot in RUU mode and unable to unlock BL) makes me believe there's something wrong with the emmc or maybe with the BL... You're not the first one to have this problem, for some users it was easy to determine that the emmc was the culprit since there were a lot of emmc related errors ( [SD_HW_ERR] ) in their dmesg output. Anyway, there's nothing you can do without access to RUU mode or without being able to unlock the bootloader. Il est mort

Ok thank you for your awnser and for your quick response it was my first post on XDA and it was cool:good: , bye

help my droid turbo wont screen turn on

I tried root droid turbo MCG24.251-5-5 with initroot and it worked, then after restart stuck in motorola logo, then i try flash stock rom MCG24.251-5-5 using rsdlite after finished my phone bootloop, i try again flash for twice times my phone got a blank screen and on my windows recognised as QHSUSB_BULK. sorry if my english bad

xyz47 said:
I tried root droid turbo MCG24.251-5-5 with initroot and it worked, then after restart stuck in motorola logo, then i try flash stock rom MCG24.251-5-5 using rsdlite after finished my phone bootloop, i try again flash for twice times my phone got a blank screen and on my windows recognised as QHSUSB_BULK. sorry if my english bad
Click to expand...
Click to collapse
Sound like you didn't flash the final command to prevent bootloop when unlocking the bootloader. You didn't follow all the instructions.
TheSt33v said:
!!!FOR MCG24.251-5-5 ONLY!!!
Sunshine will reboot your phone automatically, and it will go into a bootloop. This is normal. Don't panic.
Hold down the volume down button until the phone goes into bootloader mode.
Plug your phone into the computer, start Minimal ADB and Fastboot (see Section 0 for link if you didn't have to install it before this point), and
enter the command: fastboot oem config fsg-id "". This will disable the temporary root exploit.
[*]Reboot your phone normally, and everything should be happy again.
If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader.
(HOWEVER), If you do not see this message, open Sunshine again and follow the directions again. If you're on MCG24.251-5-5, you'll have to gain and uninstall temproot again at the appropriate times.
Click to expand...
Click to collapse
fastboot oem config fsg-id ""
Those are double quotation marks with a space between the d and the quotation marks.

ChazzMatt said:
Sound like you didn't flash the final command to prevent bootloop when unlocking the bootloader. You didn't follow all the instructions.
fastboot oem config fsg-id ""
Those are double quotation marks with a space between the d and the quotation marks.
Click to expand...
Click to collapse
Is there a way to get back life?

xyz47 said:
Is there a way to get back life?
Click to expand...
Click to collapse
when you press the volume down button and power button for several seconds, does it show you bootloader screen?
If you can get to the bootloader screen, then in ADB you can try to flash that command: fastboot oem config fsg-id ""

ChazzMatt said:
when you press the volume down button and power button for several seconds, does it show you bootloader screen?
If you can get to the bootloader screen, then in ADB you can try to flash that command: fastboot oem config fsg-id ""
Click to expand...
Click to collapse
cant get to the bootloader screen
How to use fastboot if it can not get into fastboot mode?

xyz47 said:
cant get to the bootloader screen
How to use fastboot if it can not get into fastboot mode?
Click to expand...
Click to collapse
I don't know of a way.
Maybe someone else has ideas.

anyone has a blankflash for turbo droid?

{
"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"
}
Now I can get into fastboot mode, but when I want to try flash stockrom with fasboot
(Bootloader) slot-count: not found
(Bootloader) slot-suffixes: not found
(Bootloader) slot-suffixes: not found

xyz47 said:
View attachment 4222693
Now I can get into fastboot mode, but when I want to try flash stockrom with fasboot
(Bootloader) slot-count: not found
(Bootloader) slot-suffixes: not found
(Bootloader) slot-suffixes: not found
Click to expand...
Click to collapse
Have you tried flashing that command to stop the temp root from causing bootloop?

fastboot oem config fsg-id
(Bootloader) <UTAG name="fsg-id" type="str" protected="false">
(Bootloader) <value>
(Bootloader) a initrd=0x110BEE50,2483340
(Bootloader) </value>
(Bootloader) <description>
(Bootloader) FSG IDs see http://goo.gl/gPmhU
(Bootloader) </description>
(Bootloader) </UTAG>

xyz47 said:
fastboot oem config fsg-id
(Bootloader)
(Bootloader)
(Bootloader) a initrd=0x110BEE50,2483340
(Bootloader)
(Bootloader)
(Bootloader) FSG IDs see http://goo.gl/gPmhU
(Bootloader)
(Bootloader)
Click to expand...
Click to collapse
That's not the right command. Please read carefully. That's how you messed up your phone. Go back to the top of this thread and use the right command.
Read post #2. Carefully.

I can get into fastboot but can not get into fdr, I have flash stock firmware MCG24.251-5-5 after in motorola logo vibrate, restart motorola logo vibrate like that continuously

xyz47 said:
I can get into fastboot but can not get into fdr, I have flash stock firmware MCG24.251-5-5 after in motorola logo vibrate, restart motorola logo vibrate like that continuously
Click to expand...
Click to collapse
You are going to bootloop until you flash the CORRECT command to get out of the temp root bootloop.
READ POST#2. Especially read the bottom of post #2. The command you typed is not complete.

xyz47 said:
fastboot oem config fsg-id
(Bootloader) <UTAG name="fsg-id" type="str" protected="false">
(Bootloader) <value>
(Bootloader) a initrd=0x110BEE50,2483340
(Bootloader) </value>
(Bootloader) <description>
(Bootloader) FSG IDs see http://goo.gl/gPmhU
(Bootloader) </description>
(Bootloader) </UTAG>
Click to expand...
Click to collapse
You mean fastboot oem config fsg-id "", right?

still can not

TheSt33v said:
You mean fastboot oem config fsg-id "", right?
Click to expand...
Click to collapse
yes

xyz47 said:
yes
Click to expand...
Click to collapse
Your screenshot does not show the "". Did you try it again with the "" after that screenshot?

TheSt33v said:
Your screenshot does not show the "". Did you try it again with the "" after that screenshot?
Click to expand...
Click to collapse
yes, i try it again

xyz47 said:
yes, i try it again
Click to expand...
Click to collapse
Screenshot, because at this point I'm very skeptical. I don't believe you are typing it correctly, when I told you over and over to go read the bottom of post #2. I said there exactly what you needed, and I shouldn't have to repeat myself over and over.
You are probably not typing double quotation marks or not putting the space correctly.

I do not know if the correct command fastboot oem fsg-id "" like this
I'm sorry, Now my phone back to normal..... thank you for helping me

HELP! Fastboot OEM Unlock and Flashing Unlock (Token Verify Failed)

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.

Question mi12 pro boot broken plz help

(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) dpstatus:0x20
(bootloader) socid:457
(bootloader) secure:yes
(bootloader) serialno:2d7d49db
(bootloader) product:zeus
(bootloader) snapshot-update-status:none
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
i need install windows 11 arm64 and (emui 14 or 13)
now i have fastboot loop cant go emui ... or do some thing .
cant install TWRP
Divice is unlocked

kazep said:
i need install windows 11 arm64 and (emui 14 or 13)
now i have fastboot loop cant go emui ... or do some thing .
cant install TWRP
Divice is unlocked
Click to expand...
Click to collapse
On which rom?
How did it happen?
Do you have a PC?

yes i have pc,
rom - xiaomi.eu_multi_XM12Pro_V14.0.22.12.8.DEV_v14-13-fastboot
installed- windows_fastboot_first_install_with_data_format
and broke to orangefox or twrp install ...
you help with teamviaver ?
sorry my englis

kazep said:
yes i have pc,
rom - xiaomi.eu_multi_XM12Pro_V14.0.22.12.8.DEV_v14-13-fastboot
installed- windows_fastboot_first_install_with_data_format
and broke to orangefox or twrp install ...
you help with teamviaver ?
sorry my englis
Click to expand...
Click to collapse
you help with teamviaver ?Nope.
Try re flash the rom,first install.bat
There is already a twrp included.
Use the last version https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/

now installed. no fix fastboot loop see 3s only mi logo.
buttons only gos fastboot. cant go twrp and boot emui ..

kazep said:
now installed. no fix fastboot loop see 3s only mi logo.
buttons only gos fastboot. cant go twrp and boot emui ..
Click to expand...
Click to collapse
The first boot of Xiaomi Eu roms takes 6/8 minutes.
If the flash has no errors and the CMD window closes and the device restarts, you must wait 6/8 minutes without touching any button.

at first I got emui to 14 with it.
but when I started to install windows on the korva, something went wrong.
it is definitely a separate boot to allow, currently there is no boot as allowed, everything is closed. how to unlock or activate them?
this doubleboot nonsense ... ?

kazep said:
at first I got emui to 14 with it.
but when I started to install windows on the korva, something went wrong.
it is definitely a separate boot to allow, currently there is no boot as allowed, everything is closed. how to unlock or activate them?
this doubleboot nonsense ... ?
Click to expand...
Click to collapse
I have no idea what you are talking about, be more specific.
Is your phone a Xiaomi 12 pro(ZEUS)not(DAUMIER)?

or how i make double boot
need make partisons for android device A 100Gb to android emui and B 100GB for windows
at first it was with 1 booth.
now A and B should be there, but neither is active, how to become active? these rom installs don't fix it
Xiaomi 12 pro(ZEUS) 12gb

kazep said:
or how i make double boot
need make partisons for android device A 100Gb to android emui and B 100GB for windows
at first it was with 1 booth.
now A and B should be there, but neither is active, how to become active? these rom installs don't fix it
Click to expand...
Click to collapse
You cannot dual boot.
Either flash the latest Xiaomi EU rom and let the phone reboot without doing anything or if that doesn't work you use Miflash to recover the phone (without locking the bootloader).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

{
"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 path must be:
C:\Miflash\rom folder
and Create an empty txt file of the same name if it does not exist.

I don't see any TWRP in your files apart from an OF which is not for the 12 pro.

the flash is good, let the phone restart.

phone restarts see 5s emui logo and go agen fastboot

kazep said:
phone restarts see 5s emui logo and go agen fastboot
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/mi12-pro-boot-broken-plz-help.4537753/post-87950395
and stop with CMD fastboot

NOSS8 said:
https://forum.xda-developers.com/t/mi12-pro-boot-broken-plz-help.4537753/post-87950395
and stop with CMD fastboot
Click to expand...
Click to collapse
? how stop
double boot
Renegade Project
Group of noobs trying to run everything on your phone - Renegade Project
github.com
Renegade Project
Main Page
renegade-project.tech
Installation Guide
The most up-to-date installation guide for Renegade Project!
renegade-project.tech

kazep said:
? how stop
double boot
Renegade Project
Group of noobs trying to run everything on your phone - Renegade Project
github.com
Renegade Project
Main Page
renegade-project.tech
Installation Guide
The most up-to-date installation guide for Renegade Project!
renegade-project.tech
Click to expand...
Click to collapse
The links above are not for your device.
If you use the CMD ./fastboot boot twrp.img the phone must boot on the TWRP, which is not the case, which means that either it is not the right TWRP or by tinkering you have damaged the /partitions.
Use MIFlash.
Please read the Miflash tutorial carefully before posting an error (the previous case).
BTW:the TWRP you are trying to install is for A13 not A13.