Related
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock" and also flash back to STOCK images (if changed) or else it wont boot
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
duarian said:
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
Click to expand...
Click to collapse
No, it doesn't send anything to Google, that's why they give you the option to relock the bootloader .
can this be done on linux using fastboot included in sdk?
jrod091 said:
can this be done on linux using fastboot included in sdk?
Click to expand...
Click to collapse
of course man fastboot is fastboot
matt95 said:
of course man fastboot is fastboot
Click to expand...
Click to collapse
You will probably need to run fastboot as root, though.
gnustomp said:
You will probably need to run fastboot as root, though.
Click to expand...
Click to collapse
It isn't needed, if the sdk folder is in the PATH it will work normally
udimars30 said:
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock"
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Video coming soon, after i get my hands on it!
Click to expand...
Click to collapse
Thanks！I will try it!
Re-lock
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
matt95 said:
It isn't needed, if the sdk folder is in the PATH it will work normally
Click to expand...
Click to collapse
I just put it in /usr/bin with adb, I've only had my SGSII as far as android devices, Si want sure, thanks though!
Sent from my SGH-I777 using xda app-developers app
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Lumsdoni said:
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Click to expand...
Click to collapse
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Sdk has been updated
Sent from my SGH-I777 using xda app-developers app
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
yeah thanks for reminding dude
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
---------- Post added at 02:31 PM ---------- Previous post was at 02:15 PM ----------
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Lumsdoni said:
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
Click to expand...
Click to collapse
It would appear it is a lot simpler now as you can download a sdk / eclipse bundle from here
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
I unlocked the bootloader but now the tab will not start? I starts to the X of JB and then nothing happens... Help
---------- Post added at 10:56 PM ---------- Previous post was at 10:18 PM ----------
I have the Solution :good:
If you have the same problem - Go into Stock-Recovery and make a "Factory Reset" then reboot the system.
EniGmA1987 said:
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
Click to expand...
Click to collapse
It's may be wrong, I'm basing it on my XOOM days where it wouldn't boot it you relocked with anything other than stock. If that's different now, feel free to ignore me
Sent from my GT-I9300 using Tapatalk 2
I know that when an update comes out I have to relock the bootloader, but if I unlock it after the update does it wipe the device again
Sent from my Galaxy Nexus
I have 3 questions
1. Unlocking nexus 10 means rooting it ?
2. Is unlocking or rooting tablets legal in US?
3. I ordered nexus 10 but read n
ot so good things about the limited applications are supported for 10 inch screen .. Is there any workaround to have apps look as good as iPad I mean using the entire screen ...any custom ROMs available yet
Sent from my SGH-I897
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
For the life of me I cant root it and I have an sd card id love to save apps to...... I do have a laptop. So app or laptop is fine. Any help is appreciated thank you
I was able to unlock the boot loader through htcdev website bout as far as I got though
I second that. I can find hundreds of sites, videos , and downloads about rooting the 626, but I have a 625 and there is nothing. Help! Want to root my 625
Htc dev
crypto spook said:
I was able to unlock the boot loader through htcdev website bout as far as I got though
Click to expand...
Click to collapse
I've never had trouble with HTC DEV and I can't seem to figure out how to get my Cricket HTC 625 into fastboot mode.
Any advice?
collatz said:
I've never had trouble with HTC DEV and I can't seem to figure out how to get my Cricket HTC 625 into fastboot mode.
Any advice?
Click to expand...
Click to collapse
If you can't get it via button combo then use enable USB Debugging and use adb: adb reboot bootloader
For adb and fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Rooting via Kingroot supposedly works once the bootloader is unlocked as mentioned here: http://forum.xda-developers.com/htc-desire-c/help/sowftware-update-t3255022
They didn't mention which software update it was on, but knowing Cricket and HTC, they probably never released but the original one so might be worth a try. Keep in mind that there does not seem to be an RUU to restore the phone if something goes wrong so proceed at your own risk.
Rooting is possible
Queen_Haze said:
For the life of me I cant root it and I have an sd card id love to save apps to...... I do have a laptop. So app or laptop is fine. Any help is appreciated thank you
Click to expand...
Click to collapse
It can be done by following HTCdev inductions. I did but it took a few tries to unlock the bootloader. After that any progress will root it. Even Kingroot. But there is no recovery for that device. So it's editing your stock rom. So stay backed up. The twrp 626S recovery will flash to it, I been playing with it but can't say if any rom will flash successfully yet. so my words should only be taken as offering my personal experience not as any professional advice
freeatlast34 said:
It can be done by following HTCdev inductions. I did but it took a few tries to unlock the bootloader. After that any progress will root it. Even Kingroot. But there is no recovery for that device. So it's editing your stock rom. So stay backed up. The twrp 626S recovery will flash to it, I been playing with it but can't say if any rom will flash successfully yet. so my words should only be taken as offering my personal experience not as any professional advice
Click to expand...
Click to collapse
Thank you I wish I would have seen this sooner though.. I sat on it and cracked the screen and my digitizer dont stand a chance lol oh well.:crying:.
Root htc 625 .. use twrp for the HTC desire 626s as it works with the 625 as well.. First unlock bootloader, I downloaded java (offline) version and it worked fine, then HTC manager. Then I downloaded the usb drivers for the phone(may not be needed). Then adb and fastboot (not from HTC link, found it on Google which worked much faster to download. Noe after bootloader unlocked kingroot will root it or flash the twrp img using command prompt, just type flash recovery and the name of the twrp file.. now I had to type - flash recovery twrpblablabla.img. img, so I had to add *.img at the end so it had the twrp name which ended in .img and then i had to add another - .img ..... not sure why but I was messing around and that's what got it flashed. Then I flashed superU using twrp recovery.. now I did root with kingroot after bootloader was good but that's cause the whole (.img) thing. I went back after and got the adb command to do it the way I wanted to at first.. plus rooted another HTC 625 that way..
Any questions message me I will help and can send links to the files needed.. Mau. Thing was using twrp for 626s and the .img added at the end so it looked like twrp3.2.1.img.img )
May have had a space before the last .img , can't remember so if it don't work for you try that. Help needed just ask I will be glad to help as it took me a long time to get the right info and actually do it.
Anyone have j727U and got twrp on it let me know, I will pay.
Hello,
I have tried and searched a lot, but can't find solution.
ADB,Kindle drivers are installed.
Tablet is rooted with kingroot.
Adb is working quite well, but can't enter fastboot mode.
adb reboot bootloader only restarts tablet.
How can I initate fastboot mode?
P.S OS: Windows 10 x64
arshileus said:
Hello,
I have tried and searched a lot, but can't find solution.
ADB,Kindle drivers are installed.
Tablet is rooted with kingroot.
Adb is working quite well, but can't enter fastboot mode.
adb reboot bootloader only restarts tablet.
How can I initate fastboot mode?
P.S OS: Windows 10 x64
Click to expand...
Click to collapse
Seems device has some history. If the guidance in the first link fails to work (and it probably won't) you should probably go for the full automated unlock via 1-click.
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
arshileus said:
Hello,
I have tried and searched a lot, but can't find solution.
ADB,Kindle drivers are installed.
Tablet is rooted with kingroot.
Adb is working quite well, but can't enter fastboot mode.
adb reboot bootloader only restarts tablet.
How can I initate fastboot mode?
P.S OS: Windows 10 x64
Click to expand...
Click to collapse
Guessing, without more info:
With HDX off press and hold power and volume down buttons.
Or
Depending on which twrp recovery (if any) is installed, you can reboot to the bootloader from there
gwardsc65 said:
Guessing, without more info:
With HDX off press and hold power and volume down buttons.
Or
Depending on which twrp recovery (if any) is installed, you can reboot to the bootloader from there
Click to expand...
Click to collapse
Nope; button technique only works with unlocked bootloader.
Davey126 said:
Nope; button technique only works with unlocked bootloader.
Click to expand...
Click to collapse
So, what's the solution?
arshileus said:
So, what's the solution?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...-mode-kindle-fire-hdx-7-t3923367/post79381593
Davey126 said:
https://forum.xda-developers.com/ki...-mode-kindle-fire-hdx-7-t3923367/post79381593
Click to expand...
Click to collapse
Sorry, but maybe you even didn't read my post )
I have rooted device, not it needed to be unlocked.
But while trying adb reboot bootloader, it doesn't go to fastboot but restarts.
arshileus said:
Sorry, but maybe you even didn't read my post )
I have rooted device, not it needed to be unlocked.
But while trying adb reboot bootloader, it doesn't go to fastboot but restarts.
Click to expand...
Click to collapse
I did and am well aware of the behavior. Use 1-click to fully unlock the bootloader which will restore your ability to boot to bootloader.
Davey126 said:
I did and am well aware of the behavior. Use 1-click to fully unlock the bootloader which will restore your ability to boot to bootloader.
Click to expand...
Click to collapse
I can't find download link of 1-Click unlocker, I have sent letter for post author, but no answer.
Can you send it to me?
arshileus said:
I can't find download link of 1-Click unlocker, I have sent letter for post author, but no answer.
Can you send it to me?
Click to expand...
Click to collapse
The developer (@draxie) has requested that he be the sole source for distribution which I respect. He typically responds to PMs within a few days.
UPDATE (03/09/2019):
This thread is now dedicated to the development of the Vertu Aster P replica, which has MTK's MT6755 Helios P10 chipset.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi All,
I've just recently bought a Vertu Aster P replica, which came pre-loaded with a Vertu-themed (skinned) version of Android 6.0 Marshmallow. In the 'About Device' menu, however, the developers have (not so cleverly) disguised it to say Android 8.1.0 (Oreo). Why they would do this, rather than just taking Oreo and skinning it with the Vertu theme, I don't know. Anyway, I've gone and hard bricked the phone while trying to install a custom recovery, and it will not turn on or charge. It is still recognised when plugged into the laptop, so if I had the original ROM that it came with, I would be able to reflash it and have a working phone again. Sadly, I cannot find the ROM for it anywhere online. I can find the ROM's for the Vertu Signature Touch replica and Vertu Ti, and others, but not for the new Aster P replica, which uses the MT6755 chipset. Here are a few photos of the phone's OS. So, I'm wondering if anyone might be able to point me in the right direction of where I might be able to find this ROM. I have already been in contact with the company I bought it from. Still waiting to hear back from them. Hopefully they can just send me a download link.
Chris
Still living in hope that someone has access to the ROM for this phone.
Someone kind enough eventually came along and sent me the ROM. Flashed it and my phone now works again. Lesson learnt. ALWAYS DO A BACKUP BEFOREHAND.
I will upload it myself and make it available on here for other Aster P (replica) owners shortly.
Chris
Here it is.
https://www.needrom.com/download/vertu-aster-p-mt6755-chinese-clone-firmware/
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
chris8189 said:
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
Click to expand...
Click to collapse
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
I found a TWRP on XDA forums which @lopestom made for the BLU Pure XR P0030UU smartphone -
https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
The above phone also has the MT6755 P10 Helios chip, same as the Vertu Aster P clone, so I thought I would try and port the ROM over for the Vertu Aster P replica.
I got an error while doing the repack, however @ashyx managed to perform a successful repack on the image file and the phone does indeed boot up the TWRP. Problem is, there is no touch functionality. Plugging in an OTG mouse however might work, or likewise flashing the recovery image file to the boot partition, doing what you need to do in TWRP, and then flashing the stock (or modified) boot image back. I have put the feelers out for the kernel source, so (hopefully) we can then do the necessary tweaks to make TWRP function correctly, or even better, build a TWRP from source (if we can get it). Below is the link to the TWRP file.
https://mega.nz/#!J45FWIzJ!aFyFooO5aOtxjFany_osL4BpRRQSMljQjtfnYSFKDis
Chris
ashyx said:
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
Click to expand...
Click to collapse
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
chris8189 said:
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
Click to expand...
Click to collapse
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
ashyx said:
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
Click to expand...
Click to collapse
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
chris8189 said:
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
Click to expand...
Click to collapse
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
ashyx said:
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
Click to expand...
Click to collapse
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
chris8189 said:
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
Click to expand...
Click to collapse
What result do you get for:
fastboot oem device-info
I tried it and the command doesn't work.
chris8189 said:
I tried it and the command doesn't work.
Click to expand...
Click to collapse
Try:
fastboot getvar unlocked
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
chris8189 said:
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
Click to expand...
Click to collapse
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
ashyx said:
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
Click to expand...
Click to collapse
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
chris8189 said:
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
Click to expand...
Click to collapse
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
ashyx said:
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
Click to expand...
Click to collapse
It doesn't load. It bootloops. So they have different kernels.
Chris