I was just wondering if anyone was experiencing stability issues after flashing ML2 and rooting in this manner http://forum.xda-developers.com/showthread.php?t=2690133
Lots of programs 'misfire', they start and "[app name] has stopped: report or cancel" then they start up just fine on the second try.
This almost never happened in 4.2.2 Active-rooted
Related
I'm hoping to get some eyes on this plan I've made for hacking my new Droid so I can avoid bricking it at all costs.
I bricked my old Bionic 2 days ago due a combination of problems with Clockword Recovery Mod and the leaked ICS update, as well as my battery frying for some reason. Thankfully Verizon was none the wiser and they are sending me a new phone and battery in a few days. Although I'm cautious about hacking now, I still plan on rooting the new phone so I can recover my apps and data from the old phone's SD card.
Here are my plans for the new phone. If anyone could tell me if it makes sense or if they see any issues that will arise from following these steps, please let me know:
1. Root new Bionic with Motofail.exe root
2. Restore apps and such with Titanium Backup (restoring individual apps so I don't get any old clockwork garbage or other random stuff)
3. Download Voodoo Root OTA Rootkeeper.
4. Wait for official ICS OTA (don't want to mess around with the leaks anymore) and backup root with voodoo
5. Unroot with voodoo, install ICS and re-root after update (I've read on some posts that Voodoo works with the ICS OTA but I'm not 100% sure)
I'm more concerned with the OTA installing properly than keeping the root after ICS, though while it would be simpler just to not root, I really want to restore the TiBu backup from my old phone.
If anyone sees any flaws with this plan or if you think it sounds like there won't be any problems, please respond! I really don't want to brick a second phone so any help would be invaluable.
No one can say for sure if this will work since no one has the official OTA yet.
That sounds like a plan that may work. Even if OTA Root keeper fails I see a thread with a root method that is working on ICS leaks so it should
[should being the operative word here as stated this is all subjective reasoning from my time and use of Android and many different devices there is NEVER 100% certainty EVEN IF we had access to the OTA and had a method there is no accounting for any errors caused by a multitude of things [download corruption, bad blocks in memory during flash, you missing a step and borking the whole process, etc.] so no one will ever be able to say with 100% certainty that you will not have some rare issue and have a problem even with a tested method [and if someone does try to tell you something is 100% they have not dealt with technology and computers long enough to realize nothing is ever guaranteed even fully certified OTAs have caused bugs not accounted for and been stopped, recalled, or otherwise modified when users try to apply them and have issues ]
Anyways, I did read where you flashed the ICS leak via CWM recovery and everything I have been reading about flashing ICS on a Bionic involves the STOCK recovery and not CWM [most postings even SPECIFICALLY state to NOT USE CWM AND ONLY USE STOCK Recovery [but then again I read a lot] so if I had to trace the issue you had the with the limited information you have provided about your specific experience I would prolly point to that as prolly causing the problem. See the ICS with files thread here and that is again specified as part of procedure [basically format EVERYTHING restore it back to out of the box 902 then using STOCK recoveries to apply .905 then the ICS leak THEN after ICS is running they have a rooting batch file in there as well [so no worries about rooting in .902 and using OTA Rootkeeper to sustain it in .905 and on just get stock .905 unrooted to the phone then flash ICS with stock and root once it is fully completed and drivers and all on computer side are good [dont forget to enable USB Debugging [and in ICS there is an option to allow SU to apps only OR APPS AND ADB and after rooting you may need to enable the ADB side for any super user root checks if checking via ADB] but dunno if that is CM9 only option, but seems to be stock ICS setting in developer [it protects you if you use and leave enabled the ADB over the network function from others who may find your device over a network and getting SU access].
Sorry, I digress, all to say sorry to here you had the issue, but I think you may have missed something in the install process and here's how to address it, and your methodology seems sound in theory, but there is other information already available to augment your procedure and make it easier on you, my bad.
Hope all the info helps....
Here is that thread mentioned above that seems to distill what I have read on numerous boards in to one easy to download pack with instructions that has users replying that they have had great success with it: [Guide} Bionic to ICS w/Files
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Rexxen said:
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Click to expand...
Click to collapse
I'm not sure if this is the right modem, but it could be. Hopefully somebody else will reply with a proper solution.
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Miami_Son said:
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Click to expand...
Click to collapse
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Rexxen said:
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Click to expand...
Click to collapse
Did this work out for you? I'm having the same issue.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
So i ended up doing this:
First i flashed the entire phone (since i couldn't find just the modem)
http://honai-android.blogspot.nl/2014/01/how-to-update-galaxy-s4-active-i9295.html
After that i rooted the phone again
http://androidxda.com/root-samsung-galaxy-s4-active-gt-i9295
And that fixed the issues.
Everything works fine again, and i didn't loose any data in the process.
I have rooted Kit Kat using the original method, and today while on wifi I saw the dreaded Software Update Downloading in my tasks. I quickly disabled my wifi and have had it off all day and it has kept the software update from downloading, since I'm paranoid to lose root. I have two Galaxy S4 Actives, both running the same exact Kit Kat exploit and they both had the same software update come up today. I've tried to disable the OTA but FOTA.apk isn't on the phone when I used a root file explorer to look in the System/App folder.
I can't seem to find anything on this update, it just came up on 7/2/14 around 1:00pm EST.
Is there a way to block OTA's on Kit Kat? I imagine it's different as no method I've found has worked.
I did find an APK to kill KNOX, which was popping up at least a dozen times a day to tell me about the "new security policies".
The phones work great as they are, I love having Kit Kat & Root, and don't want to lose it. Anyone have any ideas or anyone know anything about this update?
SebringTech said:
I have rooted Kit Kat using the original method, and today while on wifi I saw the dreaded Software Update Downloading in my tasks. I quickly disabled my wifi and have had it off all day and it has kept the software update from downloading, since I'm paranoid to lose root. I have two Galaxy S4 Actives, both running the same exact Kit Kat exploit and they both had the same software update come up today. I've tried to disable the OTA but FOTA.apk isn't on the phone when I used a root file explorer to look in the System/App folder.
I can't seem to find anything on this update, it just came up on 7/2/14 around 1:00pm EST.
Is there a way to block OTA's on Kit Kat? I imagine it's different as no method I've found has worked.
I did find an APK to kill KNOX, which was popping up at least a dozen times a day to tell me about the "new security policies".
The phones work great as they are, I love having Kit Kat & Root, and don't want to lose it. Anyone have any ideas or anyone know anything about this update?
Click to expand...
Click to collapse
What firmware are you on? If you're on NC9, then it's probably the NE3 update which fixes the bugs in NC9. You can root NE3 very easily with towelroot. I suggest trying to take the update with one of your phones. Odds are that the update will fail to install anyways because you're rooted.
If you're already on NE3 and receiving an update, then I have no idea what it is. Either way the update will fail to install because you've modified system files, so you have nothing to worry about.
Okay I am on NC9. Would there be a noticeable benefit to go stock, take the NE3 update, then acquire root with towel root? I don't have any problems with my phone but my wife seems to have some issues with hers. Not sure what all the update addressed.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
SebringTech said:
Okay I am on NC9. Would there be a noticeable benefit to go stock, take the NE3 update, then acquire root with towel root? I don't have any problems with my phone but my wife seems to have some issues with hers. Not sure what all the update addressed.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
Unfortunately you can't just unroot and take the update. You have to go all the way back to stock by flashing the ML2 Odin package and then flash the OTA update. Flashing the Odin package will completely wipe the phone so I suggest backing up anything you want to save with Titanium Backup.
As for benefits, the NE3 update will probably fix some of the issues with your wife's phone and put her on the latest version, but functionally it should be the same as NC9. Samsung didn't add any additional features or functionality to the NE3 update, they just fixed all the bugs they created with the NC9 OTA. Rooting is super simple now with towelroot so you shouldn't consider that a deterrent.
If you want to try to fix some bugs then update to NE3, if you're perfectly happy with the way your phone is running now then you're not missing out on anything.
If you ever have questions about firmware and updates again, check the Firmware Thread first. I try to keep that updated as soon as I hear about new firmware.
As stated, 900A on OA1 4.4.4. Toweled. Xposed worked fine alone, then uninstalled the framework to install safestrap. Successfully captured backup (took like an hour or more) then reinstalled framework. After reboot, I can send SMS and call out however I cannot receive either. Once I restored nand backup, incoming issue is resolved. Basically cannot seen to have safestrap and framework installed together. Any insight or ideas is greatly appreciated.
It should be noted that I have been searching for almost 2 weeks to find a resolution to this on my own so please be gentle in that regard.
HELP... the process com.android.phone has stopped. cant get calls!
NateDG01 said:
As stated, 900A on OA1 4.4.4. Toweled. Xposed worked fine alone, then uninstalled the framework to install safestrap. Successfully captured backup (took like an hour or more) then reinstalled framework. After reboot, I can send SMS and call out however I cannot receive either. Once I restored nand backup, incoming issue is resolved. Basically cannot seen to have safestrap and framework installed together. Any insight or ideas is greatly appreciated.
It should be noted that I have been searching for almost 2 weeks to find a resolution to this on my own so please be gentle in that regard.
Click to expand...
Click to collapse
ALSO having similar problem
currently working on Extreme debloat, with towel-root, safestrap, nandroid, xposed, in that order,
"Unfortunately, ."
I see a call coming in, but cant answer it.
android 4.4.2 base NCE
kernel 3.4.0.964333 fri mar 14 13:17 2014
build Extreme debloat v2.3 KST 2014
help,
Now I have a nice, rooted, fast booting (10 seconds after safestrap--awesome!) phone that wont take calls.. heh...
cheers, and looking forward for more help...
***** Additional dumb question *****
Which is the later release NCE or OA1?
is OA1 just KK4.4.4?
are there other reasons/fixes? and HERE is the dumbest part, that I swear I should know after mucking with this piece of S*it locked phone for two weeks now...
now that I am on NCE, if I wanted to go to OA1, do I just load that via safestrap after putting on my SD card?
********** end of dumb question ****
##### Personal observation/opinion #####
If by some chance you ever ask Galaxy S5 vs. a LG 3 which is better?
TAKE the LG3 (or LG4) and RUN as fast as you can away from this Galaxy S5 piece of junque!!!
I wish someone had written that in the months before I upgraded from my S2, when I was searching google for that answer..
##### END of Personal observation/opinion #####
NCE is older than OA1 and there's actually another one in between them. 2AND3 or something like that. OA1 is just 4.4.4. Nothing crazy-special. To do the updates, I had to unroot, odin my kernal back to NCE (I was on the middle one) and I used adb sideload from the stock recovery console. Sideload stops it from doing a data wipe, all other methods wiped the data partition. After a successful sideload install, I was free to reroot and do whatever.
Hope that helps ya some. I also agree with the G3 statement. I was very loyal to samsung prior to my experience with the 900A. Technically I don't think it's Samsung's fault tho, I'm pretty sure the carrier makes the choice to lock these things down.
Bought a replacement z3c as my former camera broke, WOW I do not remember this much pain in rooting the phone the first time.
I went through the dilligence of backing up the DRM keys - first time flashing down to 4.4.4 was somewhat painless, although in the .ftf i was using (I think it was an unbranded CE), i was getting CONSTANT process errors.
I've since flashed it back and forth (mistakenly flashed a forward .ftf build - 6.01 experiental) and now when I try to flash back to 4.4.4 (successful flash), upon boot, it attempts to put me through the language selection prompt, but I get a "google partner setup has stopped" that appears to freeze the device, and it reboots. constant boot loop - no ability to root as i don't have any system stability.
I'm trying to try different 4.4.4 versions in attempt to workaround this, but if anyone has insight it would be GREATLY appreciated.
*tear*
thanks in advance!
EDIT: RESOLVED - in flashtool, I checked the boxes to wipe data and user data when flashing new FTFs and that resolved the consistent crashing issues.