Just jumped ships from sprint and got my facinate. Today rooted with one click and tried installing clock work. Thmanage rom manager. All seems well then suddenly my phone freezes for ten minutes I have to do a battery pull. Phone wont boot in anyway or form now. No lights or signs of life other than if I hold the power button as long as its pressed. A device labeled SEC S5PC110 Test B/D appears in device manager. And that'd all it will do. Thinking about exchanging it tomorrow afternoon. Just letting the community know what happened to me any thoughts as how or what happened might be able to help future mishaps
I'd try doing an odin flash. Just search the forums for the step by step. If u can get the phone into flash mode.
Yeah dude, definitely try Odin. Did you try flashing cwm from within ROM manager? I ask because that doesn't work for our phones yet, and it wouldn't surprise me if that could cause problems. I would use Odin to flash it back to stock, and then use the very thorough guide on here on how to get cwm going.
Sent from my SCH-I500 using XDA App
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
illtema said:
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
Click to expand...
Click to collapse
Hard for him to do a backup when he got bricked installing CWM LOL
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
I would think that if newer fascinates were boot locked, so would mesmerizes and I first flashed the stock files for Verizon on my phone then went to elements zinc (which is awesome BTW) installed voodoo 1200 kernel and everything is working great for me. Could just be that he got a bunk phone or something
PhoenixPath said:
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
Click to expand...
Click to collapse
I'm thinking it's just Noob users who are bootlocked...
My phone is only a week old everything went fine root,cwm...
wisconsinated said:
I would think that if newer fascinates were boot locked, so would mesmerizes
Click to expand...
Click to collapse
Why would you think that? Same hardware!=same software...or we'd all be running USC's kernel/ROM.
Could just be that he got a bunk phone or something
Click to expand...
Click to collapse
Could be...which is why I said "possibly" instead of "definitely".
Couldn't get to the flash mode even to use odin, went back today and bestbuy swapped it out for me thinking I just got a bad phone, I could also shake the thing and hear raddling with the usb door shut to so im not really surprised. The new one seems to be working better already, eill try root tonight,
Jwahlg said:
I could also shake the thing and hear raddling with the usb door shut
Click to expand...
Click to collapse
Volume toggle. I bet the new one does it.
good day.
chopper the dog said:
Volume toggle. I bet the new one does it.
good day.
Click to expand...
Click to collapse
He's right, the volume rockers rattle like a sumbitch.
Sent from my SCH-I500 using XDA App
My Fascinate is just twp weeks old and One Click and CWM worked just fine for me. BTW I am running JTs super clean rom. Lovin this phone!
Sent from my SCH-I500 using XDA App
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
x10
This is counter development long term.
I further submit that in the future, all root processes require a ten question exam on the users knowledge to work.
Sent from my SCH-I500 using XDA App
Mine crashes sometimes. Even with all original OS. I just pull the battery and all is good.
My volume rocker doesn't rattle, so there is that plus.
Sent from my SCH-I500 using XDA App
Related
i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?
hard reset may work
Sent from my Incredible using XDA App
i tried hard resetting it. this did not solve the problem.
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.
Are you root?
When and how did this start happening?
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.
JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App
JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App
Try the RUU that was posted.
jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen
theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App
Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.
I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure
i was running odin and download mode closed my phone now wont boot up or anything......
Euhmmmmm.... *poo*
just loaded and it has a pic of a cell a caution sign then a pc
*end heart-attack it decided it would work* i love the epic even more now....
PyRo
*please lock*
Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.
bullet2300 said:
Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.
Click to expand...
Click to collapse
I sort of had the same issue, but nothing I do will get the unit to power on. Plugging it in to the charger does not turn the charging light on. And no three button method is working. The screen stays black, no charging light. Suggestions?
Never mind, it did come back.
same problem
epic wont boot, charge, etc
please help
You're going to have to give us info if you want any help.
ROM, What you did right before it happened, etc.
RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.
903tex said:
RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.
Click to expand...
Click to collapse
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App
XtaC318 said:
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah we need a new word for soft bricking. Softing? Broft? Oops?
heathmcabee said:
Yeah we need a new word for soft bricking. Softing? Broft? Oops?
Click to expand...
Click to collapse
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?
How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Sent from my SPH-D700 using XDA Premium App
XtaC318 said:
How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Click to expand...
Click to collapse
you think with all the disclaimers on each and every rom,root,theme,ect that people would understand the risks involved in modding whether its a ps3 xbox360 phone router anything but all logic seems to disappear.
kennyglass123 said:
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?
Click to expand...
Click to collapse
lol
BTW its is thrown around how about saying in your thread title like stuck on a screen, errors in clockwork or other nice terms to help u more,
It is really hard to brick this thing believe me ive done it all, FCs, errors in clockwork, stuck on samsung screens boot loops and yesterday officially bricked!!!
The only reason it bricked is some charge card in a beta bonsai rom, but thats what tep is for.
And remeber if you can see something on your screen of your phone use odin or heimdell to go back to stock if you phone wont charge,gointo download mode or go on or go into recovery then its time to take it in and replace it.
Mnhertz26. Did you fix your epic too or is it another real brick?¿
I know what a brick phone is. Im just tired of people not knowing what to do asking questions that are already explanied and sticky on top of the page. Not researching will cause this problem until people realize that if you dont understand this then you need to read, read, read. I had a wm phone and if you flashed the wrong file...DONE. Atleast with the epic as long as it can get in download mode you should be fine.
brendan802 said:
Mnhertz26. Did you fix your epic too or is it another real brick?¿
Click to expand...
Click to collapse
Another real brick? So far there haven't been any Epic's that weren't recoverable.
Ouch I am so glad I did not run Bonsai on my phone yet I was waiting for i dunno what but dodged that issue.
For those who jacked thier phones but didnt brick persay make sure you have a charged battery before starting and if unabl to charge after the incident you can charge in an external charger to get back into dload mode to odin back to stock or CW flash a back-up
Peace
First off, my tone is from frustration. I've experienced this snafu now on both versions of clockwork recovery. The phone won't completely shut off while charging. If I power the phone down unplugged, then plug it in while off, recovery boots up. If it's plugged in while powering down, recovery boots up after a few seconds.
I suppose I could flash cwm when I need it then flash back to stock recovery. I guess that's what I'm going to have to do until it might get fixed. I thought going to version 3 would fix the bug but apparently not. I've tried to flash a new recovery with rom manager but an error always happens.
I flashed version 2 the way the root guide said and flashed 3 with fastboot. I forgot if thats the way it was done with 2 or what. I am starting to wonder if I'm doing something wrong because I don't see anyone else complaining about this.
herbthehammer said:
First off, my tone is from frustration. I've experienced this snafu now on both versions of clockwork recovery. The phone won't completely shut off while charging. If I power the phone down unplugged, then plug it in while off, recovery boots up. If it's plugged in while powering down, recovery boots up after a few seconds.
I suppose I could flash cwm when I need it then flash back to stock recovery. I guess that's what I'm going to have to do until it might get fixed. I thought going to version 3 would fix the bug but apparently not. I've tried to flash a new recovery with rom manager but an error always happens.
I flashed version 2 the way the root guide said and flashed 3 with fastboot. I forgot if thats the way it was done with 2 or what. I am starting to wonder if I'm doing something wrong because I don't see anyone else complaining about this.
Click to expand...
Click to collapse
Are you looking to bump charge? You've asked this issue a multitude of times and each time its been responded to. (at least in my mind, might be others too) and it is a known issue with CWM recovery and from what I've read Koush isn't really looking at fixing it.
I can't speak for what'll happen in the future but it's not you. That is a known issue with the recoveries we currently have. I believe most of the complaints are in the how to root thread.
^ Shift Faced
I am not talented enough to "fix" the problem but it is discouraging to hear that it isn't deemed important. Maybe I was spoiled with my moment, evo, and epic. It seems as if the shift has the smallest developer base so far. When the evo came out, the devs were all over the place.
Come to think of it, I don't think I've even seen anyone besides myself that has a shift.
You don't think not being able to charge while turned off isn't really a minor problem? And you're using the Moment as a model of progress??
^ Shift Faced
That's what I started on
Yeah, me too. And every ROM was basically themed stock. No CM7, no MIUi, no cool ish like the New Sense. Jeez, they just finally got 2.2 working on it! I'd be using CM7 right now if the headphone jack worked. That ish there excites me.
^ Shift Faced
herbthehammer said:
I am not talented enough to "fix" the problem but it is discouraging to hear that it isn't deemed important. Maybe I was spoiled with my moment, evo, and epic. It seems as if the shift has the smallest developer base so far. When the evo came out, the devs were all over the place.
Come to think of it, I don't think I've even seen anyone besides myself that has a shift.
Click to expand...
Click to collapse
First..the facts show the shift as a far more superior platform to any samsung..probably even the tab..let alone its not that your problem isn't important...it just isn't to anyone but you so there is some importance..with everyone complaining about all these issues and the limited dev support maybe we should figure out whether we want a rom..a kernel..a recovery fixed or a genie in the bottle..patience is the virtue here because everyone keeps flaming about support for this and that..maybe the devs have a life..maybe they died..maybe they think its funny to see people whine and complain like they owe us some kind of development
Sent from my PG06100 using XDA App
google gave everyone a evo that went to the I/O when it comes to the devs the all had a free one from jump i too want cyanogenmod on my shift for the reason i love cyanogenmod BUT its not supported by him oficially
everydaysince87 said:
google gave everyone a evo that went to the I/O when it comes to the devs the all had a free one from jump i too want cyanogenmod on my shift for the reason i love cyanogenmod BUT its not supported by him oficially
Click to expand...
Click to collapse
Toastcfh has a CM7 where everything works but sending MMS and the headphone output. And he's been working on it everyday. And Cyanogen responded to someone asking him on Twitter if there'd be CM support for the Shift and he said "Yes, soon". I think it was on 2/17.
I have a feeling my Shift is gonna be very happy soon
^ Shift Faced
Soon isn't official yet tho I may look into a way to donate to toastcfh then
jesusice said:
Toastcfh has a CM7 where everything works but sending MMS and the headphone output. And he's been working on it everyday. And Cyanogen responded to someone asking him on Twitter if there'd be CM support for the Shift and he said "Yes, soon". I think it was on 2/17.
I have a feeling my Shift is gonna be very happy soon
^ Shift Faced
Click to expand...
Click to collapse
Sent from my PG06100 using XDA Premium App
My clockwork recovery hasn't gaven me any problems
Rob_ec said:
My clockwork recovery hasn't gaven me any problems
Click to expand...
Click to collapse
+1 and I use cwm 3
Sent from my HTC Knight using XDA App
Rob_ec said:
My clockwork recovery hasn't gaven me any problems
Click to expand...
Click to collapse
How did you install yours? Maybe your hardware version of the phone is different than mine? I bought my phone the day after it went on sale. Hardware version 4
This is the tutorial I had to follow to install my recovery..at the bottom of the page someone rewrote the 2nd command to enter and it worked for me..but I had to follow this tutorial & not the one stickied..let me know if this works..
http://forum.xda-developers.com/showthread.php?t=908267&page=6
Sent from my PG06100 using XDA App
herbthehammer said:
How did you install yours? Maybe your hardware version of the phone is different than mine? I bought my phone the day after it went on sale. Hardware version 4
Click to expand...
Click to collapse
They didn't read your post. The boot to recovery from power off while charging is univeral. Its just that very few people care very much.
Jeezimus said:
They didn't read your post. The boot to recovery from power off while charging is univeral. Its just that very few people care very much.
Click to expand...
Click to collapse
Lol +1 to not caring much
Sent from my PG06100 using XDA App
You actually turn your phone off?
there is at least now an official release of clockwordmod:
http://forum.xda-developers.com/showthread.php?t=979778
grandebob said:
You actually turn your phone off?
Click to expand...
Click to collapse
I turn it off and on no problem..I haven't tried while its plugged in..why would I even do that unless I want to boot to recovery which is what people complain about so actually its a benefit to me..
Sent from my PG06100 using XDA App
I still have my phone under the manufacturer warranty and it has been acting wonky lately. I want a new vibrant and I am just wondering what is considered a defect? Im thinking about flashing back to stock and saying my GPS doesn't work, and also I have light leakage from LED buttons. Thanks.
what is "wonky" about it?
Maybe we can fix it... I don't like the idea of helping get a new phone, just for the sake of getting a new phone.
This (and other reasons) are why phone costs so dang much.
Smh...
Sent from my ADR6300 using XDA App
s15274n said:
what is "wonky" about it?
Maybe we can fix it... I don't like the idea of helping get a new phone, just for the sake of getting a new phone.
This (and other reasons) are why phone costs so dang much.
Click to expand...
Click to collapse
Exactly, if it is indeed defective then by all means get an exchange. But if it just running slow then it can prolly get fixed with a flash. I process so many warranty exchanges that in all honesty there was nothing physically wrong with it. A simply odin to stock fixes them.
Sent from my SGH-T959 using XDA App
Marvlet said:
Exactly, if it is indeed defective then by all means get an exchange. But if it just running slow then it can prolly get fixed with a flash. I process so many warranty exchanges that in all honesty there was nothing physically wrong with it. A simply odin to stock fixes them.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And if you are willing to try, check my signature for going back to stock... files and a guide for you.
Random restarts, GPS still doesnt work at all, light leakage on buttons and screen. Ive tried numerous ROMs and I am still having issues with GPS. Ive went to stock and while it fixed my problems with restarts, stock was just to laggy so I went back to custom ROMs, GPS still doesn't work.
I am also having signal problems. Me and my friend bought a vibrant the same day and we have tested in the same room that his gets better reception. In a room where he has H, I am only on Edge. This isn't a problem with the ROM because we are both running Bionix.
If there is any way to fix my GPS/Signal issues then by all means tell me and I wont send my phone in for a replacement.
EDIT: Thank you guys for the help. Could ROMs effect signal/GPS? Like I said above when I compared with my friends phone under the same conditions (same room, same ROM) i was only on Edge and he had H. I've tried Trigger, MIUI, and CM7 and still don't have 3G or H in places my friend does.
Se7enDayz said:
Smh...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thank you for the input I'm glad you gave me some good information as to fixing my phone/getting a replacement.
ROMs COULD be a reason since they have different modems... but if you guys were on the same rom and didnt change the modem, then no....
I have best luck on KB1.
I would ODIN to JFD, root, Flash Trigger and see how your signal/gps goes... if not great, flash the KB1 modem over it (dev section) and see if any better.
If you look in my tips/tricks (first link in signature) there is a fix I do for GPS. Sometimes on a new ROM when it DOES NOT work, I have to do that to make it work. Other roms, it works right after flashing... no real rhyme or reason.
If you want a new phone, i am certain you could get one based off what you said already..... but I would not be surprised if you could make it 100% right.
s15274n said:
If you want a new phone, i am certain you could get one based off what you said already..... but I would not be surprised if you could make it 100% right.
Click to expand...
Click to collapse
not to mention the refurb you get could have the same problems or worse.
Refurbished is what you will get, there are no more "new" Vibrants.
Sent from my CM7 Powered Vibrant
For gps try this http://www.intomobile.com/2010/07/21/t-mobile-samsung-vibrant-galaxy-s-gps-issues-fix-tutorial/
I am using stock KB5, it helped me get a lock in 15-30 sec.
edit: I did mess with gps.conf from hd2 forum, dont know if that helped too.
I just received the ota for 2.3.3 and cannot find a thing anywhere about that has changed. I have noticed the facebook integration is not there and I now have mediahub. Ither than that I am finding nothingness.
Someone please help me out with this. Its getting me really irritated.
On another note there has been one bug I noticed was fixed: the screen going all tweaky when you try to type when its plugged in.
Sent from my R800x using XDA App
Didn't even realize 2.3.3 was being distributed by Verizon now. Happy day!
TheAugust said:
Didn't even realize 2.3.3 was being distributed by Verizon now. Happy day!
Click to expand...
Click to collapse
Yep. I didn't know either. I have no service where I work and when I git in my car and got like 2 miles away I saw a download in progress. Low and behold it was 2.3.3. Build # is 3.0.1.E.0.88
Sent from my R800x using XDA App
how's this panning out for unlocked bootloader / rooted r800x people? Don't wanna brick anything :/
I'm not rooted on my play. Ever since the issues I had with verizon on my fassy I think I'm gonna stay away for the 1st year of contract.
Sorry I cant help you on that subject.
Sent from my R800x using XDA App
Carriers don't typically release changelogs at all.
zerojay said:
Carriers don't typically release changelogs at all.
Click to expand...
Click to collapse
Verizon usually lists the bug fixes in a pdf.
And on a further note, there is nothing on their site stating about any updates
Sent from my R800x using XDA App
meleii said:
Verizon usually lists the bug fixes in a pdf.
And on a further note, there is nothing on their site stating about any updates
Sent from my R800x using XDA App
Click to expand...
Click to collapse
I'm hopping on the Verizon Site now, and i'll see if they'll be so kind as to respond in a forum (sometime) about this update.
Yea my phone tried to do it as well. I stoped it though because im unlocked and on an rooted/debloated stock rom and worried it could cause problems. Not that I could not fix mind you, but it would requre me borrowing a computer as I do not have one
If anyone takes the plunge from a similar position I would love to hear storys
Sent from my R800x using xda premium
looks like i will be one of the first idiots to try and OTA update my unlocked bootloader and rooted VZW play...
yea if you are unlocked and rooted don't do it, phone wont even turn on.
fun fun...
JasonKnight said:
looks like i will be one of the first idiots to try and OTA update my unlocked bootloader and rooted VZW play...
yea if you are unlocked and rooted don't do it, phone wont even turn on.
fun fun...
Click to expand...
Click to collapse
Ouch, that's lame. Do you have recovery accessible?
TheAugust said:
Ouch, that's lame. Do you have recovery accessible?
Click to expand...
Click to collapse
wont even let me set the phone up to let me use fastboot.
looks like i bricked my phone.
went looking thru the menus, first thing that stands out
AUTO BRIGHTNESS HAS A CHECK BOX!!! WE CAN TURN IT OFF!!!
update 2: Swipe is built in!
Holy moley, I might update my phone! If I lock my bootloader that is!
Sent from my R800x using Tapatalk
well this sucks... I don't have a phone now...
paxChristos said:
went looking thru the menus, first thing that stands out
AUTO BRIGHTNESS HAS A CHECK BOX!!! WE CAN TURN IT OFF!!!
update 2: Swipe is built in!
Click to expand...
Click to collapse
I'm not sure how I feel about the included version (3.6.84.26668.26670.1638.Verizon), since it's missing the custom dictionary of added words. The overall look is different, which is fine, and I like the numbers having the top row.
JasonKnigh said:
twell this sucks... I don't have a phone now...
Click to expand...
Click to collapse
=(
How did you guys get the update?
TheAugust said:
I'm not sure how I feel about the included version (3.6.84.26668.26670.1638.Verizon), since it's missing the custom dictionary of added words. The overall look is different, which is fine, and I like the numbers having the top row.
=(
Click to expand...
Click to collapse
im just gonna go ahead and put this right here
http://forum.xda-developers.com/showthread.php?t=1126358
Phone works again
JasonKnight said:
im just gonna go ahead and put this right here
http://forum.xda-developers.com/showthread.php?t=1126358
Phone works again
Click to expand...
Click to collapse
Must have been a ****ty experience. Hopefully people read through the thread and is warned not to make the same mistake.
Do not ota update your phone if you had unlocked your phone.
Sent from my XPlay using XDA App.
Cl8rs said:
How did you guys get the update?
Click to expand...
Click to collapse
OTA (you need to be on data, not wifi)
Update: After playing around a little bit, I realized i have slightly better signal!
Note: tried fastbooting and unlocking bootloader, but all i succeeded in was draining my battery...
Now it's time to try gingerbreak...
update: tried gingerbreak 2x for 20 minutes apiece, on a non formatted then formatted sd card, and got nowhere ...