Related
Hi there, I unlocked the bootloader but can not flash the recovery via fastboot.. because somehow the ADB on my device is brocken, there is no way for me to excude adb command because it's not recongnized by windows, I tried to install different Android ADB drivers, but no lock none of them are working
Also, after unlocking the bootloader, MTP file transfer under windows also not possible anymore, I can choose MTP but the phone stays in charge only
update:
there is a way for TWRP user to flash Axon10 Fastboot Enabler.zip to get the ABL with fastboot back, but my big big problem: I only unlocked Bootloader but have no TWRP installed, now I can not install any img file due to lack of fastboot...
SOLUTION: just find some FULL EDL Package with pre root and flash it with EDL Tool
del
37_ said:
del
Click to expand...
Click to collapse
Hello I am standing as your position.
I upgraded to android 10 version 2.5 via SD card way, lost way to fastboot... and cannot get twmp back.....
What EDL version you flashed? do you know how to enter fastboot in case version 2.5 or 2.3??
Sincerely
Hi, I have trouble with flashing custom rom to my Realme C2 phone.
Last night i unlocked the bootloader and tried to flash custom rom to my phone, but i really can't get into twrp recovery or fastboot mode. (The screen stuck on fastboot_unlock_verify ok). Then i tried to relock the bootloader and decided to give up and go back to normal. When i entered : fastboot flashing lock : command in terminal (im using mac os), it kept rebooting and says the current boot image(boot/recovery) have been destroyed and can not boot.
Right now i can't boot into recovery mode or fastboot mode, any chance that i can get my phone working again? Is it because that my phone is carrier locked, so they locked my fastboot option? but i got the bootloader unlocked.
Big thanks for every reply and trying to help, I really appreciate it!!
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
jwoegerbauer said:
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
Click to expand...
Click to collapse
Sorry, It was in terminal not Adb, but fixed! Anyway that i can get my phone up running again?
To me it seems your installation of TWRP - what amonng other things modifies Android's boot.img and also removes device's Stock Recovery - miserably failed for whatever reason.
You can try to bring back phone's Stock Recovery ( overwrite TWRP ) by means of SP Flash Tool.
jwoegerbauer said:
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
Click to expand...
Click to collapse
jwoegerbauer said:
To me it seems your installation of TWRP - what amonng other things modifies Android's boot.img and also removes device's Stock Recovery - miserably failed for whatever reason.
You can try to bring back phone's Stock Recovery ( overwrite TWRP ) by means of SP Flash Tool.
Click to expand...
Click to collapse
I tried to follow the guide, but Realme C2 firmware doesn't have scatter file to let me flash the stock firmware
Wondering why you haven't created the Scatter file before starting to hack/mod the phone?
Is there any way to get root/custom recovery/custom roms on the A502DL or A501DL? If so, how?
lehmancurtis said:
Use the boot mode tool from here for the a501dl. It definitely is unlockable! You can grab the TWRP.img I compiled for the a501dl from this link.
Click to expand...
Click to collapse
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
lmgnsa said:
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
Click to expand...
Click to collapse
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
fliproc said:
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
Click to expand...
Click to collapse
Use a tool that controls bootmode. Mtk-mode-selector
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Please help, it says "waiting port" forever
Thanks for the reply! I tried this tool, along with adb commands, etc., and I just can't even get fastboot. This would be an AWESOME phone, if not for this dumb crap!! The phone I had before this one is a Z717VL, and it sucks as well. They are both Tracfone phones that were given to me by my wife. I think I'll just get a Galaxy S8 or so and just root it instead. All other phones that I had on Verizon in the past have been super easy... just a One-Click-Root. Thanks everyone for your time and help!
lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Are you sure the method you thought of works? The bootmode tool you linked cannot get the A501DL to fastboot mode, it just says "waiting port" forever.
@lehmancurtis I feel like you might be lying about whether or not your method works, as the boot mode tool does not work. @lmgnsa did it work for you?
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
williamhancock328` said:
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
Click to expand...
Click to collapse
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
mickeybeats said:
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
Click to expand...
Click to collapse
I have already installed the MTK VCOM drivers multiple times, I don't know why it still doesn't work.
T
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
lmgnsa said:
To keep recovery from being replace several files need to be disable (various approaches are effective i.e. removed, replace, or renamed). Magisk usually handles this task, but sometimes there are exceptions. But, you need to address that before flashing gsi's for multiple reason and none are fun to deal with. Yes, this is A only and does not use A/B update method (at least not entirely as a few partitions are making use of the A/B partition labels). I've not been doing much with this particular device since mine was cracked and the usb port messed up when I got it, so nature took its course before I was able to achieve a fully stable custom setup.
Click to expand...
Click to collapse
sj78 said:
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Click to expand...
Click to collapse
It sometime takes a few tries to get the phone and tool to do what its supposed to, but if you get the waiting message start over until the program reboots the device. It will work, it's just not a perfect process.
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
You need to modify a few files. It's almost just like the 5059 devices and you can look up the 5041c thread to see what needs edited. Use the fstab.mt6739 from the 5041c.
Here's the tool. I think some of the links to it got messed up. Make sure you turn on developer options and check that oem unlock is ticked as well as adb usb options. Once in fastboot, issue the following
Code:
fastboot oem unlock-go
Follow the instructions on the device. Then boot into system and complete setup so that you can turn on developer options again since your device was just reset. Boot to fastboot once again and issue these.
Code:
fastboot flash recovery ./recovery.img
Code:
fastboot oem reboot-recovery
That should be the custom recovery you just installed. It will be replace on reboot if steps are not taken. I was in the process of working this issue when my beat up a501dl succumbed to its varied and multiple impact injuries. If I can find the time to repair it I will finish where I left off, but in the mean time I will help as much as I can.
Regular drivers are built into the phone but you may need vcom drivers. I'm going to attempt to repair mine enough to reset and flash again. I'll probably have to nav my screen via commands, but I will attempt to capture the process and show you.
I've got a A501DL, I enabled usb debugging and oem unlock, seems like the A501DL in fastboot does not talk with the pc, i've installed so many driver things its crazy butat fastboot when typing fastboot reboot bootloader, it reboots the phone but it skips fastboot and turns on to my home screen, I used volume up and power, I get in fast boot butthe device isnt being detected by windows 10 64 bit. Also in fast boot there is only
reboot system now
wipe data/factory reset
wipe cache partition
power off
im going nut that fastboot isnt working with this device.
I plan on developing a TWRP recovery for my phone (which doesn't have one ATM) In order to do this, I need to run tests on my device to see if it will work or not. I know flashing a custom recovery that isnt compatible/is corrupted, etc can brick your phone but would simply booting a custom recovery cause any issues? So I would just run fastboot boot twrp.img, Would that brick my phone if it doesn't work or would it just go back into fastboot mode/reboot itself? I'm pretty sure it wouldn't cause a brick but I'm a bit of a newbie so I need some confirmation.
Drysauce said:
I plan on developing a TWRP recovery for my phone (which doesn't have one ATM) In order to do this, I need to run tests on my device to see if it will work or not. I know flashing a custom recovery that isnt compatible/is corrupted, etc can brick your phone but would simply booting a custom recovery cause any issues? So I would just run fastboot boot twrp.img, Would that brick my phone if it doesn't work or would it just go back into fastboot mode/reboot itself? I'm pretty sure it wouldn't cause a brick but I'm a bit of a newbie so I need some confirmation.
Click to expand...
Click to collapse
Most likely not UNLESS u modify your system using the recovery
areallydumbperson said:
Most likely not UNLESS u modify your system using the recovery
Click to expand...
Click to collapse
Well I dont plan on modifying my system immediately after I get a good boot. But I plan on seeing what works and what doesn't and going from there. Though "most likely not" isn't enough for me. I may just run some tests on my old xiaomi phone and try to boot a samsung exynos TWRP recovery on it and other things, guaranteed failure, but will see if I can manage to brick it, just by booting.
Each recovery, so also a custom recovery like TWRP, simply is menu you can select some actions that operate on Android OS. All these actions internally are based on ADB and / or Fastboot commands. Means you can achieve same results when directly running ADB and / or Fastboot commands.
jwoegerbauer said:
Each recovery, so also a custom recovery like TWRP, simply is menu you can select some actions that operate on Android OS. All these actions internally are based on ADB and / or Fastboot commands. Means you can achieve same results when directly running ADB and / or Fastboot commands.
Click to expand...
Click to collapse
Is that so, I never knew that. But what about flashing zip files? like for example if I were to flash a custom recovery, or Gapps, etc. how would one go about doing this through fastboot, where you cannot flash zips.
A lot if not all stock recoveries need a signed zip package if you want to flash
Drysauce said:
Is that so, I never knew that. But what about flashing zip files? like for example if I were to flash a custom recovery, or Gapps, etc. how would one go about doing this through fastboot, where you cannot flash zips.
Click to expand...
Click to collapse
Flashing ZIPs is done via ADB, not via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload LINEAGEOS.ZIP
adb reboot
jwoegerbauer said:
Flashing ZIPs is done via ADB, not via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload LINEAGEOS.ZIP
adb reboot
Click to expand...
Click to collapse
Thank you!
jwoegerbauer said:
Flashing ZIPs is done via ADB, not via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload LINEAGEOS.ZIP
adb reboot
Click to expand...
Click to collapse
But don't stock recoveries only allow zips made officially by the manufacturer to be flashed??
AFAIK Android's Stock Recovery only allows to flash Update-ZIPs, not any ZIPs. Update-ZIPs by nature are provided by OEM / carrier. But I may err, as always ...
areallydumbperson said:
Most likely not UNLESS u modify your system using the recovery
Click to expand...
Click to collapse
If I do boot into the custom recovery, is there still a chance that my os will be corrupted / phone will be (soft)bricked?
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.