Related
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 at https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4) Type
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-nakasi-jwr66v.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.3 and ready to send in your tablet for warranty purposes if you so desire.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
Also, thank you to XDA user Shano56 for the formatting help on this post.
chris.wueste said:
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
1) Make sure you have your ADB and Fastboot drivers installed and working.
2) Download the factory image for the Nexus 7 here
3) Unzip the factory image into the same directory as your Adb and Fastboot drivers.
4) Plug in your device. With the device on the home screen, type "ADB reboot bootloader" or if your device is off, press and hold both volume keys and press the power button. After holding all three buttons for a couple of seconds, your bootloader should launch.
5) This should reboot you into the bootloader. Now type "fastboot flash bootloader bootloader-grouper-3.34.img"
6) Next type "fastboot reboot-bootloader"
7) Now type "fastboot -w update image-nakasi-jrn84d.zip"
8) Optional: If you would like to relock your bootloader for warranty purposes, make sure you are in your bootloader screen again and type "fastboot oem lock"
9) I don't remember if the tablet automatically reboots at this point but if it doesn't just type "fastboot reboot"
That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
Click to expand...
Click to collapse
You should change the title to [Guide] How to return to Stock / Unbrick your Nexus 7
Helps out those getting bootloops or softbricks from geting root access in certain ways or messing with the build.prop
SladeNoctis said:
You should change the title to [Guide] How to return to Stock / Unbrick your Nexus 7
Helps out those getting bootloops or softbricks from geting root access in certain ways or messing with the build.prop
Click to expand...
Click to collapse
Not a bad idea. Done and done. Also, I have proofread it several times over to ensure it is correct but would you mind making sure that all of the commands were typed correctly. My eyes are going crosseyed over here.
Nice guide man, I changed the format a little to make it easier to read. Use it if you want, won't be offended if you don't.
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 here
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4) Type
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-nakasi-jrn84d.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes if you so desire.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
If you want to use it and are too lazy to quote my post - http://pastie.org/pastes/4279753/text
The commands look good to me however I've never used "fastboot -w update" so can't say for that
Shano56 said:
Nice guide man, I changed the format a little to make it easier to read. Use it if you want, won't be offended if you don't.
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 here
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4) Type
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-nakasi-jrn84d.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes if you so desire.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
If you want to use it and are too lazy to quote my post - http://pastie.org/pastes/4279753/text
The commands look good to me however I've never used "fastboot -w update" so can't say for that
Click to expand...
Click to collapse
I updated the OP with your edits in it. Thanks for the help. I quoted you at the bottom
omg thank you so much. u saved my device
jarjar124 said:
omg thank you so much. u saved my device
Click to expand...
Click to collapse
Very welcome
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
chrisjm00 said:
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
Click to expand...
Click to collapse
In some cases due to the CWM not being official it cause bootloops by going to recovery in the bootloader.
SladeNoctis said:
In some cases due to the CWM not being official it cause bootloops by going to recovery in the bootloader.
Click to expand...
Click to collapse
There's a CWM official out?
Sent from my Nexus 7 using Tapatalk 2
chrisjm00 said:
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
Click to expand...
Click to collapse
Assuming you have already flashed CWM, then the command would actually be fastboot reboot recovery. Not sure what but you speak of.
Shano56 said:
There's a CWM official out?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes. There sure is. If you have Rom Manager installed it can be flashed directly from there.
I dont think you can really hard brick this device anyways
I'm sitting here at the command prompt with it on "erasing userdata"
It's been a couple minutes and I'm freakin' out! How long is it supposed to take? Everything flashed correctly, if I start the device now will there be an issue?
EDIT: Nevermind, just rebooted from the bootloader in the tablet and it booted fine. I'll get the OTA to 4.1.1 and that should probably fix any outstanding little issues.
hard brick?
I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.
I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?
chris.wueste said:
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
Click to expand...
Click to collapse
Pressing and holding the Volume down + Power buttons works just fine to launch the bootloader (at least for me).
No need to press (and force) the entire volume rocker button at all.
nugalonious said:
I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.
I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?
Click to expand...
Click to collapse
Try and press and hold just the power button for 30 seconds or so to re-boot the tablet and you should be fine and it should boot up just fine. From fastboot you cannot go into cwm recovery because of a bug.
I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:
FAILED (remote: (FileWriteFailed))
Anyone seen that before or have any ideas to fix?
I tried wiping cache/factory reset from CMW but no joy.
Thanks. Worked for me. I did get worried when i got (data transfer failure (too many links)) error when trying to flash the bootloader.
Turns out it was the USB port. I switched the ports and all was well.
But I followed the commands in side the flash-all.sh file
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jrn84d.zip
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
yeahthatsme said:
I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:
FAILED (remote: (FileWriteFailed))
Anyone seen that before or have any ideas to fix?
I tried wiping cache/factory reset from CMW but no joy.
Click to expand...
Click to collapse
Try the commands i posted above and see what happens
Nuts. I tried it on many USB ports and did your commands one by one. Ended up in the same spot. It happens when writing 'userdata'...
I broke my xperia l lcd last year. Digitizer was partly working. Developer option was not enabled.
Recently I found this thead and started playing:-
1. No display, so could not use a graphical recovery to flash a rom (with debug opt enabled).
2. Flashed Kitkat Omni rom (it has system.img, boot.img...) using fastboot.
3. Now I can use [email protected] and other similar tools to use the phone somewhat.
My problems / queries:-
1. Main problem I do not have app level root access, tried various methods but failed.
2. Cannot flash recovery image (using fastboot / flash_image) to use philz / cwm.. It says remote command not allowed / write not permitted. When I flashed the philz recovery as boot the omni rom does not start. Any other options?
3. Can some one let me know how to create a shortcut for system menu app 'Cast Screen' (with predefined display device) in desktop / or put it in autostart.
I leaned a lot due to this broken phone. Thanks xda, Omni Rom & [email protected] developers. k.janku1 , many others and of-course Sony mobile.
AD.
At last I found a solution for rooting
I have philz touch in my other phone. I noticed it was very easy to use blindly as it has touch feedback.
So I got the root problem solved by following steps:-
Enter fastboot mode [switch off phone - press vol up + usb cable insert -> blue light will turn on]
fastboot -w
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot philz_touch.img [temporarily, as omni will not boot with philz_cwm]
fastboot reboot
while starting pink light is on press vol down to enter recovery mode [philz touch]
Touch buttons below
down = up = back = enter
press back several times to reset the cursor at top
down once (intsall from zip) -> press power button
down 4 times (as it has internal sd and ext sd, install from side laod) -> press power button
adb sideload Update_SuperSU.zip
wait
adb reboot bootloader [fastboot mode ]
fastboot flash boot boot.img [omni's original boot.img]
fastboot reboot
Now as I got the root power every other problem will be solved very soon.
Hope this will help someone someday.
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, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
No need double reboot
Os_Herdz said:
No need double reboot
Click to expand...
Click to collapse
It is not necessary, but a preventative measure. I've had instances where I hadn't rebooted twice and the phone booted into erase mode. This is a guide for people who want to make sure they won't lose data.
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
RFD80M-75679 said:
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
Click to expand...
Click to collapse
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
softgadget said:
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
Click to expand...
Click to collapse
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
RFD80M-75679 said:
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
Click to expand...
Click to collapse
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
softgadget said:
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
Click to expand...
Click to collapse
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
RFD80M-75679 said:
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
Click to expand...
Click to collapse
Oh. OK then.thank you
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
popadic022 said:
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
Click to expand...
Click to collapse
You can unlock with the same method. But I believe you will flash a zip from TWRP to fix SIM cards and that will break your phone if you lock the bootloader. So after fixing the SIM cards, you need to leave the phone unlocked, otherwise phone will be bricked. If you want to get rid of the ugly splash screen, you can flash a custom splash you can find in the forum.
marstonpear said:
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
Click to expand...
Click to collapse
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
gusbalaa said:
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
Click to expand...
Click to collapse
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
RFD80M-75679 said:
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
Click to expand...
Click to collapse
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
gusbalaa said:
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
Click to expand...
Click to collapse
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
marstonpear said:
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
Click to expand...
Click to collapse
Thanks, already done it.
Flashed TWRP & Magisk without losing any data.
marstonpear said:
Hi,
Click to expand...
Click to collapse
will this metode also work on mi10
-fluffy- said:
will this metode also work on mi10
Click to expand...
Click to collapse
I'm not sure but probably not. Because Mi 10 is a MIUI device and this is an Android One. Still you gotta try to make sure, but the risk is all yours. Cheers.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
Wowwww! Thank you very much, time ago I've unlocked the bootloader without losing any data
That's a very good solution