Previously, I asked something similar when the JSS15R was released. I was told that when OTA is installed, it overwrites the custom recovery with the stock one and that we can flash the custom recovery later. But why does everybody seems to be going back to stock version.
Also, if I go back to stock recovery will the root work?
littleromeo said:
Previously, I asked something similar when the JSS15R was released. I was told that when OTA is installed, it overwrites the custom recovery with the stock one and that we can flash the custom recovery later. But why does everybody seems to be going back to stock version.
Also, if I go back to stock recovery will the root work?
Click to expand...
Click to collapse
Flashing back to stock recovery will insure a successful installation. Usually if you're on a custom recovery it'll go through the process of installing then fail towards the end. You can always flash back to custom recovery after you confirm the installation has gone through.
littleromeo said:
Previously, I asked something similar when the JSS15R was released. I was told that when OTA is installed, it overwrites the custom recovery with the stock one and that we can flash the custom recovery later. But why does everybody seems to be going back to stock version.
Also, if I go back to stock recovery will the root work?
Click to expand...
Click to collapse
Traditionally stock recovery is what OTAs work with and what the manufacturer tests with so you are assured everything will work.
That being said, on a platform by platform basis, it is possible the custom recoveries will flash the OTAs fine.
From past OTA updates, people have found custom recovery successfully flashes the OTA for the Nexus 7 2013.
You can flash back to stock or use TWRP/CWM. Either will work (I've tested on WiFi/Flo but I believe folks on LTE/Deb have said the same)
Thanks. flashed the ota with latest twrp along with super su. Everything works fine.
Related
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Monoclypsus said:
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Click to expand...
Click to collapse
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
ok
topherk said:
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
Click to expand...
Click to collapse
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Monoclypsus said:
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Click to expand...
Click to collapse
Yeah, that same method should work. I personally like the custom recoveries, but understand your desires to leave it at stock recovery (not triggering the flash counter).
Like I mentioned before, Samsung hasn't (and most likely won't) locked their bootloaders, so any rooting method that has worked in the past should work in the future. Just make sure to read the last 3-4 pages of the thread for whatever method you're trying to use to see if there are any issues. I know an earlier version of mskip's toolkit was having issues with JB for a little bit (it's updated now).
Well I'm gonna give it a shot. Ill let you know how it turns out.
Sent from my SPH-L710 using xda app-developers app
Just went with cf autoroot. Worked fine.
Sent from my SPH-L710 using xda app-developers app
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
jkj said:
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
Click to expand...
Click to collapse
I replied to your thread. I hope it works for what you need.
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.
I rooted my dad's phone a while back ago so he can use tethering in case of emergencies etc. He recently got a smart watch and I wanted to updated it so that he can use it. But it has not been touched since that day. I essentially want rooted stock rom, I'm unaware of where to find that the closest I can find is StockMod kitkat. Which seems to not work on ATT phones? I just want to make sure that I don't brick his only phone on christmas. So is there something I should be aware of?
His model is SGH-i747
Baseband
i747UCDLK3
Build number
jro03
So how do I go about upgrading it? Can I just flash TWRP and flash any rom using TWRP?
I found this, so I should install new TWRP, then flash a specified kernel then flash rom? would this be safe route?
Some of the latest ROMs require a 4.4.2 bootloader and modem.
The simplest and safest way to get the latest bootloader may be to flash back to unrooted stock 4.1.1 and run OTA updates until the phone is running the latest KK ROM. You can then flash TWRP or CWM and a custom ROM.
audit13 said:
Some of the latest ROMs require a 4.4.2 bootloader and modem.
The simplest and safest way to get the latest bootloader may be to flash back to unrooted stock 4.1.1 and run OTA updates until the phone is running the latest KK ROM. You can then flash TWRP or CWM and a custom ROM.
Click to expand...
Click to collapse
Would this require flashing with ODIN? I just want it so that it works with root is not required anymore.
Yes, you would flash the 4.1.1 stock ATT ROM via Odin. I prefer Odin 3.07.
You cannot install OTA updates with root.
You can try flashing just the bootloader and modem but I prefer the long slow route of OTA updates.
I rather do it this way, manually so my dad can enjoy it today. I was wondering how can I update it's TWRP? it's at 2.3 but the TWRP manager keeps crashing when I update it.
I highly recommend the latest d2lte version of Philz Touch for recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Ok I ****ed up, flash that kernel and did whatever and bam ****ed up. Not working... ****, I still ahve download mode and Recovery but it will not boot into the OS. I get a flash of samsung and then nothing else happends...****
I decided to flash stock DLK3 in odin. Then let the updates take it course (my dad doesn't need root) Where Can I find the file?
The stock ATT firmware is on sammobile.com.
If you want root, OTA to the latest 4.4.2, install Philz, flash supersu via recovery.
This is a public service announcement to save people headaches. RTFM. You cannot ever now, or in the past, take an OTA with a custom recovery. You must always have a stock recovery and system to do so. Period. If you do install a custom recovery, freeze the update center with Titanium, Rom Toolbox, or the like, so that you will remember you have a custom recovery and not accidentally take an update.
I hope this helps someone out there
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Grizzie said:
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Click to expand...
Click to collapse
.this is referring to stock software updates, unless it's updates of the rom, which you won't even receive if you're on a custom rom...to update a custom rom, you just download the updated version, or the OTA if the rom is so capable, and flash it in twrp like the first version you downloaded
Grizzie said:
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Click to expand...
Click to collapse
Wait for a flashable zip for TWRP. You can revert to stock to take an OTA. Being rooted is not a problem per se, it's the custom recovery and having non stock roms. In theory you could flash the stock recovery and bootloader and then take an OTA. However, not having stock system/apps could likely create havoc
In case you do happen to try and install it, here's a fix for your bootloops: http://forum.xda-developers.com/showthread.php?p=60117595
my m9 has received an android 6 update massage. but after installing, the phone restarts in custom recovery.
please help me how to upgrade my rooted m9 to an official marshmallow. i do not want to upgrade to a custom ROM
excuse me, my English is so weak
How did you upgrade to Marshmallow with a custom recovery as that isn't possible...
Tell us what you have flashed...g
sjmahmoudi. persiangig . com / image / d .jpg
i could not upgrade to marshmallow. i received an OTA upgrade message. i download first part and then a installing confirmation widows appeared and when i confirmed it the phone restarted and boot on custom recovery.
since i am xda new user i can not ad links to my posts. a link to a screenshot of my phone is above this post. i add some SPACES to it so i can post it
In order to upgrade to official MM....you need a stock recovery image...and a stock system image...
Search for...and flash your stock recovery....if that is the only thing you have changed....g
gregsarg said:
In order to upgrade to official MM....you need a stock recovery image...and a stock system image...
Search for...and flash your stock recovery....if that is the only thing you have changed....g
Click to expand...
Click to collapse
thank you.
i just want to upgrade to android 6.
i know that i can flash custom roms with custom recovery. is it possible for me to download an stock system image and flash it with custom recovery the same way? i do not want to make everything back to its original. i want a rooted android 6 with custom recovery.
-----------------
i had some search. if i upgrade to stock android, then i will have to root my phone again and for that i have to flash a custom recover again. i searched and find out that android revolution custom ROM is a good choice for ones how wants to keep HTC Sense.
thank you for your support.
Check here for possible stock system images and recoveries...
You should be able to flash a stock system backup from this thread...to include recovery....then take your OTA....and flash TWRP afterwards....
Just make sure everything matches your carrier....cid/mid....so the outcome is favorable...g
http://forum.xda-developers.com/showthread.php?t=3132698
You'll quickly find, if you haven't already, that the latest Android Revolution HD (v20) requires you to have the latest firmware. Flashing it without it will throw your phone into a boot loop.
gregsarg said:
In order to upgrade to official MM....you need a stock recovery image...and a stock system image...
Search for...and flash your stock recovery....if that is the only thing you have changed....g
Click to expand...
Click to collapse
If he has removed his carrier's bloatware as well as the custom recovery, would he have to flash the system image also?
Or just flash the recovery?
I am asking as many AT&T users often root to remove AT&T bloatware, like I did. I used HTCDev.com to root, and my bootloader is unlocked.
Soundwve said:
If he has removed his carrier's bloatware as well as the custom recovery, would he have to flash the system image also?
Or just flash the recovery?
I am asking as many AT&T users often root to remove AT&T bloatware, like I did. I used HTCDev.com to root, and my bootloader is unlocked.
Click to expand...
Click to collapse
Flashing a stock RUU will guarantee that the system and recovery are completely stock...
The OTA scans the device prior to update and will detect any software that isn't signed or official...
I'd RUU back to stock...then OTA will prompt....and won't get stuck trying to update the system partition...g