Hello everyone,
I'm new here, I read that introducing is not mandatory, if it is please tell me and I'll do it right away.
I've tried searching for a solution all over the forum but can't seem to find one.
A couple of days ago I was camping. Before going to sleep I checked my phone as usual, it was charged (around 80%) and everything was normal.
When I woke up the screen was black but with the backlight on and only vibrating, therefore I thought to hard reboot it by long pressing the power button.
Since then the phone has been stuck in bootloop and won't do anything.
The phone is 100% stock
I can access the stock recovery and the fastboot mode.
Fastboot is recognized by Windows. ADB doesn't seem so.
MiFlash recognizes the device.
I've also tried MiPCSuite and MiPhoneAssistant (the chinese version) but both of them don't seem to detect the device.
I really need to save the data, therefore I can't just erese everything and reflash. Do you have any suggestion?
The last thing I was thinking to do is to flash the latest stock rom via MiFlash and as far as I know this shouldn't erease the data, please correct me if I'm wrong.
Hope to hear from someone,
Thank you
Alessandro
Hey did u succeed with fixing the bootloop ? I have the same issue but after update
Related
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Search for the Hard Bricked thread by Naman Bhalla and use it. The links in it may point to older versions, so find out if any later versions are available.
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If pc detects phone try /adb devices ,if it detects phone, go like this: /adb reboot bootloader then it should reboot into fastboot. If so try fastboot flash recovery "yourrecovery.img" (I suggest stock recovery of oos you had before brick). The next step, if you boot into recovery is to adb sideload stock oos. Command for that is /adb sideload "youroosfile.zip"
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
ach3fck said:
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
Click to expand...
Click to collapse
That's right I even recover a CB8 dead OP3
toolkit
try oneplus 3 toolkit
Try the Unbrick tool, everything that is bricked can be solved...
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?
HELP PLEASE.Is there a way to flash or root AT&T Note 5,stuck in boot loop mode???
Hi to all
I'm member on XDA for a long time,but I really am a newbie considering rooting,flashing and messing with the phones.
Yesterday ,my At&t Samsung galaxy NOTE 5 restarted by itself and started doing that constantly.Maybe because the memory was almost full so the firmware didn't have enough space to run correctly ,I don't really know.
So I decided to do a FACTORY RESET in order to refresh the phone.I backed all up (it did restart few time while I did that but I managed to finish it).
After I did the factory reset and wiped the cache,I rebooted the phone and that is when the boot loop started.
Once or three times came back and started the phone up to the first settings (I managed to put in my google username e.t.c. but after a minute maybe it freezes and restarted by itself again)
I tried again another factory reset but the boot loop continues.I tried many time to turn it off,it restarted up to INSTALLING UPDATE......then tried to turn it off completely (Volume down+Power+Home button) and somehow I managed to turn it off.
I thought that I can come here and find the instructions on how to FLASH it with ODIN,but I couldn't find the stock firmware for AT&t Note 5.
Then I remembered (and read on internet) that the bootloader on AT&T phones is locked !!!!!
I searched some threads here for at least how to root it ,but I can't find anything clearly.
So I'm asking you for help: IS THERE ANY SAFE WAY THAT I CAN DO FLASH OR ROOT MY AT&T SAMSUNG NOTE 5 (EXPLAINED STEP BY STEP) IN ORDER TO MAKE MY PHONE WORK AGAIN????
I have never before messed with the phone.It has the original stock firmware Android 7.0 Nougat.
And the phone is bought in USA,but I live in EUROPE and have unlocked it ,by buying some code online, few years ago.It was working fine until yesterday.
Thank you in advance guys I hope that someone might help me.
Juno 106
Guys I found here some older version (few months older) of Android 7 for my Note 5 and I managed to do a flash. The flashing went OK I went through settings and after few minutes the phone freezes again and restarts. And then again the same,it works fine for a few minutes,freezes and restarts (I can here the camera working inside sometimes too)...........CAN ANYONE HELP ME REPAIR MY PHONE ,PLEASE ???
Hi again
I don't know why no one is replying to me???
Today I managed to make the settings and power up the phone,restored the back up....the phone is working,BUT the PROBLEM is that it constantly freezes and reboots by itself.Sometimes it works for few minutes and reboots,sometimes it works for 30min and then it reboots,sometimes longer...
What might be the problem? Is it some hardware problem processor ,memory or maybe bad battery? It is older model and I have noticed with Accu Battery that most likely the battery haslowered it's capacity.It drains faster,sometimes when it comes to 15% it drains very fast...
Can anyone help me diagnose the problem?
Thank you in advance
Try booting into Download Mode & flash a new stock firmware if all else fails, assuming u tried a factory reset first with no satisfaction. Guides are everywhere. I HTH
PiMPSoFT said:
Try booting into Download Mode & flash a new stock firmware if all else fails, assuming u tried a factory reset first with no satisfaction. Guides are everywhere. I HTH
Click to expand...
Click to collapse
Thank you for your reply
I managed to flash the firmware few times,but the phone keeps freezing after some time and restarts.Sometimes it is stuck in the bootloop,sometimes it starts up to some point,freezes and restarts.
Could it be BAD BATTERY or is it something else?
If it is the battery problem,I will replace it,but I'm afraid that it might be someting else wrong.
What is your opinion?
Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.