I did a quick battery pull and now whenever I turn the phone on, it keeps trying to update. SOOOO, is there a way to stop this or take it off through PC with ODIN????
I'm not ready to lose root yet....
Anybody have any ideas? Can I flash a custom rom through ODIN?
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
You sure you didn't brick your device? I was under the impression doing battery pulls during the update process would mess up your phone.
Someone posted something similar yesterday. Another person suggested pulling the sim card out and then rooting the phone as usual.
Edit: you already have root?
Dr. Cornelius asks you to calm down.
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
If the update went through, sorry, you're stuck for now. Here's a link to inform you of the situation.
http://forum.xda-developers.com/showthread.php?t=2359090
Crooke356 said:
Someone posted something similar yesterday. Another person suggested pulling the sim card out and then rooting the phone as usual.
Edit: you already have root?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
Yes, I already have root. The phone is currently next to me with the battery out.
First off, I'm no expert here. I'm hesitant to offer any advise. Are you able to boot directly to recovery?
Dr. Cornelius asks you to calm down.
Phatdawg said:
You sure you didn't brick your device? I was under the impression doing battery pulls during the update process would mess up your phone.
Click to expand...
Click to collapse
Luckily no, but this is very frustrating. It hasn't fully loaded yet. Trying to figure out if there is a to do a factory reset and have go it go back to what it was in the box.
I would've responded sooner but since I'm a new member.... 5 minute interval responses.
Crooke356 said:
First off, I'm no expert here. I'm hesitant to offer any advise. Are you able to boot directly to recovery?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
I tried that. It keeps trying to do that damn update.
I've never taken an OTA on a Samsung device. In my experience there is a prompt that verifies you want to install after the download. IF it's the same here, I would THINK your safe to Odin.
If you can get to recovery, throw a ROM on your SD card and flash.
Edit: oh new member
Dr. Cornelius asks you to calm down.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
By "loading" do you mean downloading? Or is actually installing?
Dr. Cornelius asks you to calm down.
you have to poke a accept after it downloads
then it boots to download mode
if you like
you can revert stock to MDK wipes everything
http://www.sxtpdevelopers.com/showthread.php?t=237
flash to complete stock and re-root ??
Not sure how far out of the way you would like to go..
I downloaded the OTA and let it site on the stock MDK phone for over a day before I rooted and installed ota root keeper to test to see if I can restore root..with out bricking
I could of easily delete the fota cache where it downloaded to and frozen the propitiate file to stop the update
Crooke356 said:
I've never taken an OTA on a Samsung device. In my experience there is a prompt that verifies you want to install after the download. IF it's the same here, I would THINK your safe to Odin.
If you can get to recovery, throw a ROM on your SD card and flash.
Edit: oh new member
Dr. Cornelius asks you to calm down.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
By "loading" do you mean downloading? Or is actually installing?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
Its actually installing. Can't get into recovery.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
no custom roms thru odin.
---------- Post added at 07:35 AM ---------- Previous post was at 07:33 AM ----------
get into recovery and just flash a custom rom.
If you have titanium backup, use it to freeze SDM 1.0 and FWUpdate. This will keep the new software from downloading and keep the software update notification from appearing (provided it hasn't been installed by now).
Sent from my SCH-I545 using Tapatalk 4 Beta
best idea has been said, get that thing into custom recovery where the OTA cant install. try beating the phone as it tries to install and get it into download mode and see if u can flash a custom recovery though ODIN
What you can do at this point depends a lot on what has already been updated on your phone.
If the bootloader is already updated, then there's no way for you to load the older kernel onto it to get it ready to root.
What I'd suggest you do is to go ahead at try the rooting process.
Boot the phone into download mode and try to push the MD2 kernel onto it,
If the install tries to restart, it'll fail since you don't have the expected software, which hopefully will give you a usable system.
Then use motochopper to try to get "su" access.
If ODIN refuses to flash the MD2 software, it's probably the case that you've already gone past the point of no return (i.e. you've got the updated, locked bootloader) and you might as well let the update finish.
If you succeed, then install MDK and Voodoo OTA Keeper and cross your fingers.
Good luck!
Related
Im an impatient idiot. Lol. I flashed a boot.img through Odin but I flashed a euro img accidentally. Now my phone turns on shows the Samsung screen and then turns off or screen goes black. I think I need to refashion the sprint stock firmware and it'll work. I can find it. Anyone have it and could send it to me please? I tried doing a factory reset already to no avail. Please help!
Thanks in advance.
hopefully over the next few days we'll see the tar ball for stock; course you could always head to your nearest sprint store and have them flash it for you.
Questions go in Q&A
Sent from my PantechP4100 using xda premium
same thing happened to me. Just spent over a hour at my local sprint store. My tech told me they dont have any software for the phone yet but they did order me a replacement s3. The tech just tried to hard reset it but it doesnt even boot recovery.
Does this help?
http://forum.xda-developers.com/showthread.php?t=1725395
If you can get into odin, just flash the tar in PDA mode.
I guess Ill give it a shot. I can still access odin. Just not too sure if I should continue to tinker with it since sprint has already agreed to send a replacement
s3xda said:
I guess Ill give it a shot. I can still access odin. Just not too sure if I should continue to tinker with it since sprint has already agreed to send a replacement
Click to expand...
Click to collapse
You see when you flash a wrong image, instead of the phone working better you will get quite the opposite.
lol ur absolutely right. This heatwave is making me stupid
Yea I have talked with Sprint, no one has the stock firmware. What does that link you sent out contain? I cannot access it yet because I am a newbie. I can access Odin and am able to reflash if I have the correct firmware.
Also, sorry for posting this in the wrong place.
channelzer0 said:
Yea I have talked with Sprint, no one has the stock firmware. What does that link you sent out contain? I cannot access it yet because I am a newbie. I can access Odin and am able to reflash if I have the correct firmware.
Also, sorry for posting this in the wrong place.
Click to expand...
Click to collapse
Basically the link is for rooting your phone; there are 2 threads in the development area concerning it.
If someone did a factory reset; then went into recovery and did a backup.
Could that backup be used by someone else; say this poor soul. To use to restore them back to stock?
I'm thinking if channelzer0 could get their phone to CWM they could use that method to get back to a working state; would that work??
I can get into both recovery or Odin. Whether itll work or not....im willing to find out if I can.
jdelano said:
Basically the link is for rooting your phone; there are 2 threads in the development area concerning it.
If someone did a factory reset; then went into recovery and did a backup.
Could that backup be used by someone else; say this poor soul. To use to restore them back to stock?
I'm thinking if channelzer0 could get their phone to CWM they could use that method to get back to a working state; would that work??
Click to expand...
Click to collapse
You should be able to simply flash the recovery and the phone should work.
But yeah, someone will probably post the stock rom by the end of the day.
channelzer0 said:
I can get into both recovery or Odin. Whether itll work or not....im willing to find out if I can.
Click to expand...
Click to collapse
I can't do it now as I'm leaving and wont be back until mid-night; if there isn't something you can odin or flash by tomorrow morning. then I'll root and backup my phone, then reset it and backup again and post that backup for you to try.
patience is truly a virtue...
---------- Post added at 08:18 PM ---------- Previous post was at 08:08 PM ----------
can boot into recovery now but still no dice
s3xda said:
patience is truly a virtue...
---------- Post added at 08:18 PM ---------- Previous post was at 08:08 PM ----------
can boot into recovery now but still no dice
Click to expand...
Click to collapse
download:http://d-h.st/qi8
adb push boot.img /sdcard/boot.img
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p7 bs=4096
Be patience next time
Fantastic, thanks. I would like to try this. Can I make this .img a tar file and load through Odin? I put the .img on an external sd card but CWM cannot see, only the internal memory.
How do I ABD? Sorry Im a newb.
Thanks again for your help.
channelzer0 said:
Fantastic, thanks. I would like to try this. Can I make this .img a tar file and load through Odin? I put the .img on an external sd card but CWM cannot see, only the internal memory.
How do I ABD? Sorry Im a newb.
Thanks again for your help.
Click to expand...
Click to collapse
Wait for your replacement an dont tinker till qbking77 releases a video so you dont break your phone.
*facePalm* to this whole thread....:cyclops:
adb cant find my device...
make sure usb debugging is checked in developer options....and also usb drivers are installed.
I seem to have downloaded a wrong version of a ROM, which apparently wrote mmcblk0p5 and mmcblk0p7 backwards from each other. So now I am unable to boot my device. Talking to some people in #koush on freenode stated that it wrote over my modem.bin with a boot image, which is why I cannot boot. I previously already had a working rom (CM10) and was simply trying another one.
So I am wondering, is thare * ANY * way to fix this bricked phone? I am unable to boot into either normal, recovery, or download mode.
check your PM.
Odin back to stock, it might rewrite your partitions correctly with your modem.
brfield said:
Odin back to stock, it might rewrite your partitions correctly with your modem.
Click to expand...
Click to collapse
I cant get into download mode. but I will try and start odin. I need a stock image though. anyone have a link?
There is a stickied thread in every carrier forum for stock.
crash822 said:
There is a stickied thread in every carrier forum for stock.
Click to expand...
Click to collapse
Got it thanks. Downloading now. I don't think it will work since I cant get into download mode. but im going to try it. Ill let you guys know.
luckysmack said:
Got it thanks. Downloading now. I don't think it will work since I cant get into download mode. but im going to try it. Ill let you guys know.
Click to expand...
Click to collapse
having the phone plugged in, it is not recognized as I figured. Also, I dont see how I would even use odin to install the zip to the device. before it was a tar file and this is a zip. So i dont know if it will work as it does not come up.
luckysmack said:
I seem to have downloaded a wrong version of a ROM, which apparently wrote mmcblk0p5 and mmcblk0p7 backwards from each other. So now I am unable to boot my device. Talking to some people in #koush on freenode stated that it wrote over my modem.bin with a boot image, which is why I cannot boot. I previously already had a working rom (CM10) and was simply trying another one.
So I am wondering, is thare * ANY * way to fix this bricked phone? I am unable to boot into either normal, recovery, or download mode.
Click to expand...
Click to collapse
No, there is nothing you can do but use a JTag service..I know, cause I did the same...I thought i was a billy bad-ass, and start flashing with out READING!! what a fool I was, anyways, And, NO a UsbJig will NOT work, again it will NOT work. Use this service...this company is GOOD.
http://mobiletechvideos.mybigcommerce.com/
---------- Post added at 11:44 AM ---------- Previous post was at 11:38 AM ----------
luckysmack said:
I cant get into download mode. but I will try and start odin. I need a stock image though. anyone have a link?
Click to expand...
Click to collapse
here is a way to check, go into device manager, if there is a device sitting there QHSUSB DLOAD, then you will NOT get flashed from Odin, I tried every program out there, nothing will see the device. JTag service, stop wasting time.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
defnow said:
check your PM.
Click to expand...
Click to collapse
Send me the same info if you don't mind, I would like to try it also, although, I have sent my phone out for repair. Just for the record.
Thanks.
Hey all i accidentally hit the OTA update "OK" button when it popped up on my screen. I've been deferring it for the past few months but my finger slipped and hit the "OK" instead of the "defer" and choosing a date to ask again.
I have a looping "Teamwin" logo and it keeps looping.. Cant seem to do anything. I've taken out the battery and then start it up but it still does the same thing.
Any advice, step by step to get out of this loop?
Thanks!
David
you can not OTA update with a custom recovery...time for a date with Odin.
Historical coodsen
droidstyle said:
you can not OTA update with a custom recovery...time for a date with Odin.
Click to expand...
Click to collapse
Would you care to give me a link to do this with a note 2, droidstyle?
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
Whats the key combo to see if i can boot into recovery and ill try it
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
stealthrt said:
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
Click to expand...
Click to collapse
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
droidstyle said:
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
Click to expand...
Click to collapse
Well i just started flashing in odin.... will update when its done.
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
And doing the volume down+home+power sends me to the same screen (WARNING!!!... custom os.. etc etc)
Any other advice?
stealthrt said:
Any other advice?
Click to expand...
Click to collapse
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
B_I_N_G_E said:
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
Click to expand...
Click to collapse
Yeah it still does the same teamwin loop doing it that way.
What else can i try?
stealthrt said:
Yeah it still does the same teamwin loop doing it that way.
I tried again to flash and it still is at the loop after a restart...
and also...
What else can i try?
Click to expand...
Click to collapse
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
B_I_N_G_E said:
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
Click to expand...
Click to collapse
ive only tried the root66 rom.
stealthrt said:
ive only tried the root66 rom.
Click to expand...
Click to collapse
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
Alright i flashed the bootloader and all seems to be fine. I got 2 tutorials mixed up so i though one was using bootloader as the ROM.
All is good now thanks droidstyle and B_I_N_G_E.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
root66 works on all devices with the current firmware since it does not contain a bootloader, recovery, or wipe data. Sometimes it will cause a bootloop which all that is needed is to wipe data in recovery.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
you need to boot into recovery and wipe data...if you can get into recovery the a full odin package will need to be flashed such as stock VRAMC3. However it looks like you figured it out.
Eh.... things have changed with the S4, well for me. I was able to root and unlock the bootstap on my S3, but from what I've read the bootloader for the S4 is still locked. So I tried to get the SafeStrap working and I can get to the config screen and the logo, but when I try and load a ROM and boot into it, the screen goes black and doesn't load anything.
I tried to go back to the stock ROM, but it won't load that one either. Is there a process to reimage the phone and get it back to stock? I tried to do the Volume Up/Home/Power at the same time, but it takes me to SafeStrap. Under the wipe and Advance Wipe options, there are settings to wipe, is this where it should be done? Any other options like Odin? Used to what I did with my S3. Is there a process to remove SafeStrap and get back to stock to start from scratch?
Thanks for the help!
Found Odin, going to try that and see where that gets me. Anyone experienced the issue with the screen going blank while using SafeStrap by chance?
minigts said:
Eh.... things have changed with the S4, well for me. I was able to root and unlock the bootstap on my S3, but from what I've read the bootloader for the S4 is still locked. So I tried to get the SafeStrap working and I can get to the config screen and the logo, but when I try and load a ROM and boot into it, the screen goes black and doesn't load anything.
I tried to go back to the stock ROM, but it won't load that one either. Is there a process to reimage the phone and get it back to stock? I tried to do the Volume Up/Home/Power at the same time, but it takes me to SafeStrap. Under the wipe and Advance Wipe options, there are settings to wipe, is this where it should be done? Any other options like Odin? Used to what I did with my S3. Is there a process to remove SafeStrap and get back to stock to start from scratch?
Thanks for the help!
Found Odin, going to try that and see where that gets me. Anyone experienced the issue with the screen going blank while using SafeStrap by chance?
Click to expand...
Click to collapse
YAY!! Fixed it. Followed this link, http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Had to get the latest firmware, so not sure what this means for me getting root. But if the bootloader is still locked, I may just hold off on flashing an image or I may try again later.
minigts said:
YAY!! Fixed it. Followed this link, http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Had to get the latest firmware, so not sure what this means for me getting root. But if the bootloader is still locked, I may just hold off on flashing an image or I may try again later.
Click to expand...
Click to collapse
You can still safely root your phone using saferoot, then install SafeStrap. You may have just tried flashing a non SafeStrap compatible ROM the first time.
I wouldn't take the KitKat ota just yet either since root and SafeStrap are not guaranteed.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
Look here... This thread will have all the links you'll need in the op
http://forum.xda-developers.com/showthread.php?t=2606501
Sent from my SCH-I545 using Tapatalk
minigts said:
YAY!! Fixed it. Followed this link, http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Had to get the latest firmware, so not sure what this means for me getting root. But if the bootloader is still locked, I may just hold off on flashing an image or I may try again later.
Click to expand...
Click to collapse
read these threads for starters
http://forum.xda-developers.com/showthread.php?t=2606501
http://forum.xda-developers.com/showthread.php?p=48683964
http://forum.xda-developers.com/showthread.php?t=2579278
Mistertac said:
You can still safely root your phone using saferoot, then install SafeStrap. You may have just tried flashing a non SafeStrap compatible ROM the first time.
I wouldn't take the KitKat ota just yet either since root and SafeStrap are not guaranteed.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
Look here... This thread will have all the links you'll need in the op
http://forum.xda-developers.com/showthread.php?t=2606501
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think the issue is one, I was used to the way I did the S3 and I hadn't done it in a while. I also rooted my phone another way than the first step in the process I found on the forums, so I didn't follow THAT process step for step. I do plan to try it again since the phone is sorta a square one right now, just maybe on a weekend when I don't need it the next day.
Thanks again for replying!
decaturbob said:
read these threads for starters
http://forum.xda-developers.com/showthread.php?t=2606501
http://forum.xda-developers.com/showthread.php?p=48683964
http://forum.xda-developers.com/showthread.php?t=2579278
Click to expand...
Click to collapse
I will definitely read through these links, thank you very much for replying!
Very appreciative for this forum and the knowledge and support within it.
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