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
Related
I've looked around and I can't seem to find a way to unlock the bootloader on my 2.3.6 Atrix. Most tuts are for 2.3.4. What's the best way to do it?
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
G-Man. said:
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
Click to expand...
Click to collapse
You just run those in ADB, right?
mugabuga said:
You just run those in ADB, right?
Click to expand...
Click to collapse
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands and reboot your Atrix when you've finished - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
G-Man. said:
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
Click to expand...
Click to collapse
But even if I've never unlocked it, it should still work?
mugabuga said:
But even if I've never unlocked it, it should still work?
Click to expand...
Click to collapse
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
G-Man. said:
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
Click to expand...
Click to collapse
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
mugabuga said:
Alright. It says it worked on the phone, but my RSD Lite claims it failed with an error switching phone to BP Pass through mode (0x70BE). Its just hanging at the success screen on my phone.
Click to expand...
Click to collapse
Can you upload a pic of the screen you are seeing?
[edit] I gotta get to bed, I'll check back here tomorrow if someone else is unable to assist you tonight. Its after midnight here and I'm getting over a bad cold still. I will check back here tomorrow.
mugabuga said:
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
Click to expand...
Click to collapse
Glad to hear that Ya had me a bit concerned for a minute there...
I'm new to rooting phones I have a Moto Photon 4G. Ido have root access but when i try to boot into Android Recovery i get a message saying fail boot 2 entering RSD mode. So I'm not able to flash any roms to my phone. It's getting frustrating I have used google to find a solution but I'm a NOOB haha so I'm not really sure what I'm looking for. Please can anyone help?
Have you unlocked it? Can't do much without unlocking and installing a custom recovery.
If not, start here.
I'm pretty sure it's unlocked but how can I be sure. I used Root check basic and it confirmed I do have root accsess.
Root and unlocking are two separate processes. When you boot the phone, if you're unlocked, it will say unlocked in the upper left on the screen with the red m.
Sent from my MB855 using XDA
My phone is not unlock so what is the next step I need to take to unlock it? Thank you all for your help. I'm begging lol please help it's making me crazy
The link Kevets gave you will tell you everything you need to know. And if you look for qbking77 on youtube he has walkthroughs for the process.
Sent from my MB855 using XDA
if you email me i'll give you the link i can't post links yet.
shows step by step how to unlock my phone but i get stuck on this part below
Now click your start menu and type "cmd", right click the cmd program and copy it to your unlock pack directory.
i'm not sure how to copy it.
Open the newly copied cmd.exe and type "fastboot oem unlock xxxxxxxxxxxxxxxx" WITHOUT THE " " MARKS and replaces the x's with your code that you got from the above step.
The links were helpful but some are outdated or my comp says they contain malware and wont allow me to proceed any further and yes qbking77 has very helpful videos
bigdaddy619 said:
motorolaphoton.webs.com/ unlocking
shows step by step how to unlock my phone but i get stuck on this part below
Now click your start menu and type "cmd", right click the cmd program and copy it to your unlock pack directory.
i'm not sure how to copy it.
Open the newly copied cmd.exe and type "fastboot oem unlock xxxxxxxxxxxxxxxx" WITHOUT THE " " MARKS and replaces the x's with your code that you got from the above step.
The links were helpful but some are outdated or my comp says they contain malware and wont allow me to proceed any further and yes qbking77 has very helpful videos
Click to expand...
Click to collapse
Once the cmd.exe comes up in your start menu, right click it and choose "copy." Then open your unlock pack directory (where you unzipped the unlock pack zip file) and right click, then choose "paste." Then double click the pasted cmd.exe. I'm not sure what has you stuck exactly.
Sent from my MB855 using XDA
I give up apparently I'm to stupid to do it Thanks for your help
I have watched qbking77 videos
How to install the Android SDK, ADB and Fastboot on your PC
How to unlock the Motorola Photon 4G bootloader
Installing Android SDK, ADB and Fastboot didn't work for me.
Hope this helps
Try my site and tell me if that helps.
https://sites.google.com/site/mophocorner/
You need to unlock your phone and flash CWM in order to put a custom rom on it. Rooting it is he easy stuff. If you flash a custom rom 99.5% of the time it is pre rooted so...
I have tried that method with no success. Thanks for your help
You have to use RSD-lite to flash the stock phone rom back onto your phone before you can unlock it.
I did the same thing you did when I first tried to load a custom rom, and many other people here have done the same thing as well, we have all gotten through it. It took me about 5 hours of trying to get everything straightened out, and the next day I was running overclocked CM7 with jokers kernel.
Close please
Sent from my MB855 using xda app-developers app
Hi Guys, Just to let everyone know the command for unlocking the bootloader is now "fastboot flashing unlock" oem unlock will return an error and no longer functions.
Isn't the command just "fastboot oem unlock"?
overlord727 said:
Isn't the command just "fastboot oem unlock"?
Click to expand...
Click to collapse
Not anymore it would seem.... fastboot oem unlock returns an error
according to the android developer FAQ, "flashing" is the correct command, but I can't figure out why.
https://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
it made me start to wonder if OEM would somehow trigger the fuse, whereas FLASHING is specifically designed not to. anyone know why there's a "unlock bootloader" switch in the developer options within Android?
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Kitch16 said:
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
Click to expand...
Click to collapse
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Kitch16 said:
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Click to expand...
Click to collapse
Yes, Confirmed on my 6P.
Cheers bud, saved me spending more than the 30 mins I have already done pulling my hair out.
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
Tung_meister said:
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Yes, Confirmed on my 6P.
Click to expand...
Click to collapse
Did it trip your eFuse?
Kitch16 said:
Did it trip your eFuse?
Click to expand...
Click to collapse
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Born<ICs said:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Click to expand...
Click to collapse
TWRP isn't available for the Nexus 6P yet!
But when it is available, we'll have to cross that bridge when we come to it.
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Born<ICs said:
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Click to expand...
Click to collapse
I got in to Fastboot by holding volume down and powering on the phone as normal.
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
So what causes the Qfuse to blow?
Being a Nexus device shouldn't command be fastboot oem unlock. Curious
On the official Google Developers Factory Images page it’s still “fastboot oem unlock”.
http://forum.xda-developers.com/nexus-6p/general/fastboot-unlocking-command-t3233722/page2
To add to this also make sure your Android SDK is fully up to date
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
indianajonze said:
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
Click to expand...
Click to collapse
Does qfuse trip if you relock bootloader?
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
GCbard said:
Does qfuse trip if you relocation bootloader?
Click to expand...
Click to collapse
Does qfuse trip if one flashes a rom?
Will huawei give any trouble if we unlock the bootloader, does anyone think its worth it? I would like to try cm when it does release and right now I'm thinking of trying the mod to turn on and off swap
Sent from my KIW-L24 using Tapatalk
Turning on and off swap is the main reason I want to unlock the bootloader at the moment. Just haven't had time yet.
Arobase40 said:
If you're talking about commercial and customers side, and for what I know Huawei won't give any kind of supports with unlocked devices.
On the legal side it may depend on your country or region laws for the hardware warranty : Europe is more protective with customers...
So the answer is YES, you may have trouble with Huawei and with unlock devices if you're seeking after any kind of supports. Otherwise you can do what you want as the device is yours...
Click to expand...
Click to collapse
Yea was wondering about that and if I ever needed any repairs, I ended up doing it anyway everyone here seems to be unlocking anyway
Sent from my KIW-L24 using Tapatalk
Silly question, but what is swap?
Sent from my KIW-L24 using Tapatalk
Is there a tool made for this device yet for flashing adb fastboot? I used adb fastboot to unlock my L24 but when trying to flash the recovery.img that is where I hit a wall. I am not to up on adb fastboot besides simple commands for logs and unlocking a bootloader such as this. when I open a comand prompt it doesn't see the img file and give me a fail message. I just thought I would check to see if anyone has made their own tool yet. Thank you for your time.
Arobase40 said:
I may probably misunderstand your post but if you passed the bootloader unlocking process the rest of the procedure should be straightforward...
The "recovery.img file" (could be named differently) should be in your local system folder (Windows or Linux) and not in the phone (so no adb shell command) and make sure you ticked the USB debug mode in the developer panel...
The full procedure is here :
http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190
Click to expand...
Click to collapse
Yes, that was the post I was using as a guide. All the commands worked great to it came to the part where I had to flash recovery in bootloader mode. It wouldn't/couldn't find the destination file. I will just have to read some more and figure this out. Thank you for your reply. I'm almost done, just have to get recovery flashed now and I'll be good to go.
"Chance Favors the Prepared"
Probably 70% chance of having some hassle with warranty with bootloader unlocked, they will also blame any glitches on software or roms you using.
I scenario where phone 100% power dead they likely never look into bootloader or rom status so won't matter .
your region & person dealing with it will make huge difference on the day ...
Arobase40 said:
I still don't understand your actual position and troubles...
- Is your bootloader already unlocked ?
- If yes, so I guess you have already installed the Honor drivers and setup the adb software ???
- Which OS are you using ?
I don't know what you call the destination file, but you simply need to download the recovery file in step 8, and then continue to step 11.
If the downloaded file is "kiwi_twrp_3-21_recovery.img" save it to for example to your C:\temp folder.
When you open the command prompt, simply "cd c:\temp"and change the command "fastboot flash recovery twrp_kiwi.img"with "fastboot flash kiwi_twrp_3-21_recovery.img" or rename the original name to a simpler one, what suite you the best.
---------- Post added at 01:44 PM ---------- Previous post was at 01:34 PM ----------
I have written different posts about warranty and the fact that manufacturers say you'll be out of warranty if you unlocked or rooted your devices has no chance to be applied according to your local laws. The manufacturers contractual rules has no value if the local laws say differently !
Click to expand...
Click to collapse
Thank you Sir. That is exactly what I needed. I needed to know where to put the .img TWRP file, the destination, and his to access that file then with the command prompt.
Yes, my bootloader was unlocked successfully and adb had no problems picking up my device. It just couldn't locate the file that I was typing into the command prompt window. A lot of the roles that are out for use have spoiled me and that is all automate because everything is located in the same folder. I need to learn this though.
Thank you again.
"Chance Favors the Prepared"
Again, thank you. That was all I needed. It worked great once I put the TWRP.img file where it needed to be. I am unlocked, have custom recovery installed and am now rooted.
Chance Favors the Prepared "
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