Related
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
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
Thanks for the reply, I will try this as a last resort, but I've already rebooted my phone many times and I can't boot into OOS..
tiga016 said:
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
Click to expand...
Click to collapse
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
adeklipse said:
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
Click to expand...
Click to collapse
The same thing happened to me about a year ago. After completing the msm tool procedure my phone got stuck in a permanent bootloop w/ the bootloader locked of course. I suggest using the msm tool sparingly as this happened to me after about the tenth time I used it.
First of all thanks to the contributors here for pulling together the user guides for unbricking the phone. I am in a rather weird situation. While trying to flash my hard-bricked onePlus 6 - I think the battery was low, and the download did not complete fully. Since then, I have recharged the phone but the download gets stuck on this error: Firehose GetUSInfo Failed
I think my phone does not power-off fully somehow. I keep holding the powerbutton for over a minute, but the minute I connect the phone to my PC, it gets recognized immediately with the correct Qualcomm 9008 port. So the drivers are correct, and the PC recognizes the phone correctly.
Any idea how to switch off the phone fully, and then how to get past the 'Firehose GetUSInfo Failed' error?
Thanks in advance!
bro izi fix, i get this before and oneplus agen in jordan cant fix it so i fix it by myself, now im going to sleep pls send me a msg on telegram ( @NotReal0 ) i will learn you how to fix it but pls tomorrow u go to any pro dev shot ask them to get you the imei partation EFC that file have imei number and mac address you will need it for real
just send me a msg so i can help you step by step
( i dont need your money )
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
i have ROG PHONE 5 global, the first mistake is im uninstall magisk full in apps not from fastboot or wiped in recovery mode. then phone stuck in logo and i try get stock_boot.img but it doesn't work, then i wipe all data from recovery but it still same stuck in logo, the last im using method unbrick fastboot with flash_AFT and phone get in menu and like normal, but battery always showing 100% and not decrease while playing game or media, after 2 hours phone getting shutdown and can't turn on again with volume button or button power. if i plug the charger phone will show bootloader menu, if i unplug the charger phone will turn off (dead off) and its showing indicator 0 voltage , im tried to method fastboot flash_AFT again but its not work and will show Failed and finally im relock bootloader again but the problem still same what can i do? asus service center has reject me because root and unlock bootloader, sorry for bad my english
First, calm down. You won't get anywhere freaking out.
If you unlocked the bootloader, flash raw firmware. If you locked the bootloader to fix the issue, you can still try flashing, but you may have blocked your chance at fixing it yourself. Contact Asus and explain the issue, but don't tell them you unlocked the bootloader. They may still help.
Leaving this here because prevention saves devices:
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
twistedumbrella said:
First, calm down. You won't get anywhere freaking out.
If you unlocked the bootloader, force it to EDL mode and flash raw firmware. If you locked the bootloader to fix the issue, you can still try flashing in EDL, but you may have blocked your chance at fixing it yourself. Contact Asus and explain the issue, but don't tell them you unlocked the bootloader. They may still help.
Click to expand...
Click to collapse
the bad news is i locked back my bootloader and i can't go to EDL mode. untill i must pay with repair phone shop, and still stuck in bootloader and battery can't charge.
i now that, this why i relock bootloader again after i get problem battery can't fill, finally asus can detect my phone from system asus, they know if i has unlock bootloader and rooting phone, they will can help me but will out the cost for software flashing firmware official asus and needed 5 till 7 days work, if in case still same and failed they recommend me for change mainboard and for me very expensive arround 400$.
kharisjeh said:
the bad news is i locked back my bootloader and i can't go to EDL mode. untill i must pay with service phone local, and still stuck in bootloader and battery can't charge.
Click to expand...
Click to collapse
Unfortunately, the lesson here is that locking the bootloader is not a repair step. It won't fix anything.
twistedumbrella said:
Unfortunately, the lesson here is that locking the bootloader is not a repair step. It won't fix anything
Click to expand...
Click to collapse
this is fatal for me, and i dont know what can i do again exactly must change mainboard. so sad
kharisjeh said:
this is fatal for me, and i dont know what can i do again exactly must change mainboard. so sad
Click to expand...
Click to collapse
I don't know that it's a hardware issue. Charging is controlled by firmware, which appears to be what got corrupted. A full restore may fix it, but that requires Asus (or a repair shop) without an unlocked bootloader.
twistedumbrella said:
I don't know that it's a hardware issue. Charging is controlled by firmware, which appears to be what got corrupted. A full restore may fix it, but that requires Asus (or a repair shop) without an unlocked bootloader.
Click to expand...
Click to collapse
maybe this security for next future if bootloader is locked phone still safe if this phone is gone or grab from thieft, but this my oppinion asus service centre can't fix this problem but they will recommend it for change main board.
kharisjeh said:
maybe this security for next future if bootloader is locked phone still safe if this phone is gone or grab from thieft, but this my oppinion asus service centre can't fix this problem but they will recommend it for change main board.
Click to expand...
Click to collapse
It's not a security feature, but it also doesn't sound like a hardware failure. Asus seems to be replacing the boards for any issue that can't be fixed by flashing the firmware back to stock, which would likely solve the issue.
twistedumbrella said:
It's not a security feature, but it also doesn't sound like a hardware failure. Asus seems to be replacing the boards for any issue that can't be fixed by flashing the firmware back to stock, which would likely solve the issue.
Click to expand...
Click to collapse
maybe i must go to repair phone shop again for detailing issue and problem, may it can fix
Just got confirmation that the raw firmware should work, even with a locked bootloader.
Make sure you are using the USB-C port on the side of the phone.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
twistedumbrella said:
Just got confirmation that the raw firmware should work, even with a locked bootloader.
Make sure you are using the USB-C port on the side of the phone.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
would me try for this method?
Many rog 5 users on Zentalk have different charging problems, more or less serious, the led on or not, the% blocked, a significant overheating or no charge at all.
Even more are the predominantly Indonesian users with WIFI and Hotspot HS.
Except, there is in the asus_battery_charger.c file a large number of tests / conditions explicitly on Wifi & Hotspot, a more experienced programmer would have an explanation by analyzing these lines, the .188 sources are available on asus download
Mine as well too but all blackscreen everytime i try to do a hard reset while charger is connected it just give me blinking red light. When trying to do a hard reset without the charger it wont blink at all.
any possible solution for this?
Hello everyone.
I need some help i think. I bought a used OP7 Pro to try my hands at installing crDroid and changing this over to my work phone without any Google installed. I have successfully flashed ROM's on about 6-7 different phones successfully before - but not this time it seems.
I think I have introduced corrupted boot partitions (both a and b) and the phone is now barely alive.
I have it plugged in on the charger, but when trying to turn it on (using volume up and power) it says that power is low and that I should leave it plugged inn a while before booting up. Doing so leaves the phone to boot, but after the initial "warning" screen about the unlocked bootloader the phone dies and I have to try to turn it on again.
To make matters worse - i do not have a Windows machine to use to try to fix it. My personal one is Linux based (I used this for the failed flash attampt). I planned on following this guide:
How to Unbrick or Restore Back to Stock ROM on all OnePlus using this Tool
From this comprehensive post, you could unbrick your OnePlus device and restore it to the Stock ROM. We will be using the MSM Download Tool for the said
www.getdroidtips.com
This required a Windows machine in Test mode.
Any other tips or guide for me to follow that you recommened?
Thank you very much!
Hey guys, I recently rooted my stylus 5g and went to install TWRP. I was able to get it to boot to TWRP, but I believe within TWRP I did the flash wrong as now my device is hard bricked. I cannot get it to show the initial logo, get to the bootloader or I think even EDL. I've tried the Lenovo recovery tool and the Moto all-in-one tool, but essentially all I get now is a black screen.
Any input on what I can do to either diagnose and possibly recover my device? I have the original firmware downloaded, but without being able to get to the bootloader, recovery, or even EDL, I'm at a loss as to how to proceed. I did grab a blankflash for the device, but I'm not clear on how to begin to use that to move forward.
Thanks for any advice you can provide.
-Ryan
Hello friend, honestly I am new to this. In fact I'm looking for how to unlock my moto g stylus 5g xt2131-1 from metropcs to use it with a mobile operator in Colombia. But given your problem, and everything I've researched recently, I would say you could check this video:
in which revive a moto g8+, although it is a different version, it should work if you do the steps as indicated.
Did you ever figure this out? Mine is also hard bricked at the moment. I've been trying to get it to the 9008 mode so I can blankflash but I've had no luck. I see on some phones there is a pair of pins on the board that need to be shorted but I'm not sure which ones. I just bought an edl cable on amazon which should be here tomorrow, hopefully that will get it in the correct mode.
duffman452001 said:
Did you ever figure this out? Mine is also hard bricked at the moment. I've been trying to get it to the 9008 mode so I can blankflash but I've had no luck. I see on some phones there is a pair of pins on the board that need to be shorted but I'm not sure which ones. I just bought an edl cable on amazon which should be here tomorrow, hopefully that will get it in the correct mode.
Click to expand...
Click to collapse
could you let me know if that works. im struggling with this as well
Absolut_Malarkey said:
could you let me know if that works. im struggling with this as well
Click to expand...
Click to collapse
No luck. Only change with the EDL cable is that if I plug the phone in via the cable with the battery unplugged it was a pretty rapid blink vs before it would blink every 10 seconds or so if I held the power button while plugged in to power. The button on the EDL cable had no effect. I then tried to short out every combination of pads on the board similar to the video above. No luck, it just seems to be completely toast. All I did from TWRP is format data and reboot to fastboot. Dead since then.
Is there any more information on this subject?
View attachment IMG_20220717_121138987~2_66348_SP-8988.jpg
Here is the pcb picture. Not sure if the number 2 has any significant meaning but someone told me it was one of those points with one by the battery connector. Anyone have any info on this it would be greatly appreciated.
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
duffman452001 said:
No luck. Only change with the EDL cable is that if I plug the phone in via the cable with the battery unplugged it was a pretty rapid blink vs before it would blink every 10 seconds or so if I held the power button while plugged in to power. The button on the EDL cable had no effect. I then tried to short out every combination of pads on the board similar to the video above. No luck, it just seems to be completely toast. All I did from TWRP is format data and reboot to fastboot. Dead since then.
Click to expand...
Click to collapse
thank god i saw this, i was getting ready to flash TWRP even just unlocked my bootloader and everything, not taking this chance! i honestly got so many phones to root, unlock the bootloader, flash new roms, but litterly all of them have at least one problem.. (my devices range from lg to motorola, zte, htc, samsung...) i had a moto g play, but i tried to flash TWRP from magisk, and looked like it was stuck in boot loop, then used motorola tool, and fried it.. litterly didnt show any sign of life after, (I dont thing it was motorlas tool, i think it had something to do with me trying to flash TWRP, anyway, the screen looks like an explosion! had more fun hitting it with a rubber mallet than getting frusterated, and maybe fixing it...
liammmmnnnn said:
thank god i saw this, i was getting ready to flash TWRP even just unlocked my bootloader and everything, not taking this chance! i honestly got so many phones to root, unlock the bootloader, flash new roms, but litterly all of them have at least one problem.. (my devices range from lg to motorola, zte, htc, samsung...) i had a moto g play, but i tried to flash TWRP from magisk, and looked like it was stuck in boot loop, then used motorola tool, and fried it.. litterly didnt show any sign of life after, (I dont thing it was motorlas tool, i think it had something to do with me trying to flash TWRP, anyway, the screen looks like an explosion! had more fun hitting it with a rubber mallet than getting frusterated, and maybe fixing it...
Click to expand...
Click to collapse
I did end up recovering mine via the test points https://forum.xda-developers.com/t/...ank-flash-boost-mobile.4469613/#post-87181339
duffman452001 said:
I did end up recovering mine via the test points https://forum.xda-developers.com/t/...ank-flash-boost-mobile.4469613/#post-87181339
Click to expand...
Click to collapse
my moto g stylus is thru T-Mobile, i heard that its different, lol i just honestly dont want to brick mine, im also kinda new to this stuff, so if something is gonna go wrong even with steps its me LOLL, also im not meaning to be mean if you take it that way
deleted.
liammmmnnnn said:
my moto g stylus is thru T-Mobile, i heard that its different, lol i just honestly dont want to brick mine, im also kinda new to this stuff, so if something is gonna go wrong even with steps its me LOLL, also im not meaning to be mean if you take it that way
Click to expand...
Click to collapse
That thread for the 2131 EDL is correct, ive used it.
wickedxjay said:
That thread for the 2131 EDL is correct, ive used it.
Click to expand...
Click to collapse
You used it it on the xt2215-4?