Related
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Problem:
This is the ultimate warning, and you likely don’t want to see this message show up on your screen. Shall this appear, it would mean your device is not safe to use, not trusted and/r corrupted. The OS could still work, but there’s high chances you will encounter performance and security issues.
Consequence:
Before your device begins to start it will be shown:
Android system
There’s an internal problem with your device. Contact your manufacturer for details nexus 6p
Also:
The camera may be no longer properly work
Fixxed:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
mfastboot flash system system.img
reboot bootloader
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot reboot-bootloader
fastboot flash vendor vendor.img
Important:
fastboot flashing lock_critical
Enjoy!
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Code:
fastboot format userdata
Also, bootloader reboots are only required after flashing the bootloader and the radio, so the sequence should be like this:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
And one more thing, you need to take more care when typing these instructions, you made a few errors, I'll highlight them:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
[Color=red]m[/color]fastboot flash system system.img [Color=blue](extra m at beginning of command)[/color]
[Color=red]reboot bootloader[/color] [Color=blue](missing "fastboot" prefix, and hyphen between reboot and bootloader (fastboot reboot-bootloader))[/color]
fastboot flash cache cache.img
[Color=red]fastboot flash userdata userdata.img[/color] [color=blue](incorrect command as outlined above)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](unnecessary)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](another one?)[/color]
fastboot flash vendor vendor.img
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
sandfreak said:
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
Click to expand...
Click to collapse
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
EDIT: This info only applies for "Bootloader MAY BE Corrupt" and not "IS Corrupt". Different situation from the OP
Thanked @Heisenberg
Please OP, you give instructions that you expect people to follow and if they type in the wrong info could be fatal...
Seriously, this thread needs closed asap. All the above info( besides Heisenberg) is careless in itself, let alone posting it for others. Stop....just stop. Smh
Heisenberg said:
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Click to expand...
Click to collapse
I have for sure made this mistake before... One lesson learned the hard way
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
That's exactly right, locking the bootloader means you can't flash anything to the device.
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
dontbeweakvato said:
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
Click to expand...
Click to collapse
That is one hell of a silly mistake. You're right, I apologize for not seeing that earlier. Will fix my previous reply so others dont get the wrong info from it. Thanks for that :good:
Dissmeister said:
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Click to expand...
Click to collapse
The way I understood it, after I re-lock then need to unlock again, the phone will force a wipe. The old app Unlock Bootloder would lock and unlock in Android. You wouldn't have to reboot. I guess the developer believes that the new 6P can't perform this same function due to the nature of new locking/unlocking.
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Rovaine said:
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Click to expand...
Click to collapse
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Heisenberg said:
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Click to expand...
Click to collapse
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Gorgtech said:
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Click to expand...
Click to collapse
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Exactly, you need the latest Factory Image for the Nexus 6P. Extract all content and only flash the vendor.img through fastboot.
Rovaine said:
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Click to expand...
Click to collapse
Rovaine said:
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
Click to expand...
Click to collapse
Flash the factory images, instructions are in my guide.
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
lextacy said:
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
Click to expand...
Click to collapse
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
shimp208 said:
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
Click to expand...
Click to collapse
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
lextacy said:
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
Click to expand...
Click to collapse
Glad I could help you out ! It must be a bad boot image then that you flashed, but that shouldn't prevent you from accessing the bootloader. When you get your new phone and root it you should be able to pull that stock boot image and then get your old phone working again. As always any questions let me know !
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
JackSlaterIV said:
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
Click to expand...
Click to collapse
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
shimp208 said:
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks, I saw but there is no answer there.
I'm really out of ideas to what's causing this so I could use some help.
My tablet has been fine for a long time and has had many roms on it previously. I have been on rooted stock however for over a year now and decided to try a rom again....
However I have tried 3 different roms now all with catastrophic problems. I install them fine through twrp along with gapps then reset Tablet but get a black screen with just a blinking charge light if it's plugged in. No boot logo or anything.
I managed to revert back to stock about 5 times today through flash mode and flash tool but I don't know what's going on.
I rooted, turned on debugging and reflashed twrp but it keeps happening across different android versions too. I thought maybe I had relocked bootloader so I tried to check through adb oem but it freezes, so I ran the unlock command just in case through adb and it was fine but still freezes.
Any ideas?
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
SabertoothTitan said:
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
Click to expand...
Click to collapse
I'm not an expert to be honest but I would try that:
put your tablet in fastboot mode, connect it to your pc and in fastboot type
"fastboot flash boot twrp.img"
Now you should have TWRP.
If this work your bootloader should be unlocked otherwise I think you should see some error in fastboot
Once you have twrp I suggest you to flash resurrection remix 5.7.0 (android 6.0.1). I suggest it just because it worked without problem with my tablet Z.
Something not clear to me: you started just with a rooted stock ROM or you unlocked bootloader, flashed TWRP and then your ROM?
I started with rooted stock rom, I am using dual recovery that seems to be working fine (it was faster since its just a bat file). I originally rooted using kingroot on stock which I used to flash stock rom prerooted with supersu with twrp.
If I try the same process with anything that isn't stock it's black screen on reboot. No Sony logo or anything.
Ive tried changing recovery to newest twrp, changing sd card to a different one, different ROMs including the one you mentioned because that's the one I wanted to try. I also tried with and without black kernel. None made any difference. Black screen boot everytime with just a blinking light on side like its got no OS installed at all.
Just to clarify, my bootloader should be unlocked. I've checked but if I run the adb command to check it just freezes like it's eternally loading. Using dialer go check it doesn't even display anything about it aside from the fact it can be unlocked.
what command do you type? "fastboot oem device-info"?
ok so I have an update, something is definitely messed up with my bootloader.
I tried to relock bootloader from fastboot but its also stuck in a loading cycle for no reason. It seems on some level my bootloader is unlocked because I can flash recoveries fine, but when I come to put a new ROM on the device it won't let me and black screens.
From fastboots I used the commands 'fastboot oem lock' and I just get '...' forever underneath. If I use 'fastboot devices' my device is listed, if I use 'fastboot -i 0x0fce oem unlock 0xbootloadercodehere' it fails the first time, then works the second time and says ok but its clearly done nothing when the device reboots. 'fastboot oem device-info' also leaves me with the '...' on command prompt forever too.
I have no idea what to do if bootloader is screwy at all.
-Pepe said:
what command do you type? "fastboot oem device-info"?
Click to expand...
Click to collapse
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
SabertoothTitan said:
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
Click to expand...
Click to collapse
I just tried with my XTZ and "fastboot oem device-info" just froze, it had 3 dot and nothing else. In my OPO it worked.
I'm gonna search something else...
Whats weird is my tablet also won't install anything on TWRP, I just tried installing SuperSU from it to see if it would work (having to use Kingroot atm) and it just does nothing.
I think this is the issue since I'm factory resetting before installing a ROM, which is therefore wiping my system and when I come to reset because TWRP isn't installing anything its acting like there isn't a system installed.
I can install via ADB fine, just when it comes to recovery... system says no. Its weird because its like its got a locked bootloader or something but even though I reinstalled using Sony software its still the same. If I try unlock bootloader again, I get an error first time then it says OKAY and does nothing.
SabertoothTitan said:
bootloader can be unlocked
Click to expand...
Click to collapse
According to an other post this should mean that your bootloader is locked but can be unlocked via Sony's code. At the same time I've read in the same post (can't find it) that people with unlocked bootloader still have "bootloader can be unlocked" even if they successfully unlocked it...
Unfortunately I can't try it myself because I'm on RR and the code *#*#7378423#*#* (this should be the code you used) doesn't do anything.
I have the code and have used it previously I have also retried it just to make sure.
When I type the dialer code above I get 'bootloader can be unlocked: yes' but nothing mentioning the actual current state of bootloader.
This is what's leading me to think it's a bootloader glitch because all posts I've seen should say 'bootloader unlocked: yes' or 'bootloader unlocked: no'. I get neither.
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
SabertoothTitan said:
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
Click to expand...
Click to collapse
Sorry, I'm out of ideas
The only thing I can tell you is what I did to my XPZ, but I doubt it may help you:
1) Unlock bootloader using Sony's guide
2) XPZ in fastboot mode → from pc "fastboot flash boot twrp.img" (assuming you have the proper TWRP image named twrp in the same folder of fastboot)
3) flashed RR 5.7.0 and Gapps
4) RR change the rocovery to CMrecovery but I "easily" changed back to twrp using a guide under RR thread.
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
I know it's only early day but has anyone found a root solution for the moto e6 plus?
Needing a new phone (hardware failure) and want one that can be easily rooted preferably with Twrp and Magisk,
McTRASH692 said:
I know it's only early day but has anyone found a root solution for the moto e6 plus?
Needing a new phone (hardware failure) and want one that can be easily rooted preferably with Twrp and Magisk,
Click to expand...
Click to collapse
I hope someone supports this device, since it is compatible with Proiect Treble
P o
I am planning to buy this, hope there is TWRP and Root soon!
Probably wont get support, cuz of the mediatek chip! I hope I am wrong [emoji1431]
Verstuurd vanaf mijn moto e(6) plus met Tapatalk
blanxlr said:
Probably wont get support, cuz of the mediatek chip! I hope I am wrong [emoji1431]
Verstuurd vanaf mijn moto e(6) plus met Tapatalk
Click to expand...
Click to collapse
The most E4 had a mediatek chipset and it had a few various root solutions,
yes, I'm waiting to root
Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Hey guys, I Need some help, I'm trying to unlock bootloader, but my device doesn't recognize fastboot commands like "fastboot oem get_unlock_data" Or "fastboot oem flashing_unlock", why?
Ps: Motorola drivers ok, usb cable ok, oem unlock and usb debugging ok
Root
Hi extrnoob! Could you explain this process step by step? Inexperienced people like me don't understand your language xD
extrnoob said:
Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Click to expand...
Click to collapse
I couldn't unlock bootloader. When i type the command fastboot devices i get a string, but when i type fastboot oem get_unlock_data, i get this message “FAILED (remote: unknown command)”.
risss said:
I couldn't unlock bootloader. When i type the command fastboot devices i get a string, but when i type fastboot oem get_unlock_data, i get this message “FAILED (remote: unknown command)”.
Click to expand...
Click to collapse
I have the same error ;_;
U are using CMD as admin, not PowerShell?
Vsx06 said:
U are using CMD as admin, not PowerShell?
Click to expand...
Click to collapse
I tried both ; -;
You can't unlock the bootloader. Don't bother with it. If you want something proper, get any device that's NOT from China, and especially form Lenovo (which is Motorola now).
**** LENOVO **** CHINA FREE HONG KONG.
I don't know if there's a moto e6 plus with enabled oem fastboot commands, it seems like Motorola didn't add support for oem unlock in this phone but maybe if we could get a hold of the download agent for Sp flash tool (since the device is a Mediatek powered device) and the auth file, we could get root via magisk patched boot.img
I searched for a little and i found nothing. I hope that someone manages to get a hold of those files, since the firmware is already available online.
Well, i managed to flash patched boot.img, but dm-verity is enabled and fstab is not on ramdisk because of project treble... now what
hookgab said:
You can't unlock the bootloader. Don't bother with it. If you want something proper, get any device that's NOT from China, and especially form Lenovo (which is Motorola now).
**** LENOVO **** CHINA FREE HONG KONG.
Click to expand...
Click to collapse
I beg to differ, as in developer option on the moto e6 plus there is a toggle for OEM unlocking,
I believe you need to get a code from Motorola to complete the unlock though,
I have not yet tested as I want to preserve warranty,
However with my moto e4 I was able to unlock bootloader and root without any issues,
Hell at one point I had to rebuild the entire system from an empty chip, (OS took me 4 Days) including rewriting the original imei numbers (that took me 2 weeks)
So no, lenovo is not as locked down as you seem to think it is,
As a side not, most phone are made with components that are built/assembled in China so it is actually quite hard to get a device that isn't at least partially made in China,
uanesgtgt2 said:
Well, i managed to flash patched boot.img, but dm-verity is enabled and fstab is not on ramdisk because of project treble... now what
Click to expand...
Click to collapse
I know the moto e4 required a no-verity flash to accept root,
Unsure if there is one that would work for the e6 yet,
Certainly something to look for,
uanesgtgt2 said:
I don't know if there's a moto e6 plus with enabled oem fastboot commands, it seems like Motorola didn't add support for oem unlock in this phone but maybe if we could get a hold of the download agent for Sp flash tool (since the device is a Mediatek powered device) and the auth file, we could get root via magisk patched boot.img
I searched for a little and i found nothing. I hope that someone manages to get a hold of those files, since the firmware is already available online.
Click to expand...
Click to collapse
It was added, it's hidden away in developer options,
May require an unlock code from Motorola though,