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.
hi .. im running android 5.1 lollipop via ota update
i tried several steps via internet (many of them to be exact) but all of them
don't work. already tried master tools from xda dev. and other softwares alike (all working fine until i go to unlock bootloader screen (volume buttons not responding).
after "fastboot oem unlock" my device go to a screen with "unlock bootloader?"
volume up to confirm, volume down to don't. both keys aren't responding.
what to do? how can i unlock my bootloader?
is there another way unlocking bootloader?
here are some other info for my bootloader:
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: TECHAIN6592_WET_L
(bootloader) version: 0.5
hope you guys help me. supper thaaanks.. godbless
Hi, I have tryed everything I could find in this forum now but nothing worked.
I'm installing TWRP on a Oneplus X via Fastboot as I did with an other OPX before without problems.
Now when I flash TWRP via Fastboot and reboot (holding power + volume down) TWRP doesn't boot.
The phone is stuck at the OP logo with the "powered by android" logo. I can restart it by holding down the power button for a while but then TWRP gets obviously overwritten by stock recovery.
The only thing I recognized is the output of
Code:
fastboot oem device-info
is different from the device I flashed before:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.018s
Shouldn't the tempered flag be on true? Could this be the problem?
I really would appreciate your help! Thank you!
obermeier said:
Hi, I have tryed everything I could find in this forum now but nothing worked.
I'm installing TWRP on a Oneplus X via Fastboot as I did with an other OPX before without problems.
Now when I flash TWRP via Fastboot and reboot (holding power + volume down) TWRP doesn't boot.
The phone is stuck at the OP logo with the "powered by android" logo. I can restart it by holding down the power button for a while but then TWRP gets obviously overwritten by stock recovery.
The only thing I recognized is the output of
Code:
fastboot oem device-info
is different from the device I flashed before:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.018s
Shouldn't the tempered flag be on true? Could this be the problem?
I really would appreciate your help! Thank you!
Click to expand...
Click to collapse
But u still able to boot into stock recovery right? If u r on oos 3.1.3 flashing official twrp will not work, u need to use oos3 twrp... After flashing it by fast boot, boot into it directly by giving cmd "fastboot boot nameofrecovery.img"
Thank you for your reply!
Just in this second I made a TWRP boot on my phone. I took the one from blu_spark. I guess this is kind of a oos3 twrp.
For people looking for it in the future: I took the twrp file from here: http://forum.xda-developers.com/devdb/project/?id=12587#downloads
Is there an official oos3 twrp? Because I took the most recent from the twrp.me download site and it didn't worked...
obermeier said:
Thank you for your reply!
Just in this second I made a TWRP boot on my phone. I took the one from blu_spark. I guess this is kind of a oos3 twrp.
For people looking for it in the future: I took the twrp file from here: http://forum.xda-developers.com/devdb/project/?id=12587#downloads
Is there an official oos3 twrp? Because I took the most recent from the twrp.me download site and it didn't worked...
Click to expand...
Click to collapse
Till now der is no official twrp for mm bootloader.. But dis one is unofficial like bluespark https://www.androidfilehost.com/?fid=529152257862676606 by NachiketNamjoshi
I tried rooting device as shown on youtube by oneplus developers. installed the setup file that shown there named "installer_r24.4.1-windows", installed adb drivers also from adb manager.
after that checked the following option in fastboot mode.
fastboot devices
fastboot adb devices
fastboot oem device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
firstly i enabled oem unlock in developer option
then booted in fastboot
then commanded fastboot oem unlock (here problem started)
it doesn't ask for wipe data or rebooted as it was supposed to.
then i directly moved to next step of installing twrp & it was installed successful.
then installed supersu zip file which was earlier copied in storage.
then wiped cache & reboot from twrp.
after that reboot & stuck at one+ powered by android screen.
after this I have wiped data, system, cache from twrp as i was not able to boot the phone & now with no OS available.
am able to go to recovery & fastboot mode.
i want to install official firmware
i download from oneplus official site its 1.3gigs in size.
and now while I boot it into recovery my pc wont detect phone here.
how do I copy that into internal storage to flash it with twrp.
please help with this.
thanks.:angel:
Hi,
I tried to root my phone and have taken following steps:
Developer options -> OEM unlock and USB debugging
Boot to fastboot mode -> fastboot flashing unlock
copy the twrp.zip and magisk.zip file to internal storage
after reboot -> fastboot set_active b
and then fastboot flash boot recovery.img (the twrp image)
want to boot to recovery (Power + Volume up) -> don't work
want to boot to system -> don't work (don't know why)
then fastboot flashing lock to make a hard reset and boot with stock image and default settings (I think that was the big mistake)
after that command the phone want to boot and ends with the error system corrupted
Now the phone stucks in fastboot mode and has a locked bootlader.
I can not boot to recovery or to system or flash any images (with fastboot flash system system.img) or unlock the bootloader again (but flashing unlock is not allowed) or change the current slot (The fastboot flashing get_unlock_ability is 0).
This is the fastboot oem device-info:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
This is a part of fastboot getvar all:
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:5
(bootloader) slot-unbootable:b:yes
(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) secure:yes
(bootloader) serialno:63ba69f84226
(bootloader) product:laurel_sprout
(bootloader) max-download-size:804261888
(bootloader) kernel:uefi
Current slot is b and that slot is unbootable (but as I wrote before I cannot change the slot).
I also tried the mi flash tool, but that also didn't work (or I made a mistake, but I don't think so).
I don't really know what to do next, one option is the edl mode (but i don't know anything about that, if that is the only way, could anyone give my some kind of tutorial) or bring the phone to a technican.
Is there way to change the active slot or the locked bootloader state with the mi flash tool?
Has anyone a tip or an idea what I could try...
to unlock to boot loader without have the flashing ability,
to change the active slot in locked state,
or anything else?
I hope I haven't forgot any important information, if so please write.
I very appreciate any help.
you need first to unlock the bootloader and then change slot. use the latest platform tools avaible
to unlock the bootloader in fastboot you should do:
fastboot flashing unlock
reboot in fastboot mode and then
fastboot flashing unlock_critical
to verify that bootloader is unlocked : fastboot oem device-info
to change slot try
fastboot --set-active=a
or
fastboot set_active a
or
.\fastboot --set-active=a
if you are planning to use miflash tool to flash stock rom, verify that you are in slot "A". DO NOT use "clean all and lock" scrip... just "clean all" script.
if you want to relock the bootloader after flashing stock rom, use the same commands but inversed the sequence.
fastboot flashing lock_critical and reboot to fastboot
fastboot flashing lock and reboot to fastboot
to verify that bootloader is locked again : fastboot oem device-info
@AlexXiaomiMiA3 - take it to the service center or use one of the online services which will re-flash your phone via EDL with an authorized Mi Account. There is no known way around this as of now.
For the future reference and as a warning for others, NEVER lock your bootloader unless you are 110% sure that your phone is 100% stock and 100% working.