Related
*Unlocking bootloader will remove all your data!*
I'm using Windows 7, and that's the steps i did. (it should be simmilar for other systems too)
Getting code:
Code will look simmilar to this: DB1ED223C5537BA756FB0671E425D650
Method 1 (no root):
Go to
https://passwordsgenerator.net/md5-hash-generator/ copy paste serial number and click generate. Then you should see code in "MD5 Hash of your string". You can also go to simmilar md5 hash generator sites, but this site automatically converts small letters to big letters.
Method 2 (root):
Okay, this is new method that is much easier and you don't need to send IMEI and wait for @the_laser to give you code. Go to terminal emulator, type su and execute it. Then type this and execute it:
redweaver said:
Actually the command is
echo -n NE1GAM4770133666 |md5sum |tr [:lower:] [:upper:]
If you don't use the -n flag, the newline character is also passed and you get a different result
Click to expand...
Click to collapse
Unlocking bootloader:
Download platform-tools which activates adb and fastboot commands (first you need Nokia 3 driver installed if you didn't)
Nokia 3 driver: http://www.devfiles.co/download/3iK0k7Sv/Nokia_3_USB_Drivers.zip
platform-tools Windows: http://www.devfiles.co/download/KtLsN6fX/platform-tools-latest-windows.zip
platform-tools Mac: http://www.devfiles.co/download/OkrfluP0/platform-tools-latest-darwin.zip
platform-tools Linux: http://www.devfiles.co/download/vk5DudZX/platform-tools-latest-linux.zip
Enable usb debugging in Developer options before running adb. To get Developer options, go to settings, about phone and press build number 7 times. Also enable OEM unlock.
Now Connect phone to computer via usb and enable usb file transfer, run cmd as administrator, then type this command which runs adb:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
then type this command to check is your device connected to adb, it will show serial number of your device, if it hangs at waiting device, then you need to reinstall drivers (if you're doing this first time, then it will ask to allow usb debugging on your computer, just tick always allow from this computer and click OK)
adb devices
then type this command to reboot to recovery (you can boot to recovery by holding power on + volume up (only with usb connected) if this command doesn't works)
adb reboot recovery
when booted to recovery, choose reboot to bootloader option with volume sliders (this will boot to fastboot)
when booted to fastboot, it will show text 'FASTBOOT MODE' in down-left corner
now type this command to check is your device connected properly to fastboot.
fastboot devices
if it show characters like 0123456789ABCDEF or simmilar then it is connected properly, if it hangs on waiting device, then you need to reinstall drivers like mentioned above.
Android Nougat (7.0 & 7.1.1):
Now type these commands to unlock bootloader
fastboot.exe -i 0x2e04 oem key (type your key after oem key)
fastboot.exe -i 0x2e04 oem unlock
then press volume up, when asked
Android Oreo (8.0 & 8.1):
First download NE1-0-215H.lk.bin:
https://my.pcloud.com/publink/show?code=XZaLMs7ZclQ2wvKwSb0ofUraMmrsiHh6uk1X
Now type these commands to unlock bootloader
fastboot oem dm-verity <your_unlock_key>
fastboot flash lk NE1-0-215H.lk.bin
fastboot reboot-bootloader
Proceed your unlock procedure.
If you have problem on flashing the lk partition, you can use MTK Smart Phone Flash Tool to flash lk partition manually.
After lk partition flashed, you may encounter "Red State" when booting the phone. Ignore that and boot your phone to Fastboot mode directly with OST LA.
That is it, i tried to explain for you to understand everything i did to unlock bootloader.
Credits:
@the_laser for codes, some additional steps and corrections. Also thanks for new method. @redweaver for new method.
@Hikari_kalyx for Android Oreo method. @bigrammy for NE1-0-215H.lk.bin link.
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
the_laser said:
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
Click to expand...
Click to collapse
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
DON'T install xposed! It bootlops.
EDIT: My fault, it actually work but you need to wait more than usual to boot.
That is great guys.
Do we have a working recovery yet?
nafnist said:
That is great guys.
Do we have a working recovery yet?
Click to expand...
Click to collapse
I use this twrp https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
I have stock recovery, but I use fastboot command 'fastboot boot recoveryname.img' when I need TWRP, and that's awesome because I don't lose stock recovery which is useful to flash OTAs and Nokia zips. I flashed SuperSu 2.79 just fine, but expect some crashes like software update, device monitor crash, but actually everything works, software update works just fine.
SkaboXD said:
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
Click to expand...
Click to collapse
TWRP can't handle Android 7.x default disk encryption, just press "cancel" and we need to use sdcard as storage for backups and packages because of this
Can I return the bootstrapper lock?
Where are you getting the codes from @the_laser?
abetterlie said:
Where are you getting the codes from @the_laser?
Click to expand...
Click to collapse
Yes
shokohiw said:
Yes
Click to expand...
Click to collapse
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
I mean where are you getting the OEM unlock keys from?
SkaboXD said:
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
Click to expand...
Click to collapse
abetterlie said:
I mean where are you getting the OEM unlock keys from?
Click to expand...
Click to collapse
idk, ask @the_laser
the bootloader I unlocked how to install root and twrp
shokohiw said:
the bootloader I unlocked how to install root and twrp
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
reboot to fastboot, then type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
Thank you!
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
shokohiw said:
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
Click to expand...
Click to collapse
on twrp, there is a option wipe, click on it, then you will see option swipe to factory reset. then wait and reboot.
And you can now enable system modification if you want (it is recommended to enable it because some zips fails to flash because this option is disabled)
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
shokohiw said:
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
Click to expand...
Click to collapse
Weird, when it says your device has failed verification?
For me reboot works fine
I've tried to flash MIUI9 over LineageOS 14 with full formating.
After flashing I'm stuck at boot logo MI. Even if I try to boot into recovery.
Fastboot works, but I'm unable to change anything
Code:
$ fastboot boot recovery.img
> FAILED (remote: unlock device to use this command)
$ fastboot oem unlock
> FAILED (remote: Token verification failed, reboot the device)
The thing is, I remember unlocking bootloader when flashing original ROM with LOS. How is it locked again?
How to get out of this situation? I don't care about any data on the phone.
Thank you.
xda-lukasik said:
How to get out of this situation? I don't care about any data on the phone.
Thank you.
Click to expand...
Click to collapse
In this situation only EDL-mode flashing is possible, but no worries, you can unlock it and get MIUI again at the same time...
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
xda-lukasik said:
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
Click to expand...
Click to collapse
You aren't reading the guide correctly, but for a Linux user I will clarify a few things.
- look, in the guide "Command: fastboot oem edl (this brings your device in a kind of emergency recovery state) -> the device does only show a black screen" - it means fastboot and "fastboot devices" do not exist anymore and your device enters QUALCOMM HS-USB QDLOADER 9008 mode
- run lsusb on Linux in fastboot and then in EDL/9008 mode - the IDs will be different and there is no Linux driver for 9008
- the Linux tool you mentioned is just a script to automate some trivial tasks which can be done manually in fastboot mode. I checked the source code and note "sudo apt-get install android-tools-fastboot", it pulls the fastboot app from a repo and works on it. The tool is completely useless for this job.
- your only option is MiFlash which runs on Windows
- you can get Windows 10 evaluation ISO from Microsoft and get rid of it later
- you can get Windows running in a much easier way but we are forbidden to talk about it on this forum
:good:
Good luck!
Tried and failed.
After oem edl there is no device listed in miflash and "flash" does nothing.
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
cybercruizer said:
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
Click to expand...
Click to collapse
I'm unable to flash anything
Ugh, when you enter edl mode it becomes different device in virtual box and you need to add it again.
But I tried it several times with real windows machine and it didnt show up either (??)
It still didnt worked, I got errors such as:
Failed to hello message
Ping failed
Solution was to use older MiFlash tool (2015).
Thanks all for your help.
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.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.
Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.
Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk
It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse
domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock
In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it
Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.
Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.
Hi everyone. I am trying to unbrick my Xperia XZ. I tried a lot during these 3 days. Guess I need help.
Here's what happened and actions I took. I can upload screenshots, but I am very exhausted now, and considering you have more knowledge about this topic than me, I don't upload screenshots.
Phone's charge went 0%. I tried to charge it via wallcharger. But stuck on Sony Logo.
Tried ADB Fastboot, flashtool, Xperia Companion, Emma to flash it with stock rom.
Emma says this phone is locked.
Xperia Companion gives error at approx 25%.
Fastboot commands doesn't work. Cannot unlock bootloader via fastboot. remote: 'Command not allowed'. (I can only manage to run fastboot devices command. Cannot even install twrp).
flashtool
Tried unlocking bootloader via BLU, it stucks at Unlock code saved to C:\......
Flashmode
I tried flash 3 different roms, always stuck at Closing TA Partition after Opening Ta Partition 2. Not even 5% of process.
Fastboot Toolbox
Select Kernel to HotBoot - Only way I got screen besides Sony logo. And it says Your device has failed verification and will not work properly.
Select system to Flash - When I choose boot.img or kernel.sin it says remote: 'Command not allowed' as in fastboot.
Select Kernel to Flash - 'Command not allowed'
The only thing comes to my mind is enabling OEM unlocking and debugging mode. But since I cannot boot my device up, I cannot do these either.
I tried execute fastboot oem unlock via adb fastboot cmd, again I got Command not Allowed.
Thanks for attention.
ADB and Fastboot are two complety different softwares: ADB deals with Android OS, whereas Fastboot deals with device's bootloader.
Do you use USB drivers provided / supported by Sony?
Drivers - Sony Developer World
developer.sony.com
xXx yYy said:
ADB and Fastboot are two complety different softwares: ADB deals with Android OS, whereas Fastboot deals with device's bootloader.
Do you use USB drivers provided / supported by Sony?
Drivers - Sony Developer World
developer.sony.com
Click to expand...
Click to collapse
I meant I tried cmd thing in the folder called Minimal_adb_fastboot
And yes, I have tried lots of different drivers, either sony or adb drivers. Computer sees the device. And by the way, I have tried on different computers and with different cables, nothing changed.
The drivers you have stored in PC's folder "Minimal..." are to be used only with Google phones.
xXx yYy said:
The drivers you have stored in PC's folder "Minimal..." are to be used only with Google phones.
Click to expand...
Click to collapse
Sir
I said that I have tried many drivers. And currently I have installed Sony official driver for my phone .
Use command
Code:
fastboot flashing unlock
instead of
Code:
fastboot oem unlock
May be it will work
xXx yYy said:
Use command
Code:
fastboot flashing unlock
instead of
Code:
fastboot oem unlock
May be it will work
Click to expand...
Click to collapse
Sir how many times I should say, I have tried almost all commands including this one, it doesn't work, only says, Command not Allowed