Condition
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
{
"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"
}
SolomonMT said:
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
View attachment 5731647
Click to expand...
Click to collapse
You seem to have a driver issue. Install libusb and try again. The battery should not be required for any of the steps as long as the usb is plugged in properly.
OK, it got unbricked, Im guessing Ill brick it again once I try installing ArrowOS for the second time, but for now, Ill try and sumarize what Ive done since I had the phone on OFW.
To get the phone hard-bricked:
I unloacked bootloader and installed Orange fox succesfully then I bricked my phone while trying to flash Global MIUI (as the first step to install ArrowOS but notice it is totally unrelated to ArrowOS), there is a detailed explanation of how I did it here
[ROM] A11 ArrowOS [Garden] 29-12-2021 UNOFFICIAL
I'm not responsible for damage made to your device About: ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end...
forum.xda-developers.com
Trying SPFlash Tool to unbrick my device
My xiaomi redmi 9A was bricked at this point, I described it as:
"the phone just vibrates after a while holding the power button and the screen doesnt even turn on, it isnt recognized by the computer, and if I try to boot into recovery the same happens but the screen turns on for a fraction of a second whith the redmi logo then turn off again, It is not recognized by the computer in this state either"
after gaining some experience with it, I think adecuate to say that the phone still vibrated when holding the power button, but at least the screen did not turn on and as I said; "it wasnt recognized", but just to be clear, what I mean by that is that the PC did absolutely nothing when I pluged the phone in, later after some failed attempts at fixing it, this changed, now the computer prompted me a message explicitly saying, "this device is not recognized" if it was actually recognized before or not is above me.
anyway, back to the moment right after hardbricking my phone in the first place:
I tried using SP flashing tool with this video
but the video is old and after some links died not all the files where provided, (it did however provide a functioning method to disable protection)
so what I did was mix and match different files from diferent sources, and try different methods from diferent videos using SPFlash tool, wich was admitedly a bad idea, the main issue with it was that it symply stayed long periods of time on "download da 100%" with no error message prompting, so i could only stop it change the files and try again, sometimes disconecting the phone, bypassing security with (vol+ vol-) and repeating.
but at one point, the phone did nothing (from now on by nothing I mean not even vibration), the vol+ vol- security did not work, then I tried:
power button alone; noting
power vol+; nothing
power vol-; nothing
and when connected to the PC it told me "this device is not recognized" so the device was totally unresponsive, total brick.
at this point I had already halfly gave up, I enjoy the process, but it was just so unsatisfactory to fail again and again that I just didnt want anymore.
It fixed itself (still hard-bricked but responding).
Now how this got fixed, I actually dont know, I thought maybe if I wait for a while it will respond again, so after two hours it was still the same, I thought maybe if I charge it, after a while with it charging, let it discharge for a while (some odd days), fully charge it (another day or so), and all of those did nothing.
Then I just left it on my desk for like another day when I decided to just try to turn it on one final time and it responded (I dont know what happened I dont know what worked I have several charger boxes and cables plus the pc usb ports, maybe one of them was defective, maybe the one I used lastly was just better, I dont know, but something worked) maybe it just needed around 5 days to work again, i think when it worked for the first time it was plugged to an outlet, Im sorry I cant be more helpful)
now the phone just vibrated after any of the regular button combos, but it no longer displayed anything on the screen if I tried to boot into recovery, but, the PC no longer prompted me that the phone was not recognized, so I could try again.
What actually completely un-bricked my phone.
(This first step is a substitute to the OP requiremeents 5 and 6 used on steps 1 8 9 10 11, this didnt work for me on windows 10, maybe it was just me , but it didnt work)
I installed the Python3.9.1, MTK driver and libUSB I left this files attached as "extra installs", and did it according to how its done on this video
The video is in spanish so if you need extra assistance you can ask me about it or search how to install libUSB wich is the only one I think needs special attention on how to install it (also MTK gave me an error but apparently always does, I tried putting adb on the install folder but Im pretty sure this did nothing as it just gave me a different error)
then, you extract what I left on "ByPass OFF", and run broom.bat a cmd will open up telling you its waiting for a device
(from now on you cant unplug your phone, if you do you have to restart from here)
You plug your bricked phone, and press both vol+ and vol- at the same time until the cmd tells you something like this
then you go to SPFlash tool latest version, (I used SP_Flash_Tool_v5.1924_Win but im pretty sure any one will work)
youll need the ROM that OP provided, its this one.
its 4.22 GB so download it with time, its not a quick page to download from even tho I have "good" internet (around half an hour to a full hour)
you extract it (i recomend using winrar)
and put the scatter file youll use, on the extracted ROM folder, in the image folder, you can download the three scatter files that are for 12.5.4.0 RCDMIXM from the page OP provided and try them all, i left down here the one that worked for me anyway but I dont know what will work for you.
after that I launched the SP Flash tool, and selected the "no auth .bin" provide by OP as Download agent.
(it is posible you get this error
fix it and try again)
as Scatter file you go to the extracted ROM\image and selecth the Scatter file you want to use (again, I left the one I used down here, I have no idea if its the same one that comes with the ROM, also its important it is on the right folder in the extracted ROM)
leave auth blank
I did not select UART port, It didnt work for me, auto USB worked better for me.
you change the dropdown menu to Firmware update
and finally start the program by pressing the download button.
this should work and youll get a prompt like this.
after it had finished I had to unplug my phone and plug it on an outlet for it to let me turn it on, I tried like 3 times before with it still pluged to the PC but it didnt work for some reason, I did not try with it just umpluged so who knows) it turned on to logo, and in around 10 minutes, it asked me to set up the phone as first start like when its brand new, (it was however different to how it used to be, so I know I at least installed a different ROM, do with that info what you will)
Whatts next?
I havent checked if I still have the orange fox recovery installed, tho I doubt it. and also how do I install ArrowOS now? can I do it from spflash tool? thatd be great, is there a better Custom ROM?
Thanks
Also thanks to OP: Yuarian that even if it didnt work for me as is, it still ended providing me with most if not all the tools I needed to unbrick it, and Im pretty sure the ones that didnt work failed becasue I had residual trash files from previous attempts that screwed over his.
anyway see you around.
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
M2006C3LG
SolomonMT said:
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
View attachment 5765891
M2006C3LG
Click to expand...
Click to collapse
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
I have the exact same model, but I dont know how common is that model number, maybe ones made in china and other places have the smae model, I have a 32 Gb version with a single SIM but I can tell it was planed at some point to have it be dualSIM it also has 2 IMEIs
This post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
About your phone in particular, I have three questions.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Ivan.Adriazola said:
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
About your phone in particular, I have four questions.
Its a redmi 9A right? this post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
View attachment 5767183
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Click to expand...
Click to collapse
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
yeah
SolomonMT said:
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
Click to expand...
Click to collapse
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Ivan.Adriazola said:
yeah
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Click to expand...
Click to collapse
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
SolomonMT said:
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
Click to expand...
Click to collapse
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Ivan.Adriazola said:
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Click to expand...
Click to collapse
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Something to be noted for ArrowOS is that you cannot install it on a phone running MIUI 12.5, as far as I can tell.
To install ArrowOS you need to install a custom recovery, and there is no custom recovery for MIUI 12.5.
Moreover, Xiaomi prevents you from flashing an older version of the stock ROM, so there is no way to rollback to a version supported by a custom recovery.
Hence, I am stuck running MIUI 12.5 for the foreseeable future.
SolomonMT said:
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Click to expand...
Click to collapse
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Ivan.Adriazola said:
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Click to expand...
Click to collapse
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad. Thanks.
SolomonMT said:
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad.
Click to expand...
Click to collapse
youre welcome
I managed to flash the rom and revive my phone thanks to this guide. It booted, works perfectly
First unplugged battery. Then.
I used MTKClient on Linux, installed following instructions, https://github.com/bkerler/mtkclient
And ran command
sudo mtk payload
(then left Vol up and Vol down pressed together and plugged usb cable to unlock the SLA Authorization)
The tool runs a generic payload to the CPU, mt6765 in this case, and puts the phone on BROM mode
(This will unlock SLA authorization, allowing the Rom to be flashed)
(A message appears saying " Successfully sent payload " along with Hardware/Port info)
From there immediately used SP Flash Tool-V5-1916
sudo ./flashtool
Used DA_6765_6785_6768_6873_6885_6853.bin as DA
Used MT6765_Android_scatter--V12.5.4.0.RCDMIXM--boundary_false.txt as Scatter file.
And flashed the whole Firmware/Rom 12.5.4.0.RCDMIXM Global with UART Connection Setting.
Thank you for the guide master. God bless you.
(Its important to be patient)
(Bypass utility didn't work for me, i think it works better in Windows or Debian/Ubuntu, but not other distros)
Yuarian said:
Condition
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
Click to expand...
Click to collapse
hi i have a redmi k50 pro whit dimensity 9000 MT6983 can you healpe me? pllleasee
Hi, I was trying these steps with no success, maybe something was missing (this was in Windows). However, I found another way to do it with Linux where you don't need to install drivers as the system comes ready to use.
I detailed what I did to unbrick my Redmi 10A here:
Unbrick or Recover Xiaomi Redmi 10A and other MTK devices
Unbrick Xiaomi Redmi 10A and other MTK devices.
runakay.blogspot.com
Related
I'm brand new to LG devices & was using this threads instructions
http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
I tried rooting using a TOT file in LG UP. However, when I opened lgup it said I needed to download the driver for it to work. But I had downloaded the h830 DLL and the mobile drivers, and the program launched and saw my device so I just continued.
After it opened, I just selected the TOT file and started, it finished, and now I can't get past the boot screen. There's red language at the upper left saying 680,730,780 boot verification fail, 830-cause mismatch_sig_len, 880,930
Ive read and downloaded things for hours now trying to figure out how to get it back to stock. I've downloaded the 4.9gb tot file that's linked in that thread for going back to stock, but all I can find is people saying use lgup to flash the file.
My question is, how do I accomplish that if I can't get past this screen? I can't get it back in the bootloader. I can't get it to be recognized by the pc. And lgup still says it needs the driver when I open it, and it doesn't see the phone either. Please help. I've had this phone all of 1 day.
BTW, I uninstalled lgup and the driver and DLL, rebooted, then reinstalled the DLL and driver first, before reinstalled lgup and it still says it needs the driver.
Anyone?
I never used adb to unlock the bootloader before trying to flash. I thought I only had to check oem unlock and USB debugging in developer options because I was trying to use iroot first.
My main problem is my phone starts up but doesn't get past the LG logo. It shows the boot verification error, mismatch_sig_len then immediately reboots and does it again. How do I reflash the stock TOT file in this state?
Is it just a driver issue, and my phone should be seen by lgup even in this bootloop? Or do I have to get it back into bootloader? If so, how?
Please don't disregard if I sound like a total idiot. I do have experience flashing with galaxy devices. I just didn't do enough research before I tried this one.
Have a look at LG Flash.
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
konchar said:
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
Click to expand...
Click to collapse
Please browse the thread and/or the guides section first. It's there. Being self-sufficient never hurt anyone.
konchar said:
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
Click to expand...
Click to collapse
Thank you for this post. Just knowing that someone who had the same issue as me was able to get the phone back to stock successfully made me not so anxious.
My main issue the other night when I was trying to fix the phone, was I couldn't get it back into download mode. I had the phone connected to the computer, and was disconnecting the battery and connecting it again while holding volume up, with the cable always connected. Tonight, I just help volume up while plugging in the cable instead, and was able to get it into download mode.
I then ran into the same anti rollback issue. But I'm now using LG Bridge to go back to stock.
I think what we need to do to get root, is enable USB debugging and check oem unlock. Then use the sdk tools with the command prompt window... Adb reboot bootloader>Fastboot oem unlock, then try flashing the root tot file with latest version of lgup.
As long as I know I can get back to stock, I won't be so scared about attempting the root again. Lol.
TH4N1X said:
Please browse the thread and/or the guides section first. It's there. Being self-sufficient never hurt anyone.
Click to expand...
Click to collapse
Come on man. Some of us have spent hours searching what to do, and are running into unforseen issues and just need a little guidance. I'm all for searching threads to get your information, but when your hours or days in and running into walls, regardless of the reason... It's ok to ask for help. Not everyone has the same knowledge and skill level with this stuff. I've only ever used Odin to flash stuff to galaxy phones before... All this LG stuff is brand new to me.
Ok relax, in order to have your device recognized by your pc you must now put it in d/l mode (with power off, hold volume down and power until d/l mode starts) then run LG UP and try to downgrade. If that gives you the all to well known anti-rollback error then you need to download the hacked version of lg up (forget what it's called but it's in one of the rooting threads) and then downgrade. I struggled with the same thing a while back. My memory just isn't so good but I'm confident you'll figure it out.
@SaintCity86
autoprime said:
Repacked LG's original installer with @ieatacid's patched EXE.
Should make installing it all even easier... no more EXE switch.. just install and use (hopefully).
I made sure to add ieatacid's name, paypal and this thread in the Setup EXE.. this way ieatacid's name will always be attached to the LG Flash install rather than the loose LGFlash.exe getting passed around like the old megalock.dll.
Added LGUP and LG Flash directions and downloads to my All-in-One G5 Thread here.
{
"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"
}
MD5 (Setup_LGFlashTool_2.0.1.6-ieatacid.zip) = 7e2a5a6c74ac3d54a707c7fcde831655
MD5 (Setup_LGFlashTool_2.0.1.6.exe) = 6d0f8a4ad4bc01157a9c7c16f3a7c574
Download Setup_LGFlashTool_2.0.1.6-ieatacid.zip
Click to expand...
Click to collapse
Second page, 7th post on it (17th in total). It's also stickied in the Guides, News, & Discussion section.
http://forum.xda-developers.com/showpost.php?p=66683763&postcount=17
You can also try different versions of LG UP and if it fails go for the LG Flash. You can find software to flash here: http://lg-firmwares.com/lg-h830sv-firmwares/. Only flash KDZs from the TMO region. If you succeed in going back to stock, you can get recovery and root by using the Dirty COW exploit.
One more thing:
SaintCity86 said:
Tonight, I just help volume up while plugging in the cable instead, and was able to get it into download mode.
Click to expand...
Click to collapse
That's how you actually get into download mode. Battery pulling is for getting out of it.
So I managed to get it back to stock by using LGBridge and updating. And I've been using the 3 step guide in this thread:
https://forum.xda-developers.com/tm...p-step-guides-rooting-t-mobile-lg-g5-t3388272
All seemed to be going fine, but when I put my phone is is debugging and checked oem unlock then plugged it into my laptop (64bit windows 7), it failed to install 2 parts of the initial driver. MTP and another one I can't remember. But it is recognized by the computer when it's on.
However, when I boot into fastboot, it's only showing up as an android device with no driver. And I can't figure out which driver to get for the life of me. Idk if I'm running into issues because it's a 64bit system or what. Do you Have any suggestions where I can look to get this resolved?
TH4N1X said:
That's how you actually get into download mode. Battery pulling is for getting out of it.
Click to expand...
Click to collapse
Yeah I'm aware. It's the same for Samsung galaxy devices which I've developed on for years....my issue was I had the phone plugged into the computer and was pulling the battery to turn it off and just plugging the battery back in holding vol up, with the cord still plugged in. I didn't realize there was a difference. I thought I just couldn't get into download mode.
djerick3 said:
Ok relax, in order to have your device recognized by your pc you must now put it in d/l mode (with power off, hold volume down and power until d/l mode starts) then run LG UP and try to downgrade. If that gives you the all to well known anti-rollback error then you need to download the hacked version of lg up (forget what it's called but it's in one of the rooting threads) and then downgrade. I struggled with the same thing a while back. My memory just isn't so good but I'm confident you'll figure it out.
Click to expand...
Click to collapse
UPPERCUT ?? thats the one your looking for
bassmek2 said:
UPPERCUT ?? thats the one your looking for
Click to expand...
Click to collapse
Yup that's it
get into download mode open device manager look for device with explanation mark right click and search for driver or u can show it where the driver is look for the folder where driver installed should be an lg folder C:\Program Files (x86)\LG Electronics\LG Mobile Driver if you don't have that folder then you haven't installed driver package download uppercut and get your kdz file I've had a few problems with a couple of kdz files I've downloaded they wouldn't install i think the file you need is H83020a_00_1107.kdz make sure when u go to flash that you have it in upgrade mode or else it will give you an error
SaintCity86 said:
Anyone?
It shows the boot verification error, mismatch_sig_len then immediately reboots and does it again.
Click to expand...
Click to collapse
Good day!
How did you solve your problem?
I have same trouble with my LG H830. When i try to boot in DL mode, appears small icon Dowload Mode and the phone restarting again with error:
[870] Boot verification fail!!
[920] cause : MISMATCH_SIG_LEN
How did you boot to download mode?
Thanks.
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please
I've bricked my OnePlus 7 pro.. how to go on edl and flash ROM..
The MSM tool should work eventually, the one time I used it, it took ages to get it working.
A few tips:
1] Use the official cable that came with your phone
2] Follow a guide like this (The certificate part is very important, it won't work without it), ensure you have the latest drivers (I've just exported my current ones from the phone here for you to download, Windows and Mac drivers are in there)
3] Make sure your computer sees the device when you press both vol up+down + power and lists it as the "QUSB_BULK_CID..." device, if your computer does not do that then the phone is not in the correct mode and the tool won't see it so won't show the entry to flash the stock rom(i.e. When it says "connected"), this part took me a while for the computer to list it properly.
4] Keep trying and don't give up, you should eventually see the MSM tool recognise the phone properly, as I said, it took me ages to get it working.
5] When the tool does start (and it will, I promise...eventually), leave it to do it's thing and leave the phone for a while to set itself up, you will, obviously, lose whatever you had on the phone because the tool will put it back to completely stock.
6] If I remember correctly, once the tool has finished the install the phone will reboot itself and will do an initial setup again.
7] Good luck and don't give up hope, I didn't think it was working at all either but it did eventually.
If you need to install an OS on your phone, follow this method.
https://forum.xda-developers.com/one...tboot-t3972469
This will get you back to factory settings, unlocked bootloader. This was and is the only method that works for me. Good luck!
Thank you
It finally worked. Turned off the phone completely, then pressed and hold volume up & down button for 5 seconds and then plugged in the usb cable to phone while holding the volume buttons. It recognised the phone and started flashing the file.
Thank you once again
Actually, let me add this that that the phone needs to be connected to a USB 2 port and not 3.0 for the qualcomm download mode to work and eventually for MSM to recognize your phone..
djsubterrain said:
The MSM tool should work eventually, the one time I used it, it took ages to get it working.
A few tips:
1] Use the official cable that came with your phone
2] Follow a guide like this (The certificate part is very important, it won't work without it), ensure you have the latest drivers (I've just exported my current ones from the phone here for you to download, Windows and Mac drivers are in there)
3] Make sure your computer sees the device when you press both vol up+down + power and lists it as the "QUSB_BULK_CID..." device, if your computer does not do that then the phone is not in the correct mode and the tool won't see it so won't show the entry to flash the stock rom(i.e. When it says "connected"), this part took me a while for the computer to list it properly.
4] Keep trying and don't give up, you should eventually see the MSM tool recognise the phone properly, as I said, it took me ages to get it working.
5] When the tool does start (and it will, I promise...eventually), leave it to do it's thing and leave the phone for a while to set itself up, you will, obviously, lose whatever you had on the phone because the tool will put it back to completely stock.
6] If I remember correctly, once the tool has finished the install the phone will reboot itself and will do an initial setup again.
7] Good luck and don't give up hope, I didn't think it was working at all either but it did eventually.
Click to expand...
Click to collapse
Bro.. can you help me with a guide to get miui 12 rom port on oneplus 7 pro.. i've tried doing it but my phone was stuck in loop.. i get confused with the installation process and kind a mess the Partitions.
Sunil2735 said:
Bro.. can you help me with a guide to get miui 12 rom port on oneplus 7 pro.. i've tried doing it but my phone was stuck in loop.. i get confused with the installation process and kind a mess the Partitions.
Click to expand...
Click to collapse
Hi, where do you get the ported miui 12 ? I am interested..
I wish someone make the MIUI12 Rom for OnePlus 7Pro. I've been waiting too.
I waiting ios14 ported op7pro, and Samsung Touchwiz sounds good to op7pro too
Maybe you can try this and let me know if it works on the OnePlus 7 Pro I found it on Google so I haven't checked it yet.
https://sourceforge.net/projects/miui-12-stable-ports/files/MI_Globe/
i installed the DSU package and now the phone is stuck on your device is corrupted and cannot be trusted. I can only get into fast boot mode
can someone guide me through resetting it, I dont care about anything on the phone i just want it to go back
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
If you can reach fastboot this method should work
_MartyMan_ said:
If you can reach fastboot this method should work
Click to expand...
Click to collapse
dont i need unlocked bootloader?
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
dont i need unlocked bootloader?
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
casualBricker said:
dont i need unlocked bootloader?
Click to expand...
Click to collapse
To flash critical partitions, yes
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
mattie_49 said:
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
Click to expand...
Click to collapse
My bad, didn't see that he changed op. I mean if he could not connect through msm, there are a few options to try, including installing a driver manually for the qcom device. I had to fiddle with drivers and whatnot for about an hour or so before flashing was able to successfully commence. msm should help but scheduling a remote repair might take a day or so from oneplus so might as well try you know?
casualBricker said:
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
Click to expand...
Click to collapse
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
D3G0N said:
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
Click to expand...
Click to collapse
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
casualBricker said:
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
Click to expand...
Click to collapse
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
D3G0N said:
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
Click to expand...
Click to collapse
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
casualBricker said:
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
Click to expand...
Click to collapse
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
D3G0N said:
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
Click to expand...
Click to collapse
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
casualBricker said:
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
Click to expand...
Click to collapse
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
D3G0N said:
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
Click to expand...
Click to collapse
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
casualBricker said:
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
Click to expand...
Click to collapse
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
D3G0N said:
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
Click to expand...
Click to collapse
im not touching the powerbutton, it confuses me as well. do I wait for it to vibrate before I plug in the phone?
Hello all. Firstly, i wish to apologise if this isnt the right place. But its been a while since ive been here, and couldnt find a ULEFone section.
Ill try to be as descriptive as i can.
Ive got my hands on a ULEFone Armor X7 that was running Android 10. It came to me with the problem of when you boot it up, it complained about corrupted firmware. And i had to press the power key to continue. They tell me it happened when they clicked on a link from a message and it took them to some website ending in RU. The phone rebooted and then displayed that every time.
So i went to their support page, and downloaded all the files needed to restore the firmware to stock. Using the SP_MDT programm they provided, Followed all the instructions to the letter. And everything responded as expected.
Looking around with other users who use mediatek/ULEFone devices this seems to be the norm.
-Plugged into the phone while holding volume down. Started a Port scan using the software
-Then using the software i start a firmware upgrade on the 1 port my device was connected to
-Let that finish, and i should unplug and reboot the phone
Except when it came time to reboot the phone. It just doesnt power on now. And now when plugging into the PC it comes up with "USB Device unrecognised/damaged"
If i leave it unplugged for say 30 mins and try again. The computer recognises it this time. But when i try to do a port scan with the tool again, it just fails.
Tried various PC's and differeing windows versions. All with the same results.
Is this phone now basically a goner? Or is there a chance i can recover it?
And what would have went wrong?
Thanks in advance
Vildar said:
..
Tried various PC's and differeing windows versions. All with the same results.
Is this phone now basically a goner? Or is there a chance i can recover it?
And what would have went wrong?
Thanks in advance
Click to expand...
Click to collapse
I suspect you're going about it the wrong way.
You shouldn't be holding any button when you connect for flashing
Hovatek said:
I suspect you're going about it the wrong way.
You shouldn't be holding any button when you connect for flashing
Click to expand...
Click to collapse
This was what was mentioned in the manufactures documents for reflashing the firmware. As holding down volume down while plugging in puts the phone into bootloader mode.
Pressing nothing when plugging in doesnt give me anything.
Vildar said:
This was what was mentioned in the manufactures documents for reflashing the firmware. As holding down volume down while plugging in puts the phone into bootloader mode.
Pressing nothing when plugging in doesnt give me anything.
Click to expand...
Click to collapse
Why don't you try SP flash tool. I'm not sure if this model has secure boot but I'm guessing its DA file is contained in the zip you downloaded if it does
Hovatek said:
Why don't you try SP flash tool. I'm not sure if this model has secure boot but I'm guessing its DA file is contained in the zip you downloaded if it does
Click to expand...
Click to collapse
I will give this one a go (As soon as im able) and let you know what happens. Thanks
So this one gave the the same problems.
The DA Download bar goes to 100%. Sits there for a while then bails out.
However i did get a nice error message pop up that will hopefully help.
Hope this helps
I have not managed to get much further than thia. My guess is the phone is hard bricked. No amount of different software/drivers etc seems to have any effect.
It gets to the DA Download phase at 100%. But then just sits there. And then failes out with the above message. From what ive read about this does indead mean its done for.
Thanks for the help all the same
did you manage to fix it ?