Hello,
yesterday I accidentally entered fasboot mode by pressing the button combination on boot.
My phone is now stuck in fastboot mode and I can't figure out how to get out.
I've installed fastboot and the appropriate drivers on my computer (W10), but if I try 'fastboot reboot', the phone boots straight into fastboot mode. I tried formatting the cache and rebooting, but still got the same result. If I switch off the phone by holding the power button and then turning it on again (tried with every button combination), it only boots into fastboot. I even tried letting the phone run out of power, but when I charged it a bit and switched it on again, it went to fastboot again.
My phone is unlocked and rooted and has Havoc OS installed.
Any help is greatly appreciated.
Have you tried fastboot continue? You may want to spam that command for good while.
It should be written on the screen how to get out of fastboot mode, press and hold power button to shutdown the device. How exactly can't you boot to the system?
XDHx86 said:
Have you tried fastboot continue? You may want to spam that command for good while.
Click to expand...
Click to collapse
Haven't tried it before.
After typing it, I get an error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: 00000050)
finished. total time: 0.316s
What is located at 00000050?
I probably have to reinstall something, I'm just not sure what. Recovery/Bootloader/OS ?
XDHx86 said:
It should be written on the screen how to get out of fastboot mode, press and hold power button to shutdown the device. How exactly can't you boot to the system?
Click to expand...
Click to collapse
Yes, it says to hold the power button. This switches the phone off, but after starting it again it automatically goes into fastboot.
Thanks for your replies, Slllingy
Slllingy said:
Haven't tried it before.
After typing it, I get an error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: 00000050)
finished. total time: 0.316s
What is located at 00000050?
I probably have to reinstall something, I'm just not sure what. Recovery/Bootloader/OS ?
Yes, it says to hold the power button. This switches the phone off, but after starting it again it automatically goes into fastboot.
Thanks for your replies, Slllingy
Click to expand...
Click to collapse
Your device is bricked as it can't load or authenticate the boot image, you need to unbrick it.
Flashing the stock image should work. Of course don't forget to backup your data through TWRP.
I downloaded the stock firmware from ASUS, but it's a zip file and the only .img contained is boot.img.
I tried erasing all the partitions (chache, data, system, boot, recovery) and flashing the stock boot.img (from ASUS) and the lastest TWRP recovery img (specific to my phone).
I no longer get the "Failed to load image from partition..." error, but after fastboot reboot the screen turns off, then it turns on, warns me that my bootloader is unlocked, shows the android logo, then the asus logo, then it turns off again, then on again, briefly shows the androif logo and goes straight into fastboot. Basically the same happens when I manually switch the phone off and turn it on or with fastboot continue.
I can not access my reccovery.
Where can I find a sytem.img file to flash with fastboot?
Or is there any other way to unbrick my phone?
Thanks again, Slllingy
Related
Need help here!
My Nexus 10 was with stock 4.4.4, rooted with TWRP. I decided to flash the factory image files by removing the -w in flash-all.sh. However it ended up with being stuck with the rotating balls. After about 45 minutes, I decided to go to the fastboot mode (pwr+both volumes), then select recovery (I planned to do factory reset and clear cache). After trying to reboot into recovery mode (pwr + one volume button), it now shows an open bootloader with following message below the bootloader (the bootloader seems still unlocked):
Dowloading...
Do not turn off target!!
What does it mean? What is it exactly downloading? And what should I do? Should I lock the bootloader? Also it does not respond now if I push the volume buttons. It's not recognized on my Mac with the with the following command:
fastboot devices
I also notice the following line:
Reboot Mode Flag: NONE
Now I just booted into recovery, but it shows the bootloader with the exclamation mark! After a few minutes, it automatically switched to the never-ending rotating balls. What can I do?
When you get the Downloading...message you're in the Recovery screen. Don't worry about the message. Press vol up and power to get into the recovery menu - there you can wipe cache and system. As you're in recovery, Fastboot devices will not recognise your tablet, only adb commands.
If I was you and this didn't work, I'd just reboot into fastboot and flash the image files manually. You'll lose root, data and twrp but these can easily be gotten back through fastboot.
Hi,
In case you want help to flash Stock Firmware files. Check the Manta Help Thread .
http://forum.xda-developers.com/showthread.php?t=2670400
~Lord
https://www.youtube.com/watch?v=niTlq4Qjhh4
Okey I have done my 1st v20 phone perfectly well. my 2nd one (my wife's) is stuck after step3 in dirty santa (flashing twrp - ok, starting twrp - won't start) it won't open. Follow the instruction (volume down+ power, lg screen, re-press power button 4sec, choose yes, yes, twrp should start) - it starts something with a circle all is below static screen. I do try to choose something with my fingers, but nothing changes. when you hit power button for 0.01sec the phone restarts and stucks in lg boot logo, re-do twrp start procedure - same thing repeating. tryed done the step3 again - successfully - same result - won't start twrp properly.
At no point of dirtysanta procedure I got any of the corrupt device pre-boot warning. done everything as instructed and as on my 1st all-went-well v20.
That circle is the boot up image.
Try
Fastboot commands
Fastboot erase system
Then place the twrp.img from dirty sanat with fasboot stuff and name it twrp.img
Fasboot flash recovery twrp.img
Then unplug and pull battery, put battery in and hold volm down and power.. When lg logo shows up let power go for 1 second and re hold it immediately. When prompt shows up yes yes and wait... Should get twrp.
That or re-run step 3 after sending fasboot erase system command and it will push the boot.img over and twrp again..
Team DevDigitel said:
That circle is the boot up image.
Try
Fastboot commands
Fastboot erase system
Then place the twrp.img from dirty sanat with fasboot stuff and name it twrp.img
Fasboot flash recovery twrp.img
Then unplug and pull battery, put battery in and hold volm down and power.. When lg logo shows up let power go for 1 second and re hold it immediately. When prompt shows up yes yes and wait... Should get twrp.
That or re-run step 3 after sending fasboot erase system command and it will push the boot.img over and twrp again..
Click to expand...
Click to collapse
Worked. Priceless! Next: using the xda search to find (if any) solution for removing the corrupt screen message after restart or power up. Not big deal but really hate this message
https://forum.xda-developers.com/nexus-5x/help/to-remove-corruption-warning-message-t3248441
Sent from my LG-LS997 using Tapatalk
nexus6r3plicant01 said:
https://forum.xda-developers.com/nexus-5x/help/to-remove-corruption-warning-message-t3248441
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Only for those specific devices our images are hosted in the bootloader. Not a IMG partition
I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.
Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick
I tried, didn't work. Had to factory reset in the end. Also opted out of beta
I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?
OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.
last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty
I recently got the Essential Phone and instinctively decided to mess around and flash a custom recovery. I then found out that TWRP is not compatible with the essential phone running 8.1 beta. I am now stuck in fastboot mode. However, when i enter recovery mode, it goes straight to the logo screen with powered by android underneath and nothing occurs. When I start the phone back up, it also goes to the powered by android screen and does not load up. My computer does not recognize my device through ADB. My bootloader is unlocked. Any help is much appreciated as I do not want to have a useless phone after having it for a day. Thank you
--from what i gathered, fixing the phone is a matter of flashing the stock.img, which i have downloaded. However, because my phone is unable to be recognized by adb/fastboot I am unsure how to accomplish this
nickyg101 said:
I recently got the Essential Phone and instinctively decided to mess around and flash a custom recovery. I then found out that TWRP is not compatible with the essential phone running 8.1 beta. I am now stuck in fastboot mode. However, when i enter recovery mode, it goes straight to the logo screen with powered by android underneath and nothing occurs. When I start the phone back up, it also goes to the powered by android screen and does not load up. My computer does not recognize my device through ADB. My bootloader is unlocked. Any help is much appreciated as I do not want to have a useless phone after having it for a day. Thank you
--from what i gathered, fixing the phone is a matter of flashing the stock.img, which i have downloaded. However, because my phone is unable to be recognized by adb/fastboot I am unsure how to accomplish this
Click to expand...
Click to collapse
Make sure not to use the cable that came with the phone.
Reboot the computer, try a different USB port.
tech_head said:
Make sure not to use the cable that came with the phone.
Reboot the computer, try a different USB port.
Click to expand...
Click to collapse
I am using a different cable; one i purchased separately from the phone. After rebooting computer, should i again attempt to connect via adb and fastboot and, if it connects, attempt to flash to stock? thank you very much for the quick response
nickyg101 said:
I am using a different cable; one i purchased separately from the phone. After rebooting computer, should i again attempt to connect via adb and fastboot and, if it connects, attempt to flash to stock? thank you very much for the quick response
Click to expand...
Click to collapse
after resetting my mac, it recognizes my phone in fastboot mode
- i believe now all i need to do is flash the stock image i downloaded, which im not sure how to do
nickyg101 said:
after resetting my mac, it recognizes my phone in fastboot mode
- i believe now all i need to do is flash the stock image i downloaded, which im not sure how to do
Click to expand...
Click to collapse
The stock image on essential website has fastboot script.
Joylesstuna said:
The stock image on essential website has fastboot script.
Click to expand...
Click to collapse
when i locate the file, how should i flash it as?
fastboot flash boot 'boot.img'
my phone is not recognized over adb; rather when i go to recovery i got the red triangle over the android with "no command" underneath it
update: thank you all for the help i appreciate it a lot. When i run the script that came with the download from the essential site, my phone will boot back up but the wifi does not work.
Macintosh-2:~ xxxxx$ #!/bin/bash
Macintosh-2:~ xxxxx$ fastboot flash nvdef nvdef.img
error: cannot load 'nvdef.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash system system.img
error: cannot load 'system.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash bluetooth bluetooth.img
error: cannot load 'bluetooth.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash abl abl.img
error: cannot load 'abl.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash dsp dsp.img
error: cannot load 'dsp.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash modem modem.img
error: cannot load 'modem.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.294s]
finished. total time: 0.294s
Macintosh-2:~ xxxxx$ fastboot reboot
rebooting...
This is what occured in terminal and then my phone subsequently booted up into the new phone setup screen. it looks like the problem is that its not flashing any of the required modules and is only erasing my phone?
i was able to flash each however it just keeps rebooting to the fastboot screen :/
nickyg101 said:
i was able to flash each however it just keeps rebooting to the fastboot screen :/
Click to expand...
Click to collapse
Which firmware are you trying to flash?
Are you using one of the back to stock ROM images?
That is what you should use.
Open the script and use the commands line by line in a terminal.
If you are using a Mac it is a good idea to reboot before you start flashing.
If you have used ads or fast boot, it can sometimes get into a state where it won't see the device.
My Mac (native USB-C) will often crash when trying to flash the system image.
Yes I am attempting to flash back to stock. I got the zip from the essential site https://www.essential.com/developer/current-builds
and this is what the package looks like
nickyg101 said:
Yes I am attempting to flash back to stock. I got the zip from the essential site https://www.essential.com/developer/current-builds
and this is what the package looks like
Click to expand...
Click to collapse
I would look here and flash one this post.
https://forum.xda-developers.com/showpost.php?p=74437484&postcount=1
Every time i try flashing the stock stuff back on to the device, it boots right into bootloader (my bootloader is unlocked) no matter what. Is there a way around this or do you know why this would occur?
tech_head said:
I would look here and flash one this post.
https://forum.xda-developers.com/showpost.php?p=74437484&postcount=1
Click to expand...
Click to collapse
I flashed the april version of oreo and it flashes everything but then still always just boots right into fastboot mode. thank you for your continued help
You need to use the command fastboot flashing unlock_critical
Then use the back to stock firmware from this thread
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page48
That should set you write and don't forget to fastboot -w as well just to make sure
We got it back to stock Thanks everyone. It was a small thing I was missing on my end
Also when going into recovery, when you get to the "no command" screen you to press a key combo to enter recovery mode. I think it was power then volume up. It's always like that even in a fully functional device.
Would you mind posting how you fixed it and what was wrong? This is how we learn!
Recently got a hold on the T-Mobile version of the OnePlus 6T. Already have a OnePlus5 running LineageOS as well and thought the installation would go as smooth.
Following these directions, I got through unlocking the bootloader (with the unlock_code.bin from OnePlus) and I thought I'd gone through flashing a custom recovery. I was able to boot into fastboot, ran # fastboot flash boot lineage-18.1-20210506-recovery-fajita.img, and shutoff the device. Now I'm stuck in a bootloop at the screen indicating that the device has been unlocked and data can't be verified.
While still connected to my PC, any combination of Power + Volume keys will flash the display and instantly go back to the bootload screen. The only way to shut-off the phone is to disconnect it and do either Power + Volume Up or Power + Volume Up + Volume Down; Power + Volume Down to try and boot into recovery does nothing. Plugging in the phone while off auto-starts it back to the bootload loop.
I can turn on the phone while disconnected, but the only way to escape the bootload loop is to boot straight into fastboot with Power + Volume Up + Volume Down. From here I can connect it to the computer and it's seen as a fastboot device. From here, however, any of the options will reboot into the bootloop.
Is there anything I can do from here? It's not a hard-brick, but I'm not sure why I'm stuck in a loop. The flashing of the recovery seems to have worked, no issues with A/B as stated could happen in the docs. I'm at a loss.
Code:
Sending 'boot_a' (65536 KB) OKAY [ 1.573s]
Writing 'boot_a' OKAY [ 0.365s]
Finished. Total time: 1.947s
Data can't be verified? It does let you run fastboot commands, just not send files?
Most people on this device use TWRP. I have a guide here.
OhioYJ said:
Data can't be verified? It does let you run fastboot commands, just not send files?
Most people on this device use TWRP. I have a guide here.
Click to expand...
Click to collapse
Yes, I can get the fastboot menu, but trying to boot from the lineage recovery image would take me straight to the warning page indicating the device is unlocked and to not store confidential data.
I just tried using the guide you posted to go with TWRP, but I'm having issues again with booting the recovery. Followed every step: downloaded the ROMs, flashed them all to the phone as per your script, was able to boot, chose the language and wiped, and once in the phone rebooted into the bootloader. But similar to before, I run # fastboot boot twrp-3.5.2_9-0-fajita.img, but now the phone seems to be stuck on the OnePlus logo with the words Fastboot Mode underneath.
savoyroad said:
Yes, I can get the fastboot menu, but trying to boot from the lineage recovery image would take me straight to the warning page indicating the device is unlocked and to not store confidential data.
I just tried using the guide you posted to go with TWRP, but I'm having issues again with booting the recovery. Followed every step: downloaded the ROMs, flashed them all to the phone as per your script, was able to boot, chose the language and wiped, and once in the phone rebooted into the bootloader. But similar to before, I run # fastboot boot twrp-3.5.2_9-0-fajita.img, but now the phone seems to be stuck on the OnePlus logo with the words Fastboot Mode underneath.
Click to expand...
Click to collapse
You may need to start over. I the unfortunate part here is the TMobile 6T is a bit different and complicates things. Recent TMobile MSM Tools have been posted in the TMobile thread, they just aren't in the OP. I'll be honest I don't follow the TMobile devices, so I don't know much about what's best to use between versions and international tools and what not. There are a few TMobile users that posted in my Guide thread that you may want to tag and see if they can help?