[HELP] MSMTool for OnePlus 7T Pro HD1913? - OnePlus 7T Pro (Regular & McLaren) Q & A

Hey, so my device is unanble to boot and the only solution possible is using MSM but I didn´t find a version for 7T Pro only 7Pro, 7T and 8Pro.
Is there a possibilty to use the MSM tool with the software provided by oneplus website or is there are MSMTool for 7T Pro. I read many forums but didn´t find something there. Please help if you can

nikiwithstyle said:
Hey, so my device is unanble to boot and the only solution possible is using MSM but I didn´t find a version for 7T Pro only 7Pro, 7T and 8Pro.
Is there a possibilty to use the MSM tool with the software provided by oneplus website or is there are MSMTool for 7T Pro. I read many forums but didn´t find something there. Please help if you can
Click to expand...
Click to collapse
This thread should help. Just use the BA version if you need the EU firmware. I used it on my 7T Pro HD1910 (AA firmware) the other day downgrading from OOS 11 and it worked fine.

Hello I m Try TO Flash But Show Error
any have solution please suggestion
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

___kuldeepsharma said:
Hello I m Try TO Flash But Show Error
any have solution please suggestion
View attachment 5361211
Click to expand...
Click to collapse
Entering EDL mode can be tricky if you've never done it. Two ways that I know of:
First using button combo:
1. Power off phone with USB cable disconnected from PC
2. Hold Power UP + Power Down and plug in USB cable
3. Nothing shows up on the phone screen, but the MSM Downloader's Status of Connection should change to "CONNECTED". This is also assuming you have the correct drivers installed.
3b. EDL mode is short lived, so if you don't press Start in time, you will miss it.
Second using adb:
adb reboot edl
Personally, I've only used the button combo and it works.

Hw4ng3r said:
Entering EDL mode can be tricky if you've never done it. Two ways that I know of:
First using button combo:
1. Power off phone with USB cable disconnected from PC
2. Hold Power UP + Power Down and plug in USB cable
3. Nothing shows up on the phone screen, but the MSM Downloader's Status of Connection should change to "CONNECTED". This is also assuming you have the correct drivers installed.
3b. EDL mode is short lived, so if you don't press Start in time, you will miss it.
Second using adb:
adb reboot edl
Personally, I've only used the button combo and it works.
Click to expand...
Click to collapse
Thank you very much for telling me but I have lived everything still it has been there and this is not an Indian phone this is a dense country phone is there any other solution for this
i think the file is wrong can you give me the correct file

___kuldeepsharma said:
Thank you very much for telling me but I have lived everything still it has been there and this is not an Indian phone this is a dense country phone is there any other solution for this
i think the file is wrong can you give me the correct file
Click to expand...
Click to collapse
MSM downloader is in the link in second post of this thread.

Related

My H96 Max X2 (S905X2) cannot be upgraded, how can i unbrick?

After some months of use , one day i turned on my android box and suddenly after loading it will give a black screen and there is nothing else after that, i tried to reinstall firmware through a SD card but it stuck in the installing/loading with a "x" on the android green man.
Now i would like to ask for a help from someone that is familiar with unbricking, i'll provide pictures of my H96 so you can see it from inside and tell me HOW CAN I SHORT CUT or whatever i need to do. (because i saw different hardware and different devices)
May i use 9.0 android version?
This is my android box:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope the pictures of my android box will help you so you can guide me in the process of unbricking and about the short cut where should i press.
Short the following 2 pins. Good Luck.
ath156 said:
Short the following 2 pins. Good Luck.
Click to expand...
Click to collapse
I got a partition error... i tried almost every firmware... what could be the problem?
argosc said:
I got a partition error... i tried almost every firmware... what could be the problem?
Click to expand...
Click to collapse
Download the correct firmware from here:https://www.h96tvbox.com/content/6-Firmware-upgrade
Probably you have LPDDR3 memory so ONLY this firmware is suitable for your TVbox. If you had 8DDR3 type of memory you could use both firmwares (those for 8DDR3 & LPDDR3).
Also please describe how you exactly are using USB Burning Tool and the short pins method (the whole sequence).
ath156 said:
Download the correct firmware from here:https://www.h96tvbox.com/content/6-Firmware-upgrade
Probably you have LPDDR3 memory so ONLY this firmware is suitable for your TVbox. If you had 8DDR3 type of memory you could use both firmwares (those for 8DDR3 & LPDDR3).
Also please describe how you exactly are using USB Burning Tool and the short pins method (the whole sequence).
Click to expand...
Click to collapse
Actually i don't use short pins, because when i connect my h96 to the PC via the USB cable it automatically gives a connection success, so i just use some firmware, i used the firmware from the official site, but still doesnt work , it always get stuck at 9%.
argosc said:
Actually i don't use short pins, because when i connect my h96 to the PC via the USB cable it automatically gives a connection success, so i just use some firmware, i used the firmware from the official site, but still doesnt work , it always get stuck at 9%.
View attachment 5246915
Click to expand...
Click to collapse
1. Did you try the official Android 9.0 version (stock firmware) for the LPDDR3 memory as I told you above?
It is this version https://drive.google.com/drive/folders/16qCsIFbGDSgopwJ3zEBQ4iLC_wLEbLVV
So did you try this version?
2. If after trying number (1) your TVbox is not brought to life, this means that it is hard bricked and your best option is the "short pin" method.
ath156 said:
1. Did you try the official Android 9.0 version (stock firmware) for the LPDDR3 memory as I told you above?
It is this version https://drive.google.com/drive/folders/16qCsIFbGDSgopwJ3zEBQ4iLC_wLEbLVV
So did you try this version?
2. If after trying number (1) your TVbox is not brought to life, this means that it is hard bricked and your best option is the "short pin" method.
Click to expand...
Click to collapse
I have the same problem and the same box.... did you manage to solve it?
the stock firmware links are down

TWRP on Moto G7 XT1965-T Plus Issue | Dying at Boot Image

The device is a Moto G7 Plus with a freshly unlocked bootloader and running on off of a "fastboot boot twrp-3.6.0_9-0-lake.img" which appears to be the latest from twrp.me
See screenshot image and recovery.log attached
Any help would be greatly appreciated as I've not been able to come up with a solution.
Thank you!
Samson
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could it be an issue with the new twrp build? Have you tried booting and flashing the older 3.5.2 version?
Teo S. said:
Could it be an issue with the new twrp build? Have you tried booting and flashing the older 3.5.2 version?
Click to expand...
Click to collapse
Hey Teo, oddly enough, TWRP flashed successfully despite the error message. I guess the error message has something to do with A/B slot conditions which I'm still not totally understanding. I know that the Moto G7 (not the plus) requires some copy-partitions-AB.zip according to an install guide that I'm using. Again, is good to go, unfortunately I hard bricked after flashing Lineage 18. I was told that I needed latest OTA for the device which I thought was already on there. I connected the device to wifi and tried to run update just before flashing TWRP but updates failed to download. So for now, I'm just another "Brick in the Wall" lol. Noob level 5000, sucks.
The G7 plus also requires a copy-partiosions-AB.zip to prevent bricking from different software on the 2 slots. It can be found somewhere here on the forum. Also there is a way to flash the latest OTA manually via fastboot. A guide can also be found somewhere here on the forum. You can download the OTA images from lolinet (https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/).
Teo S. said:
The G7 plus also requires a copy-partiosions-AB.zip to prevent bricking from different software on the 2 slots. It can be found somewhere here on the forum. Also there is a way to flash the latest OTA manually via fastboot. A guide can also be found somewhere here on the forum. You can download the OTA images from lolinet (https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/).
Click to expand...
Click to collapse
Thanks again Teo. Question : is there a way to unbrick the device if it won't even power up? I've tried every key combo that I could find but can't even get a charging status when I connect it to power. I think it's now certifiably hard bricked. Dunno
TallDarknSamson said:
Thanks again Teo. Question : is there a way to unbrick the device if it won't even power up? I've tried every key combo that I could find but can't even get a charging status when I connect it to power. I think it's now certifiably hard bricked. Dunno
Click to expand...
Click to collapse
Are you using the cable/charger it came with?
Have you tested with a different cable?
jockovonred said:
Are you using the cable/charger it came with?
Have you tested with a different cable?
Click to expand...
Click to collapse
factory cable / charger only, no other cables. I sent the device to a dev for kicks, see if he can un-brick it. Not holding my breath though. Stat tuned . .

Question EDL mode test points?

Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solved without using EDL test points. ​see The Solution below.​
BIG Thanks goes to @NOSS8 for his help.
ramiro2016 said:
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
Click to expand...
Click to collapse
this phone did not need edl or test point.
https://forum.xda-developers.com/t/...-after-flashing-gsi-rom.4448229/post-86995731
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
ramiro2016 said:
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
Click to expand...
Click to collapse
https://xiaomitools.com/sp-flash-tool-en/
there is also this tool (new not tested).
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
https://gearupwindows.com/how-to-disable-driver-signature-enforcement-on-windows-11-10/
check for program update
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
ramiro2016 said:
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
Click to expand...
Click to collapse
This is not the latest version(V52).
https://mega.nz/file/H0MW3BST#PfzzmSwbncT5aV7A1ZhWztQonLj4CgJLDHbXoRtCu54
Maybe useful
https://www.bypassfrpfiles.com/2021...h_Secure_Boot_Disable_Tool_V52_Latest_Version
BTW: I don't have and would never have a xiaomi Mediatek and therefore never use these tools for Mediatek, that's why I can help you for the links but not for the use of these tools.
If it still doesn't work post the latest log.
Unfortunately, even the latest version v52 doesn't work, but this tool helped me solve the problem.
https://github.com/bkerler/mtkclient (You need to follow the readme document).
I've used the mtk_gui, and after it got connected, I sent my original firmware boot.img that is currently installed on my mobile after renaming it to boot.bin to the device partitions boot_a and boot_b
Rebooting the device got me the original recovery mode and the fastboot mode.
Then I used the MiFlash tool to flash my phone using flash_all.bat
Every thing is working fine know.
BIIIIIIIIIIIG Thanks goes to @NOSS8 for helping me all the way to the solution .​

How To Guide How to restore and unbrick Pixel 6 Oriele or Pixel 6 Pro "Raven" ? plz help me

After I updated pixel 6 to android 13,​phone doesn't work became bricked and I can't fix it because when I plug it into my computer and see the device manager in windows,​but it is not detected by `adb devices` or `fastboot devices`.​I see it detected in seconds and disappear by watching device manager as a " USB serial port device (COM 3)" in windows 11​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in windows 7 & ubuntu detected as pixel CDC- ACM (Pixel ROM Recovery )device because devices manager in win7 can't find any driver compatible so it detected as itself in "Other devices"​
in VM box :
while I hold down the power button so I can't fix it,​how to restore my phone and flash it in this mode I think this mode is EDL​I tried to boot in bootloader by pressing press power + volume down and power + volume up and all together but nothing work , the phone is dead​I have tried to fix by this post but unfortunately it doesn't work https://forum.xda-developers.com/t/guide-unbrick-pixel-6-oriele-or-pixel-6-pro-raven.4441245/​I have escalated this issue in google tracker since 2 months but i got NO ANSWER and NO HELP https://issuetracker.google.com/issues/243636259​
is anyone have any idea to fix my ? i will appreciate any try PLZ help me
Very likely you can't.
From your description, when you flashed it, A13 was updated only on one slot with the new bootloader, while the second slot is still stuck with the previous bootloader. During the flashing (how did you flash?), something went wrong, so the Pixel wanted to boot from the second slot with the "old" bootloader and the "Anti-Roll-Back" kicked in.
RMA and hopefully get an exchange
Cheers
Follow this steps and let us know if it worked for you
1. Unplug the cable from your phone
2. Press and hold for at least 15 seconds the power button then release
3. Connect a cable from your pc to your phone but you need to press volume up and hold it until you connect the cable, once connected release the button your phone shall turn on fastboot mode, it it worked just proceeded and flash a13 again, just download it from it's official source
14. Profit
tom1807 said:
Very likely you can't.
From your description, when you flashed it, A13 was updated only on one slot with the new bootloader, while the second slot is still stuck with the previous bootloader. During the flashing (how did you flash?), something went wrong, so the Pixel wanted to boot from the second slot with the "old" bootloader and the "Anti-Roll-Back" kicked in.
RMA and hopefully get an exchange
Cheers
Click to expand...
Click to collapse
i have flashed using fastboot commands and that was on both-solts
Do you have idea how manufacturing put the Rom on devices? OR about
cdc-acm connection?
J0nhy said:
Follow this steps and let us know if it worked for you
1. Unplug the cable from your phone
2. Press and hold for at least 15 seconds the power button then release
3. Connect a cable from your pc to your phone but you need to press volume up and hold it until you connect the cable, once connected release the button your phone shall turn on fastboot mode, it it worked just proceeded and flash a13 again, just download it from it's official source
14. Profit
Click to expand...
Click to collapse
i have tried but nothing work

General how to fix hard brick 9r (Can't get into EDL mode/9008)

Few monthes ago, some 9R devices were killed by an mistake of 1+ commpany,this is link
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
As we know,if wana flash stock ,must get into 9008/edl mode,but due to reason above link,the killed devices bricked and can not get into EDL mode(usually it should work with vol+ & power button),yeah,totally hard brick,my devices was one of those
Now, there is way to fix those devices with "engineering mode cable",this cable will take over the functhion of "vol & power button" and thus make devices boot into 9008 mode directly
Usually vol+ power button send signal to motherboard to boot edl,but due to above link “send signal to motherboard” is wasted,if press the button of this cable the cable will send the signal directly.
it cost mine 19RMB (2.76 USD) on taobao to by this,I used to modify a normal microusb cable into an engineering cable,I think typec is the same(for press button the cable is engineering mode,if not pressed it‘s normal typec,the pressed button just make 2 of 3 lines inner the cable connected) ,just google how to make engineering cable if you do not want buy one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FateRover said:
Few monthes ago, some 9R devices were killed by an mistake of 1+ commpany,this is link
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
As we know,if wana flash stock ,must get into 9008/edl mode,but due to reason above link,the killed devices bricked and can not get into EDL mode(usually it should work with vol+ & power button),yeah,totally hard brick,my devices was one of those
Now, there is way to fix those devices with "engineering mode cable",this cable will take over the functhion of "vol & power button" and thus make devices boot into 9008 mode directly
Usually vol+ power button send signal to motherboard to boot edl,but due to above link “send signal to motherboard” is wasted,if press the button of this cable the cable will send the signal directly.
it cost mine 19RMB (2.76 USD) on taobao to by this,I used to modify a normal microusb cable into an engineering cable,I think typec is the same(for press button the cable is engineering mode,if not pressed it‘s normal typec,the pressed button just make 2 of 3 lines inner the cable connected) ,just google how to make engineering cable if you do not want buy one
View attachment 5860995
Click to expand...
Click to collapse
Thank you for this thread. I also solved my issue recently using "HYDRA CABLE - V2". It seems like the problems arises by flashing wrong .xbl images to the device.

Categories

Resources