Related
All I would like to do is get my (not unlocked, but un-rooted) back to a stock recovery (I think?) and a stock OS. I want to be able to do updates OTA as they arrive on my phone, and the only reason I rooted in the first place was to get Gingerbread from CM7 and they didn't work. It got stuck in a endless boot loop and once I finally got a nightly working, it wasn't even worth it to me anymore.
I have used this thread: http://forum.xda-developers.com/showthread.php?t=614850
and done hours and days of research to try and solve my problem and get me to where I would like to be. I'd like to think I am not a noob to Android but clearly I am and I can't achieve 100% of my goal.
Where I am currently: Stock image, not sure of recovery, unrooted, bootloader unlocked.
Where I would like to be: Stock everything (I know I cannot relock the bootloader) just like when I bought it, so I can patiently wait for Gingerbread to push OTA whenever Google solves the issues.
Thank you and I apologize.
That guide has pretty much all the information you need. Flashing the stock HTC images and stock recovery will enable you to get OTA updates.
Read my signature, find "Unroot/restore" guide, look for the part for unlocked bootloaders.
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
rynstphn said:
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
Click to expand...
Click to collapse
You didn't explain where you got stuck, what you attempted, what went wrong and couldn't even state your recovery image. The guide you linked to is there for a reason, it works, however onlyif you follow it correctly without jumping in with 2 feet. If in future you require more precise help perhaps you should give precise information.
Perhaps the OP has encountered some of the issues i've posted about HERE?
Don't mean to kind of hi-jack this thread...
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
CTR01 said:
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
Click to expand...
Click to collapse
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Thanks!
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Awesome! Thanks for the reply and details.
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
efrant said:
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
DirkGently1 said:
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
Click to expand...
Click to collapse
Uh, sorry, but NO. What he says in that post is incorrect.
I have been using a custom recovery since I first got my Nexus One, and I have received EVERY OTA update.
EDIT: But hey, don't take my word for it. Try it yourself.
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
danger-rat said:
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
So, in my setup (which is a rooted-but-otherwise-stock ROM and Amon_RA's 1.9.0 recovery), I receive OTA updates, and they auto-install with no problem (as Amon_RA's 1.9 recovery does not verify signatures). Note, however, that every OTA update also does two things: 1) it removes the permissions on the su binary (which obviously disables root access), and 2) it copies two files (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) back onto the system partition, which will flash the stock recovery back to your devices as soon as you reboot. You will need to root first (either manually or by flashing ChainsDD su update before you reboot, or use SOC), then delete the two files, then reflash the custom recovery you want.
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Jack_R1 said:
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Click to expand...
Click to collapse
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
efrant said:
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
Click to expand...
Click to collapse
Yep, that's correct.
Cool
thanks for all the other responses to my question! I will look into this further when i have more time
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
DirkGently1 said:
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
Click to expand...
Click to collapse
If you read post 14, you will see that you CAN install them with a custom recovery...
Hello. First off, I want to thank everyone for their hard work here. I have followed many tutorials and have seen many great conversations to keep noobs like me from making mistakes when trying to delve into the world of ROMs and rooting. However, I did encounter some troubles while installing the ICS rom onto my bionic (running on .902). I think I may have accidentally overwritten the stock rom backup that I made with safe strap or whatever that app is (I'm sorry, like I said, I am a complete noob). Is there a way to restore the phone to stock, as in before I even touched it, even if the backup I made during the process is gone by my mistake?
I'm sure this has been asked a million times, and if so, I apologize, but as I noob, I have no idea how to even begin to search for clues. Walkthroughs would be nice, but links are fine too, since I'm sure there are plenty of the same questions out there.
Thanks!!!
Pete's motorola tools check it out you will find what you need there just google Pete's tool bionic
Sent from my XT875 using XDA App
Also I believe if you disable safe mode it will boot up rooted stock from don't quote me on that I am not for sure. Also I believe there is a unroot method in development not sure if it is for 902 or not though..
Sent from my XT875 using XDA App
Thanks for the info!
No problem here to help
Sent from my AXI0M IONIC using XDA App
R3l3as3DRoot and for3v3r root will take you back to 886
Sent from the Evil Empire
Thanks! Can that be used after the .902 update? Is it possible to do a dual-boot type deal between stock and the ICS version I have installed? I've seen mentions of dual-boot around here, but I can't get a clear grasp on whether it is possible or not, or if so, how to do it. Thank you very much!
Lonepalm said:
Thanks! Can that be used after the .902 update? Is it possible to do a dual-boot type deal between stock and the ICS version I have installed? I've seen mentions of dual-boot around here, but I can't get a clear grasp on whether it is possible or not, or if so, how to do it. Thank you very much!
Click to expand...
Click to collapse
Yeah I'm sure you can.
Get on stock .902(here).
Install SafeStrap.
Backup Stock Rom by Toggling "SafeMode"
Boot up ICS.
When you want to go to Stock .902 undo "SafeMode" and the Stock Rom should boot up on Reboot
Thanks for the answer! Hopefully I can give this a shot soon!
Lonepalm said:
Thanks for the answer! Hopefully I can give this a shot soon!
Click to expand...
Click to collapse
Yeah those instructions above are correct. I just came back from the AOKP ICS Rom to stock. 902. Worked fine. I have all my apps and stuff too.
Sent from my DROID BIONIC using Tapatalk
Don't know what I'm doing wrong here, but when I plug my phone in to my PC, the phone realizes it, but doesn't seem like the PC does. Also, when I open RSD Lite and try to load the file, it doesn't do anything after clicking "Start". Please help me try to diagnose what I may be doing wrong if you can! Thank you!
Lonepalm said:
Don't know what I'm doing wrong here, but when I plug my phone in to my PC, the phone realizes it, but doesn't seem like the PC does. Also, when I open RSD Lite and try to load the file, it doesn't do anything after clicking "Start". Please help me try to diagnose what I may be doing wrong if you can! Thank you!
Click to expand...
Click to collapse
Enable Usb Debugging and Unknown Sources. Download Motohelper drivers
Sent from my DROID BIONIC using Tapatalk
I'm sorry I probably should be a little more specific. I have both of those enabled and I do have the Motohelper drivers installed. I am following the steps here: http://forum.xda-developers.com/showthread.php?p=22758211#post22758211
On step 8, I do not see a file named FXZ or a file with that extension, but I figured it was the file with the name that the zip file had. I chose that file after clicking "..." and hit Start, but it doesn't do anything.
I am running the ICS version cyanogen mod 9.0.0-rc0-droid_bionic-kang build number alpha_2012_02_10
I already have SafeStrap installed (used that to get this rom on). So, looks like I'm stuck on or around step 8 from the other steps posted. Once I can get past that, I can continue with the steps posted in this thread!
Thanks!!!
Lonepalm said:
I'm sorry I probably should be a little more specific. I have both of those enabled and I do have the Motohelper drivers installed. I am following the steps here: http://forum.xda-developers.com/showthread.php?p=22758211#post22758211
On step 8, I do not see a file named FXZ or a file with that extension, but I figured it was the file with the name that the zip file had. I chose that file after clicking "..." and hit Start, but it doesn't do anything.
I am running the ICS version cyanogen mod 9.0.0-rc0-droid_bionic-kang build number alpha_2012_02_10
I already have SafeStrap installed (used that to get this rom on). So, looks like I'm stuck on or around step 8 from the other steps posted. Once I can get past that, I can continue with the steps posted in this thread!
Thanks!!!
Click to expand...
Click to collapse
SafeStrap disables ADB(that Im sure of) which will not let RSD run(im pretty sure) you have to select the xml file
Sent from my DROID BIONIC using Tapatalk
Yes, the XML file is the one I select. However, it will not do anything in RSD. Is there anything I can do to enable ADB in order to let RSD run?
Update: I found a way to do it. I think things are going okay so far. Looks like it is installing. If it does install successfully, I would like to do everything perfectly right going forward.
So, after this is installed, I will want to:
1. Get root access again using Motofail? I assume doing this return to stock will remove root access.
2. Install SafeStrap. Once that is done, I toggle Safemode to enabled, which will backup my stock rom and protect it from being overwritten?
3. Then, flash ICS from the zip files on my sdcard?
Lonepalm said:
Update: I found a way to do it. I think things are going okay so far. Looks like it is installing. If it does install successfully, I would like to do everything perfectly right going forward.
So, after this is installed, I will want to:
1. Get root access again using Motofail? I assume doing this return to stock will remove root access.
2. Install SafeStrap. Once that is done, I toggle Safemode to enabled, which will backup my stock rom and protect it from being overwritten?
3. Then, flash ICS from the zip files on my sdcard?
Click to expand...
Click to collapse
Yes sir.
Sent from my DROID BIONIC using Tapatalk
found by me. cheesecake staging third server. posted pics on droidhive
EDIT: UPDATE. well after a full day of messing with the leak update i can say
1. radio update fixed the connection issues including lte, 3g, and wifi issues that lately were getting worst
2. battery life greatly went up a bit compared to what i used to get out out .902 and .905
3. color and screen seem to be more "vibrant" than before. good thing imo
4. had issues with playing youtube and netflix last night but a quick reset of the phone and issues were gone
5. have no issues with the face unlock
6. i've messed with nearly every feature and option and everything is running smooth as butter. no random reboots nor connection issues
7. successfully rooted using motorola 4.0.4 root method
8. camera works great and quickly too. image stabilization added on both pictures and video recording
now if your on and off about updating well take my word that you'll be happy with the update. if your one of the many like I that started to hate the damn phone because of the latest connection issues or crappy updates, this will make you fall in love with the beast that is the first 4G LTE verizon Motorola DROID Bionic
will be posting pictures up soon!
I found the same update where was the file saved?
/*Edit: nevermind I found the update file in the /cache folder*/
Wow pretty cool.
Sent from my XT875 using xda premium
Running it now. So far pretty smooth. Only negative is my webtop doesn't work. Oh neither does the face unlock. Other than that it is sweet!!
Sent from my DROID BIONIC using XDA
Need to be on 902 or 905 for this?
905.
Sent from my DROID BIONIC using XDA
I think I'll wait on this one. Don't want to get burned like some other model users did on a leak.
is it possible to flash back to .902/.905 from this ICS?
I am on 905 rooted but stock and hadn't even removed the bloat. However I cannot install this update it fails just after it tried to "verify current system" the error says
assert failed: apply_patch_check("/system/bin/logwrapper". then what appears to be the output of two md5sum runs
then
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
You can't be rooted.
You may have or have had either Clockwork Mod Recovery installed or Safestrap. Whenever I use CWM and then wish to remove it, I do the following:
1. I uninstall it through normal methods
2. Then I navigate to "/system/bin"
3. I delete the file named "hijack"
4. I then delete the file named "logwrapper" and rename the file "logwrapper.bin" to just "logwrapper"
This always seems to completely remove any traces of CWM. Hope this helps!
fxz back to stock and try it again...
so lapdock doesn't work on this?
---------- Post added at 03:29 PM ---------- Previous post was at 03:21 PM ----------
Bionic owners, when using ICS change security setting to power button locks immediately, then faceunlock works properly...Tip #1
from p3droid
No lapdock for now...but does HDMI work?
It has been confirmed that you cannot FXZ back to stock .902/.905
Info provided by P3Droid
nobreak1970 said:
It has been confirmed that you cannot FXZ back to stock .902/.905
Click to expand...
Click to collapse
When the official ics ota is released you should be able to FXZ to that
Sent from my Galaxy Nexus using xda premium
I did NOT think of that. LOL doh!
cool.
Skeetch79 said:
You may have or have had either Clockwork Mod Recovery installed or Safestrap. Whenever I use CWM and then wish to remove it, I do the following:
1. I uninstall it through normal methods
2. Then I navigate to "/system/bin"
3. I delete the file named "hijack"
4. I then delete the file named "logwrapper" and rename the file "logwrapper.bin" to just "logwrapper"
This always seems to completely remove any traces of CWM. Hope this helps!
Click to expand...
Click to collapse
Tried this, and got a different error this time complaining about /system/bin/mount_ext3.sh..
Update: opened up that script and saw where I had some lines added from forever root, removed those lines and am currently installing ICS
You must have used a version of 4everoot that modified the mount-ext3.sh file to keep root through an update. You will have to either FXZ or manually re edit that file to remove the lines at the bottom that protect root.
cellzealot said:
You must have used a version of 4everoot that modified the mount-ext3.sh file to keep root through an update. You will have to either FXZ or manually re edit that file to remove the lines at the bottom that protect root.
Click to expand...
Click to collapse
Whoops did that and updated my post just before I saw your post. Thanks for the input.
you have to be completely unrooted for this update to work? thats kinda silly
I downloaded the soak test ICS file but it fails, i do not want to keep downloading every time it fails while im troubleshooting. where is the OTA file kept so i can move it. Also how would i be able to activate it again once i finish
If you look up details about some of the gingerbread updates, one of them has information on where the ota is stored at. I dont recall off the top of my head, but I do remember this being discussed before under one of the GB updates, possibly .905 but not sure.
Sent from my DROID BIONIC using Tapatalk 2
its stored in /cache
You need to be rooted to see and grab it. I had to use RootExplorer. Even though I was rooted, and Astro could see and navigate to the folder, it didn't see the file.
Oh, btw, its been said that the MD5 (check sum) of the soak .246 matches the .246 that had leaked a few weeks back.. In other words, the soak is exactly the same as the leak. SO just find and download the leaked copy if someone hasn't re-posed the Soak.
I found the soak
https://docs.google.com/file/d/0B7z9xJrt55a6bFM0YUV1amhLZVU/edit?pli=1
Soak/Leak is also included in the HOB at -> http://www.droidrzr.com/index.php/topic/4026-samurihls-house-of-bionic/
Is this what the OTA will be for the rest of us?
Should I be free to download this and be on true official Motorola ICS?
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
tweakedlogic said:
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
Click to expand...
Click to collapse
Try this thread. http://forum.xda-developers.com/showthread.php?t=2611278
I think most issues related to the update have been covered pretty well. Best of luck to you.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
It sounds like you have quite a bit more reading to do so that you can understand exactly what you are trying to do. That said I'll try to answer your questions.
tweakedlogic said:
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
Click to expand...
Click to collapse
Is TitaniumBackup the only root app you've used, have you frozen anything, installed any mods, or messed with any of the apps in your system/app folder? This will become important later.
tweakedlogic said:
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Click to expand...
Click to collapse
It sounds like you need to uninstall BusyBox. Normally SuperSU will uninstall this but it sounds like you tried a different method of unrooting that may have left bits in your system and since you weren't technically rooted anymore SuperSU didn't know what it needed to do.
tweakedlogic said:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
Click to expand...
Click to collapse
It sounds like you have the AT&T i537. This phone has a locked bootloader as you know. AT&T has required Samsung to lock down the i537 and will not allow them to release any firmware on Kies, this is why the software says your phone is incompatible. Basically AT&T is screwing us hard.
tweakedlogic said:
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Click to expand...
Click to collapse
The website you linked to is giving you bad information. The MI2 file is not technically "Official Firmware". This is a pre-release version of the firmware that DesignGears was able to get for the community. This will become important below.
tweakedlogic said:
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
Click to expand...
Click to collapse
As you've stated, this MI2 zip file that you've downloaded has a single exe file in it. This exe file should be run from a computer and it will allow you to flash new firmware to your phone. BUT, as I mentioned above this is pre-release firmware. What that means is you will forever be stuck on this firmware, you will not be able to take official updates from AT&T or Samsung. If you're ok with that, then go ahead and flash your phone with the pre-release of 4.3. If you want the official 4.3 update you have a little work to do. Above I asked you if you messed with any of the files in system/app, this is because the official update file can be downloaded and can even be flashed but it checks nearly every file in the system/app folder to make sure that it is the original file. If you've modified anything in there, the update is going to fail.
I'm going to post a few links of stuff you should read, but there is definitely a lot more that you should be reading.
How to flash stock MF3 - this is most likely the firmware you are on, but this thread will tell you how to get it back to stock, the way it was when you took it out of the box. This should allow you to take the official 4.3 update if other methods don't work.
MF1 Pre-release (4.2.2) - this is a pre-release of 4.2.2, you should read this.
MI2 Pre-release (4.3) - this is a pre-release of 4.3, read this thread to understand the benefits and drawbacks of flashing this pre-release firmware.
Official 4.3 Update Thread - this tell you what you need to do to try to update your phone to the official version of 4.3. Currently there is to way to root the official 4.3.
SafeStrap Thread - this will allow you to flash TouchWiz 4.2.2 based ROMs on your phone. Again, you need to read before you do anything. There's actually a lot we can do even though our bootloader is locked.
I can't stress enough how important it is to read. Once you've read everything and you think you understand what you're doing, READ MORE. There's always somebody who's done what you're trying to do and someone has more than likely given the answers you're looking for. Read as much as you can and you can avoid bricking your phone and ending up with a paperweight.
Good luck and us know if you have any questions, everybody is here to help.
You mentioned something I had forgotten, I did install app quarantine so I could remove the samsung and att apps from my drawer. So i went back and installed active root and app quarantine and unlocked the apps. But it seems I must have also deleted /system/apps/wssyncmldm.apk and .../KNOXAgent.apk. I can't believe that I deleted them instead of renaming them like I normally would, but it seems that's what I did.
So I'm hoping that some of you can copy these files to a google drive or something so i can reinstall them. pretty please?
If all else fails, i have insurance so my phone might get broken in a fall while doing some dangerous house work tomorrow.
tweakedlogic said:
You mentioned something I had forgotten, I did install app quarantine so I could remove the samsung and att apps from my drawer. So i went back and installed active root and app quarantine and unlocked the apps. But it seems I must have also deleted /system/apps/wssyncmldm.apk and .../KNOXAgent.apk. I can't believe that I deleted them instead of renaming them like I normally would, but it seems that's what I did.
So I'm hoping that some of you can copy these files to a google drive or something so i can reinstall them. pretty please?
If all else fails, i have insurance so my phone might get broken in a fall while doing some dangerous house work tomorrow.
Click to expand...
Click to collapse
You need to read the links I posted, all of this is explained including how to get the apps back that you deleted.
I so much miss being able to just flash with clockworkmod. Things were so much easier.
Sent from my SAMSUNG-SGH-I537 using Tapatalk