Database Users

Successful Root and Unlock HTC One M8 with VZW Lollipop

Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!

UPDATES?
i need this working bro, my m8 is pissing me off, king root wont work i followed all your instructions
also what version of kingroot did you have?
radiowavedev said:
Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!
Click to expand...
Click to collapse

I'll work on creating a step by step when I get home. I've just been really busy. It's just a lot of trial and error but it should work at some point. Keep a look out for my reply tonight.

xercurial said:
i need this working bro
Click to expand...
Click to collapse
Such a polite way of asking someone to go out of their way to help you or write a guide for you.

lol sorry about that man i did however end up rooting it , now im having trouble
redpoint73 said:
Such a polite way of asking someone to go out of their way to help you or write a guide for you.
Click to expand...
Click to collapse
i am having trouble iwth twrp

xercurial said:
i am having trouble iwth twrp
Click to expand...
Click to collapse
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?

twrp issues
redpoint73 said:
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?
Click to expand...
Click to collapse
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!

Alright, sorry that I lied about going home and typing up a step by step things are just hectic ya know? Anyways i'm here now so let me gather myself and get you some help. lol

xercurial said:
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!
Click to expand...
Click to collapse
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure) then installed it through adb and it has been working flawlessly. I since installed ViperOne without any problems. The version of twrp I got was 2.8.7.0. Once you get your phone going again i'd suggest reinstalling twrp through adb.

xercurial said:
i have the one the ends with 7.0.1
Click to expand...
Click to collapse
As noted by the previous response, you should get the latest version of TWRP (2.8.7.0) if you are on Lollipop firmware. TWRP versions 2.7 are known to be problematic on LP.
---------- Post added at 11:32 AM ---------- Previous post was at 11:07 AM ----------
radiowavedev said:
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure)
Click to expand...
Click to collapse
You're correct, TWRP for CDMA (Verizon, Sprint) and GSM versions (most other M8 versions) was merged some time ago.

Lenovo a6000 Plus total dead

Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.

Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Plz any developers help him
Sent from my Lenovo A6000 using Tapatalk

Find how to flash device with qfil in google

Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).

sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
Im on rr 5.7.3
- first i wipe data,dalvik,cache and system in twrp
- flash L2KK.zip
- reboot recovery and stuck at boot (lenovo powered by android)
i know i have to flash twrp for kitkat right? but i end up flashing something about partition because i wasnt giving attention. not my phone cannot go into recovery or fastboot. just a red notification light. i know this is my fault.

@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.

sasukay said:
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
Click to expand...
Click to collapse
nope

Irwan Fauzi said:
nope
Click to expand...
Click to collapse
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.

sasukay said:
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
Click to expand...
Click to collapse
maybe i have to send my phone to service center because qualcomm doesnt detect my device.

sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......

Sloved
i have sent my device to service center.. thanks to everyone who trying to help me..

Irwan Fauzi said:
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
Click to expand...
Click to collapse
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
bvsbrk said:
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Click to expand...
Click to collapse
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.

sasukay said:
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
Click to expand...
Click to collapse
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.

bvsbrk said:
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
Click to expand...
Click to collapse
I can understand who you are talking about
No problem
I never considered myself above anyone so something

Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.

Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
I would not suggest flashing a6000 s ROM on your new phone or you may end up like your a6000

Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
Don't you ever try to flash custom ROM that not supported for your phone

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!

Oneplus 6T bricked in fastboot loop...Please help!

Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!

OP6TNewb said:
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
Click to expand...
Click to collapse
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.

Problem SOLVED!!!
justibasa said:
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Click to expand...
Click to collapse
Thanks for your follow up.
Just want to let you now that I fixed it using the Stock Fastboot tool posted here
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I just did exactly as instructed; my phone was already stuck in fastboot so I plugged to my PC and ran the flash-all.bat file. I really didn't think it would work because the phone did not seem to respond or do anything. I went to the toilet, came back and it was reset to factory!!!! Amazing.
Thank you so much @mauronofrio for posting this amazing tool. You saved my bricked phone! I sent you a donation for your assistance. Thanks again.

Just for future reference, as long as you can get this phone into fastboot, you should be fine. For now that's where all the flashing happens until we get a custom recovery.
But I'm glad to hear you fixed it lol

Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.

Pain-N-Panic said:
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Click to expand...
Click to collapse
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.

OP6TNewb said:
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
Click to expand...
Click to collapse
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?

Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
They probably have gone off to brag to their friends about what happened. Lol
I, too, am curious about what he did. It's been so long since I first began tinkering, but certainly remember some times I goofed.
Sent from my ONEPLUS A6013 using Tapatalk

Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!

OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
I forgot to mention one thing which may also be the reason. Initially, before using Adam Conways instructions, I started with the steps on High on Android (Max Lee) for the OP6 but on their download page, I mistakenly downloaded the twrp zip for the 5T and I flashed it. This initially cause the device to brick but I got it back into fastboot and into recovery and thats when I flashed the OTHER twrp file above. After I did this, I could no longer get into recover and was stuck in fastboot only.
So you can see that I made multiple errrors and I am not sure which one lead to what. Thank goodness OnePlus is friendly to rooting so I could save the phone!

OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
Ah, I see. Looks like you flashed a kernel zip instead.

Im not a noob, but have been so out of practice with the latest Android ROMS and flashing and the changes in the partition arrangements. I managed to soft brick my phone as well and this post totally saved the day! Mauronofrio totally deserves a donation and I also gave one.
Thanks XDA! This place has saved me many times and helped me get the most of all my Android devices!

Hey guys. i am also no noob in flashing/rooting my devices.
Don thishundres of times.
Today my OP6T has shown an Magisk update (before it was 21.4 + Magisk Manager) and now it showed the popup to update -> done and error "bad image format" (i think for the kernel). Rebooted and now i am stuck in the same fastboot bootloop.
Tried to boot up TWRP with "fastboot boot tmrp.img" sadly it doesnt boot.
Any hints how i can recover my phone without wiping everything?
maybe @mauronofrio has an idea?
thx a lot

Other users facing the same issue with magisk 22, see here: https://forum.xda-developers.com/t/...oot-roms-for-oneplus-6t.3862516/post-84553217

Bootloader repeating constantly

Hello everyone. The think is that I have read a lot with similar things but I can't fix my problem. I wanted to flash TWRP and root my phone. First day Odin couldn't do it. I had that blue bar but no reaction. Finally Odin works I can flash recovery but that's it. When I'm trying to reset the device after one second Samsung logo disappearing and its starting to reset and reset and reset. Doesn't matter which buttons I'm holding except the ones for download mode.
Samsung galaxy s8 SM-G955F_2017-12-10_08 Exynos dreamltee
And that's all information about my phone because I can't even turn it on.
Is it bricked or I have a chance to solve it?

slageroth said:
Hello everyone. The think is that I have read a lot with similar things but I can't fix my problem. I wanted to flash TWRP and root my phone. First day Odin couldn't do it. I had that blue bar but no reaction. Finally Odin works I can flash recovery but that's it. When I'm trying to reset the device after one second Samsung logo disappearing and its starting to reset and reset and reset. Doesn't matter which buttons I'm holding except the ones for download mode.
Samsung galaxy s8 SM-G955F_2017-12-10_08 Exynos dreamltee
And that's all information about my phone because I can't even turn it on.
Is it bricked or I have a chance to solve it?
Click to expand...
Click to collapse
Ya really be messing up these expensive phones check your flash counter in download Mode if it's zero still you can get a warrant exchange if you had it less then a year from the way you talking it you can't access download Mode to flash stock firmware to regain functionality your phone just might be bricked sadly
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

PoochyX said:
Ya really be messing up these expensive phones check your flash counter in download Mode if it's zero still you can get a warrant exchange if you had it less then a year from the way you talking it you can't access download Mode to flash stock firmware to regain functionality your phone just might be bricked sadly
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
I was hoping anyway that I can do something. Counter going down. As I good remember I had two last attempts. I have a new notification "an error occurred while updating the device software. Use the emergency recovery function in the smart switch pc software. But I don't have recovery key for smart switch. I'm out of it. If you guys have any ideas, please share. I'm off.

slageroth said:
I was hoping anyway that I can do something. Counter going down. As I good remember I had two last attempts. I have a new notification "an error occurred while updating the device software. Use the emergency recovery function in the smart switch pc software. But I don't have recovery key for smart switch. I'm out of it. If you guys have any ideas, please share. I'm off.
Click to expand...
Click to collapse
Try to get your latest software up date from Sam mobile and if you can get into recovery mode wipe if not plug into download mode hope Odin accepts and pray for the best we all been there trying to modifiy are pulen and getting caught out there
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

PoochyX said:
Try to get your latest software up date from Sam mobile and if you can get into recovery mode wipe if not plug into download mode hope Odin accepts and pray for the best we all been there trying to modifiy are pulen and getting caught out there
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
I'll leave that for now. Need to wake up at morning. But the problem is anyway with that software. I don't know which ones latest. For now I can't even turt it of to read numbers. I don't know. My brain is not working now. I've tired with I thought latest software but bootloader failed so then I've tried separately with parts of it via odin but same thing has happened...

slageroth said:
I'll leave that for now. Need to wake up at morning. But the problem is anyway with that software. I don't know which ones latest. For now I can't even turt it of to read numbers. I don't know. My brain is not working now. I've tired with I thought latest software but bootloader failed so then I've tried separately with parts of it via odin but same thing has happened...
Click to expand...
Click to collapse
It happens tomorrow you will get your head together and save that phone
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

PoochyX said:
It happens tomorrow you will get your head together and save that phone
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
So basically my phote is sudden death so far because i didnt had a time to think about his ressurection. But what I have just realised... I was struggling with my device because of his not turning on i cant even read any numbers, version, nothing about him at all. But suddenly, I have remind that i was register on my samsung. So there should be everything about my phone.
Ok, can now someone advise me how should I act with that knowledge?
which number I might need to find which rom for example??

Ok, It looks like i have sorted it out. I have lost one hour of my life contacting samsung support team. it doesn't matter what i've asked her - the answer was "we not recomend rooting your device". Yes, indeed
Anyway - based on info I had, I've only remembered that is was sm-g950f dreamlte exynos. But that knowlegde was useless at this time. Basically I hade to read about CSC (Country Specific Code), and then I've just choose first from top. I have download SamFirm_v0.3.6 After filling that csc number and model of my device I just had to wait for firmware to download to my PC.
After that simpli extract to desired folder and we all know what to do next using Odin. Thanks for anyone who read and who's gonna read that post. I hope my lack of developing skills, will be helpfully for your futured adventures.
Thank you @PoochyX for your faith. you believed in me when even I've stop believe. Cheers bro
Thread can be closed now. Thank you.

Ok, It looks like i have sorted it out. I have lost one hour of my life contacting samsung support team. it doesn't matter what i've asked her - the answer was "we not recomend rooting your device". Yes, indeed
Anyway - based on info I had, I've only remembered that is was sm-g950f dreamlte exynos. But that knowlegde was useless at this time. Basically I hade to read about CSC (Country Specific Code), and then I've just choose first from top. I have download SamFirm_v0.3.6 After filling that csc number and model of my device I just had to wait for firmware to download to my PC.
After that simpli extract to desired folder and we all know what to do next using Odin. Thanks for anyone who read and who's gonna read that post. I hope my lack of developing skills, will be helpfully for your futured adventures.
Thank you @PoochyX for your faith. you believed in me when even I've stop believe. Cheers bro
Thread can be closed now. Thank you.

slageroth said:
So basically my phote is sudden death so far because i didnt had a time to think about his ressurection. But what I have just realised... I was struggling with my device because of his not turning on i cant even read any numbers, version, nothing about him at all. But suddenly, I have remind that i was register on my samsung. So there should be everything about my phone.
Ok, can now someone advise me how should I act with that knowledge?
which number I might need to find which rom for example??
Click to expand...
Click to collapse
You can use the imei number to identify the model number with Samsung find out which device model it is exactly and get the stock rom for it on sammobie however how if the phone doesn't turn on how you getting it into download mode to flash the stock rom with Odin
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Ohhhh you fixed it that's good to hear you got to be careful when you modify these phones the benefits are great if you do it right however if your not doing it properly you could mess up your device best of luck to you on your adventures of modifying your device

PoochyX said:
You can use the imei number to identify the model number with Samsung find out which device model it is exactly and get the stock rom for it on sammobie however how if the phone doesn't turn on how you getting it into download mode to flash the stock rom with Odin
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Ohhhh you fixed it that's good to hear you got to be careful when you modify these phones the benefits are great if you do it right however if your not doing it properly you could mess up your device best of luck to you on your adventures of modifying your device
Click to expand...
Click to collapse
It's all done mate, now just downloading million of app updates to get back to norm. It is still not rooted but I'm glad that I was able to fix it. Maybe I'm not posting much , but reading a lot of threads on XDA. It is the best developing school I've ever seen. And I'll try to root it tomorrow

slageroth said:
It's all done mate, now just downloading million of app updates to get back to norm. It is still not rooted but I'm glad that I was able to fix it. Maybe I'm not posting much , but reading a lot of threads on XDA. It is the best developing school I've ever seen. And I'll try to root it tomorrow
Click to expand...
Click to collapse
You have to get twrp installed first once you get that done you got to remove device encryption so you can access the data partition of twrp to be able to do a nanodroid then you flash magisk and you good to go... Then do a backup and flash xposed and you then open up your device to many more possibilities
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

Everything is ok now. I've spend 30 minutes maybe. My device is rooted thanks to @dr.ketan and his guide
https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/fix-data-mount-fix-s8-twrp-oreo-t3769254.
I've made backup efs and big asking for easy explanation what to do next. Do I need to uninstal magisk for example? disable some updates?
Please guys, I have never been so far, that I dont want to screw anything because of not turning something left or right.

slageroth said:
Everything is ok now. I've spend 30 minutes maybe. My device is rooted thanks to @dr.ketan and his guide
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254.
I've made backup efs and big asking for easy explanation what to do next. Do I need to uninstal magisk for example? disable some updates?
Please guys, I have never been so far, that I dont want to screw anything because of not turning something left or right.
Click to expand...
Click to collapse
Do you have twrp installed or you have a phone with a locked bootloader and you reached root threw flashing a modfied boot img threw Odin... (Last time I had a Dr Ketan rom was when I had my galaxy 7 edge)
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

Well, first I've flashed twrp via odin, I've reboot phone in recovery at first attempt what really surprised me. Then in recovery I've flashed pie root for OEM. And after that I've stuck for a while didn't known which option to choose. But I've just click Next, yes, next and five minutes later phone was rooted. I've check results with root checker but it wasn't rooted. Till next restart. And of course I've download and install magisk and flashed recovery. I've made all backups and titan backup just in case. And I've turned off Google play updates. I've just followed instructions carefully I'm still confused about, what next? I was tying to find what is after root. But I couldn't find anything bout that. All atemps finishing differently based on devices and software versions. No, I'm sure that I have did that root correctly, there was no leaf clover, you know ?
Sent from my G3311 using XDA Labs

slageroth said:
Well, first I've flashed twrp via odin, I've reboot phone in recovery at first attempt what really surprised me. Then in recovery I've flashed pie root for OEM. And after that I've stuck for a while didn't known which option to choose. But I've just click Next, yes, next and five minutes later phone was rooted. I've check results with root checker but it wasn't rooted. Till next restart. And of course I've download and install magisk and flashed recovery. I've made all backups and titan backup just in case. And I've turned off Google play updates. I've just followed instructions carefully I'm still confused about, what next? I was tying to find what is after root. But I couldn't find anything bout that. All atemps finishing differently based on devices and software versions. No, I'm sure that I have did that root correctly, there was no leaf clover, you know [emoji6]
Sent from my G3311 using XDA Labs
Click to expand...
Click to collapse
Well after rooting you start building up your daily driver the way you like it with the apps you want...
And the customizations yuu want for your phone.... You should install a adblocker for your phone so you won't get any ads since you rooted you can go with adaway use a host file and have ads blocked don't have to worry about a background service to block ads which utlizies memory that could be going somewhere else and battery life like non rooted people have to deal with... Even tho if your phone has alot or memory to spare you can use adguard which has a mode for root users also but it's always running in the background
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

Before root I couldn't wait when I'll start doing all those things, you know what I mean, that's what I call personalisation. Something totally by me. For me. But now I'm afraid to not broke it.
Sent from my G3311 using XDA Labs

slageroth said:
Before root I couldn't wait when I'll start doing all those things, you know what I mean, that's what I call personalisation. Something totally by me. For me. But now I'm afraid to not broke it.
Sent from my G3311 using XDA Labs
Click to expand...
Click to collapse
Just periodically do backups in twrp so if you mess up you can always revert the backup and you be exactly where you wore before the error so you wouldn't have to factory restore and if you do modifications to the system partition as well then in that case a rom reflash cause a factory restore doesn't fix system partition errors cause that partition is read only can only be accessed via root permissons or threw twrps file manager which you would have to mount system partition in twrp first then twrp file manager can access it
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]