I had to resolve to making a thread because google isn't helping... And I've looked through everything.
I was running Hurricane rom v6 and I wanted to upgrade to the latest version, so I went ahead and tried to install the mj5 bootloader. I followed all the instrcutions but something didn't seem right... Right after the flashing process in Odin finished, my phone rebooted into the recovery (CWM PhilzTouch) instead of rebooting to the OS. I went to check if the new bootloader was installed and I don't think it was, because it didn't say KNOX WARRANTY VOID as it was supposed to, according to the instructions.
So I tried it again a few times and eventually what happened is that I got the "go into Kies and do the emergency recovery etc" which I did, a few times, unsuccessfully. It failed every time. So I uninstalled Kies, went back to Odin, tried to a few other ports, and finally it finished the flashing process successfully.
Now I can get into both recovery and download mode, but when I try to reboot the phone, the Galaxy Note 2 logo shows up, after that the screen goes black and then the phone vibrates every two seconds until i remove the battery.
I tried going back to recovery and then factory reset the phone but still the same thing happens. Now I'm downloading the stock firmware from samsung to try to flash that since I can still get to download mode but it's going to take an hour and until then I wanted to ask if the vibrating behavior was normal or it indicated a more serious problem. In all fairness I haven't tried installing the new version of the Hurricane rom after I tried flashing the new bootloader, but I figured that as long as I don't know that I have the new bootloader for sure I'd rather skip that step.
Any ideas?
I flashed the stock firmware onto my phone, and all was going well until it turned itself off. It then rebooted into Download Mode, and got itself stuck on 'Firmware Update'. I pulled the battery, rebooted and it went from the LG logo straight to the Firmware Update screen. I've tried going into recovery (which works, but pressing yes OR no still takes it to Firmware update. Going into download mode doesn't work either.
I tried to re-flash it using the LGFlashTool, but my PC can't find the phone in this state. I bought it off a guy on eBay 4 months ago, and it worked fine until the first sentence of this post happened.
EDIT: it's the international D855. The Firmware Update screen says '910K B0 QEM'
Galilwithit said:
I flashed the stock firmware onto my phone, and all was going well until it turned itself off. It then rebooted into Download Mode, and got itself stuck on 'Firmware Update'. I pulled the battery, rebooted and it went from the LG logo straight to the Firmware Update screen. I've tried going into recovery (which works, but pressing yes OR no still takes it to Firmware update. Going into download mode doesn't work either.
I tried to re-flash it using the LGFlashTool, but my PC can't find the phone in this state. I bought it off a guy on eBay 4 months ago, and it worked fine until the first sentence of this post happened.
EDIT: it's the international D855. The Firmware Update screen says '910K B0 QEM'
Click to expand...
Click to collapse
Thats not actually right
Booting into recovery normally should factory reset the phone. Would you be able to post a picture of the firmware update screen
itsbighead said:
Thats not actually right
Booting into recovery normally should factory reset the phone. Would you be able to post a picture of the firmware update screen
Click to expand...
Click to collapse
I tried it then. When I do it, I get the normal 'No (Exit)' and 'Yes' and then the same thing to confirm it. It then goes to the LG logo, and boom! Firmware Update!
I don't have a camera (stupid, I know) but, if you boot into download mode, it looks just like the screen there. Except it shows '910K B(0-99) QEM' in the update box thingo.
Hi, i have the exactly same problem, even if i try to power up the device normally or in download more it goes directly in to firmware update. Any way to fix it or install LGE MTP Driver so my PC will see my phone in order to flash it again?
LE: Video
I have run into the same problem like you guys. I recently updated my phone and it started to malfunction with resets, crashing and eventually got it stuck in boot loop. Then it booted into a green screen that said "demigod crash handler/tz crash" thrice. Instead of a hard reset I decided to using the lg mobile support tool to fix it. During the upgrade recovery my phone went into download mode/firmware update. I could see the progress bar moving and then get stuck and my mobile would switch off. Took out the battery, disconnected and reconnected the phone and tried the process all over again but in vain. I repeated this at least 8 times and eventually gave up. Now my phone is basically useless and only boots into firmware update. Hard reset doesn't work either. Can somebody please help me fix this?
I HAVE THE SAME PROBLEM :crying:
910k b0 qem
I tried to flash TOT file and it kept failing around 10%. I read somewhere that I should select the "Flash Board" option so I did. This also failed and left my phone booting to "Firmware Update" screen with following text in the gray box at the bottom.
910K B0 QEM
Windows no longer recognizes the devices and fails to install drivers.
I believe that what is required here is the "910K resistor flash cable"
Something like this ebay[dot]com/itm/OCTOPUS-Z3X-MICRO-USB-LG-P970-P990-P999-CABLE-56K-130K-910K-VARIABLE-RESISTOR-/131321398015
Can someone confirm or offer a solution?
P.S. This 10 post URL limit has got to go!
Galilwithit said:
I flashed the stock firmware onto my phone, and all was going well until it turned itself off. It then rebooted into Download Mode, and got itself stuck on 'Firmware Update'. I pulled the battery, rebooted and it went from the LG logo straight to the Firmware Update screen. I've tried going into recovery (which works, but pressing yes OR no still takes it to Firmware update. Going into download mode doesn't work either.
I tried to re-flash it using the LGFlashTool, but my PC can't find the phone in this state. I bought it off a guy on eBay 4 months ago, and it worked fine until the first sentence of this post happened.
EDIT: it's the international D855. The Firmware Update screen says '910K B0 QEM'
Click to expand...
Click to collapse
It is possible you flashed the wrong KDZ or TOT file
You can also try to hold the power button and wait untill the LG logo appears
anyone have any luck? Im stuck in this mode also
Hi, In the Hope that i may probably be able to unroot my device, I uninstalled Magisk, but on my next restart, it has got stuck in BootLoop, sad thing is, the phone doesnt even get switched Off, when i long press the power button the screen goes Off for a while and then gets restarted again.
Please Help , how can i get my phone to behave normal, My Device ,model is XT1710-10
Update: Now I somehow was able to get to TWRP recovery, and then i wiped dalvik-cache,data,system.
But now after i reboot, it shows No OS.
I thought of finding Stock Firmware of Indian Variant to download and flash, but i cant find it anywhere .
Update 2: Flashed TWRP 64Bit and then loaded CrDroid ROM by dlproject , aleast my phone came back to Life now.
So, this is more for interest than anything else, but here's the scenario.
A friends 5T did a sudden shutdown. He picked up the phone, unlocked the screen and opened WhatsApp. An error message flashed on the screen - too fast to read - and the phone shut down immediately. He tried to restart, but it was stuck at the boot logo (circle with rotating dots).
We had a go at trying to get it back up again and did the following. I should note that both recovery and fastboot were available, however the bootloader was locked.
1) Booted into recover and sideloaded the latest OnePlus ROM - Stuck at boot logo
2) Got hold of unbrick tool and flashed with latest version (seems to be Android 8.1) - Stuck at boot logo
We were about to give up assuming a hardware issue when on a whim I tried the old unbrick for Android 7. Amazingly the phone booted. I quickly enabled bootloader unlock and unlocked the bootloader. We then flashed TWRP and tried to flash a custom ROM (Bliss in this case) - followed all the instructions to the T and got stuck at the (Bliss) boot logo (very cool boot logo by the way).
We then flashed a rollback version of Android 7 designed for folks coming back from one of the early beta 8 versions. This booted again, although it replaced TWRP as expected. We then sideloaded the latest version of 7 we could find (seems to be 7.11).
So here's the question. The only thing not working on the phone is the Wi-Fi. It does not switch on and shows a MAC address of 02:00:00:00:00:00 which indicates an issue. So I'm assuming something to do with the Wi-Fi has died on the mainboard. However, Bluetooth still works, SIM cards still work. I can use the phone normally with a mobile data.
So, what would stop anything above version 7.11 from booting if just the Wi-Fi is broken? Is there some link to this that was added in Android 8. It would great to update to 8 or 9 and still be able to use the phone, as everything else seems to work.
P.S. I have noticed that the camera takes about 10 seconds for the image to appear after the app opens, then works fine after that. Related maybe?
Anyway, was just wondering if anyone knows the inner workings and can shed some light on this one.
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
OK, here is kernel log. I powered on the device, let it boot to the latest Lineage OS (lineage-17.1-20210201), then entered pin number and waited. Screen turned off, and a couple of second later device restarted (showing "Mi" and at the bottom "unlocked"). Then I imediately pressed "power + volume UP" to boot into recevery, where I copied log file).
I noticed multiple i2c errors, but couldn't find where exactly device initiated reboot.
klepec said:
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did you do clean flash? Wipe data, cache, system, on internal storage android directory must be deleted?
What's your firmware? I guess old oreo and not new one - pie, it should be 11.0.3 or newer!
Update Firmware first using MI FLASH TOOL NOT FROM RECOVERY!!!
Than clean flash Official LOS 17.1 again.
If your WiFi won't work after that your persist partition is corrupted.
For extra info search xda forums.
Good luck and stay safe!
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
klepec said:
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Yap all above 11.0.3 is ok..
Advice: don't rush! Read and take it slow. If you rush you'll probably mess it up... unlock your bootloader first, its easy to bring it back to life if you gonna mess up your phone.
For better overview watch how flash and what options to pick
Good luck and stay safe!