yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] reluttr:
Nyandroid?

Also if I am not mistaken... you have to have the bootanimation.zip file, as it contains the animation in png image format.

http://www.addictivetips.com/mobile/how-to-change-customize-create-android-boot-animation-guide/

If you have Photoshop I am sure you could easily convert the video into still images and make your own bootanimation.zip.
[Asus Transformer TF700] Svashtar:
Does anyone know what is the biggest size that boot animation can be?

Or to ask differently: how to make a bootanimation for infinity to cover the entire screen?

I have tried many for the last couple of hours, but they all look weird if they are "fullscreen" as the size of the animation becomes smaller on infinity. Only those who are centered and have black background looks somehow OK.

I would like to resize the fullscreen ones so they would cover the entire screen.

Possbile?
[Asus Transformer TF700] JMH-ESH:
Can you change the boot animation without rooting the device?

If so, could someone please give some detailed instructions on how to do it? A link to a video of it would be nice too if there's one out there.
[Asus Transformer TF700] Jbb3393:
If I'm not mistaken the video with android in space is their "Easter egg"

Try this: go to about tablet and click multiple times very fast on the android version.

It should pop up a little android guy

Next tap and hold on him till he grows huge then be prepared to have your mind blown :D

Sent from my ASUS Transformer Pad TF700T using Xparent Blue Tapatalk 2
[Asus Transformer TF700] Svashtar:
You can't change boot animation without root. Bootanimation zip file is in folder system/media and is only readable without root.

At least I don't know of any solution that works without root, but could be mistaken....

Has anyone figured out what size should bootanimation be to fill the whole screen?
[Asus Transformer TF700] AspenMan:
Very Cool!
[Asus Transformer TF700] urrlyx:
I cropped the images and then doubled the size of the default animation. I'm on eoh's rom and the file was named bootanimation_04.zip. Not sure if that is stock or if he modified it, but it's easy enough to just rename it or change the config file if yours is different.

Infinity stock animation large

edit: actually I think I can keep the same original size cropped and then change the resolution in the desc file so that the zip isn't quite so large. will do that and re-upload if it works.

edit2: while just changing the resolution specified in the desc.txt file did increase the size of the animation, it also created a box of flashing pixels around it 1 or 2 pixels wide. I played with a few different resolutions but specifying anything other than that of the images caused the pixel artifacts on the screen. I re-uploaded the double-size animation if anyone wants it and will be putting up a couple more that I downloaded through roomtoolbox in a bit.
[Asus Transformer TF700] urrlyx:
Rotated and compressed a bit from the original:

Bokehloop
[Asus Transformer TF700] urrlyx:
Cropped the blue 3d honeycomb animation, scaled that up, and changed contrast to make the background black. It's 960x700 and looks pretty good on our screen.

Blue 3d Honeycomb
[Asus Transformer TF700] andyk11:
Can you tell me what folder the original boot animation is in and what file to modify to change it please?
[Asus Transformer TF700] redheadplantguy:
What did you change config text file to? I can't get my animation changed. Tried data/local, and system/media. Neither worked
[Asus Transformer TF700] blackmambazzz:
I have tried editing that file and it gave me a bootloop

If I change the animation in the stockrom it doesnt boot anymore but with cm10 an cleanrom it works (with romtoolbox)

The config file sets the path and name of the bootanimation I think but editing doesnt work :(
[Asus Transformer TF700] urrlyx:
You have to be careful when editing the pointer file. There cannot be any extra lines or spaces after the path text.

I've also had issues with some editors and just doing a save when you close out of the editor instead of saving beforehand. Not sure why there would be a difference in how it performs the save, but I was able to repeat the issue so I'm pretty sure it wasn't a fluke.

Also, most of the time, if the system can't play or can't find the animation it will still boot up just fine. It will look like its just sitting at the ASUS splash screen until it displays the launcher, so if you didn't wait long enough you may have thought it wasn't booting.
[Asus Transformer TF700] redheadplantguy:
What do I changed pointer file to? The "boot animation changer " app works, but only on the ones in the app. I have some I want to use, but can't get to load. After splash screen, it just says generic "Android "
[Asus Transformer TF700] bwcool55:
Bootanimation

Hi all I created my own boot animation and I had to change the in the desc.txt file here is what I used to get the image to use the whole screen.

1922 1202 30

It works for my TF700t so It should work for you as well.

I would like to know if anyone has figured out how to get the sound for boot animations working for this device.

Thanks to all.
[Asus Transformer TF700] Nurikos:
Im use Boot Animations from Market, it's work

Just select "Local" point to the bootanimation.zip on your sd card
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] adrian@alien:
Previously i have been using SGS but recently just bought a new SGN but had problem rooting this phone.

I have successfully turned this into a brick (a soft one). I find that rooting a SGS is a breeze but not the SGN.

I have been following this thread in XDA http://xdaforums.com/showthread.php?t=1329360

, by dr ketan. Is this gonna work on a DXLP9 stocked version?

I am not sure whether i have missed out some steps in between.

Let's say i have another brand new SGN now, is anybody out here willing to give me a step by step guide on rooting and unrooting?

Thank you!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] arungupta1985:
For step by step procedure

Follow this thread

http://xdaforums.com/showthread.php?t=1763151

Step 1 to 16
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
What is the current situation now?

Does the phone boot into recovery / download?

Where does the phone stop while rebooting?

Did you flash a stock ROM after your phone bricked?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Diveraz:
I, too, soft bricked my GNote recently while trying to flash custom ICS ROMs. Realised that I missed, or misread a step that caused the soft brick. All that was needed was to reflash using a PC Odin and the GNote was back in business ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jonpaslim:
I use lp9 before and i root it by using that method. Put the CWM zip in the external sd and also the rooting zip. Go to stock recovery and there is update zip ext sd there use it to flash CWM zip, after this it will become touch CWM recovery, use your finger and flash the rooting zip.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Russc73:
i'm in a similar position. After an unsuccessful flashing attempt ny note is stuck at the boot screen. I've spent hours reading and attempting to get it working again but i'm now at a dead end. If i follow the Dr Ketan method to flash back to stock GB through ODIN etc, it all goes well but the note doesnt boot beyond the initial galaxy note splash screen.

when trying a stock ics rom, again the process goes through with no problem but the phone doesn't boot (this time one step further) beyond the Samsung logo/jingle.

i've tried wiping/removing batteries etc after the stock rom install but can't seem to get it on it's feet. Does anyone have any ideas of soemthing i can try?.

If it's bricked due to the emmc bug is there some way i can determine this for sure?. does anyone know how much samsung will charge to sort it out?. My custom binary count is 4 now so i'm assuming i can't blag a warranty repair?

please help!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
If nothing works, try the repartition method on this thread's 12th post by forest http://xdaforums.com/showthread.php?t=1661590 If any sector has gone bad, recreating a partition will throw up an error.

To reset the binary counter, there is this angelom kernel. Along with the angelom kernel, keep a stock kernel handy.

Flash angelom kernel first.

Once done, reboot into angelom's recovery.

Do not do anything else.

Reboot again to download mode and check the binary counter.

If its not reset, again boot into recovery.

Reboot into download to check the counter.

Once reset, flash a stock kernel.

Do not stay on angelom kernel. In its time it was known to cause hard bricks.

You should now be able to claim warranty : )
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] adrian@alien:
Warranty Claim

I reset the triangle and the flash counter via a USB jig using this method and successfully got a warranty claim from Samsung, the stock Rom now is DXLR2.

http://xdaforums.com/showthread.php?t=1354888

Now i have to figure out how to do rooting again.

Please no more mistakes this time.
[Galaxy S III Q&A, Help & Troubleshooting] shaggydabbydo:
Since importing my contacts from Google, I have 500+ "Not assigned" (to groups) contacts.

When looking at other groups, I can "Remove Member" and tick multiple members, but I cannot seem to do this with the "Not assigned" group.

Any idea how I can remove them without having to do each one individually?
[Galaxy S III Q&A, Help & Troubleshooting] anthropolyte:
Why not block-add them to a new group first, and then remove them from there?
[Asus Transformer TF700] Svashtar:
Hi,

I am new to tablets so maybe I am shooting in the complete darkness...

Why isn't it possible to reboot TF700?

Even with root (Tasker) the reboot action is disabled.

Is that related to kernel or something else?

Is it achievable without new custom ROM?

Thanks!
[Asus Transformer TF700] MartyHulskemper:
If you are rooted you can. In that case, you can try RebootMenu from the Play Store (and in there are several more options to choose from as there are more apps that perform this particular trick).

EDIT: just search for "reboor widget" in the play store, and the one you find from fadroid is prety nice as well. Used it before (as many of the others).
[Asus Transformer TF700] Svashtar:
Hi,

thanks for the tip.

Is there a way to have a reboot options inside the menu when the power button is long pressed?

I think this is cyanogen way, but i am not sure...
[Asus Transformer TF700] MartyHulskemper:
Not that I've found so far -- I know what you mean, as my SGS2 does that when long-pressing the power button. This would be something a custom ROM might be able to provide.
[Asus Transformer TF700] KilerG:
I know on my Bionic I hate going back to stock because I miss that reboot button.
[Asus Transformer TF700] Svashtar:
Found a great solution!

Download: Elixir2

Create: status bar widget (or home screen) with reboot toggle.

It show menu with reboot, recovery etc.

Not exactly same thing as with power button (where i also like the fact that it all looks native ICS), but still a very nice solution. :cyclops:
[Asus Transformer TF700] KilerG:
I can't wait to get CM10 running on this thing lol. It looked great for the early stages on the Prime.
[Asus Transformer TF700] d14b0ll0s:
I just open

Terminal

Emulator and enter the "reboot" command, but then again I sometimes have "values not saved" or sth like that from No-frills CPU (which is actually bogus, as there was nothing to save, it still has the same things to load - governor & scheduler, doesn't reset the settings or anything, so probably some precaution measures in the code)
[Asus Transformer TF700] KilerG:
Not quite as nice as hitting a button to do it lol. I think that turning off the device then turning back on might be faster than finding terminal emulator. I'm sure that's similar to what the actual widgets and such do.
[Asus Transformer TF700] d14b0ll0s:
Depends on the point of view ;> I find using the term fun. And it's always on my main screen, so no problems finding it really!
[Asus Transformer TF700] Svashtar:
Yeah, me too, CM10 is going to kick ass to my Infinity as soon as its available :)

But, I think more important right now is to unlock the bootloader - as soon as possible :) - we just have to wait for Asus on this one, which sucks a bit. How long did it take for Prime and other transformer line products to receive an unlocker?
[Asus Transformer TF700] d14b0ll0s:
TF300 got it very quickly (less than a month since original release I think)
[Asus Transformer TF700] MartyHulskemper:
Ughhhhh... damn -- how long can "a little less than a month" feel? ;)
[Asus Transformer TF700] d14b0ll0s:
It can be Infinity, I guess.
[Asus Transformer TF700] tpmullan:
Someone try and find an exploit based on the prime's unlock, but waiting is so much easier
[Asus Transformer TF700] EndlessDissent:
Not sure about the Prime, but my TF300 got unlocked about a month to a month and a half after release. I think it was released at the end of April (in the US), and the unlocker was released either in the middle of May or the end of that month. It was a long wait even though it actually wasn't that much time.

Not possible. Devs have been trying to crack the Asus unlocker app for months. Asus' encryption is RSA-2,048 (that means the key is 2,048 bits long), which is almost completely unbreakable without a supercomputer to perform a ton of calculations. Even the NSA can't crack it efficiently.

For example (I researched RSA-2048 as I wrote this post), the most complex RSA encryption to be cracked thus far is RSA-768. The team that cracked it estimated that a 2.2GHz AMD Opteron with 2GB of RAM would need 1,500 YEARS to do the math required to break RSA-768 encryption.

Can you imagine how long it would take to break encryption that's almost 3 times stronger than that? Unless someone can come up with an insane algorithm to factor 2,048 bit numbers or you know a developer with a supercomputer laying around, no one's about to crack Asus' bootloader any time soon.

Edit: I should have paid more attention to the article. The team of crackers estimate that the desktop I referenced earlier would take "4,294,967,296 x 1.5 million years" to crack RSA-2,048 encryption. As terrible as a 2.2GHz Opteron is these days, I wouldn't expect much better from a top-of-the-line modern computer.
[Asus Transformer TF700] d14b0ll0s:
I don't think we have that much time, even with the Infinity.
[Asus Transformer TF700] MartyHulskemper:
No, even with a crapload of vitamins and healthy living to the max I won't make it that far (neither would I wish to). Oh, well, a month's waiting isn't that bleak when seen in this bit of context. ;)
[Asus Transformer TF700] Keion:
I don't know if this applies to the infinity but there are other ways of cracking this stuff. For my evo 3d, the boot loader unlock method involved intentionally bricking the device to access a hidden sort of mode where the partitions could be rewritten. If I remember correctly, that bootloader was also encrypted.

Sent from my 3d porn machine.
[Asus Transformer TF700] Jotokun:
Failing that, if we got root we could probably try the 2nd init trick used on locked down Motorola phones, where immediately after the bootloader loads a rooted Asus firmware, the trick unloads everything but the kernel and starts loading your custom rom. The only flaw with the approach is you're still locked into using Asus's kernel, but otherwise you're free.

That said, with an official unlock I cant imagine there'd be a ton of demand or developer interest in such a solution.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).

I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
[G2 and Desire Z Q&A, Help & Troubleshooting] wileykat:
"Mount" data to flash a rom? You sure? Looking at the link you provided just says place on sd, wipe, flash. Where exactly are you stuck or am i just missing the obvious.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
The /data corruption occurred halfway through the upgrade process. I'm not sure what to do, so I stopped and asked for advice. I kept going the last time I had a problem, and got a bricked phone for my trouble.
[G2 and Desire Z Q&A, Help & Troubleshooting] kbeezie:
The only "data" I see in that guide (Same one I used in fact), is the comment bout doing a "Factory Reset/Wipe Data" which is what it says, says nothing about /data/ partition, just to do a full wipe.

Naturally you do this from recovery, not from within an app or while the phone is still booted into normal usage.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
So, wiping the phone will fix everything? And then install cyanogen? Sorry, just want to be totally completely sure.
[G2 and Desire Z Q&A, Help & Troubleshooting] wileykat:
Aye, indeeed, as KB said, full wipe, then flash new rom.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
[G2 and Desire Z Q&A, Help & Troubleshooting] kbeezie:
Factory Reset/Wipe will only clear the internal partitions ( /system /data /cache ) , and additionally if you choose Dalvik Cache, then that as well is usually good to do with a brand new rom.

It will not wipe your radio, hboot, recovery, etc, just the system-related areas for roms.

Generally speaking:

Factory Reset + Wipe Cache/Dalvik Cache

Flash CyanogenMod

Flash the Google Apps Zip specific to that CM version (as CM doesn't come with Google Apps by default)

Reboot

Just remember that doing a backup before doing anything to your phone like above is available, as a factory reset and such will wipe contacts and settings and so forth unless you got a google account setup to restore them (or using something like Titanium Backup on an already rooted phone).
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless? After I wipe the device I won't be able to perform the rooting steps again...and will likely have a brick...just totally paranoid here.
[G2 and Desire Z Q&A, Help & Troubleshooting] kbeezie:
I followed that one as well. And I assume you rebooted after that point.

Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?

Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).

If you already flashed CM and can't do su via adb then it's possible that under "Security" or "Development" in your phones system memory that su is restricted to "app only" and you may need to change that to "app and adb".

You shouldn't be running su from /sdcard (since that's not a linux style partition, and /sdcard is a no exec area). The su binary should already be installed to system in CM.

Clarification If you did not yet reboot (i.e.: Step #7 and onward), and then wipe/flash cyanogenmod (or another pre-rooted custom rom), then proceed with the steps, otherwise you're just working with a half-processed phone and naturally nothing would work in that state.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
Yes.

You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.

I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:

adb push su /sdcard/

adb push Superuser.apk /sdcard/

I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
[G2 and Desire Z Q&A, Help & Troubleshooting] kbeezie:
Don't use Visionary unless for some strange reason your phone came with Froyo (2.2) on it (it's an outdated method, and has a high brick rate). Given that you may have an asian rom etc, I would just go ahead and do a factory reset /wipe via recovery, and flash CM7 or a pre-rooted stock rom found here on the XDA forum for the best result.

I think even one of the AOKP or Adromudus comes with Pinyin input support already if you need it.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.

I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
[G2 and Desire Z Q&A, Help & Troubleshooting] kbeezie:
Rooting is at the rom/kernel level. But in order to flash a new custom kernel would need an unlocked bootloader which you already did with S-OFF.

So you would either flash a pre rooted rom like almost everything available via the developer section here (via recovery not hboot) or a stock rom then root that.

If you do everything via recovery you are less likely to accidentally lock/unroot the phone since recovery normally deals with the rom/kernel /cache and not hboot.

Sent from my T-Mobile G2
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
[G2 and Desire Z Q&A, Help & Troubleshooting] kbeezie:
If I had to make a guess, I would probably say you flashed Cyanogenmod onto the phone WITHOUT first doing a factory-reset/wipe, in which case you probably broke it (hence the language and freezing) by merging cyanogenmod on top of the pre-existing rom.
[G2 and Desire Z Q&A, Help & Troubleshooting] gromky:
No, I definitely wiped the phone first. I got a few lockups in cyanogen so I went to install another rom. Now I'm getting "E:error in /cache/recovery/log" and "E:can't open /cache/recovery/log". When I install a new rom, it won't take and boots into cyanogen. It was in a reboot loop for a while but now it has booted into cyanogen again. Sigh. This is what I was afraid of. :(