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
Dear all,
I have only recently lost my IMEI und tried everything to recover it. As a matter of fact I had made a backup before and tried to restore it and it didn't work. Today, I tried doing that another time and after that I wanted to reboot my phone but after it shut down it just doesn't boot up anymore. It shows nothing, only the black screen. It seems like it doesn't react to anything, I also tried to pull the battery but that also wasn't successful. I also can't get into Download Mode.
Any ideas what I could do?
Charge the battery or try another battery first .
I did both, I charged the battery but it didn't help and I also tried another (fully charged) battery, without success.
try to connect with kies 3
Kies doesn't recognize my phone.
Service centre repair your next step .
I'll let my carrier send it to Samsung and tell them that it crashed after trying to update to Lollipop via Kies, I read that this worked in some cases. If it doesn't I'll have to have it repaired.
What do you guys think about those "USB jigs"? Do you think those could help me with my problem?
YAAAAY!
Thanks to this thread http://forum.xda-developers.com/showthread.php?t=2625332 I was able to unbrick my device and by flashing a new PIT-File and a Stock ROM even my IMEI came back. I think my partition was somehow messed up because after flashing the PIT-File it began to work properly, but I flashed the Stock ROM to have a "clean" system again and installed Cyanogenmod afterwards with success.
So how does this fix work if the phone is unable to connect or power on ..
OP yes try the usb recovery jig to see if it boots to download mode .
Well, it did help. After I had put the Image on my SDcard and removed my SIM card I was able to boot my phone, this was the main issue. The rest was child's play, I flashed the PIT-file and a stock ROM and everything was working fine again.
flash new PIT file
hi you got to flash a new pit flie. maybe something damaged your phone boot. look in here
http://forum.xda-developers.com/showthread.php?t=2625332
I'm banging my head and have been working on this for a few days now. I have an X727 that all of a sudden went into the death boot loop, and all I can get to is the fastboot screen. I can connect via fastboot and push flash files etc, but I cannot connect via adb no matter what I try. Device drivers are correctly recognized (Win10 x64) and all fastboot functions work. I successfully unlocked and rooted it after this happened (in order to push new images). This thing was bone stock beforehand.
I've tried flashing every version of recovery I can find and nothing works - I always either end up back in the loop (stock recovery) or in a screen with distortion (twrp). I've attached an image of what the screen looks like with the latest twrp recovery flashed.
I'm hoping anyone can help here, I'm just about out of ideas. Thanks in advance for your expertise!
Well I finally got the phone to be recognized in qfil mode and tried to force the factory ROM back onto it. The process, using FlashOne, appears to work, but the phone remains in an endless boot loop.
Anyone have any ideas? Really stuck here...
Thanks!
CltFlyBoy said:
Well I finally got the phone to be recognized in qfil mode and tried to force the factory ROM back onto it. The process, using FlashOne, appears to work, but the phone remains in an endless boot loop.
Anyone have any ideas? Really stuck here...
Thanks!
Click to expand...
Click to collapse
Before you had it only going fastboot what did you flash.
Sent from my SM-A730F using xda premium
mchlbenner said:
Before you had it only going fastboot what did you flash.
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Nothing - The phone was bone stock and started going into a boot loop, recovery did not work (when entering recovery mode it would exit after a few seconds and reboot). The only thing I can get to is fastboot. adb does not recognize the device at all, but fastboot does, as does the low level qfil drivers.
BUT - no matter what I push to the device it remains in the exact same boot loop. I cannot even get the (supported) TWRP to boot after I successfully flash it (either via fastboot, the Tool All In One util, etc). The boot loader is unlocked (I did that first before trying to TWRP it).
Any ideas at all before I buy another phone? REALLY appreciate the help!
I have same problem
Bumping, hoping for any traction here. I'm willing to try anything to get this phone working again (it's now a matter of principle).
I thought that the Qualcomm chipset was supposedly "unbrickable". If that's the case then I would love to understand where the failure point is...
Wish this reply was to help you, but I'm experiencing the exact same problem. Phone was acting a little laggy this morning. Turned it off and turned it back on. It shows LeEco, vibrates twice, and then loops again. Pressing Vol-Up brings it to a LeEco - RECOVERY screen, but it only sits for 2-3 seconds before rebooting again. Pressing Vol-Down brings it to fastboot, and that's about it.
I haven't gone so far as to install TWRP or anything, but this is a completely stock phone updated to 20S.
What the hell happened to our phones??
Is there any way to recover any of the data?
I hear you dude - thanks for the post anyway, there is something to be said for shared misery. FWIW, I never got the dang thing to respond. I let the battery fully drain (I left it in recovery mode then the low level mode as long as it would stay on, then let it sit for two weeks after that). Same thing - I can hit it with fastboot but NOT ADB, I can write flash files to it, it looks like I'm pushing TWRP correctly, but when I try to reboot into recovery - NADA. Just goes back into it's normal boot loop, never hits recovery.
I'm starting to wonder if there is a mechanical problem with the phones. Maybe a flex cable that eventually wiggles just loose enough to do this.
What I'd REALLY love is to find *any* answer - I can't stand a problem like this that never gets explained. So with that said, does *anyone* have *any* other ideas? I'm an electronics guy, I have rebuilt too many phones to count, etc - I can try whatever *valid* suggestions y'all might have.
Thanks for letting me rant, I LOVED this phone (and it's sister, bought exactly the same time, is still rock solid).
</soapbox>
CltFlyBoy said:
I hear you dude - thanks for the post anyway, there is something to be said for shared misery. FWIW, I never got the dang thing to respond. I let the battery fully drain (I left it in recovery mode then the low level mode as long as it would stay on, then let it sit for two weeks after that). Same thing - I can hit it with fastboot but NOT ADB, I can write flash files to it, it looks like I'm pushing TWRP correctly, but when I try to reboot into recovery - NADA. Just goes back into it's normal boot loop, never hits recovery.
I'm starting to wonder if there is a mechanical problem with the phones. Maybe a flex cable that eventually wiggles just loose enough to do this.
What I'd REALLY love is to find *any* answer - I can't stand a problem like this that never gets explained. So with that said, does *anyone* have *any* other ideas? I'm an electronics guy, I have rebuilt too many phones to count, etc - I can try whatever *valid* suggestions y'all might have.
Thanks for letting me rant, I LOVED this phone (and it's sister, bought exactly the same time, is still rock solid).
</soapbox>
Click to expand...
Click to collapse
Welp, I tried using FlashOne2.0 and QFIL to flash when I got the phone to Qualcomm 9008 mode. After trying it a few times, I got it to flash successfully. Same problem. Didn't help it one bit, FYI.
What I did notice was that the phone was a little laggy and warm so I decided to restart it. Do you think it's a heat issue causing solder to come loose from a chip? It's happened to a laptop before -- it could be causing our issues? Did your phone run hot? I have a dual layer case on mine so it did run hot sometimes...just spitballing some ideas.
That would definitely be a possibility - heat cycling causing an already suspect solder joint to fail is common. Granted, not as common with SMD devices or BGAs like the processors, but still, it happens. That would make a lot of sense too. I'd love to tear into it and look for physical problems - I just dread taking the dang screen off just to get to the insides, I can see me snapping the thing now...
I'm trying to repro the entire thing on a completely different computer - fresh drivers/everything. Will update if I see any success.
Well crap, no joy. Got very excited as QFIL looked like it worked (pushed le_zl1_qfil_ufs_fix), pulled the phone off the computer, booted, back into the same boot loop. Dangit.
I need to learn how to give up sometimes.
CltFlyBoy said:
I need to learn how to give up sometimes.
Click to expand...
Click to collapse
You and me, both. I tried every version of the qfil files I could find. No dice on any of them.
Not sure what else we can do at this point in time. The kicker is that I've had this phone less than a year but I can't find any way to contact LeEco USA. None of their numbers work and they haven't replied to any e-mails I've sent.
ME TOO
epikfone said:
you and me, both. I tried every version of the qfil files i could find. No dice on any of them.
Not sure what else we can do at this point in time. The kicker is that i've had this phone less than a year but i can't find any way to contact leeco usa. None of their numbers work and they haven't replied to any e-mails i've sent.
Click to expand...
Click to collapse
x727
i have the same problem
and it's a good phone to be losse
it happened with the phone after i make an update for android 9
if i have some novelty tell me, every day i have try doing something, and nothing works
flashone 2.0 almost all roms
fastboot i did not try yet ...
if have any news share please
grateful
I have the same problem to
Was anyone able to fix the problem? I got the exact same problem yesterday in the night. Out of nowhere it started vibrating twice and now it's stuck in this loop and with a "broken" white/black screen sometimes. No idea what to do.
On another note, is there anyway to access my files via fastboot?
I have the same problem last week and did same as everybody. Endless boot cycle even after QFIL and flashpro. I am certain it is a hardware issue.
I was using Lineage 16 and it ran hot so I put it on extreme battery saver and this helped the issue. I was just bout to change roms but been putting it off. I had it in the car next to car vent with heat blowing and google maps on. I noticed it was hot, not burn hot though. 4 hours later was using it and it had same graphical glitch problem. I'm sure it has to be disassembled and inspected, and maybe heatgun on a BGA chip or some flash memory.
That sucks! Well, I am pretty sure I am not going to be able to fix my phone, but do you know if there is a way to recover my files, using only fastboot and my pc?
Thanks!
ricecrispi28 said:
I have the same problem last week and did same as everybody. Endless boot cycle even after QFIL and flashpro. I am certain it is a hardware issue.
I was using Lineage 16 and it ran hot so I put it on extreme battery saver and this helped the issue. I was just bout to change roms but been putting it off. I had it in the car next to car vent with heat blowing and google maps on. I noticed it was hot, not burn hot though. 4 hours later was using it and it had same graphical glitch problem. I'm sure it has to be disassembled and inspected, and maybe heatgun on a BGA chip or some flash memory.
Click to expand...
Click to collapse
Count me in. Same issue. Have tried every QFIL. Every adb, fastboot, recovery, rom possible. All in one tools etc etc. There is something missing from the 727 for sure that no one has access to.
ampped101 said:
Count me in. Same issue. Have tried every QFIL. Every adb, fastboot, recovery, rom possible. All in one tools etc etc. There is something missing from the 727 for sure that no one has access to.
Click to expand...
Click to collapse
If you create a TauBao account ( free) you can have the phone repaired in China. The turn around time is 6 weeks. But apparently you pay $10 down and if the repair is simple resoldering ( most likely) it will cost $30 https://item.taobao.com/item.htm?sp...OXhfJ&id=559560190173&ns=1&abbucket=17#detail
No doubt it seems risky, but may be worth the risk, they seem legit to me and have a lot of positive feedback
Good Luck
PS Use Google translate
the same problem
interesante, exactamente me sucedio lo mismo, estaba utilizando lineage os 16 oficial y recibi una actualizacion, como no tenia bateria suficiente pospuse el reinicio y se apago por falta de carga, al encender me quedo en bootloop, el telefono entra a fastboot y se mantiene encendido, igual funciona con qfid y flashone 2.0, flash todos los archivos pero al reiniciar sucede el mismo bucle... algo me hace pensar que las tablas de particiones en la memoria flash estan corruptas y por eso a pesar de flash con exito, la particion boot o firmware esta dañado
CltFlyBoy said:
I'm banging my head and have been working on this for a few days now. I have an X727 that all of a sudden went into the death boot loop, and all I can get to is the fastboot screen. I can connect via fastboot and push flash files etc, but I cannot connect via adb no matter what I try. Device drivers are correctly recognized (Win10 x64) and all fastboot functions work. I successfully unlocked and rooted it after this happened (in order to push new images). This thing was bone stock beforehand.
I've tried flashing every version of recovery I can find and nothing works - I always either end up back in the loop (stock recovery) or in a screen with distortion (twrp). I've attached an image of what the screen looks like with the latest twrp recovery flashed.
I'm hoping anyone can help here, I'm just about out of ideas. Thanks in advance for your expertise!
Click to expand...
Click to collapse
Hi Everyone!
I have an XT1641, which previously had a charging pin problem.
At the Last week, it started to reboot only many times until it suddenly shut down and didn't light anymore.
When plugged into a charger, the white light flickered.
Since I thought it was still a charging pin problem, make the change.
The cellphone works seemed to restart, but it continues with the same problem.
Sometimes the bootloader works ( Power + Vol -) and sometimes No.
I already tried everything. Install ROM STOCK, I made it blankflash (none worked "waiting for firehose to get ready" ).
It seems to be a firmware or similar problem, but I can't find the solution.
Previously, you never had a custom ROM installed, or root, or anything; at this cellphone
Thank you!
PD: SORRY FOR MY ENGLISH
How did you try for installing stock rom? Check usb drivers installed in your pc
przvlj said:
How did you try for installing stock rom? Check usb drivers installed in your pc
Click to expand...
Click to collapse
By Fast Boot (when it worked).
Now, after a week of turning it off, the cell phone turned on again without problems.