I'm having a lot of issues with my Note 3 right now and want to return to complete stock (aside from knox 1x1, obviously) in order to see if it was something I did or if I should blame sprint. I'm frequently missing calls (phone doesn't even ring, but I'll get voicemail or on google voice it will say missed call) and I'm going between 3G and 4G all the time. I'm inclined to blame Sprint, since I've had problems with them before and their service is generally not great, but I want to give them the benefit of the doubt and return to stock before bringing it up with them. I'm new to samsung rooting so I'm not sure what all is involved in returning, could someone point me in the right direction? I'd want stock bootloader (on engineering now), most up-to-date baseband, rom, etc.
lazyboy0172 said:
I'm having a lot of issues with my Note 3 right now and want to return to complete stock (aside from knox 1x1, obviously) in order to see if it was something I did or if I should blame sprint. I'm frequently missing calls (phone doesn't even ring, but I'll get voicemail or on google voice it will say missed call) and I'm going between 3G and 4G all the time. I'm inclined to blame Sprint, since I've had problems with them before and their service is generally not great, but I want to give them the benefit of the doubt and return to stock before bringing it up with them. I'm new to samsung rooting so I'm not sure what all is involved in returning, could someone point me in the right direction? I'd want stock bootloader (on engineering now), most up-to-date baseband, rom, etc.
Click to expand...
Click to collapse
Rwilco has you covered in this thread. It's on the first page of the Development Section of the forums.
Hope this helps and you don't have any further issues with your Note 3.
so happy to have found this. in my haste, somehow I triggered knox. and my phone refuses to boot! lovely!
Related
ok about to root and rom. will verizon know if i call them for service questions? what i mean is, i suppose for a tech support call they can do over-the-phone diagnostics. right? if i call for tech support are they able to determine i am rooted and rommed through their diagnostics?
would i need to return to stock prior to making a tech support call to verizon?
thanks
there are honestly very few reps that know anything about the phones they sell
I'm not sure why you'd call Verizon for diagnostics on a device that's not running their software anymore. I'd think talking to the dev would make more sense. I suppose the could tell, but care? Probably not. I told the manager where I got mine that I intended to root it as soon as I got home shd that my old Incredible was already rooted. His only question was how much better the battery life gets.
They will try to help you for sure but they may no be able to since you do not have stock. They can not look up your phone info on their end but they may ask you for info like software or info about the phone from about phone that could give it away. Honestly you're probably better off posting your issue on this forum and having XDA help.
They wouldn't be too helpful not because you rooted but because you have a different piece of software on your phone.
It'd be like calling Microsoft because your copy of Ubuntu is acting up.
>_> big red is all knowing >_> they will find you.. they will GET YOU! >_>
I don't think they can see what software you are using, but I do believe they may be able to see your radio version.
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
littleguevara said:
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone can google "My Verizon.apk Thunderbolt", download it, and put it on their phones. Even non rooted fellas. So no, this should not throw up any red flags other than you are using a modded application.
U r legally allowed to root so dont worry about it
Sent from my ADR6400L using Tapatalk
I did this a week ago, my TB lost 3G completely at the house and 4G only works in PHX. It just happens the wife's D1 had no 3G so I called and we went through some settings on the phone and they checked the IMEI number etc. Found out the following day after talking to several Verizon people that the issue was the SIM card on the phone so I took it in and they replaced it and that fixed it.
I was rooted when I called, I went back to stock before taking it in and replacing the SIM card. They knew nothing at all.
It would be wise to just find help elsewhere. I find that online support is better than verizons anyways
I am an AT&T tech rep, so I can only speak for here. Bu universally most of us, despite carrier, that know what they are doing will answer the same from what I've found.
When someone walks into the device support center with an obviously rooted I won't exchange it for them. I will help them, find answers, and tell them how to fix it. I will also explain any known problems, or past problems, I know about with various roms. But I won't exchange the phone. And it's not to be mean. But often times when a person does come in with a rooted phone the issue they are experiencing is with the radio they flashed or the rom they are using. I see this a lot with the Inspire as is.
If I deem it to be an actual hardware issue and I can very the rom is not the issue then I will tell them how to take the phone back to stock so I can exchange it. For the Inspire I keep a handy sd card with the stock image there that I can flash it back right away.
If I know a phone has been rooted and the person brings it back to me with it flashed back to stock, I will exchange it without a problem. The phone is still under warranty and the warranty does explain in most products that not current software alterations exist (Ie: rooting, clockwork mod, unlock boot loader). If it's back to stock then warranty guidelines are meet.
Now with that being said, I have physical access to the device. Over the phone, the only way they would really be able to know is if they asked the software version, baseband version, kernel version, etc... and knew what they were off hand. Things like that. They can't magically peer into your phone over the air to see what's going on with it. That's the reason for their little script techs over the phone have to run through.
Ultimately, the advice mentioned above about asking the dev or the rom thread is the best you'll get. Most times this is your best place to look after a custom rom has been flashed. If a problem is deemed hardware and not software and you have to have it exchanged, flash back to stock and take it in. No tech rep will care if it was flashed back to stock (unless they are having a really miserable day and can prove it's rooted. but that's few and far between and not specific to any company).
Hey everyone, I like a lot of others have been getting a lot of dropped calls and my gps takes forever to lock on so I'm looking to get my fascinate replaced, hopefully with another phone. However, I'm currently running the newest version of MIUI right now so my question is, do I need to flash back to stock before I make the call? I'm wondering because I know they make you do all sorts of stuff with your phone like updating and whatnot and I'm not sure how my phone is going to react or what's going to show up to the techs I'm speaking with.
If so, what do I need to flash back to? Did they release a new update? Could someone maybe link something that can show me how to get it back to stock?
Last question and kind of a big one is that the phone is physically damaged... However, It's been that way for over a year and the problems have only come up recently. Do I have a shot?
A little bit of reseach goes along way...this topic has been beat to death. You don't need to flash back to stock until the phone is to be sent in! The official verizon Ed05 is the latest build and is in the development section.
Good Day
I went to stock ed05 and was put through a factory reset, software update check, and she even had me go through dial codes to change things which I'm not sure would work while on MIUI. Worst case scenario, make a nandroid of MIUI and flash back after the call. Just make sure to flash a mtd rom prior to restoring
Sent from my SCH-I500 using XDA App
Anything for the cracked screen problem? Like I said earlier the screen has been cracked for a VERY long time and the problems just emerged with the Ed04 update.
You don't have to flash until you send it back but personally, I would before I called. Only because they are going to ask you to try a few things and will probably ask what build you were on. Who knows, going stock may solve your call issues.
Don't know what to say about the broken screen. That's not covered under warranty but missed calls would be. Maybe you could stop by a store and ask them rather than having a tech note your account.
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
I had to send my Captivate to Samsung for repair. it was rooted and they fixed it without any issues.
Most manufacturers will fix hardware issues clearly not caused by rooting. Of course, no promises.
That's the reassurance I needed. I'll get on with it and send it away tomorrow. I'll report back in a very long 2 weeks...
Sent from my SGH-I717R using XDA
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
Best luck.... if you were in America you could just take it to an att store. Just be on a stockish rom and turn it in and they would not notice lol, get another device that day. Idk how things go up in Canada though.
Dont Do It!!!!
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Well he should revert back to stock for sure but you can't roll back the counter. But as long as your stock they may not look at the counter and just fix the phone. It's been said before, there's no known case of Samsung voiding a warranty because of it.
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Because in everyone's experience they'll generally fix hardware problems even if you're rooted. Of course they have to, but they tend to. We all said there were no guarantees.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
It seems like one does not simply revert back to stock. Admittedly I'm new to this but all I can find in the development forum is the Bell kernel. The full bell system doesn't seem to be up, just the At&T. After a factory reset and old kernal I still have super user loaded and all of the bell bloatware gone. I'm sure with some due diligence I could have made a back up right after my original root but I didn't. Frustrated with the mess I created I just set the phone back up with Saurom the way I liked it.
alexige said:
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
Click to expand...
Click to collapse
It's only 14 days here. I've had it since launch on Feb 14th. Bell is synonymous for passing the buck off, contact them online and they tell you to call in, call them and they tell you go into a store, go to a store and they'll tell you to go to the original store of purchase or another another store with a repair tech on duty. Going directly through Samsung has been smooth thus far, I just hope if they have an issue they'll contact me before blowing whistles and charging my bill some erroneous fees.
I bought a Samsung Galaxy Note II and enjoyed it for 20 days before I saw it auto-updating and I stopped it mid-stream. Then I let it (where it still remains) in Airplane mode.
I learned since that if the update from auto-update is done, 4.3's bootloader is no longer available and it can no longer be restored to 4.1.2.
I am learning terms and procedures to the best of my novice abilities, but I am still confused on how and IF I can keep my 'download-in-progess' GNII that is still 4.1.2 at 4.1.2.
Verizon and Samsung say absolutely not as you probably know and that it would be a forced installation and factory reset now or afterwards = 4.3.
SO , my question is:
is there a master link for this procedure (and a best ROM?!)
&
Also do all procedures to accomplish my goal of not updating to 4.3 involve rooting that would void the warranty as FAQ#19 states (? Or is there a non-rooting method?
[OK moderator, be kind as this is my 1st post!]
To stop the update you need to freeze an app called SDM 1.0. You will need to be rooted to do that. I guess you need to decide what direction you want to go in. If you want to unlock and flash roms then you need to do that now, before it updates. If you don't want to do that you can update and stay stock. Just be aware that if you update to 4.3 there is no going back. You can root 4.3 but you cannot unlock the bootloader.
Thank you. I see that xda's FAQ #19 says:
"Q19: Can Verizon scan my phone to see if it is rooted?
There are security features on the VZW servers that can block rooted phones from access. Know that when calling Customer Service, they can actively search your phone and see what version of Android Software you are running."
SO: Question>>> Does it not make sense to root since Verizon might actively search phone and shut me out since I did not do their forced installation?
Perhaps the answer is at best "maybe" since there are members here for sure that have rooted this and not been cut off by Big Red Verizon?
Thank you for the reply. I will look up the info. on that 1.0 program. I will prefer being rooted when I find the proper process (here is superior than youtube vids)
but the possibility of Verizon blocking phone if they can legally makes it illogical to purse rooting, unless I am missing something.
wherewasNORAD? said:
"Q19: Can Verizon scan my phone to see if it is rooted?
There are security features on the VZW servers that can block rooted phones from access. Know that when calling Customer Service, they can actively search your phone and see what version of Android Software you are running."
SO: Question>>> Does it not make sense to root since Verizon might actively search phone and shut me out since I did not do their forced installation?
Perhaps the answer is at best "maybe" since there are members here for sure that have rooted this and not been cut off by Big Red Verizon?
Thank you for the reply. I will look up the info. on that 1.0 program. I will prefer being rooted when I find the proper process (here is superior than youtube vids)
but the possibility of Verizon blocking phone if they can legally makes it illogical to purse rooting, unless I am missing something.
Click to expand...
Click to collapse
That is false. Verizon customer service cannot scan your phone. They do not know if you are rooted. Even if they did, they are not going to cancel your service. They want your monthly payment. If all of us on here have rooted several phones and still have service, don't you think that info you found is false? And if you do believe it to be true, why worry about taking the 4.3 OTA?
Sent From My Sticky Note, Too?
wherewasNORAD? said:
I bought a Samsung Galaxy Note II and enjoyed it for 20 days before I saw it auto-updating and I stopped it mid-stream. Then I let it (where it still remains) in Airplane mode.
I learned since that if the update from auto-update is done, 4.3's bootloader is no longer available and it can no longer be restored to 4.1.2.
I am learning terms and procedures to the best of my novice abilities, but I am still confused on how and IF I can keep my 'download-in-progess' GNII that is still 4.1.2 at 4.1.2.
Verizon and Samsung say absolutely not as you probably know and that it would be a forced installation and factory reset now or afterwards = 4.3.
SO , my question is:
is there a master link for this procedure (and a best ROM?!)
&
Also do all procedures to accomplish my goal of not updating to 4.3 involve rooting that would void the warranty as FAQ#19 states (? Or is there a non-rooting method?
[OK moderator, be kind as this is my 1st post!]
Click to expand...
Click to collapse
If you really think that you will want to root your device eventually then now is the time to do it so you can update when you would like to. Adam Outlet has a step by step method that sounds scaryer than it is, just read throughly and you'll be fine. Good luck in which ever way you decide. :thumbup:
Sent from my SCH-I605 using Tapatalk 2
Thank you
TonikJDK said:
To stop the update you need to freeze an app called SDM 1.0. You will need to be rooted to do that. I guess you need to decide what direction you want to go in. If you want to unlock and flash roms then you need to do that now, before it updates. If you don't want to do that you can update and stay stock. Just be aware that if you update to 4.3 there is no going back. You can root 4.3 but you cannot unlock the bootloader.
Click to expand...
Click to collapse
This was what I was looking for for a while now. Thanks for answering my question.
tl;dr ...HTC EVO LTE unlocked via HTCdev and running CM11 needs to be activated on another Sprint subscriber's account. What should I do to make sure that goes smoothly in the next few hours?
long version:
Good friend of mine just got back from a trip to SE Asia and lost her phone. She's back in good 'ol murica now and needs a handset pronto, but miraculously she's taking my advice and holding off on walking into Sprint and leaving with whatever is there, so she can shop around online and find a better deal.
I currently have an HTC Hero, HTC Evo LTE, and LG G3 that are just backup devices to screw around with, so I can lend one to the cause. The Hero just ain't gonna fly, and the G3 is my primary backup and would rather not lend her that one if possible. That leaves Jewel. Mine is unlocked via HTC Dev and currently running CM. I called up the store we'd be going to just to make sure they didn't get weird about the fact that the bootloader is unlocked for whatever reason, to which they replied that as long as it was originally a Sprint phone (check) and still had its SIM card (check), then they'd be fine with trying to activate it. The fella was more worried about being able to successfully activate it than anything else.
This brings me to my question: has anyone done something similar? Ideally, I'd just do a full wipe and bring it in ready to go, but I'm curious about possible technical issues with the fact it is running CM. Should I flash a ROM based on the latest version of Sense or is that unnecessary? What other things might I keep in mind? I want her to be able to have a phone for a week or however long it takes her to get a good one, then deactivate it so I can resume using it as a project device. It'd be great to just restore a TWRP backup after I get the phone back and be right where I left off.
Usually I find these things aren't as simple though. I don't know when sleeping beauty is going to wake up from jetlag hell since on her schedule it feels like 4am right now (its almost 2pm CST at time of posting), but I'm hoping to get some advice on how to properly proceed in the next few hours here.
I'm just spit balling but I would imagine it would have to be a stock Sprint rom in order for them to be able to activate it.
Sloth said:
I'm just spit balling but I would imagine it would have to be a stock Sprint rom in order for them to be able to activate it.
Click to expand...
Click to collapse
Yup....
I should be more than a bit embarrassed right now, but given how ludicrous the whole situation was a few minutes ago in the store, now it's just funny. Suffice to say, my friend is still without a phone. Silver lining is that I can see the path out and think I can deliver on this as soon as I get home and get some time. Will update later of course!