yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] gagdude:
https://t-mobile.jive-mobile.com:443/#jive-document?content=/api/core/v1/documents/4166
[General Questions and Answers] CoNsPiRiSiZe:
Thanks gag! I'll call tomorrow!

::Respect::
[TouchPad Q&A, Help & Troubleshooting] lewmur:
Can someone post a current link to the TWRP2.2 zip file? All of the links I've tried in this thread seem to be broken.
[TouchPad Q&A, Help & Troubleshooting] jacobas92:
If I'm not mistaken, you can actually just install it from goomanager (a LOT easier).
[TouchPad Q&A, Help & Troubleshooting] O.a.T.:
The attached should do it for you. Be aware though that TWRP 2.3 has been released, but not sure if that includes the TPad yet.
[TouchPad Q&A, Help & Troubleshooting] tiquau:
Do not install 2.3 from Goo Manager. It freezes when boot up in recovery. I don't think TWRP has released 2.3 for TP. Don't know why GooManager has 2.3.0
[TouchPad Q&A, Help & Troubleshooting] Arwany:
Thanks, you are the best!

Nobody make it better for the community than O.a.T, Thanks
[TouchPad Q&A, Help & Troubleshooting] zanderman112:
Wish I had seen this before I flashed it...

Posted by Mr. Z's Galaxy S3.
[TouchPad Q&A, Help & Troubleshooting] shumash:
Which explains why you should only download the script from goomanager. If you had tried that, you would only get TWRP 2.2.2 since that's the latest for TP.
[TouchPad Q&A, Help & Troubleshooting] zanderman112:
I did... but thanks for assuming I'm an idiot.

They must've taken it down, but it was definitely up before.

Posted by Mr. Z's Galaxy S3.
[AT&T Samsung Galaxy Note I717] simbill:
I have tried researching online, but cannot seem to find what I'm looking for. Im currently awaiting a 2 day ship on a new gnote, after finally becoming fed up with its gps woes, although my previous gnote experience has high praise for the gps in this device. My question is.. anyone know, or know a way to find, the figures for field failure rste of the galaxy note? Or cellphones in general to give me a general idea?
[Galaxy Note II General] sectorlord:
It happenned to me once last night... I need to power off on the unit to make it worked...

Should i ask for replacement....
[Galaxy Note II General] gsustech:
Could it be due to the "Smart Rotation" feature which identifies the way you are looking at the device to see if it actually needs to rotate the screen? (E.g. when u are in bed and still holding the device upright in relation to your face.)

This is a feature u should be able to disable in the settings if u want. I haven't got my Note2 yet to confirm however...
[Motorola Atrix 2] hi_john:
i have tried to install ICS OTA but was having an error so i saw a post asking to delete some files from system after that when i restarted my device it keeps stuck on the splash screen i tried to wipe data but my device isnt starting. Can anyone have me a rom that i can flash from the original phone recovery i really need to turn on my phone :S
[Motorola Atrix 2] Apex:
Dude, you've got to be more specific. What 'files' did you delete, and did you wipe data via stock recovery or via CWM? Since you wiped data/factory reset your phone, and didn't flash a ROM or install the OTA, you have no system image, so of course it won't boot. What error message were you given when trying to update to ICS via the OTA? :confused:

Sent from my rooted Mayan Calendar
[Motorola Atrix 2] hi_john:
i was running 2.3.6 and want to upgrade to OTA ics but it was showing an error while updating so i factory reset my device i was running stock rom and my device was rooted today i read in a thread to delete Delete file /system/bin/logwrapper would make ics work but it didnt work and now my device is stuck at splash screen :S i tried to wipe data but still it is not working
[Motorola Atrix 2] Apex:
I have to ask, why are there two posts from you on this same issue, both in the General Section and the Q&A? Please refrain from making duplicate posts, as it clutter up the forum. At any rate, you followed this thread: (?) http://xdaforums.com/showthread.php?p=32632730

OTA ICS update "The software update failed"

Sent from my rooted Mayan Calendar
[Motorola Atrix 2] mtnlion:
Reading for comprehension is key. The posts concerning the logwrapper was for a specific problem pertaining to custom recoveries. Now you need to check out Apex_strider's noob thread and learn how to properly flash a fxz. Read read read then when you've done that read some more. And I mean all of it! do not take pieces of it like the logwrapper out of the context of the discussion. Understand the whole of how to do something before you attempt it.
[Motorola Atrix 2] hi_john:
i have tried doing fxz but its showing an error or step 6 and my battery is low now i put my phone on charge its not even charging seems like i have lost my phone
[Motorola Atrix 2] mtnlion:
Here's your options

1 mcgyver method : http://xdaforums.com/showthread.php?t=892026

2 factory cable: http://xdaforums.com/showthread.php?t=1392693

Edit: you could also purchase a standalone battery charger or find another A2 or a bionic will work to charge it in.
[Motorola Atrix 2] Apex:
Another thing the OP could try is CFB's method using the DNA technique... :thumbup:

Sent from my rooted Mayan Calendar
[Motorola Atrix 2] hi_john:
Thank you so much i was like fed up :S but i did it because of you guys :) thanks alot
[Motorola Atrix 2] Apex:
If you don't know how to read the posts (which there are several) as to how to go about this, and aren't possessing the initiative to search the forums for this, you probably shouldn't even be messing around with your phone. Just sayin'. This is a developer Site, not tech support...

Sent from my rooted Mayan Calendar
[Motorola Atrix 2] Algarin:
Stuck on M dual core screen

Hi all, I was trying to install the avatar v2.13 rom on my atrix 2, I went into recovery with the atrix 2 bootstrap recovery, backed up my current rom wiped everything and proceeded to install the rom. After it was installed, all I got was the M dual core screen folloed by a black screen and the M screen again. I'm running linux Zorin in my computer and i've looked allover the place for a solution to this. Can anyone please give me some guidance on to what to do to solve this dilema? Your help will be apreciated guys.
[Galaxy S III Accessories] RebDovid:
Today, I received and installed my test Just Like Glass screen protector from DBA Cases. It's larger than the current mass market screen protector that I'd previously bought for myself and my wife, but not yet installed. After installing the smaller one on my wife's SGS III, I'll compare them directly. My initial impression is favorable, but based on too little evidence to be worth much.

By way of background, I had a ZAGG screen protector on my Samsung Vibrant for several months, but removed it. Over time, I became dissatisfied with the extent to which the ZAGG darkened and obscured the screen--not, however, to the point of unusability. I also didn't are for the texture. Fortunately, for the next several months nothing happened to the screen. For that reason, when my Vibrant stopped charging and T-Mobile replaced it with a Samsung Exhibit II 4G, I went naked. Very shortly I discovered a small scratch. It's not noticeable with the screen on, but I know it's there. This experience determined me on getting screen protectors for our Galaxy S IIIs.

After removing the DBA Complete Ultra case, I installed the Just Like Glass screen protector in a steamy bathroom, with wet fingers. I prepared the screen in accordance with the clear instructions provided, except that I also cleaned it by spraying some Costco optical lens cleaner on a lint-free, microfiber eyeglasses cloth.

After spraying the protector liberally with the provided solution, it went on easily. I wrapped the provided cloth around the short end of a credit-card, which I used to squeegee out solution from under the protector. Noticing one circular area that would not squeegee out, I used scotch tape to try to remove it. Even with the protector on for barely a minute (post-squeegee), it was difficult to pry up. (This, I think, is a good thing.) Unfortunately, I did not succeed i removing the circle. Whether it's a dot of lint or dust, or will disappear of its own accord, time will have to tell. There are also some hazy areas in the upper left-hand area.

Neither the dot nor the haze is visible when looking through the protector with the screen on. The protector is very smooth. There's room around the perimeter for cases that take up more space than the DBA Complete Ultra that I installed last night.

Photos and developing impressions over the 5-7 days it's supposed to take to fully cure and for the solution to evaporate will follow.

***********

A few scattered impressions after less than a day's use. First, the texture or feel is smoother than the glass on my iPad. Second, on the two long sides of the phone, there's about a one-eighth inch gap between the edge of the screen protector and the edge of the phone.Third, the front-facing camera is uncovered, but the screen protector does cover the proximity sensor and light sensor. The CEO of DBA Cases says he easily can change the factory cut; I'll be checking over the next several days to see whether the current cut causes any problems.
[Galaxy S III Accessories] RebDovid:
[Reserved]
[Galaxy S III Accessories] spicydicy:
any more info or photos? pics would be hugely appreciated!
[Galaxy S III Accessories] RebDovid:
Coming soon. I've wanted to give the screen protector a few days to bond/cure, and to be able to offer more than superficial impressions.

I will say that the Just Like Glass protectors are high quality, but I did a better job installing the (smaller) production protector on my wife's S III than I did installing the larger protector on mine. I'm not sure whether the larger size is more difficult; I had bad luck, or what. When the screen is on, there are no problems. But when it's off there's at least one pin-point that doesn't go away, even after trying the scotch tape trick.
[Galaxy S III Accessories] T3hBraveBoss:
So I presume you received the larger cut, has any peeling happened or does it perfect fit. I am also receiving one so ill be posting a review soon.

Also the reason you zagg invisible shield fogged up because I would say it is a little pourus so it collects grease from your face when you answer a call or what not
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
I'm trying manually install 4.1.2 on my rooted Nexus 7 with CMW.

I downloaded the zip, placed it on my Nexus 7, proceeded regularly to install zip

i selected the zip and it aborted, says Status 7.

Thanks to the community below are solutions to get the update to flash.

EDIT

Thanks to Logic_

You can flash this .zip instead which disables all the checks but do it at your own risk as it can brick your tablet

https://www.dropbox.com/s/isqpvb0w26....1.2edited.zip

EDIT 2

osm0sis method to get the update to work is simpler and possibly risk free.
[Nexus 7 Q&A, Help & Troubleshooting] ralphx10:
Did you try to redownload the zip?
[Nexus 7 Q&A, Help & Troubleshooting] mayoor_rao:
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.

I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
[Nexus 7 Q&A, Help & Troubleshooting] nyijedi:
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
Oh okay, how would I restore those files to their original state though?
[Nexus 7 Q&A, Help & Troubleshooting] taydee:
I'm having the same problem. I cannot seem to flash the update with CWM. I haven't edited any of the system files or anything like that. Is it the fact that I'm using a different launcher that's causing the problem?
[Nexus 7 Q&A, Help & Troubleshooting] Ohgami_Ichiro:
I'd like to know too. I get the Build.prop error too.
[Nexus 7 Q&A, Help & Troubleshooting] evodon84:
You've made no changes whatsoever? What about the kernel? Worst case just use mskip's toolkit to flash back to stock 4.1.1. Check the lag thread I posted what I did and it worked like butter.
[Nexus 7 Q&A, Help & Troubleshooting] bunbury911:
Hi all.....

I'm currently using stock Nexus 7 and did all ways possible here to update and nothing worked, last thing I did was go to setting, backup and restore and hit factory data reset and buala automatically got the update to 4.1.2

Nota: this is not a recommendation but if u wanna try do a Backup and good luck.
[Nexus 7 Q&A, Help & Troubleshooting] zippyijk:
I deleted the original browser files in the system/app folder too.

Found them on the rootwiki site here....

http://rootzwiki.com/topic/35089-can-someone-hook-me-up-with-browserproviderproxyapk/

Worked perfectly after :)
[Nexus 7 Q&A, Help & Troubleshooting] razzor1984:
modded build.prob / update problems to 4.1.2

i have similar Problem

Picture

h**p://i49.tinypic.com/w979qt.jpg

i modded my build.prob to Landsape mode. I guess that i corrupt the Md5 hash

(deleting the row with the added contend didnt solve it....)

I tried a factory reste and an Temp Wipe in clockwork. I thought this should solve the problem but i l get the sam error ....

What should i do ?

Flash a facotory Image ?

How do i get back my root, if the factory image is my only option?

Thanks a lot for your help

greets Razzor
[Nexus 7 Q&A, Help & Troubleshooting] retsnom:
I also had the same problem then remembered that I use FullScreenToggle to get rid of the nav bar. I just had to re-enable it and it installed fine.
[Nexus 7 Q&A, Help & Troubleshooting] Groid:
If you are getting the error on 'build.prop' look in the /System folder with Root Explorer or the ES explorer. If you see a build.prop.bak, that is probably your original file. Rename build.prop to something else and rename build.prop.bak to build.prop. Restart and then try taking the update again.

If you side-loaded the gnex browser so you could use flash, go to the /System/App folder and make sure you have BrowserProviderProxy.apk and BrowserProviderProxy.odex named properly. As stated earlier, rename browser.apk to browser.apk.bak. Restart and then try taking the update again. I had that problem. After getting the OTA installed, I renamed the browserproviderproxy files again, and made it browser bak file browser.apk. Now I have flash working perfectly again on the gnex stock browser.
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
Okay i managed to fix the browser proxy thing, turns out i had 10.apk at the end of it for some reason

and i renamed browser.apk to browser.apk.bak so that worked,

but now i got the same problem but with wallet
[Nexus 7 Q&A, Help & Troubleshooting] Groid:
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
I didn't, and i did use a modified APK, but i deleted that, then i downloaded an original but still not working
[Nexus 7 Q&A, Help & Troubleshooting] razzor1984:
build.prob error

Fixing steps for build.prob error :

VERY IMPORTANT: You will los all of your data, please make a backup befor you following this stepps ^^

Error Message apply_patch_check("/system/build.prob - "Numbers" , "Numbers")

My way which worked for me ;)

1.)

The only way, if you dont have any backup of the original build prob file youl have to flash a copy of the factory IMAGE.

In my case i used the Nexus Toolkit 3.2 V - with this marvelous tool I copied the Factory Image 4.1.1 on it

2.)

After the factory Image you will lose your root. Install Clockwork or a other custom recovery image. Then its easy too get back your root with the Toolkit (follow the steps)

3.) If your not able to receve the OTA update to 4.1.2, download it and copy the ZIP to your Nexus 7

After this, go back to Fastboot and install the Updates using the up an down Volium buttons to navigate

Now the updating process should go very smooth ;)

greets Razzor
[Nexus 7 Q&A, Help & Troubleshooting] lanwarrior:
I have the same error when installing from CWM and the ONLY CHANGES I made to my N7 are:

- Unlock

- Root

- CWM

- Battery Icon

Any other ideas? Will installing from ADB and Android own Recovery will work?

EDIT: I tried the update on my SECOND N7, which have all the above EXCEPT the battery icon mod and it works. So looks like the battery icon mod is the issue! Anyone know how to revert back to the original battery icon?

Also, since the first update failed, when I clicked on "Check" under SYstem Update, now my N7 said the system is up to date. How do I force the update to run again?
[Nexus 7 Q&A, Help & Troubleshooting] Logic_:
The system checks are there for a reason and I am in no way responsible if anyone bricks their device with this but...

https://www.dropbox.com/s/isqpvb0w26kqjdx/4.1.2edited.zip

This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.

I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.

Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom o_O

It's from JRO03D btw.
[Nexus 7 Q&A, Help & Troubleshooting] lanwarrior:
So you just flash this from CWM and that's it?
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
The only danger in running the ota with checks removed is that if the kernel or any files would normally fail checks will now be skipped. This can leave you with an incomplete update depending on what does not get patched.
[Nexus 7 Q&A, Help & Troubleshooting] lanwarrior:
OK, so the battery mod is the ONLY one causing the failed update. I found out I just need to get these 2 files from N7 with 4.1.1 and replace it in my N7:

SystemUI.apk

SystemUI.odex

Can anyone provide me with this files from your N7 running 4.1.1.?
[Nexus 7 Q&A, Help & Troubleshooting] Logic_:
Did the trick for me :)

Bricked was a poor choice of words on my part, but it'll scare off some people who have no idea what they're doing from flashing this on a whim.
[Nexus 7 Q&A, Help & Troubleshooting] lanwarrior:
So what I found out is that the edited OTA cause issue when the N7 UI (2 files I mentioned above) has been modified. Although my N7 boot up just fine, I received a "UI error" all the time and I no longer see any icons on the top bar, no dates, battery icon, etc..etc..

I think if you edited other things like Chrome the edited OTA works, just not on the OTA. I now have to go and reset my N7. Oh well.. live and learn.
[Nexus 7 Q&A, Help & Troubleshooting] Logic_:
Ah sorry I didn't get the fact that you modified your actual UI, I read battery Icon but I just assumed a custom one in the taskbar part of the status bar. I think you've had to (partly) de-odex your rom to make modifications like that? That's how it used to be ~2 years ago.

You'll have to either revert your changes or flash the stock rom I think.

Although if I were you I'd flash the update again, just for the heck of it. It probably won't do anything but I always feel like wanting to try everything before resetting.

EDIT: If you're going to flash anyway, you could just flash 4.1.2 right away

https://developers.google.com/android/nexus/images#nakasijzo54k
[Nexus 7 Q&A, Help & Troubleshooting] lanwarrior:
Any re-flash attempt, using the 31Mb zip file resulted in "assert error" about the SystemUI.apk. So I am going to just flash the entire ROM.

I have the odexed zip file from that is about 250Mb from here: http://xdaforums.com/showthread.php?t=1929270

But it's a zip file and I can't go to CWM anymore. I CAN go to Android Stock Recovery though. Should I just do "adb sideload <odexed zip file>" from here?

EDIT: Forget the sideload... all fails... looks like I have to revert back to stock.. deleting everything.. sigh.. Can't believe chaning the battery mod cause this much griefs...
[Nexus 7 Q&A, Help & Troubleshooting] osm0sis:
For those who've done some modding and can't remember what they did to pass the OTA asserts, all you need to do is dirty flash the system.img from 4.1.2 factory image in fastboot and eveything should work.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
+1

That is going to be the clearest path forward.
[Nexus 7 Q&A, Help & Troubleshooting] lanwarrior:
I have the new 4.1.2 img bootloader from here: http://xdaforums.com/showthread.php?t=1929270

I am using the Nexus Toolkit to flash this, and I was given the option on WHERE to install the img file:

- Boot

- Bootloader

- Recovery

- System

- Userdata

I choose "Bootloader" and even though it was successful, didn't fix my N7. Should I chose "system" instead?

If not, where do I get the system.img file from?
[Nexus 7 Q&A, Help & Troubleshooting] Logic_:
Your bootloader isn't the problem, your system is.

You can use the toolkit to easily flash a factory image.

You could also try extracting the 2 files you said you needed earlier, from the stock rom and then try flashing the update again.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Do just go flashing things over your bootloader! :eek: :)

The image files need to be extracted from the zip file inside the tar.gz file you downloaded.

Boot.img is the kernel and the others should be pretty self explanatory.

I'd also recommend you reflash your boot loader just to make sure its in order.
[Nexus 7 Q&A, Help & Troubleshooting] osm0sis:
Yup. Then wipe cache and dalvik. :good:
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
i updated the op so that people who have the problem can find the soluition thanks to Logic_ and osm0sis :)
[Nexus 7 Q&A, Help & Troubleshooting] osm0sis:
Cool. YMMV just due to some slight differences that *might* exist between the system settings saved in data between 4.1.1 and 4.1.2, but they should be neglegible considering it's all stock. Clear data on a few system apps, at worst, if problems arise. People have gone from 4.1.1 yakju to 4.1.2 takju on their GNs with no issues, so I can't imagine there being any problems here.

Worst case scenario: Backup your user apps and settings in TiBU. Go nuclear and format data in CWM/TWRP. Then just redo the settings on your system apps again and restore your user apps + settings from TiBU.
[Nexus 7 Q&A, Help & Troubleshooting] Sebianoti:
I'm backing up my whole tablet right now before i attempt to flash 4.1.2
[Nexus 7 Q&A, Help & Troubleshooting] Visa Declined:
This thread is awesome. I'm sure it's going to help a lot of peeps out.
[Nexus 7 Q&A, Help & Troubleshooting] osm0sis:
Wait. Here's an even better idea. Grab the 4.1.1 factory image from Randomphantasmagoria. Dirty flash the system.img from that. Bam. Untouched 4.1.1, setting structure preserved and the OTA asserts should pass with flying colors, so if there is any settings transitioning between the versions the OTA will now handle it.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
If your objective is to apply the jzo54k-from-jro03d ota update, then that is a great way to achieve it. However, if the goal is to get to stock 4.1.2 then the most direct route would be to flash boot.img, system.img and optionally the bootloader from the 4.1.2 factory image.