Database Info

Phone stuck on boot animation, won't sideload

I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.

pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?

All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.

rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1

pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.

zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")

You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus

rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back

rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."

pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?

rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1

pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed

pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.

[Q] systemUI broken?

Hey,
I have a major issue on my HAM7 L09, which runs on 5.1 lollipop, is rooted and has TWRP recovery.
Yesterday I was triyng to install Xposed framwork via TWRP. Okay, that failed. But then, when I rebooted my phone, my softkeys and Statusbar, overall SystemUI, is not working. I tried factory reset which didn't help. Since i did factory reset, i can no longer use adb commands from my computer, because it wont no longer authorize my phone. Even tried to downgrade to B127 to install custom rom after that, but because I have TWRP I cant downgrade. And since adb commands are not working, I cannot flash stock recovery either.
Any help please?
Urgent.
Thank you

Getoo said:
Hey,
I have a major issue on my HAM7 L09, which runs on 5.1 lollipop, is rooted and has TWRP recovery.
Yesterday I was triyng to install Xposed framwork via TWRP. Okay, that failed. But then, when I rebooted my phone, my softkeys and Statusbar, overall SystemUI, is not working. I tried factory reset which didn't help. Since i did factory reset, i can no longer use adb commands from my computer, because it wont no longer authorize my phone. Even tried to downgrade to B127 to install custom rom after that, but because I have TWRP I cant downgrade. And since adb commands are not working, I cannot flash stock recovery either.
Any help please?
Urgent.
Thank you
Click to expand...
Click to collapse
Hey Buddy, i did the same thing you did when twrp came out which was to install xposed. Also got the same issue where aspect's of the phone's UI (Status bar, nav bar, homescreen) were missing. I even did the factory reset via twrp. I was able to get out of it, but it required some focus, patience and lots of rebooting. I don't recall exactly what I did for the first step, butThat being said when you plug you phone to your PC, does your PC still recognize it? (ex.prompt to install Android Hisuite Manager pops-up on your monitor)
- If the answer is yes, with your M7 connected to the PC, enable "Developer Options" (if you haven't done it yet)>then reboot. On next boot>go to Developer's Options again>select "Revoke USB Debugging Authorizations".
-Once done, remove the USB connection from your PC's USB port then place it back in again. Let me know if the "ADB Authorization" screen appears.

Okay, as soon as I get home, I'll try that. Right now I'm using button saviour for softkeys
Sent from my HUAWEI MT7-L09 using XDA Free mobile app

blitzkriegger said:
Hey Buddy, i did the same thing you did when twrp came out which was to install xposed. Also got the same issue where aspect's of the phone's UI (Status bar, nav bar, homescreen) were missing. I even did the factory reset via twrp. I was able to get out of it, but it required some focus, patience and lots of rebooting. I don't recall exactly what I did for the first step, butThat being said when you plug you phone to your PC, does your PC still recognize it? (ex.prompt to install Android Hisuite Manager pops-up on your monitor)
- If the answer is yes, with your M7 connected to the PC, enable "Developer Options" (if you haven't done it yet)>then reboot. On next boot>go to Developer's Options again>select "Revoke USB Debugging Authorizations".
-Once done, remove the USB connection from your PC's USB port then place it back in again. Let me know if the "ADB Authorization" screen appears.
Click to expand...
Click to collapse
Being tring your solution for 4 hours. Sadly it doesn't work. authprization screen wont appear

Getoo said:
Being tring your solution for 4 hours. Sadly it doesn't work. authprization screen wont appear
Click to expand...
Click to collapse
Does your computer recognize your phone?

blitzkriegger said:
Does your computer recognize your phone?
Click to expand...
Click to collapse
yes, it does. I can watch my folders and so on.

Getoo said:
yes, it does. I can watch my folders and so on.
Click to expand...
Click to collapse
Sorry for the late reply Buddy as I'm at work at the moment. Found an easier solution. Make sure your phone is connected to your computer. Also open up the folder where you have your ADB files ans stock lollipop recovery. Open the command prompt within that folder.
Next do the following
1.) Turn off your phone and manually invoke TWRP via physical button combination
2.) Once on TWRP, select "Reboot" then choose "Bootloader".
3.) Once the phone is on bootloader mode, connect your phone to your PC's USB port then switch to your open command prompt and type:
fastboot devices
Your device should then be displayed.
4.) next flash the stock lollipop recovery for L09 via the command:
fastboot flash recovery <recoveryname.img>
5.) Once done flashing execute:
fastboot reboot
6.) Once your phone is back on, you can then use your computer to place the "Transition" update.app either within internal storage (create dload folder within internal memory) or sd card/usb drive. Proceed to do local update or update from usb.
7.) Once your phone has the transition lollipop firmware copy the Kitkat rollback firmware then do the usual drill via local/usb update.

blitzkriegger said:
Sorry for the late reply Buddy as I'm at work at the moment. Found an easier solution. Make sure your phone is connected to your computer. Also open up the folder where you have your ADB files ans stock lollipop recovery. Open the command prompt within that folder.
Next do the following
1.) Turn off your phone and manually invoke TWRP via physical button combination
2.) Once on TWRP, select "Reboot" then choose "Bootloader".
3.) Once the phone is on bootloader mode, connect your phone to your PC's USB port then switch to your open command prompt and type:
fastboot devices
Your device should then be displayed.
4.) next flash the stock lollipop recovery for L09 via the command:
fastboot flash recovery <recoveryname.img>
5.) Once done flashing execute:
fastboot reboot
6.) Once your phone is back on, you can then use your computer to place the "Transition" update.app either within internal storage (create dload folder within internal memory) or sd card/usb drive. Proceed to do local update or update from usb.
7.) Once your phone has the transition lollipop firmware copy the Kitkat rollback firmware then do the usual drill via local/usb update.
Click to expand...
Click to collapse
Holy god, dude you are awsome, it worked. Thank you so much. :angel:

[Tested]How to Root the Moto X Play

I. Before You Begin
1. This could void the warranty of your device. We won’t be held responsible for anything that happens from doing this tutorial so please proceed at your own risk.
2. You need a Windows based PC in order to do this procedure.
3. You should have Motorola USB drivers installed on your PC. If you don’t, install them first.
4. This should erase all the data stored on your device. So, please backup everything that you’ll need.
5. This should also flash a custom recovery on your device.
How to Root the Motorola Moto X Play
Root the Moto X Play
Photo Credit: fonearena.com
To root the device, you’ll first unlock the bootloader, flash a custom recovery, and then flash SuperSU using the custom recovery to achieve root access. Here’s how:
II. Downloading Required Files
1. Download Fastboot and save it to your desktop.
Fastboot
2. Download TWRP Recovery and save it to your desktop.
TWRP Recovery
3. Download SuperSU and save it to your desktop.
SuperSU
III. Unlocking the Bootloader on the Motorola Moto X Play
1. Extract files from Fastboot over to your desktop by right-clicking on it and selecting Extract here.
2. Turn off your device.
3. Turn your device back on in fastboot mode. To do that, hold down Volume DOWN and Power buttons together for a few seconds.
4. Your device should now be in fastboot mode.
5. Plug in your device to your PC using a USB cable.
6. Launch a Command Prompt Window on your desktop by holding down Shift and right-clicking anywhere on the screen and selecting Open command window here.
7. Type in the following command into the Command Prompt Window and hit Enter:
Code:
fastboot oem get_unlock_data
8. You should see a string of text on your screen. Copy it to your clipboard removing any spaces so that it is a long string of text.
9. Head over to the Motorola Bootloader Unlock website and get yourself logged-in. If you don’t have an account with them, create one now.
10. One of the steps on that website will ask you to paste the string of text. Just paste the string that you’ve already copied to your clipboard and follow the on-screen instructions.
11. You’ll receive an unlock key to your email address. Copy that key to your clipboard.
12. Now, type in the following command replacing KEY with the actual unlock key that you’ve copied to your clipboard and hit Enter:
Code:
fastboot oem unlock KEY
13. Wait for it to unlock the bootloader on your device.
14. When it’s done unlocking the bootloader, reboot your device by issuing the following command:
Code:
fastboot reboot
15. Your device should reboot.
And there you go.
The bootloader on your Motorola Moto X Play is now unlocked, and you can now flash a custom recovery on your device. Here’s how you can do that:
IV. Flashing a Custom Recovery on the Motorola Moto X Play
1. Turn off your device.
2. Reboot your device into fastboot mode by holding down Volume DOWN and Power buttons together for a few seconds.
3. Connect your device to your PC using a USB cable.
4. Open a Command Prompt Window on your desktop. To do that, hold down Shift and right-click anywhere on your screen and select Open command window here.
5. Type in the following command into the Command Prompt Window and hit Enter. Make sure to replace recovery.img with the actual name of the recovery image that you have downloaded.
Code:
fastboot flash recovery recovery.img
6. Wait for it to flash a custom recovery on your device.
7. When it’s done flashing a recovery, reboot your device by using the following command:
Code:
fastboot reboot
8. Your device should reboot.
Your Motorola Moto X Play now has a custom recovery using which you can gain root access on your device. Here’s how:
V. Rooting the Motorola Moto X Play
1. Connect your device to your PC using a USB cable.
2. Copy SuperSU .zip from your desktop over to the internal SD card storage on your device.
3. Unplug your device from your PC when SuperSU is copied.
4. Turn off your device.
5. Turn your device back on in recovery mode. To do that, hold down Volume DOWN and Power buttons together.
6. Your device should reboot into bootloader mode.
7. Select Recovery from the options appearing on your screen.
8. Select Install in the recovery menu.
9. Choose SuperSU .zip to be installed on your device.
10. Tap on Swipe to Confirm Flash to confirm flash.
11. Wait for it to flash SuperSU on your device.
12. When it’s done flashing SuperSU, reboot your device by selecting Reboot followed by System in the recovery menu.
13. Your device should reboot.
Source: http://theunlockr.com/2015/09/21/root-motorola-moto-x-play/

Nice plagiarism here..... [emoji35]

How is it plagiarism if I have mentioned the source?

going into recovery mode gives me the dead android with the red triangle logo with the text "no command." under it. i tried both twrp versions.

Auros42 said:
going into recovery mode gives me the dead android with the red triangle logo with the text "no command." under it. i tried both twrp versions.
Click to expand...
Click to collapse
The same here (Dual-Sim-Version) :crying:
Also link forFastboot ist down

route9 said:
The same here (Dual-Sim-Version) :crying:
Also link forFastboot ist down
Click to expand...
Click to collapse
Make sure you get this version.
twrp-lux-2.8.7-v2.img
for fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790

This works, I tried that, I have root now
Enviado desde mi XT1562 mediante Tapatalk

I can confirm that this recovery worked.
Model India Moto X Play Dual Sim - (xt1562)

route9 said:
The same here (Dual-Sim-Version) :crying:
Also link forFastboot ist down
Click to expand...
Click to collapse
Flash TWRP again & boot TWRP before booting Android again. The stock rom tries to replace TWRP but TWRP will fix that on its first boot.

mahir1995 said:
Flash TWRP again & boot TWRP before booting Android again. The stock rom tries to replace TWRP but TWRP will fix that on its first boot.
Click to expand...
Click to collapse
There was trouble with opening bootloader. I used a opening-tool, which said, that the device bootloader is now open - but it wasn´t. Everything´s ok now. I managed bootloader-opening with cmd.exe.

I think this thread should be titled "tested" instead of "untested".... works great! thanks

Dear Android Gurus,
I am new to XDA forum. I am going to try rooting my new Moto X Play and I am pretty excited about this as I am trying this for the first time. Can someone please confirm if the steps given here or in theunlockr website works for Moto X Play?
Mine is the Indian version - Model# XT1562 and below are the details. Please advice.
Hardware SKU: XT1562
Baseband Version: M8936_2020613.22.03.21.33R
LUX_EMEA_DSDS_CUST
Kernel version:
3.10.49-g6d623da
[email protected] #1
Wed Jul 15 21:06:16 CDT 2015
System version
23.21.10.lux_retasia_ds.retasiaall.en.03 retin
Build number
LPD23.118-10

koolkans said:
Dear Android Gurus,
I am new to XDA forum. I am going to try rooting my new Moto X Play and I am pretty excited about this as I am trying this for the first time. Can someone please confirm if the steps given here or in theunlockr website works for Moto X Play?
Mine is the Indian version - Model# XT1562 and below are the details. Please advice.
Hardware SKU: XT1562
Baseband Version: M8936_2020613.22.03.21.33R
LUX_EMEA_DSDS_CUST
Kernel version:
3.10.49-g6d623da
[email protected] #1
Wed Jul 15 21:06:16 CDT 2015
System version
23.21.10.lux_retasia_ds.retasiaall.en.03 retin
Build number
LPD23.118-10
Click to expand...
Click to collapse
Bro, don't root if you root u will not receive android marshmallow update for your phone, and u will lose your warranty

RahulPrasad said:
Bro, don't root if you root u will not receive android marshmallow update for your phone, and u will lose your warranty
Click to expand...
Click to collapse
Why not? You can get the better system, called CyanogenMod . And after i tested my phone for 3 weeks i dont need warrenty. Works perfect, and cm 12.1 with a new kernel is fantastic.
Bye, Klaus

RahulPrasad said:
Bro, don't root if you root u will not receive android marshmallow update for your phone, and u will lose your warranty
Click to expand...
Click to collapse
Hi Rahul, Do you mean I should wait for the marshmallow update to be done and after that I can root or should I wait till the warranty period gets over?

If you root you will be able to get any marshmallow rom that is available for the phone anyway. So don't worry about that nonsense. The warranty however is a different issue. It's all about whether you see the 'risk' as worth it.

Work !!
I root it in ten minute, thanks.

Can it be changed to say 'tested and works great', as it does.
Sent from my XT1562 using Tapatalk

I also have a concern on rooting. I like Moto Display function, so if I root it, I will lose it, so I will not.

SteveCC said:
I also have a concern on rooting. I like Moto Display function, so if I root it, I will lose it, so I will not.
Click to expand...
Click to collapse
That's a function of the ROM. I'm rooted with a custom recovery and stock ROM, and still have it.

Impossible to continue my setup at first time

Hi, i install android P beta one my One plus 6, then i downgrade its good. I start my phone and at the step copy apps & data i selec: Set up as new. Then i connec my wifi or LTE. I click next and my phone watch the next step and instant backwards. I cannot go in my os. I try everythings, fasstboot, wipe cache reset all. I go the Error in time : Google plays stop working, but i can do anything.

Same problem here. I need serious help

d3dev said:
Same problem here. I need serious help
Click to expand...
Click to collapse
I contact the support one plus, i send my phone for repair ....

w4n7ed said:
I contact the support one plus, i send my phone for repair ....
Click to expand...
Click to collapse
You flashing ROMs or betas isn't something they will cover under warranty

TechOut said:
You flashing ROMs or betas isn't something they will cover under warranty
Click to expand...
Click to collapse
I nothing flashing, i just update my phone with android P and downgrade with oxygen OS

w4n7ed said:
Hi, i install android P beta one my One plus 6, then i downgrade its good. I start my phone and at the step copy apps & data i selec: Set up as new. Then i connec my wifi or LTE. I click next and my phone watch the next step and instant backwards. I cannot go in my os. I try everythings, fasstboot, wipe cache reset all. I go the Error in time : Google plays stop working, but i can do anything.
Click to expand...
Click to collapse
Okay so I found a somewhat working solution after 10hrs of trying to get this to work.
1. Get fastboot and ADB package and install it on your PC.
2. Get the Developer Preview ROM and move it to your adb and fastboot install directory.
3. Get TWRP from the official website for OnePlus 6. Only the .img file and put it in the same folder. - here - dl(.)twrp(.)me/enchilada/
4. Go to the ADB and Fastboot install directory and click "CMD-HERE.exe".
5. Hold down the power and vol. down button and enter recovery mode. Then click on advanced options and from there boot into Fastboot.
6. When successfully in Fastboot mode, use this command in the CMD that opens :
Code:
fastboot boot twrp-3.2.1-0-enchilada.img
You should enter into TWRP recovery.
7. Type this command :
Code:
adb push OnePlus6Oxygen_DP1_180516.zip /sdcard/
8. Now click on install and scroll down until you see the ROM we just moved to the phone and install it. It should install successfully and after that reboot your device and you will be able to set up your device successfully.
After that, if you wish to return to Stable release then FOLLOW THE INSTRUCTIONS ON THE OFFICIAL POST ON THE ONEPLUS FORUMS

(guide) root nokia 3 android 9.0

Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing

https://drive.google.com/open?id=1HtjdNjdJ3XiSaOAUNVwZ8E-tGv3xr2Ly
https://drive.google.com/open?id=1eFpvFeUe_xLRUFnBbT2ZzKdTgX8-nyYQ

I will try it and see that it breaks this time

Marakas89 said:
Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing
Click to expand...
Click to collapse
Thanks for share
work fine in me

wirdan.hungkul said:
Thanks for share
work fine in me
Click to expand...
Click to collapse
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c

djxpro said:
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c
Click to expand...
Click to collapse
I don't have Ota update ..., you should re-flash your device

wirdan.hungkul said:
I don't have Ota update ..., you should re-flash your device
Click to expand...
Click to collapse
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c

djxpro said:
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c
Click to expand...
Click to collapse
bootloader must be activated ..

wirdan.hungkul said:
bootloader must be activated ..
Click to expand...
Click to collapse
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.

djxpro said:
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM

wirdan.hungkul said:
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM
Click to expand...
Click to collapse
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same

djxpro said:
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same
Click to expand...
Click to collapse
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS

Apparently it is an issue of the operator that I do not have the update yet.
I went back to 8.0 while I find out what happened to the ota.
And if it comes out I'll capture it.

wirdan.hungkul said:
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS
Click to expand...
Click to collapse
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command

Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 through recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again

djxpro said:
Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 thrgough recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again
Click to expand...
Click to collapse
:good:

Well.....i thought let me give it a try.....but.....problem started then...
--- adb works fine.....both the commands (adb devices and adb reboot bootloader) gets executed
--- but my device doesn't get detected in fastboot mode
--- thinking that its problem with drivers...i tried every driver (adb and fastboot) out in the internet and nokia drivers...but got no luck
--- hoping that someone could help me i posted here.... thanks in advance

djxpro said:
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command
Click to expand...
Click to collapse
i found a way to flash the patched boot and unlock the bootloader on pie
Here

NulledRoot said:
i found a way to flash the patched boot and unlock the bootloader on pie
Here
Click to expand...
Click to collapse
actually, i have a rooted phone.
but, i lock the bootloader again, and now, i need connect to usb to start up
without usb, i give a red state
.-.)

my phone stuck at reboot loop can someone help me?