Database Develop

[Q] flashing with sim in

I am considering buying an otterbox and I got to thinking how big a pita it may be to remove the sim and sd card each time I flash. So my question is what does it cause if you leave the SIM in and SD in and flash a new ROM? Whatever problems people say it cause, has anyone experienced the problem themselves?
Some things are just 1 in a million or old stuff that doesnt impact things now so I am trying to figure out the difference.
Thanks!

I do it as rule of thumb. Today I did not. Have not had an issue yet
Sent from my SGH-I897 using XDA App

I've never removed my sim, and never had a problem.....

I am a firm believer that if you are having problems with a ROM delete everything possible and remove the SIM and SD. though I have installed the last few ROMs with both in without any real problems.
i would be interested in finding out why its suggested...

Never removed anything before unless I soft bricked it.
Sent from my SAMSUNG-SGH-I897 using XDA App

I never remove the SIM while flashing. Don't generally remove the external SD card either. I didn't even remove them when recovering from a soft brick. If it's a concern of possibly losing data you can always back it up when you mount them to use on your computer.
To answer your ultimate question you really don't need to be removing the Captivate from your Otterbox.

avgjoegeek said:
Never removed anything before unless I soft bricked it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I've never removed it. Don't see why we would need to to be honest

I've never removed mine, never had trouble. I think it might be one of those "do it if it makes you feel better" sort of things.

I flashed once with the SIM to Cog6 about 5 weeks ago and lost my baseband version. Meaning, I couldn't make calls.
Reflashed to 1 click then back to Cog W/O SIM and I calls worked again

avs420 said:
I flashed once with the SIM to Cog6 about 5 weeks ago and lost my baseband version. Meaning, I couldn't make calls.
Reflashed to 1 click then back to Cog W/O SIM and I calls worked again
Click to expand...
Click to collapse
So reflashing can actually clear SIM settings? Yikes.

plasticdarlow said:
I've never removed my sim, and never had a problem.....
Click to expand...
Click to collapse
neither have i and i have flashed probably 30 times or more and never had a single issue.

I think I took the SIM out like once. And I've done hundreds of ROM flashes.

Only time you would need to take out your SIM is if your phone is soft-bricked so bad you end up having to do the whole take out everything to get it back into DOWNLOAD mode.
Otherwise - I've flashed probably about as much as Mikey (sad for not being a developer/chef) and never had an issue.

[Q] POLL: Bell replacement Phones - staying with JL2 or taking the plunge?

For those that have received their replacement i9000m's from Bell/Samsung, what are you doing to them regarding ROM's and Kernels?
I am awaiting my second replacement (5th phone in total) and am quite hessitant to do anything with it. I am interested in knowing what others have decided to do ...

I'm getting my replacement phone back soon as well, (with JL2). I haven't found a concise answer on here. Has JL2 fixed the problems, or do the new phones still have defective hardware? If not, its outrageous to think that samsung would continue selling these phones, even though they know if has major issues.
I'm probably going to sell my phone on kijji when i get it back, and go buy an HTC. I'm sick of this, and just want a phone that works. right now I'm stuck with my treo pro, that is so slow and crappy.

My new phone (Date 10.12) has JL2 on it and has been working great for almost a month. The only thing I did was root it.
Ian

I'm not screwing around with mine. I'll stress the internal SD card but beyond that, I'm not gonna get too brazen. Right now, JL2 is running fine, is really quick and so is as advertised (2.2 I mean). Mind you, I just got it back yesterday from Bell (just reflashed to JL2 - no replacement or hardware replacement) so I guess time will tell.

I'll probably update it to JL2 (if its not already)...
when I get my phone BACK... been stuck in "In Transit to Store" for a freaking WEEK already... stupid Bell... I mean I can probably walk it from their service stores back to the store in less time... wtf...
I'll consider installing darkyy rom on it when official Gingerbread comes out instead of the gingerbread theme...
I just want my phone back ..!!

I received my phone back with a new board inside and JL2 already installed. I tried to root it with z4root in order to use OCLF abut it keeped crashing on me without being able to do anything. So i uninstalled everything. However, I can say that the phone is working great and is quicker than before.

I noticed that jl 2 in recovery mode gives option to format internal sd card. Until now my phoned is working ok but I haven't restarted it for a week. So.... Lets hope for the best.
Sent from my GT-I9000M using XDA App

ravi31naik said:
I noticed that jl 2 in recovery mode gives option to format internal sd card. Until now my phoned is working ok but I haven't restarted it for a week. So.... Lets hope for the best.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Yes, that is a 3e recovery feature.
Unfortunately totally useless when you get the dreaded 'cannot mount SDCARD error' as it cannot format what it cannot mount.

Sorry for my lack of knowledge on the subject - but are you guys all having issues with failing phones? If so, is it a specific version and how do I find out where I stand?

been following seeARMS bell JL2 rom for a bit and it seems good. he has some info there on corrupted SDs.
ive been using it for a few days and i have no complaints. its located here http://forum.xda-developers.com/showthread.php?t=906977

My phone died a few days after putting on JK4. I got it back on Dec 24, and about a week ago put on Darky's v8. It's not necessarily better, but definitely looks different.

After bricking my 1st one (me or the firmware), I got my new Galaxy S today, installed the speedmod kernel and then darky's 8.0, working perfectly, I've got root, most of aps back in and set up already. Will try it for a few days before running the lagfix. Scored about 1100 on quadrant as is.

The replacement phones are shipping with either JH2 or JL2. Neither of these are proving to prevent sd card failure. Period. Sorry for the bad news.
Btw, I received a jl2 (10.11) phone. I've since flashed a doc rom with jl2 modern. Works awesome so far (no lagfix).

gtg2 said:
The replacement phones are shipping with either JH2 or JL2. Neither of these are proving to prevent sd card failure. Period. Sorry for the bad news.
Btw, I received a jl2 (10.11) phone. I've since flashed a doc rom with jl2 modern. Works awesome so far (no lagfix).
Click to expand...
Click to collapse
I know,. My first replacement shipped with JH2 and failed 5 hours after upgrading to Darky's. My second replacement shipped with JL2 but unfortunately the back button was broken. Waiting for my 3rd replacement phone to arrive - looks like Monday.

I received a jl2 phone replacement. Rooted, unlocked, flashed Darky's v8, then the jl2 modem (no lagfix). Runs great so far!

How do I tell whether my phone is at risk of this or not?

Just got a 11.10 dated brand new phone as a replacement from bell.within an hour I had it unlocked and running doc's jpy with hardcore kernel. I will use this phone the way it I bought it to use
Sent from my GT-I9000 using XDA App

Be aware though, so far I've seen two replacement phones being shipped with JK4 (one of them being my own). I updated immediately to JL2 (stock) and so far it seems fine after some stress testing.

n0th1ng said:
I received a jl2 phone replacement. Rooted, unlocked, flashed Darky's v8, then the jl2 modem (no lagfix). Runs great so far!
Click to expand...
Click to collapse
What method did you used to root it? On my JL2 z4root doesn't seem to work.
Thanks.

Kops said:
How do I tell whether my phone is at risk of this or not?
Click to expand...
Click to collapse
Do you own one of the Bell versions of the Galaxy S (i9000M)? Then you're 100% at risk. The only question appears to be when it'll fail. Who knows, maybe it'll never fail over the life of your contract.
momyc said:
What method did you used to root it? On my JL2 z4root doesn't seem to work.
Thanks.
Click to expand...
Click to collapse
Use SuperOneClick. It works for me every time z4root doesn't (and I know for certainly that it works on JL2).

[Tutorial][Bell Atrix]What need to be done before Warranty Service?

[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...

Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!

With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?

Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk

hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)

scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.

thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.

thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back

ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot

I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.

But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.

binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues

binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.

I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.

binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software

Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !

binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.

seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.

Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen

NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.

[Q] I hard bricked and am getting a new one thru warranty, will I be screwed?

So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks

Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App

If your phone shows any signs of life they will most likely be able to tell that you are not stock.

Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0

For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."

Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.

Will T-mobile able to tell you rooted your phone after you hard bricked it?

So I hard bricked my note 4, nothing works.
I called T-Mobile, they said they will put am insurance on my phone and give me a replacement.
So $8 for insurance and $5 for processing fee.
I only told them the device wouldn't power on, they didn't ask me if I rooted my phone or not.
Today, I got my new phone, and about to send my bricked one in.
So will T-Mobile be able to tell I rooted my phone even after a hard bricked?
Will they charge me if they find out?

I don't think so because the device is unable to boot therefore no trace ever rooted jmo

guccifer said:
I don't think so because the device is unable to boot therefore no trace ever rooted jmo
Click to expand...
Click to collapse
Unless they somehow flash stock and get device to boot up, they can check knox counter

Then the device is not brick. It depends on the brick soft or hard

How do you know the device is bricked?

U can't Odin anything flash nothing like a phone with no soul u can't get the soul back into the phone. Hard brick. Soft brick u can still rivive the phone but idk how never bricked one

guccifer said:
U can't Odin anything flash nothing like a phone with no soul u can't get the soul back into the phone. Hard brick. Soft brick u can still rivive the phone but idk how never bricked one
Click to expand...
Click to collapse
You haven't lived until you've bricked a phone. I have not heard of ANYONE hard bricking a Note 4 yet though.
How was the phone bricked?

Lol I hope I don't brick one lol

ShrekOpher said:
You haven't lived until you've bricked a phone. I have not heard of ANYONE hard bricking a Note 4 yet though.
How was the phone bricked?
Click to expand...
Click to collapse
Wiped everything else beside external sd card through TWRP, then flashed TEKXodus custom ROM through TWRP.
Clicked reboot after it finished, it never rebooted.
I tried everything, no signs of life.
Got a replacement phone through T-Mobile Premium Handset Insurance, have to send the old one back.
Scared they will find out it was customized.
Should I damage the micro USB port on purpose to render it useless?

Kenny243 said:
Wiped everything else beside external sd card through TWRP, then flashed TEKXodus custom ROM through TWRP.
Clicked reboot after it finished, it never rebooted.
I tried everything, no signs of life.
Got a replacement phone through T-Mobile Premium Handset Insurance, have to send the old one back.
Scared they will find out it was customized.
Should I damage the micro USB port on purpose to render it useless?
Click to expand...
Click to collapse
You can't boot into recovery or anything? Does the screen come on at all?

ShrekOpher said:
You can't boot into recovery or anything? Does the screen come on at all?
Click to expand...
Click to collapse
I tried EVERYTHING, no download, no recovery, no nothing.
It's just a black screen.
Think T-Mobile will find out?

Kenny243 said:
I tried EVERYTHING, no download, no recovery, no nothing.
It's just a black screen.
Think T-Mobile will find out?
Click to expand...
Click to collapse
Doubt it. Don't intentionally break it. They may catch you at that. If the screen won't come on you are probably fine. When you connect it to your computer does your pc recognize it? Try that first. Only reason I say that is if I were you I'd want to wipe the data from the phone, otherwise some tmobile tech is going to look at all your picture and everything while they reflash the phone.

ShrekOpher said:
Doubt it. Don't intentionally break it. They may catch you at that. If the screen won't come on you are probably fine. When you connect it to your computer does your pc recognize it? Try that first. Only reason I say that is if I were you I'd want to wipe the data from the phone, otherwise some tmobile tech is going to look at all your picture and everything while they reflash the phone.
Click to expand...
Click to collapse
Ohhh, I'm just scared that I would get charge for it
Going to deny that I modified anything.
Learned my lesson now, not more flashing, I'm too stupid for that, lol.
Being a T-Mobile customer for almost 8 years, hope they were drop the charge even if they do find out.
My computer don't recognize the phone.
I wiped the system and everything before stupidly flashing a custom ROM.
Pretty sure there is nothing on the device.
But my knox is still tripped.
Should I worry about my knox?

I really don't think they'll know/care. I recently jumped from a Note 10.1 with a cracked screen to a Tab S2 in a store ($175 deductible ). The Note was rooted w/ custom rom and I just straight up factory reset it in the store right before trading it in and had no problem at all.
If you're sending it in on an insurance claim I think you might be sending it to Assurion rather than Tmo, who I think cares even less. Either way, you should be fine. Nothing to worry about

Yea what he said

jazzmachine said:
I really don't think they'll know/care. I recently jumped from a Note 10.1 with a cracked screen to a Tab S2 in a store ($175 deductible ). The Note was rooted w/ custom rom and I just straight up factory reset it in the store right before trading it in and had no problem at all.
If you're sending it in on an insurance claim I think you might be sending it to Assurion rather than Tmo, who I think cares even less. Either way, you should be fine. Nothing to worry about
Click to expand...
Click to collapse
But you are doing a jump, and the device is working.
In my case, my phone wouldn't turn on, they might consider it's software problem and check it.
Going to cross my finger :/

Tmobile doesn't ever check for root in any circumstance. They only check if the screen is cracked or if the phone powers on.

It is a possibility that they will check, however it is remote the fact is they've already sent you a new phone.

No, they don't care. I talk to the girl in Tmobile all the time about it and they never check, they are told it doesn't matter. And the fact that I've rooted every person at the stores Note 3 and Note 4 for them.

Kenny243 said:
But you are doing a jump, and the device is working.
In my case, my phone wouldn't turn on, they might consider it's software problem and check it.
Going to cross my finger :/
Click to expand...
Click to collapse
You're all good, breh. I've sent in plenty of rooted phones under warranty and have never been flagged. Nobody gives a d*** about that stuff, they're just trying to get through their day and go home.