Hello guys, i'm having a problem ;f
I was on cm12 nightly when i decided to reboot my device after few days of running, strange thing happend and i ended up in bootloop.
I've downloaded 4.4.2/4.4.4/5.0.1 stock images and tried to flash it guided by the instructions in this thread, however i still get a bootloop, even after clean installation, even after wiping cache and doing a factory reset.. I've managed to boot up my device twice since yesterday, after getting stock image to work i pushed cm12 and gapps on my phone and flashed them.
At the first try, i got bootloop again, so i decided to go through the whole process again, many attempts later i've managed to boot up my device again, and again i decided to flash cm12 and gapps, this time my device booted up properly so i wanted to gain root access, in order to do so I flashed UPDATE-SuperSU.zip file and as a result end up in bootloop again.. I have no idea wtf is wrong with my nexus. I am still trying to flash factory image, and i always end up with bootloop.. I'm out of ideas here, HALP! ;(
@update:
I have uninstalled all drivers, and mount my device to another usb port, then with NRT i installed google's drivers, by using nrt i have flashed 5.0.1 factory image, rebooted into recovery and wiped/factory reset, after that i rebooted my device and still no luck - hanging on floating dots for 15 minutes..
Before all of this I tried formatting my cache to FAT and to sdf4 and it didn't help, I literally tried every single instruction i could've found ;/
What's wired is that when i encountered bootloop yesterday and wiped/factory reset i booted fine, after restart it went into bootloop again, so i thought i would wipe/factory reset again i'll be good to go, but.. it didn't help this time oO
things i've already performed:
1. fastboot oem lock/unlock
2. wipe data/cache/factory reset
3. flash factory images of 4.4.2/4.4.4/5.0.2 through NRT/manually
4. converting partition to fat and next to sdf4
5. reinstalling drivers
6. different ports and usb cords
6. i even tried switching motherboard from my old n4 and i still stuck at bootloop *LOL!?*
7. after 6 i thought it may be related to usb port so i switched usb port from my old n4 and it did help but.. until next reboot ;/
from time to time, after flashing it boots up just to make my hopes and then it gets the bootloop after restart ;/
@update2:
It seems it's hardware related issue. I have tearn down my nexus device and left only motherboard with fron/back cameras and audio jack, daughterboard, i even disattached the speaker along with antena. At this point i flashed factory 5.0.1 and it works, i'm in the moment when i plug peace after peace and turn on the device to check if it still works. I'll update when i find out what was the cause of the problem.
@update3
Stupid as it sounds the issue was caused by the vibrator module, while it was disattached, the device was booting up without any problem.
Related
Hi All
I searched all the threads related to boot loop but did not solve my problem. I was in stock lollipop and my phone was working without any issues. One fine day I felt that the phone is hot and tried rebooting. The phone was struck in the initial graphic screen. Tried restarting again but the same result. After multiple failed attempts, tried doing a factory reset from the recovery with no luck. Thought that something got corrupted, installed twrp and did a fresh install of the factory image. That also did not help. Then installed Chroma ROM and then back to Kitkat factory image and all the attempts failed. Then tried installing Chroma ROM again and after a long wait, it booted up. I inserted the sim card and the network was not detected and hence had to reboot again. The reboot resulted in the bootloop again. Then installed CM 12.1(without sim) and it booted after considerable amount of wait time. Then inserted the sim card and it was not detected and had to reboot again. Now struck again in the boot animation. Is this a hardware issue? Also does the SIM card insertion requires a restart in Nexus 4.
Tried clearing cache/ dalvik cache and did factory reset, file system check but nothing worked..
Can some one help me on this..
Sabari
I also have same issue
I also have same issue,Then I installed clean os with Nexus Root Toolkit.But issue is not solved.some time when plugin into charger or pc that want happen.
sabarirjpm said:
Hi All
I searched all the threads related to boot loop but did not solve my problem. I was in stock lollipop and my phone was working without any issues. One fine day I felt that the phone is hot and tried rebooting. The phone was struck in the initial graphic screen. Tried restarting again but the same result. After multiple failed attempts, tried doing a factory reset from the recovery with no luck. Thought that something got corrupted, installed twrp and did a fresh install of the factory image. That also did not help. Then installed Chroma ROM and then back to Kitkat factory image and all the attempts failed. Then tried installing Chroma ROM again and after a long wait, it booted up. I inserted the sim card and the network was not detected and hence had to reboot again. The reboot resulted in the bootloop again. Then installed CM 12.1(without sim) and it booted after considerable amount of wait time. Then inserted the sim card and it was not detected and had to reboot again. Now struck again in the boot animation. Is this a hardware issue? Also does the SIM card insertion requires a restart in Nexus 4.
Tried clearing cache/ dalvik cache and did factory reset, file system check but nothing worked..
Can some one help me on this..
Sabari
Click to expand...
Click to collapse
Have you tried out the Nexus Root Toolkit? I know most are against toolkits but it really can't hurt in your situation! Try following the guide while having the SIM installed. And yes, SIM card insertion requires a reboot.
Good luck!
Chris
My Google Nexus 4 which was working without issue suddenly began stopping at random times. After few boot ups OS didn't bootup where I had to factory reset wipe from recovery mode. But suddon stopping issue still persisted. Soon it came to a situation where factory reset could n't recover at which case I tried installing Synagenmode. I could not install Synagenmode for some reason. There after I flash factory Nexus 4 ROM again. Still the sudden stopping issue exist when phone is discoonected from charging cable. Phone works fine when connected with main power.
The battery is not empty though it stopped suddenly, I am saying this because I can boot it up again though it stops again before fully bootup. Is this a hardware failure or software faikure such as battery cache
udaraliyanage said:
My Google Nexus 4 which was working without issue suddenly began stopping at random times. After few boot ups OS didn't bootup where I had to factory reset wipe from recovery mode. But suddon stopping issue still persisted. Soon it came to a situation where factory reset could n't recover at which case I tried installing Synagenmode. I could not install Synagenmode for some reason. There after I flash factory Nexus 4 ROM again. Still the sudden stopping issue exist when phone is discoonected from charging cable. Phone works fine when connected with main power.
The battery is not empty though it stopped suddenly, I am saying this because I can boot it up again though it stops again before fully bootup. Is this a hardware failure or software faikure such as battery cache
Click to expand...
Click to collapse
When you say your phone is stopping, do you mean it turns itself off, or just freezes? When you said you flashed factory ROM, do you mean a factory reset, a zip or a factory image via fastboot?
theminikiller said:
When you say your phone is stopping, do you mean it turns itself off, or just freezes? When you said you flashed factory ROM, do you mean a factory reset, a zip or a factory image via fastboot?
Click to expand...
Click to collapse
Yes it turn itself off.
First I factory reset via recovery mode
Then I flash factory ROM via fastboot as mentioned in "[GUIDE] Nexus 4 - Factory Image Restore" of androidcentral dot com
udaraliyanage said:
Yes it turn itself off.
First I factory reset via recovery mode
Then I flash factory ROM via fastboot as mentioned in "[GUIDE] Nexus 4 - Factory Image Restore" of androidcentral dot com
Click to expand...
Click to collapse
Try using a Qi Wireless charger and see if it does the same thing. It could be that your battery has shot craps and while it has a charge, it is not producing enough mAh/voltage and the phone is turning off believing the battery to be dead. I used to have a similar with a Samsung handset which had a removable battery. I would be at 90%+ and it would just shut off. Every time, the battery was swollen and beginning to fail.
You can see how the system is reading the battery status from a logcat. It might give you some insight into the root cause.
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!
Hello!
It's my first time here on XDA-Developers, so I hope I can solve my problem here. So, I flashed with ODIN my SM-G530FZ with the Stock ROM, since I had some issues with the phone. I wiped Data, Cache, System and Dalvik Cache via TWRP before doing this. After the flash, I couldn't start the phone anymore. Only when it's connected to my Samsung charger. Then, it started on its own and got stuck at the boot logo. I had to remove the battery to stop the process. But the same thing happened when I put the battery back in. Phone boots up when it's being charged. I tried to go to recovery mode, but nothing happened. Also tried to do the same thing with download mode, but this didn't work as well. I assume that I have bricked my phone pretty bad, so I hope that I can find some help here
Thanks for reading!
I've hard brick my 1H like this before, so I had to make a USB JIGG, made it with 1 dollar in materials.
You can buy these on the internet for about 3 bucks if you don't know how to build one or look up some tutorials.
What they do is force the phone to go into download mode.
Now, the commands for recovery and download mode could have been damaged so this should work unless.. you actually damaged them both from ever working.
So, my G4 Plus got itself bricked out of thin air. I got it last year , unlocked it ages ago, tried some ROMs but decided to go back to stock+ because of pesky camera problems.
Earlier today i was using it normally when it froze and a long vibration started. With no other options I made a hard reboot and it started up again, only it didn't... The boot animation came out all choppy before rebooting itself again. Sometimes it lasted longer, sometimes a bit shorter but it never fully booted up again. Back home I booted into TWRP, flashed cache/dalvik, nothing. It DID get to a full "G" logo, then rebooted itself again. Got a ROM into the SD card, started flashing, froze, reboot again. Tried formatting everything, same thing, froze, reboot.
Just about the only things I can do with it are boot to TWRP and do anything that doesn't involve storage (so pretty much useless) and bootloader.
I also tried just about everything in my power to flash it on ADB/fastboot, but windows itself won't recognize the thing. All sorts of drivers, command lines, windows test mode (for driver certificate shenanigans), nothing worked. I even tried the same on a netbook with win7 since my desktop doesn't have a single USB 2.0 and I heard ADB has trouble with 3.0, nothing again. It doesn't recognize the device at all. They do recognize my girlfriend's G5 by the way, but seem to want nothing to do with my crippled-down-to-bootloader G4+.
I need some help guys, any clues?
Remember:
-Not your everyday bootloop
-Stuck with bootloader and limited usage of TWRP (i can copy files from SD to Internal with no problems)
-Neither Win10 with USB3.0s nor Win7 with USB2.0s recognize the phone at all, at least in this state (every driver out there already installed in every order)