Hello,so here's what happened with my device,I've tried to flash a new rom on it everything was just fine until I've clicked the "Download" button in sp flash tool. All drivers were installed correctly but when I wanted flash the rom the phone was surprisingly disconnected from my pc. Now it won't boot,I can't access recovery,the only thing is doing is that when i plug it in only the led is on, the screen is always black,I've tried to re-flash different roms but nothing to do,the tool gives me this error every time "s_dl_get_dram_setting_fail (5054) and sometimes this one s_ft_enable_dram_fail (4032)". I did a lot of forums searching,tried almost everything,but always I'm stuck with this. If anybody can help it wold be so nice!
I've forgot to mention it's a 7040A model.
Related
I too have a focus that is stuck in a loop at the Samsung logo. I bought it like that thinking I might be able to resurrect it as another toy. I have had lots of experience with Samsung, HTC and Sony droid phones, this would be the first WP.
It is a I917R on Rogers, there is no hardware revision under battery. I am assuming it is V1.3 as I have only seen software for the that version posted. I do not know how the phone got to its present state. They just said it happened during normal use?
I can get to both download mode and factory reset. I have flashed the stock rogers files without errors, but I never get the screen connecting to pc. The phone just restarts after successfully flashing, only to reboot continuously. I have been able to install MAGLDR and flashed every v1.3 ROM i could download. All without errors, just the same outcome they all just keep displaying Samung logo and then reboot. Only thing I noticed is that when I flash MAGLDR and custom ROMs it takes the phone longer to reboot.
I never get the connect to pc if I hold camera and power, nor do I ever get that screen when I flash a ROM.
Not sure if situation is similar... I am puzzled?
Your situation is very similar with other folks' here, unfortunately. It's not clear what causes it and there's no solution as of yet. For some, re-flashing worked. For others, a new battery. Most are stuck on loop...
When you connect the phone to USB when in download mode, what do you get?
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
blackangel21 said:
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
Click to expand...
Click to collapse
I see. What messages do you get when you connect the phone to the PC via USB, in either mode?
No messages, just shows up as Samsung USB composite device, Samsung mobile modem and Samsung mobile modem diagnostic serial port in download mode.
In magldr it shows up add Microsoft USB sync.
The only thing I forgot to mention was that when I flash with WP7 it finished without error in 90 seconds, but on the phone it says it will take 10 minutes.
Not sure what more I can add...
You could try different downloaders. Please see this thread for 7.41 downloader, maybe that helps?
Tried both, same outcome... No errors, just keeps rebooting... No Connect to PC message.
Im having the same problem. And i can see many other people who are having the same issue also. So i think its time to dump those phones, not worth a penny. The one i have in here was actually working, i followed all the directions in order to flash it. And still the phone got stuck into that bootloop. Its ridiculous from what i can see. I think ive read once you put that SDmini in it the phone will use it for the OS. But the one i had was working actually without it, i could turn it off as many times as i wanted and nothing happened. But if i tried a factory reset data would stay and diagnosis mode wasnt working. So i decided to flash it. Big, huge mistake! Hope you have better luck than i did. Because im dumping this one....
Same problem here, ive checked a couple of threads and no solution so far
hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help
Reposting it here, since this is the Lenovo sub-forums. Probably may find more help here.
I was using the Allegro ROM for the A1000G and it was running fine and dandy without any problems. Last night I tried installing a game and after I restarted it, it didn't turn on. I thought that maybe the device had low battery or something. So I plugged it in and let it charge for an hour and it still didn't turn on. Than I let it charge overnight and in the morning, it still doesn't turn on. So I tried to flash the Stock ROM for Lenovo a1000g and I got an error saying the storage was different or something - Error 3182 Message: BROM ERROR: S_STORAGE_NOT_MATCH (3182) [Edit - Tried to find the error, this is the one]
It was probably because the Allegro ROM was installed before it stopped working. So after that failed attempt at Flashing the Stock ROM - I don't get the battery indicator anymore and no matter what I try inside SP Flash Tool, it doesn't detect the device and the flashing process doesn't work. I tried installing and uninstalling all the MTK and Mediatek drivers but still not working. It shows up as MediaTek DA USB VCOM (Android) but it doesn't disappear, unless I remove the usb cable.
Before when I flashed the Allegro ROM and as seen across other youtube tutorials and guide, the device would show up for 2-4 seconds before disappearing and the SP Flash Tool would start working. Now it is just blank and the MediaTek DA USB VCOM (Android) doesn't go, no matter what.
Please, I would appreciate help. Since I don't have much knowledge regarding this. What must I do? I am depending on you guys.
~Aaron.
Bump. Please someone help.
**EDIT**: Had to send the phone back as the bootloader was locked and nothing was flashing. I believe they EDL flashed it and all is good now. Unlocked the bootloader on the new one just in case this happens again, I will be able to fix
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BACKSTORY:
Okay, so I recently updated to MiUI 12 and it wasn't great. My apps were crashing all the time and the general stability was not good. (this was around a week ago)
Then earlier today, my device just went into the boot screen (the colourful MiUI one) and stayed there for over 30 mins.
I forcefully restarted my phone using the volume buttons and it would go into the first "Mi powered by android" screen and then back into the colourful MiUI screen.
Then it would stay in the MiUI screen for a minute or so, and then restart itself, continually repeating the process.
At this stage, I had no custom recovery, had not tried to tinker with the phone (other than disabling some default apps through FastbootTools), and everything was fine until MiUI 12 came.
WHAT I DID:
I was able to access the default XiaoMi recovery (3.0?) and tried to wipe the data and restart, but nothing would change.
I tried to use the MiPC Suite after selecting in recovery, but it would recognise my device, even after updating to latest version.
I tried to use FastBootTools, but that would also not recognise my device.
I tried to use XiaoMiTool V2 (by Francesco Tescari), and that did recognise my device. I selected "my device is bricked" option and it did its thing, downloading and trying to sideload something. And then on the device, it got stuck at 4.99% with a message "You won't be able to turn on your device if you try to reboot it", and on the XiaoMiTool, the progress was at around 400% and said -70 seconds remaining, and around 40000MB / 3000 MB or something along those lines. Basically, **** was ****ed.
So I just let it sit there for a bit and then the XiaoMiTool V2 gave and error, "miui sideload failed adb execution exception adb sideload exited with status 1"
I had 3 options,
"Retry step"
"Go back to previous step"
"Cancel and abort"
I tried to search what the error was, but all of the results came from years ago, for different devices. So I clicked "Cancel and abort", only for the device to remain unchanged (4.99%, You won't be able to turn on your device if you try to reboot it), while the XiaoMiTool V2 went back to the start screen.
So I tried it again, the "my device is bricked option", and went through the same steps, and now it is stuck at "Pushing file to the device via ADB, ..., Starting MIUI sideload procedure".
Now I am stuck. My phone screen just says
"4.99%, You won't be able to turn on your device if you try to reboot it"
and my XiaoMiTool is stuck on the beginning sideload procedure.
Closing
If you managed to read this far, thanks, even if you don't have a solution. I appreciate anything that could help with this situation.
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Badis st said:
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Click to expand...
Click to collapse
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
coolboy328509 said:
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
Click to expand...
Click to collapse
Try another computer and another USB port...
The solution will benunder fastboot. You have to unclock your bootloader and flash a custom twrp or flash a stock rom using miflash
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
EdoDT99 said:
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
Click to expand...
Click to collapse
this is totally the wrong thread for ur device
So yeah, I screw up by a lot, but let's see if someone can help me/
I tried to update twrp on my phone and it got bricked, ADB was not seeing the device but Mi FlashTool was with a code but not COM, tried changing the phone drivers brom 900E to QL8000 and it got registered by MiFlashtool as COM and another code, the phone was still showing there even if I could not make the phone go to fastboot mode, just blackscreen; I tried to reinstall stock rom with it but got stuck at "flashing", disconnected the phone, the phone was still bricked in a black screen, when trying to reconnect the phone again to the pc, Win10 now displays an error
https://imgur.com/a/VS1yh6t
,
https://imgur.com/a/4PxUD7E
, I already tried uninstalling the device, deleting and reinstalling the drivers (unable because for some reason they won't appear now, but already tried installing the from their 1st party and prom MiFlashTool), so the phone won't turn on, display anything, go into recovery/fastboot, and I don't know what to do now, is the phone lost? I hope you can help me with this issue.
Hello Bro. Try install latest Mi Flash Tool latest version and then install the drivers. For my it's works in windows 10.