so i received the OTA update this morning and postponed it until i could look around a bit and make sure it wasn't a disaster (should have looked a bit more). I didnt see much so i figured it would be ok and installed....ofcouse it instantly bricks my phone (FU tmobile/samDung). it would not boot past the "vibrant/samsung" screen (i waited 10+ mins). I then went into recovery mode and restored from a nandroid backup, still wont boot past the same screen. does anyone have any other ideas before i do a complete wipe?
Please searcg before starting a new thread....a quick search found me this.
Thread moved to Q&A
Thread Closed.
Related
Today i woke up to the new Update for the vibrant. So of course i tried to update it. My phone is rooted if that makes a difference running everything else stock though. I did the one click root or whatever it was. Well i clicked update and sat my phone down as i got ready. Come back its at the boot screen where it says Vibrant and Samsung in white. I figured it was just loading the new files and just taking a little long. Well by the time i got to school it was still like that so i removed the battery so it would not overheat. Replaced the battery booted up and stalled on boot screen again. This time it made the opening music but never transitioned screens. So i took battery out replaced it and went into clockwork and did a nandroid. Reset it same thing happened. Tried that with three of my backups of previous dates. all failed. so i decided to wipe all data of the phone or factory reset. still stuck at boot screen.
If anyone can help me it would be much appreciated. if you need any other information just let me know.
same thing here. i've done all those steps. when i get home, im going to try and update the JI6 update through ODIN. i'll let you know what happens.
Common problem, easy solution..
http://forum.xda-developers.com/showthread.php?t=803492
Took an over teh air update while on a road trip this weekend and upon reboot, the screen is showing nothing but semi-random dithered pixels. Looks like the display is pointing at the wrong RAM or something.
Tried a hard reset. Nothing.
I would assume this was just a coincidental hardware failure and nothing to do with the update if I wasn't seeing other reports out there of exactly the same symptoms.
Spent 3 hours on live chat with Samsung (kept getting cut off and having to start all over again). They want me to send it back in - 4-5 days UPS ground there, 3-4 business days to fix, 4-5 days UPS ground back. So my one month old $500 product will be gone for 2 weeks getting fixed from the company's own SW update. (fun note - they do not appear to have actually updated any of their internal tools to support this device - I kept getting asked for a serial number then told what I provided was not correct -- even though it was the one printed on the box and the device).
Decided to see if maybe KIES could help (unlikely) and it can connect to the device and recognizes that it needs an update, but when I try to do the update, as soon as it goes to download the files, the device disconnects. Then when it reconnects, it does the same thing all over again - re-downloading the same files, losing connection, re-acquiring it, loop. loop. loop...
So basically, Samsung, epic FAIL. You really think this is how you go toe to toe with Apple?
Anyone have any advice on whether it might be possible to force the factory firmware back into this thing to see if it is indeed jsut teh firmware being horked instead of the video circuitry?
Do you have CWM recovery?
Most definately you can bring this back by flashing another kernel or ROM via Odin. If you already flashed CWM Recovery before, it's just a matter of clearing cache & dalvik cache. If not, flashing another ROM only takes 10-15 minutes if you are used to it. Or about an hour to read up and do your first flash (read the first post in the Android Development subforum. Come back here if it's not clear. Just make sure you pick the right kernel & ROM).
Mine did the same once with a previous update. It would start up eventually though (after several minutes). As mentioned in the previous post, if you can get into Recovery (hold Volume-Down and Power toghether until 2 icons appear), a wipe of the Cache and/or a factory reset will probably bring it back to life.
Samsung & software, it remains a troublesome combination .....
PS. If you have got it up and running, disable checking for new updates. Once an update has been downloaded, the Tab keeps bugging you with popups to install it, even though you tell it never to. 2 days ago, the update question popped right up on the spot i was to tab a link on a website, firing off the update instead. It immediately wrecked my Tab. Luckily i had CWM Recovery flashed earlier, so a clear cache & clear Dalvik cache solved it.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi all -- I have a situation and am at a loss, I've searched the other reads and found nothing QUITE like this (if there is and I missed it, I apologize). (Let me note: I am not new to flashing ROMs, SBFing, ADB, etc. -- no expert, but not new). Basically, I'm hoping someone might have an answer as to whether I'm looking at a hardware issue or not at this point.
Had NT rooted, installed CWM using one-click app. One day I went to turn on my NT and it went to the white Read Forever screen and stayed there for hours (literally). I held the power button for 30+ seconds, it turned off, and I tried to turn it back on -- same thing: Read Forever screen Forever. I could reboot into CWM (installed internally) and still can. I tried to flash the recoveries out there in the FAQ thread, I tried the Ubuntu recovery, etc. I'm confident I followed the directions in all of them. The Ubuntu Recovery went through to the part where it says to power down and remove the SD card and I did that. Turned it back on and Read Forever screen stuck.
Now, the strange thing is, no matter what I try to do, every once in a while it WILL boot all the way through. (This has been going on now for about 2 weeks until I can get the opportunity to try different things, etc.) When it does boot up it's exactly in the state it was before all of this started a few weeks ago -- no matter what I've tried -- flashing albertwertz's recovery, the Ubuntu recovery method, etc.
The LAST time I got it booted up (about 3 days ago), I attempted the flash stock recovery (through the one-click app) + the unrooter app, etc. to be able to get back to stock recovery and deregister, etc. That process SEEMED to go exactly as planned (stock recovery said it flashed, unrooter posted success message, etc.). Device restarted, got a boot loop through three attempts and then a freeze on the Read Forever. When I tried to restart by holding the N + Power button and getting to Factory Reset it goes to CWM, suggesting the previous process while booted up did NOT work.
I'm at a loss. I've tried different SD cards. I've Google searched the issue. I've tried everything I could think of (that's not to say I've tried everything -- hence why I'm asking here). If anyone has an answer, a suggestion, I'd appreciate it.
Space your question next time
Space your question next time cuz i did not bother reading everything
flash a random rom from the development. I use
http://forum.xda-developers.com/showthread.php?t=1494367
[ROM] Stock 1.4.0 + Root + Apps + Mods - GO Launcher [No B&N Store|Rebloat] 15 FEB
BUT IT DOES NOT MATTER
if that does not work for you then
http://forum.xda-developers.com/showthread.php?t=1470910
this is recovery for 1.4.0 BY ADAM OUTLER
not albertwertz
QUESTION: how the hell am i a senior member when you are a junior member.
i joined this epic forum last year when i was like in the friggen 8th grade
Edited with spacing.
As far as Junior v Senior, I tended to respond elsewhere so my posts are low but I'm changing that tendency, particularly with the NT (hopefully).
Sent from my DroidX using Tapatalk
424aca said:
Space your question next time cuz i did not bother reading everything
flash a random rom from the development. I use
http://forum.xda-developers.com/showthread.php?t=1494367
[ROM] Stock 1.4.0 + Root + Apps + Mods - GO Launcher [No B&N Store|Rebloat] 15 FEB
BUT IT DOES NOT MATTER
if that does not work for you then
http://forum.xda-developers.com/showthread.php?t=1470910
this is recovery for 1.4.0 BY ADAM OUTLER
not albertwertz
QUESTION: how the hell am i a senior member when you are a junior member.
i joined this epic forum last year when i was like in the friggen 8th grade
Click to expand...
Click to collapse
you have more posts thats why...
Stuck in "loop" after OTA 2.3.5 update on rooted Photon. Any way to get out of this?
Just curious if anyone knows any trick to get out of this loop.
I've got a rooted photon with 2.3.4, and I've been getting the notification to update to 2.3.5 from Sprint.
The message states that "a new update is available for your phone", and I've just been clicking the "install later" option because I know it doesn't work if my phone is rooted and I have a custom boot loader.
So I think this morning when my alarm was buzzing to wake me up the software update screen popped up and I accidentally clicked "Install now" when I was trying to snooze the alarm.
It rebooted into my bootloader, says it's trying to apply the update, and then says that it failed.
When I reboot the phone, it boots up like everything is normal, I get to my regular homescreen and then it realizes that the update didn't apply so it restarts immediately into bootloader, and the update fails all over again.
Does anyone know of any way to get out of this loop? Like, there has to be some flag flipped in the main system that's telling it that it needs to reboot to apply the OTA update. Is there a way to turn this flag off so I can keep using my phone like it was?
In the mean time I did a nandroid backup of the current state, and then restored an old nandroid backup from several months ago so I could use the phone for now (which sucks cuz I've made alot of little changes since then).
I haven't been on the site for a while, and I'm really busy throughout the day so I don't really have that much time to search through dozens of old threads, even through I tried looking for similar issues (considering if a fix for this problem exists it was probably discussed when this OTA update first popped up several months ago).
I'm sure this question has been asked a bunch so flame away if you must, but I'm just hoping someone can point me in the right direction if a fix or trick exists to get out of this situation without having to completely wipe my whole phone and start over.
Thank you,
--Hammy
Looking for some help, and though my title may sound familiar, in all the OTA when rooting threads I've read I didnt see anyone with it.
So Ive had the phone a couple of weeks, I stupidly forgot to check for updates before unlocking and rooting. Phone was unlocked and rooted using the All in One kit, custom recovery is CWM touch GSM. First thing after unlocking I made a nandroid backup. Then unrooted, setup the phone like i wanted and made another backup (rooted). It was at this point I checked for updates, see there is the new update (ending in .15) that enables the LTE bands. Tried to update and it fails, from the research I then did (shouldve done first, I know) it seems to be because I need stock recovery/unroot. Everything Ive read seems to point to people with the original unlocked/rooted ROM needing to reflash the stock recovery and OTA should work.
So I track down the stock recovery (have tried with 2 different files-same results), go into the whole thing, phone reboots, I sit through the recovery screen (blue circle made of arrows,phone, blue progress bar) progress bar completes, phone shuts off...and then nothing.(Having tried this a few times I have given it at least 5 minutes before trying to turn it on) When I pushed the power the capacitive buttons blink but nothing happens. I have to hold down the power button long before the phone finally boots.
Seems fine and then a message pops up saying update failed, to wait for a future update. I check the phone info and the it lists the new version (ending in .15, original was .12). I was thinking maybe it did update and was going to give it a try but then noticed my Wifi will not turn on, the switch is moved to on, its says its turning on but then eventually times out and gives me an error. I cant for the life of me figure out what step I missed or where I went wrong. I went back to my original nandroid backup and re-rooted and started from scratch which is what Ive been using.
Any help would be appreciated, sorry for the length.
Incredibly short version: Stock unlocked rooted, flashed stock recovery to do OTA update, update fails and breaks wifi, totally lost