Related
Hello,
I totally screwed up my phone. I recently unlocked the OEM on my phone in order to download TWRP and to download Tomatot Debloater. Long story short, EVERYTHING is gone and not working. I tried to do a factory reset but it didnt work. Can anybody please let me know what are my options to restore my phone back to normal factory settings?
Many Thanks,
Sam
1. Install local update
2. Reboot your phone
3. Factory reset in settings your phone
4. Lock OEM etc
Could you be more specific? Im very new to this. How do you install the local update?
samdaman91 said:
Could you be more specific? Im very new to this. How do you install the local update?
Click to expand...
Click to collapse
Download the full zip for your Model/OOS version and copy it to your internal storage where all the folders are Android, Music etc..
Settings > System > System Updates > Click The Settings Cog (Top Right) > Local Upgrade > Select The Zip And Install It (When It's Finished Installing Reboot).
samdaman91 said:
Hello,
I totally screwed up my phone. I recently unlocked the OEM on my phone in order to download TWRP and to download Tomatot Debloater. Long story short, EVERYTHING is gone and not working. I tried to do a factory reset but it didnt work. Can anybody please let me know what are my options to restore my phone back to normal factory settings?
Many Thanks,
Sam
Click to expand...
Click to collapse
You need to give us much more info:
What will your phone do at the moment? i.e. Can you only get fastboot, recovery or will it boot to the rom but not accept pin/pattern?
Which recovery do you have available to use at the moment? Stock or TWRP?
Have you tried changing the active slot using fastboot? i.e. fastboot set_active a or fastboot set_active b then restarted the phone?
djsubterrain said:
You need to give us much more info:
What will your phone do at the moment? i.e. Can you only get fastboot, recovery or will it boot to the rom but not accept pin/pattern?
Which recovery do you have available to use at the moment? Stock or TWRP?
Have you tried changing the active slot using fastboot? i.e. fastboot set_active a or fastboot set_active b then restarted the phone?
Click to expand...
Click to collapse
1. I can still access fastboot mode. It is still unlocked. When i go to regular mode i can still use my PIN to go into phone, but everything is gone.
2. Stock. Looks like i deleted TWRP by trying to factory reset it.
3. How do i do that? Do i have to use my command prompt from my PC?
liam_davenport said:
Download the full zip for your Model/OOS version and copy it to your internal storage where all the folders are Android, Music etc..
Settings > System > System Updates > Click The Settings Cog (Top Right) > Local Upgrade > Select The Zip And Install It (When It's Finished Installing Reboot).
Click to expand...
Click to collapse
Will try this by downloading the oxygen OS zip file from the oneplus pro site. Ill put the file into my computer then copy it to my phone. Maybe it will work.
1) Download an earlier Fastboot update from this thread
2) Unzip the file
3) Reboot phone into bootloader
4) Click on the "flash-all" bat file and wait for the operation to finish
5) Reboot into bootloader when the phone itself reboots
6) Unzip the "images" file
7) Flash boot into both partitions via Fastboot
8) Relock the bootloader
9) Let the phone boot normally this time
10) Once setup is complete and it's confirmed that the phone is 100% stock and OEM Unlock is deselected in Developer Settings, update via OTA normally
blackknightavalon said:
1) Download an earlier Fastboot update from this thread
2) Unzip the file
3) Reboot phone into bootloader
4) Click on the "flash-all" bat file and wait for the operation to finish
5) Reboot into bootloader when the phone itself reboots
6) Unzip the "images" file
7) Flash boot into both partitions via Fastboot
8) Relock the bootloader
9) Let the phone boot normally this time
10) Once setup is complete and it's confirmed that the phone is 100% stock and OEM Unlock is deselected in Developer Settings, update via OTA normally
Click to expand...
Click to collapse
Thank you. Sounds complex. Is it ok if you can provide me more specific guidance on how to do this? I am going to try the other options above first so ill let you know if those work beforehand.
samdaman91 said:
Thank you. Sounds complex. Is it ok if you can provide me more specific guidance on how to do this? I am going to try the other options above first so ill let you know if those work beforehand.
Click to expand...
Click to collapse
There's not much more we could tell you, those instructions already provide a step-by-step guide on how to restore the default partitions to the phone. After you do that then change the "Unlock bootloader" option in developer settings that you changed originally and run "oem lock" from the console the same way you unlocked the bootloader originally. That's only if you want the phone back into the state you received it in,
djsubterrain said:
There's not much more we could tell you, those instructions already provide a step-by-step guide on how to restore the default partitions to the phone. After you do that then change the "Unlock bootloader" option in developer settings that you changed originally and run "oem lock" from the console the same way you unlocked the bootloader originally. That's only if you want the phone back into the state you received it in,
Click to expand...
Click to collapse
The only step I think I missed is relocking the bootloader, but Google can handle that
djsubterrain said:
There's not much more we could tell you, those instructions already provide a step-by-step guide on how to restore the default partitions to the phone. After you do that then change the "Unlock bootloader" option in developer settings that you changed originally and run "oem lock" from the console the same way you unlocked the bootloader originally. That's only if you want the phone back into the state you received it in,
Click to expand...
Click to collapse
blackknightavalon said:
1) Download an earlier Fastboot update from this thread
2) Unzip the file
3) Reboot phone into bootloader
4) Click on the "flash-all" bat file and wait for the operation to finish
5) Reboot into bootloader when the phone itself reboots
6) Unzip the "images" file
7) Flash boot into both partitions via Fastboot
8) Relock the bootloader
9) Let the phone boot normally this time
10) Once setup is complete and it's confirmed that the phone is 100% stock and OEM Unlock is deselected in Developer Settings, update via OTA normally
Click to expand...
Click to collapse
Thanks it worked. But i didnt have to do steps 6 and 7. I got it working without the steps. Am i potentially missing something or is it fine?
Updated my OP7 pro to android 10 few days ago.
Yesterday, I turned off my device. But now when I’m trying to turn it on, it stuck in bootloop.
I tried clearing cache from recovery mode, it’s still In bootloop.
Devices is non rooted & bootloader is locked.
If any other solution except wiping data. Please let me know.
Update :- Tried "Reset System Settings"
"wipe cache"
"Erase Everything(music, pics, etc)"
all 3 options from recovery mode, still it's not turning on. Seems like software damaged. Any way to flash stock firmware on locked bootloader?
Can you turn the device off? If yes, when powered off, boot into qualcomm download mode and use MSM Download Tool to restore the device:
''With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.''
Right after the step above, plug the usb cable in.
You can download the tool here. Make sure you download the correct one:
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Arsh1219 said:
Any way to flash stock firmware on locked bootloader?
Click to expand...
Click to collapse
Yes, there is. It does require having fastboot setup, and having at least a basic knowledge of how to use fastboot: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Or I think you can try to switch slots A/B and see if it can boot off the currently inactive slot. Again, this requires at least a bit of working knowledge of fastboot commands:
fastboot set_active b
(or active a, depending on which slot is currently active)
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
No need double reboot
Os_Herdz said:
No need double reboot
Click to expand...
Click to collapse
It is not necessary, but a preventative measure. I've had instances where I hadn't rebooted twice and the phone booted into erase mode. This is a guide for people who want to make sure they won't lose data.
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
RFD80M-75679 said:
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
Click to expand...
Click to collapse
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
softgadget said:
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
Click to expand...
Click to collapse
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
RFD80M-75679 said:
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
Click to expand...
Click to collapse
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
softgadget said:
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
Click to expand...
Click to collapse
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
RFD80M-75679 said:
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
Click to expand...
Click to collapse
Oh. OK then.thank you
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
popadic022 said:
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
Click to expand...
Click to collapse
You can unlock with the same method. But I believe you will flash a zip from TWRP to fix SIM cards and that will break your phone if you lock the bootloader. So after fixing the SIM cards, you need to leave the phone unlocked, otherwise phone will be bricked. If you want to get rid of the ugly splash screen, you can flash a custom splash you can find in the forum.
marstonpear said:
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
Click to expand...
Click to collapse
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
gusbalaa said:
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
Click to expand...
Click to collapse
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
RFD80M-75679 said:
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
Click to expand...
Click to collapse
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
gusbalaa said:
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
Click to expand...
Click to collapse
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
marstonpear said:
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
Click to expand...
Click to collapse
Thanks, already done it.
Flashed TWRP & Magisk without losing any data.
marstonpear said:
Hi,
Click to expand...
Click to collapse
will this metode also work on mi10
-fluffy- said:
will this metode also work on mi10
Click to expand...
Click to collapse
I'm not sure but probably not. Because Mi 10 is a MIUI device and this is an Android One. Still you gotta try to make sure, but the risk is all yours. Cheers.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
Wowwww! Thank you very much, time ago I've unlocked the bootloader without losing any data
That's a very good solution
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.
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Try fastboot getvar all then do fastboot set_active to either a or b depending on which partion you are on you want to change it also pretty sure USB debugging doesn't matter in bootloader you can also try fastboot oem unlock to unlock bootloader to boot twrp unless you updated to oos twrp doesn't work yet
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
JonasHS said:
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
Click to expand...
Click to collapse
With MSM he will get everything wiped on his device. This is not he is intending to do.
AK138 said:
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Click to expand...
Click to collapse
Run fastboot flash recovery twrp.img ... And then fastboot reboot recovery or choose recovery on your phone.
Sometimes holding volume up and power to do a soft reset boots back into system worth a try.