Related
I have a one xl that will reboot after being on for 2 minutes
evita pvt ship s-on rl
hboot-1.14.0002
it is unlocked, but i cant relock it. Every time i try it says fails then reboots. I have also tried flashing twrp and cwm recovery via fastboot, but everytime i try to enter one it hangs on the teamwin screen. I have tried the ruu it reads my phone at first then when it says rebooting to bootloader the phone reboots normaly and get error 107.
Any help would be greatly appreciated.
What method are you using to try to relock the phone? What method are you using to install the mentioned recoveries? Please give as much detailed information as possible.
Sent from my Evita.
To relock i have used fastboot in cmd and typed fastboot oem lock. I have done that 10 times with the same result phone reboots normally and when i reboot back into bootloader it still says unlocked.
To flash recoveries i have used fastboot flash recovery ********.img
fastboot erase cache
fastboot reboot-bootloader
but instead of rebooting to the bootloader it boots normally
What did you do to the phone before all this started happening? Phones don't usually just start doing things like this of their own accord.
Sent from my Evita.
I bought it like this. The last owner said it happend after he installed a rom. I was hopping i could unbrick it with out jtagging it becuase i am still able to fastboot to it.
If you can't get an RUU to work I think jtag might be your only option.
Sent from my Evita.
I've only tried 2.20. I even extracted the system IMG from it but fast boot says it is too large. The only reason ruu won't work is because I can't get my phone to reboot into boot loader. Is there any way I can flash a different boot loader through fast boot.
Just curious, but when you type fastboot devices from the Bootloader, what is the output?
Are you running fastboot oem lock from the bootloader?
Sent from my One X using XDA Premium 4 mobile app
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
keithman2567 said:
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
Click to expand...
Click to collapse
If when you type fastboot devices (while in the boot loader) in your computers command prompt, and it doesn't show your HTC device being attached, that means that your computer is not recognizing your phone. Have you installed the HTC drivers? Do you have the newest versions of fastboot and adb installed?
What OS are you running on your computer?
Sent from my One X using XDA Premium 4 mobile app
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
keithman2567 said:
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
Click to expand...
Click to collapse
Does your device boot into the ROM at all?
Sent from my One X using XDA Premium 4 mobile app
Yes. But only for 2 mins before it reboots.
keithman2567 said:
Yes. But only for 2 mins before it reboots.
Click to expand...
Click to collapse
If you can connect to Google Play store, download recovery tools, if you have time. From there you could try to install a new recovery for your device. With only 2 minutes you will have to be quick though.
Do you have access to your sdcard from your computer?
Sent from my One X using XDA Premium 4 mobile app
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
keithman2567 said:
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
Click to expand...
Click to collapse
Here is the app. Not sure if you'll have time, but you can try
https://www.dropbox.com/s/wa4u565woyrrrlw/de.mkrtchyan.recoverytools-2.apk
Sent from my One X using XDA Premium 4 mobile app
Thank you, but there isn't enough time to even transfer it over
keithman2567 said:
Thank you, but there isn't enough time to even transfer it over
Click to expand...
Click to collapse
Do you have USB debugging enabled in the phone?
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:15 PM ----------
Have you tried to flash a new ROM from fastboot? It sounds like your recovery partition might have been corrupted.
Sent from my One X using XDA Premium 4 mobile app
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
keithman2567 said:
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
Click to expand...
Click to collapse
Alright, so I have a few ideas.
1. Try flashing a new rom via fastboot. (the following is based on the assumption that you have adb and fastboot in your path)
Flashing a ROM through Fastboot
So Why Do I Need To Do This?
You don't, normally you would flash a ROM through recovery, but why not have another way? Maybe your recovery partition on your phone is corrupt?
Maybe you just want to say "I learned something new!" whatever your reason here are the simple steps:
To start:
Quote:
Quote:
We need to download the ROM of choice to your computer. Once complete find the folder that rom is in and open terminal/cmd to that directory
(quickest way for windows; just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
2. Boot into Recovery via fastboot.
Plug phone into PC, connect with USB cable and have phone in fastboot mode, now open CMD/Terminal in the same directory as your recovery image
Code:
fastboot boot recovery.img
Of course name image correctly to fit command or vise versa
Now you are in recovery of choice within your device without it being flashed to your recovery partition. There is a time and a place for everything, can you think of ways this may help you? Sure you can!
This doesn't actually flash the recovery.img... it will just allow you to boot into it. Make sure that you have a good TWRP version.
The previous quotes were taken from this guide on XDA-University:
http://forum.xda-developers.com/showthread.php?t=2277112
EDIT: made a typo the first few tries!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
please see post #2
i was making a mistake. the correct command line is
adb devices
adb reboot bootloader
adb sideload update.zip
in this last command line it says:
loading : 'update.zip'
error: device not found
what now? when i type adb devices it sees my phone before rebooting into bootloader. after i reboot into bootloader and i type adb devices it does not give me any result
cesar.maranhao said:
i was making a mistake. the correct command line is
adb devices
adb reboot bootloader
adb sideload update.zip
in this last command line it says:
loading : 'update.zip'
error: device not found
what now? when i type adb devices it sees my phone before rebooting into bootloader. after i reboot into bootloader and i type adb devices it does not give me any result
Click to expand...
Click to collapse
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
thanks, I see I am doing it all wrong..
i have found this guide
http://forum.xda-developers.com/showthread.php?t=2559200
when i get to the
adb usb
it also says device not found despite the deamon starting successfully on port 5037... i will need help please
cesar.maranhao said:
thanks, I see I am doing it all wrong..
i have found this guide
http://forum.xda-developers.com/showthread.php?t=2559200
when i get to the
adb usb
it also says device not found despite the deamon starting successfully on port 5037... i will need help please
Click to expand...
Click to collapse
First off, you need the stock recovery, not twrp or cwm to flash the update.zip. If you don't have the stock recovery you'll need to flash it in fastboot with the recovery.img from 5.0. Are you on the stock recovery? Also, are you rooted?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
First off, you need the stock recovery, not twrp or cwm to flash the update.zip. If you don't have the stock recovery you'll need to flash it in fastboot with the recovery.img from 5.0. Are you on the stock recovery? Also, are you rooted?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
yes, i am rooted with twrp custom recovery.
i tried to install the ota zip from the custom recovery. the ota file i downloaded and it failed. i tried all three options you see in this topic:
http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327
what should i do then?
1. Its adb reboot-bootloader to reboot into the bootloader.
Have to choose recovery from the bootloader, then press and hold power button then press volume up once to be able to choose adb sideload and press power. Once choosing this option from recovery then check adb devices. If it doesn't recognize your device then the USB drivers are not installed properly. Go to device manager on your PC to install the correct drivers. There are a few post already about this. Alternately you can use universal naked drivers. These work very well with Nexus devices.
2. Have to be completely stock to apply the OTA. Simply clicking unroot via supersu does not allow the update to apply.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
cesar.maranhao said:
yes, i am rooted with twrp custom recovery.
i tried to install the ota zip from the custom recovery. the ota file i downloaded and it failed. i tried all three options you see in this topic:
http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327
what should i do then?
Click to expand...
Click to collapse
First unroot using the full unroot option in supersu settings. Then you'll need to flash the system, recovery, and boot images from 5.0 with fastboot. Then you can sideload the update.zip in the stock recovery. If you've changed the radio you'll have to flash that from 5.0 too
It's a pita. The other option is to just flash in fastboot the radio, system, and boot images from 5.0.1 and forgo the ota.
Either option won't wipe data
Sent from my Nexus 9 using XDA Free mobile app
Jnewell05 said:
1. Its adb reboot-bootloader to reboot into the bootloader.
Have to choose recovery from the bootloader, then press and hold power button then press volume up once to be able to choose adb sideload and press power. Once choosing this option from recovery then check adb devices. If it doesn't recognize your device then the USB drivers are not installed properly. Go to device manager on your PC to install the correct drivers. There are a few post already about this. Alternately you can use universal naked drivers. These work very well with Nexus devices.
2. Have to be completely stock to apply the OTA. Simply clicking unroot via supersu does not allow the update to apply.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
jd1639 said:
First unroot using the full unroot option in supersu settings. Then you'll need to flash the system, recovery, and boot images from 5.0 with fastboot. Then you can sideload the update.zip in the stock recovery. If you've changed the radio you'll have to flash that from 5.0 too
It's a pita. The other option is to just flash in fastboot the radio, system, and boot images from 5.0.1 and forgo the ota.
Either option won't wipe data
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I am so confused.. when i bought my nexus 5 i upgraded kitkat several times by flashing a downloaded OTA from xda forums inside custom recovery. i just flashed the update and flashed the supersu afterwards to keep root.
i do not understand what is happening now, i never done such steps before.
were those kitkat ota's modified by xda members to help not so knowledgeable users like me to update?
this is what I have been using:
EDIT:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
Just noticed thisis only for 4.4.4 OTA's and below only.
cesar.maranhao said:
I am so confused.. when i bought my nexus 5 i upgraded kitkat several times by flashing a downloaded OTA from xda forums inside custom recovery. i just flashed the update and flashed the supersu afterwards to keep root.
i do not understand what is happening now, i never done such steps before.
were those kitkat ota's modified by xda members to help not so knowledgeable users like me to update?
Click to expand...
Click to collapse
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
you missed my last edit while you were replying.
EDIT:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
Just noticed thisis only for 4.4.4 OTA's and below only.
Click to expand...
Click to collapse
it is more clear for me now. i used all those fastboot command line when i flashed 5.0.0, one line for each image.
i will do that for 5.0.1. thanks a lot mate for all the clarification.
one last question: will I lose any data/configurations by apllying this method?
cesar.maranhao said:
you missed my last edit while you were replying.
it is more clear for me now. i used all those fastboot command line when i flashed 5.0.0, one line for each image.
i will do that for 5.0.1. thanks a lot mate for all the clarification.
one last question: will I lose any data/configurations by apllying this method?
Click to expand...
Click to collapse
No data will be lost. Everything will still be there
Oh, you're custom recovery will be gone and you'll have to re-root but that's easy. If you have problems let me know.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
No data will be lost. Everything will still be there
Oh, you're custom recovery will be gone and you'll have to re-root but that's easy. If you have problems let me know.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nice! i suppose i need to flash the custom recovery and root again right?
cesar.maranhao said:
nice! i suppose i need to flash the custom recovery and root again right?
Click to expand...
Click to collapse
Yep, flash the twrp.img in fastboot, fastboot flash recovery twrp.img (I recommend twrp, if you have a problem with this step let me know. It may try to keep the stock recovery). Then flash supersu 2.4 in twrp
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Yep, flash the twrp.img in fastboot, fastboot flash recovery twrp.img (I recommend twrp, if you have a problem with this step let me know. It may try to keep the stock recovery). Then flash supersu 2.4 in twrp
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
will you stay online for a while? if I run into trouble you already know what is going on
cesar.maranhao said:
will you stay online for a while? if I run into trouble you already know what is going on
Click to expand...
Click to collapse
I'll be here
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'll be here
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
cesar.maranhao said:
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
Click to expand...
Click to collapse
Put SuperSU beta flashable zip on your sdcard then fastboot flash TWRP. Boot directly into recovery and flash SuperSU
cesar.maranhao said:
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
Click to expand...
Click to collapse
I thought that would be the problem. You'll want to boot twrp, flash supersu and the flash twrp
fastboot boot twrp.img
Then flash supersu in twrp
Then boot back into the bootloader and
fastboot flash recovery twrp.img
There are couple of scripts, one in /system and one in /system/bin that put the stock recovery back on. You could remove the scripts put I find this easier
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I thought that would be the problem. You'll want to boot twrp, flash supersu and the flash twrp
fastboot boot twrp.img
Then flash supersu in twrp
Then boot back into the bootloader and
fastboot flash recovery twrp.img
There are couple of scripts, one in /system and one in /system/bin that put the stock recovery back on. You could remove the scripts put I find this easier
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
rootSU said:
Put SuperSU beta flashable zip on your sdcard then fastboot flash TWRP. Boot directly into recovery and flash SuperSU
Click to expand...
Click to collapse
i am having problems in putting the supersu file into my nexus 5, it says the device has either stopped or has been disconnected.. this never happened before. i haveit setup as MTP. also tried ptp without success
So I was trying to get into fastboot to put TWRP on my phone and it wont boot into that mode. I tried via ADB but it just reboots the device. Anyone have a suggestion as to what I can do. This is my current version
Try the following command "fastboot oem unlock" before installing twrp through fastboot.
Sent from my R7plusf using XDA-Developers mobile app
No that is not the solution. I think you updated to the latest version and together with that you lost the option to fastboot your device. I had exactly the same thing. What I did was I flashed back an older full official rom and with doing that I got the fastboot option back. There is a thread on this on the oppoforums, here's the link: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46631&extra= Here i pointed out what i did and which file i used.
My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.
This is my first time rooting a phone but Im defiantly in over my head and think i almost broke the oneplus 6 when i was trying to enter commands in the linux terminal. So far I have unlocked bootloader and am currently stuck trying to figure out a) what exactly the twrp recovery really does, b) which is the right files to download, c) the proper commands to flash custom recovery in a linux terminal. Thanks in advance to anyone who can help me.
Command you need is fastboot boot (recovery name). Replace recovery name with whatever you called the download of the twrp image file.
Twrp is necessary to flash custom ROMs, kernels and magisk.
After flashing rom you need to flash twrp zip of your choice to maintain recovery otherwise it is overwritten by stock recovery.
There is a helpful guide I will post the link to
Here
https://r.tapatalk.com/shareLink?ur...share_tid=3792643&share_fid=3793&share_type=t
Sent from my ONEPLUS A6003 using Tapatalk
The commands for Linux and Windows are nearly identical. You just need to use the Linux version of adb instead of adb.exe.
TWRP is a custom recovery. It's similar to the GRUB bootloader for Linux, but more touch interface friendly. It allows you to make edits to the system, backup the system, and install custom zip's for the system.
keep getting error
when i run command to flash recovery (sudo fastboot flash twrp-3.2.1-0-enchilada.img) i keep getting this error:
unknown partition 'twrp-3.2.1-0-enchilada.img'
error: cannot determine image filename for 'twrp-3.2.1-0-enchilada.img'
Instead of trying to flash twrp from fastboot do a sudo fastboot boot <image name> then flash the zip while in twrp...
Sent from my ONEPLUS A6003 using Tapatalk
Thanks bkeaver for the advice and im glad to say I finally got that phone rooted. One more obstical I experienced was the phone not booting into twrp instead it was locking up on a screen that said Qualcomm crash dump mode. I unplugged and rebooted by holding the power button. From what I could read online it had to do with compatibility issues with Android pie. The Blu_Spark TWRP img and zip files seemed to do the trick. Anyone else who is experiencing the same issues I suggest you read this page: google.com/amp/s/amp.reddit.com/r/oneplus/comments/9iid4e/unable_to_flash_recovery
Linux_fart_18.3 said:
when i run command to flash recovery (sudo fastboot flash twrp-3.2.1-0-enchilada.img) i keep getting this error:
unknown partition 'twrp-3.2.1-0-enchilada.img'
error: cannot determine image filename for 'twrp-3.2.1-0-enchilada.img'
Click to expand...
Click to collapse
Did you even try to read man page? Just use right syntax, which is identical in Windows BTW.
fastboot flash partition [filename]
http://manpages.ubuntu.com/manpages/xenial/man1/fastboot.1.html
Linux_fart_18.3 said:
From what I could read online it had to do with compatibility issues with Android pie.
The Blu_Spark TWRP img and zip files seemed to do the trick.
Anyone else who is experiencing the same issues I suggest you read this page: google.com/amp/s/amp.reddit.com/r/oneplus/comments/9iid4e/unable_to_flash_recovery
Click to expand...
Click to collapse
In oxygen OS ver.9, you must download "twrp-3.2.3-x_blu_spark_v9.86_op6.img" and "twrp-3.2.3-x_blu_spark_v9.86_op6.zip" from https://forum.xda-developers.com/devdb/project/?id=27466#downloads ,
and launch twrp from this command "fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img".
After your device boot trwp, you can install "twrp-3.2.3-x_blu_spark_v9.86_op6.zip" from your device's internal storage (if you copy into it) or adb side-load mechanizm.
Once zip installed, you don't need to run fastboot to boot twrp recovery (only you reboot the device to fastboot mode and select recovery, trwp boot up).
What's a syntax?
davfiala said:
Did you even try to read man page? Just use right syntax, which is identical in Windows BTW.
fastboot flash partition [filename]
http://manpages.ubuntu.com/manpages/xenial/man1/fastboot.1.html
Click to expand...
Click to collapse
rhetorical question in the title and fyi I will never claim to be very tech savvy thanks for the info though