Q&A for Bootloader unlock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Bootloader unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
ImportError
After executing ./cublock.py XX SSSSSSSS it gives me this error :
Traceback (most recent call last):
File "C:\Users\angie\Desktop\cublock.py", line 4, in <module>
from cuber import forge
ImportError: No module named cuber
How can I fix this. Also do I need a fastboot cable? Thankyou.
1st Gen Fire HD ?
Hello, will the JMZ bootloader unlock method work for the 1st Gen Fire HD 7? Currently running sw 7.5.1
That's wrong cuber.
I think you need cuber.py from attachment in this topic: http://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Do you need a fastboot cable to get into fastboot? I have ran the adb-setup in this thread http://forum.xda-developers.com/showthread.php?t=2588979
I can assure you I have ADB and fastboot drivers installed. When I get to the step to issue the adb reboot-bootloader command it just boots up back into the OS. I'm not sure what I am doing wrong, but I am stuck. Please help?? Also, I really appreciate your work you have done.
Fire HD 6/7 Boot loader unlock working with HDX devices?
Any idea if this will work with the HDX 7 and 8.9 devices?
hlep
i user kinder hd 6 , i unlock bootloader erro
[email protected]:/media/vo/DATA/Android/Rom/Kinder Fire/Fire HD6/cublock$ ./cublock.py 15 af2bb827
Traceback (most recent call last):
File "./cublock.py", line 4, in <module>
from cuber import forge
ImportError: No module named cuber
please hlep me fix erro
To fix ImportError: No module named cuber
Download tools.zip and extract to folder where you put cublock. (See here about tools. Thank you @draxie!)
codomir said:
Do you need a fastboot cable to get into fastboot? I have ran the adb-setup in this thread http://forum.xda-developers.com/showthread.php?t=2588979
I can assure you I have ADB and fastboot drivers installed. When I get to the step to issue the adb reboot-bootloader command it just boots up back into the OS. I'm not sure what I am doing wrong, but I am stuck. Please help?? Also, I really appreciate your work you have done.
Click to expand...
Click to collapse
Can someone please help me? I don't understand why my device won't boot into fastboot I have tried adb reboot-bootloader and adb reboot fastboot and I still can't get in. I am rooted and I have my unlock.img but I can't get into fastboot to flash it. PLEASE someone help me get into fastboot. And please clarify if I need a cable or not, maybe that is the reason I can't get into fastboot?!
codomir said:
Can someone please help me? I don't understand why my device won't boot into fastboot . . .
Click to expand...
Click to collapse
You don't need fastboot cable--they don't work with our device. You might have said No to installing device drivers with the 15-Second installer. Maybe adb is working because its dlls are in the adb dir. I'd try running the installer again, but you may need Fire-compatible driver, idk. That's all I've got. Good luck.
DoLooper said:
You don't need fastboot cable....
Click to expand...
Click to collapse
They do work with our device, I have the soho. You use it to restore the soho with Firerooter. I have ran the installer I don't know how many times and I am pretty sure the drivers are installed. The two drivers I have in device manager are:
Android Device -> Android Composite ADB Interface
Portable Devices -> Fire
Everytime I issue the command it just goes straight back to the OS. I don't understand? Unless it has to be some other USB. I am using my front USB panel and I do have an intel chipset but I am on Windows 7 Home Premium 64 bit. The only other usb device I see is USB Composite Device. But that can't be the driver for fastboot can it?
codomir said:
They do work with our device, I have the soho.
Click to expand...
Click to collapse
Oh, good grief! No, "our" device is 2014 Fire HD, not soho. No wonder the confusion.
Yes, FB cable required for soho. Get one and then go to G+ KFSOWI modding and follow their install guide to update both adb and FB drivers. Guide tells you how to connect cable for fastboot mode. Be aware that the bootloader unlock process here was not written for soho and probably hasn't been tested on it. Please post any further questions at KFSOWI site. thx
.
Related
Q&A for [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Everything works until....
the very last stage when I put in adb devices and it says command not found???
Please advise
Simon
Thank you AshtonTS
I had been stuck in boot animation after trying to install a modification and with your help and another on flashing a stock image I'm back up and running! Thanks so much.
Followed the whole step-by-step and I got it to work. After I unlocked the bootloader using the how-to from Sony, the device can't be found anymore.
Any thoughts?
[edit] Got it, USB-check was turned off. My bad
i've followed this yet when i execute ./adb devices no devies show up... anyhelp would be greatly appreciated.
tnx
Flash
How can I flash TWRP, root my device and load OS 11 using this method? Thanks in advance...
How can I get the latest dab and fast boot?
Or else, how can I know if the ones I have are right for my Nexus 5?
I've downloaded the ones posted by r0ger here: http://forum.xda-developers.com/showpost.php?p=61676680&postcount=183
I'm pretty sure everything should work ok, but after burning a N4 last year, when modding from a Mac, I now proceed very carefully.
Thank you.
When I enter the command
./adb devices
My device is shown, but it is shown as offline. Further I cannot execute any other commands.
Hello All,
Need help with TWRP installation, I have tried everything to install TWRP on my one plus x but with no luck
The problem is to unlock OEM, when I am trying to do it it hungs up.
I followed the installation given --> http://forum.xda-developers.com/showthread.php?t=2588979
Upon updating Driver via Device Manager, I don't get the ADB interface but get ONE Plus Interface and it installs MTP drivers and not the "Android ADB Interface", please help!!!:crying: I tried all possible ways but with no luck, any help will be highly appreciated!
Regards,
Vineeth
There's an all in one PC program somewhere in here you should give it a try real easy.
Exodusche said:
There's an all in one PC program somewhere in here you should give it a try real easy.
Click to expand...
Click to collapse
Thanks for the prompt response, please can you guide me or help me with the link?
All the necessary prerequisites to install TWRP is done on my mobile but still don't know why the OEM is not getting unlocked.
Follow this thread http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830/page1
Hi,
Try this : https://theunlockr.com/2016/02/17/video-how-to-root-the-oneplus-x/
Twrp link : https://dl.twrp.me/onyx/
Mahesh8348 said:
Hi,
Try this : https://theunlockr.com/2016/02/17/video-how-to-root-the-oneplus-x/
Twrp link : https://dl.twrp.me/onyx/
Click to expand...
Click to collapse
Hi Mahesh,
Thanks for your prompt response but again with no luck things failed
See the screenshot:-
http://screencast.com/t/RwG4vXbtgg
Below is the drivers page lead to when I select Browse Driver Manually option:-
http://screencast.com/t/5RouYso1fndO
It gives me below Drivers Rather that ADB
http://screencast.com/t/5RouYso1fndO
And its hangs like this:-
http://screencast.com/t/x9w1asrmusZ0
Any help where I am doing wrong?
vinteeth said:
Hi Mahesh,
Thanks for your prompt response but again with no luck things failed
See the screenshot:-
http://screencast.com/t/RwG4vXbtgg
Below is the drivers page lead to when I select Browse Driver Manually option:-
http://screencast.com/t/5RouYso1fndO
It gives me below Drivers Rather that ADB
http://screencast.com/t/5RouYso1fndO
And its hangs like this:-
http://screencast.com/t/x9w1asrmusZ0
Any help where I am doing wrong?
Click to expand...
Click to collapse
Did you enabled OEM unlock in developer options . if not please enable and do it .
Mahesh8348 said:
Did you enabled OEM unlock in developer options . if not please enable and do it .
Click to expand...
Click to collapse
Thank you for the prompt response, all the prerequisites settings are in place like OEM unlocking and USB debugging are enabled.
Read is somewhere that ROM can be installed by sideload method but does it require ROOT privilege? Or can the ROM be installed from recovery by selecting Install it from SD card?
It's
fastboot oem unlock
Not unblock !!!
Kéno40 said:
It's
fastboot oem unlock
Not unblock !!!
Click to expand...
Click to collapse
Thanks alot Kéno40!!!!!!!!! and of-course sorry for such a stupidity of mine asking for help without checking the commands properly! :crying:
Thanks to all others member for the helping hands... All sorted and now I have successfully installed the CyanogenMod on my One Plus X!! Kindly close this thread...
Once again pardon for my extreme stupidity..
Regards,
Vineeth
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Really desperate here.. :/
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Yousucks2 said:
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Click to expand...
Click to collapse
You are in a world of hurt. It's possible (likely) the device can be recovered but not without considerable effort and (probably) many failed attempts. Such assistance is beyond what can reasonably be provided via the forums. You can browse through HDX threads to get the gist of what needs to happen. If you are a technology/Android noob it will probably be easier to pick up a refurb at an auction site. Good luck.
PM for support is normally ignored
joltpodcast03 said:
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Click to expand...
Click to collapse
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
draxie said:
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
Click to expand...
Click to collapse
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Do your homework...
joltpodcast03 said:
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Click to expand...
Click to collapse
As I said, if fastboot works, it's fixable (in other words, it's not a brick).
BUT, you'll have to find one of the million guides on how to setup and
use fastboot all by yourself. That's not something I'm willing to spend
time on. Sorry...
As for cables, unless the device is a soft-brick, you don't need a special
cable, but it's preferable to use your factory cable not random junk.
BUT, seeing that you have MacOS, my 1-Click tool _should_ work for you.
Then, all you need to do is click through a web-UI. If you want to do that
instead, you'll have to wait though, because I need to iron out a wrink or
two, and haven't had the time the last week or so...
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Yousucks2 said:
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Click to expand...
Click to collapse
Technically not ADB if working in fastboot but guidance is still 100% relevant.
fastboot commands?
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Montisaquadeis said:
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Click to expand...
Click to collapse
Wow - that's an old build! If you have used adb, have a host PC or laptop, can install device drivers and are comfortable following directions unlocking is relatively easy. At present the task remains a largely manual affair. However, the rewards are rich with a nice suite of custom ROMs including several Nougat based options. It will be like having a new device!
I have both a laptop and desktop both are running Windows 10
Montisaquadeis said:
I have both a laptop and desktop both are running Windows 10
Click to expand...
Click to collapse
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Davey126 said:
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Click to expand...
Click to collapse
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Montisaquadeis said:
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Click to expand...
Click to collapse
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Davey126 said:
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Click to expand...
Click to collapse
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Montisaquadeis said:
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Click to expand...
Click to collapse
Congrats! You have gotten through the riskiest part of unlocking the bootloader. From this point forward there is little you can do to hurt your HDX aside from sustained contact with a blow torch or direct engagement with an A1 Abrams battle tank (bit of an overreach but you get the point).
Unfortunately, 1-Click is still not ready for prime time. The author has the best of intentions but a severe lack of bandwidth to complete.
That said, manual unlocking is relatively easy:
1) Download/install this package on one of your Windows machines which scores drivers that have proven reliable with every HDX device I (and others) have encountered. Yep, seems illogical but it works better than all of the other alternatives (drivers) that have been bounced around for the past 4 years. You can remove the package after unlocking your device.
2) Install Minimal ADB and Fastboot (here) on the same machine
3) Verify you can launch the ADB/Fastboot command window via the icon that should have been added to your Windows desktop.
4) Boot into TWRP and tether your device using a reliable USB cable. You should receive some audible/visual feedback from Windows that it recognizes the device.
5) Launch the minimal ADB/Fastboot window, type "adb devices" and press <return>. Response should be the device identifier followed by the word 'device'. If successful type "adb reboot bootloader" followed by <return>. After a few moments the device will boot into fastboot. Type "fastboot devices" and press <return>. If successful response should be similar that noted above. Finally, type "fastboot reboot" to boot into FireOS. If any of the previous commands fail simply untether and long press power button (8-20 sec) to turn off your device. It can then be restarted in the usual fashion.
If you have difficulty with any of the items in step #5 please detail your observations and I will help you through remedial steps. Otherwise, bounce back and we will go through the remaining few steps to complete the unlock process.
Sorry for parceling this out in small chunks. Experience has taught this is the best approach rather than penning a long novel in a single post.
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Montisaquadeis said:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Click to expand...
Click to collapse
Hum - something seems wrong. That command should not have failed if the previous "adb devices" returned the expected response. Let's take a different approach to the fastboot connectivity test:
- untether device
- boot into TWRP
- tap 'reboot' followed by 'bootloader'
- you may be prompted for a confirmation swipe; go ahead and do that
You should now see a gray "Kindle fire" logo followed by the word "fastboot" in brackets. Retether device; hopefully a ready prompt will appear. If so continue with fastboot connectivity test as documented in previous post.
If a ready prompt does not appear or the test fails you'll need to use Windows device manager to identify your device and update the device driver to "Mot Composite ADB Interface". This can be a tedious process if you haven't gone through it before. Bounce back if you need assistance.
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Montisaquadeis said:
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Click to expand...
Click to collapse
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Davey126 said:
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Click to expand...
Click to collapse
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Montisaquadeis said:
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Click to expand...
Click to collapse
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Davey126 said:
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Click to expand...
Click to collapse
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Montisaquadeis said:
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Click to expand...
Click to collapse
You want to work the entry listed under Portable Devices. I'm in the same timezone; also winding down for the evening.
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
leeismyname said:
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
Click to expand...
Click to collapse
Reasonable questions; responses:
- SafeStrap v4 and TWRP can coexist on the same device; no need to uninstall the former which is not a true recovery (it lives in the system partition and will be wiped out when you install a custom ROM)
- No issue running FireOS while navigating the bootloader unlock procedure
As previously noted be sure to use the Thor builds on your HDX 7. Recovering from an inadvertent Apollo flash make passing a kidney stone look appealing.
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Montisaquadeis said:
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Click to expand...
Click to collapse
Excellent! Next steps:
- Complete the 3rd bullet in the prerequisite section of this post. Pay careful attention to where the extracted batch file resides; move as needed. Most likely the directory will be "C:\Program Files (x86)\Minimal ADB and Fastboot" but you will need to confirm. Obviously referring to the Win 10 box.
- Perform steps #1 and #3 in the "Code generation and unlock" section. When complete it is quite possible the bootloader will be fully unlocked. However, if the procedure stalls we will have to take one more (easy) step to complete the procedure.
IMPORTANT: Step 2 in the "Code generation and unlock" section has already been performed (as directed earlier in this thread)! No need to repeat as this is the riskiest part of the unlock procedure.
Bounce back when complete. There are a couple clean-up steps that should be done before flashing a custom ROM. I can also provide guidance on which ROM to install if you don't already have one in mind.
I have 2 of these with Android 9. A 50 and a 60. They use the android home launcher and so display ads, etc.
Specs:
Mstar M7322
2gb Ram
4GB storage
Mali GPU
Right now:
Adb can be entered over wireless. Most apps can be user disabled/uninstalled.
App List: https://pastebin.com/GL8b00s6
Apps to Disable: https://pastebin.com/ngM3Gy8g
You can use termux with ADB addon to use ADB right from the TV with BT keyboard.
Use ADB and Fastboot Commands on Android without Root
Using ADB Fastboot Termux Git you can install and use ADB and Fastboot commands on Android devices via Termux without root or using a computer.
technastic.com
Android launcher contains the input switcher so hard to replace but this one works: https://forum.xda-developers.com/t/app-android-tv-projectivy-launcher.4436549/
Can only use VPN based firewall. Can't use my VPN.
Can't be trusted on network.
Remote has a microphone (hi Orwell!).
Bromite/VLC/Kodi/etc all run.
No [email protected] 4:4:4 beyond 8bit.
Issues:
* USB adb works with a male to male cable. Bought one on ebay.
* There is no service jack/socket or service manual I could find to get the bootloader console.
* On reddit someone used a raspi zero?
https://www.reddit.com/r/AndroidTV/comments/pyo4sk/_/hfqvua9
* Cannot list MTD partitions on ADB without root.
* Supposedly unlockable from bootloader/fastboot but beware:
https://forum.xda-developers.com/t/android-tv-stuck-on-black-bootloader.3803695/
* No firmware updates to dissect.
Service Mode (Mstar Service Menu):
Menu -> Sound -> Advaned -> Balance -> Type '1' '9' '6' '9'
How to disable an app without root:
Code:
pm disable-user --user 0 com.hisense.tv.ota
pm uninstall --user 0 com.hisense.tv.ota
pm disable-user com.hisense.tv.ota
Board info?!
In app manager system info the mainboard identifies as MSD6886. This one is slightly different in terms of port layout as if it was the upgrade version. But that board has a service manual and bootloader/layout stuff applies. https://www.manualslib.com/products/Hisense-Msd6886-10481497.html
The uart on that board is the headphone jack which isn't present on this TV. Maybe it has to be soldered.
TV Source code from Hisense:
GitHub - opensource-hisense/SmartTV-SeriesVidaaU5: product:75U9GEVS 75U9GQ 75U90GQ 75U91GQ 75U92GQ 75U9GQCH 75U90GQCH 75U98GQNE 75U96GQ 75U97GQ 75U98GQ 75U99GQ 75U96GQCH 75U97GQCH 75U99GQNE 75U9GQTUK 75U90GQTUK 75U91GQTUK 75U92GQTUK 75U96GQTUK 75U97G
product:75U9GEVS 75U9GQ 75U90GQ 75U91GQ 75U92GQ 75U9GQCH 75U90GQCH 75U98GQNE 75U96GQ 75U97GQ 75U98GQ 75U99GQ 75U96GQCH 75U97GQCH 75U99GQNE 75U9GQTUK 75U90GQTUK 75U91GQTUK 75U92GQTUK 75U96GQTUK 75U9...
github.com
Has anyone gotten any farther with this or any other mstar based TVs? Tried more malwareish programs like kingroot? What's worth trying next?
If the bootloader can be unlocked a backup could be made and it might just be a matter of adding magisk binary for all of that receiver/service disabling goodness.
Maybe one day we can compile a rom for it.
nxb said:
Has anyone gotten any farther with this or any other mstar based TVs? Tried more malwareish programs like kingroot? What's worth trying next?
Click to expand...
Click to collapse
Hello and good afternoon, @nxb
Prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Hope its not moved here to die.
nxb said:
Hope its not moved here to die.
Click to expand...
Click to collapse
I guess that depends on other things then that it has been moved out of an not suitable forum.
Regards
Oswald Boelcke
I have simply copied where similar threads were posted:
Rooting MediaTek Based Linux Smart TV
Hi Guys, I am looking for methods to get root on my Linux smart tv. Anyone have any ideas? I ran metasploit against it and had no luck, it did find some open ports for upnp and something called twonkymedia but I was not able to get anywhere...
forum.xda-developers.com
Sony Android TV Users
Hi All, I have searched over XDA but couldn't find any appropriate place for Sony Android TV. I have got my Sony Android TV, KDLW800C, couple of days ago. Sony has just started to ship out 4K and 2K Android TV's. From the interface, it's almost...
forum.xda-developers.com
This is definitely not help/troubleshooting and Q&A.
I have my 70A6G3 Bootloader unlocked following in your footsteps then unlocking via fastboot command in bootloader. Now im kinda stuck as I dont have a boot.img to use for root. Nor TWRP to make a backup. Any ideas?
Did unlocking reset to factory defaults? I should unlock mine now that its not going to brick.
We can try to boot generic recoveries through fastboot until we get one that works and then dump the MTD partitions, edit and flash back.
Backup/dump kernel image without root or twrp/cwm
Is there any way to backup/dump kernel image without root or twrp/cwm ?
android.stackexchange.com
AndroiddiordnA said:
I have my 70A6G3 Bootloader unlocked following in your footsteps then unlocking via fastboot command in bootloader. Now im kinda stuck as I dont have a boot.img to use for root. Nor TWRP to make a backup. Any ideas?
Click to expand...
Click to collapse
Bro,I have a rom of hisense tv, Can you extract the boot image for me,plz?
AndroiddiordnA said:
I have my 70A6G3 Bootloader unlocked following in your footsteps then unlocking via fastboot command in bootloader. Now im kinda stuck as I dont have a boot.img to use for root. Nor TWRP to make a backup. Any ideas?
Click to expand...
Click to collapse
Bro,I have a rom of hisense tv, Can you extract the boot image for me,plz?
codernixx said:
Bro,I have a rom of hisense tv, Can you extract the boot image for me,plz?
Click to expand...
Click to collapse
It should not be too difficult to extract a boot image from the ROM file.
What file format is the ROM? tz rar zip ?
codernixx said:
Bro,I have a rom of hisense tv, Can you extract the boot image for me,plz?
Click to expand...
Click to collapse
How did you manage to get rom? I am also looking for rom of 50A71F tv. Any help would be appreciated!
I have a Hisense 43A6H and its bootloader unlocked it was easy just had to load the drivers in bootloader mode and fastboot flashing unlock worked and yes IT WIPES THE TV but patching my boot.img never works, well it patches successful on some but not all magisk versions and flashing is a success in bootloader fastboot but it did not root the tv so its not working for some reason on my tv, as its android 11.