So I originally rooted using SuperOneClick, then I got an OTA that broke root. I then found gingerbreak and rooted using that method. I have done a few cool things, like change the boot animation and lock/unlock sounds, enabled sideloading, etc.
Anyway...
With rumors and speculation about Gingerbread coming out in the coming months (hopefully), I am wondering if the boot animations, lock sounds, and/or SuperUser access will deny the OTA from installing. Is it a good idea to return the ROM to stock to avoid any bugs?
Second,
Specifically on the Atrix, if I performed a factory reset, I assume I won't lose root access, but would I lose the boot animations, and lock/unlock sounds? Let's say I wanted to return it to a 100% stock ROM (un-root, stock boot animation, EVERYTHING) before the 2.3 update comes, how would I do it? I feel as though if I perform an OTA with the mods I've done to it, some unknown bugs/issues would appear (I've seen PLENTY of bugs as is). Can anyone shed some light on this? Call me paranoid, but I've seen too many software issues with this phone, and I'm hoping 2.3 will address them, and I hope I don't introduce any new bugs by updating a modded phone.
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
rytymu said:
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
Click to expand...
Click to collapse
Try this.
Motorola
brewstermax said:
Try this.
Motorola
Click to expand...
Click to collapse
I have 4.1.83, and this will not work for it.
I would be interested in learning more about this too
Sent from my MB860 using XDA Premium App
This is a thread I commented on over at the Motorola forums. I actually got the forum manager to comment on the issue:
"rytymu
What do I do if I'm on 4.1.83 and want to return to stock (rooted)? The software given just says my device is up to date...
Mark (Forums Manager)
With next update/upgrade you will go up to next stock version. You have to
wait til then.
rytymu
So if I understand right:
I most likely will not get an OTA notification because of the root access, so when I run the Motorola Software Update program after the next update comes out, it will then flash a 100% stock image as if I just pulled it out of the box? This includes removing/wiping busybox, root access, boot animations, and EVERYTHING else?
Mark (Forums Manager)
If you are on 4.1.83 but modded you will get ota notification but will
likely fail on install. If MSU is made available you can update /upgrade to
that version. Root and other sideloaded things will be removed. Stock ATRIX
Att software. Not AOSP Android."
I guess this is what I'm looking for, unless someone interprets otherwise...
brewstermax said:
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
Click to expand...
Click to collapse
OTA update should be fine if you have not deleted any of the original Moto files/bloatware, or leave any of the original Moto bloatware frozen. The updates only throw up at you when there are missing or frozen Moto apps and/or files.
If you are on 4.1.83, (or any firmware), and rooted only, you will get the update fine, but will lose root.
If you have flashed for example GladiAtrix, you will more than likely have to flash back to stock first.
If you have rooted on any version and then frozen any apps, thaw those apps and you will update fine, but again lose root.
Every time you update you lose root.
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
beazie0885 said:
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
Click to expand...
Click to collapse
If you installed a newer version of the same Swype, this should I imagine be the same as updating Swype. I'm thinking this would allow you to just unfreeze all the bloatware and update OTA. Only thing I can think of is that you try the OTA when it's available, and if it balks at you, flash back to stock.
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager at Motorola instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
rytymu said:
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. Now, I'm actually in the "soak" beta feedback over at the motorola forums, and I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
The Moto Software Update is not needed, and Mark, or whoever over on the Moto forums did not "tip" you off to this. This is no secret, and is well known. (BTW, you are breaking the NDA just by saying you are in beta, (soak feedback forums are down in any event as they are always taken down between betas), but that's another story, and being in beta doesn't make you more knowledgeable either).
You have made this sound more complex than it is.
To go back to stock (and the instructions are all over the forums BTW) --->
Flash 4.1.26, OTA to 4.1.57, OTA to 4.1.83!..............Done!
Or ------------>
Flash 4.1.57 sbf, OTA to 4.1.83!..................Done!
People who were having the OTA notification issues, (continually popping up), were those who flashed the 4.1.83 sbf which is floating around, and that's why they were told to flash 4.1.83 through the Moto Update portal.
(Edited above statement)
Sent from my MB860 using XDA App
Related
I am hearing some people who removed bloatware got soft bricked and then some are saying they didn't. Is there an official word on this? I removed some of the Samsung bloat because I would never use it.
If there is anyone HERE (on a forum I actually trust) that has updated their Vibrant to J16 after removing bloatware and didn't get a softbrick- then I will update. If not, does anyone have the bloat apks? I'd rather just download and install them all again then have to ODIN.
Never mind
DreamcastDC said:
Never mind
Click to expand...
Click to collapse
Never mind what? Does this have anything to do with my question?
I did. I removed a bunch of the programs that came installed wroth the phone, such as mobitv, gogo, the gps program by using Titanium Backup.
I had to reflash mine due to this problem.
Sent from my SGH-T959 using XDA App
Mine soft bricked and didn't even have bloat removed... all I had was root... no lag fix, nothing...... bricked and recovered in less than ten minutes... you would spend more time downloading and installing the bloat back... and when your device bricks anyways your gonna need odin so just use it or leave your phone alone...
I'm hardware blocked from accessing Recovery and Download so I'm trying not to softbrick my phone at all. Not because I don't want to use ODIN but because I do not wanna risk my phone being inoperable.
I was rooted and removed ALL of the Samsung crapware, and yes my phone bricked as a result of the OTA. I was able to flash JI6 via ODIN and everything is working again.
After the OTA, my Vibrant was stuck at the Samsung Vibrant screen.
Would I be able to do all of that through ADB? I'm hardware locked. Not only that, ODIN won't recognize my device!
Yes I removed a lot of bloat and still updated fine through Odin.
Btw, there is now a fix for hardware locked phones. I tried it last night and now my phone can access download and recovery through the vol buttons. Go ahead and get adb set up though--you'll need it to remove the hardware lock.
If Odin isn't working for you, (1) do you have the Samsung phone drivers, and (2) what version of Odin are you using?
Sent from my SGH-T959 using XDA App
Yeah I removed a bunch of stuff that I didn't user using titanium and I was also using the one click roote and I updated fine using odin.
Just a question, why would people want to remove these applications? does it have something to do with the battery life? or to have more memory for more applications?
It was kind of superfluous in my case since I have more app space than I'll ever need.
Sent from my SGH-T959 using XDA App
iynfynity said:
Just a question, why would people want to remove these applications? does it have something to do with the battery life? or to have more memory for more applications?
Click to expand...
Click to collapse
Because I know I'll never use them and they take up space in the app menu as well as the memory, also a bunch of them start themselves and take up processing power, like the Tel-Nav GPS app.
I rooted then unrooted, can someone explain what exactly Odin is doing and why people's phones are getting bricked? I don't really want to flash a rom or something if that's what Odin is doing. My goal is to keep everything stock minus the bloatware apps.
richiehd said:
If there is anyone HERE (on a forum I actually trust) that has updated their Vibrant to J16 after removing bloatware and didn't get a softbrick- then I will update. If not, does anyone have the bloat apks? I'd rather just download and install them all again then have to ODIN.
Click to expand...
Click to collapse
I have updated my Vibrant successfully without any bricks having removed bloatware each time before each upgrade.
I was always stock since I got the phone on release date. Now until JI5 came out, I had never decided to update the phone. When I updated to JI5 on the same day that was leaked, I did so via ODIN and had all the bloatware apps removed (TeleNav, GoGo, Slacker, etc).
When JI6 was leaked, I had done the same process again as above. I already had the bloatware removed before and once again after updating when it all came back.
When the official OTA JI6 came out, I waited a few days but flashed that over the leaked JI6 update without any issues once again via ODIN. I did the same thing again, had removed bloatware prior and again after. I honestly did not believe there was any difference in either prior nor do I see so after. Especially by file size or any fixes that weren't already in the leaked one.
This was just my experience and having removed the bloatware apps and not getting bricked. I never once applied any other modifications either (such as the battery ones, etc).
I did have 2 lag fixes applied (not at the same time) when I was on stock. The first one with terminal commands from a post here on the forums which was removed when I decided to try out One Click Lag Fix which was then removed before I flashed JI5. I have yet to apply a lag fix again with JI5 or JI6, nor will I be anytime soon I think either.
When you say everything is working again, did your bloatware come back? ARe you able to remove it if it did? For some reason I cannot remove the bloatware when it came back.
EDIT:
Woops, I meant to ask J3ST3RM4A3 this.
but has anyone seen this problem? after going to JI6 the bloat comes back and is not removable?
and if you did remove bloat, with what? ADB? Root explorer? Astro? Titanium? None of these worked for me
i purchased root explorer after i updated to JI6, it seems like such an useful app.
that allowed me to remove all the bloatware after the update.
i updated via KIES mini not OTA (i heard too much **** happened to people who did it the OTA way)
so when you delete your bloatware, they would just pop back? Cause i had that issue prior to updating root explorer. After i updated root explorer (purchasing the latest) i was able to successfully remove the bloat
richiehd said:
I am hearing some people who removed bloatware got soft bricked and then some are saying they didn't. Is there an official word on this? I removed some of the Samsung bloat because I would never use it.
If there is anyone HERE (on a forum I actually trust) that has updated their Vibrant to J16 after removing bloatware and didn't get a softbrick- then I will update. If not, does anyone have the bloat apks? I'd rather just download and install them all again then have to ODIN.
Click to expand...
Click to collapse
I had bloat removed prior to JI6. I did step 2 of this and had no trouble whatsoever.
Same. I soft bricked with the OTA update but Odin worked fine. I've heard there may be an issue with leaving the update.zip on your phone while you try to update.
Any help is appreciated, I'm still fairly new with Android, but trying to learn my way around.
When the OTA update for 2.2.1 came out, I decided to do a factory reset because I'm just picky like that, and I like to be fresh coming out of OTA updates. Prior to the factory reset, I was running stock 2.2, though I was rooted using the manual (D2) method through adb, I had bloat frozen with Titanium Backup, and I had Droid X Bootstrap installed.
I unfroze the bloat and did the 2.2.1 update prior to factory reset. I did not unroot prior to the OTA. After the OTA I did a factory reset. I expected the bootstrap to go as well. It didn't, and I noticed immediately because I was booting into its recovery every other reboot because I was no longer rooted.
I still had the superuser icon (ninja) in the app drawer, however was no longer rooted of course, so I loaded z4root and let it "unroot" me, and then let it root again, which fixed the Bootstrap recovery issue.
Here's my problem. Obviously the factory reset did not wipe everything because bootstrap was still trying to load. My phone is definitely more sluggish than it was prior to the factory reset. Different types of screen lag are very noticeable and the phone really lags later in the day if I don't reboot. I loaded less apps after the reset than I had prior to, but otherwise did nothing different. I want to try to remove the bootstrap too, as well as anything residual to try to figure this out, even if I do have to factory reset again, because it's definitely not stable the way it is. Is it possible to remove it, and how so?
I'm aware that this may not fix the problem, and to me it doesn't even make sense that it would, but I definitely feel something "off" here and for my own peace of mind I'd like to remove it at least for now just to see. I've done factory resets before and the phone always feels much snappier once it's back up and running. This time it's worse than when I started.
Any assistance would be greatly appreciated.
You would have to flash a stock sbf. Correct me if I am wrong but I think that stands for system boot file. That should take care of everything. I am sure u can find the thread on the forum on how to do it. Just to mention I think that all the boot strap does is hijack your normal boot process by interrupting it allowing u access. It doesn't actually replace the boot process.
Sent from my DROIDX using XDA App
Info on the bootstrapper can be found here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Basically it replaces the logwrapper.bin file which gets executed very early in the boot process. This allows bootstrapper to control the rest of the boot sequence.
To *just* remove bootstrapper, I think there is a backup of the original logwrapper executable stored in /system, so you could just replace the exploited version with the original.
However, if you are having issues, I would suggest you just go ahead and flash back to complete stock:
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
Make sure you are still on the 2.3.15 version before using this. Once you take the OTA (to 2.3.340) I don't think this SBF will work any longer.
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
crxin said:
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The .340 update "upgrades" your bootloader to 30.04. I've read that the 2.3.15 SBF will not work with this bootloader.
There are some SBF files produced by Team Black Hat (at Leaked 2.3.320 and patch files to put you to 2.3.340), but I've not used them.
I think you can find more info on those at mydroidworld (or you can support TBH by buying their app in the marketplace and downloading direct from there)
jaynyc22 said:
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
Click to expand...
Click to collapse
I'm not sure what you mean?
Try uninstalling from Manage Applications and re-install?
Do you mean the DroidXBootstrapper UI or the logwrapper exploit?
My friend lost the memo app on her samsung phone after upgrading to 2.2. Will these DJ0509 updates er whatever do that to me?
Basically, I haven't updated the software at all. I rooted and uninstalled a ton of bloatware right after getting the phone, and I guess I lost whatever it is that does the updates so I'm still on day 1 version... I've been thinking of updating.
Well, if I understand the rooted rom/update scenario I've read a bunch of times here (though not done myself), when you use the rooted flash scenario to put on the updates, it will wipe your device. So you will need to back it all up with titanium or something.
If you are stock and you OTA update the DL09 that just released this morning, then nothing gets removed or lost on your phone. This I did do and it's all there.
Are you talking about doing the standard update, via Verizon and Innopath ????
Backup with Titanium Backup. Install your new ROM/Software/Kernel/Theme. Use ROM manager/Download ROM/SonofSkyWalker3/Stock Apps. Chose Memo to reinstall. Install/Reboot. Go into Titanium and restore memos. All of your saved memos will be there.
Hope that helps.
superchunkwii said:
Well, if I understand the rooted rom/update scenario I've read a bunch of times here (though not done myself), when you use the rooted flash scenario to put on the updates, it will wipe your device. So you will need to back it all up with titanium or something.
If you are stock and you OTA update the DL09 that just released this morning, then nothing gets removed or lost on your phone. This I did do and it's all there.
Click to expand...
Click to collapse
Installing a rooted update .zip wont wipe user data. It will only wipe system. Also he wont be able to install via OTA because of the bloatware removal. Since OTA updates patch files instead of overwriting them. If it can't find them the update will fail.
So if you were to update using say super clean DL09 you won't lose user data. But if you were to flash the full odin DI01 so you could get the DL09 OTA, you will lose user data.
If you haven't done something please don't spread false information regardless of if you read about it many times, because you obviously got it wrong.
Sent from my SCH-I500 using XDA App
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
ogal said:
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
Click to expand...
Click to collapse
why dont u just make a nandroid, fastboot back to stock ics with rsd, dont root your phone or do if you think it doesnt matter which ur right ive flashed the leak and official multiple times already both rooted and not, boot back to recovery and try it again...i heard this might help although i never have had to but rename it update.zip.
heres the one i used have never had a problem:
http://forum.xda-developers.com/showthread.php?t=1982934
Hi, I've downloaded the OTA update from Verizon for my Razr M three times this morning because each install shows "The Software Update Failed". It'd be just peachy if they didn't make me download all 250 MB each time I tried. Sheesh.
Aside from that, it's still not updating. This phone is rooted, but has never had a custom ROM put on it.
Hmmm...now that I think about it, I do have a bunch of apps disabled, including some Verizon apps, etc. I'll try enabling them and trying this all again.
Hmmm...didn't work. Still getting the failed error message. Going to back everything up and do a Factory Reset.
lostpilot28 said:
Hmmm...didn't work. Still getting the failed error message. Going to back everything up and do a Factory Reset.
Click to expand...
Click to collapse
I am currently having the same issue in attempting to download/install the latest VZ update. I've done a factory reset and tried voodoo rootkeeper to temp unroot the phone to no avail. The only modifications I had made before the reset were deleting some of the bloatware manually with root explorer- those apps were subsequently restored from the reset.
Any idea how I can update the phone? Given that there is currently no way to install a custom ROM currently and can only delete bloatware, I'm thinking rooting this phone doesn't really help much if we are then not able to update it
Update
fiendebass said:
I am currently having the same issue in attempting to download/install the latest VZ update. I've done a factory reset and tried voodoo rootkeeper to temp unroot the phone to no avail. The only modifications I had made before the reset were deleting some of the bloatware manually with root explorer- those apps were subsequently restored from the reset.
Any idea how I can update the phone? Given that there is currently no way to install a custom ROM currently and can only delete bloatware, I'm thinking rooting this phone doesn't really help much if we are then not able to update it
Click to expand...
Click to collapse
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
ogal said:
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
Click to expand...
Click to collapse
I upgraded to JB via OTA from Verizon, you will not lose anything if you upgrade that way, nor will you have to setup anything again. If you flash it through RSD lite than you probably will lose everything plus have to go thru the setup process again. Hope this helps. Make sure you uninstall safe strap recovery and if you're rooted make sure you backup and save root via the voodoo app, before accepting the OTA. I found out the hard way. If you don't uninstall the safe strap recovery the OTA will fail every time.
Being rooted does not have anything to do with the OTA failing. Its safe strap if you are using that.
Sent from my XT907 using xda app-developers app
fiendebass said:
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
Click to expand...
Click to collapse
I used this method phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock-ICS-from-the-JB-leak_id35580 .
Followed all the links and tried to RSD back to stock and then OTA, but now Im bricked....any suggestions on flashing a fresh copy of ICS using RSD LITE??
fiendebass said:
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
Click to expand...
Click to collapse
Could you direct me to somewhere I can find out details about this? What is the fastboot method?
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
jjimenezjj said:
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
Click to expand...
Click to collapse
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
phonic said:
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
Click to expand...
Click to collapse
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
jjimenezjj said:
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
Click to expand...
Click to collapse
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
phonic said:
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
Click to expand...
Click to collapse
It's not that bad. Everything works fine except for updating the thing. As for the restoring the original browser.apk, if you mean Chrome, I never touched it so it is there.
My guess is that I didn't install the CWM Recovery correctly because I can't boot into Recovery Mode. It just hangs and stays in a loop. I will re-install CWM and see if that helps.
John J
Re-installed CWM Recovery and flashed 4.2.1 from there. Lost everything but I had anything important backup already. All is good