yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Rirere...

This is my understanding as well... (sort of! - I've always been a bit hazy on this topic:().

My take on it is this...

The OTA would only fail, if it found files in /system that SHOULD BE THERE, but have been removed, modified, or replaced by the user (or via some app run by the user).

Logically (one would think), the OTA can't check for files THAT SHOULDN'T BE THERE (How would it know what to look for?) but have been ADDED by the user... like the su binary that confers root.

So, an OTA on pure ROOTED (but in all other regards, unadulterated) stock you would expect to succeed... you'd just lose root (and from what I've read elsewhere, your Custom Recovery). Both of which are trivial to recover.

Is my understanding correct... or have I missed something?

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Rirere:
I believe you are correct! Theoretically, the script could rather easily check for added files by checksumming the entire /system partition before running the update (using a fast hash algorithm-- you're only looking for the presence of any changes, afterall). And I did have one OTA that went fine, other than losing root back on my Galaxy Nexus.

Again though, it's a classic case of should versus real life. Some root methods might alter things in /system without your knowing, or root actions might alter permissions. Either way, it's a tricky, nasty little game.

So far as recoveries go: yeah, OTAs have a nasty habit of trying to do that. Some of the more advanced recoveries can resist being overwritten though/slipstream a root ZIP into the update process.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Typically the OTAs also update the boot image, so the boot partition (LNX) is also checked. The stock recoveries almost always use the same kernel (with a different ramdisk) as the boot image, so they are usually rewritten too.

Owners of tilapia N7 devices have reported successful flashing of everything but radio firmware images when they used a custom recovery to process the OTA bundle. Not a disaster, as their devices will still function with old radio firmware, but it puts them in an unusual position of being unable to use the OTA to subsequently update the radio, even if they restore the stock recovery (the system files and boot images will have been changed, so almost all of the checksums will fail). At that point, using fastboot is an alternate option, but then the newbs will need to read about OTA images, unpack them, yadda yadda yadda.

IMO it is just a dumb idea applying OTAs to anything but a pure stock device. And when I say pure stock, I mean including the stock recovery. The boot loader can be left unlocked, but that's about it.

There are a lot of ways to skin the cat, but IMO the best way to proceed is to operate with two parallel but independent tracks of Nandroid backups/restores: one track is a sequence of pure stock, and the other your customized ROM du jour.

Let's presume you have a Nandroid backup of the pure stock ROM. Make a backup of your current (customized) ROM & get it copied off the tablet (in the event of a disaster), restore the pure stock ROM nandroid backup, flash the stock recovery back to the tab, and then take the OTA.

At this point:

[ unlocked bootloader ] soft-boot (no flashing) a custom recovery using fastboot, and then make yet another Nandroid backup of the newly updated stock ROM including the recovery image. (This becomes the new baseline for future OTAs)

[ locked bootloader ] re-root with motochopper, capture the (new) stock recovery partition using 'dd', flash a custom recovery ('dd' or other method), make a Nandroid of this. (These two backups become the new baseline for future OTAs)

Then, repeat any rooting customizations (if you are a "lightly customized rooted stock" kinda person), and restore apps (Market apps only!) with TiBu.

This may seem like a great deal of work, but it is the only way to insure that you can revert to a prior starting position. Look: after going down a road like this you can even restore the old customized ROM backup to make TiBu app backups after the fact, simply because you can return to any point in time if you have made a backup (and kept a copy of it off the tablet).

Everybody makes mistakes - even the experts. But the lazier folks are (read: toolkit user) the more likely is a disaster. Everybody needs to make backups.
[Nexus 7 Q&A, Help & Troubleshooting] backslashV:
What will happen if I change some values in build.prop editor? I won't be able to install stock ROMs anymore? Or what?
[Nexus 7 Q&A, Help & Troubleshooting] kbeezie:
Depends on how you mean "install", you can always install via .img or recovery flashing method, but course that will overwrite your build.prop with the provided version and you would just have to re-edit the values again.

Did you mean OTA wise? If the update doesn't check for the hash of the build.prop, it will likely just replace it with a newer version if anything has changed from the last version to the new version.

As others have said, worse case scenario, the OTA fails to proceed due to errors and you would just have to manually update it yourself, as you could just flash a new boot.img and system.img from google's site (just have to remember anything you added on top of system or custom kernels will of course be reverted, so they will need to be reapplied).

Settings and user apps and such all live in /data , so it should just simply boot up as an upgraded system but with everything else intact (course I always make a backup via my custom recovery just in case).
[Nexus 7 Q&A, Help & Troubleshooting] backslashV:
Thanks, and does backing up thru cwm also back up the build.prop?
[Nexus 7 Q&A, Help & Troubleshooting] kbeezie:
Yes, but not in the way you're thinking. If you back up the whole system, CWM will package each partition up (/system /data , etc), so when you flash a new rom or system on, you can't just selectively restore build.prop since restoring in CWM Would also restore the entire system partition.

You can while in recovery, mount /system and do something like

adb pull /system/build.prop , and save a copy of it on your computer, so you can go back in and change the affected values back if for some reason you needed to.

If you're familiar with ghosting, nandroid backups (what CWM and most others do, minus some variations), are basically exact clones of all the files on each partition. Older recoveries actually took an image snapshot, newer ones basically pack all the files in a compressed archive (With some kind of note of what partition type it was, ext4, etc). The latter can easily be unpacked with tar, or 7zip, etc, but disk images are a different matter.

I can't remember which one CWM does exactly since on my DZ I use 4EXT, and on my Nexus devices I use TWRP.
[Nexus 7 Q&A, Help & Troubleshooting] backslashV:
Thanks, an easier way is to copy the build.prop thru a file manager.

But since I'm on my geek mood today I wanna know if it's possible to extract the backed up (Nandroid) file and find the build.prop somewhere there.
[Nexus 7 Q&A, Help & Troubleshooting] kbeezie:
If it's a backup done with 4EXT or TWRP most certainly since it's just a tarball package (or tar+gzipped if you enabled compression) and can be easily unpacked by tar, or any popular archive utility like 7Zip for windows. (restoration generally just looks at the file info to see what partition type it's supposed to be, formats the partition as such, and then just un-tars the content, with the permissions and such retained).

If it's older where it's an actual jaffs (may have spelled that wrong) disk image, I'm not sure off the top of my head how you would mount it as a disk , and then mount the ext4 or ext3 partition in order to get to it. I would assume ClockworkMod would have upgraded their backup method to the same as TWRP or 4EXT, but it's possible that they didn't for compatibility reasons.
[Nexus 7 Q&A, Help & Troubleshooting] backslashV:
OK, I accidentally clicked on ClockworkMod 2.X in ROM manager app and every time I open the app it says an update is available. Any ways to revert it to previous state?
[Nexus 7 Q&A, Help & Troubleshooting] kbeezie:
Re-do it from Rom Manager with the correct version?
[Nexus 7 Q&A, Help & Troubleshooting] backslashV:
It's not possible since it only has two options: ClockworkMod 2.x and ClockworkMod 3.x.
[Nexus 7 Q&A, Help & Troubleshooting] kbeezie:
Download the correct recovery image for your device and flash it via :

fastboot flash recovery ./nameof-cwm-6-touch-for-grouper.img

perhaps?
[Nexus 7 Q&A, Help & Troubleshooting] backslashV:
That's what I was thinking but there's no other way?
[Nexus 7 Q&A, Help & Troubleshooting] kbeezie:
Unless they or someone else has made a flashable zip, or app that would do the version you want, I can't think of one. The way I see it, the time spent trying to find something that does is the time could have been spent flashing from fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] rouski:
I can't seem to find the answer I'm looking for anywhere so here it goes..

I am mounting a Nexus 7 in my car with a bluetooth head unit to get sound through my speakers. If I make a dock containing pogo pins to charge the device, can I run those pins to my cigarette lighter so the N7 charges will the car is on? I have a 12v to 5v 3A converter on the way if needed. I really don't want to fry my battery and have to start over.

Could this idea cause any problems? Thanks in advance.
[Nexus 7 Q&A, Help & Troubleshooting] player911:
I don't think the pogo pins will charge the device fast enough to keep up with the usage. So if you travel it will slowly deplete. It is a slow charge. People do this though.

You should also look into installing a wireless charger under your battery door so it charges through induction like the Nexus 4. There are videos that walk you through this. Usually they connect the wireless disc up to the pogo pins or to the battery contacts directly.

The N7 will shut off charging once the battery is full, so youd want the power always on through to the cable.

Food for thought. There are numerous threads here in the forums that show people doing this and their findings. I would do the induction charge though for ease of removal and hassle. You can pick up a touchstone charger and disc for probably $20 on eBay. There are specific models to look for and the details would have to be researched.

My buddy did his N7 and he said it was super easy. His only beef was the N7 was too heavy for the included magnets to really keep a secure connection and some people also purchased stronger magnets for under the battery door to fix this. They turned out so strong that the N7 would actually hang simply by the magnets so it kind of "snaps" in place.
[MDA III, XDA III, PDA2k, 9090 General] igadget:
Hi

anyone has any ideia how i can use an external monitor/display and conect it to Qtek 9090 ?

my purpose is to use qtek to display navigational data on a car LCD display/monitor.

thx
[XPERIA X8 Q&A, Help & Troubleshooting] Nahalas:
Hello, i have old xperia X8, with CM7 alpha 1 version. I want something new faster.

I was trying instal http://xdaforums.com/showthread.php?t=1836116

but all time i was failed to check bootloader unlock, when i was trying to check status with *#*#3738423#*#* it just blink and nothing happen, i was trying with my sony and its working i can check status.

Maybe that means my bootloader unlocked? because i have allready instaled rom?
[XPERIA X8 Q&A, Help & Troubleshooting] cascabel:
if your bootloader is unlocked, you would know because you'd have to be the one to do it or paid/asked someone to do it for you. check with s1tool. there's a thread regarding bootloader unlocking.

Just because i don't doesn't mean i can't.
[XPERIA X8 Q&A, Help & Troubleshooting] Nahalas:
thanks for respond i checked with s1tool and there i was reading if code starts With R - means locked, if r unlocked ?

them my was with R.
[XPERIA X8 Q&A, Help & Troubleshooting] cascabel:
correct. your bootloader is locked. if you're planning to unlock it check the date at the back of the phone first.

Just because i don't doesn't mean i can't.
[XPERIA X8 Q&A, Help & Troubleshooting] Nahalas:
This writed under batery ? I checked it my code is 01. if bigger then 29 then problems if i good read ?
[XPERIA X8 Q&A, Help & Troubleshooting] xWhiskey:
If it's higher than 11w29, not trying to unlock is recommended, as the chance of having a hard brick is extremely high. Not saying that it's impossible to unlock after that number, there are several people who did it, but I wouldn't try it unless you think you have nothing to lose. It's very difficult to repair the phone by yourself if a hard brick was to happen this way (you need some technical knowledge to do so).

Several things to keep in mind:

- Do not look for the number on the battery, but on the sticker beneath the battery.

- 11w29 means 2011, week 29, so basically it's possible for you to have 12w25 or something, denoting year 2012, week 25. If you keep an eye on the second number only you would thing unlocking bootloader is safe, but it isn't. It's still well over 11w29.

As for the ROM to install, I already recommended these two in another topic:

2.2 - FroyoPro v2.5

2.3 - GingerDX v031b

Both work very well with custom kernels.
[XPERIA X8 Q&A, Help & Troubleshooting] Nahalas:
Maybe you can recomend anything to instal without bootloader unlock ? or its not impossible ? just put any rom to SD card open with CWM instal and use.
[XPERIA X8 Q&A, Help & Troubleshooting] cascabel:
gongerdx if you want gb. froyobread for froyo. there are other roms for stock kernel, you can try them to see which one suits you.

Just because i don't doesn't mean i can't.
[XPERIA X8 Q&A, Help & Troubleshooting] xWhiskey:
Both of these run well with stock kernel. I run FroyoPro with stock and I'm very satisfied.

For others, I suggest you search the forums a bit or Google them out. There are lots of ROMs to choose from.
[Droid X General] truwrxtacy:
Hey guys i have a Droid X,

stuck onboot loader, i have tried to load the .621 SBF then tried the shadow SBF, both of them goes through all the way till the end and says error switching to BP. I remember fixing it before using .621 file but i cant seem to dig up the guide. can somone point in the right direction? I flash .621 it fails i wipe data/ cache and flash shadow it fails wipe data/cache. boot up and it only goes to boot loader

bootloader .04

thanks
[Droid X General] sd_shadow:
error switching to bp, is usually a driver issue

check my list for driver errors or just use ezSBF 621

sd_shadow's [Collection] of Links for: Droid X (MB810)

DX (MB810) ezSBF & Root 2.3.4/4.5.621

---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------

are you sure it says

bootloader .04 ?

---------- Post added at 09:08 PM ---------- Previous post was at 09:05 PM ----------

should be bootloader 30.04
[Android Q&A, Help & Troubleshooting] kiran2001:
hi guys i found out this site where two customs roms were developed for our andi 4.5h i tested both and working fine check them

http://iballandi45h.blogspot.in/
[Android Q&A, Help & Troubleshooting] ron.gt:
Yup thanks dude for referring my blog... more ROMs will be available soon:laugh:
[Android Q&A, Help & Troubleshooting] kiran2001:
please share all ur roms on facebook group here man..........

please share all ur roms on facebook group here man..........
[Android Q&A, Help & Troubleshooting] ron.gt:
yes thats what i m doing....

frequently check this thread...

http://xdaforums.com/showthread.php?t=2331629
[Android Q&A, Help & Troubleshooting] Jjatinbhardwaj:
Nothing is available

Hay

Nothing is available on this link they are making visits to earn money. when we are opening their blog nothing is there
[Galaxy S 5 General] FinancialWar:
Please post any speculations about the S5 specs.

1080p or 4k display amoled

16 core

Android key lime pie

64gb storage
[Galaxy S 5 General] Jedi2011:
4K resolution screen expandable up to 56" via flexible graphene technology

7.1 surround sound speakers

32 core bigLITTLE CPU

SLI graphics

Direct brain interface for HUD and audio overlay over reality plus telepathic hands free communication and control

Spoiler content hidden.
[Galaxy S 5 General] GalaxyS49505:
Qualcomm snapdragon 16 cores - 2.6Ghz

5.3 Inch Full Hd Display with Gorilla Glass 4

4GB Ram

Baets by Dre (or Eminem) :laugh:

32/64/126GB Memory

16Mp Camera

3800Mah Battery

And most importand Metal Body.
[Galaxy S 5 General] boterkaaseneieren:
Useless, NON meaningful, lousy sh!t thread!
[Galaxy S 5 General] sebas98619:
300 gb internal

69 cores

50 gb ram

A brain

The ability to use the brain

The abiltity to use the brain in a smart way- S smart

Ability to create fire

Ability to fly

Another extra brain
[Galaxy S 5 General] FinancialWar:
why are you trolling my thread?
[Galaxy S 5 General] sebas98619:
Why are u making this thread ?
[Galaxy S 5 General] Skander1998:
Well this thread will probably get locked anyways - BUT.

3 Million Core CPU - 4 of them.

Liquid Nitrogen cooling.

18K Resolution SAMOLED display.

Trillion Cuda cores nvidia titan GPU.

192837 Million mAh Battery.

Yeah , I know this thread is pointless and the specs he even mentioned are ridiculous for now.
[Galaxy S 5 General] FinancialWar:
That's what people said about 1080p and 8 cores on a photo two years ago.
[Galaxy S 5 General] Skander1998:
"FOR NOW" - Read it again ;)

That stuff isn't for 2013 - 2014 bro ;)
[Galaxy S 5 General] FinancialWar:
what do you mean it isn't for 2014? S5 is a 2014 product. Go learn some arithmetic...
[Galaxy S 5 General] Skander1998:
*facepalm* My brain is starting to hurt - I'm talking about the specs and NO, you won't see 16 core CPU's in 2014 - neither this year 2013.

Man you hurt my brain.
[Galaxy S 5 General] FinancialWar:
Since you can't do simple arithmetic, I see why this might hurt your brain cells.

1 cores, 2 cores, 4 cores, 8 cores ....

Applying simple geometric sequence equation a*r^(n-1), where a is the first term, r is the common ratio.

Since a = 1, r = 2, therefore the number of cores in the nth generation phone is 1*2^(n-1) = 2^(n-1)

number of cores in S5 will be

= 2^(5-1) = 16 cores

number of cores in S10 will be

= 2^(10-1) = 512 cores

Did your brain explode?
[Galaxy S 5 General] Skander1998:
Welcome to XDA 2013, where 13 y'old trolls hang around :3

One of the main reasons I don't even bother developing and sharing my work here.

PS: Facepalm at doubling the cores - I owe you 100$ if the S5 comes with 16 CPU cores.
[Galaxy S 5 General] sebas98619:
Not trolling ... why would someone create a thread about next year's product ? We all know this thread is going to get closed ..
[Galaxy S 5 General] chubby65:
This thread pisses me off

It's pointless you should be more concerned about your s4 if you even have one mate :D:D:D
[Galaxy S 5 General] FinancialWar:
why would I want a S4 when I have the Note 2? S5 could be a good candidate to replace my Note 2 but not S4.
[Galaxy S 5 General] chubby65:
No chance
[Galaxy S 5 General] lacordaire:
Plutonium battery
[Galaxy S 5 General] Clark Joseph Kent:
Thread Closed and Cleaned...this thread has ran its course....
[Xperia Z Q&A, Help & Troubleshooting] Gschisi:
What is the difference between Original Android Development and Android Development?
[Xperia Z Q&A, Help & Troubleshooting] ckyy:
Original Android Development = AOSP based rom

Android Development = Stock sony based roms

at least thats what i believe
[Xperia Z Q&A, Help & Troubleshooting] SXUsr:
Original Android Development = Built from Source

Android Development = Anything
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anerik:
Hey guys, i just sim-unlocked my phone, they gave me the unlocking code, i put in another sim card and unlocked it, but it still says bootloader unlock allowed: no!!! why is that? I was so happy until i saw that
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Rempty:
You need to do a SIM UNLOCK via TEST POINT method no via code.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anerik:
damn...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anerik:
Is there any way to do it? I don't mind the testpoint, but any way at all? Wotan says it's 12w11 and before, i don't know any others
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Rempty:
My phone is 11w47 and i sim unlocked via plasmatool.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anerik:
Did you do testpoint? Don't know if it'll work with 12w26
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Rempty:
yes, i do it via test point method.

Try to search on other forums about unlocking via test point method.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anerik:
Yeah, plasmatool is the only one i found that didn't say if it was compatible or not with 12w14+... Do you have user/pass?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Rempty:
No, try to contact with flinston via sonork

http://xdaforums.com/showthread.php?t=2151778
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anerik:
thanks a lot, but plasmastool doesn't seem to work anyways, many users reported it. I guess i'll never be able to unlock my bl... some people said i could email to sony my imei unlock code or smth like that but the tutorial link was down
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] iPusak Gaoq™:
Hmm....SIM lock and Bootloader lock is different my friends....unlocking SIM lock just to make your phone usable with any SIM card while unlocking Bootloader is for development purpose....

all phone will SIM Lock can be unlock easily but for Bootloader lock that depend on the date of your phone is manufacture...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Rempty:
SIM unlocking vía test point method, chnge the bootloader status from no to yes. Before posting plz read a bit.

I think that this thread must be closed.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Goomowiec:
http://unlockbootloader.sonymobile.com/ universal and official method of bootloader unlocking
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Abhinav1997:
Do u really understand why the thread has been made?:rolleyes:

Cheers,

AJ

alokbina is now Abhinav2
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Kordius:
So.. if I unlock SIM lock via test point method I saw bootloader unlock allowed: YES ?

How unlock SIM via test point ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Someguyfromhell:
If we are talking about a Samsung phone, then you are in the wrong section of the forum.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Kordius:
No -.- we talking about Sony Ericsson phone.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] liverkop:
Thank you. brief explanations very carefully
[T-Mobile Samsung Galaxy S 4] Zackg111:
I was wondering if there is any way to flash a international rom and implement the Wifi Calling back in the settings. Want to run wanamlite with Wifi Calling? Is this possible? Perhaps an apk for Wifi Calling. It is a T-Mobile device
[T-Mobile Samsung Galaxy S 4] Skipjacks:
Not yet. Its more than just an apk, which can be easily extracted and installed on any device. It needs a lot of libs to go with it, and those are pretty closed sourced and hard to figure out.

There is a team trying to reverse engineer it to get it working on non stock ROMs. They are doing it for another device but once its done it should in theory work for any device. Last I heard there was a sizable bounty of promised donations if they could get it working, so I'm sure they are motivated.

Many people will tell you this is and will always be impossible. But the WiFi calling app was hacked and made installable for ICS AOSP ROMs. So its been done before. They JB version is apparently tougher, but the software that couldn't be hack has yet to be developed yet as far as I am aware. Its jus a matter of if XDA's devas are smarter than T Mobile's devs

Sent from your phone. You should be careful where you leave that thing.