Related
Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!
Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.
Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.
If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard
Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.
Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.
Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else
Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.
Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.
dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.
This is a step-by-step guide that will get you to a fully working lineageos on your sony xa2 ultra, starting from a device that was just purchased.
I used Linux, but everything should be more than doable on Windows as well.
Make sure you have:
A copy of platform-tools from google (ubuntu's version works to some extent, i had to use binaries from both). You need:
fastboot
adb
The TWRP image for XA2 ultra: twrp-3.2.3-0-discovery.img
A working copy of xperifirm. If you're on Linux set a light UI theme, or it won't work. Also
Code:
export TERM=xterm
before launching it.
A working copy of newflasher. You can build it on linux by typing
Code:
make newflasher.x64
newflasher.x64 will be the name of the binary.
A fresh lineageos build for your phone (from now on referred to as lineage.zip)
A build of gapps, if you want them
The first thing you have to do is to
Unlock your bootloader
Preliminary operations:
Start your phone
Connect to the internet (3g or wifi)
Go to Settings > System > Device info, tap "Build number" until developer mode is active
Go back, open developer options
Tick USB Debugging and OEM Unlock
Open the phone dialer and type
Code:
*#*#7378423#*#*
this will open the service menu. It could take a few seconds.
Go to Service info
Enter 'Model info', write down the string (e.g. H4213) somewhere
Go back and enter 'Configuration'.
Check that "Bootloader unlockable" is 'yes', if it's not you can't proceed.
Write down the IMEI code. If it's a dual sim, you need to write down the "Sub1" one.
Go here, select the device and paste the IMEI that you wrote down
Write down the unlock code
Put phone in fastboot mode and unlock the bootloader:
Shut down the phone completely, unplug the USB cable if plugged
Hold VolumeUp, plug USB cable
Phone should power on, press Power if it doesn't
Wait until you have a fixed blue light on the led
You are now in fastboot mode
Code:
fastboot oem unlock xxxxx
where xxxxx is the unlock code that you obtained from the previous step
Flash an updated firmware
First you need to obtain the latest firmware for your device:
Run xperifirm
Open Sony XA2 discovery
Select whatever you wrote down from the 'Model info' section of the service menu
Download whatever firmware has the highest build number
If you're on Linux xperifirm will fail to unpack the firmware. You can work around it by entering the firmware directory on a shell and running:
Code:
for i in FILE_* ; do unzip $i ; done
unzip boot.zip -d boot
Remove a bunch of files, you can copy/paste this string after 'rm' or delete them manually:
Code:
kernel_X-FLASH-ALL-18AE_0x00.hash kernel_X-FLASH-ALL-18AE.sin persist_X-FLASH-ALL-18AE_0x00.hash persist_X-FLASH-ALL-18AE.sin system_other_X-FLASH-ALL-18AE_0x00.hash system_other_X-FLASH-ALL-18AE.sin system_other_X-FLASH-ALL-9B8D_0x00.hash system_X-FLASH-ALL-18AE_0x00.hash system_X-FLASH-ALL-18AE.sin system_X-FLASH-ALL-9B8D_0x00.hash userdata_X-FLASH-CUST-18AE.sin vendor_X-FLASH-ALL-18AE_0x00.hash vendor_X-FLASH-ALL-18AE.sin vendor_X-FLASH-ALL-9B8D_0x00.hash
Put your phone in flashing mode.
Shut down the phone completely, unplug the USB cable if plugged
Hold VolumeDown, plug USB cable
Phone should power on, press Power if it doesn't
Wait until you have a fixed green light on the led
You are now in flashing mode
Run
Code:
newflasher
(or newflasher.x64 if you built it yourself) from the directory where you have the remaining firmware files. It could ask you whether to dump the TA section, feel free to answer 'n'.
Go back in fastboot mode, and run:
Code:
fastboot set_active other
Then rerun the last list (go to flashing mode, run newflasher).
If 'other' doesn't work, run "fastboot getvar current-slot" in fastboot mode and then use either 'a' or 'b' instead of 'other' - whatever is not the one returned by getvar.
Flash lineage
Boot into TWRP:
Put your phone in fastboot mode (see above)
Code:
fastboot boot twrp-3.2.3-0-discovery.img
You are now in TWRP
When I first tried this my phone kept power cycling. If this happens to you too, here is how to fix it:
Hold VolUp and let it power cycle until it goes into fastboot mode again (fixed blue led)
Code:
fastboot -w
Try booting into TWRP again
Flash lineage:
On TWRP go to advanced, enable sideload
On your computer run:
Code:
adb sideload lineage.zip
It should start flashing by itself, if it doesn't, make it.
If you want to also flash gapps, repeat steps from 'Boot into TWRP' and flash the gapps zip file.
Reboot your phone into fastboot one last time, and run
Code:
fastboot -w
.
Reboot with
Code:
fastboot reboot
.
Congratulations, you're now running lineage!
Thanks @xstasi for the write up. However, I have a question.
After flashing the firmware with newflasher the first time, I then went to download mode, found I was on "b" so I set it to the "a" slot. But after powering down, now my phone will not do anything. I can't get back into the flash mode, or fastboot mode. No matter what I press, when I plug in the USB cord, the light blinks green several times but never goes solid. Any advice on how to fix this?
So im lost here on how to start this process on win10. Play by play, where did you enter codes.
N00b question:
The automatically generated lineageos installation instructions recommend backing up the "trim area partition" as it contains "the" DRM keys:
https://wiki.lineageos.org/devices/discovery/install#unlocking-the-bootloader
There seems to be a tool on XDA for this: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Why do I need to bother with that? What would I need the DRM keys for? Does it make a difference when running lineage? Or reverting back to stock?
BR
voidling42 said:
N00b question:
The automatically generated lineageos installation instructions recommend backing up the "trim area partition" as it contains "the" DRM keys:
https://wiki.lineageos.org/devices/discovery/install#unlocking-the-bootloader
There seems to be a tool on XDA for this: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Why do I need to bother with that? What would I need the DRM keys for? Does it make a difference when running lineage? Or reverting back to stock?
BR
Click to expand...
Click to collapse
You backup the TA Partition once you've booted into TWRP. Theres a section where you can backup the TA Partition through there... Unfortunately it isn't mentioned here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:20 AM ----------
Hmmm, I would have recommended the 'Minimal Adb and Fastboot' instead of the 'platform-tools' from Google. Less bloaty, quicker installation and same instructions as above. All thats needed is the twrp.img in the same folder where the 'Minimal Adb and Fastboot' is installed and voila!
You never mentioned the Add On SU, to add rooting capability into Lineage itself rather than third party apps, activated from the developer options once flashed.
I know GApps are a rather personal preference from person to person. But I'd personally recommend installing the Aroma package from Open GApps. Whilst it is essentially the Super package (Where it has all the Google Apps), Aroma unlike Super has a GUI where you can select what Google Apps you do and don't want installed from it. So you can add as much or as little as you need to. further on, It also has extra really useful features; before installing you can tell if you want Aroma to replace the Lineage apps with the Google versions (Such as Gallery, Camera, Contacts and Messaging... etc), because normally it will just overwrite them anyway. Finally, the most useful feature before installing GApps, is that you get the option to uninstall Lineage features. There's only 3 options (LineageOS Recorder, LineageOS Setup Wizard and LineageOS Updater), the rest dont really apply to Lineage. At the very least I'd recommend uninstalling the LineageOS Setup Wizard (But I usually uninstall all 3). I say that because Aroma also installs a Google setup wizard, thats much more useful than the Lineage one, particularly if you're updating Lineage and have previously made a backup with Google and want to quickly reinstall all your apps and settings, rather than reinstalling them one by one.
Hello guys,
I found some differences with other Newflash guides:
- you do not delete *.ta files in main folder and in boot folder;
- you delete kernel_* files instead of boot_* files in main folder;
I can't tell if those different steps make any difference, anyway.
You should mention that DRM keys are lost with bootloader unlock and that TA partition should be backup up via TWRP before flashing lineage.
I'm very excited about the hardware on this phone. While I might be late to this game, can anyone tell me if Volte is working properly in US? Losing 3G is a few months is forcing me to find a new phone.
------------------------------------------
Latest update to guide: Jul. 5, 2020
------------------------------------------
Hi everyone!
Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides and threads expecting a working knowledge of Android devices. Many may say that if you don't know what you are getting into, don't do it, but this warning is not followed by many people. Instead of having to deal with the pleas for help from lost users with soft bricked phones, I decided we need a 'megathread' with accurate, easy to follow instructions with correct grammar and concise descriptions.
This thread is constantly updated. Please inform me with a reply or PM if you want anything modified
Sections:
Unlock the bootloader (required for most other modifications)
Install the TWRP custom recovery
Install Magisk for superuser/root
Install an OTA update while rooted
Section 1: Unlocking the bootloader (Windows Only)
If your device is a T-Mobile version, you must first request an unlock token from this website to complete this section. Your device may also need to be SIM unlocked. Check your carrier website for details. Using the cable included in the box is also recommended.
Step 1: With your phone turned on, open Settings. Scroll down to the bottom and select About phone. Touch Build number quickly until a toast message (grey rectangle at the bottom of the screen) appears reading You are now a developer!. Go back one screen to the main settings list and select System. Select Developer options. Turn on the switch next to OEM unlocking. Scroll down a small bit and turn on the switch beside Advanced reboot. Scroll down a bit more and turn on the switch beside USB debugging. Go back to the home screen.
Step 2: Plug your phone into your computer with the cable supplied in the box. On your phone, look in the notifications for a message that says: "Android System Charging this device via USB." Touch the notification once to expand it and again to open it. Choose File transfer from the list. Download and extract this zip file by right clicking it, clicking Extract All, then Extract. (File Credit: Google) This file contains the official ADB and Fastboot binaries. Open File Explorer and navigate to This PC. Under Devices and drives, click on the CD drive labelled with a bunch of numbers. Click on OnePlus_USB_Drivers_Setup and click yes in the User Account Control popup. Click Ok then Install, then Finish. Navigate back to the extracted ADB and fastboot files (the folder will likely be named platform-tools). With this folder open, hold shift and right click on the blank space. Click Open command window here or Open PowerShell window here. Unlock/wake up your phone. Type in the terminal window on your computer followed by the enter key
Code:
adb devices
A prompt should appear on your phone. Click Ok. Type followed by the enter key
Code:
adb reboot bootloader
Your phone screen should show the OnePlus logo as well as the words FastBoot Mode briefly. Type followed by the enter key
Code:
fastboot oem unlock
Warning: This next step will wipe your phone. On your phone, use the volume down key to select Unlock the bootloader and then the power key to select. Your phone will then be wiped and restart automatically.
Step 3: Follow the phone's initial setup exactly how you would if you were setting up a new phone. Restore any backup you have now. Once completely set up, follow the instructions from Step 1, ignoring the OEM unlocking switch. I also recommend typing this followed by enter
Code:
adb devices
A prompt should appear on your phone. Click Ok.
Your device is now Bootloader Unlocked.
Section 2: Installing TWRP (Windows Only)
Your bootloader must already be unlocked, and you must be on the latest version of OxygenOS. Using the cable included in the box is also recommended.
Step 1: With your phone turned on, hold the power button and until the reboot options menu appears on the right side. Click Bootloader. Plug your phone into your computer with the cable supplied in the box. Download these two files (File 1 for Android 10, File 1 for Android 9, File 2), which now work on both the OnePlus 7 Pro and OnePlus 7. (File Credit: @mauronofrio and Team Win Recovery Project). Put these files somewhere accessible, such as your Desktop.
Step 2: Open the folder with your ADB and Fastboot binaries (the folder will likely be named platform-tools). With this folder open, hold shift and right click on the blank space. Click Open command window here or Open PowerShell window here. Type in the terminal window
Code:
fastboot boot
followed by a space. Drag the image/img file you downloaded called twrp-3.3.1-79-guacamole-unified-Q-mauronofrio into your terminal window. The resulting command in your terminal window should read something like this
Code:
fastboot boot C:/Users/Arden/Desktop/twrp-3.3.1-79-guacamole-unified-Q-mauronofrio.img
If it does, click the enter key.
Step 3: On your phone, enter your PIN/Password/Pattern if requested. You should now see a screen with grey boxes. This is the TWRP recovery. Click Advanced, then ADB Sideload, then swipe the bar at the bottom to the right. On your computer, type
Code:
adb sideload
followed by a space. Drag the zip file you downloaded called twrp-3.3.1-79-guacamole-unified-installer-mauronofrio into your terminal window. The resulting command in your terminal window should read something like this
Code:
adb sideload C:/Users/Arden/Desktop/twrp-3.3.1-79-guacamole-unified-installer-mauronofrio.zip
If it does, click the enter key. On your phone, you will see some text scrolling in a black box. Once the button appears on the bottom right, click Reboot.
Your device now has the TWRP custom recovery.
Section 3: Installing Magisk
You must already have TWRP installed to complete this section.
Step 1: On your phone, download the Magisk installer zip (File Credit: topjohnwu). If you are not already in the TWRP recovery, hold the power button and until the reboot options menu appears on the right side. Click Recovery.
Step 2: Enter your PIN/Password/Pattern if requested. You should now see a screen with grey boxes. Choose Install and navigate to the folder you downloaded the Magisk file to. Select the Magisk file (likely named Magisk-20.4.zip) and swipe the bar at the bottom to the right. Once the button appears in the bottom right, click Reboot.
You now have Magisk root.
Section 4: Installing an OTA update while rooted
You must be rooted to complete this section.
Step 1: If you have any themes installed, such as Renovate ICE, Swift Themes, RoundyUI, or Substratum themes, remove them before continuing. Remove the Call Recording Enabler module if you have it. Restart if needed.
Step 2: Click on the system update notification. If it does not appear, open Settings, scroll to the bottom and click System, scroll to the bottom and click System updates. Click on the Install or Download and Install button and let it complete. Do NOT click Reboot.
Step 3: Open Magisk Manager and click the hamburger menu in the top left (3 horizontal lines). Click Downloads and then click the search icon (magnifying glass) in the top right corner. Type "TWRP" and click enter. Click the download arrow beside the module named TWRP A/B Retention Script. Do NOT click Reboot.
Step 4: Click the back button in the top left, followed by the hamburger menu in the top left as well (3 horizontal lines). Click Magisk and then click the top Install button, followed by Install again, then Install to Inactive Slot. You may now click Reboot.
You now have updated your phone's OxygenOS. Reinstall any modules or themes deleted in this process if they are compatible.
(reserved extra section)
Great idea, very thorough!
You forgot the very first step, which is to get sim unlocked. Without this OEM unlock will be greyed out
anoymonos said:
You forgot the very first step, which is to get sim unlocked. Without this OEM unlock will be greyed out
Click to expand...
Click to collapse
Oh, my bad. In my country it's illegal to sell locked phones
Arden144 said:
Section 1: Unlocking the bootloader (Windows Only)
<snip> Type followed by the enter key
Code:
fastboot flashing unlock
Warning: This next step will wipe your phone. On your phone, use the volume down key to select Unlock the bootloader and then the power key to select. Your phone will then be wiped and restart automatically.
Click to expand...
Click to collapse
I am curious about this step. For most all time with a phone that has an unlockable bootloader the command has always been:
Code:
fastboot [B]oem[/B] unlock
Why do we use 'flashing' instead of 'oem' in that command for this phone?
teddyearp said:
Section 1: Unlocking the bootloader (Windows Only)
<snip> Type followed by the enter key
I am curious about this step. For most all time with a phone that has an unlockable bootloader the command has always been:
Why do we use 'flashing' instead of 'oem' in that command for this phone?
Click to expand...
Click to collapse
Good question, actually. I'm not entirely sure why the wording change, but the command has been different on close to stock devices since the Nexus 6P/5X. If someone more knowledgeable could explain, that would be great
Arden144 said:
Code:
fastboot boot C:/Users/Arden/Desktop/twrp-3.3.1-3-guacamole.img
Click to expand...
Click to collapse
On earlier OOS versions, the command "fastboot boot" is broken, and this won't work. Process in that case is to flash a patched boot image, root with Magisk, and then flash TWRP like a Magisk module.
Your method works for those that have updated to more recent OOS versions. However, there are folks still out there with older OOS versions, where "fastboot boot" won't work (don't know the cutoff exactly).
redpoint73 said:
On earlier OOS versions, the command "fastboot boot" is broken, and this won't work. Process in that case is to flash a patched boot image, root with Magisk, and then flash TWRP like a Magisk module.
Your method works for those that have updated to more recent OOS versions. However, there are folks still out there with older OOS versions, where "fastboot boot" won't work (don't know the cutoff exactly).
Click to expand...
Click to collapse
Thanks for the info. I'm not going to add the patched image way, as extracting the boot.img is annoying and I'm trying to avoid methods that rely on someone else providing files. However, I'll add a note to the TWRP install section asking for 9.5.7 minimum as everyone should be on that update by now
I hope this gets stickied. Thank you for the guide
just an update, fastboot flashing unlock didnt work for me, but fastboot oem unlock did
Yayodroid said:
just an update, fastboot flashing unlock didnt work for me, but fastboot oem unlock did
Click to expand...
Click to collapse
For me also...the right command seems still fastboot oem unlock
Is this method applicable to all versions ? Im getting the GM1910: China version , I have used this method when i had my OP6 so i just have to get the correct TWRP version, if the IMG boots the TWRP i guess the zip will be good to go when flashing .
Cheers
Yayodroid said:
just an update, fastboot flashing unlock didnt work for me, but fastboot oem unlock did
Click to expand...
Click to collapse
I confirm this. Tried this tutorial but was stuck at flashing stage. A YouTube video provided further assistance. Fastboot oem unlock worked.
I think it's great you're supplying these basics. Wish I had it when I first rooted first Android device (htc Evo 4g on sprint). Kudos.
ph1dft said:
For me also...the right command seems still fastboot oem unlock
Click to expand...
Click to collapse
I'm skeptical that the command "fastboot flashing unlock" is applicable for this device. I think it may just be a carryover from some other device(s). The original poster responsed that it is applicable to "close to stock devices since the Nexus 6P/5X" but never explicitly stated whether it even worked for him on the 7 Pro.
Far as I can tell "fastboot oem unlock" is the correct and only command on this, and other previous OnePlus devices (and is also the command that worked for me).
Hi all,
Haven't seen a guide for this and thought I would write one for myself and others
DISCLAIMER* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
You will also lose any L3 Widevine DRM Certification, aka no more HD netflix. Please keep this in mind.
REQUIREMENTS:
SDK Platform-tools (Get it here)
Getting boot.img
Download Lenovo Rescue and Smart assistant.
Link: https://support.lenovo.com/au/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
You'll need a lenovo ID, Sign in or register an account
and once there go to "Rescue" > Tablet Rescue
Input your serial number > Make sure it finds the tablet > Click Start Rescue to download the firmware
The download is about 2.6GB
Navigate to
Code:
C:\ProgramData\RSA\Download\RomFiles\YT_J706F_S000049_211204_ROW
Which should have the firmware and boot.img
LET'S BEGIN!
Extract the SDK Platform tools folder to an easily accessible directory
UNLOCKING THE BOOTLOADERNOTE: THIS WILL ERASE ALL DATA FROM YOUR DEVICE SO MAKE SURE TO TAKE A BACKUP IF NECESSARY
Extract the SDK Platform tools folder to an easily accessible directory
Go to Settings > About Tablet > Tap build number 7 times. Go back to main page of Settings > System > Developer options and enable OEM unlocking and USB Debugging
Reboot the system to bootloader (Press Vol - and Power key or type "adb reboot bootloader" by opening a command prompt window in Platform tools directory)
To unlock bootloader run the command
Bash:
fastboot flashing unlock
The device will do a factory reset and restart itself
After Setting up your device install the magisk app from GitHub. I recommend Magisk-v24.3 as that's what worked for me.
Link: https://github.com/topjohnwu/Magisk/releases
ROOTING [MAGISK] - Using Fastboot
Transfer your boot.img to Internal Storage
You can use the command:
Bash:
adb push .\boot.img /storage/emulated/0/
After installing the magisk app Go to Install > Select and Patch a File
Select the boot.img you transferred to Internal Storage. Magisk will patch your boot.img and display the output folder after the process.
Transfer the Patched boot.img to your computer and rename it to boot_patched.img
Bash:
adb pull /storage/emulated/0/Download/magisk_patched-[random_text].img
Reboot to Bootloader
Bash:
adb reboot bootloader
Flash the patched image
Code:
fastboot flash boot boot_patched.img
You also need to flash vbmeta.img. This file is available in the firmware folder.
Bash:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Reboot the device by typing
Code:
fastboot reboot
Check Magisk manager and the device must be rooted now
TroubleshootingBoot loop after flashing magiskCould be a variety of things. Make sure that:
You've flashed vbmeta.img
You're using v24.3 of magisk
To get back to a working stage you can flash the stock boot.img and vbmeta.img. To enter fastboot mode just hold Vol - (Vol Down) + Power button forever until the fastboot mode text appears on the screen.
fastboot not detecting deviceYou'll have to install a driver manually from device manager.
Install a driver already on this computer
Select Android Phone
Select Google
Select Android ADB composite driver
After that fastboot could recognise my tablet
ThanksJohannj22 For the guide on another version of lenovo tablet which I followed https://forum.xda-developers.com/t/...of-lenovo-yoga-smart-tab-and-root-it.4387131/
Ofc Magisk for the ability to root so easily.
One of my first posts, sorry if there's any mistakes and let me know if there's any. There wasn't a forum for the yoga tab 11 so I posted here. I've been looking for months on how to root and I'm glad I figured it out and this post is here for others.
After typing flashing unlock command it enters fasboot mode and nothing happens, Left it for a while and nothing changed.
If I remember correctly it printed something on the fast boot screen when it started and when it's done. Then I rebooted into android to verify that it was actually wiped.
Hi,
about loosing L3 widevine, i assume this will also loose Amazone Prime HD, correct?
Also, will L3 Dome Back If i Go Back top Stock? Or are there any known workarounds to geht IT Back?
Noob Questions i assume, sorry, but maybe you can clarify
Ender
Tablet new, first rooted, thx. for manual!
Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.
Warning
This has only been tested on Android 13. This guide may not work for other Android versions.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Android 13
Spoiler: Step 1 - Unlocking Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Spoiler: Step 2 - Flashing TWRP
Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.img
Code:
fastboot flash recovery_b twrp.img
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Spoiler: Step 3 - Flashing Magisk
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device
3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Spoiler: Fixing Data Backup [Optional]
If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap
The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.
Spoiler: Bypassing Safetynet [Optional]
Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!
PlasmaTornado said:
Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings -> About -> Tap on Build Number 7 times
2. Open Developer Settings
3. Enable OEM Unlocking
4. Enable Android Debugging Bridge (ADB)
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
View attachment 5792895
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot oem unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Then finally:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Step 2 - Flashing TWRP Image:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
! It is HIGHLY recommended that you boot into the twrp.img before flashing to ensure that TWRPworks . I did not, but I recommend you do. !
To test this, enter the following command:
Code:
fastboot boot twrp.img
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.image
Code:
fastboot flash recovery_b twrp.image
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
You should now enter the device
3.C - Installing Magisk APK
If for some reason the Magisk Installer did not install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Click to expand...
Click to collapse
Good post but one problem...to unlock is " fastboot flashing unlock"
Canuck Knarf said:
Good post but one problem...to unlock is " fastboot flashing unlock"
Click to expand...
Click to collapse
Of course! Thank you, used to the old way of unlocking
I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
kouzelnik3 said:
I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
Click to expand...
Click to collapse
Following the method created by @dladz should still work perfectly fine!
There could still be issues with this TWRP as this is not an official image.
AFAIK Switching ROM is still untested, but decryption, backups and flashing are all confirmed working, which for me makes me feel significantly more comfortable
I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!
kouzelnik3 said:
I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!
Click to expand...
Click to collapse
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!
PlasmaTornado said:
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!
Click to expand...
Click to collapse
I will try factory wipe...flash flash from 2213...to 2215...might work
Canuck Knarf said:
I will try factory wipe...flash flash from 2213...to 2215...might work
Click to expand...
Click to collapse
Fantastic news. Let us know the results!
i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. AND my 10T and 10 Pro BOTH have been fully bricked, then formatted and flashed thru an authorized MSM Account.... Doing an ERASE ENTIRE FILE SYSTEM, thru msm, did not get rid of this file, so i doubt a twrp level wipe will do it either... MAYBE an "unlock Critical" in Fastboot, followed by a "Fastboot wipe", "DM-verity disable", and "VB-Meta erasure" MIGHT take out this crazy security system, but i know this .... if you flash an original FW using TWRP, it has protections in it to keep IT (twrp) from being overwritten, so you might find yourself in bootloop territory if you region hop.... cuz the fw might notice the changes to the partitions... For now, until someone is brave enough to challenge the Android 12 kernel and remove these trapdoors, I would just be happy you have TWRP, and wait for the person who finds and slays the Tmobile Dragon hidden in our phones! But this is truly an android 12 function that was put in place for Carrier and Manufacturer benefit ONLY. Another strike against 1+
beatbreakee said:
i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. So this is truly an android 12 function that was put in place for Carrier benefit ONLY. Another strike against 1+
Click to expand...
Click to collapse
Absolutely despicable and such an anti-consumer technique.
This stands against everything OnePlus was. It's sad to see OnePlus turn into such an anti-developer phone
A Carrier should never have this much power over a device. It is absurd
heres a google drive link to my account if anyone wants to see a video of what you will go thru if triggered!
feel free to share or re-upload the link/video to anywhere... ppl need to know this is happening thanks to Tmobile and Oneplus collaboration. I have not seen any reference to another carrier inside any of the device policy files, and my phone was restored to a NON TMO branded build of android 12 for the 2217 NA model, so it should NOT have even recognized the TMO policies cuz i even used a new sim card after the MSM Unbrick, and it still instantly locked in less than a second of plugging it in... heres the vid
https://drive.google.com/file/d/17H6YpGrUCe1Y7PoFji4gperdpTHNX5AI/view?usp=sharing
also everyone should know, that EVERY fw on the internet no matter whether it is labeled, 2213, or 2215... 2217, as well as 2413-2419 ALL have EVERY other model's manifest built in and all of the restrictions / bloatware that each region comes with, saved into the OFP extracted files.... so there really is nothing that expressly was bricking your phones by simply flashing a different labeled FW..... the brick came from the manifest reading the region identifiers that the manifests are labeled under.... it is a file that is again picked by some random hidden check inside the TMO EFS, and as soon as your phone tries to boot the newly flashed FW, the TMO Lock is what bricks your phone, to either a bootloop state, or if you continue to force a flash by using Fastboot , you will have a non responsive phone, thanks to this stupid security issue. If unresponsive, the only way out is MSM Tool... and i can help you locate your test points if your buttons dont work.
I cannot publicly post a picture nor a description of where the test points lie inside the 10T , because i already got a cease and desist letter from BBK and i dont know if they have said anything to the mods here about posting Undisclosed hardware access points.... but ive been a member here almost 10 years, and i aint risking a ban from a tattle tale company! There are test points on the 10 t though,.. just well hidden!
The 2nd pic is of the 2217 Unpacked OFP , yet the build prop shows a 2210-2211 base in one and a 2413-2415 base in the.... with NO 2217 in either prop,or manifest file, yet when my phone was flashed back from Brick status, THIS is the FW that was used, and my phone identifies as a 2217 NA now..... can oneplus be any more clear that they have completely turned against us, by straight SHOWING US that they are being super cryptic and sneaky in something as common as the BUILD.PROP files?!?
The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?
kouzelnik3 said:
The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?
Click to expand...
Click to collapse
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )
Canuck Knarf said:
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )
Click to expand...
Click to collapse
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.
kouzelnik3 said:
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.
Click to expand...
Click to collapse
Yeah i hear you but I'm not sure if this a bootable version or a just install version....I will try it on mine to see if i get the same as you
Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works
Canuck Knarf said:
Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works
Click to expand...
Click to collapse
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?
kouzelnik3 said:
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?
Click to expand...
Click to collapse
It appears the image is not bootable. As stated, this is the one thing I didn't try.
I have amended the guide. Thank you