Why to use the Fastboot Enhance is required to unlock the Bootloader and not to use the OPLocalupdate?
You can't unlock the bootloader using OPlocalupdate. It's used to install OS upgrades both full and incremental releases.
Fastboot is the android tool from Google that is used to flash the phones partitions if there's an issue the phone doesn't boot. It also is the tool used to flash custom boot images for rooting or full custom roms.
"Fastboot enhanced" just slaps a gui over the Google tool so it's easier to use.
Related
To start: 5.1.1 (LMY48M), rooted, with TWRP for recovery
For every 5.x update so far, this has been my procedure using fastboot:
Flash boot.img
Flash radio.img
Flash system.img
After successfully updated, I'd use WugFresh's Nexus toolkit to root and flash TWRP.
I'm a fan of not needing to flash userdata.img, as I don't think that should be necessary given that the OTA wouldn't wipe installed apps and such.
I've read other threads about using fastboot to upgrade and am concerned about the boot warnings, which seem to require a custom kernel to circumvent. My question is: will the above approach still work? Do I need to flash any other files? If I need to flash a custom kernel, where do I get it, how do I flash it (is it just a custom boot.img?), and at which point in the flash sequence should I apply it?
Secondly, has anyone tried gaining root through the Nexus toolkit once upgraded to 6.0?
I'm looking for recommendations so I don't spend hours trying to unbrick my device. Thanks!
You'll also want to flash the 6.0 bootloader and why are you using the toolkit to flash twrp when you can flash it in fastboot along with the rest of the files?
Ah OK, I'll flash the bootloader image as well. Anything else to be concerned with? The toolkit has a feature to root + flash twrp as a feature, so I just use that.
Do the bootloader first, then reboot the bootloader before you flash anything else. There are instructions floating around here some where or you can google nexus 6 flash factory images. You don't have to flash user data as this will format all you data/ apps.
Just download the latest SuperSu zip (2.50) and put it on your SDcard. If you flash as you suggested and then boot directly into recovery, you will still have TWRP. If you don't flash the stock recovery.img to replace TWRP, it will replace on first boot anyway, unless you root imeediately, but you are probably booting to use the toolkit, which replaces recovery only to have to use the toolkit to flash recovery anwyay.
So do your flashes, boot straight into recovery, flash the supersu zip on your sdcard. Done.
Just took delivery and trying to root. Using nexus root kit successful at unlocking. But will not unencrypt or root. Being denied copying files from PC to device Also can not flash/recover to any other boot img. Is there anyway to revert back to an unencrypted image? Stock build came as LMY47D but it updated to the 5.1.1 yesterday. Also is there any known issues using windows 10 to run the toolkit?
Have you tried just doing everything the proper way following our guides?
i.e using fastboot to flash stock images, and TWRP recovery. Then use recovery to flash a kernel that doesn't force encryption. Then format userdata from recovery.
It's very easy
yeah, I hate to be that guy, but you really should avoid the toolkit and learn some very basic fastboot and adb commands.
Once you have these at your disposal, you can pretty much unbork anything on a nexus.
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
mirunaa said:
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
Click to expand...
Click to collapse
You don't need to lock bootloader to get OTA updates. Keep it unlocked if you want to get back to stock android.
First uninstall all the Magisk modules you've downloaded. Then flash stock boot.img and system.img (If you've edited build.prop without adb shell). After this you'll be on stock android and you'll get OTA updates.
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
mirunacont said:
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
Click to expand...
Click to collapse
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
[email protected] said:
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
Click to expand...
Click to collapse
Download this - https://android.googleapis.com/pack.../f9b27203a7d6dd2c6709f238d9953c6d4e18c04b.zip
Then extract the files and then find the boot.img and system.img. Flash the images from fastboot using -
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Extract the Images & Flash Them Individually
you have to flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders. From here, there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
fastboot flash boot <boot image file name>.img
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot.
At this point, your device should be fully updated, or if you were trying to recover from a soft brick, it should be running flawlessly.
Hello everyone
Please i'm in France and would like to upgrade to Pie
When i try nby updater no update appear
i'm on 8.1 with Nov Sec Patch
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Slymi4n said:
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Click to expand...
Click to collapse
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
zgfg said:
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
Click to expand...
Click to collapse
YES!! IT WORKED!!! Thank you so much
Hello everyone, this guide will be as simple as possible, taking into account that they deal with almost all the same things as to unlock the bootloader
First of all from flashtool flash the stock version number 76 (the one used to unlock the bootloader)
Turn on the device in fastboot mode, and use this command "fastboot flashing lock or fastboot flashing lock_critical" to then proceed to turn off the device
Then from lolinet download the latest stock version for your region and your device version either arm or arm64, once downloaded flash from flashtool, they must do this after blocking the bootloader because the last stock does not allow said unlocking
After doing all this, you should already have the bootloader locked with its latest corresponding stock version, I must remind you that basically the same thing is used as when unlocking the device.