Database Develop

Having issues trying to RUU

My room mates device has been having some issues, after playing pandora, the device reboots, and starts boot looping. So I try to get into TWRP to reflash.to fix the issues. But when trying to boot into recovery, it just sticks on the TWRP splash screen. So I go into bootloader, and try to flash the recovery.img again. It says it flashes just fine. but still sticks at splash.
So I figured the next step is to run the RUU. I try to oem lock the device as it seems by every tutorial that you need to lock the bootloader again to run a RUU file.
And I get this...
C:\Android-adb>fastboot oem lock
...
FAILED (status read failed (No such file or directory))
finished. total time: 890.481s
And the bootloader actually froze, and it seemed to give quite a bit of time. I didnt wanna to just run the RUU and cause another brick.
I just wanted to get a few more people to chime in before I continue on.

I did get oem lock to run with this coming back....
c:\Android-adb>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 1.605s
Then it reboots instantly... and tries to boot the rom again.

oOflyeyesOo said:
I did get oem lock to run with this coming back....
c:\Android-adb>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 1.605s
Then it reboots instantly... and tries to boot the rom again.
Click to expand...
Click to collapse
Reboot into bootloader and verify it says relocked.
next from fastboot run
fastboot oem rebootRUU
it should take you to an htc screen with greenish letters
run your ruu

It still says unlocked.

oOflyeyesOo said:
It still says unlocked.
Click to expand...
Click to collapse
YOUR FAStboot directory, is it c:\Android-adb or c:\Android---------so type cd c:\Android>enter or cd c:\Android-adb>enter, then type fastboot oem lock
are you using a 3.0 usb port, this can cause issues.

It is the android-adb folder. I will check when I get home if it was a USB 3.0 port or not.
Nonsense.

oOflyeyesOo said:
It is the android-adb folder. I will check when I get home if it was a USB 3.0 port or not.
Nonsense.
Click to expand...
Click to collapse
Also try reflashing recovery if you haven't already

Aldo101t said:
Also try reflashing recovery if you haven't already
Click to expand...
Click to collapse
I tried to push the the recovery img, and it says that it is sucessful, did it multiple times, said it flashed just fine. But I try to reboot and it sticks on the TWRP splash. I feel like somehow something got deleted from the system. Id think the ruu would fix it.... but id need to lock the bootloader again, and that doesnt seem to work :-/

What ROM was he running? Have you gotten this worked out?

oOflyeyesOo said:
I did get oem lock to run with this coming back....
c:\Android-adb>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 1.605s
Then it reboots instantly... and tries to boot the rom again.
Click to expand...
Click to collapse
What ROM? This happened to me and at least one other person today...
C:\Users\Owner>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
(bootloader) SD: write failed in CMD25.
OKAY [ 1.080s]
finished. total time: 1.087s
I had the same warnings as you regarding links in other ADB attempts...
Bro, something is other their borking partitions in the EMMC
My experience I tried everything imaginable...

hooover said:
What ROM? This happened to me and at least one other person today...
C:\Users\Owner>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
(bootloader) SD: write failed in CMD25.
OKAY [ 1.080s]
finished. total time: 1.087s
I had the same warnings as you regarding links in other ADB attempts...
Bro, something is other their borking partitions in the EMMC
My experience I tried everything imaginable...
Click to expand...
Click to collapse
I was using rootbox. Still no luck.

oOflyeyesOo said:
I was using rootbox. Still no luck.
Click to expand...
Click to collapse
Try:
fastboot oem rebootRUU
If you churn out the error I mentioned, be prepared to take it in...I had to, I told the guy the truth and he got me a new device...

C:\Users\Ryan>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.043s
So it seems to be a bit different than your device. Its still boot looping the device.

oOflyeyesOo said:
C:\Users\Ryan>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.043s
So it seems to be a bit different than your device. Its still boot looping the device.
Click to expand...
Click to collapse
Did it go into RUU mode after the command or not? I see barely any total time...
Can you side load a custom, if you can get to fastboot run Hasoon's tool and unlock again, even if it says unlock...try to adb side load a custom ROM after you reflash recovery, if it boots then RUU...

Can't you just try running the RUU as an app like right click on the exe. And run as administrator on your computer. I have always done it that way not through CMD. Just seems easier for me and always works I do have my phone in fastboot when I do it. It just takes a long time to actually load maybe my computer bit sometimes I think it didn't work than the program will open and return me back to stock
Edit: just wanna clarify what I mean is run the ruu utility after you extract the zip have you tried that
Sent from my HTCONE using xda premium

It did not reboot into RUU mode. It just restarts the device and tries to boot. Every reboot option, oem lock, and quite a few other commands that try to reboot into the bootloader, just makes it try to reboot into the ROM. I tried to run the RUU this morning before work real fast, it detects the device, see's what version it is, I get all the way to waiting for bootloader, which the RUU tries to reboot into the boot loader, even when I am in the bootloader, tries to reboot into rom, I force it back to the bootloader while its still waiting, but it never seems to detect it in the bootloader.
Seems to be having issues writing, when it did not have issues before, as the rootbox splash screen still comes up from when it was working correctly. I will try to relock and see where I can get tonight and get back to you.
Before my room mate decides to destroy his phone for a insurance claim, since he doesnt want to go back in the store and tell them that another phone is bad... but I couldnt even hard brick it if i wanted to it seems....

[Q] HTC One M7 disaster

Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4138mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.

Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
usb debugging has nothing to do with the bootloader, adb or fastboot, it is only required to be on when you want to mod something or control your phone using adb commands inside a booted rom, as you cant boot, then that's not an option.
if your bootloader is locked and you have warranty, send it back, because if you unlock your bootloader then your warranty will be void and you'll have to pay for repairs.

Hi there & thnx for your concern,
The warranty is not an option , cause I bought it in another country and have no service support here.
For the usb debugging mode , as far as I know , it needs to be "on" so the smartphone can be connected to adb.
I looked on the net how to turn it on without having access to android I got some command but I need an android command-line shell to make it work , wich is not an option right now.
I'm all open for suggestions.

Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .

Rave201 said:
Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .
Click to expand...
Click to collapse
only thing you can do is unlock your bootloader, try again, get a new unlock token from HTC Dev.
by the way, adb commands are only for in a rom or in recovery, use fastboot commands only in the bootloader, if you cant unlock the bootloader then theres not a lot you can do.
could you post your fastboot getvar all please, remove imei and serial number information before posting, maybe there is an RUU we can run.

Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Now try the RUU again

clsA said:
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
lol how I missed that I don't know

Thanks ! : downloading , I'll leave answer after I test.

Hi again ;
So I downloaded and followed the steps I got errors :/
on the RUU flash I got Error 171 at "Bootloader waiting" and later saying that it couldn't connect to the device . It did connect to it in the first place though and device rebooted and so .
So I followed the second parts and I got errors aswell :
Code:
c:\mini-sdk>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.016s]
finished. total time: 0.016s
c:\mini-sdk>fastboot flash zip firmware.zip
sending 'zip' (43508 KB)...
OKAY [ 2.870s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 6.538s
Any help please

anyone ?

Rave201 said:
anyone ?
Click to expand...
Click to collapse
bootloader needs to be locked / relocked to flash the RUU or firmware as your s-on.
"fastboot oem lock" is the command without quotes.

Hi there, I did it already , it says device already locked.

Rave201 said:
Hi there, I did it already , it says device already locked.
Click to expand...
Click to collapse
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?

Seanie280672 said:
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?
Click to expand...
Click to collapse
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up

Rave201 said:
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up
Click to expand...
Click to collapse
what I meant was when fastboot usb is showing, have a look in windows device manager and make sure it see's your phone, should say MyHTC.
only drivers you need which have never let me down, even on Windows 10 is HTC sync manager, just download and install the latest version from the HTC site, I would uninstall all current phone drivers first, then run a cleaner like CCleaner to remove old files, reboot computer then install HTC sync manager, after the install, un-install HTC sync, just leaving HTC driver package above it alone.
make sure your phone is unplugged when doing the above, leave your phone in the bootloader, and when you have finished the last step of un-installing HTC sync, then plug your phone into the computer and let it load the fastboot driver, thats the main one you need right now.

Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?

Rave201 said:
Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?
Click to expand...
Click to collapse
It's a 2 year old phone, it's really only worth fixing if you already have the parts for free.
This phone sells for $149 New in the US, and even cheaper used on eBay.

Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.

Rave201 said:
Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.
Click to expand...
Click to collapse
SD_HW_ERROR = probably a defective emmc. You can't replace the emmc chip, its soldered directly on the Motherboard so you will indeed need to replace the motherboard but like clsA said it really doesnt worth it. You can get a new M7 for 150$. HTC sells their Motherboard around 100$ + you'll probably need to replace the body like many users who tried to open the phone themselves (very fragile around the volume rockers). Even if I love my M7, I wouldn't spent 100$ to replace the MB.
And buying a used motherboard is not a good idea. You don't know if its working good + you don't know if the IMEI is blacklisted.

Thanks for the explanation alray, I excpected the fail in the emmc too cause read_mmc emmc didn't work.
Anway I don't live in the us . Here though, a new one cost roughly 300 $ and the motherboard is about 80$ or less.
Thanks again

Need stock firmware for HTC Desire 510 Cricket variant.

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?

Stuck in fastboot - No running ROM, recovery , ADB

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

Oneplus 3T Stock recovery + Bootloader/OEM locked = Black Screen + White Led

Okay.... who ever fix my mobile I will pay him USD 100/- as reward!!!!!!!!!!
simply unlock my locked OEM ... so i can install OS ... for detail read my old post
old post:
hi everyone, please help me here is what i did :
I switched from stock OS to custom + root ... everything was fine
then I switch back to stock and by mistake after flash stock recovery i run the command "fastboot oem lock" and restart my phone
now i am stuck ... i can access Fastboot + Stock recovery + adb + adb sideload and no OS (it's give me Black screen + White Led)
I tried every thing from A to Z ..... Mega Brick all method / QPST tool / MSM tools 3.6 / 4.0 ..... nothing can help me
then i contact OPO support center they also tried online but no use... they told me that i have to send the device to service center
Bad news for me that there is no service center in this country so they told me to send it to nearest country OPO service center
which cost alot + fixing charges..... i ask for unlock Bootloader & they refuse it... they say sorry this option is for internal use only.
okay now what i need is that some one help me to unlock Bootload / OEM .... via Fastboot Or ADB Shell (engineering mode)
i can access the my internal storage via ADB Shell but i cant do anything ... i can bypass Fastboot OEM lock & install TWRP but i cant boot in TWRP it's give me Black Screen + White LED on
i found a form about OEM lock for MOTO mobile & there customer service unlock it by remotely accessing the phone... by useing command as
"fastboot OEM unlock *XXXXXX (*OEM unlock code)
i dont know wht to do now...please help me :crying:

You say you can access stock recovery and ADB. Why not sideload the full stable stock image? And format the data partition. That should, hopefully, bring you back to normal.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
You say you can access stock recovery and ADB. Why not sideload the full stable stock image? And format the data partition. That should, hopefully, bring you back to normal.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
as i mention i tried ADB sideload to flash stock OS ..no use....
by the way in stock recovery not showing the internal storage too ...when i click it nothing happend

shahabkhan99 said:
as i mention i tried ADB sideload to flash stock OS ..no use....
by the way in stock recovery not showing the internal storage too ...when i click it nothing happend
Click to expand...
Click to collapse
Have you erasing the data partition, including the internal storage?
I can't remember what process is on the stock recovery for doing that, but it may be a factory reset including storage.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Have you erasing the data partition, including the internal storage?
I can't remember what process is on the stock recovery for doing that, but it may be a factory reset including storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
yep... i erased data + system + userdata + case + boot .... no use
i think that the boot path in DEV folder is mislead the system bcz in stock recovery it is not showing any folder under "internal storage" but via adb i can see ... i think custom rom use different installation path & boot address then stock

shahabkhan99 said:
yep... i erased data + system + userdata + case + boot .... no use
i think that the boot path in DEV folder is mislead the system bcz in stock recovery it is not showing any folder under "internal storage" but via adb i can see ... i think custom rom use different installation path & boot address then stock
Click to expand...
Click to collapse
I'm out of ideas.
Sent from my OnePlus3T using XDA Labs

so that's why i need to unlock bootload / OEM "by Hook or by Crook"

What happened when you tried MSMTool?
I had the same issue with my phone but i got it fixed with this tool. Same story with OEM lock, no recovery and no OS on board. Though I had to retry each USB port on my PC to get it done without errors

lShepherdl said:
What happened when you tried MSMTool?
I had the same issue with my phone but i got it fixed with this tool. Same story with OEM lock, no recovery and no OS on board. Though I had to retry each USB port on my PC to get it done without errors
Click to expand...
Click to collapse
MSM tool give me Green DONE ..... i tried MSM from different sites including Oneplus support tried MSM 4.0 by remotely but after restart black screen + white led ..... nothing else

shahabkhan99 said:
MSM tool give me Green DONE ..... i tried MSM from different sites including Oneplus support tried MSM 4.0 by remotely but after restart black screen + white led ..... nothing else
Click to expand...
Click to collapse
Try following steps
While black screen and white LED
1) press volume up + power + home button, hold them till you see fastbook menu
2) go to recovery
3) wipe cache and data
4) see if it helps
Or try flashing fastboot flash boot <file> via ADB
I suppose it might be a hardware issue as well

lShepherdl said:
Try following steps
While black screen and white LED
1) press volume up + power + home button, hold them till you see fastbook menu
2) go to recovery
3) wipe cache and data
4) see if it helps
Or try flashing fastboot flash boot <file> via ADB
I suppose it might be a hardware issue as well
Click to expand...
Click to collapse
tried as above you say.... no use.... BTW fastboot command only work under fastboot
AW can anyone help me to check there device status for OPO 3T via Fastboot command as:
#fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4251000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1a600000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c4e077000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xbc000000
(bootloader) serialno:
(bootloader) kernel:lk
(bootloader) product:msm8996
all:
finished. total time: 0.218s
i wanna see where is the problem

shahabkhan99 said:
yep... i erased data + system + userdata + case + boot .... no use
i think that the boot path in DEV folder is mislead the system bcz in stock recovery it is not showing any folder under "internal storage" but via adb i can see ... i think custom rom use different installation path & boot address then stock
Click to expand...
Click to collapse
Boot doesn't reside on /dev folder, don't mess with that. And no, there is no difference between stock and custom, it doesn't make any sense.
lShepherdl said:
Try following steps
While black screen and white LED
1) press volume up + power + home button, hold them till you see fastbook menu
2) go to recovery
3) wipe cache and data
4) see if it helps
Click to expand...
Click to collapse
This method won't help as the problem is in boot.
OP, are you sure you are actually flashing OP3T files and not OP3? Are you able to flash anything via fastboot at all?
(bootloader) product:msm8996 - this is clearly OP3, OP3T has msm8996pro mine actually shows msm8996 on fastboot
Edit: you can check bootloader status by typing fastboot oem device-info

@przemcio510 thank for the information .... yes i am using MSM for 3T im 100% sure
my bootloader / OEM is lock ..... but via bypassing command i can flash ...system.img + boot + recovery .... etc
but still no use ...also i cann access ADB SHELL in engineering mode other then recovery ADB SIDELOAD bcz i am flashing 4.02 OS .... also i tryied the leatest OS 5 but no use.... i am become crazy now

anyone ..... help me ... to hack crack or unlock the bootloader....please !

@przemcio510
Edit: you can check bootloader status by typing fastboot oem device-info[/QUOTE]
> fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: permissive
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
(bootloader) force_training: false
OKAY [ 0.109s]
finished. total time: 0.109s

let see who is the real HERO
see first post