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.
Curious if anyone has tried this on the Sprint version with/without success (it backs up your EFS to your internal storage). I'd be careful if you want to try it though, my Note is bricked and I don't know if that caused it (it looked like it was successful) or when I was enabling/disabling KNOX notifications for an app I released. Granted, it could have been a coincidence and unrelated to both, but I doubt it.
I was unable to use Odin to restore the phone. I can get into Download mode, but I've tried numerous combination of using Garwynn's .pit file, the official Samsung stock tar, formatting data/cache in stock recovery, and enabling Nand Erase All option in Odin. The phone just comes up and says "Process system is not responding", reboots, and does the same thing over and over. Current binary shows Samsung Official, system status says custom. If anyone has any ideas on that, I'd love to hear it
But I'm really curious if anyone tried adb reboot nvflash this before on the Sprint version.
-viperboy- said:
Curious if anyone has tried this on the Sprint version with/without success (it backs up your EFS to your internal storage). I'd be careful if you want to try it though, my Note is bricked and I don't know if that caused it (it looked like it was successful) or when I was enabling/disabling KNOX notifications for an app I released. Granted, it could have been a coincidence and unrelated to both, but I doubt it.
I was unable to use Odin to restore the phone. I can get into Download mode, but I've tried numerous combination of using Garwynn's .pit file, the official Samsung stock tar, formatting data/cache in stock recovery, and enabling Nand Erase All option in Odin. The phone just comes up and says "Process system is not responding", reboots, and does the same thing over and over. Current binary shows Samsung Official, system status says custom. If anyone has any ideas on that, I'd love to hear it
But I'm really curious if anyone tried adb reboot nvflash this before on the Sprint version.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2471421
gerald410 said:
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2471421
Click to expand...
Click to collapse
Thanks for the link, but it didn't work. On the Sprint version, efs is mmcblk0p11 (12 is modem1) but no go. Seems like the issue was directly related to backing up the efs, I guess KNOX thinks that someone might be trying to pull some info from the phone that it wants to keep secure? Very silly that it would let you run that command without any warning. I ran that the other day on a friends GS3 and that's how I found out about it.
-viperboy- said:
Thanks for the link, but it didn't work. On the Sprint version, efs is mmcblk0p11 (12 is modem1) but no go. Seems like the issue was directly related to backing up the efs, I guess KNOX thinks that someone might be trying to pull some info from the phone that it wants to keep secure? Very silly that it would let you run that command without any warning. I ran that the other day on a friends GS3 and that's how I found out about it.
Click to expand...
Click to collapse
I wish you luck Viper!
gerald410 said:
I wish you luck Viper!
Click to expand...
Click to collapse
Thanks man, I will go get the phone exchanged at Best Buy tomorrow. I'm home for the weekend and they wouldn't exchange it last night at the store here (used to work there) cause I didn't have the box. Apparently, they need that to get credit for phone returns now or they get hit with the full cost of the phone. I was kinda ticked off about that, but I do still have the box back up at school, so I'll get it replaced tomorrow. The thing that really ticks me off is what if I didn't have the box? You think you can deny a return within 14 days if I don't have the box? I would have fought it at that point, but I figure why cause an issue if I can just handle it tomorrow.
-viperboy- said:
Curious if anyone has tried this on the Sprint version with/without success (it backs up your EFS to your internal storage). I'd be careful if you want to try it though, my Note is bricked and I don't know if that caused it (it looked like it was successful) or when I was enabling/disabling KNOX notifications for an app I released. Granted, it could have been a coincidence and unrelated to both, but I doubt it.
Click to expand...
Click to collapse
So, to be clear, you suspect issuing that command, caused the problem? If so, there shouldn't be an issue backing up EFS, via other means (like TWRP recovery). Does that sound reasonable, or am I way off?
By the way, thanks for all you do for the community.
Sent from my SM-N900P using Tapatalk now Free
-viperboy- said:
Curious if anyone has tried this on the Sprint version with/without success (it backs up your EFS to your internal storage). I'd be careful if you want to try it though, my Note is bricked and I don't know if that caused it (it looked like it was successful) or when I was enabling/disabling KNOX notifications for an app I released. Granted, it could have been a coincidence and unrelated to both, but I doubt it.
I was unable to use Odin to restore the phone. I can get into Download mode, but I've tried numerous combination of using Garwynn's .pit file, the official Samsung stock tar, formatting data/cache in stock recovery, and enabling Nand Erase All option in Odin. The phone just comes up and says "Process system is not responding", reboots, and does the same thing over and over. Current binary shows Samsung Official, system status says custom. If anyone has any ideas on that, I'd love to hear it
But I'm really curious if anyone tried adb reboot nvflash this before on the Sprint version.
Click to expand...
Click to collapse
EXACT SAME THING happened to me. I was able to return it though bc my buddy works for an official retailer. Im just going to flash ONE custom ROM and deal w it UNTIL the whole SE-Linux issue is figured out. Its sorta my ONE FREE CHANCE I know this offers up absolutely NO help-lol-but indeed-the same exact situation happened to me but ONLY after using a TWRP restore that I had only a few hours before, created as a fail-safe. After that point, I tried every single thing you had mentioned-only 3or4x over! DO NOT RESTORE A NANDROID BACKUP is the prime lesson learned
milton007 said:
EXACT SAME THING happened to me. I was able to return it though bc my buddy works for an official retailer. Im just going to flash ONE custom ROM and deal w it UNTIL the whole SE-Linux issue is figured out. Its sorta my ONE FREE CHANCE I know this offers up absolutely NO help-lol-but indeed-the same exact situation happened to me but ONLY after using a TWRP restore that I had only a few hours before, created as a fail-safe. After that point, I tried every single thing you had mentioned-only 3or4x over! DO NOT RESTORE A NANDROID BACKUP is the prime lesson learned
Click to expand...
Click to collapse
Wow, really? I've restored nandroids, at least 10 times, in the 4 days I've had the phone. Maybe I'm just lucky. Thanks for the info, though.
Sent from my SM-N900P now Free
LMMT said:
So, to be clear, you suspect issuing that command, caused the problem? If so, there shouldn't be an issue backing up EFS, via other means (like TWRP recovery). Does that sound reasonable, or am I way off?
By the way, thanks for all you do for the community.
Sent from my SM-N900P using Tapatalk now Free
Click to expand...
Click to collapse
Yes, I believe that to be the issue. I don't want to test it again though lol I hope to have a solution soon for backing up EFS in a safe way
milton007 said:
EXACT SAME THING happened to me. I was able to return it though bc my buddy works for an official retailer. Im just going to flash ONE custom ROM and deal w it UNTIL the whole SE-Linux issue is figured out. Its sorta my ONE FREE CHANCE I know this offers up absolutely NO help-lol-but indeed-the same exact situation happened to me but ONLY after using a TWRP restore that I had only a few hours before, created as a fail-safe. After that point, I tried every single thing you had mentioned-only 3or4x over! DO NOT RESTORE A NANDROID BACKUP is the prime lesson learned
Click to expand...
Click to collapse
LMMT said:
Wow, really? I've restored nandroids, at least 10 times, in the 4 days I've had the phone. Maybe I'm just lucky. Thanks for the info, though.
Sent from my SM-N900P now Free
Click to expand...
Click to collapse
Restoring won't cause the issue I had, if anything, you'll get FCs and knox warnings that can either be fixed with my TB Restore Fixer app or using a kernel that is SELinux permissive.
Sent from my Nexus 7 using Tapatalk 4
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.
It's been 3 days I've been up and down the forums, was on CM11, dirty flashed over the nebulas, ran into a few problems decided to go back and make it a clean flash, got 4.1.1, couldn't find one CASUAL that worked, went to 4.1.2, same problem, Yes i tried other cables, other computers, no difference.
Then updated 4.3 boot looped all kinds of problems tried Nand Erase All, didn't work, one way or another root66 stopped working. nothing would flash, it would all fail or if it did say it worked it just boot looped,
I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
To work. So now I'm 4.3 Stock, with no root.
I want to get back to Nebulas,
I want to take this step by step because it's been a nightmare and I can't find any solutions to questions that have been asked before.
From what I research the next step is to flash:
sch-i605-16gb.pit file
+
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
But when I try I get sboot.bin fail. Got a tip somewhere to flash the just the PIT, this actually fixed it without needing to flash anything else.
Now I know I'm down grading so it's going to boot loop because nothing is compatible. Boot into recovery and do a wipe to fix that. I boot into the OS just to make sure I'm doing 4.1.2. Which it is. and enable usb debugging.
Now to root and bootloader.
I try the newest verison of CASUAL R991b-JenkinsBuild
I get Error Failed to confirm end of pit file transfer
Pit Upladoing Failed
ok, so I pull battery and reboot. Trying R515b because that's the one in the tutorial:
I get Pit upload successful
Error: Bootloader upload failed!
This corrupt the bootloader and it will fail the boot, taking a step back and reflashing the mc3 fixes this.
Then I try this tip "most times you will need to delete and uninstall the Samsung Mobile usb from your Computer's device manager while ur device is connected already in download mode. i failed several times to execute casual successfully until i did this and it worked like charm!"
That didn't do anything, Tried verision 535 same results.
Said screw that I'll just flash some Root and recovery. But it always fails to flash recovery.img or if i put in the PIT and say repartition it will fail after the NAND Write Start. I've tried
openrecovery-twrp-2.6.3.1-t0ltevzw.img
CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.tar.md5
philz_touch_6.07.9-i605.tar.md5
and none work.
Any idea what I should do at this point? Everything fails the only thing I can do is flash 4.1.2 and 4.3 reliable.
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Galaxy S4 way works on MJ(
TonikJDK said:
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Click to expand...
Click to collapse
Not true -- but it took me HOURS to find it:
http://forum.xda-developers.com/showthread.php?t=2565758
give the guy a thanks, huh?
TX_Jax said:
Not true -- but it took me HOURS to find it:
http://forum.xda-developers.com/showthread.php?t=2565758
give the guy a thanks, huh?
Click to expand...
Click to collapse
I must be missing it. I see that it roots, but I don't see where it unlocks a VZW bootloader.
TonikJDK said:
I must be missing it. I see that it roots, but I don't see where it unlocks a VZW bootloader.
Click to expand...
Click to collapse
That's correct -- so you are looking to unlock the phone? Have you tried the fee-for-service sites?
There is no unlock method on any 4.3 Samsung device that I'm aware of.
TonikJDK said:
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Click to expand...
Click to collapse
But right now I'm on 4.1.2, I flashed back to that. that's where i've been trying to find a way to get to the next step.
mavermc said:
But right now I'm on 4.1.2, I flashed back to that. that's where i've been trying to find a way to get to the next step.
Click to expand...
Click to collapse
You are unable to flash a recovery because your bootloader is locked, from when you flashed 4.3. That was game over. How you got part way back to 4.1.2 I don't know, but be careful. I would flash back to 4.3, root it and hope someone unlocks the bootloader for 4.3
TonikJDK said:
You are unable to flash a recovery because your bootloader is locked, from when you flashed 4.3. That was game over. How you got part way back to 4.1.2 I don't know, but be careful. I would flash back to 4.3, root it and hope someone unlocks the bootloader for 4.3
Click to expand...
Click to collapse
Well that really sucks, with this soft root, any chance I could atleast get back my NFC on while screen off?
u can. look for the exposed installer, I seen it on here somewhere. theres a option for nfc on with screen off on it. I'll try to remember where I seen it and post for ya.
mike7728 said:
u can. look for the exposed installer, I seen it on here somewhere. theres a option for nfc on with screen off on it. I'll try to remember where I seen it and post for ya.
Click to expand...
Click to collapse
I use the Wanam Xposed module for NFC with the screen off.
jcollier said:
I use the Wanam Xposed module for NFC with the screen off.
Click to expand...
Click to collapse
I got Xposed working so I'll be checking this out, thanks!
Any idea how to get the features from the other roms in this? like smart scrolling with your eyes and the other features that the [ROM] N3BULA [MJ9] has snuck in from the note 3?
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