Related
Hey all,
For the past month or so, I've been having an issue with my Bad Boyz Sprint ONE KitKat v1.2 rom, where it manually restarts continuously for no reason apparent to me. I've wiped and reflashed twice, but the manual restarting continues. I've tried installing the Bad Boyz ONE Sense 6 v1.0 to replace the kit kat version but it continually fails in TWRP. People suggested on the main thread that flashing the newest firmware could help, but the guides I've found to flash new firmware require S-OFF, which I do not have. So my two questions are
A) is the KitKat v1.2 manual restart loop a known problem there is a solution for?
or B) Is there a way to flash the newest firmware for the phone with S-On, and if so, how do I do it?
Any help would be greatly appreciated. And I can reply to this thread with additional details as needed. Thanks.
-Lettuceface
LettuceFace said:
Hey all,
For the past month or so, I've been having an issue with my Bad Boyz Sprint ONE KitKat v1.2 rom, where it manually restarts continuously for no reason apparent to me. I've wiped and reflashed twice, but the manual restarting continues. I've tried installing the Bad Boyz ONE Sense 6 v1.0 to replace the kit kat version but it continually fails in TWRP. People suggested on the main thread that flashing the newest firmware could help, but the guides I've found to flash new firmware require S-OFF, which I do not have. So my two questions are
A) is the KitKat v1.2 manual restart loop a known problem there is a solution for?
or B) Is there a way to flash the newest firmware for the phone with S-On, and if so, how do I do it?
Any help would be greatly appreciated. And I can reply to this thread with additional details as needed. Thanks.
-Lettuceface
Click to expand...
Click to collapse
Update SuperSU, should fix it. Here is the link: http://download.chainfire.eu/supersu
Download that zip, and flash it in recovery.
StormyNight said:
Update SuperSU, should fix it. Here is the link: http://download.chainfire.eu/supersu
Download that zip, and flash it in recovery.
Click to expand...
Click to collapse
Thank you, sir. I was able to update it after getting the most recent TWRP and then I was able to get the Sense 6.0 which I'm using right now. SOOO NICE!
-Curtis
LettuceFace said:
" ... it continually fails in TWRP ..."
Click to expand...
Click to collapse
Go get the TWRP here -- you'll likely be a happier with performance, off-line charging notifications, etc.
If you wonder how it came about that we have an enhanced TWRP, look here.
:good:
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
ponso said:
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
Click to expand...
Click to collapse
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Thank you. I went with the 2nd option and my phone is running great with the update.
Although it took awhile to reconfigure everything back.
mjones73 said:
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Click to expand...
Click to collapse
I have been rooting, unlocking, and loading Roms on other devices for awhile now, but I'm not familiar with how to manage stock updates. I can't seem to find anything, (so maybe this info could be added to a sticky).
I'm rooted with TWRP and a zipped OTA has been posted in anothet thread for my device, XT1064. What can I do to load it? Do I need to flash back to stock first? Can I simply run a fastboot command? I feel like I should know this by now but I'm a bit confused by all the different sources of information.
Thanks, all, for your help.
I have the same question. If someone who has done this, is out there, please let us know.
you tried asked in that other thread???
If is the OTA update do not use it!!!
If you received the OTA on your phone do not update!!!
you will brick your phone.
To install OTA revert back to stock with the factory image. You will go back to Stock Kernel and recovery.
Or wait til someone builds a stock updated ROM and flash that.
If is a image of the ROM, not the OTA, a already updated ROM just follow the instructions on the thread...
Yes, I did ask in the other thread, but I thought it would be better to post a new Q&A thread to keep from cluttering up the other one. Thanks for your help. I'll just wait for a flashable ROM..
Try this method:
http://forum.xda-developers.com/moto-g-2014/help/guide-update-to-lollipop-losing-apps-t2979971
The main idea with OTA is the incremental nature of the update. To keep OTA filesize to a minimum, the system will be patched, not completely overwritten.
So, if you have altered your system in any way, OTA will fail, because it tries to patch files that differ from what it expects. The OTA will check which device it is executed on and will perform various checksum tests before actually installing itself.
If you are experienced with flashing and know how to modify the update-script inside the OTA.zip, then you can go from XT1068-4.4 to XT1064-5.0.1.
But it is quite a lengthy process and not easy nor recommended
You have to go from XT1068-4.4 to XT1064-4.4 to 5.0 to 5.0.1 and must restore the modem. Last but not least the build.prob has to be modified to reflect dual-sim capability.
By the way, the need to lock the bootloader for OTA is a myth. It is not necessary.
Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,
No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ
Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.
torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Maybe Oxygen Updater has full download link?
BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.
Did you flash stock recovery to both slots the last time?
g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?
BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.