I updated my Note to JB 4.1.2 using KIES. After that I installed TWTR 2.5, and rooted my NOTE. Now I want to go back to stock Recovery, so I can reveive any future OTA updates, but I cannot find the flashable .ZIP anywhere. Does anyone know if it even exits? I googled and searched the forums everywhere but I can only find the Gingerbread recovery. If anyone knows where can I find the stock recovery for JB let me know.
Thank you
:good:
Just go back to kies and select firmware update again. It will unroot and reinstall 4.1.2. The only thing it won't do is clear your flash counter. But you'll be stock with the stock recovery again.
Just Stock Recovery
440bro said:
Just go back to kies and select firmware update again. It will unroot and reinstall 4.1.2. The only thing it won't do is clear your flash counter. But you'll be stock with the stock recovery again.
Click to expand...
Click to collapse
I was looking to just getting back the stock recovery without having to flash the whole ROM again. I have reinstalled the stock ROM before using ODIN, and that get's rid of the flash counter. What Im looking is for a way to:
a) install STOCK ROM
b) install CWR or TWTR, and install Root zip
c) reinstall the stock Recovery (I believe 3e) and keep root.
d) be able to install OTA update if it comes.
I dont want to have to install STOCK ROM whenever a OTA update comes out. Or maybe im mistaken, and reinstalling stock recovery breaks root?
Anyone knows if it's possible?
I don't think I we'll even see another update. Note is reaching EOL.
Even with stock recovery... the update will most likely fail because you're rooted.
recovery doesn't have anything to do with root either. Root is only for when booted into the os.
Instead of going to stock with Odin to get the update... how about just going to samfirmare.com and getting the Odin package of whatever update may come and just installing that with Odin?
That's your best bet. Tbh
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
btswein said:
I don't think I we'll even see another update. Note is reaching EOL.
Click to expand...
Click to collapse
Just because it won't be to 4.2.2 doesn't necessarily mean no more updates...
Could be a newer build of 4.1.2. ...
Sounds fair
studacris said:
Even with stock recovery... the update will most likely fail because you're rooted.
recovery doesn't have anything to do with root either. Root is only for when booted into the os.
Instead of going to stock with Odin to get the update... how about just going to samfirmare.com and getting the Odin package of whatever update may come and just installing that with Odin?
That's your best bet. Tbh
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Just because it won't be to 4.2.2 doesn't necessarily mean no more updates...
Could be a newer build of 4.1.2. ...
Click to expand...
Click to collapse
With my wife, brother, and sister-in-law's Note 2's, were rooted with CF-Auto-Root, kept stock recovery, and were able to install the OTA update successfully. That's 3 Notes, so it's not a fluke, or a one-off. They lost root, but was easy to root again using CF-Auto-Root to get it back.
So I suspect that having the stock recovery can enable me to install a OTA update, if one comes to the NOTE 1. I love to keep it as simple as possible. I don't have any trouble getting the Odin update package, but that requires one extra step. Im just being curious why nobody has the flashable stock recovery.
Related
I followed this thread to root: http://forum.xda-developers.com/showthread.php?t=2024207
I think I used the Root66 stock VRALJB I don't remember. My phone model number says SCH-I605, the Android version is 4.1.1, Baseband is I605VRALL4, Build number is JRO03C.I605VRALJB. I don't know if the kernel number is necessary because it's really long to type out, but if you need it I will post it.
Then I unlocked the Bootloader using AdamOutler's thread and now I have a custom TW recovery thing.
When I try to do the update in the Settings, it reboots to the TW recovery and doesn't do anything. When I select to turn on the phone with the TW recovery, it says the update failed. Someone told me that I shouldn't do that update because it's something called OTA and it's bad for my rooted phone, but then how do I know when I need an update? Do I have to check this forum every day for announcements? Which thread will the updates be in?
Thank you
The update option in settings is for Verizon OTA updates. OTA stands for over-the-air. The updates are sent to your phone using the Verizon data network. After the update is loaded onto your phone, it reboots into stock recovery to install the update. Since you have a custom recovery, (TWRP, I believe), the update will always fail. I see that you have the latest baseband, which is really the only reason for taking the OTA update to begin with.
Now that you have a custom recovery, you can flash any of the wonderful 4.1 ROMs that we have at our disposal. I'm currently on Jedi X11 and I recommend that, but there are more to choose from. One word of caution: if you decide to flash a 4.2 ROM, then you can't go back to a 4.1 ROM unless you flash the sd card downgrade .zip file. This is because 4.2 will change your directories around. I will try to link to a thread with the downgrade zip in it on another post.
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
Here is the link to that thread. The downgrade .zip is in the third post
http://forum.xda-developers.com/showthread.php?t=2129787
I haven't installed a ROM because I want to keep all the stock stuff, but if there is a ROM that keeps all the stock but somehow increases speed, then I'd install it but I don't know of any that don't not have some stock stuff removed.
The annoying thing is that the phone keeps telling me to update every 3 days and I don't like it. Is there a way I can stop this without doing anything bad to the phone?
While it's true that all ROMs are not 100% stock, you have to ask yourself what you really want to keep. The ROM I'm running is Touchwiz-based, which means it has all the S-Pen apps along with true multi-window functionality. The stuff that I left coming from pure stock was mostly bloatware.
Either way, if staying on pure stock is all that you want and you want to stop receiving the OTA update notices, then you need to use an app that can freeze other apps. Freezing means that the app is disabled, will no longer appear in your app drawer, and will not start up when you boot the phone. I use Titanium Backup to freeze apps. I recommend freezing apps over outright deleting them because you may inadvertently soft brick your phone that way.
Once you have Titanium Backup or another app with the same functionality, then you need to find and freeze SDM 1.0. It was mentioned in this post here:
http://forum.xda-developers.com/showthread.php?t=2177551
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
I will add that I am not sure why you would unlock your bootloader if you didn't intend to flash any ROMs. The act of unlocking the bootloader is what took away your stock recovery and causes your OTA updates to fail when the installation process starts. You may want to research how to get your phone back to 100% stock if you want to be able to take updates in the future.
Hello All. I had installed SHOStock 3.0.1. Then I somehow thought that I will back ROM and that reminds me of ROM Manager which I installed ages back . Clicked on backup which restarted the phone and then phone didnt start ever. So I put back Stock Gingerbread UCKH7. But now after that when I am trying to update using AT&T software update, it is giving me error that software cannot be installed due to interrupation. When I try to install from Kies, office laptop does not recongnize my phone. Home laptop do recongnize the phone but gives message that this version of Android is not supported to upgrade by Kies. I dont know how shall I proceed. When I try to install stock ICS downlaoded from some XDA thread using ODIN, it is not doing anything. Tried to use Exynos Abuse to root but not working. Any other tool to root? Is it ok to directly install some Jelly Bean ROM after root on Gingerbread or shall I go for ICS first then JB? PS: Tried to read thr' all stickies and Q & A but could not find proper answer. Thanks in Advance.
I hope you didn't do any permanent damage by using rom manager. If you did all the reading you mentioned, you probably saw, after the fact, the sticky thread warning not to use rom manager.
First, you can not do an over the air update any longer; the only way to update officially is via kies. Not sure what is blocking kies, but you might try entering 3e recovery and performing a wipe data/factory reset, then see if kies will install the update. You do have to be bone stock for kies to work, I think. Rooted may be ok. Not sure exactly what elements causes kies to fail.
I mention the possibility of damage because you say:
When I try to install stock ICS downlaoded from some XDA thread using ODIN, it is not doing anything.
Click to expand...
Click to collapse
You should be able to flash any of the stock firmware via Odin.
If you want to go the custom firmware route, you can install a custom kernel, then use ClockworkMod Recovery to install your custom firmware. You should be able to do this from any version, Gingerbread, ICS or JB.
You can root by flashing one of the stock plus root packages. Exynos Abuse only worked with 4.0.3 I think. The exploit was patched. People have been using Framaroot to root stock 4.1.2, and I believe someone mentioned using it successfully on ICS as well. Results posted here have been mixed but generally successful.
There are several resources in the Download Repository. See the link in my signature.
Will try tonight
creepyncrawly said:
I hope you didn't do any permanent damage by using rom manager. If you did all the reading you mentioned, you probably saw, after the fact, the sticky thread warning not to use rom manager.
First, you can not do an over the air update any longer; the only way to update officially is via kies. Not sure what is blocking kies, but you might try entering 3e recovery and performing a wipe data/factory reset, then see if kies will install the update. You do have to be bone stock for kies to work, I think. Rooted may be ok. Not sure exactly what elements causes kies to fail.
I mention the possibility of damage because you say:
You should be able to flash any of the stock firmware via Odin.
If you want to go the custom firmware route, you can install a custom kernel, then use ClockworkMod Recovery to install your custom firmware. You should be able to do this from any version, Gingerbread, ICS or JB.
You can root by flashing one of the stock plus root packages. Exynos Abuse only worked with 4.0.3 I think. The exploit was patched. People have been using Framaroot to root stock 4.1.2, and I believe someone mentioned using it successfully on ICS as well. Results posted here have been mixed but generally successful.
There are several resources in the Download Repository. See the link in my signature.
Click to expand...
Click to collapse
Thanks. I will try tonight at home.
Try this to root if not already.. Framaroot.apk
http://forum.xda-developers.com/showthread.php?t=2130276
Sent from my SGH-I777 using xda app-developers app
It worked
creepyncrawly said:
I hope you didn't do any permanent damage by using rom manager. If you did all the reading you mentioned, you probably saw, after the fact, the sticky thread warning not to use rom manager.
First, you can not do an over the air update any longer; the only way to update officially is via kies. Not sure what is blocking kies, but you might try entering 3e recovery and performing a wipe data/factory reset, then see if kies will install the update. You do have to be bone stock for kies to work, I think. Rooted may be ok. Not sure exactly what elements causes kies to fail.
I mention the possibility of damage because you say:
You should be able to flash any of the stock firmware via Odin.
If you want to go the custom firmware route, you can install a custom kernel, then use ClockworkMod Recovery to install your custom firmware. You should be able to do this from any version, Gingerbread, ICS or JB.
You can root by flashing one of the stock plus root packages. Exynos Abuse only worked with 4.0.3 I think. The exploit was patched. People have been using Framaroot to root stock 4.1.2, and I believe someone mentioned using it successfully on ICS as well. Results posted here have been mixed but generally successful.
There are several resources in the Download Repository. See the link in my signature.
Click to expand...
Click to collapse
It worked.
I used your root to official ICS. Then I rooted Exynos to root. Thank you. Do I still need to have CWM after this? I am planning to install Helly Bean please let me know.,
guru1212 said:
It worked.
I used your root to official ICS. Then I rooted Exynos to root. Thank you. Do I still need to have CWM after this? I am planning to install Helly Bean please let me know.,
Click to expand...
Click to collapse
Assuming that Helly Bean uses a CWM flashable zip file, as almost all rom's do, then you will need to install a custom kernel containing a CWM recovery. You can not flash rom's from stock recovery or Odin.
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I would try using the me7 factory image that wipes everything and then try the upgrade.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
reinaldistic said:
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
Click to expand...
Click to collapse
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
[/COLOR]
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
reinaldistic said:
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
Click to expand...
Click to collapse
There is no link or post on it really. Its a patched recovery and boot image so when you odin back to a factory image they get replaced with the non patched versions
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I to am having same exact problem but im on me7 and was safstrapped????????
The advice from @hexitnow worked! I downloaded ME7 image here http://forum.xda-developers.com/showthread.php?t=2357235
It worked fine then I took the latest OTA. Thanks guys!:good:
Quick Qestion
I have a quick question, and i dont want to make a who new thread about it. But since we already talkin about it on here, is it worth it to do this Verizon update?? I just did a Verizon update 2 days ago. And now to me i think it just aggitated me. My Email are different now. My delete button moved and it added more buttons. And my task manager seems a lil different. Cant seem to put my finger on it.. But its weird. What else has changed? Was it even worth doing an update?
Okay, I've been working on this all night and most of the morning. I upgraded my Sprint Note 3 via OTA to Lollipop (5.0). I attempted to root and my phone booted up and all of my apps stopped working--including System UI. I ended up just factory resetting. Somehow though, the root was successful.
Now I'm trying to install Clockwork Recovery so that I can Nandroid backup and install Xposed Framework. I'm having the hardest time find stuff for my phone. Is it that old that no one is updating stuff for the Note 3? Anywhoo, can anyone tell me the proper way to flash CW Recovery? I've tried all kinds of sources, but nothing is clearly indicated for my phone. I've even tried the ROM Manager and that soft bricked my phone.
Use TWRP 2.6.1. You will have better success.
jdoggz said:
Okay, I've been working on this all night and most of the morning. I upgraded my Sprint Note 3 via OTA to Lollipop (5.0). I attempted to root and my phone booted up and all of my apps stopped working--including System UI. I ended up just factory resetting. Somehow though, the root was successful.
Now I'm trying to install Clockwork Recovery so that I can Nandroid backup and install Xposed Framework. I'm having the hardest time find stuff for my phone. Is it that old that no one is updating stuff for the Note 3? Anywhoo, can anyone tell me the proper way to flash CW Recovery? I've tried all kinds of sources, but nothing is clearly indicated for my phone. I've even tried the ROM Manager and that soft bricked my phone.
Click to expand...
Click to collapse
I have to wipe cache every time I go into twrp 2.8.1.0. Or I get the ui errors if it gets past the Sprint screen.
I was on an older version but the backup won't restore.
use Chainfire's method,twrp 2.8.6.1 and SU 2.46
ttkyles said:
use Chainfire's method,twrp 2.8.6.1 and SU 2.46
Click to expand...
Click to collapse
Which of Chainfire's method? Those were the ones I tried. I don't see anything on his site for SM-N900P with Lollipop.
You can find philz cwm touch that you can flashbwith odin. If your upgrading to lollipop xposed isnt supported right now. If you cant find the files let me known I keep them backed up and can upload to Dropbox.
---------- Post added at 06:44 AM ---------- Previous post was at 06:43 AM ----------
By the way cf-auto root works great. You flash it in odin as well
the NH7 tar on chainfires site works on OC5
Thanks all...I ended up flashing TWRP via flashify.
I thought I saw somewhere that xposed beta version was working for 5.0.
I rooted my Kyocera with Kingroot, worked well. Wasn't to keen on some of the files it was adding and found I couldn't unroot with Kingroot built in feature. So I then found I could use SuperSu-Me to rid myself of Kingroot and purchased. It removed Kingroot and I am still unable to uninstall root so that I can upgrade to lollipop. All I get is software update failed. Any suggestions. I even did a factory reset and phone is still rooted. I have not tried any install and custom roms.
Did you ever fix this?
OTA uptate to lolipop bricked my phone... I was able to find a Rooted 5.1 rom to rescue it. But like you, I cannot remove root and all future update attempts keep failing...
Did you try to flash a stock 5.1 rom on your rooted 5.1 rom? That should allow to get back to normal upgrade (back in time, it usually worked, still I am not aware of latest android pains regarding that matter)
Harsher said:
Did you try to flash a stock 5.1 rom on your rooted 5.1 rom? That should allow to get back to normal upgrade (back in time, it usually worked, still I am not aware of latest android pains regarding that matter)
Click to expand...
Click to collapse
I was not able to find an unrooted Verizon factory ROM for my Brigadier.
ghj018 said:
I was not able to find an unrooted Verizon factory ROM for my Brigadier.
Click to expand...
Click to collapse
I am not sure you need it to be verizon to just be able to leap to "future" android version, unless this version is only available via kies from your PSP/carrier.
flashing any stock rom might work. Alternative would be to find an unrooted kernel for your android version of a rooted but else stock ROM (as some people do as they like TW experience but with the added benefits of root). But they are just guesses, I wish someone with more technical know-how would join, I just talk from past experiences, not from current ones, so it might have changed.
Harsher said:
Did you try to flash a stock 5.1 rom on your rooted 5.1 rom? That should allow to get back to normal upgrade (back in time, it usually worked, still I am not aware of latest android pains regarding that matter)
Click to expand...
Click to collapse
this phone may have been carrier specific to Verizon...
I did find some custom roms for marshmallow and nougat. But that's totally new territory for me to learn how to put those ones on and of course no updates. 5.1 is as far as the Brigadier went officially. This was not a common phone so it's support and information for it is scarce
---------- Post added at 08:48 PM ---------- Previous post was at 08:21 PM ----------
This is the update it keeps asking me to install , and it keeps failing . I suppose if anybody had a fully updated ROM for the Brigadier that would be useful solution...
https://www.verizonwireless.com/support/kyocera-brigadier-update/
Do you have xposed installed? Sometimes that can cause problems.
I do not, I am going to attempt to put TWRP on and then flash the Super SU Binary so that I can run FlashFire.
Lots a learning lol
Locked bootloader. You can run TWRP from adb but you cannot permanently flash it to the device.
I rooted with Kingroot and updated my phone. It was on 4.4.2 1.102vz. My phone boots up but screen goes blank after the Kyocera screen. I powers it off one time but it was luck. I can boot it into stock recovery. I would like to flash the 5.1 ROM to it and beagle to use it. I do not know how to flash a ROM to the phone since it does not have fast boot. Can anyone assist me? The phone was new and never used too. Was going to be a great phone for me at work. I have rooted before and took a ota and I only risked loosing root. But that was with Droid phones. That is where I have more experience in.