Database Users

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

Just info about Samsung Sweden and brickbug

Hello
I just read on Facebook of Samsung Sweden that they recommend people with problems in ics to factory reset the phone. I guess that shows its not so well known about the brickbug.
I thought it was dangerously to do that even with stock kernel?
But I now hope I misunderstand.
Sent from my GT-N7000 using Tapatalk

Ztrindberg said:
Hello
I just read on Facebook of Samsung Sweden that they recommend people with problems in ics to factory reset the phone. I guess that shows its not so well known about the brickbug.
I thought it was dangerously to do that even with stock kernel?
But I now hope I misunderstand.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
There is a smaller risk to brick stock ICS but there is still a risk i believe.. I wrote to Samsung Sweden about brickbug 24 minutes ago before seeing this thread..
I want to install CM9 but there is no stable one yet, only nightlies.. Even if there was one, I dont want to downgrade to GB and then install the CM9 ROM.. Im lazy..

Lazy or not lazy......it should of course be possible to use the phone (not the cheapest one) as it was out of the box.
Its the same thing as if a brand new car would die at the first service........
I think this shows how little a big company as Samsung really cares. They are now to big. Maybe they are more as Apple now. Just dont really care about customers, only money and market.

Its a sick world we live in unfortunately where everything is about money..

Rivan_92 said:
There is a smaller risk to brick stock ICS but there is still a risk i believe.. I wrote to Samsung Sweden about brickbug 24 minutes ago before seeing this thread..
I want to install CM9 but there is no stable one yet, only nightlies.. Even if there was one, I dont want to downgrade to GB and then install the CM9 ROM.. Im lazy..
Click to expand...
Click to collapse
I'm using a cm9 nightly from the end of June and I've gotten up times of more than 200 hours. It is perfectly stable. As a normal phone, I get 2 days running on Edge.
How stable do you need it to be? just to have the words stable in it?

Samsung and the emmc chips

Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Edit: here a link to the issue http://forum.xda-developers.com/showthread.php?t=2091045
Tapatalking on my n7000

msedek said:
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium

Samsung :thumbdown: for that..
click THANKS BUTTON if I helped…
Recognized Distributor™

i know of a close relative with a white s3 , after two months of purchase the set stopped charging from wall socket, the charging worked with laptop ......since he had warranty he was told the motherboard needed replacement and he got that done. the back of it has a spider-like faint grey mark and he asks me if its cracked or what ....he doesnt want to go back to service centre and wont let me root it and he doesnt have patience for xda. he is on 411 still.
he didnt pay for it himself, doesnt have a job yet and its not a gift...pretty chaotic situation if u ask me !!

bloody money grubber *** *****. Poor quality control. There's still no permanent solution for N7000 emmc brick bug.

sepehrthegreat-iran said:
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Talk to him and make him read about it here
http://forum.xda-developers.com/showthread.php?t=2091045
Check if he have an affected device..
Tapatalking on my n7000

I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app

krivinash said:
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000

msedek said:
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
Click to expand...
Click to collapse
The brick bug on the Note shouldn't be a problem anymore. Just flash the PhilZ kernel which gives you root without increasing the flash counter and you're Note is fixed. You can also download Chainfires got brick bug app.to see if your Note is affected at all. Or you download the brick bug app from the play store which does the same.
Sent from my revived Galaxy Note

N7000
My Samsung Galaxy Note is on JB Alliance Rom XXLSC Beta1.1 which comes with it's own kernel and I don't think PhilZ is supporting it, PhilZ and Alliance Cook had a minor misunderstanding/fallout, (I could be getting my Roms mixed up) I've flashed different Roms 10+ times. Started to worry reading threads on here so downloaded the eMMC Brickbug Check app. All's good here

Maybe you wiped on STOCK ICS KERNEL which is known to cause the Brickbug
click THANKS BUTTON if I helped…
Recognized Distributor™

Arobase40 said:
The brick bug on Note is just a legend... ^^
The only safe kernel I'm aware of is the stock one !
The sole time I flashed a non stock kernel I got my Note fully bricked !!!
Click to expand...
Click to collapse
Yeh you are right!so can you post a video wiping on your stock kernel???!!!
I really appreciate the job that Phil and other Devs are doing
Sent from my GT-N7000 using xda premium

Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app

qazibasit said:
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What you believe it's completely different from what's a FACT... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase formating .. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000

msedek said:
What you believe it's completely different from what's a fact... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase commands.. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
Click to expand...
Click to collapse
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
<<do not,under any condition,I repeat do not wipe from your stock ICS recovery>>
sent from galaxy s4(testing dev edition) using xda premium

sepehrthegreat-iran said:
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
sent from galaxy s4(testing dev edition) using xda premium
Click to expand...
Click to collapse
I'm not disrespecting anyone.. Own experience it's bullcrap.. Software developing and electronics engineering its not popular believes or "experiences" everything its done by scientific methods, procedures and knowledge of how things works..
A clear example could be that an engine its build to reach [email protected] if you force the engine beyond that it will get damaged...
Now some people could force it to 160kph and maybe it will work some times.. But at some point it will break.. And you know this because engineers made the engine to work Max at those speeds and RPMs..
It's matter of design.. Not "experiences"
Tapatalking on my n7000

Its been reported that stock ICS is unsafe, since the day it was released, people know about it and avoid it, so anyone saying that it is safe is talking nonsense, if they wanna take the risk and brick their device then thats their choice.
Moving back on to the S3 chips, my GF has had hers several months now and luckily havent encountered any issues at all, I tend to only find device faults AFTER ive purchased them !! i really need to research more before buying
the S3 is 100% stock, my GF wont let me mod it but luckily the device has warranty for the lenght of the contract which is 24 months, so if it ever breaks within this time they'll just fix it for me free of charge
Still, it makes me wonder WTF are a giant company like Samsung doing about this issue ? SGS 2, SGS 3, SGN 1 (unsure about SGN2)
this isnt acceptable from Samsung, regardless if <5% of devices suffer this, I would expect sudden death and insane chips from a cheap chinese knock off, but not a £500 smart phone.

If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app

qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
They knew about it. It was fixed in Galaxy Nexus eMMC firmware but yet they kept shipping other devices with the same firmware.
Cut the crap: Do you know more about the emmc brick bug than some elite and recognized devs here ?

qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Before ICS (gb and older) , Android used recursive deletion.. (no mmc_cap_erase procedures in the kernel).. Samsung didn't know about it because the chip was designed under another required process and there's no way to know this kind of things until you produce something in big scales.. As you said you could spend months wiping everyday on stock ICS and never get brick, but after 6 months of doing it the next day you brick...
Entropy went to samsung and he tried several times to brick a note in front of samsung engineers with no luck.. But the bug its there from the first ICS firmware to the very last and considering we are still officially on ICS, i dont think it's a "retro" information...
Exynos source has nothing to do with the emmc chip and what kind of delete/formating methods will damage it.. Heck even deleting big files (over 500 mb) could trigger the bug.
Once again you are talking nonsense
Tapatalking on my n7000

[Q] If something should go wrong?

Hey there XDA Samsung Galaxy S4 Community, I come to you today to ask, If something should go wrong(mainly a user error) while flashing a new rom/kernel and my phone starts bootlooping like a fruit bowl, is there a fail safe for this phone? Like for the Samsung Infuse 4g no matter what you messed up on the phone all you had to do was put it into download mode and flash stock rom via Oden. It was pretty much unbrickable unless you totally noobed something xD So I was just wondering if this beautiful sex god of a phone had the same fail safe. Get back at me

MaliciousIntent69 said:
Hey there XDA Samsung Galaxy S4 Community, I come to you today to ask, If something should go wrong(mainly a user error) while flashing a new rom/kernel and my phone starts bootlooping like a fruit bowl, is there a fail safe for this phone? Like for the Samsung Infuse 4g no matter what you messed up on the phone all you had to do was put it into download mode and flash stock rom via Oden. It was pretty much unbrickable unless you totally noobed something xD So I was just wondering if this beautiful sex god of a phone had the same fail safe. Get back at me
Click to expand...
Click to collapse
Same with the GS4, if you get to download mode, flash back to stock with odin, no issues here.

TheAxman said:
Same with the GS4, if you get to download mode, flash back to stock with odin, no issues here.
Click to expand...
Click to collapse
Awesome. I've been wondering that, Now I feel well enough about it to finally flash a ROM on my new baby xD

MaliciousIntent69 said:
Awesome. I've been wondering that, Now I feel well enough about it to finally flash a ROM on my new baby xD
Click to expand...
Click to collapse
Whatever rom you choose, just make sure you read, you will be ok, in fact, the hard brick is hard to do on this phone, but it could happen. Good luck

Some of us can testify that soft bricking your device when you start out definitely makes you start reading a lot more. LOL Unless you try flash a rom from a totally different device, you should be able to reboot into recovery and just wipe and restore. If I don't bootloop more than once a week I'm not flashing enough.

Phoneguy589 said:
Some of us can testify that soft bricking your device when you start out definitely makes you start reading a lot more. LOL Unless you try flash a rom from a totally different device, you should be able to reboot into recovery and just wipe and restore. If I don't bootloop more than once a week I'm not flashing enough.
Click to expand...
Click to collapse
Haha i know exactly how that is xDD I used to be an insane flashaholic on my Infuse 4G mainly because the community for that phone was amazingly large at the time.

+1
Isn't having a bootloop not a part of the process, if your not bootlooping, your not FLASHING enuf! yeah baby.

TheAxman said:
if your not bootlooping, your not FLASHING enuf! yeah baby.
Click to expand...
Click to collapse
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.

mattdm said:
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
Click to expand...
Click to collapse
Same here. Never once bootlooped. There's a difference between constantly flashing and correctly flashing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

plwalsh88 said:
Same here. Never once bootlooped. There's a difference between constantly flashing and correctly flashing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
There's also a difference between flashing things that are untested / should work and things that have been fleshed out so to speak.
I flash a lot of untested stuff (mostly built by others, some by me) and have boot looped my phone at least 10 times since 5 May when u bought it.
Bootloops are not damaging as the software is juat not loading (hence the loop). As long as you dont mess with bootloaders you should b3 fine (and loki is not touching the bootloader just feeding it false info)
Sent from my GT-I9505 using Tapatalk 4 Beta

mattdm said:
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
Click to expand...
Click to collapse
All it is, is a statement saying that you are going to get bootloops, guess you guys are perfect. but they happen, easily recoverable, so I think my statements holds true.
Moving along!

_Dennis_ said:
There's also a difference between flashing things that are untested / should work and things that have been fleshed out so to speak.
I flash a lot of untested stuff (mostly built by others, some by me) and have boot looped my phone at least 10 times since 5 May when u bought it.
Bootloops are not damaging as the software is juat not loading (hence the loop). As long as you dont mess with bootloaders you should b3 fine (and loki is not touching the bootloader just feeding it false info)
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Completely agree and knew that would be the response. But based on their posts it sounded more like ROM hopping than testing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

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