This Oneplus X seems to be more difficult than my previous attempts for installing TWRP and custom ROM. I keep getting stuck and nothing returning once in fastboot and executing command "fastboot devices". I just keep getting "< waiting for device >" .
I think I have ADB installed right because while the Oneplus X is on and in normal mode (developer settings enabled with OEM unlocking and USB debugging enabled also) ADB connects. The USB drivers look to work fine because I can see the device (including SD card storage) and transfer files. in ADB and typing in ADB devices, I see the device.
When I run adb reboot bootloader and execute fastboot devices using command.com with administrator privilege, it just returns another prompt. It doens't show any device. I get the same results with Powershell with administrator privelge.
I'm already on my 2nd machine trying to do this although it's a windows 10 also just w/o updates for six months (was off and on the side of office). I had the same issues on my newer machine and thought it's the windows 10 machine I'm using. Researching the internet and here, I see others mention it though I didn't see any solution. I don't have a Linux machine (never really used it though had redhat installed eons ago somewhere). I guess I can do a refresh of my 2nd/older machine and not do any updates to see if that may help with any driver conflict though I don't see any indicators since adb can see the device. I thought trying to install TWRP via sideloader may work but I don't see tutorials and commands via that way.
Also I'm using ADB 1.4.3 in the 2nd windows machine. I had the Minimal ADB and Fastboot version on the other machine.
Anything else I can try?
P.S. The Onyx seems to be harder than putting android on my old HP touchpad! Putting a Tmobile rom on a AT&T Galaxy S4 and custom rom on a Oneplus 2 seemed much easier than the Onyx though unsure why. Onyx and the Oneplus 2 were comparable manufacturing years iirc.
On the 2nd machine, i did a windows 10 reset to basically refresh it (like a fresh install). I started over again and managed to get past the fastboot device problem and it's showing it now. I think the prior problem was the device and driver and even with a re-install, can't seem to get past it. The only difference I did with ADB install was not opting to install google drivers.
I got the bootloader unlocked and the recovery.img file done. Basically I'm following the direction from this page - https://www.technobuzz.net/root-oneplus-x-install-twrp-recovery/ - which seems to be aligned with most youtube and I think same as old pages here.
Now where I'm stuck is when executing "fastboot boot recovery.img" I get the failed (remote : dtb not found) and can't seem to find a solution to this one. Some sites say something about the partition?
Thoughts? hopefully this machine is not too old/dead for some comments/guidance unless I'm posting on the wrong section.
well to share back here and for closure.. looks like the recovery image i used on the site above must be for a different OOS. doing some further searches here and different terms and jumping to another thread from a search result thread (lol), i read that i needed a specific twrp for oos 3.1.4. (odd since recovery is supposed to be independent of ROM version, but that seemed to have work). guess persistence pays after all.
it really did heavily matter having the device recognized properly by windows 10. once i got past the blank fastboot device command execution, i got the another issue due to the phone not knowing how to boot into the recovery version i was trying to install, at least that's how another poster in another thread explained it. hence the right twrp had to be used for oos 3.1.4
Related
I see they are flashing custom files / ROMs on the Kindle Fire using fastboot. I believe we are limited on this due to our current bootloader state, but does anyone with experience with Fastboot know if this may be a possible working option until we can get CWM / recovery ?
I agree, can someone please try this? I've seen romified asking this question several times but no one seems to have tried it. The chances aren't great, but it's definitely worth a try.
might be as simple as "adb reboot fastboot"
and then "fastboot oem unlock" or other commands (I'm not too familiar with them myself)
This harks back to the (not so long ago) days of flashing via fastboot on my HTC Magic, which have since passed since I move onto a SGS II.
Edit: Oops it wasn't romified who asked this previously. Can't remember who it was. But either way, that's not really important.
I have not asked about fastboot yet as I just though of it and did some quick research. I am comfortable hacking roms and decompiling files and what not, but bootloaders and hacking recovery is new to me (for now anyway) As soon as I get to where I can I will dig into it further but if someone knows it isn't going to happen with this bootloader, no need in wasting time on it. It could open the door for other possibilities as well. I tried to get fastboot to recognize my NT but no luck. It was just a quick try though.
Did you manage to get the NT to get into fastboot mode though? Probably using the adb reboot fastboot or adb reboot download command (unless we find the hard button shortcut to it)?
I don't have the Nook Touch yet, but will probably be getting one to play with soon (the gf has her eyes on one). Either way, the more capability unlocked, the better.
If you can get the device into fastboot, it's a matter of looking carefully at the USB device tree and seeing that you have a fastboot device listed, then digging through the strings until you find a string you can use to communicate with the device.
If Fastboot isn't included with the NT, it is available with a number of other software packages.
I know it's part of one of the Lenovo LeTools packages, for instance, which is available for download for Windows hosts. If you get the copy from LeTools, be aware that it will install (or try to) the LeTools.apk that's bundled with it from your computer to any bloody Android device that's attached, not just to Lenovo devices. So you may want to delete LeTools.apk after installing and before connecting your NT.
Or you might want to try leaving it there as an experiment. The apk does some interesting things, one of which is make your device discoverable via wifi, at least if it's a Lenovo branded device.
The release of LeTools I just confirmed fastboot for is available at http://consumersupport.lenovo.com/us/en/DriversDownloads/drivers_show_5004.html release IN12STW151WW5.exe.
You don't need to install everything to get fastboot - you can unzip the installer a couple of times to get to the install.msi file for just the tools.
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
I have the same problem
Shaiden said:
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
Click to expand...
Click to collapse
I know it's been 4 years but did you find any solution to this? I'm asking because I have the same problem. I decided to downgrade to Remix OS 1.5 in order to root (I have tried 5 rooting apps with no success) but my device refuses to enter fastboot protocol. The whole idea was since I can't find a way to root the damn thing in its current state maybe I can manage it with its older OS version. All this just to turn it to android root apps "testing ground" device. Oof.
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.
Hi all,
Came by a Blackview BV6600 from someone who gave up on it - shipped saying that the device was 'corrupt and couldn't be trusted'. Went back and forth with their crappy customer service and gave up, sold it to me for cheap. It seems like a decently rugged phone but it does have a lot of bloatware and according to some threads on here about the mfgr I don't know if I trust them too much.
I'd like to wipe this phone, and I'm finding it difficult to locate a generic 'How to' for flashing a new OS to a phone. Disclosure; this is the first time I've done something like this. My experience is with computers, I know phones are a different beast and the user has much less freedom due to specifics of the hardware. If I say anything based on incorrect assumptions please correct me.
Again, what I would like to do is akin to installing Linux on what was a Windows box. I'd like to ****can as much weird chinese bloatware as possible (upto and including the entire OS) and replace it with some basic clean open source software. It seems like LineageOS does not have a version for Blackview phones, nor does it have a generic image. I notice that the Android open source project has 'Generic System Images' https://source.android.com/setup/build/gsi#flashing-gsis which sounds like what I want but references a vbmeta.img file which itself, as far as I can tell searching the forums, is likely manufacturer dependent, maybe phone dependent.
Anyway, I'm taking all the steps I see across enough sites to suggest they are platform-independent and won't brick my phone. Been following this video
since it's relatively recent and addresses my specific manufacturer.
So far I have:
Got developer permissions (go to Settings-About Phone, click build number repetitively)
in Settings-System turned on OEM unlocking and USB debugging
Figured out how to put this phone model in fastboot mode (hold volume up during restart)
Installed ADB and Fastboot (Linux), pinged the phone with "adb devices" and checked it's partitioning with " 'adb shell' <enter> 'getprop ro.build.ab_update' " no output, so that suggests 'A only'.
Next step seems to be:
oem unlock using fastboot. I seem to be having trouble here. In fastboot mode connected via USB, I can't detect the device. "Waiting for any device". 'adb devices' gives no response. No idea why. Phone screen looks exactly like in the video, hooked to USB that did return output for USB devices in normal boot mode.
Once I get over this dumb hump, I think I'll need to find a version of TWRP that will work on my device, install TWRP.
At this point I'm even more at sea: Most places suggest Magisk, but I've also seen explainers to wipe the old OS and install LineageOS.
If anyone has advice on what to do from here, specifically the near-term issue of not being able to find my phone via USB debugging while in fastboot mode, please let me know. But of course, long term I'm gonna need to know how to shovel this **** the phone came with out of storage and replace with a clean install so that is welcome as well.
bump