yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] In3rDm0RetHeNu:
I will post my soon.

Anyway here is the template

Pic:

Kernel ( include version ):

Rom version:

I/O Scheduler:

Governor:

Voltage/Clock settings ( CPU + GPU ):

Other/Misc/Mods:

The pic is not the most important part by the way.
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Thread title is a bit misleading. "AOKP kernel/scheduler settings" or something may be a better title? Also its kinda phone and user dependent, some settings won't work for some people.

Edit: thread title has changed since this posting.
[HTC Sensation] cashman0712:
I have tried everything under the sun, but I cannot get this thing to work. My phone will not find any recovery img I put on my SD card. No matter how new or old it may be. It is really frustrating. Can anyone help?
[HTC Sensation] Rusty!:
You're doing it wrong.

Take the recovery.img off your SD card and put it on your desktop. Then use fastboot to flash the recovery image.
[HTC Sensation] cashman0712:
Wait how do I use fastboot? I used a Mac to unlock my phone using htvdev.com's method.
[HTC Sensation] cashman0712:
My intentions are to also root my phone and install the new set Coindroid rom. Can I do that with my current setup? I couldn't use revolutionary because I own a Mac.
[HTC Sensation] Rusty!:
If you unlocked, then you know how to use fastboot!

To install the recovery you use

fastboot flash recovery recovery.img
[HTC Sensation] cashman0712:
ok well what about install a custom ROM such as coindroid and rooting the phone? Do i follow the same steps every time?
[HTC Sensation] Rusty!:
Nope, once you've installed recovery, you just enter that and install the ROM/root files.
[HTC Sensation] cashman0712:
Ok which recovery would you recommend? I am mostly used to ClockworkMod, but does the touch interface ClockworkMod work for the Sensation 4g?
[HTC Sensation] Rusty!:
Yes it does, that's what I use. You can find it here: www.clockworkmod.com/rommanager
[HTC Sensation] cashman0712:
Ok.

And the code for that would be:

fastboot flash recovery (what I just downloaded?)
[HTC Sensation] Behold_this:
TO OP: Coindroid is an ICS ROM. All ICS roms require updated "ICS" firmware found in HTC's 3.32 software update. Here's the problem, you CAN'T update your firmware (except for stock TMobile versions) because you didn't s-off. HTC bootloader unlock does not give you s-off and only allows for flashing rom, recovery, and in a round about way kernel. You need to update your hboot and radio by updating firmware, which, as i said, you no longer can do. You are now stuck on gingerbread based ROMs until TMobile releases their version of the ICS update next month. If you flash an ICS ROM you will end up in a bootloop.
[HTC Sensation] cashman0712:
hrm. Well if I root can I still get the update from T-Mobile? I want to remove the crap off of my phone. And then would it be wise to still install a recovery?
[HTC Sensation] Behold_this:
You would need full stock ROM to successfully install the update via OTA, meaning stock recovery and all system apps present.

**edit** I also added a little more info in my previous post, to give you a clearer understanding of what's happened.
[HTC Sensation] cashman0712:
Ok, So I only unlocked the bootloader via htcdev.com. Should I just leave my phone as is until the update then? And did the bootloader unlocker mess up my chances of getting the update?
[HTC Sensation] Behold_this:
I honestly don't know how HTC bootloader unlock may or may not effect OTA's, but I will say this, if you don't get the update or if you do and it causes problems with your device, you're on your own. Your warranty has been voided by the HTC unlock method and TMobile will not service the device so you will have to go through HTC which can cost $$$!
[HTC Sensation] cashman0712:
Won't there be a way to update it even if I don't get updated through T-Mobile?

EDIT: Also couldn't I just relock it just in case?
[HTC Sensation] Behold_this:
There probably will be. In your case, your best hope is that the official RUU for the TMobile updated software gets leaked and posted. They usually do. Look for it in this thread. Probably won't be available until sometime after it's official release.
[HTC Sensation] cashman0712:
Ok thanks for the help and tips!
[HTC Sensation] cashman0712:
Another quick question. Can't I just flash the GB Stock ROM and then update if I need to?
[Acer Iconia Tab A100] bjones72751:
I've seen a few mentions of cm9 for our device. Where do I find the download and what is or isn't working? I assume its not an official cm9...
[Acer Iconia Tab A100] toyface:
If you'd have spent time looking here in the General forum it'd have screamed out at you as the Iconia ICS Project tagged as [CM9] This thread will lead you to all that you seek.

Iconia ICS Porject - CM9
[Acer Iconia Tab A100] illego:
Someone should make a thread in the dev section. Its getting buried in all the bricked/ics upgrade threads.
[Acer Iconia Tab A100] ptesmoke:
its linked in my op of my cwm thread in dev section. fwiw.
[Acer Iconia Tab A100] bjones72751:
Thanks guys. Any bugs I should know of before flashing?
[Xperia Arc Q&A, Help & Troubleshooting] Mr.Smile:
hi every one

when i bought my xperia arc I found a screen protector in the box so I apply it on the screen but I noticed that there is another one under it! !!!!!!

Does Sony Ericsson pre install a screen protector on the screen ? Plz answer me
[Xperia Arc Q&A, Help & Troubleshooting] soumya_digi:
That is the shatter proof sheet. :D
[Xperia Arc Q&A, Help & Troubleshooting] Mr.Smile:
sorry my english is bad !!! what do you mean ? does i have two screen protector or what !!

sorry for the bad english
[Xperia Arc Q&A, Help & Troubleshooting] Mr.Smile:
Thanks for you both

i have removed the S.P that i have applied and useing the pre-insstaled and the screen look amazing now
[HTC One X] Techimplant:
Guys is a particular dead pixel visible on every background or can it be color specific too?..coz I think I saw a very tiny one on black background..but on every other background its fine..

Sent from my Stunning White HTC One X
[HTC One X] Danzki83:
Dead pixels usually miss a colour or two or are completely dead. If it's dead on black, i would guess it would be dead on all backgrounds.
[HTC One X] Techimplant:
Thanks..n I checked again n I think that its not a dead pixel but a scratch in my screen protector ;)

Sent from my Stunning White HTC One X
[HTC One X] Dj android:
even me i have 2 dead pixel and show just in black and blue i try to fix it by use some apps but it doesn't work please if there any way to fix it tell me

because I went to the warranty company and they told me should you have 5 dead pixel or more to change my one x.
[General Questions and Answers] Treebark123:
For some reason i am unable to upload pictures right now but i went into the astro file manager and went to /system/app/ and i found two files side by side one called nfc.apk and the other one nfc.odex or something. Anyways someone tell me what this means
[General Questions and Answers] ckvirya:
I also can't find

I also can't find... or this is true?:(

a bit disappointed!
[General Questions and Answers] jiawei0309:
i cant find it on stock ics LP9
[G Tablet Q&A, Help & Troubleshooting] paintermanscott:
Ladies and gentlemen,

I'm getting my viewsonic g tab tomorrow and have been reading the threads about nvflashing bootloaders. My question is (if my tablet comes with bl1.1) can I just nvflash from bl1.1 to bl1.2? I ask this because it seems some of the folks here either don't want to upgrade their bootloaders to 1.2 because theyre either too scared of bricking or "like" (?) bl1.1 but I like the rom branch and veriety of the 1.2 bootloaders. Thanks in advance folks.
[G Tablet Q&A, Help & Troubleshooting] paintermanscott:
BTW, I have read the guide on nvflashing (very great write up and summary of nvflashing the g tab) and it covers everything except if you can nvflash back and forth between the 2 bootloaders. This is my first tablet and please excuse my noobness on the subject of nvflashing. I know most topics regarding cwm and how to use it and have owned, rooted and flashed MANY ROMs on a total of 4 android phones. Thanks again.
[G Tablet Q&A, Help & Troubleshooting] DaggerDave:
You should be just fine to nvflash to 1.2. Many consider it "safer" to flash to the stock 1.1 TnT first but if your tablet comes with 1.1 you will already be there. Once you are on 1.2, you probably will not want to go back, but it is possible.

However, if your tablet comes with 1.1 you could also just take the OTA update to get to 1.2 and not have to nvflash. Then you can install CWM and a rom. Check out this site for lots of good info if you decide to use nvflash, and also make sure you read this thread. Backup your .bct file and use it any time you use nvflash. Some roms will require you to nvflash to change the size of the system partition (ICS for example).

Also, be sure to use the correct version of CWM:

CWM v08 - use for bootloader 1.1 only

3028 rev.5 - use for bootloader 1.2 only

5504 touch - use for ICS rom only (is included in the nvflash file found in the ICS thread)

BTW - if you do take the OTA update to get to 1.2 make sure you have the stock recovery installed NOT CWM.
[G Tablet Q&A, Help & Troubleshooting] paintermanscott:
OK, so my understanding here is; tab comes with 1.1-update to 1.2 with ota (no cwm, install after update)--> tab comes 1.2-downgrade with tnt 1.1 tool then nvflash back to 1.2 w/cwm? Hope that sums it up. And my whole point here is to end up with 1.2 w/cwm so I can start flashing bl1.2 branch ROMs. I think I'm pretty sure what I'm doing now. Thanks bud.
[G Tablet Q&A, Help & Troubleshooting] DaggerDave:
Yep, except that if the gtablet comes w/ 1.2 already there is no need to downgrade, and you only need to nvflash if you are going to use a rom that requires it. Just install CWM and then your rom of choice.
[G Tablet Q&A, Help & Troubleshooting] paintermanscott:
Thank you again daggerdave. My g tab didn't show up today. Tracking says tomorrow. Excited to have my first tablet!!!!
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
So, I'm starting this thread to start trying to put a root method together.

I've started work on a unsecure boot image using the at&t boot.img from 1.68

(going to try and get a 'INSECURE BOOT AND ROOT' going for our devices that paulobrien already has going for teg3 models)

I'd like a confirmation that the at&t 1.68 ruu does indeed work 100% without issue on the rogers devices. As there's no Rogers RUU, I'm taking a big leap with semi-bricking a pretty expensive device that I bought outright and would like to minimize risk (I still am willing to take the risk)

Also, any other information/help/idea's from other dev's or users alike would also be appreciated.

Let's get this ball rolling without waiting for the at&t release... :cool:

Edit: Has anyone attempted to compare the partition table to the one already somewhat put together for the Tegra 3 One X ?

PS: I'm going over information regarding the regular one x, and comparing them to the extracted items from the 1.68 evita ruu (so I can get a sense of the makeup of our devices) ... I might have to make us a partition table comparison similar to mike1986's
[AT&T, Rogers HTC One X, Telstra One XL] LNKNPRKFN:
from my understanding and research... the Rogers and AT&T are identical minus the HIGHEND bloadware
[AT&T, Rogers HTC One X, Telstra One XL] ytwytw:
Even the CID is the same?!

Wow that's good news for AT&T people, they can flash the Rogers RUU to gain more features

For rooting... Possible to unlock with htcdev?

Then we only need a custom recovery to push busy box and whatever to get root
[AT&T, Rogers HTC One X, Telstra One XL] craig0r:
I haven't done it myself yet, but some misguided users did unlock their bootloader and flashed the CWM for the Tegra edition of the One X. So I'd assume we're good on that front. I was going to start trying to compile CWM for our device on the weekend, but life got in the way.
[AT&T, Rogers HTC One X, Telstra One XL] bongd:
I've unlocked my bootloader through HTCDev. I also believe the CID are the same but please don't quote me on that. I spent hours trying to correct my device so everything is a blur.

I believe that outside the carrier bloatware that the Rogers and AT&T devices are completely identical. I've killed just about every piece of Sense software too and my device is running flawlessly. On a side note, I'm quite impressed at how polished this is and that Sense isn't the beast it was on previous devices. Re-enabled a lot of features and I quite enjoy them.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
The same was the case between the Telus DHD and the Inspire 4G... But one was the PD9814000, while the other was a PD9812000 (ordered respectively). I wouldn't doubt the same. The original DHD was PD9810000 (DHD 9191), and there was also a PD9815000 as well floating around in the asian market (I think Korea) and was simply another variant of the TelusDHD/Inspire (9192).

If someone were to hop into an at&t store and check their display model, what it says on the back under the FCC logo .. or better yet install terminal on it and run /sbin/grep and get the androidboot.mid value to accurately get the CID, would be best.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
Well, if our recovery sits in the same partition as the teg3 device, then we might actually have a chance.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
Also, here's a link to a 1.68 mirror I put up. More reliable that the one's currently available.

http://d-h.st/hoA

Will upload more as I get them (clicking my user name will get the full listing of items I have available; 'ER3BUS' is NOT for the One X if anyone's wondering)
[AT&T, Rogers HTC One X, Telstra One XL] ~David:
On the Rogers unit, it's NM8PJ83100.

I believe some AT&T customers here said they had the same number on their pre-orders.
[AT&T, Rogers HTC One X, Telstra One XL] craig0r:
(This may be a dumb question.)

Even if it's not on the same partition, does that really matter when we can just "fastboot flash recovery cwm.img?" Of course we'd have to find the partition locations, but I think fastboot should be enough to get us off to a start. Maybe I'm wrong. I've never had the chance to work on rooting a device, but with this one being so new, I'm hoping I get a chance to help out.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
Compiling a proper working cwm 'port' (if you will), kinda requires adaptation of code to correspond to the device's partition table... values need to change for commands for it to work properly and not cause your device to brick (you wouldnt want to flash the recovery to mmcblk0p05 if the recovery isnt in that partition)

(think back to the sd partition issue with cwmrecovery early last year which repartitioned some device's emmc instead of the sd)

I personally havent dabled in kernel / recovery compiling... so I'm only going off the amount of knowledge that I know; I could be wrong however.
[AT&T, Rogers HTC One X, Telstra One XL] danielsaenz:
I'm an AT&T rep, and I have a One X on hand. I can't take it home with me, but here's some info that you guys have been needing. Let me know what else you guys need me to find out/dump.

CID is CWS_001
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
Thanks.

I also have a modelid confirmation that the 1.68 is indeed the same as the 'release' firmware, and that our devices are identical.

I'll be attempting a down n dirty 'boot n root' tonight. :)
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
I'd rather fastboot flash a modded boot image (since thats easy to change) rather than flash an untested recovery, espeically since I'm the one changing the default prop values, and permissions in init.rc the boot.img. lol.

Edit: The boot image i'll be modifying is the 1.68 boot image.

no, you dont need root for that.
[AT&T, Rogers HTC One X, Telstra One XL] RMatt1992:
dev: size erasesize name

mmcblk0p23: 000ffa00 00000200 "misc"

mmcblk0p22: 00fffe00 00000200 "recovery"

mmcblk0p21: 01000000 00000200 "boot"

mmcblk0p33: 67fffc00 00000200 "system"

mmcblk0p30: 00140200 00000200 "local"

mmcblk0p34: 0ffffe00 00000200 "cache"

mmcblk0p35: 97fffe00 00000200 "userdata"

mmcblk0p26: 01400000 00000200 "devlog"

mmcblk0p28: 00040000 00000200 "pdata"

mmcblk0p36: 27be00000 00000200 "fat"

mmcblk0p31: 00010000 00000200 "extra"

mmcblk0p17: 02d00000 00000200 "radio"

mmcblk0p18: 00a00000 00000200 "adsp"

mmcblk0p16: 00100000 00000200 "dsps"

mmcblk0p19: 00500000 00000200 "wcnss"

mmcblk0p20: 007ffa00 00000200 "radio_config"

mmcblk0p24: 00400000 00000200 "modem_st1"

mmcblk0p25: 00400000 00000200 "modem_st2"

---

Using ADB - adb shell cat /proc/emmc

dsixda's kitchen auto root did not work for the stock ROM, it results in bootloop. Also, my other bootimg decompilation tools aren't working either. I know what to do, just not how to get it to boot on my phone. logcat doesn't pick anything up, either. If anyone has any ideas on how to get the boot.img decompiled/recompiled, feel free to send it my way.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
So, I think Paul may have beaten me to it.

But I'm still going to test my edits later tonight anyways. heh
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
Just make's you wonder what's actually sitting in our 5th partition (the recovery location of the endeavor)

dsixda's kitchen is really only for gingerbread devices.

I use that kitchen... just to 'cook' the final release into a signed zip.
[AT&T, Rogers HTC One X, Telstra One XL] RMatt1992:
FYI, Rogers CID = ROGER001, so they are different unfortunately.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
doesnt matter...

ro.aa.modelid=PJ831000 <- key value (this is what usually denotes hardware variance... usually the third last '0' becomes a different number)

same as the at&t one x.

the maincid and cidlist values mean nothing other than software branding. :)
[AT&T, Rogers HTC One X, Telstra One XL] RMatt1992:
Cheers, I thought the CID was important for something.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
only when s-offing/flashing different firmware for older devices. :D
[AT&T, Rogers HTC One X, Telstra One XL] sk806:
CID Rant & Recovery

Not to beat a dead horse, but...

CID is important if you are flashing firmware either as PJxxIMG.zip of through an RUU, as the CID will block you from flashing firmware from another version of the same handset onto yours. This can sometimes be maneuvered around by altering the android info file within a firmware update, but not always.

Probably not as big a deal on a carrier branded phone, but it has been kind of a pain on the International One X, in that most developers are using EU RUU-based ROM builds, but many do not have the EU firmware and can't get it due to CID issues. Most of the EU-based ROMs run fine, but I personally have noticed that ROMs I build from Asian RUUs worked better with my Asian CID One X, which can't flash EU software. People are free to disagree, however...

I am switching over to the AT&T LTE version, so kinda irrelevant. Just wanted to explain what the CID can potentially mean and why it is important in some cases.

Anyway, what I really want to know is whether anyone has begun trying to build an unofficial CWM for the Evita? I know Paul has a superboot planned, but we still need CWM (or at least I do)...:).

I'm more of a smali-coding guy than an android builder, but am happy to try to get one up if anyone wants to collaborate.

Steve
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
... with the new bootloader's its amost irrellevent now... its like a vestigial remnant. I learned quite quickly that making a pj83img.zip doesnt work like doing similar with older devices did.
[AT&T, Rogers HTC One X, Telstra One XL] sk806:
True, I'm just bitter over the International One X frustration..:). You really can't flash firmware without the right CID )whether zip on sdcard or RUU), and some of the One X's have no CID. Annoying.

Anyway, dead issue. Sorry....
[AT&T, Rogers HTC One X, Telstra One XL] RMatt1992:
Doesn't quite work that way -- have to make the boot.img insecure, and then make the superboot. I've got the bootloader unlocked, it's just a matter of compiling a functional version of the boot.img to do so. I spent my afternoon and evening attempting this, however all my .img's resulted in bootloop.

I'm interested to see exactly what was done to get it working.

We can. See "All Other Supported Models" - bottom choice on the list. Follow the instructions, flash the unlock token, and you're golden.Please keep in mind that this will wipe your device. Don't say I didn't warn you.. There's multiple developers who have already done this.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
unlock bootloader = allows you to flash an non secure boot.img, then you can push the su binary to /system/xbin and the app to /system/app

then superuser will actually work, and can then proceed to install busybox.
[AT&T, Rogers HTC One X, Telstra One XL] Pirateghost:
??

really you just need a CWM and an unlocked bootloader.

non-secure boot.img is not really required...wasnt required on vivid
[AT&T, Rogers HTC One X, Telstra One XL] RMatt1992:
Fair enough. Think we're all after the Superboot method though.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
well, im doing the non secure boot method... im working on the boot image as we speak actually...

Paul already confirmed that his is working (though at the moment unreleased because the nda for the at&t one x ended too late in the evening for him)

you know how to compile a recovery... because i don't (sadly, I havent had time to learn to compile zimages or recoveries. lol)

also, the boot.img's in the vivid's *non-canon* (meaning not stock/carrier) rom's are unsecure :P
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
never said stock were unsecure... they're totally secure... first

default.prop found in every stock boot img

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0

default.prop found in non secure boot images found in every dev/user made rom (custom built kernel or not)

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1

then there's editing certain permissions in some of the .rc files.

If you still have a secure boot img, the su binray wont actually work properly. you'll get the toast, but doesnt actually do anything (from what I remember anyways).
[AT&T, Rogers HTC One X, Telstra One XL] Pirateghost:
yeah. we had root on vivid WITHOUT flashing any boot.img files.....still do in fact

i am saying this because i know it to be true....we did NOT need boot.img files to root vivid.... unlocked bootloader, flashed CWM recovery, installed su binary and superuser.apk via CWM flashable zip.....and trust me it works....

thats all i was saying....not saying you cant go about it the way you are, just saying it wasnt necessary for that device.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
yeah, it probably wouldnt be necessary for the PJ83 either, but we dont have a recovery yet. Frankly, if we had a proper recovery then 100% we'd be rooted already without question... instead rogers's users screwed themselves by flashing a recovery for a completely different device (hardware wise). lol
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
boot loop with "tampered" in the bootloader on first attempt. Also, had a nice red message saying its htc property, not to leak it.

lmfao love it.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
Im checking to see whether there's a slightly different hex offset start/end on the newer boot images, comparing the stock 1.28 boot.img with paul's, and an older boot img from a different device. I dont have work in the morning, so i'll have a couple hours before I become incoherent... i've also had 2 double cups of coffee. lol