This is a load of bullcrap! I ran the update on my phone. it says it'll take approx 10 min. Then when it hits 100% it says "Update Failed" "Rebooting phone" The worse part is that the phone hangs on the dam Vibrant screen. Guess I need to do a naniod restore. I forgot to make a backup since i thought that these dam updates wouldn't do this to my phone.
So now I'm stuck on the dam logo screen, with my latest nanoid backup 10 days ago. that's a lot of stuff I'm going to lose on my phone. Is there a way to at least get past this screen without me losing all my information? Thanks! Any way possible!
Related
ok here's what's going on perhaps someone can figure out what's wrong. Last night I had placed my mda on its charger like usual b4 bed. well sonce my battery cover is slightly broken I had placed a some cardboard within the battery door due to the fact that it would "white screen" then rest and get stuck at the loading screen and drain my battery, anyhoo.... well it whitescreened cause my dresser rocked due to my cat stepping on my phone. so I reset it as usual and the splash screen would load then fade to white. after several attempts it finally started to load as usual but then it went to the boot loaderscreen. I had reset it several more times but no luck. I took out the mobo to see if something was stuck and again nope. luckly I had an older mobo that wouldent charge so I had replaced the mobo but does anyone know why it would randomly get stuck on the boot loader screen? I had even did a hard reset in the device and still no luck. if it was a normal computer I would say that it had lost it's OS any ideas on how to fix it so I can get back my phone the way it should be?
-rastlin
update on bootloader
well I was able to aquire tmobiles flasher utility and I attemted to flash the unit to no luck. I went through all the steps and it gave me an error that it cannot retreive data from the device. ok now I am totally stumped. I am open to any and all suggestions
-rastlin
Phone - I400 (Continuum)
So I turned my phone on and it got stuck in a boot up, samsung logo then the verizon would come up and the phone would get stuck there. After i went through the typical remove battery, wait a while turn on again, I still couldnt get it to load. On my last attempt at this instead of any logos, I got a completely white screen with a black bar. I had done no flashing prior to this point. All that will load is the android digging screen. It is detected by odin but nothing will work on it. I have a picture that I will load up when I get back home.
If you have any ideas how to fix this, it would be greatly appreciated.
thebod15 said:
Phone - I400 (Continuum)
So I turned my phone on and it got stuck in a boot up, samsung logo then the verizon would come up and the phone would get stuck there. After i went through the typical remove battery, wait a while turn on again, I still couldnt get it to load. On my last attempt at this instead of any logos, I got a completely white screen with a black bar. I had done no flashing prior to this point. All that will load is the android digging screen. It is detected by odin but nothing will work on it. I have a picture that I will load up when I get back home.
If you have any ideas how to fix this, it would be greatly appreciated.
Click to expand...
Click to collapse
If you have not flashed the phone, I would call Verizon and have them send out a replacement. My very first Continuum did that to me. After I received the replacement, I started flashing it, and haven't had issues with flashing. I have had a total of 4 Continuums. The first one did something like yours. The next two have/had critical memory errors, and this one has a broken camera. I think I am getting lemons... But, when you get refurbished items, one never knows what to expect...
1) It started black screen when I was upgrading to Mango with Zune.
When restart phone and the phone could not boot up ,just into black screen.
2)The phone can enter into Download Mode(Vol up + Camera + Power).
Even I tried to flash I8700XENJK1 with Downloader 7.03, everything looks good , processing bar, success message. The only things was when finished flashing, the phone restarted and booted up into black screen and nothing could be done then.(Downloader 7.14 also tried)
3)trying Device_Update_Support_Tool_for_OMNIA7_KC3_Ver1.2.exe which runs well and no error but when came to restart phone, it still went into black screen.
4)In the black screen, I can not access Download Mode except putting out of the battery and put in again which probably means power is on in black screen.
I am not sure which problem causes this, Flash, CPU or other things. Please help me out of these troubles.Thanks.
How long did you leave it out of interest?
Mine sat at a black screen when rebooting for a good 5 minutes or so...
Freypal said:
How long did you leave it out of interest?
Mine sat at a black screen when rebooting for a good 5 minutes or so...
Click to expand...
Click to collapse
I think when I used the Downloader 7.03 tools, there was a message of waiting for several minutes after flashing.
Beside I wait more than 10 minutes, and nothing changed.
Thanks anyway
benaustin said:
I think when I used the Downloader 7.03 tools, there was a message of waiting for several minutes after flashing.
Beside I wait more than 10 minutes, and nothing changed.
Thanks anyway
Click to expand...
Click to collapse
Sorry dude, hope you get it sorted though!
Hoping for someone can help me.
When I went RTM from NoDo, I got a black screen that seriously was there for like half an hour..I put it down to my laptop being like 7 years old and nearly dead, and just left it alone, done nothing else on it and it eventually finished the update.
When I flashed on my mates computer back to NoDo, it was the quikest thing I had ever seen - updated back to mango and the black screen was there for like a minute.
The problem is, when you pulled it the first time, you really should have left it, I would have for at least an hour. I hope you haven't completely bricked your phone
Spookidoodles said:
When I went RTM from NoDo, I got a black screen that seriously was there for like half an hour..I put it down to my laptop being like 7 years old and nearly dead, and just left it alone, done nothing else on it and it eventually finished the update.
When I flashed on my mates computer back to NoDo, it was the quikest thing I had ever seen - updated back to mango and the black screen was there for like a minute.
The problem is, when you pulled it the first time, you really should have left it, I would have for at least an hour. I hope you haven't completely bricked your phone
Click to expand...
Click to collapse
First, thanks for sharing your update experience.
I have updated the phone several times without black screen once.So when black screen came out, I noticed there are something wrong.
Atfer this happen, I tried flash different version ROM, waiting for a long time.
Now I am hopefulless except some new flashing tools or new rom.
Right I feel silly, knowing this I just couldn't resist trying to fix my "phone", so I've bought a S7 Edge from eBay from a trusted company with a 14 day refund which is good right?
We'll I couldn't rest as the phone was going into boot loops, i.e booting once every 5 times, going into the black screen of death with blue LED.(Had to wait for the battery to drain to 0%) https://youtu.be/K9T_UF-_5ho (Even though it booted at the end after a minute of use it crashed and went back into a boot loop and crashed and then it was fine for like an hour)
It would get stuck if I went to stock recovery, get this weird static line. I did boot into recovery once so I did a factory reset hoping it would fix something, which it did not. So I guess I was going to return the phone, I then had the stupid smart idea that it booting up fully and me activating it and then resetting it would be a good idea, and boy I was wrong. So it went to you know the usual "erasing screen" in which it would get stuck on, I did the hard restart maybe 4 times then it sorta worked the android guy kept spinning until IT JUST DIED.
And here we are now me typing this out, I feel like the company isn't going to accept it back due to it not being "functional".
Absolutely no sign of life now. Not even charging, this has happened before with it when I went into the recovery menu and it got stuck. I waited out an hour and then pressed ALL the buttons and the charging icon appeared but now, now I think it's different.
TLDR: Bad eMMC of phone, caused me to try to reset it and now it's bricked?
Well lesson learned? When things aren't working at the first place don't try to fix them just refuse outright.
Some say the phone can't be bricked but I feel like I really did it this time.
No the phone wasn't rooted, no I didn't flash with ODIN.
http://imgur.com/SxA0Q9b
http://imgur.com/QLLwhot
Just return it.
There is nothing else you can do and I see no reason why they wouldn't accept it unless there's a physical damage.
Sent from my SM-G935F using Tapatalk
Hello, so I have a J7 2017 (SM-J730GM/DS) 32 GB Unlocked Dual SIM which has served me well for a while. I ended up dropping the phone at some point in a sliver of time without a case and the screen cracked. After replacing the screen I noticed if the screen was pressed in a certain area it would go crazy and reboot the phone (crazy as in the pixels would do weird things like dimming, going grainy, like the display shorted in some area, then the phone would reboot itself), probably some error on my installation of the screen and the ribbon cables (I can see an area where it looks creased, it never sat flush with the body of the phone as the OEM screen did). I was able to just be careful and not trigger the reboot for some good time until it happened again and the phone would continuously reboot, allowing me to only get back to the OS through the boot menu, selecting "reboot now". That worked for a while until it would never boot into the OS, just looping at the screen where it says the phone name, where it would vibrate, go black, and go back to the phone name screen. I gave up trying to fix it, as I had a backup phone, and just now had some ideas. I figure the OS is corrupted in some way, I am no master in knowing the details on how phone boots up and such, so I did some research and successfully flashed the most recent ROM onto the phone using Odin 3.14. It still doesn't stop the looping, unfortunately.
Any ideas? I hear people talking about using TWRP or something to do things boot related, but I don't want to possibly mess anything up further nor do I know what they were talking about.
Thanks,
Stella