yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] thephantom:
How did you install? Ota or manual flashing? I had that issue when I first went to stock with the n7. A simple factory reset solved it
[Nexus 7 Q&A, Help & Troubleshooting] player911:
Yea I'd say that it probably just needs a factory reset to clear unneeded files. I find it good practice to clean up my SD storage occasionally too. Between old backups and app data, you can usually free up lots of wasted space.
[Nexus 7 Q&A, Help & Troubleshooting] lsharp1226:
Recently updated to 4.2 (yay!), and like it so far. I'd like to set up an account for my granddaughter (yup, I'm old). I've got the account set up (no Google Play account made), but when I went to add applications (that I've paid for under my account) the apps aren't on the device.

Any clue how I can use my account (and apps) on her login? As always, all help is greatly appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] pankomputerek:
I guess we can can it work in progress Multi-User. There is no way to share paid apps between accounts for piracy reasons. Until they find a walk-around and possibly limit number of users who can be assigned or some sort of "special" offer for multiple-users you will have to re-buy apps. :(
[Nexus 7 Q&A, Help & Troubleshooting] akakitsu:
One way to do it is to login with your account on the guest user, download the apps you want and then remove your account. The apps should still be available to the guest user, unless an app does a market check to see if it's bought by the guest.

This is in theory, I haven't tried it yet.
[Samsung Epic 4G Touch] acejoker25000:
http://phandroid.com/2012/11/13/android-4-2-jelly-bean-aosp/

I'm curious how the new toggles in 4.2 will be handled in cm10 and aokp after the source code has been added to each rom.

私は神の罰です。
[Samsung Epic 4G Touch] im0rtalz:
Android 4.2 is getting the OTA treatment from the powers that be. We eagerly await the source to hit the AOSP repos. When it does, we will begin the task of defining what is new, what has changed, and what CM features should stay (or go). We already anticipate removing the CM enhancements to the Clock app (Google made their own), and enhancing the Quick Settings (most likely not porting over the Notification Power Widgets). However, these assessments are preliminary, and won't be finalized until MR1, or whatever tag is used, has the source to go with it.

Edit: Oh and yes, before its asked, 4.2 will be CM 10.1 (not CM11).

just wait and see
[Samsung Epic 4G Touch] F3L1XZS:
Like the person above me said, they'll get rid of a lot of stuff that is now useless since it's baked into Android. Obviously something built by the Android team and baked into Android has lees possibility of crashing or making issues in the future than if it was put on top of Android like we're doing right now for notification power widgets.

Regardless of how it goes, I can't wait for Sbrissen to release 4.2 AOSP, and then development will take off from there.

*crosses fingers*
[Samsung Epic 4G Touch] evo3d6:
Man I can't wait hope all goes well!
[Samsung Epic 4G Touch] asd87:
I've grown to love the quick reply from CM. Sbrissen is a monster tho and definitely check out his AOSP build of 4.2 :D
[Samsung Epic 4G Touch] F3L1XZS:
Wait, what? Don't you mean 4.1?
[Samsung Epic 4G Touch] moparfreak426:
Really all I've seen significant is the 4.2 camera which I have along with all the 4.2 gapps on my 4.1.2 king kang build
[Samsung Epic 4G Touch] themisterwilson:
Well i think that 4.2 has quick settings in the pulldown, lockscreen widgets built in, and not really sure what else, something about group MMS in the messaging app. Go check out the gNex Dev forums and the stock 4.2 ROMs.

I'm not suggesting you flash them, but you can still read about the features.
[Samsung Epic 4G Touch] byrdcfmma:
I hear you, But...

I think that since we have all seen 90% of what JB can do on our phones on these custom roms, the upgrades dont seem like much to us. There is a much larger audience out there than us and that is who they are trying to WOW. They just use us to help figure out what mistakes they are making:p
[Samsung Epic 4G Touch] Croathlete:
Also system wide font tweaks...
[Galaxy S III Q&A, Help & Troubleshooting] mox123:
how can the boot animation be changed in this rom? it works on omega rom by moving the bootanimation.zip to system/media or data/local

but IT DOES NOT WORK ON ANDROID REVOLUTION HD 14.0 with perseus kernel! ??

and how can i make the status bar at the top black instead of dark grey ??
[Galaxy S III Q&A, Help & Troubleshooting] da_jojo:
-first get totalcommander and root

-delete all bootanimation.zip from your phone mem

-delete system/media/audio/ui/camerashutter sound and poweron.ogg sound

-delete system/media/bootsamsung.qmg and bootsamsungloop.qmg

-put bootanim.zip in system/media and sound in system/media/audio/ui

- goto forumpost http://xdaforums.com/showpost.php?p=31833122 and in recovery install zip enable bootanim

-reboot

works on stock and not so stock (int. or whatever rom) 4.1.1 and 4.1.2
[HTC One X+] hardstuffmuc:
Hi there,

I may be blind but I just cannot find the settings for the backlight...it was working before but the last couple of hours they don't light up anymore...even in dim conditions.

Is there anyone to point me into the right direction? I tried the search...but only solutions for rooted devices..which my HOX+ is not ...yet!

Thank you in advance
[HTC One X+] serafinmarius:
Hy

Sorry but there is no settings for the backlight. Only root .....

But try puting your Finger over the light Sensor ( on the other side from front cam ) and it wil go on , it Not then you have a Hardware Problem

Cheers :thumbup:
[HTC One X+] hardstuffmuc:
Thanks mate, they do light up then..but as it is already evening here i have only dim light conditions but they do not light up by themselves weird

I only got the fone this afternoon.. so still getting used to it as it is a bit different from my rooted HOX...
[HTC One X+] serafinmarius:
Yup ... Mine is just like yours , but is Not that bad, i got use to it .... And if the Sun is lightning the lds go on aswell , and if is realy dark .

Cheers :)
[Atrix 4G Q&A, Help & Troubleshooting] chepe263:
I bought a motorola ATRIX 4G, it came by mail yesterday. It has a lot of things from AT&T i don't like because I don't live in the US and some options are blocked (can't switch to 2G or enable tethering).

Is there a way to get a retail android system for my atrix? Where do i get the stock rom? How to flashed?

I'm a "noob" in android ^^¡
[Atrix 4G Q&A, Help & Troubleshooting] ravilov:
That IS the stock ROM. Stock ROMs for the Atrix 4G come with AT&T stuff and various limitations.

You can easily cure n00bness by reading and learning. I suggest you start with the n00b guide thread in the General section.
[LG Optimus 2x] chiprian:
Hi, All

My first post and I need your help. My phone needs to go to a service and I need to put in the "stock" condition - no root, no custom recovery and etc.

Can I do it with smartflash? If yes, can somebody give me a link to the latest stock GB firmware - Euro open. The link here is brocken - http://xdaforums.com/showthread.php?t=1035041

Or if there is another easyest way, I'll apriciate your help.
[LG Optimus 2x] SLS197:
Restoring Stock

Hi,

Have you tride this:

http://xdaforums.com/showthread.php?t=1264289&highlight=kdz+recovery

I did it this way:

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

You can find the links for the kdz files provided by Homero here:

http://www.todomovillg.es/elforodehomero/index.php?topic=317.0
[LG Optimus 2x] vanmarek:
The link is working just fine...
[LG Optimus 2x] chiprian:
Thank you both!

I'll try either way.

For the Euro open link it constantly says:

No Downloadserver. Please try again later!
[LG Optimus 2x] mickru:
Are you from Germany? I found this to be very helpful. Its a collection of howtos for everything you possibly want to do with the P990:

http://www.handy-faq.de/forum/lg_op...ptimus_speed_p990_alle_anleitungen_blick.html
[LG Optimus 2x] chiprian:
Hi, mickru!

I'm not german, but the link helped a lott! I''ll smartflash in a while!

10x, again!
[LG Optimus 2x] Dnst:
If you need another guide, check this one:

http://androidadvices.com/lg-optimus-2x-p990-install-stock-rom-tutorial/
[myTouch 3G, Magic General] GammaPaladin:
Every time I want to update my phone I run into this, there are instructions for 32A and 32B, but nothing about whether a given ROM is specifically compatible with the 1.2/Fender MyTouch, which I'm given to understand has its own quirks. ROM threads will have Radio/SPL requirements for 32A and 32B, but not for the 1.2

It would be nice if we could get a sticky with info specific for the 1.2/Fenders, like what Radio/SPL is a good choice, which ROMs are known to work with it, and so on.
[myTouch 3G, Magic General] tvall:
The rule I follow:

Use 32b roms, that's it.

On roms that have autokernel, you don't have to do anything at all. it'll just work. On roms without this feature, you need to make sure you flash the right kernel.
[HTC One S] Deleted member 3452239:
This is why it is easier on evita.. http://db.tt/kCeCpDAE

I made a version for you guys.. http://db.tt/ar4sbw6V

Place on your sdcard

open terminal emulator

$ su
# dd if=/sdcard/mmcblk0p23 of=/dev/block/mmcblk0p23

reboot to fastboot and lock your bootloader. And then run the RUU

You can download the edited version. USE WITH CAUTION
[HTC One S] dc211:
Just finished downgrading from 1.14 to 1.06.

I started with Jet and replaced the bakp4 after it was created with my own and replaced the hboot with the 1.06 version for the One S. Jet got stuck and kept giving me "Failed to flash hboot" so I jumped over to the manual instructions and finished it that way.

Thanks mikeyinid for bringing to my attention that we can do this and being the first guy to try it with the One S. Thanks absolutelygrim for all your hard work and instructions.
[HTC One S] Deleted member 3452239:
Jet has a few bugs right now, some users have reported it working, I haven't gotten it to work for me. Failed at flashing hboot, manual method has always saved them :)
[HTC One S] Behold_this:
Nice work! This should be on the dev forum. Please request a moderator move it there where those in need have a better chance to find it.
[HTC One S] mikeyinid:
You should mention that Linux is needed earlier on in the OP so people don't brick then realize they can't unbrick cus they don't have Linux. People won't read the whole thing before they jump in.
[HTC One S] Rampage:
And maybe sticked.

Send from a phone.
[HTC One S] sherry478:
which hboot does this downgrade to? i am currently on 1.14.001 can mine be downgraded?
[HTC One S] Deleted member 3452239:
It downgrades you to 1.06
[HTC One S] mikeyinid:
Yes it can. I downgraded mine from 1.14 to 1.06.
[HTC One S] Darknites:
How easy is this to do if you never used linux? and also can it be done in Virtualbox?
[HTC One S] Deleted member 3452239:
Yes and no. LiveCd or install only
[HTC One S] Darknites:
Thanks, I see if I got the balls to do it tomorrow lol.
[HTC One S] mikeyinid:
Follow grims instructions and it's simple, for anyone
[HTC One S] Darknites:
Ya it does seem easy but I never used Linux before and the idea of bricking it to do it just sounds wrong to me lol but the idea of having to use an app or fastboot in till my next phone is no fun lol.

Will I need to download anything other then whats in the OP to go with the linux install?
[HTC One S] Deleted member 3452239:
Nope.. Should work right off a clean install
[HTC One S] Darknites:
Thanks again I get everything sorted tonight to try tomorrow.
[HTC One S] diabolusmiles:
Linux running off a usb stick will work right? Think I got puppy linux sitting around my room somewhere.
[HTC One S] Deleted member 3452239:
Haven't tried it on puppy.. I prefer using debian based versions
[HTC One S] mikeyinid:
I haven't tried yet, but downgrading hboot like this, does it mean we can run the old ruu?
[HTC One S] :
Most people don't want to buy/pay for something like that
[HTC One S] topnomi:
Successfully downgraded another one s with this tutorial. no issues whatsoever!

Thanks again!
[HTC One S] gszabi:
I know but it can be useful for developers.
[HTC One S] misko903:
failed

In Step 9:

it has rebooted several times, writed several times, but after cca 10 minutes comes this:

Waiting device /dev/sdb12.......

Found device!

FATAL: Failed to open /dev/sdb12

than i was following the next steps, failded again in the last step - restoring from the backup.

what i should do? i need the phone :)

thanks a lot, guys!

[EDIT]

repeated the steps, worked second time

done with Ubuntu 12.10 x64 running on VMWare 9.0.1
[HTC One S] Zarboz:
So i have done this on my new one s

now when i flash my unlock_token it just stays "relocked" on bootloader after doing RUU
[HTC One S] :
Enable usb debugging and try

Fastboot erase cache

And try again

Sent from my HTC One X-
[HTC One S] Zarboz:
i just switched machines will try this next

switching comps seemed to do the trick

that was odd
[HTC One S] lonoguge:
Need help! I'm stuck at the 2nd command when I have to kill the phone via the emulator!! It says cannot open for read: no such file or directory
[HTC One S] Darknites:
Think you put the wrong path to the file by the looks of it.

Edit, Is there any real need to run a RUU? because I not done that and everything has been working fine.
[HTC One S] lonoguge:
ok thanks, this is too damn confusing lol

So what you're saying is that I can start from the enumurating step even if the killing of the phone failed?
[HTC One S] Darknites:
Just need to make sure you know where the kill file is and try again. and if that don't work post a screenshot of it.
[HTC One S] lonoguge:
Thank you for all the help man, I got past the killing phone issue my next question is what is meant by spam in the terminal?
[HTC One S] Darknites:
Np, after hitting enter press the up key and enter again and keep doing that in till it works.
[HTC One S] lonoguge:
After spamming using the following code: /dev/sd*

this is what I kept getting, it's the only code that had 5 segments per line , am I on the right track?

I have a tmobile htc one s from the U.S if that helps

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*

/dev/sda /dev/sda2 /dev/sdb /dev/sdc /dev/sde

/dev/sda1 /dev/sda3 /dev/sdb1 /dev/sdd /dev/sdf

lonoguge@ubuntu:~/Desktop/ville$ ls /dev/sd*
[HTC One S] dc211:
Your on the right track, if you get stuck anywhere just restart that step. In this case restart step 3

So you need to restart the phone and spam the command. You missed the window to get the desired result. Just try again.
[HTC One S] lonoguge:
Thank you! I had no clue that was what i needed to do, you've saved me from potentially hours of useless clicking
[HTC One S] dc211:
No problem, did you make it all the way through the guide?
[HTC One S] lonoguge:
no I I'm on step 9 and actually flashing the hboot in 24K segmants which is taking forever but I'm not complaining lol

Edit: Finally finished downgrading!! :D I could have sworn I would be bricked by the end of the day haha

So do I need to update the Ruu? In all honesty I don't know which one I currently have but all I'm going to flash viper rom and see if the wifi and data speeds are fixed and then I'l flash a radio zip file
[HTC One S] c_shekhar:
May be it appears a noob question. Why at all do we need to downgrade the hboot to 1.06?
[HTC One S] dc211:
There isn't a huge reason to do it anymore since Flash GUI came out. It mostly just removes the need for an extra step when flashing a rom, or if you want to flash a different radio then the one you're using if you're not using a CM based rom.
[HTC One S] Sneakyghost:
Well it is quite interesting for the experimental stuff. For the average user, there is little need apart from the mentioned kernel flashing.

Sent from a phone.
[HTC One S] andryyyy:
Hi,

first I tried an 64bit Ubuntu 12.10, patched. It never worked that emmc_recover resets the phone itself. So I changed to a live USB 12.04.1 Ubuntu 32bit, no manual reset was needed. :)

Everything worked!

Thank you!
[HTC One S] Ergo Proxy:
If I do something wrong then what's the worst thing that can happen to my phone?
[HTC One S] dc211:
After step 2 there isn't really too much you can do that is worse then that.
[HTC One S] blackcell1:
im getting the same problem. anyone know why ?

my hboot is 1.14.0002,

after locking my bootloader, and running the ruu, it returns with the 155, i can rollback down 2.21.401.10 but not down to any lower.
[HTC One S] dc211:
You can use the all in one tool kit and hit the Main Version Error Fix button and it should fix the problem I think you are having.
[HTC One S] blackcell1:
no joy :( the steps i took

pushed mmcblk0p23

ran error fix tool on the tool kit

fastboot oem lock

then ran the ruu and it still returns the 155 error
[HTC One S] Sneakyghost:
Well with that hboot you can only flash a RUU with equal or higher hboot and it also needs to fit the CID. You cannot go below your current hboot.

Also, changing the CID often results in an error. Only SuperCID can flash all carrier RUU's but still not lower than your current hboot.

Sent from a phone.
[HTC One S] blackcell1:
So method 1 is my only option ?
[HTC One S] devgee:
Worked perfectly

I had to manually reboot my device during the hboot recovery and also had small problems with the last step!

But hey, it worked!

Hundreds thanks mate for sharing this!
[HTC One S] :
What is your cid and what error does the ruu say other than 155

Sent from my HTC One X-
[HTC One S] dc211:
I'm pretty sure he hasn't downgraded his hboot. He was trying to downgrade by tricking the RUU with the version number.
[HTC One S] :
Yea.. you need an hboot equal to or older than the version you want to ruu downgrade..

Like I can run the 1.85 ruu on the 1.09 hboot or 1.01 hboot, but not 1.11 or 1.14

Sent from my HTC One X-
[HTC One S] blackcell1:
to both questions, my boot is 1.14, and my cid is htc_0001
[HTC One S] Inferi0r:
Is there a change this method will work on Windows one day?
[HTC One S] blackcell1:
no. Linux is the only operating system you can use to unbrick, unless you have a riff box
[HTC One S] blackcell1:
i didnt fancy using method one (because everything i touch gets bricked :D)

but it worked a treat and im now running 1.06 :) thanks for your tutorial
[HTC One S] Inferi0r:
Me too, everything worked well, i'm on newest radio now.
[HTC One S] andryyyy:
Made a little script to "enumerate" the partitions.

It checks for a phone in QDL mode, asks you to push power-button, tells you when to release it and then - after a reset - shows the right device to use.

Was a bit bored at work and used it later .. maybe I will improve it to do the whole process (except of the emmc_recover part, for sure).

Thought I could share it here ...

#!/bin/bash

devices="/dev/sda12
/dev/sdb12
/dev/sdc12
/dev/sdd12
/dev/sde12
/dev/sdf12
/dev/sdg12"

clear

echo "Looking for a phone in QDL mode..."
lsusb | grep -i QDL >>/dev/null
if [ $? -ne 0 ] ; then
echo -e "\e[00;31mNo device found! Exiting...\e[00m"
exit 1
fi

echo -e "\e[00;32mFound! Going on...\e[00m"
echo
echo "Hold down power-button until it says \"Release power-button\""
echo

while [ $? -ne 1 ] ; do
lsusb | grep -i QDL >>/dev/null
done

clear

echo -e "\e[00;31mRelease power-button!\e[00m"
echo
echo "Waiting for the device to come back, please wait..."

while true; do
for device in $devices
do
if [ -e "$device" ]
then
device=${device%?}
clear
echo -e "\e[00;32mFound device at ${device%?}\e[00m";
exit 0
fi
done
sleep 0.2
done

(or attachment)

Download/Paste, chmod +x filename.sh and ./filename.sh :P
[HTC One S] 1aladdin1:
great job, grim.

successfully went back to hboot 1.06 using your tutorial.

perhaps you should add an info at step 9 that the flashing process probably interrupts many times requiring you to press the power button many times.
[HTC One S] :
It's already there.. it says you can reset if your phone doesn't kick out of qdl mode and continue writing
[HTC One S] beyored:
i downloaded terminal did the commands rebooted and phone just turned back on....no black screen
[HTC One S] :
Then you didn't do it right. Make sure the.file is on the root of your sdcard named killp4

dd if=/sdcard/killp4 of=/dev/block/mmcblk0p4
[HTC One S] beyored:
cheers you were right....

lol.....forgive my noobness but what does it mean by spam....

second terminal comand is not registering....

it comes up with /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1........then nothin....
[HTC One S] Evil-Monkey:
What's a riff box?
[HTC One S] :
Spam means to do it over and over and over and over and over... And over and over again
[HTC One S] beyored:
thanks for that....i must have done it 50 times and still nothin....
[HTC One S] :
you gotta reset the phone first by holding the power button
[HTC One S] beyored:
got to the end and qdl mode decided to close now i cant run any comands....

and it didnt work...
[HTC One S] :
Restart the computer.. If you have lsusb open you will see it change from QDL mode to Qualcomm inc, that's when you do

ls /dev/sd*
[HTC One S] beyored:
Iv just gone through it all again this time without a hitch.....thanks for the help I appreciate it.....iv gone from hboot 1.14 to 1.06 thought I had destroyed my phone at one point .....made me sweat for a minute...lol

Thanks again for the help.....
[HTC One S] FlyinGrub:
please help!

my computer has going in sleepmode when the restore is in run !

linux didn't detect my phone now...

What can i do ?

sorry fo my english i'm french..
[HTC One S] andryyyy:
No problem! Just reboot, start over. :)
[HTC One S] FlyinGrub:
thanks !

i've do that but now i finished without error and my phone is reconized as qualcomm ..
[HTC One S] Evil-Monkey:
Questions?

So I've been reading and reading this thread and I have a couple of question the more experienced crowd may be able to clarify.

[1] Theoretically, this process is for us who updated our devices and are now stuck on a high HBoot [1.14/1.13] which only allows us to flash radios via recovery when on stock android but not sense?

[2] So in essence if we want to run sense we cant have the latest radios unless you run a complete RUU, re-root etc?

[3] Is there a reason why HBoot 1.06 was chosen over 1.12 [not sure if that's the one below 1.13, but i'm just going in order] since 1.12 is the highest Hboot that can still flash radios via recovery?

[4] The reason I ask # 3 is because technically isn't the highest Hboot that isn't .13 or .14 the best option because then you can run more RUU's without supercid?

[5] Is there a method to change HBoots without bricking after you complete this process?

[6] once I downgrade what are the possibilities that i'll have those home button issues? I dont have them now but that's the only reason i wouldn't wanna do this. Unbuntu is complete and i wanna go through with this but i wanted to see if you guys could help clear my head.

Thanks in advanced!