Database Users

[Q] Defy bricked. Wont turn on, only white led on pc

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 somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize 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 before 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?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_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 don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?

Niko. said:
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 somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize 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 before 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?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_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 don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.

htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing

Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...

Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help

Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"

Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk

thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.

htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...

Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?

[Q] Milestone 2 Bricked Helpp

Hello everyone, i need help. Yesterday i installed cyanogen 11 rom on my milestone, but when the phone boots, it said setup wizard stopped working and i couldnt do anything, after that i flashed my device with 2.3.4 version, from 2.3.6. At that time i didnt knew that that will brick my phone. So now it wont turn on...when i put it on the charger led next to charger/usb flashes, when i connect it to usb led stays on. I read a lot threads on the forum but no luck. I just need to enter to bootloader so that i can flash it again, i tryed it with camera vol down and power but now luck. Anyone knows another way?
Thanks in advance.

I fixed it by using battery bypass. I wont delete thread maybe will help someone.

nikolacirjakovic said:
I fixed it by using battery bypass. I wont delete thread maybe will help someone.
Click to expand...
Click to collapse
How to do a battery bypass on motorola milestone 2?

sssloba said:
How to do a battery bypass on motorola milestone 2?
Click to expand...
Click to collapse
look here and here

Tnx but this don't do the magic for me.. It's the same, only LED lights up and no reaction on button press..
I'll have to try something else.

sssloba said:
Tnx but this don't do the magic for me.. It's the same, only LED lights up and no reaction on button press..
I'll have to try something else.
Click to expand...
Click to collapse
Sorry, but it worked for me...did you fixed it some other way?

Nope, not yet.
I'll try this with another cable. Also, i find a tutorial how to make Motorola factory cable, and i will try that when i find the time.
I can't put links here now, but it's called "How to Make Motorola Factory Cable to Unbrick Your Android! " on Youtube, maybe it can help someone elese.
I'm not giving up. :fingers-crossed:

sssloba said:
Nope, not yet.
I'll try this with another cable. Also, i find a tutorial how to make Motorola factory cable, and i will try that when i find the time.
I can't put links here now, but it's called "How to Make Motorola Factory Cable to Unbrick Your Android! " on Youtube, maybe it can help someone elese.
I'm not giving up. :fingers-crossed:
Click to expand...
Click to collapse
I almost killed my M2 last week, all my fault. When battery is too low, cable bypass is not enough to turn on with vol down + camera. But there is another trick in RSD lite.
Put the bypass cable in the M2 battery & phone then connect bypass cable in a wall charger (computer usb port has not power enough). Now plug the data cable in the M2 usb then connect to PC USB port. Phone still appears to be dead if you try to power on (try it). Go to RSD lite 5.7 and click "Show device" until device properties shows something. Now ignore that your phone looks powered off and go ahead flashing with RSD.
After flashing you will need to do a factory reset as usual, turning on with X pressed until triangle appears. Note that in some M2 you go to wipe menu pressing @ one or more times in triangle screen, while on other M2 you press vol up + vol down to get wipe menu.
Mine was bricked for the same reason, flashed BL, 2.3.6, then because I could not wipe (didn´t know that there was two ways to get menu), I messed up the entire thing, flashing 2.3.4 - phone dead with side led on when connected. Battery does not charge in this state, so after discharged I recovered this way.

Progress
Ok, this helps a bit......I managed to flash my M2 but still no startup screen.
When I did what you wrote, RSD Lite v5.7 did show my device and it started flashing it, in some point the screen on my phone lights up and shows "FW update in progress.." . Everything finishes nice with no trouble...rebote and PASS...
But there is no Motorola icon shown, neither I can start in recovery mode, or bootloader mode or any other that i tried.
When I connect it to PC with data cable, it makes sound like the USB device is plugged in, and it also can be seen in RSD Lite as connected device but nothing on the M2 screen... Same thing happens when i press power button on the phone while it is connected with the data cable.
Any idea why?!
By the way, tnx for helping me this much! :good:

sssloba said:
Ok, this helps a bit......I managed to flash my M2 but still no startup screen.
When I did what you wrote, RSD Lite v5.7 did show my device and it started flashing it, in some point the screen on my phone lights up and shows "FW update in progress.." . Everything finishes nice with no trouble...rebote and PASS...
But there is no Motorola icon shown, neither I can start in recovery mode, or bootloader mode or any other that i tried.
When I connect it to PC with data cable, it makes sound like the USB device is plugged in, and it also can be seen in RSD Lite as connected device but nothing on the M2 screen... Same thing happens when i press power button on the phone while it is connected with the data cable.
Any idea why?!
By the way, tnx for helping me this much! :good:
Click to expand...
Click to collapse
Excuse me, what sbf version are you trying to flash? Do you know your current BL version?
Please note that some sbf requires bootloader upgrade to 70.13 first.
And there is not direct downgrade - i.e. once flashed GB, flashing froyo bricks M2. Actually even between GB versions, once installed a R01 GB sbf you can not flash any R00 GB sbf. Some downgrades only this way.
Also there is not BL downgrade.

lampwarez said:
Excuse me, what sbf version are you trying to flash? Do you know your current BL version?
Please note that some sbf requires bootloader upgrade to 70.13 first.
And there is not direct downgrade - i.e. once flashed GB, flashing froyo bricks M2. Actually even between GB versions, once installed a R01 GB sbf you can not flash any R00 GB sbf. Some downgrades only this way.
Also there is not BL downgrade.
Click to expand...
Click to collapse
I also think he's trying to downgrade. Perhaps he flashed Latin America ROM, and now he's trying to flash UK one. I don't know, but what he describes looks exactly what I experienced when I tried to flash Froyo over GB.
IMHO he should try to flash the latest ROM, that means Latin America 2.3.6 GB.

rabinhood said:
I also think he's trying to downgrade. Perhaps he flashed Latin America ROM, and now he's trying to flash UK one. I don't know, but what he describes looks exactly what I experienced when I tried to flash Froyo over GB.
IMHO he should try to flash the latest ROM, that means Latin America 2.3.6 GB.
Click to expand...
Click to collapse
Yes, that is exactly what happened.
After reading some more about this, I now understand what was my problem....
Playing with my M2 I installed some CM versions, 10, 10.2, 11... and finally when I wanted to go back to stock rom, I find newer version than mine was, and there is the first mistake. I installed it not knowing that I can't do a downgrade later.
Secound mistake was that i TRIED to go back to my old stock rom, and....black screen happend.:crying:
But thanks to your help I now know how to fix it. And i did! :victory: :highfive:
My BL is 70.13 , and when i checked my CG31 with "smgver" it show that it is v4.
I can't go back to my old rom, but now I can install costum or some BR/AR gb except for persona&vivo,which is 4 as Endless7 explaned in his text.
Now there is only one more problem... the battery cannot be charged. There is icon like it is being charged, and also it says charging 1% and always is 1%.
I have original battery and one that is not original...neither one of those two can't be charged.

sssloba said:
(...)
Now there is only one more problem... the battery cannot be charged. There is icon like it is being charged, and also it says charging 1% and always is 1%.
I have original battery and one that is not original...neither one of those two can't be charged.
Click to expand...
Click to collapse
When connected with a wall charger a discharged battery should jump to 20% in config, battery. If locked in 1%, probably there is a mess in the battery state variable.
If you are using a custom recovery, try to clear battery state on it and select the option to fix permissions.
Doing again the master clear/factory clear also may work, but needs to config all the phone again.
Another thing to consider, any short circuit or wrong wiring while doing the bypass cable may damage the charger (or battery, or phone), do you have a spare one to test?

lampwarez said:
When connected with a wall charger a discharged battery should jump to 20% in config, battery. If locked in 1%, probably there is a mess in the battery state variable.
If you are using a custom recovery, try to clear battery state on it and select the option to fix permissions.
Doing again the master clear/factory clear also may work, but needs to config all the phone again.
Another thing to consider, any short circuit or wrong wiring while doing the bypass cable may damage the charger (or battery, or phone), do you have a spare one to test?
Click to expand...
Click to collapse
I tried both of this things, and none of them worked. When powered on, without charger, on the battery icon stands [!]
and when it is connected with a wall charger, icon changes to little lightning ( standard charging icon) inside the empty battery, without movements (battery do not changes colors, red, yellow, green). On lock screen says: Charging 1%, and same on the battery settings (1%).
That was on costum rom.
And on the stock rom in the battery icon stands [?], and when I connect it to the wall charger it says (with original Motorola battery inside):
"Invalid battery
Your device battery is invalid and cannot be charged.
Replace the battery with an original Motrola battery."
I changed the cable, and the charger, but I do not have third battery...short circuit...maybe...maybe.
One interesting fact, the battery seems to be charging, although it says 1%.
The original battery was empty at the begining, she couldn't even start the phone, and now phone is working on that battery....strange. Should it be able to do that, if there was a short circuit?

As far as I know, flashing stock sbf overwrites most config files, also battery statistics. Maybe the easiest solution would be to buy a new replacement battery - at least here, in Poland they go for 7-8$ - quite cheap IMO.
I remember when I was using MS2 that once I had this question mark instead of battery status - it heppened when I drained battery to zero, phone was unable to boot to charging mode, so I booted from another battery, and with a wall charger plugged in, I replaced battery with empty one. Then question mark sign appeared when there was no battery, but I don't remember how I got rid of it. Maybe it disappeared after some time? I don't know. But for sure it disappeared.

sssloba said:
I tried both of this things, and none of them worked. When powered on, without charger, on the battery icon stands [!]
and when it is connected with a wall charger, icon changes to little lightning ( standard charging icon) inside the empty battery, without movements (battery do not changes colors, red, yellow, green). On lock screen says: Charging 1%, and same on the battery settings (1%).
That was on costum rom.
And on the stock rom in the battery icon stands [?], and when I connect it to the wall charger it says (with original Motorola battery inside):
"Invalid battery
Your device battery is invalid and cannot be charged.
Replace the battery with an original Motrola battery."
I changed the cable, and the charger, but I do not have third battery...short circuit...maybe...maybe.
One interesting fact, the battery seems to be charging, although it says 1%.
The original battery was empty at the begining, she couldn't even start the phone, and now phone is working on that battery....strange. Should it be able to do that, if there was a short circuit?
Click to expand...
Click to collapse
Battery sign with a "?" shows when battery is completely uncharged (and before the master clear in my case). Power off the phone, install the bypass cable (again) and put it in the wall charger with phone powered off. Wait 15 minutes charging before power on and wait more 15 minutes charging. Now remove the bypass cable and let battery charge as usual before powering on again.

I did all of that. I downloaded some battery widget, and it shows the battery state 100%. Same is when i go to Settings=About phone=Phone status, battery status is charged 100%. Now the only thing is that in the original battery status icon is still [?].
The important thing is that battery is 100% full and phone is not broken, it works! !
@rabinhood
I flashed costum and stock rom.
I have replacement battery, and same thing happens on it. Also I tried changing them while charging...nothing.
Maybe it will disappear by itself if I wait long enough. :laugh:

[Q] Jiayu S3 semi-hard brick (NOT BY FLASHING), help needed

Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.

Bump..
Anyone?

bump

Is my S7edge broken or bricked?

Had been rooted my phone before, didn't like it because I couldn't use my banking apps. Back to official firmware via Kies, been using for few months... no problem until yesterday. I charged my phone up to 92%, I unplugged and unlocked my phone, it restarted itself then never come back live again.
I used Smart Switch for another stock firmware flashing with no luck. The software skipped downloading from 85% to 100% immediately, it was ok installing system update on Smart Switch but when the phone completed and restarted, on the screen it shown "erasing" and "installing system up to 32%", it won't get pass above 32% except a blue dead android with loading icon, it freezes every time.
Full Album here, so you might get some ideas of what's going on...
http://imgur.com/a/Ad6dV
{
"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"
}
I went to Samsung store yesterday, however once they see knox has been tripped, they refused to fix my phone unless I pay for a new motherboard which will cost me £220. :crying:
I have been trying to flash any official firmware using both Smart Switch, Samsung Kies and Odin, Android 6.0 or 7.0 and every tools lead to blue led black screen or boot looping. I have tried at least 10 times of each methods, even ADB mode, but ADB won't offer much choices except 'adb sideload' commands but it verify each package. So I cannot install TWRP recovery and so on... Odin won't install TWRP recovery as well, it failed every time.
It is sad to see this phone die on me. I have never dropped this phone and it has 0 scratch on it... still looks brand new! If anyone of you could help me out getting this baby alive, I could pay you little money.
Thanks for your time!

lovetv said:
Had been rooted my phone before, didn't like it because I couldn't use my banking apps. Back to official firmware via Kies, been using for few months... no problem until yesterday. I charged my phone up to 92%, I unplugged and unlocked my phone, it restarted itself then never come back live again.
I used Smart Switch for another stock firmware flashing with no luck. The software skipped downloading from 85% to 100% immediately, it was ok installing system update on Smart Switch but when the phone completed and restarted, on the screen it shown "erasing" and "installing system up to 32%", it won't get pass above 32% except a blue dead android with loading icon, it freezes every time.
Full Album here, so you might get some ideas of what's going on...
http://imgur.com/a/Ad6dV
I went to Samsung store yesterday, however once they see knox has been tripped, they refused to fix my phone unless I pay for a new motherboard which will cost me £220. :crying:
I have been trying to flash any official firmware using both Smart Switch, Samsung Kies and Odin, Android 6.0 or 7.0 and every tools lead to blue led black screen or boot looping. I have tried at least 10 times of each methods, even ADB mode, but ADB won't offer much choices except 'adb sideload' commands but it verify each package. So I cannot install TWRP recovery and so on... Odin won't install TWRP recovery as well, it failed every time.
It is sad to see this phone die on me. I have never dropped this phone and it has 0 scratch on it... still looks brand new! If anyone of you could help me out getting this baby alive, I could pay you little money.
Thanks for your time!
Click to expand...
Click to collapse
Take a look here https://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878/page12
post #114

mrsmtt said:
Take a look here https://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878/page12
post #114
Click to expand...
Click to collapse
I've tried this solution more than 10 times with no luck

Have you tried flashing the boot.img recovery.img ect separately? I had this kind of thing on a different Samsung and i fixed it by flashing each one separate.

Clarkiieh said:
Have you tried flashing the boot.img recovery.img ect separately? I had this kind of thing on a different Samsung and i fixed it by flashing each one separate.
Click to expand...
Click to collapse
That's good idea, which option should I use in Odin? Should be AP option right?

The files should work with their own options I'm not too sure which ones work with which, and there is a set order to flash in as well which I'm not sure about either.
---------- Post added at 03:47 PM ---------- Previous post was at 03:38 PM ----------
They all have their own button I think pal

What about fastboot flash?

I finally revived my phone!!! I'm so happy right now
I'll provide these solutions if anyone has the same issue like me. What I did altogether was:
1.0) Remove devices from your Google accounts (I had 2), wait for 48 hours to cool down? Although not sure if this option caused the bootloop, might be useful for someone...
1.1) Downloading the oldest firmware from https://www.sammobile.com flash it using Odin 3.11.1
1.2) Upload BL, AP, CP and CSC files, but I uploaded the correct Pit file too! WARNING: Be sure you know what you doing before trying to mess with this! Otherwise don't try pit file! Leave the options by default! Unless you ran out of choices!!! but I've ticked auto reboot, re-partition, f.reset time, nano erase all and bootloader update for my case. Then start to flash of course.
2.0) Phone were still crashing upon system update... I waited out the battery to drain up. Until next day... Tips: If there's no led light, try to sense it with your face if there's any temperature
2.1) Plugged in ur phone and see if there's the battery charging icon. If there is, you're in luck.
2.2) Charge until 100%, turn it on. Hopefully you can boot up now but I couldn't...
3.0) My phone was still in boot looping (Samsung Logo), I had to turn on recovery mode and wipe + format system then mount /system for whatever reason... then restart using the recovery mode...
3.1) At this time, I finally past through the boot loop which I'll be in the Google sign in screen!
4.0) Phone was in the oldest firmware, of course I will update the official firmware automatically, however the first update didn't make it, and stucked on Samsung logo again!
4.1) All I did was wait a little bit about (25mins) and reset again... somehow it fixed the issue and boot back in.
4.2) Then system update every single firmware up to the latest, boom! I'm on the latest firmware again and everything is up and running!
5.0) Extra tips: Make sure you have up to 60% battery life before turning on recovery mode, but I had to charge up to 100% for my case.
5.1) Remove FRP lock (google accounts, remove devices) might help?
5.2) On recovery mode, wipe cache and format system again might help too!
Good luck guys, I was about to give up trying after 20 flashes (Smart Switch, Kies, and Odin with different pc too!) and had to wait for battery to drain everytime if it stucks! Which annoys me but I made it!!

Glad you got it sorted ?
I would recommend Batman ROM if your willing to flash again.

Same happen to my Phone many times!
Solution!
After a few Reboots your Phone will stuck with screen of or may a blue led on (pulsing) or without any reaction (black screen, all led off) !
Now you have to wait until your battery will be empty compl. Can be up to 18 hours and more! depend how much your Mobile was loaded! or until Led light is off! is your phone still warm? Than it is still draining!You have to wait untill it is complet off and getting cool. Or, if u can, get it in the download mode, with sreen on it will be decharged faster! but mostly your phone will stay death.
After all that, Phone is cold and no Led is illuminated, plug your Phone to usb charging! Wait a little time until you can see the normal charging screen and orange Led is illuminated! (if charging screen will not upper, you have to wait longer!for decharging battery)
let it charge untill it is complet full! Dont touch! Wait at leasst 8 hours and more with charger still connected ! Best is overnight.
after this usely your phone will start normaly , without loosing any data!
Thats what helped me many times!
All my tries with bootloader, software brought nothing, just lots of waisted time and lost Data! you not need to del your phone at google!
Try this, it will work

Vollidiot said:
Same happen to my Phone many times!
Solution!
After a few Reboots your Phone will stuck with screen of or may a blue led on (pulsing) or without any reaction (black screen, all led off) !
Now you have to wait until your battery will be empty compl. Can be up to 18 hours and more! depend how much your Mobile was loaded! or until Led light is off! is your phone still warm? Than it is still draining!You have to wait untill it is complet off and getting cool. Or, if u can, get it in the download mode, with sreen on it will be decharged faster! but mostly your phone will stay death.
After all that, Phone is cold and no Led is illuminated, plug your Phone to usb charging! Wait a little time until you can see the normal charging screen and orange Led is illuminated! (if charging screen will not upper, you have to wait longer!for decharging battery)
let it charge untill it is complet full! Dont touch! Wait at leasst 8 hours and more with charger still connected ! Best is overnight.
after this usely your phone will start normaly , without loosing any data!
Thats what helped me many times!
All my tries with bootloader, software brought nothing, just lots of waisted time and lost Data! you not need to del your phone at google!
Try this, it will work
Click to expand...
Click to collapse
My phone turned out to be a faulty motherboard, went to Samsung support centre and they repaired for me within 3 working days. Now I got a sort of a new phone, it has 0 scratch since I bought it last year Feb, so it's like a new phone to me :laugh::good:
But yeah, motherboard was acting weird, was lasting a week then breaks again... finally motherboard was dead, so I could repair it without seeing the knox being triggered. Phew

poco m3 does not turn on anymore

I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.

you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.

vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
And how can I flash the firmware? I've tried using the Xiaomi Flash tool but it asks me for a Mi account that is valid for the process.

charecktowa said:
And how can I flash the firmware? I've tried using the Xiaomi Flash tool but it asks me for a Mi account that is valid for the process.
Click to expand...
Click to collapse
unlock bootloader. install twrp. flash firmware

charecktowa said:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
Click to expand...
Click to collapse
Drain out your battery and then just plug the charger then wait.
I had this happen to me 2 times now,it would take days if your phone fully charged like mine,it takes 5 days.
After that,
make sure to backup your phone,unlock your bootloader and then re-flash the stock rom with Mi-Flash or just use another rom to your liking.
The truth is I like the stock MIUI than any other rom but if this kind of problem keep happening,I rather just flash another rom.
Hopes this help fixing your phone,sorry for the rant there.

Biggest problem with this phone is , there's no way to force reset the phone. I literally tried everything from vol up + power and volume down + power and everything else Buying this phone is prolly one of the biggest regret of my life. And the youtuber xiaomi slaves didnt help. But my real question is.... Will flashing custom rom fix this problem?

yankee77 said:
Biggest problem with this phone is , there's no way to force reset the phone. I literally tried everything from vol up + power and volume down + power and everything else Buying this phone is prolly one of the biggest regret of my life. And the youtuber xiaomi slaves didnt help. But my real question is.... Will flashing custom rom fix this problem?
Click to expand...
Click to collapse
Same question...i have experienced deadboot in this poco m3 4 times already...the only option is to remove the battery and put it back again...then hold power button to turn it on...no fastboot...no recovery mode...i dont have a choice but to open it and remove the battery...now...my question is...What if i flashed a custom rom...will it fix deadboot issue on this phone?

charecktowa said:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
Click to expand...
Click to collapse
have you try test point?

Hopefully this doesnt happen to anyone.. saw this vid on youtube. Basically poco m3 doesnt turn on even when battery connectors removed.

yankee77 said:
yankee77 said:
Hopefully this doesnt happen to anyone.. saw this vid on youtube. Basically poco m3 doesnt turn on even when battery connectors removed.
Click to expand...
Click to collapse
It did happen to me and I did pull the battery connector even pull the display connector while doing it.I read a post on reddit about it,pull the battery and display connector and then try connect it back while pushing the power button,the guy said the phone did turned on but whenever he tried to restart,phone would not boot and he would repeat that unplug,plug,hold power thinggy .I did try the method but nothing happened.Plug in to pc would only detect it as in EDL mode,with a locked bootloader theres nothing I can really do as flashing it would only met with this and that error.Then I read someone on a forum said to just let the phone fully discharged and try to plug in charger and wait for the battery empty logo pop on screen then the phone would boot as normal.It did work for me but I gone through nearly 5 days as my phone was fully charged.Its been like 4-5 days now and eventhough I already downloaded the latest ota for miui global,Im still dreading to install it as Im afraid the same problem would occurs again.Maybe I should unlock my bootloader first so the next time my phone goes EDL mode again,things would get easier to do.Sorry if this rants of mine a bit too long.
Click to expand...
Click to collapse

i did a factory reset.... but the phone didnt turned back on. i did do the ota update three times prior to this one which failed three times. .. the first one prolly broke the recovery and fastboot mode ... im not sure what to do after this. since i cant go to recovery or fastboot mode. this is prolly the first time i experienced this. where the ota itself which is supposed to make the phone better broke the phone. it will prolly turn on after it got drained but im not sure how to update firmware without recovery or fastboot and yes this is a ****ty phone and company alright. i send my logs to xiaomi. and still no response from them.

tnx sa share boss malaking tulong

when i heat ( about 3 to 5 sec. or more with soldering iron and flux) camera power ic under ( Power Control IC PMI632-902 ) the phone boots up
HCBE AKD written on this ic
in some other m3 phones that text is different
it has 4*3 pin under lower left side of shield
phone boots up with this method one time
if you use flux phone will be good till 1 hour power off then problem comes back
i neeeeeed schematic diagram of this phone's motherboard...
in some cases when you unplug battery
then short circuit with power key
then plug pc usb till flashing screen
after that i connect battery with holding down power key and usb connected
phone powers on from edl mode to normal mode (in some cases lcd flashes in some other battery icon shows rapidly and gets off)
ow in cit mode #27-charger test some phones we have red text battery test fail insted blue text that ask reverse plug usb type c connection)
is there another test or somting else???
{
"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"
}

does the phone go to fastboot with adb

Any update on this?
I have this same problem

How can I drain the batter ?

vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
after you reflashed, did you encounter the same problems again?

pidliget said:
does the phone go to fastboot with adb
Click to expand...
Click to collapse
no just edl mode
phone current in charge is about 100 mAmp
if you heat motherboard phone turns on get charge normally and every thing is ok till you get reboot or turn phone off

vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
How do I drain the battery

ArcherXY said:
How do I drain the battery
Click to expand...
Click to collapse
Poco m3 drains battery by itself. General rule of the thumb
1-10% - 0 to 1 day
11-20% - 2 days
Basically 1 day is around 10% of battery
I think the motherboard is on but for some odd reason the display board and basically the whole thing doesnt turn on on. But it still is draining battery even when turned off. Removing the battery doesnt fix it. I tried several times