Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4xxxxxx02551
(bootloader) imei: 358xxxxxxx2624991
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.013s
I just plug the phone to charge it and it restart by itself and this appeared in the screen (Attach Files)
Can you confirm the bootloader is unlocked (says UNLOCKED on bootloader screen)?
If so, try fastboot erase cache, and then try to flash TWRP again. Try the current version TWRP (2.8.7.0). It shouldn't make a difference, but maybe there is some bug in 2.8.5.0 that I don't know about.
Of that doesn't work, you can try to relock the bootloader and run the 4.28.502 RUU. But if that doesn't work, it puts you in a slightly worse position than before, since you can't do much with bootloader locked (except RUU).
Yes is unlocked and I use this version openrecovery-twrp-2.8.5.0-m8
Please help me :'(
gato06 said:
Please help me :'(
Click to expand...
Click to collapse
I gave 2 suggestions in my last post. Did you try them?
Yes I tried run the RUU but don't work I have error
gato06 said:
Yes I tried run the RUU but don't work I have error
Click to expand...
Click to collapse
I gave 2 suggestions, did you try both?
Also, its hard to help when you post one line of text and give no details. What error message (number)? The error message and number tells you why the RUU failed.
Did you relock the bootloader before RUU (which is required to RUU with s-on) as I already previously mentioned?
Honestly, it doesn't bode well for your device when the person trying to help is putting forth more effort then the person that is trying to get help.
The phone worked well 2 days and I relock bootloader and install the RUU and the phone worked 4 more days and again two days ago the same problem
when I try edit boot o recovery says fail timeout
Sorry I don't speak English :/
gato06 said:
The phone worked well 2 days and I relock bootloader and install the RUU and the phone worked 4 more days and again two days ago the same problem
when I try edit boot o recovery says fail timeout
Sorry I don't speak English :/
Click to expand...
Click to collapse
You speak (or at least type) English just fine for the purpose, from what I can tell.
You need to unlock the bootloader again to flash any recovery.
I'll ask again: What error message do you get when you try the RUU????
ERROR[171]: ERROR USB CONECTION
but when I cmd fastboot command
C:\adb>fastboot devices
HT45ECDM02551 fastboot
gato06 said:
ERROR[171]: ERROR USB CONECTION
but when I cmd fastboot command
C:\adb>fastboot devices
HT45ECDM02551 fastboot
Click to expand...
Click to collapse
So you obviously have a USB connectivity issue.
Although, I'll admit its a bit odd to have that error when the command "fastboot devices" seems to return the proper response (indicated that the device is connected).
Do you happen to have USB 3.0 ports?
Yes the command fastboot work fine and I'm using USB 2.0 port
don't are the ports because I tried in other pc and don't work the RUU file
gato06 said:
Yes the command fastboot work fine and I'm using USB 2.0 port
don't are the ports because I tried in other pc and don't work the RUU file
Click to expand...
Click to collapse
Maybe your cable is faulty, try another cable.
Man I sent the phone to HTC for repair
gato06 said:
Man I sent the phone to HTC for repair
Click to expand...
Click to collapse
Too bad. Unless there was some physical damage or physical defect to the phone, the condition was probably reversible without HTC service.
As HTC will easily determine that the phone was modded (UNLOCKED on bootloader screen), they will charge you from the repair. And usually in these cases, they replace the motherboard, which is a costly repair.
redpoint73 said:
Too bad. Unless there was some physical damage or physical defect to the phone, the condition was probably reversible without HTC service.
As HTC will easily determine that the phone was modded (UNLOCKED on bootloader screen), they will charge you from the repair. And usually in these cases, they replace the motherboard, which is a costly repair.
Click to expand...
Click to collapse
**** I wait the answer of HTC
and I'll say you what they respond
Same issue
I am having the same problem. ROM is LOCKED and S-ON. I cannot unlock using the HTC Unlock_code.bin. I tried several times over the past day. Reliably same result - flash works but phone reboots into HTC then AT&T logo and I am back to "Decrypt storage" screen.
C:\Android>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.141s
RUU also fails to work. It completes a couple of checks then makes the phone reboot back to screen mentioned above. I *can* run FASTBOOT DEVICES and other FASTBOOT commands from FASTBOOT USB with cable. Have tried other computers and other cables with similar results. I am hoping for a miracle answer so my OCD doesn't drive me crazy.
If I could actually get the ROM unlocked that might help me. Somehow I think AT&T is taking over each reboot. I have had this phone since last March when they first came out, if that lends a clue. Thanks for any ideas!
rica0322 said:
I am having the same problem. ROM is LOCKED and S-ON. I cannot unlock using the HTC Unlock_code.bin. I tried several times over the past day. Reliably same result - flash works but phone reboots into HTC then AT&T logo and I am back to "Decrypt storage" screen.
C:\Android>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.141s
RUU also fails to work. It completes a couple of checks then makes the phone reboot back to screen mentioned above. I *can* run FASTBOOT DEVICES and other FASTBOOT commands from FASTBOOT USB with cable. Have tried other computers and other cables with similar results. I am hoping for a miracle answer so my OCD doesn't drive me crazy.
If I could actually get the ROM unlocked that might help me. Somehow I think AT&T is taking over each reboot. I have had this phone since last March when they first came out, if that lends a clue. Thanks for any ideas!
Click to expand...
Click to collapse
Send your phone to HTC, the repair it's free I'm waiting for my repaired phone the next week
gato06 said:
Send your phone to HTC, the repair it's free I'm waiting for my repaired phone the next week
Click to expand...
Click to collapse
I will speak with HTC and see what they can do to help. Thank you!
Error 171 was common on Windows 8 machines, it was a connectivity issue. There are a number of threads on this. It was resolved in 8.1, if that's what you are using. There are also things you need to do to get a RUU to run properly. There are plenty of threads on that too. This site is your friend, read, keep reading, and then read some more. I have never had an HTC One series that I couldn't get back running no matter what was done to it.
Related
Last week I accepted an OTA update on my One-X+ just running all standard (no custom roms, no root etc).
During update, it got stuck and now it keeps rebooting.
I've googled a bit about this problem, and I've done "fastboot erase cache", which didn't solve it.
I also tried a factory reset (also from the menu you get when doing vol.down+power), but that didn't help either.
It's a test phone for development, and I really need it to be in stock, standard condition, so no custom roms.
Is there any step-by-step guide available for people like me that are new to this?
FWIW here's the output of fastboot getvar all:
C:\dev\utils>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: (edit)
(bootloader) imei: (edit)
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) devpower: 85
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.525s
Any help is greatly appreciated!
(I posted this before on the HTC One-X forum, but a few gentlemen pointed out that I should be posting in the One-X+ forum so I reposted here)
If the OTA is still on your SD Card/Internal Storage. try booting into recovery and choose the option to install update from SD Card..
Sent from my HTC One X+ using Tapatalk
AndroHero said:
If the OTA is still on your SD Card/Internal Storage. try booting into recovery and choose the option to install update from SD Card..
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
Sorry for possibly sounding stupid/ignorant, but here it goes:
When I boot into recovery (going into the vol.down+power menu and choosing "recovery"), I'm getting this red triangle/exclamation mark.
When I then plug in the phone to my PC, I see "Removable Disk D:" is added. When I try to open it, it says "Please insert a disk into Removable Disk D:".
Am I misunderstanding something or is it possible that the SD storage is simply broken/corrupted? Because (although I'm not sure it's related), "fastboot getvar all" does say "(bootloader) partition-layout: None".
EDIT: I also tried to do "fastboot update" when in recover mode (while the red exclamation mark shows), but that doesn't go beyond "waiting for device".
When I do "fastboot update" when in "fastboot usb" mode, I get "error: failed to load 'update.zip': No error".
Its been ages since i booted into stock recovery :/ When you get the red triangle, you have to hold either vol up or vol down to go to recovery....
The bootloader partition variable is fine, mine says the same
Fastboot update won't work in recovery mode, and when in fastboot the update command has to be accompanied by an update file... Eg: "fastboot update
c:\users\bob\downloads\update.zip"
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Its been ages since i booted into stock recovery :/ When you get the red triangle, you have to hold either vol up or vol down to go to recovery....
The bootloader partition variable is fine, mine says the same
Fastboot update won't work in recovery mode, and when in fastboot the update command has to be accompanied by an update file... Eg: "fastboot update
c:\users\bob\downloads\update.zip"
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
Running the risk of sounding increasingly ignorant , my update is obviously not on my PC as it was an OTA update on my phone. So maybe "fastboot update" isn't what I should be looking at?
Holding vol-up or vol-down didn't seem to do anything, still just the red exclamation mark on the phone and no difference on the PC.
First off, I received this phone from a friend of mine who received it brand new from textnow through the mail. I went through the steps to unlock the bootloader and errors came of that, but on the device it says "Device is UNLOCKED. Status Code: 3" so i assumed the bootloader was already unlocked based on what i have already researched and found. If this is incorrect, let me know and i will answer accordingly.
Assuming that my assumption is right, I keep getting errors when i try to install twrp. either that, or it appears to do nothing.
Going by the instructions on the cyanogenmod wiki for flashing twrp, fastboot returns this when i enter the "fastboot flash recovery your_recovery_image.img" command where "twrp.img" was my image name and then does nothing:
C:\Users\Me\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (6808 KB)...
OKAY [ 0.219s]
writing 'recovery'...
OKAY [ 0.302s]
finished. total time: 0.524s
I did the same with mfastboot and there are no errors, but it still does nothing:
C:\Users\Me\Downloads\mfastboot-v2>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (10270 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.448s]
finished. total time: 0.779s
I tried each of these a few times to no avail. Ive tried waiting at each step, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands to where it booted straight up to android, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands where i held the buttons to go back to fastboot mode and nothing.
Other things to note:
-Power+Volume down boots to a screen that has "AP Fastboot Flash Mode (Secure)" in red letters where there is device information at the bottom and I can only cycle through one option at a time at the top (if that makes sense).
-Selecting "Restart Bootloader" and "Recovery Mode" brings me back to this same screen mentioned.
Thank you in advance for your replies. I am completely new to this and appreciate the help.
I am only able to boot into fastboot mode and not the bootloader if that was not clear previously. I was up until 6am last night (or this morning) trying to figure it out and it didnt cross my mind this may be my actual issue. Thanks.
Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch
Code:
fastboot oem unlock
and all it does is coming up with this message:
Code:
OKAY [ 0.015s]
finished. total time: 0.016s
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.010s
I also tried with
Code:
fastboot flashing unlock
but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
nickimola said:
Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch and all it does is coming up with this message:
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
I also tried with but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
shravanv3 said:
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
Click to expand...
Click to collapse
Yes, this worked!
Thanks a lot.
I have been trying for the past few days to try to recover my CMR-W09(C00) device with no luck.
What it looks like now?
At the moment there is nothing showing on the screen regardless of what button combinations I've tried (Vol Up+Vol Down+Pwr/Vol Up + Pwr/Vol Down + Pwr, and each with USB power cable plugged in and without). The phone is able to get into fastboot mode (detected by running fastboot devices) automatically, fastboot reboot would get it to fastboot again (i.e., doesn't go to any other mode). The screen is completely dark with nothing at all.
From fastboot I can even see the current firmware version is 195. (CMR-W09C00B195 (8.0.0.195))
What did I do?
Flashed the 160 (CMR-W09C00E160R1P160B160 (9.0.1.160)) firmware which I found on firmware finder, and used EMUI Flasher to flash the firmware. (Found here: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171) Flash seems to have worked and at 100% it said something along the line of checksum failed, rebooted, and never came back to life again.
What I have tried?
1. No eRecovery (that would be easy)
2. Use HiSuite to repair devices, received unsupported device error.
3. Flashed recovery-ramdis, recovery-vbmeta and recovery-vendor and ramdisk that were extracted from 195 OTA (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v225819/f1/full/update.zip) and 160 OTA(http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v234512/f1/full/update.zip). Nothing happened. In Fastboot I can flash these three partitions and system, anything else would return command not allowed.
4. Tried DC Unlocker, when flashing xloader I got command not allowed error, in the end DC Unlocker refunded me.
5. Tried dload method with UPDATE.APP in dload folder only as well as the entire contents (META-INF/tags files and mbn files together with UPDATE.APP) in dload file, reboot using three button combo
6. In desperation I even tried to buy some "factory flash" image which was supposedly to be used by Huawei repair centres internally (with two zip files) to extract to dload folder. Again didn't do anything.
7. Tried to contacted FH to see if they support unbricking this and didn't hear a response.
8. Went to local Huawei authorized repair centre and they don't seem to have seen this device. They told me they can only fix devices bought locally.
9. Tried to flash in TWRP by flash the recovery_ramdisk partition.
All of above leads to nothing (i.e., it goes back to the blank screen with fastboot, however I can hear the USB connected and disconnected sound and HiSuite popped up again which tells me the reboot actually took place).
Some output from fastboot command:
E:\Android\M5>fastboot devices
HYY6R189********** fastboot
E:\Android\M5>fastboot oem get-product-model
...
(bootloader) CMR-W09
OKAY [ 0.013s]
finished. total time: 0.013s
E:\Android\M5>fastboot getvar vendorcountry
vendorcountry: all/cn
finished. total time: 0.013s
E:\Android\M5>fastboot oem get-build-number
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.014s]
finished. total time: 0.015s
E:\Android\M5>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.027s
E:\Android\M5>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.015s]
finished. total time: 0.016s
Click to expand...
Click to collapse
I think I am pretty much out of options right now, but if there is anything
Just wondering if there is anything else I haven't tried that I should?
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
thref23 said:
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Click to expand...
Click to collapse
Thanks for your input, I am able to write to recovery_ramdisk, recovery_vbmeta and recovery_vendor, as well as system partitions, however XLOADER and ERECOVERY* and FASTBOOT partitions seems to be out of touch.
Here are some more output from fastboot:
fastboot oem check-rootinfo
...
(bootloader) status : RISK
(bootloader) version : v1.1
(bootloader) current status: SAFE
(bootloader) old status : SAFE
(bootloader) change_time : 0
(bootloader) item: root-prop, status: SAFE, credible: Y
(bootloader) item: setids, status: SAFE, credible: Y
(bootloader) item: verifyboot, status: SAFE, credible: N
(bootloader) item: verity-enable, status: SAFE, credible: Y
(bootloader) item: fblock, status: locked, credible: Y
(bootloader) item: userlock, status: unlocked, credible: Y
OKAY [ 0.031s]
finished. total time: 0.032s
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Are there multiple lock? What is the fblock? Would unlock that allow me to write to the XLOADER partition?
THE MAXIMUM POWER said:
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
Click to expand...
Click to collapse
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
zhuanyi said:
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
Click to expand...
Click to collapse
Im sorry about that, try to send it to china huawei service as they might repair it their for free because yours is C00
Hello, how are you guys? Well, I have a small (not to say big) on my A3. I try to root from the moment you arrived and after several unsuccessful attempts, it went into a brief loop and stopped at the Fastboot screen.
He used to say that it was corrupted and needed to be formatted. Gave Permission, it starts normal and I flashed a stock rom. For example, after repeating the process other times, they simply go through and always go back to FASTBOOT.
I'm hunting in the forum but I can find no solution or something that can get me out of this hole. Who can help me, I appreciate it.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot getvar current-slot
current-slot: b
finished. total time: 0.003s
obs¹: I can't change the slot for A.
obs²: I have already flashed the global and the EU hoping to get back to normal.
Sorry for the english, I used google to help me.
I have the same damn problem and still I didn't find a solution. I can't change the slot from A to b, i tried using the flash tool and nothing has changed.
overfake said:
Hello, how are you guys? Well, I have a small (not to say big) on my A3. I try to root from the moment you arrived and after several unsuccessful attempts, it went into a brief loop and stopped at the Fastboot screen.
He used to say that it was corrupted and needed to be formatted. Gave Permission, it starts normal and I flashed a stock rom. For example, after repeating the process other times, they simply go through and always go back to FASTBOOT.
I'm hunting in the forum but I can find no solution or something that can get me out of this hole. Who can help me, I appreciate it.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot getvar current-slot
current-slot: b
finished. total time: 0.003s
obs¹: I can't change the slot for A.
obs²: I have already flashed the global and the EU hoping to get back to normal.
Sorry for the english, I used google to help me.
Click to expand...
Click to collapse
I am a new user and I can not link here, I will send a direct message to help you
Try mi flash tool. You won'tnt have the slot problem. I did the same today. And download the rom .tgz from mi forum.
Sapper Morton said:
Since you have the bootloader unlocked, you can change the slot, using:
fastboot --set-active=a or fastboot set_active a
Don't use Minimal, it's quite outdated, instead use the latest platform tools, from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
thanks man u saved my day , i was trying for days now to change the slot but nothing happend and i didn't understand why ? it's because i was using the minimal version which doesn't even understand the command set_active=a