After Bricking my Elephone P9000 because of SP_Flash_Tool crashing halfway through a recovery flash, i got the UMI Super as its a comparable spec
Neither can be unlocked via fastboot oem unlock, because when you try the UP Volume button doesn't seem to work allowing you to continue
i would much prefer this method as it takes away layers (imho) that aren't needed. Why use a GUI & scatter txt when you could load a recovery straight from fastboot? And then flash ROM's
Same here. When´ve been asked to confirm with Vol+ nutin happens...Vol- also. So I cant get OEM Unlock on my ZTE Blade L6... :/
From hat I've been reading it seems that doesn't work on mediatek processors. That's why we have to use that gui spft.
lexuz said:
From hat I've been reading it seems that doesn't work on mediatek processors. That's why we have to use that gui spft.
Click to expand...
Click to collapse
I have a Blu Studio Selfie 2 with the Mediatek MT6580 chip, and I'm running into the same problem where the Volume Up key doesn't work after the adb command "fastboot oem unlock." I haven't seen anything else on the internet about this being a problem for devices with the Mediatek chip, where did you see that?
More importantly, what do you mean by "we have to use that "gui spft"?
Spft is a tool that works with mediatek processors. I've flashed twrp with and it's really easy. Just search with Google and do research. ?
lexuz said:
Spft is a tool that works with mediatek processors.
Click to expand...
Click to collapse
Oh, okay... "spft" is "SP Flash Tool."
lexuz said:
Just search with Google and do research.
Click to expand...
Click to collapse
Thanks, but I have used Google search and xda search until my fingers are numb. Nothing seems to work with my BLU Studio Selfie 2, including SP Flash Tool. I only found ONE thread on this entire forum where someone else was asking how to root this same phone, and no one ever answered him. I posted a new thread recently, and no one answered me either. I have yet to find anyone claiming that they have positively been able to root this phone (with Android 6.0), and/or give steps to do it correctly.
lexuz said:
Spft is a tool that works with mediatek processors. I've flashed twrp with and it's really easy. Just search with Google and do research.
Click to expand...
Click to collapse
i can't seem to get my umi super into twrp, when i flash the recovery image with spft, it says download OK, but when i try to boot it with power and vol+ i get the umi welcome screen twice and the phone boots. if i try again it goes into a menu that says no command i really don't know what to do, any assistance will be appreciated.
leskivra said:
i can't seem to get my umi super into twrp, when i flash the recovery image with spft, it says download OK, but when i try to boot it with power and vol+ i get the umi welcome screen twice and the phone boots. if i try again it goes into a menu that says no command i really don't know what to do, any assistance will be appreciated.
Click to expand...
Click to collapse
Hello! What is your rom version??
Take a look at here .
noobp said:
Hello! What is your rom version??
Take a look at here .
Click to expand...
Click to collapse
my rom version is v7.01_20170308
thank you so much i will try it out now.
Related
fixed
curry67 said:
I was running cyanogenmod 10.1 M3 and i couldnt find a gapps file to get the google apps working so i decided to flash to the old version i was on 10.1 M1 i did it threw the update feature in the options of the phone no im stuck in the boot animation. for some reason im unable to boot into recovery when i do it is stuck at the google symbol.
Click to expand...
Click to collapse
You can boot any d*mn thing you please with
Code:
fastboot boot name-of-recovery-image-file.img
so long as you have an unlocked bootloader (and have properly operating drivers on Windoze PCs).
I have been using gapps 20130301-jb on CM10.1 nightlies. (It seems to often report "gapps has stopped", but to no ill effect).
If you have a PC with USB drivers installed it's a very good news for you. I think the best solution for you will be to flash with Nexus Root toolkit with the help of this toolkit you can flash from fast-boot mode.
As far as I know there are so many similar problems and solutions in this forum so if you searched a little you may have got an answer without creating a new thread. Try keeping that in mind for the next time.
==========================================
Please press the thanks button if you find this helpful.
ashik992 said:
If you have a PC with USB drivers installed it's a very good news for you. I think the best solution for you will be to flash with Nexus Root toolkit with the help of this toolkit you can flash from fast-boot mode.
As far as I know there are so many similar problems and solutions in this forum so if you searched a little you may have got an answer without creating a new thread. Try keeping that in mind for the next time.
==========================================
Please press the thanks button if you find this helpful.
Click to expand...
Click to collapse
well turns out i can get to recovery mode i wasnt able to last night it auto installed all the drivers as soon as i entered it
ok
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:
I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying
Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)
MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...
Have you tried flashing a stock ROM with the qcom download tool
abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.
Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.
Hey everyone, I'm currently on B29, non-rooted and locked bootloader.
I would like to root and make my up to stock 7.1.1. The issue I'm having, is that there is an absolute ton of conflicting info and ways to do things that I'm just not sure at all how to proceed.
What I've tried so far was starting with this guide: https://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234. But the tool from step three wouldn't download and the hosting site threw a ton of popups and redirects at me (yes, I have uBlock).
Then continuing through that same thread I found this tool https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 that is apparently safer, but I have no idea how to use it.
Then I started hearing about this EDL mode stuff https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 which I attempted to do when I tried the Axon7Toolkit yesterday, but my phone just wouldn't go into EDL mode (or I just had no idea how to tell if it was or not) and the MiFlash thing didn't do anything.
So my real questions are:
1: Which version of TWRP and SuperSU do I need?
2: How do I unlock the bootloader?
3: What steps should I take so that I eventually end up rooted on stock 7.1.1 (currently still on B29)?
Thanks!
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Choose an username... said:
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Click to expand...
Click to collapse
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
CookedBooks said:
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
Click to expand...
Click to collapse
No access with adb or fastboot in edl mode. It' strictly for use with low level tools like miflash. Your environment will make the difference. I couldn't get miflash on my main pc (win8/x64) to see the device. Likely an issue of drivers even through the proper driver is installed, and phone is showing up properly in device mgr. I used a spare pc with a relatively fresh win10/x64 install. Miflash saw the phone right away.
Also, for edl mode, my u model will just flash the led once then go blank.
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
gpz1100 said:
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
Click to expand...
Click to collapse
Okay thanks, I'll give it a go again. Would you be able to clarify which version of TWRP I should use? I'm thinking 3.0.2-0 but I've seen other guides mention different versions and other people say the wrong version is going to be a massive headache.
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
gpz1100 said:
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
Click to expand...
Click to collapse
Okay thanks. As for the rest, am I correct in my understanding that I need to:
First: Use Axon7tool to flash TWRP https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Second: Unlock bootloader
Third: flash the official 7.1.1
Hmm you could use a7tool to flash TWRP, then install the twrp app and upgrade to 3.1 or whatever, and then get to nougat after some backups. I'm not sure but I think tenfar's twrp FUBAR'd some partitions when you tried to backup
Okay thanks. I think I'll give it a rest for today, I've been scouring threads since yesterday trying to get a clear picture of what to do. I think I'll spend the week researching further and give it a go next weekend.
I just miss having AdAway and CF Lumen installed on my phone. And I really want to give Substratum a try.
Thanks for all the tips and info!
Hang in there. You are on the right track. The edl thing can take a few attempts to get recognized.
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
lafester said:
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
Click to expand...
Click to collapse
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
If you have to use axon7tool then you might find this useful
https://forum.xda-developers.com/showpost.php?p=71206394
But I think that the US version has a different way to root and stuff, so i wouldn't be able to help...
bkores said:
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
Click to expand...
Click to collapse
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
CookedBooks said:
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
Click to expand...
Click to collapse
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
bkores said:
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
Click to expand...
Click to collapse
Okay, I just walked into work though. When I get home and settled this evening I'll give it a whirl and let you know what happens.
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
bkores said:
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
Click to expand...
Click to collapse
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
lafester said:
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
Click to expand...
Click to collapse
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
bkores said:
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
Click to expand...
Click to collapse
I used the toolkit to flash b15 full with miflash and it worked fine, however I already had miflash installed.
I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.
Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not
Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.
Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
AOnePlus6TDestroyer said:
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
Click to expand...
Click to collapse
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
rogerrulez said:
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
Click to expand...
Click to collapse
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Only option now is to use msm tool again and hopefully get something working
Even with the bootloader locked you still should be able to boot the recocery image.
I have the 6T and 7T Pro. When I messed up my 6T my only hope was the msmdownloadtool. But make sure it's the right one.
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Brettroth said:
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Click to expand...
Click to collapse
Are there more suitable tools for fixing a broken recovery mode? It did successfully do that.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
How?
rogerrulez said:
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Click to expand...
Click to collapse
Thank you! And yes, I tried that command but it is probably unset in the developer options (which I cannot reach, as Android isn't working anymore). I guess I'm using the incorrect version - how do you identify the correct one? I think I've used both the T-Mobile one and the other. I don't think the phone is T-Mobile, but I'm not sure how to identify whether it is or not.
It is very easy to convert a t-mobile variant to the international version. If you bought the phone used you would not know. One tell tale sign could be if you sim card holder supports either one or 2 sims. But that's not a sure way either because you can buy a replacement sim card holder. The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
As for the msm tool you would needd a modified version of that tool. You first use it to downgrade to Android 9. Then you have to upgrade that verion of android 9 to a slightly higher version before you are able to fully upgrade feely to 10 than 11 if you wanted.
If you have the international version pretty much and version of the msm tool would work but a modified version would be best.
However, the first step is to find out which variant you have.
When you used the msmdownload tool which version did you use, and did it finish the job ?
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
When I bricked mine I thought it was gone forever, I spent several days working on it but I was able to restore it. But I would never use the ubuntu rom on any phone that I care for.
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Brettroth said:
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Click to expand...
Click to collapse
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
rogerrulez said:
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
Click to expand...
Click to collapse
That's what I meant. Flash a ROM from twrp. Ok so if that works this guy can fix everything from there. Gonna be a hassle tho. Instead of rebooting to recovery I think you would have to shut off phone and fastboot boot back into twrp to change slots right?
Somehow I feel like that won't work but I'm not locking my bootloader to test it
rogerrulez said:
The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
Click to expand...
Click to collapse
I'm afraid I can't' find it... It is dual-sim though.
rogerrulez said:
When you used the msmdownload tool which version did you use, and did it finish the job ?
Click to expand...
Click to collapse
I used a few - both T-Mobile and not. They all succeeded with (seemingly) no error, but didn't fix the bootloop.
rogerrulez said:
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
Click to expand...
Click to collapse
I see, but won't that need me to be in Android to be able to run the software?
rogerrulez said:
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
Click to expand...
Click to collapse
Yup, fastboot and recovery mode work fine. The bootloader is locked though, else installing TWRP, etc. would be easy.
rogerrulez said:
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
Click to expand...
Click to collapse
Yeah...
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
It doesn't do it automatically. Is there another way to boot it?
Brettroth said:
Somehow I feel like that won't work but I'm not locking my bootloader to test it
Click to expand...
Click to collapse
As far as I can tell there's no way to flash TWRP without unlocking the bootloader. And there doesn't seem to be any way to do that without getting into Android. And I can't get into Android...
Someone else suggested using this tool (https://github.com/bkerler/edl) as a last-ditch attempt. I'm going to give it a try and hope for the best!
Thank you both for your suggestions.