Related
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
voxoph said:
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
Click to expand...
Click to collapse
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
cmulk said:
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
Click to expand...
Click to collapse
Thanks for responding. I am going to try ADB again but I can't get into recovery mode at the time being.
A similar thing just happened to me, except I got right out of it. Device was completely unresponsive, no download mode, adb nothing, indicative of a hard brick. Scared the **** out of me as I've had it less than 6 hours... Started holding buttons, and it came to life after ~1 minute of power button + volume down. Related? Well maybe not, thought I'd post it here. (TWRP 2.8.5 + Rooted CM12)
True Hard Brick, No OS!
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
TSF14 said:
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
Click to expand...
Click to collapse
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
hyelton said:
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
TSF14 said:
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
Click to expand...
Click to collapse
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 plug using the OEM LG cable while holding volup and then plugging in the USB cable?
hyelton said:
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 CCCC?
Click to expand...
Click to collapse
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
TSF14 said:
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
Click to expand...
Click to collapse
Are you sure your battery is not dead??
hyelton said:
Are you sure your battery is not dead??
Click to expand...
Click to collapse
Yes, if only it was that easy.
There are a few things you can try :
1.) Press the Powerbutton for a longer time
If you have a responce like the LG Logo or something like that, you might want to try and plug it to the computer and use the managing software
with which you can emergency reinstall the firmware.
2.) Press Power + Volume Down
If it restarts into the recovery menu, try to find a way to load a flashable stock rom of your handy onto the memory of your phone in order to "reflash" it.
(I don't know how you can do that )
3.) Go to the shop where you bought it and explain your problem, since rooting a LG device is not really easy to detect the chances that your warranty will cover for it are pretty high.
Sent from my LG-D955 using XDA Free mobile app
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Read this.
http://forum.xda-developers.com/att-lg-g3/help/bricked-d850-help-t3064874
I was tinkering with my phone, did not know what I was doing, tried to flash a stock recovery to replace twrp, most probably was flashing the wrong version as the recovery was not booting, (being the noob i am) also flashed recovery.IMG.header and now my phone is stuck in bootloader with error message
Please update system again (in red color)
And under the gutted Android logo
Something about boot image being corrupted (again in red)
and an error number.
Adb does not recognize my device, actually even device manager does not recognize it any more.
Tried to force install drivers and any other method I could think of or read here on XDA forums. Still the same
So, is there a room of developers or tech enthusiasts who can help me to try to solve this problem.
Thanks
This is the screen I get, battery does not charge, no matter how hard I try, I can not enter a bootloader without error message, and my PC does not even recognize my device when I connect it. Mean windows device manager does not show any changes in hardware
muradulislam said:
I was tinkering with my phone, did not know what I was doing, tried to flash a stock recovery to replace twrp, most probably was flashing the wrong version as the recovery was not booting, (being the noob i am) also flashed recovery.IMG.header and now my phone is stuck in bootloader with error message
Please update system again (in red color)
And under the gutted Android logo
Something about boot image being corrupted (again in red)
and an error number.
Adb does not recognize my device, actually even device manager does not recognize it any more.
Tried to force install drivers and any other method I could think of or read here on XDA forums. Still the same
So, is there a room of developers or tech enthusiasts who can help me to try to solve this problem.
Thanks
Click to expand...
Click to collapse
first of all download the stcok firmware that suits your device, then follow one of these methods.
1. Prepare a capacity of more than 2GB SD card
2. confirm the presence UPDATE.APP dload file directory, then the whole dload copied to the SD card root directory. SDcard\dload\UPDATE.APP
3. Press the volume button down, press power button, volume up and down keys to sustained 10 seconds, the phone will automatically trigger an increase in the SD card.
.
Second Methods : Upgrade normal
1. Prepare a capacity of more than 2G SD card, it is recommended to use Micro SD class 8 and up
2. Format SD card (optional).
3. confirm the presence UPDATE.APP dload file directory, then the whole dload copied to the SD card root directory.
4. SD card into the phone is turned on, go to “Settings”, select “Settings – Phone Upgrades – System Software Update – Local Upgrade.” Based on the dialogue choose whether to back the data, and finally select the “Upgrade” button to start the upgrade.
tell me if it works.
I tried this method once, did not work. Will give it another try and will let you know.
muradulislam said:
I tried this method once, did not work. Will give it another try and will let you know.
Click to expand...
Click to collapse
I hope it works
@muradulislam did you solve it buddy? By doing the three button reset?
Nope
Still get the same screen no matter what I do
How about flashing firmware?! @DigiGoon
Try this method buddy:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
I already tried pressing the volume down button and connecting to PC simultaneously, also tried power + volume down.
Also tried power+volume up, 3 btn restart.
Nothing works. It does not boot into bootloader no matter what i try and my PC does not recognize it at all in the present state so no chance for adb to recognize it.
Also installed Huawei Usb drivers, kouch's universal drivers.
I am thinking that it's a hard brick looking like a soft brick.
I saw a guide somewhere saying that I need to physically pry open the phone and do some meddling with the hardware to get it fixed but I am not into that so just closed the page and never tried to find it again.
Well, that's the whole sad story :crying:
muradulislam said:
I already tried pressing the volume down button and connecting to PC simultaneously, also tried power + volume down.
Also tried power+volume up, 3 btn restart.
Nothing works. It does not boot into bootloader no matter what i try and my PC does not recognize it at all in the present state so no chance for adb to recognize it.
Also installed Huawei Usb drivers, kouch's universal drivers.
I am thinking that it's a hard brick looking like a soft brick.
I saw a guide somewhere saying that I need to physically pry open the phone and do some meddling with the hardware to get it fixed but I am not into that so just closed the page and never tried to find it again.
Well, that's the whole sad story :crying:
Click to expand...
Click to collapse
Don't lose hope, try again
muradulislam said:
I already tried pressing the volume down button and connecting to PC simultaneously, also tried power + volume down.
Also tried power+volume up, 3 btn restart.
Nothing works. It does not boot into bootloader no matter what i try and my PC does not recognize it at all in the present state so no chance for adb to recognize it.
Also installed Huawei Usb drivers, kouch's universal drivers.
I am thinking that it's a hard brick looking like a soft brick.
I saw a guide somewhere saying that I need to physically pry open the phone and do some meddling with the hardware to get it fixed but I am not into that so just closed the page and never tried to find it again.
Well, that's the whole sad story :crying:
Click to expand...
Click to collapse
If it is still under warranty, I would try oficial support. They generally dont bother about installing recoveries, 3rd party ROMs...
Even if it is out of warranty, they could provide you a reasonable cheap repair. Better than fiddling inside and do some physical damage that could mean replacing the whole board.
zinko_pt said:
If it is still under warranty, I would try oficial support. They generally dont bother about installing recoveries, 3rd party ROMs...
Even if it is out of warranty, they could provide you a reasonable cheap repair. Better than fiddling inside and do some physical damage that could mean replacing the whole board.
Click to expand...
Click to collapse
Your idea seems to be the better solution :good:
Agreed with zinko_pt here, don't open it and try anything physically, instead throw it in a Huawei service center, they'll definitely help you.
zinko_pt said:
If it is still under warranty, I would try oficial support. They generally dont bother about installing recoveries, 3rd party ROMs...
Even if it is out of warranty, they could provide you a reasonable cheap repair. Better than fiddling inside and do some physical damage that could mean replacing the whole board.
Click to expand...
Click to collapse
I am thinking the same thing. Will try'em out now.
Its the Chinese version of honor 6 h60-L01 so was thinking of taking it to them whenever I visit China again.
May be I should try the local Huawei service center in Pakistan first but I am not so sure that they can solve it here...
muradulislam said:
I am thinking the same thing. Will try'em out now.
Its the Chinese version of honor 6 h60-L01 so was thinking of taking it to them whenever I visit China again.
May be I should try the local Huawei service center in Pakistan first but I am not so sure that they can solve it here...
Click to expand...
Click to collapse
It's worth a try though. They could tell you they can't repair it due to being a Chinese version, but they could also analyse the symptoms all tell you what repair is needed.
zinko_pt said:
It's worth a try though. They could tell you they can't repair it due to being a Chinese version, but they could also analyse the symptoms all tell you what repair is needed.
Click to expand...
Click to collapse
Nice. I will definitely do that now. Thanks.
muradulislam said:
Nice. I will definitely do that now. Thanks.
Click to expand...
Click to collapse
Well, today my son used my bricked honor 6 as a brick, its gone for good now, I guess
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Well, today my son used my bricked honor 6 as a brick, its gone for good now, I guess
Click to expand...
Click to collapse
That's hilarious and sad at the same time, I hope you get a new device ASAP
muradulislam said:
Well, today my son used my bricked honor 6 as a brick, its gone for good now, I guess
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
So which one you are gonna get now?
Sent from my PLK-L01 using Tapatalk
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Same thing here. Flashed wrong ROM via TWRP.
As a result, immediate loop (repetitive vibration, led blinking red) when connected via USB. No recovery access. Only fastboot access (blue led).
Locked bootloader.
Flashtool:
- tried flashing kernel.sin extracted from a stock ftf - no good (locked bootloader, unlocking requires flashboot which is not accessible).
- tried flashing system.sin extracted from a stock ftf - no good, flashtool says
INFO - Flashing selected system
and immediately after that
INFO - Please check the log before rebooting into system
So it clearly doesn't do anything. Any other approaches to try?
Tech core said:
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
Click to expand...
Click to collapse
Flashmode does not work, it starts cycling immediately.
Tech core said:
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
Click to expand...
Click to collapse
Yes, certainly.
Tech core said:
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or at least take a rest for what the heck is going on with your phone
Click to expand...
Click to collapse
Can't flash anything, so can't try it.
Tech core said:
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Click to expand...
Click to collapse
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
TheControlled said:
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
Click to expand...
Click to collapse
I didnt get your comment brief it to me
I have a conundrum. I bought an international S10e so I could root and run custom ROMs, even though I live in the US. While flashing with Heimdall, my USB controller flaked out and the flash failed hard. It left the phone in such a corrupted state, that it no longer will go into download mode or boot into recovery. When connecting it to a computer, it just goes to a teal screen that says the following:
An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
Click to expand...
Click to collapse
I installed Windows, the drivers, and the Smart Switch software, but the program refuses to see my S10e as a valid device for emergency recovery or otherwise. I took it to a shop to see if they could perform the reset, and they told me that Samsung US refuses to give them the necessary files due to it being an international model.
Are there any other tools I can use to perform this reset, or do I have to mail it in to Samsung?
it will go back into download mode again!
nakedhitman said:
I have a conundrum. I bought an international S10e so I could root and run custom ROMs, even though I live in the US. While flashing with Heimdall, my USB controller flaked out and the flash failed hard. It left the phone in such a corrupted state, that it no longer will go into download mode or boot into recovery. When connecting it to a computer, it just goes to a teal screen that says the following:
I installed Windows, the drivers, and the Smart Switch software, but the program refuses to see my S10e as a valid device for emergency recovery or otherwise. I took it to a shop to see if they could perform the reset, and they told me that Samsung US refuses to give them the necessary files due to it being an international model.
Are there any other tools I can use to perform this reset, or do I have to mail it in to Samsung?
Click to expand...
Click to collapse
---- connect it to a pc press bixby and volume down it may take a few tries but keep trying i had the same problem but am now up and running again if that doesnt do it make sure its off and connect to a pc again pressing power, volume down and bixby all at the same time it will go into download mode again i tried the smartswitch thing as well but useless.
martindar said:
---- connect it to a pc press bixby and volume down it may take a few tries but keep trying i had the same problem but am now up and running again if that doesnt do it make sure its off and connect to a pc again pressing power, volume down and bixby all at the same time it will go into download mode again i tried the smartswitch thing as well but useless.
Click to expand...
Click to collapse
I have tried all that many times. The phone will not go into download mode. Unless there is a way to perform the reset that it suggests without download mode, it is dead and I will have to mail it in to Samsung and fight with them about it. Are there really no consumer-available tools that can do this?
same screen
nakedhitman said:
I have tried all that many times. The phone will not go into download mode. Unless there is a way to perform the reset that it suggests without download mode, it is dead and I will have to mail it in to Samsung and fight with them about it. Are there really no consumer-available tools that can do this?
Click to expand...
Click to collapse
i had the same picture as you posted but was still able to get back into download mode keep trying or if youve given up trying then return it but its nearly impossible to brick these phones
just saying
i have the same problem, did you solve ?
maiki1 said:
i have the same problem, did you solve ?
Click to expand...
Click to collapse
I'm afraid not. Got a shiny brick on my desk, waiting in vain for some kind of low-level flashing procedure to recover it. At this point, its looking like it won't amount to much more than e-waste
nakedhitman said:
I'm afraid not. Got a shiny brick on my desk, waiting in vain for some kind of low-level flashing procedure to recover it. At this point, its looking like it won't amount to much more than e-waste
Click to expand...
Click to collapse
i find a solution with that mode odin see the phone and with the firmware ctg4 nothing is happen but i installed
new firmware dth7 with odin and that work my phone reboot in stock firmware
nakedhitman said:
I'm afraid not. Got a shiny brick on my desk, waiting in vain for some kind of low-level flashing procedure to recover it. At this point, its looking like it won't amount to much more than e-waste
Click to expand...
Click to collapse
I would gladly buy this off you if you don't fix it. Feel free to send me a pm as I'm never on here.
It's just soft bricked lol. I've been at this exact screen myself (S10e exynos). Just download Odin, Samsung USB drivers and stock ROM. Connect phone to PC, and Odin should detect it right away if I remember correctly. If not, hold power + volume down until the phone shuts off, then quickly plug it in while holding bixby + volume down. Try messing with it until Odin detects it and then just flash stock. I can assure you, it's fixable, nothing serious.
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