Related
I am sorry, I am a Noob, but I learn quick. I also have to post in the noobie forums for a while until I can grow some gills so here goes...
The goal - to install Clockwork Mod Recovery on my SGP312 running 4.2.2 (10.31.1.C.0.136)
Where I am at in the process - my tablet is rooted.
From what I have read, I am lead to believe that ROM Manager can't install just CWM because the recovery boot process on Sony tablets is integrated into the kernel. So I think I need to use adb to get into fastboot mode and flash a boot.img that contains CWM. I also believe that you can't flash a kernel with a locked bootloader. Am I correct so far?
At this juncture I only want to get CWM installed, I'm not ready to actually install an entire ROM yet. "One step at a time grasshopper"
Ideally, I would like to get CWM installed before I unlock my bootloader so that I can make a backup and return to a locked bootloader config if I ever have the need to.
So my question is this: Is there a way to get CWM onto my tablet without unlocking the bootloader? If what I would prefer isn't possible is following and using the boot.img in this thread the next best way of proceeding?
http://forum.xda-developers.com/show....php?t=2433466
Thanks everyone for a) putting up with such a basic set of questions, b) helping me become less of a Noob and c) helping me accomplish what I need to get done.
dph3055 said:
I am sorry, I am a Noob, but I learn quick. I also have to post in the noobie forums for a while until I can grow some gills so here goes...
The goal - to install Clockwork Mod Recovery on my SGP312 running 4.2.2 (10.31.1.C.0.136)
Where I am at in the process - my tablet is rooted.
From what I have read, I am lead to believe that ROM Manager can't install just CMR because the recovery boot process on Sony tablets is integrated into the kernel. So I think I need to use adb to get into fastboot mode and flash a boot.img that contains CMR. I also believe that you can't flash a kernel with a locked bootloader. Am I correct so far?
At this juncture I only want to get CMR installed, I'm not ready to actually install an entire ROM yet. "One step at a time grasshopper"
Ideally, I would like to get CMR installed before I unlock my bootloader so that I can make a backup and return to a locked bootloader config if I ever have the need to.
So my question is this: Is there a way to get CMR onto my tablet without unlocking the bootloader? If what I would prefer isn't possible is following and using the boot.img in this thread the next best way of proceeding?
http://forum.xda-developers.com/show....php?t=2433466
Thanks everyone for a) putting up with such a basic set of questions, b) helping me become less of a Noob and c) helping me accomplish what I need to get done.
Click to expand...
Click to collapse
Sorry, I can't answer you main question - but I can give a bit of advice:
I you are going to unlock your bootloader make sure to back up the "TA" partition first. This contains information such as DRM keys which are specific to your device and cannot be recovered once lost (unlocking the bootloader will wipe the TA partition). Google "Sony DRM TA partition" for more info.
I don't think you have to do a nandroid type backup via CWM before unlocking the bootloader. As long as you've backed up the TA partition I believe you can get back to locked, stock ROM. There is advice in these forums somewhere.
I would really think hard before unlocking the bootloader - why do you want to do this? The stock Sony ROM is pretty good.
Hope the above is of some use - hopefully someone else will reply (and correct me if I've mis-informed you!)
GretaLewd said:
Sorry, I can't answer you main question - but I can give a bit of advice:
I you are going to unlock your bootloader make sure to back up the "TA" partition first. This contains information such as DRM keys which are specific to your device and cannot be recovered once lost (unlocking the bootloader will wipe the TA partition). Google "Sony DRM TA partition" for more info.
I don't think you have to do a nandroid type backup via CWM before unlocking the bootloader. As long as you've backed up the TA partition I believe you can get back to locked, stock ROM. There is advice in these forums somewhere.
I would really think hard before unlocking the bootloader - why do you want to do this? The stock Sony ROM is pretty good.
Click to expand...
Click to collapse
Thx for the advice. I don't really want to unlock the bootloader at this point in time. I would just like to get CMR installed and am looking for a way to do that without unlocking. I have read about backing up the TA but must admit don't fully understand the process. What does TA stand for and how does one go about backing it up?
Answer:
http://forum.xda-developers.com/showthread.php?t=2234627
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
scaftogy said:
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, there is no reliable method to determine bootloader version. If you are confident in the steps you are taking to unlock the bootloader the your system may have upgraded past 3.2.3.2 which is the last version that contains the vulnerability that the unlock exploit leverages. You could try one of the Safestrap Flashable HDX Stock Images (suggest v3.2.6 for greatest compatibility) in the stock slot but this could result in a brick if everything doesn't line up properly. Not sure it is worth the risk given your device may have other lingering issues from the previous update attempt gone bad. Nexus v2 is still highly functional; you can safely update that to v2.05 and add a few Xposed modules to acheive a near KitKat experience.
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
dpeddi said:
- Bootloader shipped with firmwareversion 1[34].3.1.0 <= x <= 1[34].3.2.4 (as we use the rsa bug)
Click to expand...
Click to collapse
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
scaftogy said:
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
Click to expand...
Click to collapse
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Cl4ncy said:
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Click to expand...
Click to collapse
I am on @ggow's CM12.1 now! :victory:
Rolled back with this to .3.0.9, upgraded to stock .3.1.0, rooted, unlocked bootloader, flashed TWRP, and finally flashed CM12.1. Thanks so much for the hint to roll back!
To come full circle to the original question: Determining the version of the bootloader is not possible from adb or fastboot. If you don't know which version of the bootloader you have, it can help to try to find out which roms / updates you flashed before. In my case I had a folder on my PC that showed I must have had .3.2.4.
Hello,
I am new to this forum and rooting procces, I've read some threads and didn't understand few things.
So, my questions are:
1. Is it possible to root phone without unlocking bootloader and losing DRM keys?
2. If it isn't,is there a way to backup DRM keys and restore them after rooting?
3. If I am able to root without unlocking bootloader will I still get OTA updates and if I do, will OTA update delete my root status?
Sorry if these questions were already asked in other thread, I was searching a bit and couldn't find any of those. Hope you can help me out.
Thank you in advance and have a nice day
1. Yes it is although you do need some time to do it. It's not difficult though.
2. As soon as you root, you can take a ta backup(which requires a few clicks and about 2 minutes of your time).
3. You won't be able to use Ota (even if you are which you most likely won't, it is recommended that you DO NOT use it).
cindra said:
1. Is it possible to root phone without unlocking bootloader and losing DRM keys?
2. If it isn't,is there a way to backup DRM keys and restore them after rooting?
3. If I am able to root without unlocking bootloader will I still get OTA updates and if I do, will OTA update delete my root status?
Sorry if these questions were already asked in other thread, I was searching a bit and couldn't find any of those. Hope you can help me out.
Thank you in advance and have a nice day
Click to expand...
Click to collapse
1.-Yes, the method is called "Downgrading". I go back to 4.4.2 (Build number 314) and use the older XZDR (Xperia Z Dual Recovery). It will temporarily root to install the recovery. When the phone reboots you can install a custom ROM or whatever to get Lollipop with Root and Recovery
2.-After rooting on 4.4.2 you can do a backup of the DRM Keys
3.-Just because you have rooted your phone you will no longer be able to get OTA updates for the Android system itself. OTA will show a random error message and PC Companion will refuse because of the modified software.
Ok, thank you for answers
Is there any 6+ Android build that is pre-rooted or is it better to stick with 5.1.1 rooted?
Alo, I've heard that cam quality could drop after rooting or unlocking bootloader, is it true?
cindra said:
Ok, thank you for answers
Is there any 6+ Android build that is pre-rooted or is it better to stick with 5.1.1 rooted?
Alo, I've heard that cam quality could drop after rooting or unlocking bootloader, is it true?
Click to expand...
Click to collapse
Stick with android 5.1.1 for now.
And yes, cam quality WILL DROP, but only after UNLOCKING YOUR BOOTLOADER. Rooting alone won't hurt your cam quality.
Mokiwipeout said:
Stick with android 5.1.1 for now.
And yes, cam quality WILL DROP, but only after UNLOCKING YOUR BOOTLOADER. Rooting alone won't hurt your cam quality.
Click to expand...
Click to collapse
Ok, so I was thinking a lot if I should root or not. I decided to root. So just to clarify some things. If I use comunity root with downgrading,will it keep my DRM keys? If yes, I backup TA partition when rooted and then I can proceed with BL unlocking. Can I restore DRM keys to a custom ROM? Do you have any good custom ROM suggestion for me and is it better to use odexed or deodexed ROM?
I saw also saw this thread, hope it works so I won't be losing any camera quality.
That should be all.
Thank you in advance.
Have a nice day .
If you do NOT UNLOCK your bootloader, you wont lose your drm keys. (this is why after rooting using this method you can actually backup your drm keys, which you MUST DO no matter what).
When you restore your drm keys, you actually RELOCK your bootloader, so you must be on a stock based custom rom, and not using a custom kernel, otherwise you will simply brick your device.
Odexed or deodexed rom is purely personal preference, the difference being that deodexed ROMs allow for more customization (which is not necessary though). Regarding this, it doesn't really matter whether it is deodexed or not, so keep this in mind.
I cannot suggest a rom and I would advise against asking which rom is the best, because it is against the forum's rules.
Mokiwipeout said:
If you do NOT UNLOCK your bootloader, you wont lose your drm keys. (this is why after rooting using this method you can actually backup your drm keys, which you MUST DO no matter what).
When you restore your drm keys, you actually RELOCK your bootloader, so you must be on a stock based custom rom, and not using a custom kernel, otherwise you will simply brick your device.
Odexed or deodexed rom is purely personal preference, the difference being that deodexed ROMs allow for more customization (which is not necessary though). Regarding this, it doesn't really matter whether it is deodexed or not, so keep this in mind.
I cannot suggest a rom and I would advise against asking which rom is the best, because it is against the forum's rules.
Click to expand...
Click to collapse
Thank you for answer. If i use this method will it keep my bootloader locked (Will DRM keys stay on phone?).
Look.
Your bootloader cannot be "accidentally" unlocked. You have to get the bootloader unlock code by YOURSELF. A program wont do it on its own.
So don't worry, even if the method you chose to root the device requires an unlocked bootloader, it will be stated since you have to do it manually.
Plus, rooting a device with an unlocked bootloader simply requires installing a custom kernel(which has a recovery too) and then flashing a zip file that will root the phone.
Mokiwipeout said:
Look.
Your bootloader cannot be "accidentally" unlocked. You have to get the bootloader unlock code by YOURSELF. A program wont do it on its own.
So don't worry, even if the method you chose to root the device requires an unlocked bootloader, it will be stated since you have to do it manually.
Plus, rooting a device with an unlocked bootloader simply requires installing a custom kernel(which has a recovery too) and then flashing s zip fike that will root the phone.
Click to expand...
Click to collapse
Thank you very much and sorry for so stupid questions, I am new to this and just want to be sure
Hi
help me how to install .bin file
Standin.Weed said:
Hi
help me how to install .bin file
Click to expand...
Click to collapse
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Davey126 said:
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Click to expand...
Click to collapse
I have the kindle fire hdx 7 13.3.2.4 and I also have file:
mod-update-kindle-thor-13.3.2.8_user_713328020.bin
I do not know how to manually install this file
these words are translated by google because I have bad english
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Cl4ncy said:
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Click to expand...
Click to collapse
teach me how to install 13.3.1.0 install TWRP, update the bootloader to 3.2.3.2
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelihood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Cl4ncy said:
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelyhood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade Images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Click to expand...
Click to collapse
I do not know to do this step:
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
this is not have to be?
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Cl4ncy said:
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Click to expand...
Click to collapse
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Standin.Weed said:
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Click to expand...
Click to collapse
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Cl4ncy said:
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Click to expand...
Click to collapse
tks you so much.
I did all :laugh:
Standin.Weed said:
tks you so much.
I did all :laugh:
Click to expand...
Click to collapse
You're welcome - enjoy your "free" HDX.