Hello i am trying the webtop Mod, with my atriz 4.5.91 att, i think its OTA update, not sure, boughted like that, and its a no go; i try to undo the Mod by returning the original apks, but theres a PortalService error saying IllegalArgumentException and another one from PortalHdmiHelper with a bindservice failed for mmirrorconnection.
i check the permitions and are the ones recommended and the sizes check with the ones in bakup.
does someone have the original ones?
I also have ATT 4.5.91 OTA and have Webtop over HDMI working.
If you're new to rooting, etc. I would recommend backing up all of your precious apps and data (Titanium Backup is helpful) and then reinstalling 4.5.91 OTA. Then install Superuser and root your machine using this link:
http://wiki.rootzwiki.com/index.php...ingerbread.29_unrooted_w.2F_locked_bootloader
Then follow the instructions in this link for Webtop over HDMI:
http://forum.xda-developers.com/showthread.php?t=1144119
I'm sure there are quicker ways, but I have tried several of them without success
Original OTA 4.5.91 webtop files.
I'm in need of the ORIGINAL DockService.apk, DockProvider.apk, PortalApp.apk, and their associated odex files from the OTA 4.5.91 AT&T software.
I don't have originals because the script I used to backup the originals and install the modified files was ran twice. Now I need to restore them to install the OTA 4.5.141 update.
Thanks!
Related
Used to my beloved Captivate, when I got my hands on the Atrix I rooted it and I erased some of the apps that I didn't want (everything from Bell actually). If I have a System Dump of Bell's ROM for the Atrix, can I just replace everything in the files from where I deleted the apps, reboot, and have an "untouched" Atrix?
I know, I should have read before....but it's done, so...lets face the music.
Thanks
Someone made a system dump of the system folder from the Bell Atrix. Link here: http://forum.xda-developers.com/showthread.php?t=1004503
To stay safe, I'd restore those files that you deleted and then freeze so they won't start. They might be needed for future updates.
I have a ATT atrix rooted in 1.5.7.
My webtop is full open too with the script of Sogarth.
The phone ask me to update in 1.8.3 if i do, i can root with Gingerbreak after the installation of the update but i don't loose anything else? the faculty too use the webtop without hdmi?
Or before the update is better for me to uninstall the script of Sogarth and try to restore the original files dockApp and PortalApp?
I sorry if the reponse is already here but i can't find anywhere...
Thanks for the information.
Sent from my MB860 using XDA App
Kind of new to the technical part of android here.
I have an Atrix running 4.1.8.3 with the following:
Rooted
Enabled Sideloading
SD Speed Hack
I have no other major system mods (no webtop mod, prom's, etc).
Here's my problem:
I don't want to lose my data/brick my phone.
How can I make a complete backup of every last thing on my phone? (Camera images, messages, ringtones, etc).
I have Titanium Backup installed that backs up apps, but is there a way to make sort of a "recovery image" or a mirror backup of my entire phone that I can flash?
Am I better off unlocking the BL first, and then flashing the sbf? (I know that this involves a factory reset in the process).
Or should I just use the OTA? My root, sideloading, and sd hack shouldn't interfere with the update, right?
Can I use the preinstall method to root my phone for GB, even though I'm rooted already? (Used gladroot)
I don't intend to jump into the custom ROM wagon just as yet, mainly because my job leaves me with no extra time to sit down and do it, restore my data, etc.
Today, I'm off though
Sorry for my noobishness, atleast I didn't post this in the development section
Thanks!
[Q] Clarifying switch from 2.2 ROM to P3 pr-root GB
Hey guys, just want to make sure I have the process down for my switch tonight. I read through few other threads and didn't see this addressed directly.
So I am running the affinity 2.2 ROM and would like to upgrade to P3's pr-root version of Gingerbread. Since the rom is debloated and deodexed I can't xo a direct update because I am pretty sure some system files will be missing. So the question is do I have to SBF back to stock or could I just restore the android backup I made before updating to the ROM? From what I know so far (but I am new to this) doing so would fulfill all the requirements for the P3 upgrade.
Thanks in advance.
Sent from my DROID X2 using XDA App
Its probably best to err on the side of caution and sbf to avoid any unforeseen events
Sent from my DROID X2 using XDA App
I don't have SBF so I used a regular backup. Might be good to get the 2.2.2 system dump just in case you deleted a few apps that will make you error on upgrading.
I'd make a backup of your apps/data (Titanium Backup, or whatever equivilent you may use). SBF to stock, boot up, re-activate, re-root, and install the recovery app. Slap P3's update.zip on your sdcard-ext root, boot into recovery, and apply it. After that you can re-install your backup program and restore your apps.
That's what I did. I don't think anyone has put out any custom ROMs for this release, but I'd only assume they are coming shortly.
i didn't sbf before i flashed p3s gb and everything has worked great.
i would flash the orig backup. restore all apps. restore the build.prop to the original. delete script manager to get rid of any scripts that you were running.
wipe data, system restore, wipe dalvik, wipe cache and flash the p3 gb. that's all i did.
h_10 said:
i didn't sbf before i flashed p3s gb and everything has worked great.
i would flash the orig backup. restore all apps. restore the build.prop to the original. delete script manager to get rid of any scripts that you were running.
wipe data, system restore, wipe dalvik, wipe cache and flash the p3 gb. that's all i did.
Click to expand...
Click to collapse
Im still new at all this but that seems like more work than just doing a sbf, wouldn't it just be easier to sbf the phone?
Sent from my DROID X2 using XDA App
Thanks for all the replies guys.
H_10 hit the nail on the head about what I was going to try. But EvilTim might be right in that it may end up being a little more work that way. I just never had SBFed before (coming from blackberry) and figured I knew this route better. I guess it wouldn't hurt to learn how to SBF now anyhow but I thought I saw some people having some weird problems SBFing.
the sbf problems are why i stayed away from sbf. i've used sbf on my OG droid w/ out any issues but reading about all the issues w/ the x2 made me shy away from it. it's entirely up to you. it was that much "work" to restore the phone for me since i wasn't running a rom. just unfrooze my apps, re-stored orig build prop, deleted 99supercharger from init.d folder, and uninstalled script manager. took 5 mins.
h_10 said:
the sbf problems are why i stayed away from sbf. i've used sbf on my OG droid w/ out any issues but reading about all the issues w/ the x2 made me shy away from it. it's entirely up to you. it was that much "work" to restore the phone for me since i wasn't running a rom. just unfrooze my apps, re-stored orig build prop, deleted 99supercharger from init.d folder, and uninstalled script manager. took 5 mins.
Click to expand...
Click to collapse
The only issues people have are 95% user error, read and follow all instructions and its easy
Sent from my DROID X2 using XDA App
I searched the forum but was not able to find this answer. Is there an .apk that can be renamed once rooted that will prevent OTAs from being downloaded?
I came from a Droid X and this is something that we had to do when we were rooted. On Verizon-Samsung devices.... does the OTA auto download and install? or do you have to accept it?
If you have Titanium Backup , you can just freeze "AT&T Software update" if I'm not mistaken that would do it.
That didn't work for me, at least on sprint. What DID work was letting it try to update and once it fails, it doesn't reappear for a long time (assuming you're on a custom recovery).
Sent from Sprint's 3rd Blazed ICS Galaxy
I'd like to know this as well...
I guess the biggest concern I have is being able to decline the OTA. Is this possible? I have rooted, loaded CWM, and I have removed some system .apk files that I had no use for (i backed them up to sdcard though).
If the OTA is automatically accepted... it would fail due to CWM, correct?