I restarted my phone and got a screen that said Unknown error. Restarted my phone again and now bootloop. Can't get into recovery because of it.
Related
I have a verizon galaxy s5 I rooted it with the help and guidance from xda members over here. The method I used to root my phone was this one http://forum.xda-developers.com/ver.../safely-upgrade-root-4-4-4-nha-volte-t2879348 since i was already on NI2 I skipped steps 1. to 2.5 post rooting my phone everything was running pretty good for a few days without any issues but less than a day after I inserted a sim card in the phone it started randomly restarting so did a data wipe factory reset but the problem still persisted where my phone would would either randomly restart or go into a boot loop then I got the G900VVRU1ANI2_G900VVZW1ANI2_G900VVRU1ANI2_HOME.zip stock retail tar from here http://forum.xda-developers.com/showpost.php?p=53447942&postcount=1 and used ODIN to flash it but strangely even after I flashed the stock firmware it gave me the UNLOCKED logo at start below the Samsung galaxy S5 logo so I did another data wipe factory reset and now the UNLOCKED logo has gone but I'm getting a black screen after the Samsung galaxy logo. I can enter recovery mode and download mode my phone also gets detected in kies even with black screen.
I'm pretty freaked out and devastated right now because of the suddenness of this problem. I hope someone knows how to fix this issue.
Sorry for the long post but I wanted to be as detailed as possible.
So a friend of mine owns a Note 4 N910H, and yesterday it froze while attempting to post online, so he forced it to turn off. It now refuses to boot, and keeps getting stuck on the Note 4 logo. Ive tried using recovery mode, and thats not working. The Samsung store at the mall told him that they weren't able to connect to their computer to reflash the software either. Any possible solutions?
My device is not passing the Note 4 logo neiter. I can enter bootloader and flash anything, but afterwards it is looping again... is it vibrating two times before restart?
Hello guys, i am using the Samsung Galaxy S5 g900i and i recently upgraded from Lollipop to Mashmallow, when i was installing the update it was stuck on "Android is upgrading" and this was going on for 4 hours and i switch it off to clear the cache, it was still doing the same thing but now it is stuck on the Samsung Logo. Because the Re-activation lock is on, i cannot flash, root or do anything to it.
ANY SOLUTIONS??
recently my phone have been acting strange, android 7.0 with samsung-something 8.1 so i thought i should root it and then update it. - bad idea..
So, i found a old root guide for 7.0
youtube.com/watch?v=-nveQWZlnOI
did a backup of my stuff, then downloaded odin3_v3.12.3 and twrp-3.1.1-0-dreamlte.img.tar, activated the dev-menu and turned on the oem-unlock
did volume down, home, power, run odin, but i acceidently inserted twrp-3.1.0-1-dreamlte.img.tar
the os restarted, everything was wiped, felt ok. I wanted to fix the issue i did, so i did the same thing again but forgot the oem-unlock.
i went odin mode with twrp-3.1.1-0-dreamlte.img.tar and got stuck in "samsung s8+ logo" after...
tried volume up, home, power but nothing....
tried turn off the phone, but it restarts and got stuck on samsung s8+ logo...
tried drain the battery, it worked but it still stucks on samsung s8+ logo....
tried go into "odin mode" it works.
when i running odin, i get "fail" and phone turns off, and go back to "samsung s8+ logo"
im not sure what i can do now.
and suggestions would be appreciated...
I have a Samsung Galaxy S8+. It is now stuck on a boot loop. It all started when it crashed and turned off when I was watching something on Youtube.
I already tried using Odin and flashed my phone. It worked for like a week and then the problem repeated itself when there was a software update. It was updated. Then after a day the boot loop started again.
I flashed my phone again but it wont work anymore.
I will always get these types of messages:
dmverity hash failed
or
cannot open recovery cause
or
invalid
please help :crying::crying::crying: