Related
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know much about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Sorry but looks like its gone. Have seen a few ppl able to recover with mskips fix but only if theyre able to turn phone on.
DeathGrind said:
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
A compatible jig may be your only solution if you can't get into download mode manually. A jig would force the phone into download mode, once in download mode you'd be able to flash the stock AT&T firmware through Odin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
DakiX said:
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
Click to expand...
Click to collapse
he's in oregon and I'm in california. I think he is freaking out. But he did say ODin was not recognizing the device.
ADB? ^^
Sent from my Hybrid Note using Tapatalk 2
Error 1. Not reading
Error2. Wrong section... not reading
If he cant get cwm or screen to show something who knows what he did...fix: there is none get another device and read before u do stupid stuff.... u can't expect us to fix lack of reading or not knowing what ur flashing....
im on my phone. expect terrible typos.
DeathGrind said:
oh no. Its his first android phone. He only had it about a week. I can't believe this. I feel so bad for him.
Thanks for the reply
I have been looking for a jig that is compatible with the att samsung galaxy s3 sgh-i747 and had no luck. Do they exist?
Click to expand...
Click to collapse
A jig is a jig the one I bought for my captivate works 100% on gs3, get the jig put into phone if don't boot into download mode, hold down power button with jig still in if that don't work ur screwed .... your better off trying make ur own jig ( YouTube it ) cause if the phone runs out of battery and won't charge then u have another issue...
---------- Post added at 12:38 AM ---------- Previous post was at 12:27 AM ----------
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Just cause "we " can't turn it on don't mean they eventually can't ..
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Moh_Jay said:
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Some people actually have there phones just stop working. Happened to my friend that had a Samsung galaxy nexus, stock unrooted. Just died. There was nothing I could do to fix it.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
If you didnt know a rom could brick a phone you shouldnt be flashing period. Theres always ALWAYS bold letters that says this may brick your phone an or we are not responsible if this breaks your phone... no one with there first android should be flashing till they know android smoothly... *sigh*
Usually 90% of the time your always able to get into recovery mode. From what I've read this only happens when flashing the omega Rom. People make mistakes.
I've rooted and rom'd 100s of phones, and never not been able to get back to recovery.
Sent from my ADR6400L using Tapatalk 2
SiNJiN76 said:
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Click to expand...
Click to collapse
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
jcbofkc said:
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
Click to expand...
Click to collapse
If ppl read things 95% of there questions would be answered. The other 5% could be found by google
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Personally i wait a bit to root rom a brand new phone... however ive never had a issue untill i fried my gs mesmerize so im a lil hesitant
Yeah, this is the first serious issue I have ran into in almost 3 years of mod'ing android phones.
Sent from my ADR6400L using Tapatalk 2
First post, I've been lurking a while so first off thanks to the xda community for providing great tips, instructions and insight. Now I need some more individual help. I'm sorry for the long post but it will help explain the problem.
I've had my TB for a while (had it and the SIM replaced a few times too) but I'm having huge data issues. I've googled the heck out of it and still haven't found a solution that worked. The data worked great back on Froyo but on GB and ICS(Thanks liquid and jester) data sucks the big one. I've tried it in several cities (Knoxville, Miami, Lexington, Louisville, St. Louis to name a few) and still no dice. Here's what I've tried:
##778 trick
Replaced the SIM once on another TB a while back
Removed FB
Changed to many different ROMs
Tried all kinds of radio combos (currently on .19 radio)
Signing in to My VZW
Pulled the SIM and let it sit for a while
I really don't want to unroot and go back to Froyo but I'm about to give up. Anyone got other ideas?
Have you checked to see if something is wrong with the little golden tabs on the back of the phone under the battery cover?
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Have you checked to see if something is wrong with the little golden tabs on the back of the phone under the battery cover?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
This is going to sound really dumb...What SHOULD they look like? I've thought about that once but since I've got nothing to compare it to I never really gave it any more thought. They don't look funky or anything.
Well they should be shiny and not broken at all. I have heard of people getting corrosion on them or being broken. Something you may try is pulling the tabs up very carefully with some tweezers or a pen knife. The phone antennas are on the back cover of the phone and those gold tabs need to make contact on the pads on the cover for you to get signal.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Well they should be shiny and not broken at all. I have heard of people getting corrosion on them or being broken. Something you may try is pulling the tabs up very carefully with some tweezers or a pen knife. The phone antennas are on the back cover of the phone and those gold tabs need to make contact on the pads on the cover for you to get signal.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
They look fine. No signs of corrosion or damage. I called VZW and after talking to them and Assurion for a while they're going to send me another phone. I read somewhere that they're out of TBs and some guys were getting a Rezound. :fingers crossed:
Back in the days of my BB Storm there was certain was that worked better than others (I think it was ones that were made in Mexico). Is there something like that for the TB?
I think some tbs were made better than others. I had the data issue you had for a month and then out of nowhere it was normal.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I think some tbs were made better than others. I had the data issue you had for a month and then out of nowhere it was normal.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yeah I'm starting to get that impression. Do you know if anyone has tried the new leaked radios on stock GB? I downloaded them from the other site, checked the md5 and they don't even load for me. I guess maybe they're only for ICS.
If they send me another TB, I'm rooting right off (after downgrading) and throwing jester's ICS on there with the leaked radios. That ROM is the best I've ever used.
What do you mean they aren't loading for you? Are you putting them on the root of your sd card, renaming them to PG05IMG and flashing them in fastboot?
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
What do you mean they aren't loading for you? Are you putting them on the root of your sd card, renaming them to PG05IMG and flashing them in fastboot?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yeah I put them in the root of the card and flash them as I've done every other radio. They start to load, go through the check process and it returns right back to fastboot. I unrooted and flashed stock so that I could return it, I've flashed radios at stock before so I thought it wouldn't matter. Do you think that has anything to do with it?
If you're s off it should flash. Are you sure the md5 sums are right? Also, try clearing caches first and then flash them. It sounds like a bad download. I honestly would try downloading from a different source and check the md5 again because it sounds like you may end up bricking if you keep trying your current file.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
If you're s off it should flash. Are you sure the md5 sums are right? Also, try clearing caches first and then flash them. It sounds like a bad download. I honestly would try downloading from a different source and check the md5 again because it sounds like you may end up bricking if you keep trying your current file.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
In a earlier post I think I mentioned that I'm running it stock, s-on. I unrooted so that I could exchange it but I'd love to have working data the rest of the day or at least experiment while I'm bored at work. lol I love getting paid to sit around and be bored. Yeah I may try downloading it again. I checked the md5 before I tried flashing it and it lines up with the hash that the uploader posted.
I really appreciate all the help. It's frustrating as heck dealing with a phone that doesn't get consistent data. I have to actually got to sites on my computer to read? Crazy talk!
I guess I missed that you were s on. I don't think the radio will flash s on unless you can get it in the entire ruu. If you're already unrooted I would just return it.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I guess I missed that you were s on. I don't think the radio will flash s on unless you can get it in the entire ruu. If you're already unrooted I would just return it.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Cool, thanks for the info. Maybe if I get a working one my tweaked framework-res.apk will work for Jester's ICS and I can send it to him to try. I think I was making progress on the whole APN thing but it was hard to tell with the TB I had.
If you were me, what would you do in this situation? I had to get a replacement Note 2 and the replacement thankfully came with the VRALJB software installed. I deferred the update to L4 for 5 days.
Would you just root and unlock the bootloader now the easy way, or take the L4 update and do it the harder way? Would either way be beneficial or does it not really matter?
Thanks!
Go ahead and unlock/root. You don't have to do anything further if you don't want to and you never know how difficult it would be to unlock in the future.
When I purchased mine outright it had the older software. I used the jailbreak method and that worked like a charm.
Sent from my SCH-I605 using xda app-developers app
Either way. Just do it on the current software and save a step. Same end result.
Sent from my SCH-I605 using xda premium
As others said doesn't matter. Once you flash aROM you could just flash the LL4 radio and it would be the same as the OTA.
So I guess Odin didn't fix your last one?
Sent from the dark on a Note 2
kintwofan said:
As others said doesn't matter. Once you flash aROM you could just flash the LL4 radio and it would be the same as the OTA.
So I guess Odin didn't fix your last one?
Sent from the dark on a Note 2
Click to expand...
Click to collapse
im guessing it had a emmc failure that some have reported.
Well if you were me you wouldnt think about it and just root when I got my phone I didnt even sign into google first I skipped all that and was rooted within half an hour of owning my phone...Lol so root away mang
mine came with the ota last Saturday night, i waited til Monday to root just because I've always had htc phones, had to get familiar with touchwiz. took me 10mins to root after i couldn't take all the bloatware anymore
sent from my rooted SAMSUNG GALAXY NOTE 2...
droidstyle said:
im guessing it had a emmc failure that some have reported.
Click to expand...
Click to collapse
Good idea. I thought with that failure it went black with no signs of life, but haven't read up on it. It was a strange that Odin of stock didn't fix it for him.... That's usually a guarantee unbrick
Sent from the dark on a Note 2
Yeah guys, odin didn't fix it. I consider myself somewhat of a veteran with phones, rooting, etc. This time it stumped the hell out of me. Absolutely nothing that I did worked.
I want to thank you all for the help, info, etc. I will be back in business soon!
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yeah guys, odin didn't fix it. I consider myself somewhat of a veteran with phones, rooting, etc. This time it stumped the hell out of me. Absolutely nothing that I did worked.
I want to thank you all for the help, info, etc. I will be back in business soon!
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Ya man I've seen you around, I think from the s3 also. I knew you actually knew what you were doing that's why it was so strange Odin didn't fix it. Guess with this beast of a phone we get beast of bugs
Sent from the dark on a Note 2
kintwofan said:
Ya man I've seen you around, I think from the s3 also. I knew you actually knew what you were doing that's why it was so strange Odin didn't fix it. Guess with this beast of a phone we get beast of bugs
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Yup, I had the S3 for a while and was over there. Yeah man, I was chatting to the developer of the Jedi ROM and I sent him the meta folder of the ROM that I flashed for beta testing and he saw some problems. He said it was touching some partitions that it shouldn't be touching.
Anyhow, I guess I learned the hard way to be careful of testing ROMs from devs that I don't really recognize.
Time to root this bad boy and get back in business lol.
Sent from my SCH-I605 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kintwofan said:
Good idea. I thought with that failure it went black with no signs of life, but haven't read up on it. It was a strange that Odin of stock didn't fix it for him.... That's usually a guarantee unbrick
Sent from the dark on a Note 2
Click to expand...
Click to collapse
normally yes...i was just throwing that out there. something was corrupted since recovery was borked.
I was running Scotts CleanRom 4.25 on my s3 and flashed Saberkernel.13.4 and it bricked my sg3.. will not boot into recovery.. the kernal works on my note 2.. but just thought I would post to prevent others from making same mistake. I done the battery pull. and can only get a red light to come on , on the top left of the device. Even tried a second battery I have from wife's s3.. same thing.. and it is not recognized with usb chord either. Had to ship it back to Samsung...
ronschuck said:
I was running Scotts CleanRom 4.25 on my s3 and flashed Saberkernel.13.4 and it bricked my sg3.. will not boot into recovery.. the kernal works on my note 2.. but just thought I would post to prevent others from making same mistake. I done the battery pull. and can only get a red light to come on , on the top left of the device. Even tried a second battery I have from wife's s3.. same thing.. and it is not recognized with usb chord either. Had to ship it back to Samsung...
Click to expand...
Click to collapse
Aaaaand that's why you don't flash anything that's not made specifically for your phone, unless you know it's compatible. Sorry for your loss though. Can you get into download mode? Guess it's too late now, if you already sent it back, but I'm sure you tried to Odin back to stock..
Sent from my Inverted Beans ROM @ 240 DPI
sleevasteve said:
Aaaaand that's why you don't flash anything that's not made specifically for your phone, unless you know it's compatible. Sorry for your loss though. Can you get into download mode? Guess it's too late now, if you already sent it back, but I'm sure you tried to Odin back to stock..
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
yes.. i tried Odin several times.. I could never get the phone to show up on my pc.. reinstalled drivers. rebooted..couldnt get into download mode for anything.. after a day of trying everything.. I said.. OK... I quit... good thing is .. it was my backup phone that I flash with as a hobby.. still have my note 2..
ronschuck said:
yes.. i tried Odin several times.. I could never get the phone to show up on my pc.. reinstalled drivers. rebooted..couldnt get into download mode for anything.. after a day of trying everything.. I said.. OK... I quit... good thing is .. it was my backup phone that I flash with as a hobby.. still have my note 2..
Click to expand...
Click to collapse
Kinda like me I still use my S3 as a backup phone for streaming music on Wi-Fi/hotspot, playing games, hooking it up to my tv, and flashing ROM's when I get an itch, and don't feel like changing my current Note setup. I really like the Galaxy Mod ROM for the S3 mainly because it has Multiwindow, which I can no longer live without!
Sent from my Inverted Beans ROM @ 240 DPI
So, you flashed a Note 2 kernel that is for an Exynos SoC to the SGS3, which is a Qualcomm SoC? I'm not sure why anyone would even think to try this in the first place, so I'm not sure why you felt the need to warn everyone. Also, this is exactly the reason VZW locks the bootloader, because people do things like this and then get warranty replacements.
As for fixing it, you should be able to, but you likely need a USB jig to force it into download mode, then a full Odin tar plus a PIT file so you can re-partition properly.
Exactly what imnuts said. People sending their phones back for warranty replacement due to mistakes THEY made themselves is exactly why verizon is locking bootloaders and why rooting voids your warranty. If people took responsibility for their own actions, the rest of us wouldn't have to pay for the consequences.
Should change the title to I bricked my phone by flashing a kernel that was not made for my phone. The kernel did not brick your phone you did by making a really bad decision.
This thread is bad and you should feel bad, too.
Sent from my Galaxy Nexus using xda app-developers app
This may be the most ridiculous thread I've seen in a long time. But only the fact instead of paying for his mistake he thinks some how is Samsung responsibly, but how completely ridiculous he was to knowingly flash a note 2 kernel on a s3.
op why do you think there are different sub forums for phones and even carriers. You're probably one of the people who flashed an international ROM too. ...Then sent your hard bricked phone in for warranty
Sent from my SCH-I605 using Tapatalk 2
<Facepalm>
Sent from my Galaxy Note II
I can't even comprehend how you failed this hard. I feel sorry for the dead phone.
Sent From My Galaxy Note 2
This gave me a good healthy laugh. Thanks OP :thumbup::beer:
sent from my Note 2
And this is why most people should not be allowed to root and ROM phones....
Sent from my SCH-I605 using xda app-developers app
What the hell? Everyone did my job for me??
Late to the party today, twice!
Sent from my SCH-I605 using Tapatalk 2
so you guys get all high and mighty and tell the guy he screwed up. I think he knows. cut the guy some slack. we've all made mistakes flashing. some bigger than others. he knows what he did wrong. no need to be complete jerks. this is why xda sucks now.
Sent from my SCH-I605 using xda app-developers app
fearjego said:
so you guys get all high and mighty and tell the guy he screwed up. I think he knows. cut the guy some slack. we've all made mistakes flashing. some bigger than others. he knows what he did wrong. no need to be complete jerks. this is why xda sucks now.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Screwing up is forgetting to check the md5 and soft briking. Flashing a kernel made for a different phone ON PURPOSE then, instead of paying for it himself, decides it's somehow Samsung fault. Oh and then posting here like it's the kernels fault is ignorance!
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
Screwing up is forgetting to check the md5 and soft briking. Flashing a kernel made for a different phone ON PURPOSE then, instead of paying for it himself, decides it's somehow Samsung fault. Oh and then posting here like it's the kernels fault is ignorance!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Uh forgetting to check MD5 can be more than just screwing up. Do that with an HTC hboot that is corrupt and no soft brick for you!
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
Uh forgetting to check MD5 can be more than just screwing up. Do that with an HTC hboot that is corrupt and no soft brick for you!
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Well true and I guess doing it with a radio on my note would be pretty bad to.
Sent from my SCH-I605 using Tapatalk 2
Instead of criticizing, just help the person. We all make mistakes. Just find the Odin stock zip of your device. Here's a fix: http://forum.xda-developers.com/showthread.php?t=2065470
kintwofan said:
Screwing up is forgetting to check the md5 and soft briking. Flashing a kernel made for a different phone ON PURPOSE then, instead of paying for it himself, decides it's somehow Samsung fault. Oh and then posting here like it's the kernels fault is ignorance!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Lol you realize he sent the phone back 6 mos ago?
AJ Bryant said:
Instead of criticizing, just help the person. We all make mistakes. Just find the Odin stock zip of your device. Here's a fix: http://forum.xda-developers.com/showthread.php?t=2065470
Click to expand...
Click to collapse
Sent from my SCH-I605 using Tapatalk 4
I know I'm a pain, but I have a few more questions. I'm unable to find the answers that are specific to this device.
I've decided that (at least for now) I'll be keeping the stock ROM that is currently on this phone. I have yet to look at all of the other great ROMs and decide which ones I'd like, and I will eventually do that, but not today.
One of these days, Verizon will be pushing an OTA update. I don't want to lose my root, but if I'm keeping JB, I want the update. Will Voodoo OTA Rootkeeper work on this phone?
Will I get the OTA with a fully debloated device?
What apps do you recommend for a rooted device other than Titanium backup?
As always, any and all help is much appreciated.
If you're debloating the stock rom (using TiBu to remove apps), your phone most likely wont update properly. OTA Root Keeper should work. This phone hasn't had a update so no one can confirm any of this.
Your best bet is to flash a stock based rom (Clean Rom or something similar) and whenever we get an update, the rom developers will update the rom.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
I backed up using twrp to my sd card. I apparently didn't have enough space on the phone, so I did sd. Is that enough or do I need to backup onto my phone as well?
Sent from my SCH-I545 using Tapatalk 2
When an OTA finally rolls out, you will receive a notification. It's not going to force you to update. Then to get rid of the notification, you just need to change a few lines in the build.prop to the newest build number.
Sent from my SCH-I545 using xda premium
My wife's Note 2 was stock w/ root and recovery. Sometimes in the mornings her phone would be in TWRP from where it had downloaded the OTA and attempted to install it. I imagine the S4 will be the same way.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Just read in the root thread that the OTA updates your bootloader and prevents you from flashing the old kernel to root again. BEWARE - Do not update if you plan to keep root.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
If I were to get this update without unrooting first, would I get in trouble/lose warranty with this update?
Sent from my SCH-I545 using Tapatalk 2
bpmamom said:
If I were to get this update without unrooting first, would I get in trouble/lose warranty with this update?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You'll only ever get in trouble/lose warranty if you return a rooted/modded phone. Research Odin and download a stock Odin image. If you ever need to return your phone, just flash that first and you're good to go.
Also look into an app called Triangle Away. I haven't checked this phone ik download mode yet to see if I've tripped the flash counter but Triangle Away is an invaluable app for resetting it (requires root on a stock rom).
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Make the Jump!
To be completely straightforward -- you probably really don't want the new update. From what I've been hearing around the boards, it doesn't really provide any new important (at least not in my eyes) functionality to the device. If anything, it's mostly just a patch for holes that they unintentionally left. Those holes are what allow you to root the device so easily.
You're doing the same thing I did, by the way -- I hung on to the stock ROM for quite some time, and was a little worried to separate. However, I highly recommend just making the jump and going with HyperDrive. It's on release 5.7 at this point, and I've been using it as a daily driver for a few days now. I'ts really solid, you get all of your stock capabilities and functions plus MORE customization. Pretty cool, and much better than whatever Verizon will eventually push out in my opinion.
Good luck with whatever you choose!
I did decide to unroot for now, and go with the update. Sooner or later, after a good root method comes out, I will likely root again. Mostly, I just wanted to see what this update was all about. It's both good and underwhelming. It's good because the phone doesn't lag like it used to, but otherwise underwhelming.
Thank you, everyone, for your help. I'll definitely stick around on the forums. I really like the community here.
A rom would have fixed that lag.
Sent from my SCH-I545 using Xparent Green Tapatalk 2