Related
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
Wait did you pull the battery while you were unlocking or after you got error?
Sent from my LG-P880 using xda app-developers app
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
Download this:
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html
Instructions are inside
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
You did all alright, but LG does not want you to unlock, in other words your phone can not be unlocked at the moment...
Try: adb reboot oem unlock - phone on debug on, if you get red letters in top left corner LGE security...no unlock...
Did the job for 234-XXX now after reflash it is EUR-XXX...
nedooo said:
You did all alright, but LG does not want you to unlock, in other words your phone can not be unlocked at the moment...
Try: adb reboot oem unlock - phone on debug on, if you get red letters in top left corner LGE security...no unlock...
Did the job for 234-XXX now after reflash it is EUR-XXX...
Click to expand...
Click to collapse
i tried as you said adb reboot oem unlock but i dont get such tiny letters... after i tried it i checked Bootloader Unlock Check but says : Lock .
Maybe it's not my time to unlock it
the thing is it seems that the bootloader does unlock if you use the chinese kdz but the issue must be with android software not recognising it, i was on 23400 (not unlockable) and i found that the chinese kdz reported that the bootloader was unlocked, now i had the problem when trying to use unsecure boot and custom recovery so it seemed like it was still locked, now i found out the hard way that it was unlocked according to the hardware as i erased my bootloader and in the process bricked my phone
i think the problem with android recognising it is too do with something in the odm side of things,not being changed appropiatly
RuedasLocas said:
Download this:
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html
Instructions are inside
Click to expand...
Click to collapse
I've tried this but I'm stuck at: <waiting for device>
deownagee said:
I've tried this but I'm stuck at: <waiting for device>
Click to expand...
Click to collapse
Need to install the drivers "CT_HsPhone_General_Drivers", they're inside of the folder.
If it doesn't works, don't touch the cmd window, unplug the phone and pluggit again, try all the ways.
Be creative. I had the same problem in CN V20A (also cause I didn't follow the tutorial...) but I made it.
RuedasLocas said:
Need to install the drivers "CT_HsPhone_General_Drivers", they're inside of the folder.
If it doesn't works, don't touch the cmd window, unplug the phone and pluggit again, try all the ways.
Be creative. I had the same problem in CN V20A (also cause I didn't follow the tutorial...) but I made it.
Click to expand...
Click to collapse
i was enough creative to install linux to my pc and do the whole procces on linux! And guess what: Bootloader status : Unlock ! :victory:
deownagee said:
I've tried this but I'm stuck at: <waiting for device>
Click to expand...
Click to collapse
It used to be my problem also. LMAO..
I finally succesfully unlock my phone using HTC fastboot driver.
When I got waiting for device message, I went to device manager, update fastboot driver with HTC one fastboot driver. Then my phone shows option to unlock it or not.
Sent from my LG-P880 using xda app-developers app
Hi all. Can anyone find me a flashable ZIP of the firmware for the 510? I can't install it with HTC's installation wizard from their website. If you got one, I'd appreciate it. Thanks!
awesome4489 said:
Hi all. Can anyone find me a flashable ZIP of the firmware for the 510? I can't install it with HTC's installation wizard from their website. If you got one, I'd appreciate it. Thanks!
Click to expand...
Click to collapse
Why can't you install it with the installation wizard? Do you lack access to a computer or do you have another problem that can possibly be resolved? Here is a stock Cricket NANDroid backup. I don't think a flashable zip exists yet.
blaqueknight said:
Why can't you install it with the installation wizard? Do you lack access to a computer or do you have another problem that can possibly be resolved? Here is a stock Cricket NANDroid backup. I don't think a flashable zip exists yet.
Click to expand...
Click to collapse
I'm not sure why I can't install it. But I think it might be because I'm using a custom ROM. What happens is, an error message comes up on my laptop saying the installation has failed. And on the phone, the silver HTC letters appear but nothing happens. Though, thanks for the backup. Now I need to learn how to install it. :good:
awesome4489 said:
I'm not sure why I can't install it. But I think it might be because I'm using a custom ROM. What happens is, an error message comes up on my laptop saying the installation has failed. And on the phone, the silver HTC letters appear but nothing happens. Though, thanks for the backup. Now I need to learn how to install it. :good:
Click to expand...
Click to collapse
A custom ROM will not stop the install. The only requirement is for your bootloader to be locked.
blaqueknight said:
A custom ROM will not stop the install. The only requirement is for your bootloader to be locked.
Click to expand...
Click to collapse
So I have to relock the bootloader, and then I can install Sense?
awesome4489 said:
So I have to relock the bootloader, and then I can install Sense?
Click to expand...
Click to collapse
Yes
blaqueknight said:
Yes
Click to expand...
Click to collapse
Just one problem. I'm a bit of a noob at this. But how exactly do I re-lock it?
awesome4489 said:
Just one problem. I'm a bit of a noob at this. But how exactly do I re-lock it?
Click to expand...
Click to collapse
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your adb.exe, fastboot.exe stuff from Android Studio or wherever you obtained it from (Mine is in C:"myusername"\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up my phone
10. You should see something like: "HT42PXU99475 fastboot" if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Type
Code:
fastboot oem lock
in the command window
You should see something like:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 596539196 (0x1FFFFD6C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 9
(bootloader) [INFO] Reset reason in IMEM is 0x77665800
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
Your phone will automatically reboot and your bootloader will be locked
You can check by booting into the bootloader and it should say *** RELOCKED *** at the top in white letters and purple background
blaqueknight said:
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your adb.exe, fastboot.exe stuff from Android Studio or wherever you obtained it from (Mine is in C:"myusername"\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up my phone
10. You should see something like: "HT42PXU99475 fastboot" if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Type
Code:
fastboot oem lock
in the command window
You should see something like:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 596539196 (0x1FFFFD6C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 9
(bootloader) [INFO] Reset reason in IMEM is 0x77665800
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
Your phone will automatically reboot and your bootloader will be locked
You can check by booting into the bootloader and it should say *** RELOCKED *** at the top in white letters and purple background
Click to expand...
Click to collapse
Thanks bro. You're awesome :good:
blaqueknight said:
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your adb.exe, fastboot.exe stuff from Android Studio or wherever you obtained it from (Mine is in C:"myusername"\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up my phone
10. You should see something like: "HT42PXU99475 fastboot" if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Type
Code:
fastboot oem lock
in the command window
You should see something like:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 596539196 (0x1FFFFD6C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 9
(bootloader) [INFO] Reset reason in IMEM is 0x77665800
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
Your phone will automatically reboot and your bootloader will be locked
You can check by booting into the bootloader and it should say *** RELOCKED *** at the top in white letters and purple background
Click to expand...
Click to collapse
Well, I've ran into another problem. It tried to reboot, but now it won't leave the bootloader. Another banner appeared at the top saying "Security Warning" as well.
awesome4489 said:
Well, I've ran into another problem. It tried to reboot, but now it won't leave the bootloader. Another banner appeared at the top saying "Security Warning" as well.
Click to expand...
Click to collapse
You don't have anything on your phone so it can only go to the bootloader. As long as it says RELOCKED, install the RUU and you should get no error this time.
How do I do that?
blaqueknight said:
You don't have anything on your phone so it can only go to the bootloader. As long as it says RELOCKED, install the RUU and you should get no error this time.
Click to expand...
Click to collapse
How do I do that?
It's saying USB connection error, even though when I check in the command prompt it detects my phone. Sorry if I'm wasting your time, but I really want to go back to stock.
awesome4489 said:
How do I do that?
Click to expand...
Click to collapse
Go here, get the ROM/RUU that corresponds to your carrier, and install it. It is a .exe file. What were you trying to install? I thought that was the RUU, but it said it failed. You said the silver HTC letters appear. This time it will not fail because the bootloader is locked. They do not allow you to install with an unlocked bootloader so they don't have to deal with supporting the problems that users would incur.
blaqueknight said:
Go here, get the ROM/RUU that corresponds to your carrier, and install it. It is a .exe file. What were you trying to install? I thought that was the RUU, but it said it failed. You said the silver HTC letters appear. This time it will not fail because the bootloader is locked. They do not allow you to install with an unlocked bootloader so they don't have to deal with supporting the problems that users would incur.
Click to expand...
Click to collapse
I did relock the bootloader, then I launched the RUU exe program while the phone was in the bootloader. But its saying theres a USB connection problem even though everything is connected properly.
awesome4489 said:
I did relock the bootloader, then I launched the RUU exe program while the phone was in the bootloader. But its saying theres a USB connection problem even though everything is connected properly.
Click to expand...
Click to collapse
I'm trying to think of what the problem could be. I haven't seen that before. You can try to go into TWRP and see if your computer can read your sdcard. Just to make sure your USB cable is good. You can try to use it with another device if you have one. In TWRP you can go into Mount-Enable MTP. If that doesn't work, the cable could be bad, or you could try using another USB port.
I have found that immediately prior to relocking the boot loader I've had to flash the stock boot kernel. Then I relock and all boots properly.
awesome4489 said:
It's saying USB connection error, even though when I check in the command prompt it detects my phone. Sorry if I'm wasting your time, but I really want to go back to stock.
Click to expand...
Click to collapse
You're not wasting my time. I'm just trying to figure out what is wrong.
awesome4489 said:
It's saying USB connection error, even though when I check in the command prompt it detects my phone. Sorry if I'm wasting your time, but I really want to go back to stock.
Click to expand...
Click to collapse
Have you had any progress?
Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Some more info:
- ADB does not work currently. I tried Win and OSX , so I believe its the phone rejecting it.
- With stock recovery, reading in the 0P8BIMG.zip RUU file containing a 2.19.401.2 or 2.18.401.3 system fails.
- Flashing recovery TWRP 2.8.5.0 / 2.8.1.0 works, but the phone will not start it.
Code:
C:\Users\USER>fastboot flash recovery "Z:\Installs\HTC Mini 2\recovery-twrp-2.8.5.0.img"
sending 'recovery' (11796 KB)...
OKAY [ 1.393s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 1.790s
- My bootloader is ***Unlocked*** according to the fastboot screen. However, I cannot lock it :
Code:
C:\Users\USER>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 8
(bootloader) [INFO] Reset reason in IMEM is 0x77665501
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.056s
- Output of getvar all :
Code:
C:\Users\USER>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if I missed to provide important information.
Is there any way for me to start over on a lower level ? Or is a mobile shop / HTC my only solution left?
Thanks a lot for any feedback!
Greetings,
faiv
faiv said:
Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Click to expand...
Click to collapse
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
kativiti said:
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
Click to expand...
Click to collapse
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
faiv said:
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
Click to expand...
Click to collapse
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
kativiti said:
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
Click to expand...
Click to collapse
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
faiv said:
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
Click to expand...
Click to collapse
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
kativiti said:
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
Click to expand...
Click to collapse
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
blu3sm4n said:
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
Click to expand...
Click to collapse
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
kativiti said:
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
Click to expand...
Click to collapse
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
blu3sm4n said:
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
Click to expand...
Click to collapse
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
kativiti said:
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
Click to expand...
Click to collapse
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
blu3sm4n said:
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
Click to expand...
Click to collapse
thx for the picture.
you hboot shows that nothing has been done to the phone. so it was NEVER unlocked as stated in original post.
At this point im gonna suggest get your self an original usb cable because the one you using its no good. its giving you wrong info and it seems some get to the phone but corrupted and thats why unlock fails.
im trying to create a new updated RUU but might take some time.
please get OTA cable and try to unlock
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
blu3sm4n said:
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Ok I'll try and let you know
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
kativiti said:
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Click to expand...
Click to collapse
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
blu3sm4n said:
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
Click to expand...
Click to collapse
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
kativiti said:
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
Click to expand...
Click to collapse
in hboot when I try to enter recovery, red warning comes and pressing power+vol up, it says "device cw install:cant mount/data" and then black screen.
I tried second step and added your file into sdcard and update. it says press power button. After that white htc screen is coming. It is waiting since 15 minutes but still nothing and still white screen [emoji21]
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Sorry but it seems I'm unable to help you.
The picture shows green letters behind the red ones. It means the flashing fail, maybe it rejected the recovery or because its locked.
Either way your problem is, your system and recovery are corrupted.
My advice is contact HTC and send for repair. They usually don't charge you.
Ok dude thanks a lot. I'll contact HTC, i hope they can help ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
I recently reverted to stock so I can start from scratch and install everything over again. After all that and booting into android, I checked the ADB and OEM Unlock options in my settings. Then I rebooted into the bootloader and entered the "fastboot OEM unlock" command I followed the on-screen instructions and selected "yes" to continue. The command prompt then shows the following:
(bootloader) Unlocking bootloader...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 24.776s
I've googled this for about an hour and a half and can't seem to find an answer. Any help would be greatly appreciated.
I don't know if it's a typo, but you said you "booted into android" which to me suggests normal android system.
(which might explain why you needed adb...you don't need to enable adb for fastboot mode)
How about booting into fastboot / bootloader mode instead and try your commands there.
(press/hold power and volume down buttons to get to fastboot/bootloader mode)
Sorry if I'm misunderstanding and you are in fact attempting this in fastboot/bootloader mode.
also type a "fastboot devices" command to make sure fastboot is working between phone and pc
Someone else posted exactly this question a few months ago.
Answer? The device was already unlocked.
http://forum.xda-developers.com/nexus-6/help/help-bootloader-unlock-t3349455
I figured that might be the case. I assumed flashing the factory image also re-locked the bootloader.
You had it right. I booted the Android system. I was following the steps on the All-In-One Beginner's guide which included enabling adb. But as for me running the unlock command, I was in the bootloader when trying that.
@dahawthorne gave me the right answer in saying the device is already unlocked. Now I have a separate issue where I can't complete the rooting process, but I'll post a separate thread if I can't figure that out.
Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?
bootloader is locked correct?
SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.
Try: fastboot getvar all
Paste the result. Just hide you imei...
5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot
the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/
5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!
Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?