A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
SeanBond said:
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
Click to expand...
Click to collapse
Damn, sorry. Pretty sure you're out of luck if you can't connect to PC and you can't get into recovery. I'd give it straight into support now and give an excuse like update failed, randomly started restarting etc.
What OS Are you running? 8.1? I would suggest using a Linux Live Disc or Windows 7. its much more reliable.
I am pretty sure you need hboot 1.56+ for windows 8 to work correctly in Fastboot
SeanBond said:
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
Click to expand...
Click to collapse
usually when it boots into the os, then reboots after 30sec or so, the radio is borked. the radio is the last thing to load in the os
if you can get into the bootloader as it shows in your pic, you need to select FASTBOOT. what you see in the pic is youre in HBOOT mode, and that will not connect to a pc that way. ADB will not work in the bootloader in any case, so dont even try that. You should have your recovery.img file ready, get into the bootloader as you show, and select FASTBOOT. then flash your recovery with command-- fastboot flash recovery recovery.img
however, if your radio is hosed, flashing a rom wont help you. You should probably do a RUU. Many RUU's work off fastboot mode, so get into that and start the RUU.exe
Related
Dear Sir/Madam,
Before Spring Break, I rooted my droid bionic using motofail for windows. I do not know what the software version is, but I will include the software (motofail) in this email. On Thursday March 28, 2012 I decided to try installing ROMs to my Droid Bionic. I saw that Liberty Rom, Blurr3d Rom, and Eclipse Rom were cool roms. so first, I got Bootstrap (I will include it in this email) Bootstrap is a .apk file. I also got ROM manager, titanium backup, and one more, but i do not recall what it was. I made a backup of the stock ROM with ROM manager. and i installed bootstrap. little did i know that if something bad happens to the phone during a ROM install, you cannot restore a previous backup. So i cannot get my stock ROM back on. later on, before i had a problem with bootsrap i installed liberty ROM. then i got board with it then got blurr3d. then i got eclipse ROM. that's when i started to have problems. After i installed the eclipse ROM, noticed that i could not get any cell service or data service. I could get data from wifi though. So i freaked out and got liberty ROM. i read up on it and someone said i should get safestrap. Safestrap is like bootstrap but it is safer because you can access the recovery menu from boot and not have to access it through an application on the phone like with bootstrap. So after i got safestrap i installed it, rebooted it and made a back up. Before i made the backup i put plurr3d back on becasue i thought that the radio files from eclipse were not compatible with the radios on the bionic for some reason. This was all on Thursday. well, this time, it took 3-4 hours for blurr3d to get passed the welcome to andorid please touch the android to continue screen. on the screen it said, "please wait... this may take a few mins" after about 20 mins i got worried so I pulled the battery and rebooted the phone. and got back to the same screen. After i got back to the welcome to android screen, i had to go to football practice and dinner afterwards. when i got home, which was 3-4 hours later, I checked on the phone and it was past that screen and i was able to add my gmail account to it. For some reason or another, the cell and data services were not working. so i left it at that for a day or so and on Friday, I tried using what a lot of people are saying on the Internet which is, RSD lite. you can use RDS lite to flash a stock ROM onto the droid bionic. at that point, i thought that if i got the stock ROM back on, the radios would start working again. well, when I put the phone into fastboot mode it said,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Connect USB
DATA Cable
It also said the same thing when i connected the USB cable to the phone and the computer. RSD lite did not recognize the phone so i tried for a couple hours with the same result. Later on, I read that restarting the computer with the phone in AP Fastboot while the phone was plugged in would get the phone to say,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
This worked, but RSD lite still would not recognize the phone. So then i remembered that i had a stock ROM backup with bootstrap and i did. so i un-installed safestrap (one of the worst mistakes i made so far) and installed bootstrap. so i booted into recovery via bootstrap to restore to stock ROM. things did not go as planned... for some reason or another, it booted up normally. without going to recovery. then it wont to the dual core screen then the bionic eye screen with someone's ROM underneath it (it didn't say someones ROM but it said some one's name then the word ROM) then blurr3d ROM booted up and it kept crashing. so i ended up staying up to around 2-4 AM trying to fix that. i ended up saying forget this and going to sleep.
When i woke up in the morning, i looked at the phone and i had my data and my cell service back so i was confused so i started texting my friends and when i tried to go tot he home screen, nothing happens. but what i learned earlier is that when i reboot the phone, my data and cell service goes away for a couple of hours. So here i am now with my droid bionic, and cant do anything but text and call. i can only call when i get a text from someone, open up the text, and click on the phone number and click call when it brings me to the contact page for the number. I am also not able to access the home screen, the settings folder, or anything besides the notification bar. i really need my phone to use email, games, software (learning how to write java code), and for school in some instances. Any help would be greatly appreciated.
Thank you for your time,
NH85
Seems to me...you lost data along the way.
A possible reason rsdlite is not recognizing your phone might be because you dont have the proper moto drivers installed.
Try this rsdlite and install the correct drivers for your pc...http://dl.dropbox.com/u/63864500/rsd_drivers.zip
Make sure your battery does not die!
Boot into AP fasboot (power and down volume)
Use the cable that came with your phone.
See if rsdlite recognizes the phone.
If it does, you can flash the full 902 xml file (make sure your pc has 4g of RAM tho)
Do you have the full 902 xml file...if not, let me know.
Drivers
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
i notice that you didn't once mention a wipe data or otherwise cleaning of previous ROM before flashing another (correct me if im wrong). also DO NOT have bootstrap and safestrap installed at the same time, this could be what caused all your problems. in order to switch between the two (which i've had to do for webtop issue), you have to return to STOCK +root, uninstall the currently used strapper, reboot, then install the other. things start getting even hairier if you forget that safestrap has both a safe/non-safe system. you need to be doing the switch on the non-safe system if necessary.
the purpose of safe-strap isn't that it can boot to recovery, it's that it *creates a an isolated ROM installation while preserving your "safe" system in case things like everything your experiencing occur. from what i can tell, you did not change to safe system before flashing new ROMs, again correct me if im wrong. at any rate, a bit of advice for the future is follow directions to the dot, but before even attempting the install read through AT LEAST 3 or 4 pages of user feedback to see what the common issues or install goofs are!
that being said...
having your computer recognize the phone as storage device does not necessarily mean you have the right drivers installed, however it does mean that you probably have the right cable (this is important, bionic is finicky without the proper moto cable). you will know if you have the right drivers if you see in device manager Motorola ADB. when you plug your USB cable in, there should be an option for "PC Mode" which will force the computer to search for the drivers you claim to have installed correctly. if not found, here is your chance to install them properly and test RSD to make sure device is detected.
nh85 said:
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
Click to expand...
Click to collapse
Obviously you don't.
Mass storage and ADB are not the same drivers.
If you are in fastboot mode and your device doesn't connect, it's most likely your missing or don't have the fastboot drivers installed on your computer properly.
Once you get the ADB driver from motorola you can use fastboot start flashing.
The information you need is here
http://forum.xda-developers.com/showthread.php?p=22758211 .
I had trouble using RSD to flash the .902 FXZ.
What I had to do is extract the .img files from the ZIP, and use fastboot through CMD to get everything up and running.
Just open up the XML file inside the zip, it will show you the commands you need to type to flash each section and when to reboot the bootloader
Hello all! So, I tried to install CM11, the one on this post.
Went into CWM, did Wipe data factory reset and formatted /system. when I tried installing the rom, it said operation aborted and it could not install it. No biggie, the post says to install cm10.2 before doing so.
So i Powered the phone off to copy the file over to the SD. To my surprise, now I can't get into CWM, Philz, TWRP, fastboot or flashmode. Whenever I press the back pin to power the phone off, it turns back on automatically before I have time to press the key and connect the USB cable. Furthermore, when I manage to do it quick enouhg, the green led lights up, but it fades away after 10ish seconds only to display the sony logo again, and a "can't recognize USB device" popup comes up in my PC. I've used flashtool with this same pc in the past, so I don't know what that is about. Also, whenever I try installng flashtool drivers again, just in case 2 things happen:
there is no xperia SP device listed and whatever i select it fails to install.
What can I do now? I had 4.3 with the eXistenZ Ultra ROM before all of this.
Damm, this is the first time this happens to me, I've been swapping roms for ever, and this is not even the first phone i do this in, had a galaxy s2 and a wildfire S before. I feel like such a noob
UPDATE!:
So I finally managed to fix it. I posted this after about 8-9 hours of trying to get into fastboot on the 3 different pcs in my household, all had the drivers at some point and i've worked with them and fastboot and this same phone previously, so I figured they'd still work. They didn't, I couldnot even get SUS to work. So i went to a 4th PC, installed SUS and the needed drivers and it only took like 40 minutes worth of tries. I'm in the software download part of the SUS, i'll keep this updated!
UPDATE2!:
So, it finished downloading but it suddenly disconnected, tried again for about 10 minutes and then got it going again. Downloaded the second time and installed it successfully. Leaving this up for future reference!
Bottomline: if you can't get into flashmode, try on as many PCs as you have available for at least 30 minutes each.
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Th3Duck said:
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Click to expand...
Click to collapse
No problem, it kinda sorted itself out by brute force connections :> Dammed sony, locking the bootloaders for real. I even got the sim unlock code from my phone company and it's still not bootloader unlockable at the phone settings, even though i can now get any sim i want in it -.-
Long story short my sister upgraded to iphone so she left her xperia SP untouched for two days, which somehow drained all the battery ( i know it because LED blinked three times when I pressed power button). So I left it to charge for 3 hours using a wall charger & then following happened:
1. Sony logo came up.
2. Sony Auto repair mode activated. (Phone was perfectly working earlier).
3. Then the Sony rainbow wave kept on coming for hours.
4. A message popped up ‘Process system is not responding’ with option ‘wait’ & ‘continue’. I chose continue.
5. Phone was stuck on that screen for half an hour. Then I decided to switch off the pone normally. Power off popup screen came and screen froze on it for hours.
6. Then the process restarted and it has been the same way no matter what i try.
Solutions that I’ve already tried:
1. Repairing using Sony PC companion. Progress stay stuck at same point on all three of my PCs and then errors shows up. ( tried on windows 8.2/xp sp3/Windows 7 64bit).
2. Repairing using Flashtool. Everything gets loaded successfully but no progress has ever taken place. Even left it for a day but my phone’s battery died yet not flashed. Tried it on windows 7 and XP-SP3, with three different ‘*.ftf’. windows 8.1 is still pending.
3. I installed EMMA. It detects my device pretty well but as it is not rooted nothing further happens.
Installed all drivers prescribed in flashtool successfully. Reinstalled them after reinstalling flashtool and PC companion.
Tried rooting only kernel but didn’t work. It stayed stuck as well.
4. Updated java.
5. Took phone apart and pulled the battery ribbon out and repeated step 1-4. Still no success.
Any type of suggestions/help is really appreciated.
rohitchandra said:
Long story short my sister upgraded to iphone so she left her xperia SP untouched for two days, which somehow drained all the battery ( i know it because LED blinked three times when I pressed power button). So I left it to charge for 3 hours using a wall charger & then following happened:
1. Sony logo came up.
2. Sony Auto repair mode activated. (Phone was perfectly working earlier).
3. Then the Sony rainbow wave kept on coming for hours.
4. A message popped up ‘Process system is not responding’ with option ‘wait’ & ‘continue’. I chose continue.
5. Phone was stuck on that screen for half an hour. Then I decided to switch off the pone normally. Power off popup screen came and screen froze on it for hours.
6. Then the process restarted and it has been the same way no matter what i try.
Solutions that I’ve already tried:
1. Repairing using Sony PC companion. Progress stay stuck at same point on all three of my PCs and then errors shows up. ( tried on windows 8.2/xp sp3/Windows 7 64bit).
2. Repairing using Flashtool. Everything gets loaded successfully but no progress has ever taken place. Even left it for a day but my phone’s battery died yet not flashed. Tried it on windows 7 and XP-SP3, with three different ‘*.ftf’. windows 8.1 is still pending.
3. I installed EMMA. It detects my device pretty well but as it is not rooted nothing further happens.
Installed all drivers prescribed in flashtool successfully. Reinstalled them after reinstalling flashtool and PC companion.
Tried rooting only kernel but didn’t work. It stayed stuck as well.
4. Updated java.
5. Took phone apart and pulled the battery ribbon out and repeated step 1-4. Still no success.
Any type of suggestions/help is really appreciated.
Click to expand...
Click to collapse
Okay, i am thinking you have troubles with drivers. Open up flashtool folder and go into USB drivers . Install it and see if your device detects it. Do not install drivers from by running flashtool.
By the way are you using the latest flashtool with latest drivers provided in its folder ?
I suggest you install a custom recovery (which you can get from a kernel even from flashtool by going into fastboot mode) and try to clear cache/ complete wipes. See if that helps. Make sure the recovery is specific to your android version. Do not flash a kernel which is based on 4.2 but you have 4.3 flashed etc.
Quote me back if you expect a reply.
Good Luck
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
iXanza said:
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
Click to expand...
Click to collapse
I got this error as well,
After some search it seems using a deep flash cable could, I cannot make one currently so maybe you could take a look and try it
http://forum.xda-developers.com/showpost.php?p=69727277&postcount=2
I just checked the second post in the xiaomi eu thread
"- NEVER wipe /system partition manually in your life!"
hmm, I have always done this
Edit:
Many people reporting the same issue their.
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
iXanza said:
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
Click to expand...
Click to collapse
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
No clue. I'm taking it to the shop for them to do it for me tomorrow.
https://www.youtube.com/watch?v=ED96PJ-qYMM
Do follow the videos, i was hard brick 2 times but now it's working
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Shaky156 said:
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Click to expand...
Click to collapse
I don't really think that this is the problem because the "rom" flash completely successfully. I don't think that the font flash would cause all this mess. Anyway, I left it charging overnight and I keep pressing power button with vol +/- but nothing happens. Thanks anyway. it seems I have to either use test points or deep flash cable.
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
EDIT: ok, got it booting now. The red blinking led is actually a good sign, it means low battery. I just let it charge for about 20 min and the led changed to yellow, and then I could boot it up.
It seems like in all that time the phone was plugged into my PC usb port for flashing, it didn't charge the battery. So I think we should take into account what Shaky156 said, just in case.
jiaming2009 said:
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
Click to expand...
Click to collapse
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
IMTLD said:
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
Click to expand...
Click to collapse
Good to know it also worked for you, I just didn't believe that my battery was depleted from 70% just by hardbriking it...
After installing TWRP it asks to decrypt data even though I did not encrypt, hmmm what now
Edit:
I just did factory reset in TWRP and now I can see sdcard.
IMTLD said:
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
Click to expand...
Click to collapse
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
idmissile said:
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
IMTLD said:
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
Click to expand...
Click to collapse
At that point, I didn't really care if I lost data since I didn't have much on it anyway. Nice to hear that you got yours back. Those were dark hours, yes?
Thanks for giving a hope (checking way to recover from video). I'll get proper screwdrivers soon and try do the same.
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Shaky156 said:
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Click to expand...
Click to collapse
but how my mi5 now hardbricked no fastboot no recovery no edl
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
I can confirm that this 100% works for me. You need to be a bit patient with the tweezers and getting the contact points right. It didn't immediately work for me, and I think I had to try a dozen times at least. But eventually it did recognize it. Once MiFlash can see it, you need to use the latest China stable rom. I tried the latest china dev, but it kept on giving errors of missing hello packets.
Hello all, It has been some time since my last post.
My sisters Note 4 started boot looping the other day... More specifically, it would boot up, then a few min later reboot into recovery. Failure to Mount Cache, or something along those lines... So I did the cache wipe and a FDR. Thought all was well, then a few hours later, booop, rebooted into recovery again.
So she sent me her phone, I went to flash via Odin the latest release from Tmo...it kept failing. So then I did the Kies way... Failed the first time, but after a few tries.. it worked... Phone booted into setup.. YAY... premature YAY. A few min later, the phone rebooted, but this time into download mode....crazy. So I plugged it back into the PC ran odin again.. Fail, Tried different releases of Andriod... Fail... I rebooted it, and now I can't get any recovery or download mode. When I plug the phone into the PC.. it makes the beep boop beep boop.. like a USB device has been connected.. but does not show up in the drives list, or the device manager.. also Odin does not see it.
I thought the battery was the issue, but I check the current out of the ports with my multi Meter... Checked the battery as well and it's healthy.
I have found a few things about teh 1..2..3.. thing, that doesn't work. Saw some about leaving the battery out for a few hours.. that didn't work. I know the vol down-home-power button etc.. I have tried all the basic ways to get into download, even tried ADB (won't work because device isn't recognized.)
Any ides or maybe?....maybe something I haven't seen yet? I am a good googler, and wouln't have posted here if I hadn't kept running into a dead ends... Could it be the mobo in the device?
Thank you in advance!!
RP
Rabid Panda said:
Hello all, It has been some time since my last post.
My sisters Note 4 started boot looping the other day... More specifically, it would boot up, then a few min later reboot into recovery. Failure to Mount Cache, or something along those lines... So I did the cache wipe and a FDR. Thought all was well, then a few hours later, booop, rebooted into recovery again.
So she sent me her phone, I went to flash via Odin the latest release from Tmo...it kept failing. So then I did the Kies way... Failed the first time, but after a few tries.. it worked... Phone booted into setup.. YAY... premature YAY. A few min later, the phone rebooted, but this time into download mode....crazy. So I plugged it back into the PC ran odin again.. Fail, Tried different releases of Andriod... Fail... I rebooted it, and now I can't get any recovery or download mode. When I plug the phone into the PC.. it makes the beep boop beep boop.. like a USB device has been connected.. but does not show up in the drives list, or the device manager.. also Odin does not see it.
I thought the battery was the issue, but I check the current out of the ports with my multi Meter... Checked the battery as well and it's healthy.
I have found a few things about teh 1..2..3.. thing, that doesn't work. Saw some about leaving the battery out for a few hours.. that didn't work. I know the vol down-home-power button etc.. I have tried all the basic ways to get into download, even tried ADB (won't work because device isn't recognized.)
Any ides or maybe?....maybe something I haven't seen yet? I am a good googler, and wouln't have posted here if I hadn't kept running into a dead ends... Could it be the mobo in the device?
Thank you in advance!!
RP
Click to expand...
Click to collapse
Your device is definitely hard bricked to unbrick.
Have a look at link below it might help.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
I gave that a shot this morning....no dice. Still nothing...Still get the beep boop beep when i connect the phone, but still can't get it into download mode. I might consider using it as a Frisbee...or target practice...