Rooted when I first got the tablet, was not using it much. Used Kingoo to remove root. On reboot it is now stuck at the NVidia logo.
When I reboot into recovery mode and select factory reset I get a CWM manager screen, select factory reset and reboot. Still stuck on the NVidia logo (currently in excess of 30 minutes.)
Any ideas?
Solved it:
Solution:
1. Register for the NVidia Developer program (I chose the gaming selection, not hardware). Takes about 30 seconds: https://developer.nvidia.com/gameworks-registered-developer-program
2. Download & unzip the Shield Software: https://developer.nvidia.com/gameworksdownload
NOTE: Make sure you download the correct version for your Tablet. WIFI, LTE-USE or LET-RoW (Rest of World). DO NOT FLASH THE WRONG ONE.
3. Download the Minimal Fastboot and ADB http://forum.xda-developers.com/showthread.php?t=2317790
4. Install the drivers for the shield from the NV download in step 2. The one PDF in the download is instructions (ish) if you need them.
5. Run the Minimal Fastboot and ADB installer.
6. Copy the contents of the fastboot folder to the NV folder from Step 2 (this is easier than editing the path for a single use).
7. Power off the tablet and connect it via USB to your computer
8. Hold down the Volume Down button for 3 seconds, press the power button and continue holding the volume down.
9. At the recovery screen you will see a menu. Look carefully. The bootloader will need to be unlocked. If it is locked see the note below. Select fastboot and press power. (I am not sure this step is required, since it returned me to the same menu, but it worked)
10. from the NV folder in step 2, double click "flash-all.bat" to flash the tablet.
If this did not work I would imagine that your boot loader is locked.
NOTE: To unlock the bootloader (Instructions are from NVidia directly)
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
The complete instructions from NVidia (may be easier for some)
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Quick resolvement! Nobody could comment in the meantime.
My original K1 is stuck like a bootloop, will try this!
DizzyDee said:
My original K1 is stuck like a bootloop, will try this!
Click to expand...
Click to collapse
For a stock K1 (no custom recovery TWRP, etc.) I'd say the process outlined above is your best bet (restore stock recovery image).
I don't think you have to register to the Nvidia Developer Program anymore. Just go to the NVIDIA Download Center (as linked in the post above), find the right image, and download. Use search term "K1" and you should see the right image as one of the top few results. I believe version 5.2.0 is the last one that was released.
Once downloaded, flash the partitions using fastboot, as noted in the instructions.
Hello Everyone
I use YU Yuphoria 5010 since more than a year with original cyanogenmod updated via updater to 12.1 without root and locked bootloader.
Since a month i have been facing force closure in many apps so i downloaded the cyanogenmod 12.1 reovery rom and did dirty flash via recovery solved settings app force closure but not all FC. Then I decided to clean flash a custom rom since cyanogenmod is closed now and also lineage and Yuos have no Volte support.
For this i read many posts forum properly unlocked my Yuphoria with Doomlord's method then rooted it and then flashed TWRP 3.0.0.0 on it and then did clean install of MIUI by Gaggu,and then Rohan successfully and used them but volte was not working. Then flashed stock rom by Yukick and everything (volte + vilte) was working fine exceptfor phone shutting down at 40% of battery.
Then decided for resurrection remix (5.8.1) and flashed it successfully. Tested it for three days some force closure were there also Vilte (not Volte) also not woking. Then saw a RR update (5.8.2) on resurrection remix download page for Yuphoria downloaded it and first time done a dirty flash (every previous flash was a clean flash this time I thought i am already on RR so no problem should be there).
There starts my problem the phone stuck at YU logo then tried to enter the Twrp recovery but could not. So flashed twrp via fastboot again and then wiped cache, delvik cache but no use could not start the phone. so tried to clean flash original cyanogenmod 12.1 rom ( that i used as for dirty flash many times to rectify some fc before) but could not.
Then read many threads on Yu forum and XDA forum and tried many things but no use.
Now the present condition is i can enter Fastboot mode by pressing vol up + power button with
cyanogen fastboot written on screen and can execute various fastoot commands but cannot flash rom as
Fastboot -i 0x2a96 flash system system.img
fail to write system.
I can't enter recovery with vol down + power button (after i entered the command Fastboot erase recovery previously i can enter the recovery by pressing vol down + power button, I did so to replace the TWRP with CWM recovery but no success) Phone starts YU logo appears for some time and then Blank screen.
But i can enter recovery via Fastboot with command
Fastboot -i 0x2a96 boot twrp_3.0.0.0_lettuce.img
but in twrp cannot mount system, data and cache partition tried various things like full wipe and repair file system change file system but no use. Twrp shows intenal storage 0 mb. also cannot flash other custom recovery if i try to flash other custom recovery via fastboot it says ok but cannot boot into recovery but when tried to enter via fastboot command phone enters in cyanogenmod recovery. it can also boot in recovery of Fastboot stock rom via fastboot command.
Fastboot -i 0x2a96 oem device-info
shows
device tampered false,
device unlocked true,
Charger screen enabled true.
I can lock the bootloader also by command
Fastbbot -i 0x2a96 oem lock
then device-info shows
device unlocked false
(without bootloader restart if restarted it shows device
unlocked true).
when enetered in TWRP 3.0.0.0 via fastboot command the phone is also shown as MTP device in Windows but only memory card is shown as storage no internal storage.
if i try to start the phone by pressing power button it stucks at YU logo.
if i connect the phone to computer while it is poweroff it is shown as Android Phone (Android
bootloader interface) in Device manager on my windows 7 laptop.
any other information or screen shot if needed I will provide.
Thanks in advance
For me also same error, possibly because of Flash memory life cycle end.
I found my Shield Tablet again today. I tried to install a costom ROM once, but I think I failed with rooting my tablet. The reason for this is, that i had no clue what i was doing.
I would like to have a fully functional tablet again, but i still have no clue what to do.
I try to describe the current status.
- I have a Shield Tablet 16GB Wlan with Android 5.1.1
- With Root Checker: No root.
- In the Bott menu it shows that the device is unlocked.
- There is a SuperSU app, but i get a notification , that the SU binary needs to be updated. If I do that it fails every time and tells me to reboot. After that nothing changed. Same Problem.
- There is a OTA Update, when i try to restart my tablat this comes up:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
After testing both, no changes
I tried to find a solution on my own for the last 3h, but I just failed over and over again.
Root access is optional for me now, i don't need it, but it would be nice to have it.
Could someone tell me what I should do? (Or post a link to instructions wich fits to my problems)
Thanks in advance
What version of software are you on? I recommend downloading the last Marshmallow recovery image available (for the original Shield, it's package 4.4), unzip the contents to give you the various images, and then flash using Fastboot. Just boot the tablet while holding down the power+vol down key, then release when the screen lights up. Plug into your PC, and run the Minimal ADB+Fastboot (google it, I think version 1.4 is latest).
Download site from Nvidia: https://developer.nvidia.com/gameworksdownload
Follow the instructions in the recovery package. Basically like this, assuming your images are in your fastboot directory:
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018
"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin
volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs
Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.
unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!
Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this
@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs
not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s
What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs
Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.
@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs
I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?
ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.
@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs
I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).
I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.
unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.
Code:
TRY THIS AT YOUR OWN RISK! This could brick your phone. It shouldn't but it can. If you brick your phone, or anything stops working on your phone, YOU are responsible.
Reboot combinations:
Fastboot: Shutdown and with USB cable hold power and volume down until it says FASTBOOT MODE at the bottom
Recovery: Shutdown and with USB cable hold power and volume down until the
Code:
Please release key to power off *
dissapears.
Unlocking Bootloader
Code:
Note: This will delete all user data! Backup all your data before doing this!
This part of the guide is part of the tutorial made by @Arin59 at https://forum.xda-developers.com/nokia-3/how-to/method-to-unlock-bootloader-nokia-3-pie-t4012285
First of all convert your serial number (should look like NE1*************) to MD5 Hash and enable OEM Unlock in developer options.
Then reboot to fastboot and type
Code:
fastboot oem key {HASH}
then type
Code:
fastboot flashing unlock
.
To reboot to Android, run fastboot reboot.
Installing TWRP
Code:
This will delete your user data, but it should be already deleted.
You can use any TWRP image made for this device but I had the most success with https://forum.xda-developers.com/nokia-3/development/twrp-teamwin-recovery-nokia-3-t3762512 .
Flash your TWRP Image chosen with
Code:
fastboot flash recovery your-recovery-image.img
and then reboot to recovery.
In TWRP go to Wipe and then Format Data and type yes.
Install Magisk
Install Magisk normally.
< waiting for device >
I put the phone in fastboot mode and ran fastboot with the oem key md5 hash command but it just said "< waiting for device >". I think it might be because I forgot to install the Nokia 3 USB drivers. I'm using a linux computer, do I need to find OS specific drivers?
edit: And now my phone is stuck in fastboot mode and for some reason will not shutdown no matter how long I hold down the power button for.
Totalitor said:
I put the phone in fastboot mode and ran fastboot with the oem key md5 hash command but it just said "< waiting for device >". I think it might be because I forgot to install the Nokia 3 USB drivers. I'm using a linux computer, do I need to find OS specific drivers?
edit: And now my phone is stuck in fastboot mode and for some reason will not shutdown no matter how long I hold down the power button for.
Click to expand...
Click to collapse
If you're using a linux computer, you should try running the command with sudo.
If it doesn't work, try with another cable (or computer if it doesn't work) and try again.
#AC said:
If you're using a linux computer, you should try running the command with sudo.
If it doesn't work, try with another cable (or computer if it doesn't work) and try again.
Click to expand...
Click to collapse
Thanks. I've since got it working. For some reason I had to use the -i argument (the interface argument) along with the code for the device (0x2e04) "fastboot -i 0x2e04 <command>".
However, I've recently bypassed the "NO COMMAND" screen and gained access to TWRP custom recovery but in trying to shut down the phone, it shuts down fine but only boots up in fastboot mode. Even using the fastboot reboot command from adb tools boots it up in fastboot mode. This is a problem as I need to boot it in its normal mode so I can download the magisk.zip file required for installing magisk but I seem to be unable to do so.
Totalitor said:
Thanks. I've since got it working. For some reason I had to use the -i argument (the interface argument) along with the code for the device (0x2e04) "fastboot -i 0x2e04 <command>".
However, I've recently bypassed the "NO COMMAND" screen and gained access to TWRP custom recovery but in trying to shut down the phone, it shuts down fine but only boots up in fastboot mode. Even using the fastboot reboot command from adb tools boots it up in fastboot mode. This is a problem as I need to boot it in its normal mode so I can download the magisk.zip file required for installing magisk but I seem to be unable to do so.
Click to expand...
Click to collapse
Try holding volume up and down at the same time while holding the power button.
#AC said:
Try holding volume up and down at the same time while holding the power button.
Click to expand...
Click to collapse
Thanks, it worked.
Though I tried wiping, but it didn't solve the booting issue. Unsure how to proceed at this point. I feel like I've tried everything. Actually, I just checked my /boot folder and it's empty...is that why it's always booting into fastboot?
I tried using adb to sideload the magisk.zip file but then the phone rebooted into stock recovery??
Any and all guides on this say to download the magisk.apk either into the SD card or internal storage, but I don't have a micro SD card and I can't access the normal mode of the phone to download anything.
What can I do?
I've flashed TWRP successfully but forgot to download the magisk.apk. Now whenever I boot up my phone, it boots into stock recovery mode automatically, even if I tell TWRP to reboot into system it reboots into Stock Android recovery. I can still access TWRP by holding down the up + power buttons on boot though, but I can't access the normal mode of the phone anymore.
I tried using TWRP's sideload feature with ADB tools to sideload Magisk.zip and it said it succeeded but in using TWRP's install feature to find the zip file, it wasn't in /sideload/ or /storage/ as both were empty.
How can I temporarily restore normal functionality so I can simply download the Magisk manager.apk?