Hello!
I am not a completely tech savvy person so I thought that I would post a thread to see if anybody knew anything and to see if anybody could help before I officially put my previous phone to rest. If anybody has feedback that is appreciated, thanks in advance!
I tried opening Google Chrome but that did not open so I tried the built in browser and that did not open as well, both of them immediately closed after so I thought restarting it would fix the problem but it did not when I turned it on it went to the carrier logo and stayed there (If I recall correctly) so I took the battery out and put it back in to try and fix that problem, that did not work. So I tried booting it into the only menu I could get into and did the factory reset, it went to the Green Android robot and it did the reset, after I restarted it, it went to the carrier logo and the brand logo but it just goes to the brand logo and keeps going to that and in the corner it says "790 Secure Booting Error! Error Code : 1006" and now it does not charge when I plug it in, when I plug it in all it does is the bootloop. Because the phone will not power on and go to the home screen, my computer does not recognize it.
I want to fix the phone to get it back to the home screen and make it stop doing that and to use the phone on WiFi! If you all have questions, just let me know.
Related
Hi Guys,
I was in the middle of flashing my OMNIA 7 then suddenly my computer shutdown due to a blackout at our home. Now my phone is stuck on the OMNIA 7 logo during boot and keep going that way.
I could still manage to go to download mode and reflash but when I try to flash it there is an error that would indicate "WRITE MIBIB FAILED!"
Is my phone bricked? I need your help.
By the way, if I get still manage to go to the DOWNLOAD MODE would that mean that my phone is not bricked?
Thanks!
Have you tryed formating before you try? Just use the other volym button.
Tryed yet?
Yeah I tried it, but still not working. . I still manage to get to "download mode" though.
As I have read through the different posts in the forum I see people experiencing the same problem such as the phone which keep on restarting and stuck on the "OMNIA 7" startup logo. . I tried the fixes that other's recommended but still doesn't work.
I tried taking the battery out for a day then putting it back in, the phone managed to boot up and I was actually able to use it but if I try to restart it again or sync it to the computer, It suddenly resets then goes on the boot loop once again. .
Well then I guess there is only one way. Return it to the store. :'(
to flash, ALWAYS restart your computer before and use a laptop with charged battery to avoid this problem.
For your problem you can tried to flash only bootloader part, radio part, or only PDA part for testing.
hay man
I had the same problem and here is the solution
follow the this link http://support.microsoft.com/kb/2530409/en-us
it works 100%
I hope it works with you as well
Nice one Abd654. Hope that helps you bor. GL
I have a problem getting in to "Connect to PC" I followed the instructions on holding the power and camera buttons, etc. but it won't go to "connect to pc" screen. . it's just keeps on flashing the "Samsung Omnia 7 logo" on the screen everytime I turn it on.
I tried doing hard reset but I cant because once the hard reset screen shows up, the phone just restarts again then the start up loop happens again. .
try this one this is from microsoft answer
http://support.microsoft.com/kb/2547687/en-us
Hello I am trying to fix a friend nexus 7 first gen
the problem is that it keeps flashing the white google logo like its boot looping , the system doesn't even seem to be restarting just a flash on flash off google logo , no nexus logo or anything else at all.
I cannot get into recovery it will just shutoff everytime i try even from the bootloader menu
tablet doesn't have debugging mode on so only thing I can do is work via fastboot
already tried to flash like 5 different versions of android and everytime it finish (succesfully) and goes to restart it just keep doing the same on the google screen.
any help is greatly appriciated, and I have been searching all around the internet for hours now and have seen many solutions to bootlooping which I have pratice before on many of my other android devices but nothing like this problem.
thank you and pardon my english.
When you turn on the tablet with the power button and the screen's backlit turns up, press the VolDown button. This way you can boot into bootloader and flash a factory image provided by Google.
yup like I said before I did got into bootloader and flashed factory stock images like 10 times now and still having the same problem, this is what i usually do when I get into bootloops with any other android device but for some reason this time is different.
its not idle at google and I dont even get to see the nexus logo it just shows the google logo for one second and screen goes black then again the google logo and black screen like infinite restarts with one second delay.
Then it maybe hardware related (corrupted nand/partition/etc) so you might consider to send it to Asus/Google to repair.
Hi guys,
I have an issue with my phone:
Yesterday, tried to restore factory settings, since the phone was quite slow.
A second or so after I confirmed the reset, the phone turned off and wouldn't start.
I took out the battery and it was swollen.
I bought a new battery today, inserted and stated the phone.
What happens now, is that the phone boots, Samsung logo appears, then the TWRP logo appears, from this point, the phone stuck at this logo screen,
and flashes every few seconds (I can't post a video here, so I can share the link in private, if anyone can take a look).
I tried to leave the phone for about 20mins without battery at all, removed SD cards, removed SIM cards, no use.
Trying to boot to recovery or download mode gives the same result.
Tried today with an original battery of a friend's Galaxy S4 , same result.
Does anyone have an idea what I can do?
Thanks in advance for you help
webking said:
Hi guys,
I have an issue with my phone:
Yesterday, tried to restore factory settings, since the phone was quite slow.
A second or so after I confirmed the reset, the phone turned off and wouldn't start.
I took out the battery and it was swollen.
I bought a new battery today, inserted and stated the phone.
What happens now, is that the phone boots, Samsung logo appears, then the TWRP logo appears, from this point, the phone stuck at this logo screen,
and flashes every few seconds (I can't post a video here, so I can share the link in private, if anyone can take a look).
I tried to leave the phone for about 20mins without battery at all, removed SD cards, removed SIM cards, no use.
Trying to boot to recovery or download mode gives the same result.
Tried today with an original battery of a friend's Galaxy S4 , same result.
Does anyone have an idea what I can do?
Thanks in advance for you help
Click to expand...
Click to collapse
Sound to me your power button is stuck/faulty. Does it reboot also when in download mode? If so, then it's your power button. Wiggle it loose or replace it.
Lennyz1988 said:
Sound to me your power button is stuck/faulty. Does it reboot also when in download mode? If so, then it's your power button. Wiggle it loose or replace it.
Click to expand...
Click to collapse
It never gets to download (or recovery) mode...
It keeps flashing at the logo of the TWRP
Trying to boot to download or recovery modes, gives the same results
I don't think it's the power button. Otherwise it would turn off if it is stuck or not turn on at all if it's faulty.
Still, I wouldn't exclude it.
The screen flashing might related to a GPU problem. I don't think it is a problem you can fix yourself.
Hey everyone,
So my phone died and then I got it charged and turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened, I think I might have accidentally turned on the secondary encryption, but this really sucks, I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode. I really hope someone can help or knows what is going on because, I really dont want to lose all my stuff.
Thanks for your time
I tried posting link but im new, if you look up s7 edge frozen encryption, its the first link , another person describes the same issue.
I had this issue. In recovery, tell it to clear the delvic cache. Then try a reboot.
It too a few attempts before the phone would not boot directly into recovery. But once i got it to do a normal boot, it started normally.
Then after it's running, back it all up, boot into recovery, and do a system restore.
Hi I wonder if anyone can help me. I restarted my phone, it asks for my pin which I enter correctly. It then gets stuck on spinning padlock. I've tried a soft reset (I think that's what it's called, holding down power and volume keys). It restarts, I enter pin, it says starting android then gets stuck again. I'm not very tech minded (typical girl). Can anyone help. I'd rather not lose all my photos and apps. Thank you so so much in advance. Toni x
I am facing the same issue, but with a Samsung Galaxy S8.
- Safe mode: doesn't boot
- Recovery mode: works, clear cache doesn't solve the problem.
So since nothing worked to make it work (except the Factory Reset, but I didn't tried this option), I decided to wait in the padlock screen. After 3 hours the phone started.
I guess that the phone is decrypting some big file during startup. Indeed, some days before before this problem happens, I downloaded some big files via torrent (~2-4 GB video files).
I'll delete these files and make some tests to understand the source of this problem.
Have same issue after recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
Have exactly the same issue..Please help
After recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
I tried to root my device trough odin. Odin said it was succesful, but when i turned on my device it said someehing like 'vertification failed, you have to reset your device'. So i tapped the button 'reset'. Then my phone restarted and its now stuck on a boot loop with the 'erasing' screen. It just goes to a blue screen with the android logo and beneath it it says 'erasing'. Then after a few seconds, it restarts and turns back to the screen again.
I cannot get into recovery mode, because you'd have to do it with the power button, volume and bixby button, but the second i try to do that, it just restarts and starts the loop again. Even when my phone stopped with the bootloop and just shut down, when I hold my power button it just restarts the boot loop... I already let the battery drain but then still, it just happens again.
I can only get into download mode, but thats all. I dont know my build number. I already looked at the box my phone came in when i ordered it, but all I could find was:
- an IMEI code
- an S/N code.
- a long code existing of numnbers only.
None of these codes I think were build numbers, only the S/N code contained letters.
So I dont think i have my build number. I cant get into recovery mode since it just starts the bootloop.
Please help
My phone is a samsung galaxy sm-g950f
I hope my phone isnt bricked and this can be fixed.
hi did you find a fix? I have the same issue