Database Users

2.2 coming??????

Check out Eugene_373's twitter. Looks like rhcp has a word that a 2.2 firmware for the vibrant may be coming tonight to samsungfirmwares.com
Sent from my SGH-T959 using XDA App

*fingers crossed*
I don't always complain, but when I do, I #BlameWes

Ovrclock said:
Check out Eugene_373's twitter. Looks like rhcp has a word that a 2.2 firmware for the vibrant may be coming tonight to samsungfirmwares.com
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i can guarantee you it wont come tonight. take my word for it. even if it does we wont officially get it from android for another couple of months .i promise you that.

flameinthefire said:
i can guarantee you it wont come tonight. take my word for it. even if it does we wont officially get it from android for another couple of months .i promise you that.
Click to expand...
Click to collapse
You can't guarantee anything. I know this because you don't even know how the process works.
1st Step: Samsung completes update to be released.
2nd Step: T-Mobile checks it out, makes changes.
3rd Step: Over the air update.
Also check it out, if it goes on that website, it will be here, and you can flash it yourself.

zaduma said:
You can't guarantee anything. I know this because you don't even know how the process works.
1st Step: Samsung completes update to be released.
2nd Step: T-Mobile checks it out, makes changes.
3rd Step: Over the air update.
Also check it out, if it goes on that website, it will be here, and you can flash it yourself.
Click to expand...
Click to collapse
dont wanna flash anything anymore. ill rather wait for the official over the air update. if it does come to that site. how long you think it will take for tmobile to send it over the air. and is that website official samsung website?

flameinthefire said:
dont wanna flash anything anymore. ill rather wait for the official over the air update. if it does come to that site. how long you think it will take for tmobile to send it over the air. and is that website official samsung website?
Click to expand...
Click to collapse
It's so easy to flash? Eh whatever.
T-Mobile has probably already been working with Samsung, so that shouldn't take much time at all. For T-Mobile to roll out the updates (to everyone) will take probably around a week or so. (I don't know why they would delay unless they need to make changes.) Like say they start Monday, some people will receive Monday, Tuesday, etc, until everyone has it.
And yea, I'm not sure if samsungfirmwares.com is an "official" site. In fact I'm pretty sure it isn't. However, a stock rom for 2.1 wandered it's way onto their before, and I mean, the rom before t-mobile even put their hands on it. So who knows.
I say to everyone. Hope for this to be real, BUT! don't expect it.

flameinthefire said:
i can guarantee you it wont come tonight. take my word for it. even if it does we wont officially get it from android for another couple of months .i promise you that.
Click to expand...
Click to collapse
I can guarantee you.....that you have no idea what you're talking about. I said it MAY be on tonight. If its not, then no biggie. If it is, then awesome. But unless you're working in samsung's mobile division and actually have a clue, I say good day to you sir, and stop being the pessimist of the forum.

flameinthefire is just upset because he's been having a lot of problems with his Vibrant with battery and all that since he has made so many threads about his problems in the General forum.
Even if there is a OTA, you can manually push that update without waiting for the OTA as long as someone has the link for it. Just put it onto the root of your sdcard, rename to update.zip then boot into recovery and Reinstall Packages. Good to hear about this though, I'll stick to my idea by saying "I'll believe it when I see it" so I won't be disappointed if this is false. I'm hoping that it is true, but we all hoped the same about CM6 when that thread was made back in July because Gunnerman decided to post a thread about it to get people anticipated for it. (Not blaming anyone but it causes a panic in the community)

zephiK said:
flameinthefire is just upset because he's been having a lot of problems with his Vibrant with battery and all that since he has made so many threads about his problems in the General forum.
Even if there is a OTA, you can manually push that update without waiting for the OTA as long as someone has the link for it. Just put it onto the root of your sdcard, rename to update.zip then boot into recovery and Reinstall Packages. Good to hear about this though, I'll stick to my idea by saying "I'll believe it when I see it" so I won't be disappointed if this is false. I'm hoping that it is true, but we all hoped the same about CM6 when that thread was made back in July because Gunnerman decided to post a thread about it to get people anticipated for it. (Not blaming anyone but it causes a panic in the community)
Click to expand...
Click to collapse
indeed lol i bricked my 2nd vibrant with the disabled keys now its stuck on the triangle screen. and there is no way out.. this sux

zaduma said:
And yea, I'm not sure if samsungfirmwares.com is an "official" site. In fact I'm pretty sure it isn't. However, a stock rom for 2.1 wandered it's way onto their before, and I mean, the rom before t-mobile even put their hands on it. So who knows.
Click to expand...
Click to collapse
It is not even close to being an official site.
Samsung would never purchase such a domain name to use, and even use WordPress on top of that especially with a free, ugly theme.
I already knew this begin with weeks ago when this site started getting mentioned on here, but if this site were official. I would think that there would of been more 2.2 news and release dates to come with those news too. Like I said, if it were to have been official. Which I am not saying it ever would of been with such a domain name, and using WordPress.
One more thing to note, Samsung would also never create a site at Google Blogspot/Blogger. They seem to have actually hosting somewhere else now though (they did not weeks ago).

flameinthefire said:
indeed lol i bricked my 2nd vibrant with the disabled keys now its stuck on the triangle screen. and there is no way out.. this sux
Click to expand...
Click to collapse
Hold down on volume. (Keep holding this until you get to download mode.)
Plug in USB and tap power button for a couple seconds.
Boom. There is no confirmed locked hardware. It is just difficult to time.

zaduma said:
Hold down on volume. (Keep holding this until you get to download mode.)
Plug in USB and tap power button for a couple seconds.
Boom. There is no confirmed locked hardware. It is just difficult to time.
Click to expand...
Click to collapse
i have the new vibrant with the hardware locked. i have tried everything. nothing worked. but what you are saying is that turn the phone on first. and when i see the triangle screen hold down both vol keys till it gets in to download mode?

zaduma said:
Hold down on volume. (Keep holding this until you get to download mode.)
Plug in USB and tap power button for a couple seconds.
Boom. There is no confirmed locked hardware. It is just difficult to time.
Click to expand...
Click to collapse
just tried it. doesnt work

hey but whats the password and username to download it

If I don't get FroYo next week, I'm probably going to start doing drugs.

We will not see froyo on this device soon . I'm sure of it, just like the GPS fix will never come out either. It's completely hardware. How do I know? I bird told me so.

its eclair...http://twitter.com/rhcp011235

Ovrclock said:
Check out Eugene_373's twitter. Looks like rhcp has a word that a 2.2 firmware for the vibrant may be coming tonight to samsungfirmwares.com
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Good job, I got the hint of new 2.1 leak from your post thanks

heygrl said:
If I don't get FroYo next week, I'm probably going to start doing drugs.
Click to expand...
Click to collapse
Very few things on the internet actually make me laugh out loud, but holy **** that was funny.

heygrl said:
If I don't get FroYo next week, I'm probably going to start doing drugs.
Click to expand...
Click to collapse
I'm going to commit suicide
Jesus people, Chill out. When is out, is out. Meanwhile enjoy the phone & don't lose your mind over this

Day one and im bricked..

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

Is there ever going to be a version of recovery that works 100%?

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

[Q] A500 always powers off after booting up

Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy

hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile

dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.

Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna

Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse

Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...

Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk

Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app

sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk

Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna

One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb

Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg

My Note 4 died. Goodbye Yall.

Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.

Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.

jcip17 said:
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
Click to expand...
Click to collapse
Thanks man. You're one of the people who make XDA such a cool place. It ain't like this is goodbye forever. I'll be in here fairly often. Tapatalk keeps me notified of what goes on. See you later.
Sent from my SCH-I535 using Tapatalk

Sorry to hear you're leaving. You've been a great help to a lot of us. I share your feelings toward Verizon, they are just too big to care. So go on.... have some fun with the new toy....there's so much development over there... I'm actually over in the note4 snapdragon side more recently because I'm running all other than Verizon MM stuff. Anyways thanks Stuey for your contributions and help!
Sent from my SM-N920V using XDA-Developers mobile app

stueycaster said:
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Click to expand...
Click to collapse
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.

ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Nice.
Sent from my SM-N920V using XDA-Developers mobile app

ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk

stueycaster said:
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download

ryanbg said:
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
Click to expand...
Click to collapse
Isn't that going to overwrite the Dev Ed bootloader? I guess that's ok though because it's useless as a Developer Edition anyway right? And then I can do the unlock procedure.

It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.

stueycaster said:
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
Click to expand...
Click to collapse
We'll get DE back after you are stable. Uninstall Verizon Software Repair Assistant and Kies if you have it. To me, it looks like a USB/Driver/Software conflict going on preventing a successful flash. Try a different computer, and a different USB cable. Something is interrupting the write process.

I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.

stueycaster said:
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
Click to expand...
Click to collapse
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.

Dark_Plasma said:
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Click to expand...
Click to collapse
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk

stueycaster said:
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Sorry to hear that....hoped you could revive it. For sure these things get blistering hot! I've been flashing like crazy this past week thinking my phone is cookin! So I know what your saying could be the culprit. Still hoping you find a way!
Sent from my SM-N920V using XDA-Developers mobile app