Hi, i couldnt find anything on google and youtube, so im here to ask you.
Every bricked situation has a USB Logo on screen or Android logo with ERROR message, BUT i have nothing on the screen. Just opening vibration and it keeps vibrate over and over again in 5-10 min. I dissambled my phone and disconnect battery from mainboard and re-connect it. It just keep vibrate when i re-connect it and it begins a loop. No led when charging, no adb connection (device not found error). Like i said, it keeps vibrate after 5-10 min last vibration. The time it vibrates again, adb finds my device but then it just lost connection.
HOW IT HAPPENED?
1. I was using official android 5 rom with root, I didnt get android 6 update
2. I tried to flash it via Recovery mode but it just didnt get in Recovery mode and it shows an ERROR message on screen. So i googled it and found a few solutions like wipe cache
3. I get in Recovery mode and tried to wipe cache again, but it stuck like 10 min so i forced close my phone. AAND no system i have.. It just didnt opening, ASUS logo with loading circle..
4. I flashed TWRP via ADB
5. so i tried to flash android 6 zip file via TWRP
6. it stucked, i waited over 10-20 min and i forced it to close(it stucked in "Splash screen installing", i though it must last like 1 min or 2 min maybe, its not the system its just opening animation)
7. NOW I HAVE A BRICKED PHONE WITH NO LED NO SCREEN JUST OPENING VIBRATION, cannot connect to adb, cannot get in recovery mode, nothing
Please give me some advices, im ready to try everything that can return my phone back.
English is not my native language, sorry for the huge grammer mistakes. I'm in a hurry and cant think about how can i make a sentence with perfect grammar.
up
This is the best guide : unbrick
Same PRoblem
if u get the solution please send it to me too at [email protected]
please update the links... i can't download the files i need.... thank you in advance...
This happened to me also . In my case i leaved my phone on charge (it was on low battery ) its keeps vibrating in 30 sec - 1 min interval , After some hours of this it finally booted to recovery (but i then rebooted bootloader then safe thing happens . Again after some hours it booted to recovery ) ,then i flashed stock ROM ,it failed but bootloader was back.
Hit Thanks if i helped.
Well, this happened with me, I needed open My phone and unplud batery cable and plug again. Easy to do.
same situation
I am facing the same issue at the moment.If you did fix it ,please reply with the solution or mail it to me at [email protected]
Thanks in advance
Related
hey there!
Ok so I got this problem. My phone felt to the floor like 2 weeks ago and the screen got crashed, everything else works normally, touch is ok, screen is ok, just glass is broken, after 2 days I downloaded some dota apps and it suddenly started rebooting and crashing:
By this I mean, apps stopped working and lots of pop-up messages appeared, after some reboots It stopped turning on, so I decided to root it and installed a custom ROM the one from mike, Android Revolution, this was last week, this weekend it worked fine until sunday when it got bricked because of an outdated recovery from clockwork. I managed to solve this with some help from you guys, but now again.
I flashed the android monday again with same version, it was working well until yesterday at night, it started showing some whatsapp stopped working stuff again, i rebooted it and now a bunch of window errors... reboot it again and well... no luck it stayed in the Android loading window.
After this I was trying to install the stock version ROM from mike also, and that's when it got worse.
Flashed boot and recovery OK, then rebooted and when I tried to install the ROM it just won't let me, failed unknown error, failed remote : 00030000, and other messages, now when I try to flash the recovery again it says low battery, and when I try the script to charge it it won't work, FAILED remote: unknown reason.
What can I do guys? =S (Sorry for the long post, I just don't know what could it be, and I wish by giving that much information someone can find out the reason, contacted HTC and they said it has no guarantee since I rooted and the glass is broken)
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
faiz02 said:
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
Click to expand...
Click to collapse
I can but there is some weird reason that won't let me do any flash, either low battery and when it gets charged a bit (because it may charge enough sometimes) it says FAILED remote:00030000 or unknown reason.
Don't know what it could be.
I ran into the exact same problem, the charger script does not help me too (low power on usb port of pc).
Thats how I fix this:
1) disconnect original charger, let's phone die. or use shutdown in fastboot.
2) connect original charger, and wait while phone powered up (He himself off as he does not have enough battery power.). disconnect charger.
3) vol.down and hold power,choose fastboot
4) connect charger
5) choose reboot bootloader (phone will reboot in fastboot)
6) choose reboot bootloader (phone will reboot in fastboot)
7) choose reboot bootloader (phone will reboot in fastboot)
....(do it fast)
249) choose reboot bootloader (phone will reboot in fastboot)
250) choose reboot bootloader (phone will reboot in fastboot)
251) disconnect charger, choose shutdown.
252) go to PC
253) vol down, power up
254) choose fastboot
255) flash the custom recovery with power supply support
256) flash custom kernel
257) don't disconnect USB!
258) fastboot / reboot bootloader / hboot
259) recovery
260) mount USB storage
261) drop zip of custom flash to the phone
262) unmount
263) advanced / restart recovery
264) flash the zip of rom
265) restart phone and dont disturb it, at 30 minute, let hi charge.
266) disconnect USB and connect original charger (1A)
267) Have fun!
It worked but bad news... now as always I am getting the message windows, with some weird apps.
First it was htc.com.bgp or something which I found it was the weather, then whatsapp, then Personalize, pretty much everything I open stops working after a while, what can I do? This was the exact reason that brought me here in the first place. It started showing these messages and I decided to install a custom ROM, it was first stock and locked and happened, now with this Android HD ROM it is still the same.
Thanks man... i was scared like hell when i realised that by script my battery voltage didnt raise up... even worse... it became less... i was reboting bootloader for 1h, but finally it worked... now im charging it to max... then ill flash stock rom
Thanks again.
Hi,
My phone : ZE550ML
When I tried to update the TWRP recovery I installed .img file then everything collapsed.
My phone was only booting in bootloader, even if I chose normal boot.
I tried to install another .img file and since my phone doesn't want to do anything. No asus logo, no usb logo, no color nothing.
When I press power button nothing happen however how long I press even with volume button.
I charged it for a day long then I tried like a lot of times this procedure : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 .
(Surprisingly when I connect my phone to my computer sometimes the xfstk software recognize it)
But I always get : FW+OS download did not complete because of limit reconnecting to device attempt number reached.
Does someone have any idea ?
Hi,
long story short:
- worked for few hours, then refused to start, black screen, just vibrating
- bought it from my mom, by the time I got to see her, too late to retrun the phone. Seems like was a chinese import (I'm in France) so no ASUS support and too late to return it to seller...
- so tried to unbrick it following https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785.
- Got the first steps ok (xfstk done)
- time to unzipthe stuff etc, phone turned off and PC rebooted for whatever reason
Where I'm at right now:
- nothing happens, not a vibration, not a detection in device manager, nothing... (I charged it)
-When plugged into computer, after a while, gets hot (more than battery charging, means CPU working like hell?)
Seems like dead for good? any hope to "reanimate it" at least to the fastboot to resume the precedure?
Thx much for your help, buying another one would be ... super sad and difficult
Cheers!
Try to flash using asus flash tool.
1. Download the lollipop raw firmware.
2. Asus flash tool
3. Drivers .
Now start the flashtool then select your device model from list then browse for the raw file that downloaded.
Now connect phone in boot loader mode.
Then click start it will take some time to flash. During flashing phone restarts at that time again boot it to bootloader mode.
You will loose total internal storage data.
R.sahane1 said:
Now connect phone in boot loader mode.
Click to expand...
Click to collapse
that's the issue, can't enter bootloader mode (phone remains completely dead even if charged, no vibration, screen remains black etc)
thx anyway
TL,DR:my s4 mini got a random android update and when it finished updating the evie launcher and touchwis stopped working then android stopped working, got frozen and then shut down after, some time i got it to enter odin mode put the stock rom and got into boot loop with samsung logo, i turn it off after some time, now it wont boot into anything, if a put a sd card with debrick img this apear and only this, if reboot and that msg show again
Boot recovery mode
check boot partitions
copy from t-flash
boot recovery
write 1390008 sections
reboot
_________________________________
Long explanation:
My movistar brand samsung S4 mini (the phone contract ended so i change service provider so they did gave me a code and the phone was free from the contract and now it can accept any service provider) gt-i9190 2 year ago died after a chash in the system, i did have the evie launcher and a different keyboard (not using touchwis) the evie launcher stopped working then touchwis stopped working the phone home menu got to the simple layout then the phone freased and after a couple of second it shut down all this in less than 1 min t and never turn on again, i have a new phone but i will like to use the s4 mini for a proyect but its not starting,
i put an SDXC UHS-I class 10 A1 with a debrick.img(i did try 2 .img from this forum and the phone enter boot recovery mode and show this
__________________________
Boot recovery mode
check boot partitions
copy from t-flash
boot recovery
write 1390008 sections
reboot
________________________
then reboot and the same msg this for more than 30 mins then it stopped until i reconnect it to the pc or the charger or try to turn it on using the power botton, when the phone stop rebooting the normal convinations of keys make it vibrate for 3-4 times but nothing shows in the screen, the bottom convination make it vibrate just after the reboot part and the boot recovery mode dont show again until i stop pressing the bottom comvination then it start the boot recovery loop again, the boot dont fail or at least it do not say it, it just stop trying to rebootafter a long time, its like if its waiting for something to be done by me, like using the botton combination to enter download mode but well idk what to do plz help
Time line of what happened so far
2018
phone died after random update of android OS , though it was his time as i own it for + 5 years
2019
got a new phone and got curious about what happened so i started looking the internet , ended in this website almost everytime.
i left the phone chargin while i searched for answers, i connected the phone to my pc, try the botton combination to get to download mode and recovery(not succesfull) , removed the battery, try to turn it on without baterry to drain all power of phone and restart volatile memory (multiple times) and put it again without gettin anywhere try to connected to a netbook that was freshly formated and with fresh windows 10 intall, odin in that pc recognise the phone just as Qloader-9008 com (x) continued searching and from nowhere the phone started vibrating and then stoped and the chargin icon apeared on the screen i left it to charge as that was the first time i was 100% sure it was chargin after 10+ hours chargin while i was sleeping i try the botton to enter download mode and it worked, try the stock rom from my model, country and service provider and the phone got stuck on a boot loop showing the movistar intro then the s4 mini intro and vibratin each time it was to late so i stupidly turn it of, next morning i got back to try make it work but now it was totally unresponsive odin didn recognize the phone, didnt enter download mode or recovery , no boot loop, nothing is only make a sound in my pc when i try the botton combinations but nothing more just a sound of something connecting and disconnectingx2 got frustrated and left it there collecting dust, also the usb jig dont work
2020
4 months ago i got back to try to make the s4 mini work so i searched the internet again and found the sd card way i did try it and now im here with the phone in a loop of rebootin an starting the same boot recovery mode, it do not say "Flash write failure Ddi : mmc_read dailed" as i did read on other threads in this forum so as i stated before
i put an SDXC UHS-I class 10 A1 with a debrick.img and the phone enter boot recovery mode and show this
__________________________
Boot recovery mode
check boot partitions
copy from t-flash
boot recovery
write 1390008 sections
reboot
________________________
then reboot on a loop and the same msg this for more than 15 mins then it stopped until i reconnect it to the pc or the charger or try to turn it on using the power botton, when the phone stop rebooting the normal convinations of keys make it vibrate for 3-4 times but nothing shows in the screen, the boot dont fail or at least it do not say it, it just stop trying to reboot,
what can i do to at least get it to a point that kies or smart switch can take the controll or be able to use odin, the battery is at 3.78volts
If you can get your S4mini into Download mode, you should try Odin again. But this time, under the Options tab, UNcheck the box for Auto Reboot as well as the box for F. Reset Time. And then when Odin gives the green success indication, immediately disconnect USB and remove battery. Re-insert the battery after a minute or so. Another suggestion; flash the Movistar firmware only if you intend to use their carrier service. Otherwise, it would be better to use firmware not specific to any one carrier. Be sure the 3rd letter of the baseband code is "U" (for "unspecified" carrier). Good luck, hopefully your troubles are not due to faulty hardware.
HY to me happend tha Same my S4-Mini has showing Error in instand and after a tryed to Reboot the Phone was Complete DEAD , tryed the to Boot From SD- Card BOOT RECOVERY MODE it Says FLASH WRITE FAILURE ddi MMC read Failed ! Via odin same happens cant Write Read and NO PIT Partiion FOUND a Tryed also WiTH PIT FAIL .. IT LOOK MY S4- Mini Is Complete DEAD at least the emmc Chip
Happened to me aswell... When i put my SD card with debrick.img on then it bootloops the exackt same way. Cant find any prog or any help to avoid this. Cant even see the phone in Odin no matter with or without the sd card - Or get it to download mode either... i only see the Qualcomm 9008 port as open in device manager
Titanity said:
Happened to me aswell... When i put my SD card with debrick.img on then it bootloops the exackt same way. Cant find any prog or any help to avoid this. Cant even see the phone in Odin no matter with or without the sd card - Or get it to download mode either... i only see the Qualcomm 9008 port as open in device manager
Click to expand...
Click to collapse
How long your has lasting until it died myn was 8 Jears
DEXXO said:
How long your has lasting until it died myn was 8 Jears
Click to expand...
Click to collapse
I need a solution, not a competition in the fails
Titanity said:
I need a solution, not a competition in the fails
Click to expand...
Click to collapse
It was just a question plz dont Cry , and there is no solution your emmc sandisk memory is death 99% buy new or repair good luck
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
wenyendev said:
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
Click to expand...
Click to collapse
They can’t boot….adb only works when booting or booted, and if it bootloops, they won’t have time to pull their data.
afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Bootloader locked or unlocked?
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Unfortunately, USB debugging was not enabled. I stopped developing for Android quite a while back now, and I don't turn on USB debugging anymore.
@Arealhooman My bootloader is locked... I tried unlocking it with MTKClient, but no success since the phone reboots during the process.
wenyendev said:
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Click to expand...
Click to collapse
This helped a lot actually!
It seems that the power button got faulty and got constantly pressed, making the phone constantly hard-rebooting itself.
I have a piece of paper preventing the buttons from contacting the motherboard, and the phone stopped rebooting when charging!
Ingenious method. Glad you solved the issue.
I enabled USB debugging to be able to reboot into fastboot / bootloader without the buttons (since my piece or paper prevents all the button from working xD)
wenyendev said:
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Click to expand...
Click to collapse
Only custom. Stock doesn’t support it.
Bro first check if your power button is working fine, if it is being pressed by any hardware issue it can happen, and when you fastboot try flashing recovery within that time fastboot remains.