Does anyone else know if you can still root and install a recovery for custom ROMS after taking this update? I'm on ME7 now but over night my phone downloaded a update, but I haven't installed it yet.
Not until a new method is released. It will also break safestrap if that's something you care about.
jim2029 said:
Does anyone else know if you can still root and install a recovery for custom ROMS after taking this update? I'm on ME7 now but over night my phone downloaded a update, but I haven't installed it yet.
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, but it's not 4.3. Still 4.2. It will upgrade your phone to the MI1 firmware. There is a root process here- http://forum.xda-developers.com/showthread.php?t=2487142 and Safestrap works, but at the moment there are no MI1 based roms. ME7 based roms will flash without a problem but wifi won't work.
That's nice.... It said it was 4.3 on the notice... That sucks.
riker147 said:
Sorry to be the bearer of bad news, but it's not 4.3. Still 4.2. It will upgrade your phone to the MI1 firmware. There is a root process here- http://forum.xda-developers.com/showthread.php?t=2487142 and Safestrap works, but at the moment there are no MI1 based roms. ME7 based roms will flash without a problem but wifi won't work.
Click to expand...
Click to collapse
I'm thinking I should just go ahead and let mine update. I all of a sudden get the notice to download and install the update even though I'm rooted (not sure how to remove that notice) and figure ME7's boot loader won't be unlocked
Sent from my SCH-I545 using Tapatalk
WarEagleUS said:
I'm thinking I should just go ahead and let mine update. I all of a sudden get the notice to download and install the update even though I'm rooted (not sure how to remove that notice) and figure ME7's boot loader won't be unlocked
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
You can freeze the app SDM 1.0 in Titanium and that will stop the notificiations. Since it's still 4.2 there's no good reason to take this update, in fact it adds some Knox security to the bootloader so you might end up tripping it and screwing yourself if you need to send it to Samsung. Not worth it imo. Also Safestrap works I think but the roms have broken wifi with the update from what I've heard.
Okay thanks bro I'll dl.titanium backup
Sent from my SCH-I545 using Tapatalk
Ok so this is my first post, I dont know very much about rooting and such but I followed directions on how to root 4.2.2 and it was successful but now that this update is out im pretty much just bored with my phone being rooted and I want to update but
When I select install update now it turns off my phone and says "normal boot failed, odin mode, (other things)
Downloading do not turn off target" and doesnt do anything else
I knew how to get out of this so I did and now I dont know what to do
CDWells said:
Ok so this is my first post, I dont know very much about rooting and such but I followed directions on how to root 4.2.2 and it was successful but now that this update is out im pretty much just bored with my phone being rooted and I want to update but
When I select install update now it turns off my phone and says "normal boot failed, odin mode, (other things)
Downloading do not turn off target" and doesnt do anything else
I knew how to get out of this so I did and now I dont know what to do
Click to expand...
Click to collapse
The best thing to do is odin back to stock and let the phone re download the update. BUT remember that once you update your stuck so if your bored now it will be worse once you update. And its not the 4.3 update even though it might say so.
That should be grounds for a lawsuit for false advertisement, lol.
Sent from my SCH-I545 using Tapatalk
Well if its not 4.3 then im not gonna update
can one of you guys give me links or just walk me through how to flash a custom rom onto it?
Im running 4.2.2 baseband version 1545VRUAME7
CDWells said:
Well if its not 4.3 then im not gonna update
can one of you guys give me links or just walk me through how to flash a custom rom onto it?
Im running 4.2.2 baseband version 1545VRUAME7
Click to expand...
Click to collapse
Root
Install Safestrap
Install Recovery
Create Rom Slot
Flash Rom (no re- boot)
Flash SS kernel module
Reboot
All the instructions will be found in Root, SS and ROm threads.
Have fun!!
DON"T TAKE NO STINK'N UPDATES!!
CDWells said:
Well if its not 4.3 then im not gonna update
can one of you guys give me links or just walk me through how to flash a custom rom onto it?
Im running 4.2.2 baseband version 1545VRUAME7
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448726
Thanks a lot guys
I'm going to install the Bonestock ROM
*Edit* thought i was going to put bonestock 1.1.4 on but it keeps failing
is there something im doing wrong?
Size of bonestock is 1.2GB
boot into recovery
choose rom slot
create rom slot 1 for 1500MB of data
1500MB of system
300MB of cash
only 3751MB to use total
finished that
install
choose bonestock.zip
2 seconds in it fails
what did i do wrong?
Related
Ok, so last night my phone downloaded the update (guessing Gingerbread). I'm still running 2.2.1 on my Thunderbolt, as I was out of the country for the past few months. I caught the phone before it completed the installation and thought that if I removed the PG05IMG.zip file from the sd card, that would prevent it from being able to install the update. I turned the phone back on and it began to attempt to install the update again. I would like to flash a new ROM to the phone (as I was simply rooted without a custom ROM before) so that I am running 2.3+ but I don't want to have to re-root the phone. I would like to be able to back everything up before I flash a new ROM. How do I prevent the phone from installing the OTA update that was inadvertently downloaded last night , which will unroot my phone??
Please help! Thank you
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Someone fee free to correct me, but if you flash the CWM recovery it will prevent the update from happening?
Essentially, I just use the phone for wireless tether, so that's mainly why I root. Doubt that changes much of anything...
hallstevenson said:
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Click to expand...
Click to collapse
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
tomgillotti said:
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Click to expand...
Click to collapse
That's a common problem as I recall from a few weeks back. I saw threads about it but never read them as I wasn't affected. I don't know if it's a dead-end or easily fixed or complicated to fix...
Sent from my ADR6400L using XDA App
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
tomgillotti said:
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
Click to expand...
Click to collapse
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Thread moved to Q & A
tomgillotti said:
Any thoughts on how to prevent VZW from pushing this update from now on?
Click to expand...
Click to collapse
Install a non-stock ROM. Don't worry, you can get Sense-based ones that won't be anything "new".
It appears that VZW will eventually force the update so there's no way that I'm aware of to stop it while running stock (even rooted stock).
tomgillotti said:
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Click to expand...
Click to collapse
Flash a ROM that has the update. There are a few around here that are 2.11.605.5 that you flash in Recovery so that it'll stop bugging you to update. Just pick one that is already rooted. You can do a backup of your currrent rom, flash the 2.11.605.5 then restore your data and your all set....
jv
There are a couple threads on preventing ota updates. A quick search will tell you what file to rename and how to.
Sent from my infected thunderbolt.
Hi I'm new to all this rom flashing stuff and I was trying to flash bonestock 1.1 on my me7 gs4. I wiped everything as, I was rooted, and I put the zip file in my sd folder. After this I booted into recovery and it didnt give me an option to install from sd. I am formatted to exfat by the way. I tried using goomanager and ended up bricking my phone which I figured out how to fix, but would still like to use this rom. If anyone could give me a step by step walkthrough it would be greatly appreciated.
Thank you for your time.
If you have ME7 already on your phone, you can't have a custom recovery which is needed to install custom ROMS. Sorry but your out of luck.
gslife said:
Hi I'm new to all this rom flashing stuff and I was trying to flash bonestock 1.1 on my me7 gs4. I wiped everything as, I was rooted, and I put the zip file in my sd folder. After this I booted into recovery and it didnt give me an option to install from sd. I am formatted to exfat by the way. I tried using goomanager and ended up bricking my phone which I figured out how to fix, but would still like to use this rom. If anyone could give me a step by step walkthrough it would be greatly appreciated.
Thank you for your time.
Click to expand...
Click to collapse
ilkevinli said:
If you have ME7 already on your phone, you can't have a custom recovery which is needed to install custom ROMS. Sorry but your out of luck.
Click to expand...
Click to collapse
His link said it could be used for ME7
http://forum.xda-developers.com/showthread.php?t=2384362
This is the link
gslife said:
http://forum.xda-developers.com/showthread.php?t=2384362
This is the link
Click to expand...
Click to collapse
I believe he just means that his ROM is using the updates that ME7 provided, minus the part about locking down your phone for good. As was mentioned above, once you're on the official ME7, there's currently no way to install a custom recovery and thus no custom ROMs.
gslife said:
His link said it could be used for ME7
Click to expand...
Click to collapse
my link says the ROM is BASED off ME7..
Don't put words in my mouth, please.
If you successfully took the ME7 OTA or your phone already came with ME7 build, then you can only root and cannot flash custom roms as of yet. For rooting help check out android development section. Everything you need to know is there.
gslife said:
His link said it could be used for ME7
Click to expand...
Click to collapse
Thank god I didn't update and bonestock came to xda I love being able to choose what I want installed through the aroma installer. This rom is all the good of me7 with none of the evil :angel:
Just picked up my note 3 running 4.3 an hour ago and have not unlocked/rooted/custom recovery it yet, still 100% stock. There is an OTA available and I was wondering if I should take it before rooting?
Thanks in advance
You can either, accept the ota and then root(which I never liked accepting a ota cause Im cautious of downloads being corrupt.) Or you can download a odin version of kitkat and flash thru odin then root(which is what I did)
Thank you very much for your answer MrWicked! One more question if I may ... I just came from US Cellular with the Note 2 to Sprint with the Note 3 - we had very little development there compared to here. I have read a ton of topics on here today about Knox, NAB engineering bootloader, Odin ... etc. and I understand that and how to follow instructions, but I see several different ways. I was wondering which method you used or would suggest? All I am trying to accomplish at this point is root, custom recovery, a (close to) stock rom, (hopefully) not trip the Knox trigger, and run titanium backup (which I read there are issues with that I have to fix afterwards).
Ok couple things, no matter what root method you chose once you flash a recovery it will trip knox. So that being said you have a couple options......
1. You flash via odin the kitkat update and use the "kingo" root method which I personally have not tried and can't give much input on. It is not supposed to trip knox it leaves you rooted but with your stock recovery. Once you flash a recovery you trip knox. But you are stuck with a stock rooted rom in which you could use titanium backup.
2. You flash the kitkat via odin, and you use Chainfire's method(which is what i did personally) I have always had good luck with Chainfire's root methods. but then it trips knox and you can flash a recovery and flash what ever roms you like. But at this time technically you warranty is voided with Samsung.
str8nitro said:
Just picked up my note 3 running 4.3 an hour ago and have not unlocked/rooted/custom recovery it yet, still 100% stock. There is an OTA available and I was wondering if I should take it before rooting?
Thanks in advance
Click to expand...
Click to collapse
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
rcjunky said:
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
Click to expand...
Click to collapse
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
rcjunky said:
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
Click to expand...
Click to collapse
Thanks for the advice on this, may I ask what Rom you are on?
MrWicked1 said:
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
str8nitro said:
Thanks for the advice on this, may I ask what Rom you are on?
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
Click to expand...
Click to collapse
Yep
MrWicked1 said:
Yep
Click to expand...
Click to collapse
I have used TWRP before but mostly CM, I am not familiar with PHILZ at all, Is one better than the other? I really appreciate your time and advice here as I am sure others with the same questions will as well. Thanks!
str8nitro said:
I have used TWRP before but mostly CM, I am not familiar with PHILZ at all, Is one better than the other? I really appreciate your time and advice here as I am sure others with the same questions will as well. Thanks!
Click to expand...
Click to collapse
Personally I love twrp but it doesn't always seem to go as smooth with it. Philz is a modified version of Cm. Philz is rpetty much the go to for least amount of problems.
MrWicked1 said:
Personally I love twrp but it doesn't always seem to go as smooth with it. Philz is a modified version of Cm. Philz is rpetty much the go to for least amount of problems.
Click to expand...
Click to collapse
I will give it a go then, I thought I read something about "NAB engineering bootloader" with Philz, is this something I need to read up on more or self explanatory once I get into it?
Haven't used the Engineering one personally to me it didn't give me any benefits for now for me to flash it
MrWicked1 said:
Haven't used the Engineering one personally to me it didn't give me any benefits for now for me to flash it
Click to expand...
Click to collapse
SOrry for so many questions, but I saw that a few people has issues. Hopefully last question and I will be golden ... For Philz I see to downloads in the link provided by rlmiller - philz_touch_6.12.9-hltespr.tar.md5 and philz_touch_6.12.9-hltespr compared to just one file for TWRP - TWRP KITKAT hltespr-recovery-4.4.img. To use Philz do I need just one file or both? The reason I ask is because in the instructions it says "And lastly....
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file
you now click start and wait until it says pass and reboots. Unplug and wait for startup"
But it does not give instruction for Philz, which is 2 different files that are not the same as the TWRP.
str8nitro said:
SOrry for so many questions, but I saw that a few people has issues. Hopefully last question and I will be golden ... For Philz I see to downloads in the link provided by rlmiller - philz_touch_6.12.9-hltespr.tar.md5 and philz_touch_6.12.9-hltespr compared to just one file for TWRP - TWRP KITKAT hltespr-recovery-4.4.img. To use Philz do I need just one file or both? The reason I ask is because in the instructions it says "And lastly....
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file
you now click start and wait until it says pass and reboots. Unplug and wait for startup"
But it does not give instruction for Philz, which is 2 different files that are not the same as the TWRP.
Click to expand...
Click to collapse
No just flash the stock....let it load up....reboot into dl again...odin cf autoroot....boot up....then reboot dl mode again then you can flash which ever recovery you like twrp or philz.....then load up reboot to recovery I would make a backup then flash Sacs rom....then you should be all good to go. And no prob on the questions it's better to ask then not.
MrWicked1 said:
No just flash the stock....let it load up....reboot into dl again...odin cf autoroot....boot up....then reboot dl mode again then you can flash which ever recovery you like twrp or philz.....then load up reboot to recovery I would make a backup then flash Sacs rom....then you should be all good to go. And no prob on the questions it's better to ask then not.
Click to expand...
Click to collapse
Sorry, I think I didn't explain well. I am going to go with Philz because it worked well for you, but my question was which Philz file:
philz_touch_6.12.9-hltespr.tar.md5
or
philz_touch_6.12.9-hltespr
do I use in whe I get to the TWRP area of the instructions:
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file <----------------------------------- here
you now click start and wait until it says pass and reboots. Unplug and wait for startup
Yeah instead of the twrp file you use the philz tar.md5
str8nitro said:
Thanks for the advice on this, may I ask what Rom you are on?
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
Click to expand...
Click to collapse
I am stock no root at this time. ota update.
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
MrWicked1 said:
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am stock no root at this with the ota update.
I have done a ton of searching and usually don't post because there is something out there but I am losing it. I have a Verizon GS4 with 4.3 MJ7 rooted. I have put off updating for a while because I was unsure what it would do to my root but when I recently tried the OTA to 4.4 it will reboot and try to update but just gets an error and drops me off in the recovery page where I hit reboot now. Then it tells me my update was unsuccessful (thanks android....). I have tried using Odin to update to CM11 and it always fails when i hit start. I tried using kies 3 and it downloads the update, download window disappears, and then kies stays up greyed out until it crashes. I found somewhere that kies 3 is picky so i unmounted the sd card, turned off usb debugging, restarted, everything. I would be perfectly fine with 4.4 or CM11. I dont care. I just want to update....
superseahawk said:
I have done a ton of searching and usually don't post because there is something out there but I am losing it. I have a Verizon GS4 with 4.3 MJ7 rooted. I have put off updating for a while because I was unsure what it would do to my root but when I recently tried the OTA to 4.4 it will reboot and try to update but just gets an error and drops me off in the recovery page where I hit reboot now. Then it tells me my update was unsuccessful (thanks android....). I have tried using Odin to update to CM11 and it always fails when i hit start. I tried using kies 3 and it downloads the update, download window disappears, and then kies stays up greyed out until it crashes. I found somewhere that kies 3 is picky so i unmounted the sd card, turned off usb debugging, restarted, everything. I would be perfectly fine with 4.4 or CM11. I dont care. I just want to update....
Click to expand...
Click to collapse
Well, not sure I understand exactly what you are running or exactly what "update" you are talking about. But, there is not a 4.4 release for the Samsung Galaxy S4 (Verizon). 4.3 is the best you can do if you're talking about getting the latest firmware for the S4. Secondly, if you have 4.3 MJ7 I think the only way you are going to be able to flash anything is with SafeStrap and only TW based ROMs. Even though you may be rooted, you cannot install a custom recovery on MJ7, only SafeStrap. Hope this helps.
jpcalhoun said:
Well, not sure I understand exactly what you are running or exactly what "update" you are talking about. But, there is not a 4.4 release for the Samsung Galaxy S4 (Verizon). 4.3 is the best you can do if you're talking about getting the latest firmware for the S4. Secondly, if you have 4.3 MJ7 I think the only way you are going to be able to flash anything is with SafeStrap and only TW based ROMs. Even though you may be rooted, you cannot install a custom recovery on MJ7, only SafeStrap. Hope this helps.
Click to expand...
Click to collapse
You should start your research by reading this thread. http://forum.xda-developers.com/showthread.php?t=2606501
riker147 said:
You should start your research by reading this thread. http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
Geez, isn't what I said the same as the link you provided?
jpcalhoun said:
Geez, isn't what I said the same as the link you provided?
Click to expand...
Click to collapse
I quoted the wrong post. Sorry.
riker147 said:
Better for them to learn on their own than to have everybody spoon fed the same info every day.
Click to expand...
Click to collapse
Yeah I agree. I thought your comment was directed at me because you quoted my post, maybe I got it wrong.
jpcalhoun said:
Yeah I agree. I thought your comment was directed at me because you quoted my post, maybe I got it wrong.
Click to expand...
Click to collapse
I edited my post as you were responding.
I quoted the wrong post. Sorry.
riker147 said:
I edited my post as you were responding.
I quoted the wrong post. Sorry.
Click to expand...
Click to collapse
Absolutely no problem. That's easy to do. By the way, great advice/thread you gave to the OP.
The user lordazoroth originally posted this method here in the T-Mobile SGSIII forum. However, I have confirmed that it works with the Note 3 (at least with the Verizon variant) with one small difference. Feel free to give us both a "THANKS" if this helped you out.
You can disable the OTA Update notification by following the steps below. Just be aware that there is a small change in STEP #3.
Solution:
Step 1. Delete the update located in /cache/fota/ (may be /data/fota) and then click the update notification prompt to install it, it will instantly fail and the notification will disappear. (My phone rebooted and tried to install the update - this is the point where my Note 3 gave the update failed notification. I just rebooted the phone and went to STEP #2.)
Step 2. Disable otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak
Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/
Step 4. Reboot
(NOTE: The difference in STEP #3 for the Galaxy Note 3 is that the [FotaClient.apk] is named [LocalFotaClient.apk] instead of just [FotaClient.apk]. All of the other steps are the same.
Continue running JB 4.3 and enjoy your Note 3 without that nagging update notification!
But the kitkat update is awesome... so you might want to reconsider doing this
Sent from my Note 3 using Tapatalk Pro
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
lmike6453 said:
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
Click to expand...
Click to collapse
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Grompy said:
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
TMFGO45 said:
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I personally use ROM Toolbox to do it
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
As of this morning...Verizon seems to be trying to "ram the update" onto your note 3
I was rooted and safestrapped on MJE and when I unplugged my phone from the charger this morning...I had a notice that the update failed to install.
I had previously downloaded, but removed the download.
Sent from my Note 3 via Tapatalk
boamuro said:
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
Click to expand...
Click to collapse
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
LeftyGR said:
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
Click to expand...
Click to collapse
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
boamuro said:
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
Click to expand...
Click to collapse
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
LeftyGR said:
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
Click to expand...
Click to collapse
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
boamuro said:
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
Click to expand...
Click to collapse
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Hulk0069 said:
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
boamuro said:
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
Click to expand...
Click to collapse
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Hulk0069 said:
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
boamuro said:
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
Click to expand...
Click to collapse
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
mwshows said:
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
Click to expand...
Click to collapse
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
boamuro said:
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
Click to expand...
Click to collapse
Unfortunately no. Once you have nc4 loaded you cannot go backwards.
<Note3>
bummer