Database Users

[Q] Bricked? HELP

Hi there. I'm a total newbie at this and all i wanted was some pretty fonts. I rooted my brand new nexus 4 with the CLockwork mod and it was fine. I then installed the Font Installer, and when installing a font i ended up in a bootloop. The phone wouldn't move past the Nexus logo.
I entered recovery mode and cleared the cache, and did a factory reset. I also reformatted the SD card and the system (which i think is where i made a big mistake). When i hit reboot, i ended up at the Google logo, i am not even moving past that now. It's completely stuck.
When i try to go to the bootloader, by powering down (volume down + power) and then vol up + vol down + power vibrate release power -> this usually brings me to the bootloader but now i get Download mode do not unplug the device until the process is complete.
Please help!!
Am i bricked? Is there a way to solve it? Please, please help, i am begging. It's a brand new phone and i probably shouldn't have messed with it but i really don't know what to do and my parents are going to kill me.
PLEASE HELP.

clpw said:
Hi there. I'm a total newbie at this and all i wanted was some pretty fonts. I rooted my brand new nexus 4 with the CLockwork mod and it was fine. I then installed the Font Installer, and when installing a font i ended up in a bootloop. The phone wouldn't move past the Nexus logo.
I entered recovery mode and cleared the cache, and did a factory reset. I also reformatted the SD card and the system (which i think is where i made a big mistake). When i hit reboot, i ended up at the Google logo, i am not even moving past that now. It's completely stuck.
When i try to go to the bootloader, by powering down (volume down + power) and then vol up + vol down + power vibrate release power -> this usually brings me to the bootloader but now i get Download mode do not unplug the device until the process is complete.
Please help!!
Am i bricked? Is there a way to solve it? Please, please help, i am begging. It's a brand new phone and i probably shouldn't have messed with it but i really don't know what to do and my parents are going to kill me.
PLEASE HELP.
Click to expand...
Click to collapse
To get into the bootloader, just hold volume down, and then press and hold power until it vibrates. Now you should be in the bootloader. Just re-flash the system and boot image using fastboot (as per this thread).

efrant said:
To get into the bootloader, just hold volume down, and then press and hold power until it vibrates. Now you should be in the bootloader. Just re-flash the system and boot image using fastboot (as per this thread).
Click to expand...
Click to collapse
Thank you i will try!

Got it working again. Thank you!! Don't think i'll be rooting/flashing again anytime soon that scared the crap outta me. Thank you so much!

clpw said:
Got it working again. Thank you!! Don't think i'll be rooting/flashing again anytime soon that scared the crap outta me. Thank you so much!
Click to expand...
Click to collapse
But it's the best way to learn!! That and lots of reading! Rooting and flashing ROMs and kernels really isn't that difficult. Once you've done it a few times, it'll be second nature. Hell I think a lot of guys here do it in their sleep!

I do feel like i understand the flashing process now before it was all like FLASH WHAT HOW DO I DO THAT?! But exactly what you said, i learnt how to do it and now i feel so accomplished + a staggering sense of relief.
:laugh:

Pardon me, but i have another question. I would like to root the device again using the method described in this thread - http://forum.xda-developers.com/showthread.php?t=2019273 After following the instructions to flash the stock ROM i now have a stock rom installed with an unlocked bootloader, i believe (i did everything but relocking the bootloader) but i don't know what a locked bootloader means. Is it safe for me to go ahead and redo the root now with the unlocked bootloader? I would very much like to use the display control app to modify the colours again.
Again, thank you for your help!

clpw said:
Pardon me, but i have another question. I would like to root the device again using the method described in this thread - http://forum.xda-developers.com/showthread.php?t=2019273 After following the instructions to flash the stock ROM i now have a stock rom installed with an unlocked bootloader, i believe (i did everything but relocking the bootloader) but i don't know what a locked bootloader means. Is it safe for me to go ahead and redo the root now with the unlocked bootloader? I would very much like to use the display control app to modify the colours again.
Again, thank you for your help!
Click to expand...
Click to collapse
just leave your phone's bootloader unlocked.
having a bootloader locked = cant flash custom images (Recovery,radio,etc)
unlocked = ...... well the opposite.
but yeah you can. just if ur phone's bootloader is unlocked (theres a lock on the bottom of the screen as you boot up when it says Google.. if not present it is LOCKED, and in bootloader mode it tells you if u are LOCKED or UNLOCKED) follow that guide and it will bring you on your way.

clpw said:
Pardon me, but i have another question. I would like to root the device again using the method described in this thread - http://forum.xda-developers.com/showthread.php?t=2019273 After following the instructions to flash the stock ROM i now have a stock rom installed with an unlocked bootloader, i believe (i did everything but relocking the bootloader) but i don't know what a locked bootloader means. Is it safe for me to go ahead and redo the root now with the unlocked bootloader? I would very much like to use the display control app to modify the colours again.
Again, thank you for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1995688
^That one is super simple to use. A locked bootloader prevents custom kernels, ROM, and other Mods that people use.

Hmmm, i do have that unlocked logo below my google when i switch on the device, but i suppose that is from the previous time i rooted it. Since the bootloader is already unlocked then, will going through the same steps again cause any problems? Because from what i gather the rooting process unlocks the bootloader + does other stuff.. so now that my bootloader is unlocked, will going through the same steps lead to a complication because it's a duplicate step?
Thanks!!

Ace42 said:
http://forum.xda-developers.com/showthread.php?t=1995688
^That one is super simple to use. A locked bootloader prevents custom kernels, ROM, and other Mods that people use.
Click to expand...
Click to collapse
NO! He said he want's to learn. A toolkit does not teach one a damn thing!

El Daddy said:
NO! He said he want's to learn. A toolkit does not teach one a damn thing!
Click to expand...
Click to collapse
Am a girl. But yes. I do wanna learn.

clpw said:
Am a girl. But yes. I do wanna learn.
Click to expand...
Click to collapse
Ha sorry. 95% of the time its a "He" around here.
The best way to learn is to study the process efrant linked originally.
Also go through his Nexus 4 101 guide which is also a sticky in the general section. It contains a ton of great info. Efrant did a great job putting it together.
Sent from my Nexus 4

El Daddy said:
Ha sorry. 95% of the time its a "He" around here.
The best way to learn is to study the process efrant linked originally.
Also go through his Nexus 4 101 guide which is also a sticky in the general section. It contains a ton of great info. Efrant did a great job putting it together.
Sent from my Nexus 4
Click to expand...
Click to collapse
Will do! Thanks!

El Daddy said:
NO! He said he want's to learn. A toolkit does not teach one a damn thing!
Click to expand...
Click to collapse
I don't recall reading that part, sorry I skimmed.

Ace42 said:
http://forum.xda-developers.com/showthread.php?t=1995688
^That one is super simple to use. A locked bootloader prevents custom kernels, ROM, and other Mods that people use.
Click to expand...
Click to collapse
Actually, on this device, assuming you have root, you can still flash custom kernels and ROMs even with a locked bootloader.
And yeah, as El Daddy mentioned, you learn a lot more by doing things yourself, without scripts and toolkits. See the link in El Daddy's sig for more info.
Sent from my Nexus 4 using Tapatalk 2

efrant said:
Actually, on this device, assuming you have root, you can still flash custom kernels and ROMs even with a locked bootloader.
And yeah, as El Daddy mentioned, you learn a lot more by doing things yourself, without scripts and toolkits. See the link in El Daddy's sig for more info.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I think I have learned enough for now, but I didn't know the N4's loader allowed changes even when locked(guess you really do learn everyday haha). The manual way is not always suitable for someone like myself, when I first got this thing I was eager to jump straight into mods. And I read Dad's rant so I understand why you guys aren't fans of automatic methods. However if you are already knowledgeable on the topic then what's it gonna hurt to try the toolkit.

[ROOT][UB] Xperia Z all version included 4.3 - 12 step easy.

Hi guys this method works with any version. Very easy to follow.
I have done the following:
1) Unlock bootloader (first make a backup).
2) Download SuperSu.zip and copy in memory. (Last version http://download.chainfire.eu/supersu)
3) Download fastboot.rar and extract. (fastboot.rar inlcudes boot.img (doomkernel) for flash).
4) Place fastboot folder in C:
5) Open cmd (from start) and go to C:/fastboot
6) Plug phone in fastboot mode (shoutdown and press Vol + and plug usb).
7) In cmd write "fastboot flash boot boot.img" at the end "fastboot reboot".
8) Enter in recovery pressing vol + or vol - when phone booting and led is coloured.
9) Flash supersu.zip. Unplug usb.
10) After go in advanced and shoutdown phone (NOT RESTART).
11) Flash ONLY stock kernel of your firmware with flashtool. Reboot.
12) Relock bootloader.
Fastboot.rar
https://mega.co.nz/#!U5pkQQ6T!5YAVu3VOwpTSg-WH5aE6djJOKF3ilfg_R-JEBoJ25cM
Sorry for my bad english.
I did everything in less than 10 minutes.
This is a guide made ​​by me. Then tested and working also with last 4.3 10.4.1.B.0.101.

Useful, but somebody already made a very similar guide -
http://forum.xda-developers.com/showthread.php?t=2590781
Sent from my C6603 using Tapatalk

you forget to put backup TA step I think. Because without restoring TA, the low-light camera quality will be reduced.

Somehow between step 10 and 11 my phone automatically rebooted while I getting ready to flash the stock kernel. Maybe I wasn't in the right mode and plugged / unplugged the USB cable. Either way, my phone restarted when I didn't intend it to. I believe when this happened my phone was reset to like-new.
I did lose all data / settings / etc. The backup and restore functionality of the Sony PC Companion seems to be crap in this situation and I'm not sure just what might be useful about it.
Just an FYI to others who might try this.

colacin said:
Somehow between step 10 and 11 my phone automatically rebooted while I getting ready to flash the stock kernel. Maybe I wasn't in the right mode and plugged / unplugged the USB cable. Either way, my phone restarted when I didn't intend it to. I believe when this happened my phone was reset to like-new.
I did lose all data / settings / etc. The backup and restore functionality of the Sony PC Companion seems to be crap in this situation and I'm not sure just what might be useful about it.
Just an FYI to others who might try this.
Click to expand...
Click to collapse
AFAIK unlocking the bootloader factory-resets the phone. making and restoring a backup, including TA, should be step 0 and 13

colacin said:
Somehow between step 10 and 11 my phone automatically rebooted while I getting ready to flash the stock kernel. Maybe I wasn't in the right mode and plugged / unplugged the USB cable. Either way, my phone restarted when I didn't intend it to. I believe when this happened my phone was reset to like-new.
I did lose all data / settings / etc. The backup and restore functionality of the Sony PC Companion seems to be crap in this situation and I'm not sure just what might be useful about it.
Just an FYI to others who might try this.
Click to expand...
Click to collapse
Unplug USB and when you flashed supersu.zip you had to turn off the phone from recovery.
Then go to step 11
Coirpre said:
AFAIK unlocking the bootloader factory-resets the phone. making and restoring a backup, including TA, should be step 0 and 13
Click to expand...
Click to collapse
I unlock bootloader with flashtool and I do not lose anything.
When restores TA partition is not made no wipe.

kingvortex said:
Useful, but somebody already made a very similar guide -
http://forum.xda-developers.com/showthread.php?t=2590781
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Similar not equal.

Please stop this unlocked bootloader root posts, they are useless.
If you got unlocked bootloader you can root when ever you want, that is not a talent.
If you got any solution for locked bootloader, then speak, or remain your silence...
Sent from my C6603 using Tapatalk

eryen said:
Please stop this unlocked bootloader root posts, they are useless.
If you got unlocked bootloader you can root when ever you want, that is not a talent.
If you got any solution for locked bootloader, then speak, or remain your silence...
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
I don't think the OP was claiming any particular talent - this is simply a step-by-step guide - and there are countless other posts of this sort for various other purposes. Sure, he could have put UNLOCKED BOOTLOADER in the title and that way you wouldn't have read it.

eryen said:
Please stop this unlocked bootloader root posts, they are useless.
If you got unlocked bootloader you can root when ever you want, that is not a talent.
If you got any solution for locked bootloader, then speak, or remain your silence...
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
If you want to follow the guide, good. Then nothing. I have done some work to help the forum. If you unlock the bootloader after you relock. It took me 10 minutes to do all this. For unlock andrelock takes 2 minutes.
I do this to also help users to root their phone.
At the end of unlocking the bootloader will not void your warranty if you re-lock at the end of the guide.
I could agree with you if you were a moderator.
Are you a home user who wants to increase their own posts on the forum.
Please do not offend people who want to help the forum. Thank you.
colacin said:
I don't think the OP was claiming any particular talent - this is simply a step-by-step guide - and there are countless other posts of this sort for various other purposes. Sure, he could have put UNLOCKED BOOTLOADER in the title and that way you wouldn't have read it.
Click to expand...
Click to collapse
Thanks.

First, nobody needs to be a moderator to comment on a thread/post. This is the second time I've seen someone say this in 24 hours. It's a strange attitude.
Having said that, I've some suggestions to make -
1. Change your thread title to reflect that an unlocked bootloader is required.
2. Remove the part where you say that data will not be lost, as unlocking the bootloader wipes data and sdcard. This is quite important, as it seems somebody already lost their data following this guide.
3. You should mention that DRM keys should be backed up by backing up the TA partition before unlocking the bootloader to prevent their permanent loss and loss of warranty.
http://forum.xda-developers.com/showthread.php?t=2292598
4. Linking to the thread or at least crediting the creator of whichever boot.img you're using would also be polite or indeed essential.
5. A direct link to Chainfire's site, where the latest version of SuperSu is available would be better than attaching whatever version you have lying around, as security fixes may be made at any time.
http://download.chainfire.eu/supersu
Sent from my C6603 using Tapatalk

kingvortex said:
First, nobody needs to be a moderator to comment on a thread/post. This is the second time I've seen someone say this in 24 hours. It's a strange attitude.
Having said that, I've some suggestions to make -
1. Change your thread title to reflect that an unlocked bootloader is required.
2. Remove the part where you say that data will not be lost, as unlocking the bootloader wipes data and sdcard. This is quite important, as it seems somebody already lost their data following this guide.
3. You should mention that DRM keys should be backed up by backing up the TA partition before unlocking the bootloader to prevent their permanent loss and loss of warranty.
http://forum.xda-developers.com/showthread.php?t=2292598
4. Linking to the thread or at least crediting the creator of whichever boot.img you're using would also be polite or indeed essential.
5. A direct link to Chainfire's site, where the latest version of SuperSu is available would be better than attaching whatever version you have lying around, as security fixes may be made at any time.
http://download.chainfire.eu/supersu
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
1) ok.
2) I myself have done everything ... and I have not lost ANYTHING. was wrong in the user process. It is not my fault.
3) I think it was a logical thing.
4) DooMkernel.
5) thank you.
6) I will never do anything to help this forum. I know it will not matter anything to anyone, but a small contribution had a lot to me.

I have in no way lessened your contribution by what I posted, neither did I intend to. As you will see, I already said your post was useful. They were simply suggestions to make your guide better. No need to get upset about it.
As for not losing data, I'm sorry, but you're wrong about this. Unlocking the bootloader on this device wipes both /data and the internal SD card. There was no user error.
See the warning in DooMLoRD's guide - http://forum.xda-developers.com/showthread.php?t=2153261
Please just remove the part that falsely states that data will not be lost or I'll have to ask a moderator to do it as it's not fair on inexperienced users that may lose their data when following this guide.
No malice intended, only the intention of correct information being posted.
By their very nature, guides are followed by less experienced users, so the information in them must be correct and complete. Even if backing up DRM keys is a logical step to you, a new user may not even know about it.
Sent from my C6603 using Tapatalk

Ok first off, if you haven't anything constructive to say then don't say anything at all. Users helping other users is what makes XDA a pleasant place for developers and users alike.(this is not directed at the OP)
Also I have added a warning about data being wiped when unlocking the bootloader to the OP.
A backup is required as unlocking the bootloader on this device wipes both /data and the internal SD card
@djnino4style, @kingvortex was only making suggestions to help this thread and you, if it was criticism it was constructive. We do appreciate guides which could help new users so do not think we are getting at you.
Thanks again,

wedgess said:
Ok first off, if you haven't anything constructive to say then don't say anything at all. Users helping other users is what makes XDA a pleasant place for developers and users alike.
Also I have added a warning about data being wiped when unlocking the bootloader to the OP.
A backup is required as unlocking the bootloader on this device wipes both /data and the internal SD card
@djnino4style, @kingvortex was only making suggestions to help this thread and you, if it was criticism it was constructive. We do appreciate guides which could help new users so do not think we are getting at you.
Thanks again,
Click to expand...
Click to collapse
Ok delete this thread. Thanks.

djnino4style said:
Ok delete this thread. Thanks.
Click to expand...
Click to collapse
I think you misunderstand my intentions and the moderator's post above.
Nobody is getting at you here. My posts are simply constructive criticism intended to make your guide more complete. Nothing more.
Nobody is saying that your guide is no good or that it needs to be closed or removed.
Put simply; chill out, friend.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kingvortex said:
I think you misunderstand my intentions and the moderator's post above.
Nobody is getting at you here. My posts are simply constructive criticism intended to make your guide more complete. Nothing more.
Nobody is saying that your guide is no good or that it needs to be closed or removed.
Put simply; chill out, friend.
Click to expand...
Click to collapse
Words of wisdom as always @kingvortex

Thanks. I try my best hahaha.

thanks buddy. its a;; thanks to you,doomlord androxyde i have succesfully rooted my device...
thanks...

The problem with this thread is that they mention it's a root methods for Xperia z 4.3, and they are talking of backing up TA partion which is not possible without rooting the device. In that case you will have to downgrade to 4.1 or 4.2.
Dear it's not possible till now to back up TA partition in uprooted 4.3' so useless step.
If you want to root 4.3, u must downgrade otherwise u gonna loose TA partition and hence, warranty, dry keys, ba2 forever. Never think of recovering these and relocation,
So please correct the title or make suggestion to downgrade.

Guide: How to bootloader unlock your Honor 5X (official and unofficial methods)

All Honor devices currently shipped with a locked bootloader. As long as manufacturers provide a way to unlock, then we're down with that - it helps keep your device secure and means that if you lose it, it's harder for people to steal your data (the process of unlocking the bootloader wipes the phone).
There are two ways to unlock your Honor phones bootloader, which will then allow you to install things like custom recoveries, custom kernels / ROMs etc. The first is using the official Honor method, which is free, and the second is using a third party, which costs €4 Euros, but may be the quickest option if the official method isn't working for you.
The official method
In order to unlock your Honor device using the official method, complete the following steps:
Visit https://www.emui.com/en/plugin.php?id=unlock&mod=detail and either create a new account or login with an existing Huawei account.
In the form displayed after logging in, enter:
Your phone model (KIW-L21 for the Honor 5X)
Your phone serial number (this can be found in Settings -> About -> Status)
Your phone IMEI1 (this can be found in Settings -> About -> Status)
Your phone product ID (to find this, open the dialler and enter *#*#1357946#*#*)
The captcha code
Press the 'Submit' button.
At this point you will either be provided with a code, or you will receive an error such as 'The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.' If you get the error, you will need to use the unofficial method below.
Open a command window on your PC / Mac, which needs to have 'adb' and 'fastboot' installed from the Android SDK.
Enable USB debugging by tapping the build number in Settings -> About 5 times, then going back and selecting the option from the Development menu.
Enable OEM unlock in the Development menu.
Connect your phone to the PC and approve the security prompt on the device screen.
In the command window on your PC / Mac, enter 'adb reboot bootloader' to enter fastboot mode'.
In the command window on your PC / Mac, enter 'fastboot oem unlock [insertnumberhere]', of course using the number provided by the Huawei site.
YOUR PHONE WILL WIPE ITSELF AT THIS POINT!
That's it! You're done!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The unofficial method
In order to unlock your Honor device using the unofficial method, if for example you receive the '14 day' error from the Huwei site, complete the following steps:
On a Windows PC, download and install DC-unlocker from https://www.dc-unlocker.com/.
On your phone, enter Manufacturer Mode - open the dialler and enter *#*#2846579#*#*. In the app that then opens, select Project Menu -> Background settings -> USB ports settings -> Manufacturer Mode.
Download the Huawei driver pack from https://files.dc-unlocker.com/share.html?v=share/88D4A98C154D4E19AF9D4A1EF09BA620.
Install the Huawei driver pack by extracting the file you just downloaded (using WinRAR or similar) and running 'DriverSetup'
After installing the driver pack, connect your phone to the PC. In Device Manager, after the automated driver install, you should have no 'Unknown Devices'.
Launch the previously downloaded DC-unlocker application.
From the drop down lists, select 'Huawei Phones' and 'Auto Detect Model'.
Press the magnifying glass icon - the app will then search for your phone.
You should see an image like the one below showing your phone is found. At this point, press the 'Buy Credits' option to set up your DC-Unlocker account and purchase the 4 credits required for code retrieval (this will cost €4). You can also do this directly from the DC-Unlocker website.
After your credit purchase is complete, click the 'Server' section and enter your new DC-unlocker login details. Press 'Check Login' to validate the details (if the server is busy, this may take multiple attempts).
Click the 'Unlocking' section, and click 'Read Bootloader Code'. Do NOT click 'Unlock'. Again, if the server is busy, this may take multiple attempts. The white area of the app will now display the bootloader code. Screen grab this just in case!
Open a command window on your PC, which needs to have 'adb' and 'fastboot' installed from the Android SDK.
Enable USB debugging by tapping the build number in Settings -> About 5 times, then going back and selecting the option from the Development menu.
Enable OEM unlock in the Development menu.
Connect your phone to the PC and approve the security prompt on the device screen.
In the command window on your PC / Mac, enter 'adb reboot bootloader' to enter fastboot mode'.
In the command window on your PC / Mac, enter 'fastboot oem unlock [insertnumberhere]', of course using the number provided by the DC-Unlocker process.
YOUR PHONE WILL WIPE ITSELF AT THIS POINT!
That's it! You're done!

by unlocking the bootloader with official method, will i lose warrenty ? will i get OTA update ?

hanu_blr said:
by unlocking the bootloader with official method, will i lose warrenty ? will i get OTA update ?
Click to expand...
Click to collapse
Unlocking the bootloader will not void your warranty, and yes you will get OTAs
If you flash a custom recovery and root, THAT will void your warranty and you will not be able to get OTAs unless you relock the bootloader and go back to stock everything

Inpain said:
Unlocking the bootloader will not void your warranty, and yes you will get OTAs
If you flash a custom recovery and root, THAT will void your warranty and you will not be able to get OTAs unless you relock the bootloader and go back to stock everything
Click to expand...
Click to collapse
U can still get OTAs with unlocked bootloader?

paulobrien said:
[*]In the command window on your PC / Mac, enter 'adb reboot bootloader' to enter fastboot mode'.
[*]In the command window on your PC / Mac, enter 'fastboot oem unlock [insertnumberhere]', of course using the number provided by the Huawei site.
Click to expand...
Click to collapse
For Linux users (Mint 17.3 in my case), right after adb reboot bootloader, watch when the phone restarts, I had to unplug usb cable.
Only then my phone was recognized with sudo fastboot devices. After plugging the cable back in, ofcourse.
It was also nowhere to be found in lsusb.
Before that I could not do fastboot oem unlock..
EDIT: Just flashed TWRP, problem seems to be in front usb panel on my pc case.
When I plug phone in the back of my pc, works fine.

Hey Paul, many thanks for the tip (and your wealth of contributions over the years)!
Can you comment on how pernicious the server busy thing is with DC Unlocker?

It's annoying, but persist and it's fine.
P
Sent from my HUAWEI NXT-L29 using Tapatalk

Inpain said:
Unlocking the bootloader will not void your warranty, and yes you will get OTAs
If you flash a custom recovery and root, THAT will void your warranty and you will not be able to get OTAs unless you relock the bootloader and go back to stock everything
Click to expand...
Click to collapse
Are you sure?? Unlocking bootloader will not void your warranty ??
This attach pic is from official huwei support !!! Read the last lines

For those who don't reach the US unlock site: just use chrome to translate the asian site and get the unlock code from there. It works fine!

sachoosaini said:
Are you sure?? Unlocking bootloader will not void your warranty ??
This attach pic is from official huwei support !!! Read the last lines
Click to expand...
Click to collapse
Of course it voids your warranty

Zakaria.R said:
Of course it voids your warranty
Click to expand...
Click to collapse
It know that... But assuming that he don't know so I quoted him

sachoosaini said:
It know that... But assuming that he don't know so I quoted him
Click to expand...
Click to collapse
Yeah I got you there, I was solidifying your point, there aren't many oems that are developer friendly out there, so yes you can unlock the bootloader and you can receive otas but that's pretty much it, that's why many users relock it before taking their phones to customer service.

sachoosaini said:
Are you sure?? Unlocking bootloader will not void your warranty ??
This attach pic is from official huwei support !!! Read the last lines
Click to expand...
Click to collapse
The last lines say that you will be held accountable for things broken as a result of unlocking your bootloader - (and I quote) in the event that it cannot be recovered.
That's pretty standard language and it doesn't say specifically that "unlocking your bootloader voids your warranty" - because consumer protection laws vary a lot by country.
It does say that if you brick your phone and it can't be recovered you're going to be charged.
Anything that can be disputed in a gray area they'll probably put on you. But I don't know that because I'm not a lawyer and if I were, I'm not your lawyer.
~~~~~
Meanwhile, after weeks of having even the Chinese site time out on one of my other Huaweis (my honor5x is already unlocked) I tried DC Unlocker and it worked just fine - five of my friends tried it and they're happy too. Many thanks for the tip, Paul!

Zakaria.R said:
Yeah I got you there, I was solidifying your point, there aren't many oems that are developer friendly out there, so yes you can unlock the bootloader and you can receive otas but that's pretty much it, that's why many users relock it before taking their phones to customer service.
Click to expand...
Click to collapse
EarlyMon said:
The last lines say that you will be held accountable for things broken as a result of unlocking your bootloader - (and I quote) in the event that it cannot be recovered.
That's pretty standard language and it doesn't say specifically that "unlocking your bootloader voids your warranty" - because consumer protection laws vary a lot by country.
It does say that if you brick your phone and it can't be recovered you're going to be charged.
Anything that can be disputed in a gray area they'll probably put on you. But I don't know that because I'm not a lawyer and if I were, I'm not your lawyer.
Click to expand...
Click to collapse
Well yeah brother you are right.
Now second thing, except very rare case like HTC are unlocked by revolutionary methods apart from HTC dev, and being a device most of em apart from 2-3 each and every company which provides official way of unlocking does not support opening bootloader without voiding warranty. Once you go to official way you probably loose warranty except some developer edition devices. So there is no need to be my lawer lol...

sachoosaini said:
Well yeah brother you are right.
Now second thing, except very rare case like HTC are unlocked by revolutionary methods apart from HTC dev, and being a device most of em apart from 2-3 each and every company which provides official way of unlocking does not support opening bootloader without voiding warranty. Once you go to official way you probably loose warranty except some developer edition devices. So there is no need to be my lawer lol...
Click to expand...
Click to collapse
Even HTC has replaced my phone with an unlocked bootloader by their site, carrier version, not developer - so these guys can do whatever they want.

What the ****... I get the message "The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.".
Damn this difficult phone.

rumsey said:
Damn this difficult phone.
Click to expand...
Click to collapse
Read forum on that issue.
I had imei imeiid error on mine & all details input 100% correct so had either email huawei 100 times in hope get 1 response or use dc locker. dc locker is easy option although costs you 4 euro :-/ ...
Huawei main drw back is poor support & sloppy software

Zakaria.R said:
Yeah I got you there, I was solidifying your point, there aren't many oems that are developer friendly out there, so yes you can unlock the bootloader and you can receive otas but that's pretty much it, that's why many users relock it before taking their phones to customer service.
Click to expand...
Click to collapse
How to relock bootloader on Huawei Honor 5x ( L21,22,24) ?

kartrikpal said:
How to relock bootloader on Huawei Honor 5x ( L21,22,24) ?
Click to expand...
Click to collapse
I guess with the command "fastboot oem relock" and you must be on stock rom and stock recovery, but please ask others as well just to make sure that's the way.

Arobase40 said:
To relock the phone you can re flash a stock firmware but that doesn't change anything as you'll get a "relocked" status when the normal bootloader status should be "locked".
So Honor/Huawei will know if the bootloader has been modified or not...
Click to expand...
Click to collapse
Could you redirect me to some page or site that say you can relock by flashing stock firmware ? Because I've never heard of this, I for one have many times flashed stock firmware and it didn't relock my phone (not on the Honor 5x though) so if you could give me a link or something, would be nice..

About disabling "Secure Boot" (S-ON) on the N5X.

Secure Boot (aka S-ON, aka other names) is the responsible for checking and validating the entire chain of trust from the psychical bootloader (BootRom) to the Android Bootloader (aboot). From there on, validating boot.img (kernels) and recoveries are checked via the lock/unlock state of the device, and validating system is duty of the Verified Boot (dm-verity) feature on the kernel.
Unlike the old days with the Nexus One and its S-OFF achievement (for reformatting the nand and others), I haven't seen any S-OFF or bootloader/radio development on any Nexus device from that point. Has been any exception for the N5X for some rare chance?
I know that disabling Secure Boot wouldn't be much useful considering there doesn't seem to be any radio or bootloader development at all, but the truth is that without the chance to flash and test it no development can appear from the nothing either. I honestly do not have any idea if by chance secure boot was disabled, anyone will jump into developing a better radio or more feature rich bootloader..
Just wondering, has this been ever attempted or anything? It seems that any HTC is attacked in this sense, but others aren't, even if Nexus are considered development freely, the truth is that they're all S-ON by default and no development of a radio or a bootloader seems to be in place ever. If It was able to happen with the Nexus One, why not for latter nexus devices?
And I don't agree to the point of "we don't need Secure Boot disabled because we would be able to really brick our Nexuses!!", because you can still brick any nexus by flashing any (signed) bootloader or radio from another device, for example N5 bootloader into a N5X (and a ton of more examples with other signed images, and let's not talk about inside android with root.. literally the first Nexus 5/5X were bricked by kernel auto uploaders because they had hardcoded the partition for the kernel, and it happened to be the bootloader one on the new device..). The S-ON check is only to guarantee you don't flash unauthorized stuff from the point of view of Google, not for your security of not bricking the device at all.

Agree
Sent from my Pixel using Tapatalk

there is really no point here because we can actually flash anything without any problem...
on htc devices (I had last 5 year's flagships, so I know something about it) you need it to flash unsigned factory images, zips with firmware files, change your phone's id and in some cases (htc one x) even flash a kernel from recovery! yes, you had to flash manually boot.img every time you change kernel/rom
but here...really....no need, unless some really crazy guy wants to make a bootloader from scratch and load something like windows phone

throcker said:
there is really no point here because we can actually flash anything without any problem...
on htc devices (I had last 5 year's flagships, so I know something about it) you need it to flash unsigned factory images, zips with firmware files, change your phone's id and in some cases (htc one x) even flash a kernel from recovery! yes, you had to flash manually boot.img every time you change kernel/rom
but here...really....no need, unless some really crazy guy wants to make a bootloader from scratch and load something like windows phone
Click to expand...
Click to collapse
I agree on that we don't "need" it for basic rom flashing stuff, but your last line defines why it would be awesome to have it. It would give out options not only to "boot Windows", but also add features to the bootloader, repartition as we please (reduce system partition after debloating), adding a mechanism to prevent any bricking by adding a safe first bootloader sequence (like it was done for the N7 2012, via nv flashing if I don't remember bad), stuff like removing the damn bootloader unlock orange or other warnings (not only changing the images but also deleting the damn timeouts at boot), being able to add passwords for bootloaders, and a ton more **** could be done.
And let's not talk about "Radios". That garbage partition is a GIANT security hole and for the worse it boots BEFORE the main cpu and controls everything, from the application cpu to the memory it's using. Literally the radio controls the phone, it's the most important partition, it's FULL of backdoors (like the Replicant guys demonstrated for the Nexus S/Galaxy S2), it's FULL of unintended security holes (because no one develops for it decently, there have been some hacking conferences having fun at them) and it's the worst we all having running on the phone right now. It doesn't matter your Android Version or security patch date, you have security holes that date from years ago opened and being probably exploited by goverments as we speak.
There are great devs around, the bootloaders are usually decompiled to find exploits to be unlocked, for S-OFF and a lot of stuff. I'm sure people could jump on radio cleaning and fixing. There is a great community and great potential unused.
Until we fix the radio and the BL, "our" N5X is not our phone. Secure Boot should be killed and development would take place.

Really interesting ! Thanks

Aww, no one is interested in this .
Sometimes I wish that the Nexus weren't so unlocked and that we would need S-OFF to even flash custom roms, so a lot more development would appear, like it did for the Nexus One.

Well, I really dont see such a point of locking down the choice. If I buy something, then its mine. So what I do with mine should really be mine choice, dispite warranty. If I break it, its still mine.
Sent from my Pixel using Tapatalk

jugoslavpetrovic said:
Well, I really dont see such a point of locking down the choice. If I buy something, then its mine. So what I do with mine should really be mine choice, dispite warranty. If I break it, its still mine.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yes, this is the point, but we are accepting nowdays devices that are full-locked except some partitions for us to play with. All is good while the bootloader is completely locked on and the radio is even more untouchable, literally making everyone able to spy on us.
The funniest part is that only "we", the users, are locked. Because I am expecting malware to grow up to the point that it will be able to get root, then unlock, then turn secure boot OFF, and then overwrite the bootloader and radio in a ransomware form blocking the boot of the device until payment is done or something like that.

RusherDude said:
Yes, this is the point, but we are accepting nowdays devices that are full-locked except some partitions for us to play with. All is good while the bootloader is completely locked on and the radio is even more untouchable, literally making everyone able to spy on us.
The funniest part is that only "we", the users, are locked. Because I am expecting malware to grow up to the point that it will be able to get root, then unlock, then turn secure boot OFF, and then overwrite the bootloader and radio in a ransomware form blocking the boot of the device until payment is done or something like that.
Click to expand...
Click to collapse
Exactly. Scary. That reminded me of a movie I have seen recently called Zero Day.
Sent from my Pixel using Tapatalk

jugoslavpetrovic said:
Exactly. Scary. That reminded me of a movie I have seen recently called Zero Day.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I wonder if it's as easy as flipping some bits like for unlocking bootloader..
@segv11 @osm0sis , hey guys! you both worked for BootUnlocker, so you may know something about this : do you know if a value is stored in memory to control "Secure Boot enabled" or "Secure boot disabled" like for bootloader locked or unlocked? Have you ever found this or something related by accident? Thanks!

RusherDude said:
I wonder if it's as easy as flipping some bits like for unlocking bootloader..
@segv11 @osm0sis , hey guys! you both worked for BootUnlocker, so you may know something about this : do you know if a value is stored in memory to control "Secure Boot enabled" or "Secure boot disabled" like for bootloader locked or unlocked? Have you ever found this or something related by accident? Thanks!
Click to expand...
Click to collapse
Don't think so.. that's all secure bootchain stuff.. some is open source and some is not.
Google the following: lk bootloader
That's what the LG devices use if I recall correctly. Checking out some of the public source will be your best bet of finding if it even possibly can be disabled.

osm0sis said:
Don't think so.. that's all secure bootchain stuff.. some is open source and some is not.
Google the following: lk bootloader
That's what the LG devices use if I recall correctly. Checking out some of the public source will be your best bet of finding if it even possibly can be disabled.
Click to expand...
Click to collapse
Thanks a lot for the input! I think it can be disabled because apparently some N5 users made it, and considering that the N5 is the N5X's brother from LG, it should be doable too:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image is from http://bbs.gfan.com/android-7753460-1-1.html , apparently a chinese site about a tool? for disabling secure boot? no idea honestly
So it probably is doable on N5X too, the question is how . If its a bit flip for unlock, it is probably just another value for secure boot, I wonder if adjacent to the unlock one or something like that. I'll search for lk bootloader stuff but I have not the bootloaders knowledge (or tools like IDA2 pro to get it done anyway, which sucks ) for making it anyway
Thanks a lot!

I definitely think it can be disabled and I found some rather interesting things by reading up on a site, where someone has actually spent time reverse engineering what's most likely a signed and compiled version of ABoot (LK Bootloader). I thought it was interesting as it covers the actual process of disassembling the image, which may expose the values that need to be changed to actually achieve a true state of disabled secureboot.
http://newandroidbook.com/Articles/aboot.html
What worries me however, is if the signature is checked upon flashing, as if that's the case then replacing the bootloader may in fact be next to impossible. I'm not all that interested to try it out either, as I simply don't want to risk ending up with a hardbricked phone as that wouldn't be all that great so to say. However, if someone is successful making a patch that really works and release it, I'll definitely give it a go after it has been comfirmed to work.

Doenms't the PixelROM flash a custom bootloader?
So what's the "fastboot unlock bootloader" command for?

LazerL0rd said:
Doenms't the PixelROM flash a custom bootloader?
So what's the "fastboot unlock bootloader" command for?
Click to expand...
Click to collapse
No it doesn't.
Unlocking the bootloader is the ability to ask the bootloader it self to boot a different/custom rom.

scr60 said:
No it doesn't.
Unlocking the bootloader is the ability to ask the bootloader it self to boot a different/custom rom.
Click to expand...
Click to collapse
Well, actually it does. It's using the Google Pixel Bootloader. Check is files. It's a custom bootloader.

LazerL0rd said:
Well, actually it does. It's using the Google Pixel Bootloader. Check is files. It's a custom bootloader.
Click to expand...
Click to collapse
It's not a custom bootloader, it only changes the imagdata, the graphical aspect of it that you see when the phone boots. Iit's far from being a custom bootloader

Gr0vk said:
It's not a custom bootloader, it only changes the imagdata, the graphical aspect of it that you see when the phone boots. Iit's far from being a custom bootloader
Click to expand...
Click to collapse
Okay. Thank you for correcting me there!

LazerL0rd said:
Okay. Thank you for correcting me there!
Click to expand...
Click to collapse
Should exist more people like you on the internet

I haven't been able to find a way. Probably have to burn your own bootloader onto the emmc board.

[Root && Unlock] Droid Turbo 6.0.1 mcg24.251-5-5

@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
fastboot oem config fsg-id " "
Click to expand...
Click to collapse
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.

jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.

ChazzMatt said:
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
Click to expand...
Click to collapse
mcg24.251-5-5

Fantastic. Yeah, I figured that had to be typo.
Will make a lot of people happy.

I will try now

KARIM9377 said:
I will try now
Click to expand...
Click to collapse
Yes, great news, right?

jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?

TheSt33v said:
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
Click to expand...
Click to collapse
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.

Oh My Lord. @jcase and @autoprime do it again! Even though mine is unlocked my replacement 32gb isnt and this may make me buy a new screen for it to use! Looks like i know what im doing on my day off tomorrow. Transplanting this screen back onto its orginal donor and unlocking that sucker

autoprime said:
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Click to expand...
Click to collapse
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?

TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
no, pressing volume down or vol dwn + pwr should not interfere with sunshine.
whichever method people find easier.. i'd assume not everyone will be able to catch it on the initial reboot after sunshine completes.
i'd just avoid pressing buttons while sunshine is still running.. but once the screen shuts off have at it.
also, not sure how it is with the turbo but on my g4 play i do not have to force a 'power down' while phone is in bootloop. i just wait for bootloop cycle to turn screen off and then quickly press the button combo to go into fastboot (volume down + power for g4 play).

Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****

FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
killer520 said:
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
Click to expand...
Click to collapse

ChazzMatt said:
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
Click to expand...
Click to collapse
Those instructions were in autoprime's OP, so they did make it into my guide.

need more help
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one

KARIM9377 said:
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
Click to expand...
Click to collapse
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.

TheSt33v said:
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
Click to expand...
Click to collapse
thanks for your help
can you please update the TWRP

KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.

KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
What @TheSt33v said.
This link is to the most recent TWRP with @bhb27 mods for our Quark phones. @bhb27 is our official TWRP maintainer. He's why our TWRP has official status. But he also builds personalized versions which include some features/mods for our phones that other TWRP versions do not have, mods specifically for our Quarks. His modded versions are always better than the versions on the TWRP website (which again are only there due to his efforts).
On that page below you want the modded TWRP with the most recent date -- will always be the one listed at the bottom.
https://www.androidfilehost.com/?w=files&flid=39562

need help
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
i need stack firmware to flash it with my locked droid turbo xt1254 MCG24.251-5-5 with tool to falsh it