unlock bootloader and following root the device - Nokia 7.1 Questions & Answers

Hello there,
I've read many topics and watched many videos before bothering you guys here so I'm sorry if my question is too stupid or inappropriate, but I'm lost and really want get this done and play with my phone.. I'm new to android at all, coming from jailbroken iOS which I don't like that much these days, so I wanted to give android a try. First of all I'm using:
ubuntu 18.04
Nokia 7.1 - Android 10
model: TA-T1100
Build number: 00WW_4_08B_SP01
what I did:
1. downloaded fastboot and adb tools to my system by typing this in terminal
Code:
apt-get install android-tools-fastboot
Code:
apt-get install android-tools-adb
everything works fine, so next step for me was unlocking developer mode on my phone by taping on build number in about phone settings serval times after unlocking developer mode I allowed USB debugging in developer options.
now when I type this in my terminal
Code:
adb devices
Now after allowing debugging I can see my phone listed here
when I try type
Code:
fastboot devices
nothing happens
same with
Code:
fastboot reboot
terminal keep waiting for the device to connect but nothing happens
but when I try
Code:
adb reboot bootloader
my phone restarts and here comes the trouble... android-one logo appears with tiny text in the left corner which says "download mode" I gave it good 20 minutes but nothing else happens, noting else appears only what I can do is restart my phone by long pressing "turn on" button and boot normally
so if anyone can help me get thru this and actually root my phone I'd be grateful
have a nice day everyone

Related

Problems unlocking, not finding device..

Hi good people of the internet,
I recently brough a brand new ZTE Blade Vec 4G and i wanted to replace the Android OS that came with the device before i start using it, but i hit a snag when trying to run the shell commands via USB.
I have been trying via my Ubuntu machine, but i also tried allitle in Windows, but i got the same result there.
So far ive been following this list (could not post the links, but its via the main "Installing Ubuntu for Devices" page:
Unlock the Android device
To install Ubuntu, you must first “unlock” the Android device bootloader.
Warning: Unlocking deletes all data from the device, including apps and other data. You may want to create a backup first.
You must first have enabled USB Debugging in the Android OS.
Boot the device into the Android bootloader:
$ adb reboot bootloader
Tip: When the device is booted into the bootloader the screen displays the green Android robot lying on its back with its front panel open and a highlighted Start menu item.
Verify the device is connected to your Ubuntu Desktop as follows:
$ fastboot devices
025d138e2f521413 fastboot
Unlock the device as follows:
$ sudo fastboot oem unlock
Accept the terms of unlocking displayed on the Android device.
Reboot the device to Android as follows:
$ fastboot reboot
Complete the first use Android setup steps, entering minimal information: Android and its data is about to be deleted during the Ubuntu install.
Click to expand...
Click to collapse
Ive only made it to highlighted point, but when i hit "sudo fastboot oem unlock" it just stops on < waiting for device >, and when i try to find the device i cant see it when in "Android system recovery mode".
Any help would be great as ive spent near 5 hours trying to do this now
I don't think it's possible to unlock the bootloader on your device yet. From what I've read, even the adb reboot bootloader method does not actually get you into fastboot mode. Replacing the OS with Ubuntu will not be an option because of this as well as other reasons.
es0tericcha0s said:
I don't think it's possible to unlock the bootloader on your device yet. From what I've read, even the adb reboot bootloader method does not actually get you into fastboot mode. Replacing the OS with Ubuntu will not be an option because of this as well as other reasons.
Click to expand...
Click to collapse
Thank you for the reply. So how can i remove Android at all then? would it be better to try something like CyanogenMod or MIUI? I have also been looking at Firefox OS, but if i cant remove Android, then i cant really do much at all..
Just saw this thread:
http://forum.xda-developers.com/general/help/soshphone-4g-zte-blade-vec-root-t2810210/page1
Guess i just need to make do with the unrooted Android for now..
Pretty much stuck for awhile. There might never be an option for it. Many phones never get the chance to have different OSes or even custom versions of Android. Hopefully that's not the case, but it's not uncommon.

driver trouble

I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
Sorry to say, but you gotta follow this thread.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X
Since you may ignore the other thread you started or it may get deleted I'll copypasta here:
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04...xygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.

Can't unlock bootloader (iOcean X8 Mini)

Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!

[Question] ZTE Majesty Pro

Hello,
I have a Straight Talk ZTE Majesty Pro LTE [Z799VL]. It runs Android 6.0.1. This phone occasionally installs apps and has an annoying app called AppFinder. I have tried to root this phone with KingoRoot and KingRoot. So, I need help figuring out if this thing is even rootable. I would get a more accessible phone, but I'm short on money. I know this is short on information, but I'd be willing to help in any way I can.
Any help would be greatly appreciated.
Boop.
I'm fairly certain this phone was released recently. Maybe it's just too soon.
I have this same phone and am having the same problem finding info on how to root it. Keeping a hopeful eye on this thread
Any news for ZTE Majesty PRO unlock?
My friend just brought it from USA to Europe and he want to use it in normal way
Any news?
Any news?
Zte z799vl -
I have this phone and have tried many types to root it with no luck.
same here looking for root
Root
I've tried SRS King Kingo 360root etc... And many others and nothin so far. Any luck from anyone else?? Even temp root??
ZTE majesty pro z799vl tracfone
The OP is running Android 6 but I have the Straight Talk boxed ZTE Majesty Pro and it runs 7.1.1 out of the box.
There is a thread called Universal Method with a file and instructions but my Android device is the only PC I own so I haven't given it a try. The post has a Windows and a Linux method.
ChernobylBloodwolf said:
Hello,
I have a Straight Talk ZTE Majesty Pro LTE [Z799VL]. It runs Android 6.0.1. This phone occasionally installs apps and has an annoying app called AppFinder. I have tried to root this phone with KingoRoot and KingRoot. So, I need help figuring out if this thing is even rootable. I would get a more accessible phone, but I'm short on money. I know this is short on information, but I'd be willing to help in any way I can.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you unlocked the bootloader?
I recently upgraded to an Android 7.1.1 ZTE Majesty™ Pro Plus LTE (Z899VL) from TracFone,, and was rather dismayed to find out that it has an unremovable Facebook app (among other rubbish that I don't want/don't use).
I've never rooted a device before, and I know that this thread's a little old, but would anyone be willing to post a very-newbie-friendly step-by-step tutorial/walkthrough for rooting this phone (assuming it's possible)?
I have Developer Options enabled, and I can easily unlock the bootloader if that's required. I just want to get rid of these useless (for me) System Apps.
Oh, also: I don't have Linux, so… if it's possible, perhaps the rooting method could work using a Windows 7 PC?
need fastboot to unlock the bootloader. to the best of my knowledge, which aint much. but i can not find access to any kind of dl mode let alone fastboot.
Kizul said:
I recently upgraded to an Android 7.1.1 ZTE Majesty™ Pro Plus LTE (Z799VL) from TracFone,, and was rather dismayed to find out that it has an unremovable Facebook app (among other rubbish that I don't want/don't use).
I've never rooted a device before, and I know that this thread's a little old, but would anyone be willing to post a very-newbie-friendly step-by-step tutorial/walkthrough for rooting this phone (assuming it's possible)?
I have Developer Options enabled, and I can easily unlock the bootloader if that's required. I just want to get rid of these useless (for me) System Apps.
Oh, also: I don't have Linux, so… if it's possible, perhaps the rooting method could work using a Windows 7 PC?
Click to expand...
Click to collapse
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Augustoandro said:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
Click to expand...
Click to collapse
Well, I finally managed to get my 899VL (it's not a 799VL as I'd thought — sorry) to show up as an ADB device; it accepts commands from the ADB program… except that when I execute "adb reboot bootloader", it just reboots my phone.
The ZTE logo shows, then the TracFone logo, and then Android boots as normal. It's as though I simply used the "Restart" option on my phone itself.
Due to this, I can't use "fastboot" commands, because it doesn't seem to enter Fastboot at all.
I do have both the OEM unlocking and USB debugging options turned ON. My only guess as to what's going wrong is that it's TracFone's fault. (Alas, I have no proof…)
Is there anything else that I can do to try and unlock the bootloader? Or is this phone a lost cause?
Kizul said:
Well, I finally managed to get my 899VL (it's not a 799VL as I'd thought — sorry) to show up as an ADB device; it accepts commands from the ADB program… except that when I execute "adb reboot bootloader", it just reboots my phone.
The ZTE logo shows, then the TracFone logo, and then Android boots as normal. It's as though I simply used the "Restart" option on my phone itself.
Due to this, I can't use "fastboot" commands, because it doesn't seem to enter Fastboot at all.
I do have both the OEM unlocking and USB debugging options turned ON. My only guess as to what's going wrong is that it's TracFone's fault. (Alas, I have no proof…)
Is there anything else that I can do to try and unlock the bootloader? Or is this phone a lost cause?
Click to expand...
Click to collapse
Well, I don't know about any other method to unlock boot loader.
BTW, in case of some phones, turning on the "OEM Unlock" button in Developer Options unlocks the bootloader automatically, so maybe, just check whether your bootloader is locked or not.
Both Didn't work
Augustoandro said:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Click to expand...
Click to collapse
I tried using both the wasy for the first one the device not going to fastboot mode it just restarts for "adb reboot bootloader".
i tried KingoRoot, Dr Fone but it didn't work.
Did you unlock the ZTE Majesty Pro Z799VL with this method???
drona91 said:
I tried using both the wasy for the first one the device not going to fastboot mode it just restarts for "adb reboot bootloader".
i tried KingoRoot, Dr Fone but it didn't work.
Did you unlock the ZTE Majesty Pro Z799VL with this method???
Click to expand...
Click to collapse
No, these are general instructions which work for most phones.
Z799vl Help USB tethering

Trying to apply Nexus 6P bootloop fix

Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.

Categories

Resources