yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] LuckyColdJohnson:
What would be the ultimate ROM. If a DEV could have all the Tweaks and Mods in a single flash. All the different lock screens. All the customization's and MODs from our favs. We have some flash addicts here I know. I had the Skyrocket before with a lot of different ROMs. Now that I have the Note 2, I've tried a bunch. I bet there is a DEV out there who could make the [Everything ROM] One with like I said, a little of all the options. Would Aroma installer be the best way to flash it. Have all the mods and customizing available for you to choose.*Or just choose ALL.... That would be sick......It might be impossible, but then again nothing is here @ XDA.....Love this site.

Thanks to all you DEVs that take the time to make our phones better.!!!!
[AT&T Samsung Galaxy Note II] cdshepherd:
The ultimate ROM is the one you like the most
[AT&T Samsung Galaxy Note II] LuckyColdJohnson:
The EVERYTHING ROM

No, I run the SKYNOTE 8 ROM. Its a beast! I just think it would be sick to have a EVERYTHING ROM. With Aroma installer and tons of options. Dont know if it can be done though. I am reading up on making ROMs as we post. I'm the type to stay up all night just to get something to work.
[AT&T Samsung Galaxy Note II] cdshepherd:
If you built one yourself that would be epic:thumbup:
[AT&T Samsung Galaxy Note II] borijess:
Lol

Sent from the TermiNOTEr 2! ;)
[AT&T Samsung Galaxy Note II] SlsAustin:
Lucky going 2 for 2 closed threads in one day. Lol
[AT&T Samsung Galaxy Note II] dligon:
The one that can incorporate everything every user and dev and tinkerer can imagine with of course insane battery life and stability.
[AT&T Samsung Galaxy Note II] LuckyColdJohnson:
Im new but know my stuff. I MOD everything...

Lol. Im not going 2 for 2. I have much respect for this site and just want to be involved you know...
[AT&T Samsung Galaxy Note II] Brad.S.:
Getting one thread closed that you made earlier.. And then trying to work around the rules by posting another similar thread with a topic that is completely correlated with the now locked thread isn't having respect for the site, nor its users.

Edit: to keep from bumping this thread, I'll reply here.

better yet, buddy, tell me how this thread is showing respect for xda.

Here: for the next time that you have an Off Topic idea that you want to "just throw out there"

You said you came from the i727 forums. If you know anything about that forum, then you know that stupid threads like this aren't allowed. What you learn in one forum, apply to the next that you visit. That's how it's disrespectful.

Take the advice given to you. Build something, find someone to collaborate with, whatever, and then ask what you can do to make it better for the users. This thread stands to put pressure on devs to do more than they already work their butts off doing.
[AT&T Samsung Galaxy Note II] LuckyColdJohnson:
Really

I'm not talking about all the ROMs. Im just throwing an idea out there about the EVERYTHING ROM. A lttle of each liked ROM or an Aroma Installer with a ton of options. Tell me how thats disrespectful. I can see why my first ever post got closed. Dont see that here buddy. Thanks
[AT&T Samsung Galaxy Note II] oka1:
From the moderator

Do not open another "Best Rom" Thread again..... they are not helpful........ the 1st post's answer is the right one....... the rom you like .....is the best........

.........THREAD CLOSED...........
[Galaxy S II Android Development] oddhap:
I made a port of the Chinese "Mokee OS" for cm7 http://www.mfunz.com/

This is based on v1.10.436 and latest CM7 nightly.

Working:

Everything except "about" screen.

Installation:

Wipe data/cache

Format system

Flash with cwm

Download: http://www71.zippyshare.com/v/28782496/file.html

Credits to blindndumb for his Lewa OS porting guide: http://xdaforums.com/showthread.php?t=1623464
[Galaxy S II Android Development] marcel112:
thanks for a new and different kind off rom..

i pass because off the cm7

:good::good:
[Galaxy S II Android Development] layercake87:
looks absolutely awesome!!! but i have to say that i also have to pass since cm7 is way toooooo old ^^
[Galaxy S II Android Development] snout:
+1, Looks really good tbh. Clean, refreshing but dated,.
[Galaxy S II Android Development] anshmiester78900:
wow its so beautiful going to try it !!
[Galaxy S II Android Development] jakuburban:
Getting errors while trying to install :(
[Galaxy S II Android Development] Nazato:
It's for P970.
[Galaxy S II Android Development] Phalanx7621:
So this ...isn't even for our device?
[Galaxy S II Android Development] oddhap:
Sorry, I accidentally uploaded the wrong version. Link fixed.
[Galaxy S II Android Development] Super-Bosnian:
it would be fine if someone can port launcher for this rom its beautiful
[Galaxy S II Android Development] sidrocks89:
Try go launcher ex. It looks almost same.
[Galaxy S II Android Development] Super-Bosnian:
ALMOST thats a point ;)

I love those dock icons but I cant find them in launcher apk. I have tried also to install this launcher but crashes
[Galaxy S II Android Development] 1Chef:
Deleted
[Galaxy S II Android Development] jakuburban:
Still can't install. "Error Status 7"

Edit: I had some problem with CWM. I'm gonna give this ROM a try. I remember it from my X10 and it was awesome
[Galaxy S II Android Development] shubham.dhand:
new things and roms are always appreciated... :)
[Galaxy S II Android Development] emam damon:
would some one upload systemui.apk of this rom here please?
[Galaxy S II Android Development] spiralout1:
Here ya go.
[Galaxy S II Android Development] shubham.dhand:
can't open "about phone".
[Galaxy S II Android Development] bkjugg:
read op plz

Отправлено с моего GT-I9100 через Tapatalk
[RAZR HD Q&A, Help & Troubleshooting] southcarolinacowboy:
Hey I have searched the forum and so far I have yet to find a solution to my problem. I have the Droid RAZR Maxx HD running on Jellybean. I am not sure if the problem was present before I upgraded to Jellybean.

I don't use video chat very often, but sometimes it comes in handy. Especially handy when you're troubleshooting something remotely. Ok I have tried Tango, Skype, Fring, ooVoo, Google Talk video, and Facebook video. Each one of them seem to do something different. Tango will dial the other person up and start my camera, but it will never let us connect. When I attempt to hang up a Tango call all it does is turn the green light off under the video camera icon, and the video camera stays on. I have to press the home button and force close the app. Skype will just force close if I attempt a video call as will Google+. The ooVoo app allows the video to work fine on both ends but we have zero audio and I've been unsuccessful finding anything in settings to change that. The Fring app let's the other person see me (they were on a Samsung Galaxy Note II), and we can hear each other. I can only see my own camera on my screen, though. So far ooVoo and Fring seem to be the closest to being working apps for me, but they still are not functional enough to be of any use. I contacted Verizon about this on the phone twice and visited the store once. The guy on the phone this morning said that it was likely something with the jellybean upgrade. The guy at the store last night said his works fine with the same kind of phone, but I'm not sure about that personally because I never saw him get it to work. The only phone he tried to initiate a video call with was mine. I'd really appreciate it if someone could help me figure out how to get around this. By the way, I also tried clearing the cache and the data for Tango and uninstalling, installed an older version of Tango from Google, but that only force closed. Please let me know if you need more information to help solve this issue, and thanks in advance.
[RAZR HD Q&A, Help & Troubleshooting] southcarolinacowboy:
Anyone ? ? ?

Sent from my DROID RAZR HD
[HTC Desire S] Husky34:
Original post

this feature works even on our device (i tested it on flinny 10.1 but it hould works even on a sense rom)

pratically u can add many shortcuit by pressing some part of your screen (like a popup) :)

it's really nice in my opinion

instruction:download latest apk and install it

press on the icon and set the weight & the position of the popup on your screen :D

note : this is not a Launcher so it doesen't change your homescreen, only add an invisible popup that appear when u press it!
[HTC Desire S] draken101:
Lmt

Read the link about this and it sounds pretty hectic. Does it tie into the kernel and what exactly do you use it for?
[HTC Desire S] meetom:
I have flinny 10.1 too (CM 10.1, build 21), but LMT is not working. Which option have you set in "set input device"? Because "HTC Desire S" (or "HTC Saga") isn't listed. I've tried different options but still nothing :/
[HTC Desire S] zenesis:
What are you guys talking about?

LMT Launcher is working on my HTC Desire S running android 4.2.2.

I only use the PIE control. The Swipe and Gestures aren't working well.

If you are confuse you could go to the accessibility settings and check the LMT there.
[HTC Droid DNA] devilsaces:
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.

For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?

Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?

Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.

Thanks
[HTC Droid DNA] termin8tor22:
I would do it just to be safe and I flashed the new radios and got faster 4g but only slightly faster

Sent from my ViperDNA infected with ViperBlue DNA
[HTC Droid DNA] TJMac44:
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
[HTC Droid DNA] devilsaces:
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
[HTC Droid DNA] TJMac44:
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
[HTC Droid DNA] devilsaces:
Yeah, I can't remember a ROM for the thunderbolt that had the same level of customization as Viper. TBolt ROMS went more in the direction of trying to get the latest sense roms, most felt unstable, or to get ASOP. I have my ASOP fix with my Nexus 7 now so I don't mind sticking with just sense based roms.
[HTC Droid DNA] devilsaces:
I just flashed the new radio, planning on flashing ViperDNA this weekend.

After doing a little more research I came across this post:

http://xdaforums.com/showpost.php?p=37535001&postcount=1

It turns out that there are 2 parts to a kernal, the kernal modules and the boot.img. I guess I DO need to flash the boot.img separately. The modules are already packaged with the ViperDNA Rom. Does this sound correct? When I was flashing ROMs with my TBolt I usually flashed different kernals separately so they were already together.
[HTC One S] troby86:
Not sure if this is really a tip or not, but this worked for me. I hate seeing that "Tampered" warning in my Bootloader.

Now that I am S-OFF, when I flash a new radio via fastboot, then reboot my bootloader, the "Tampered" warning goes away. Can anyone else confirm this? Thanks.
[HTC One S] blackwing182:
Did you use fastboot flash radio radio.img?
[HTC One S] troby86:
Yes
[HTC One S] troby86:
I attempted to flash the new 1.13 radio, but it failed, however, my "Tampered" warning disappeared.
[HTC One S] blackwing182:
Did you run any othe comand, like fastboot reboot bootloader or something?
[HTC One S] Darknites:
Just tried flashing a radio zip and I still have tampered.
[HTC One S] troby86:
Yea, after "fastboot flash radio radio.img" I ran "fastboot reboot-bootloader"
[HTC One S] blackwing182:
No, flash it via fastboot
[HTC One S] troby86:
Flash the radio.img via fastboot, not the zip.
[HTC One S] troby86:
Here's exactly what I did:

Downloaded the new OTA that Behold provided yesterday.

Unzipped it, then unzipped the firmware zip that was inside.

Pulled the radio.img from inside the firmware folder.

Flashed the radio via fastboot, (it will probably fail depending on your HBOOT) then rebooted my bootloader, and the "Tampered" was gone and hasn't came back.
[HTC One S] Darknites:
Ya I trying to be lazy lol but will try that in a bit.
[HTC One S] rootrider:
Writing radio with fastboot flash radio fails here, doesn't matter which one. hboot is 1.06, device is s-off.

D:\Android\android-sdk\platform-tools>fastboot flash radio radio.img

sending 'radio' (34345 KB)...

OKAY [ 2.590s]

writing 'radio'...

FAILED (remote: not allowed)

finished. total time: 2.621s

fastboot reboot-bootloader right after didn't do the trick as well. ****
[HTC One S] codf4ther:
This didn't work for me either with hboot 1.06/s-off. I understood we needed and engineering hboot to flash a radio from fastboot.
[HTC One S] jujusito:
I have hboot 1.06, before s-off i can flash radio with fastboot without any problem, with S-OFF i can't flash with fastboot.

But i can flash on recovery with this Sense-Radio-Installer-V4.zip

http://xdaforums.com/showthread.php?t=1998270
[HTC One S] veeny101:
whats your hboot? and can you link me to the thread of the radio you used. thx
[HTC One S] troby86:
The link is in the General thread named "Just another 50mb update"....I am on HBOOT 1.14

Again, the radio flash failed, which is what I expected, but the warning did disappear for me.
[HTC One S] veeny101:
I will try it now. Hope it works. Crossed Finger.:)
[HTC One S] LibertyMonger:
Tried it, it pretended to be successful but was not and tampered is still there. I am on hboot 1.06 with s-off.
[HTC One S] ECEXCURSION:
Interesting. I'll try this method on my HTC One XL. So far it hasn't worked, but I'm very curious now. My HOX has HBOOT 1.09 so I guess it might not work. Regardless I'm going to experiment.
[HTC One S] WCCobra:
Same... HBoot 1.06 with S-Off... still showing Tampered
[HTC One S] dharvey4651:
S-OFF with hboot 1.09 - still showing tampered.

Well.. Actually it's showing a black bar without the word tampered since I hex-edited it out.

Either way it didn't work.
[HTC One S] codf4ther:
did you also flash the hboot in that file by any chance? There is a thread in the dev section that states updating the hboot after s-off resets the Tampered flag.
[HTC One S] troby86:
Nope. Flashed the radio.img....has anyone on 1.14 HBOOT tried?
[HTC One S] codf4ther:
I just packaged the new TMobile 1.13 radio in an RUU with the included 1.14 hboot and flashed it via fastboot. The Tampered flag is now gone.
[HTC One S] droidkevlar:
I have not flashed any radio and mine no longer says Tampered. Im on hboot 1.14

All I did was S-off and now its gone.

EDIT:

Here is screen shot
[HTC One S] WCCobra:
Care to share this this package? Or point to where we can find the latest RUU with 1.13 radio and HBoot 1.14?
[HTC One S] codf4ther:
might be the 1.14 hboot + s-off that does it. I was on 1.06 hboot and it said tampered until I upgraded to 1.14. The OP was on 1.14 when his went away as well..
[HTC One S] droidkevlar:
OK, cool.
[HTC One S] codf4ther:
Remove "Tampered" warning and update to latest t-mobile radio & hboot

In the interest of sharing knowledge, here's the steps I went through. I don't recommend this for anyone that has a working phone, you'll get no new features out of this. You'll need adb and fastboot installed on your computer and you'll need to have a t-mobile CID or have previously set the CID on your phone to SCID (11111111). You'll need s-off if you have a current hboot higher than version 1.14. This worked for me, but you're flashing hboot, it could brick your device if something goes wrong - you decide if its worth the risk:

1.) Download the OTA from here: http://fotadl.htc.com/OTA_Ville_U_I...2.35.531.7_release_306848u5s8i4b18xs094yw.zip

2.) Unzip this file (the OTA) and the internal zip file called firmware.zip

3.) Edit the android-info.txt file from the firmware.zip in Notepad++ (or similar text editor) and add "DelCache:1" at the end of the file. This might not be necessary, but I did it on mine.

4.) Create a new zip file that contains only the following files, give it a name less than 8 characters (eg newhboot.zip). rcdata.img and wcnss.img might not be necessary, but from what I've read they go along with the radio, so I included them.

android-info.txt

hboot_ville_1.14.0005_signedbyaa.nb0

radio.img

rcdata.img

wcnss.img

5.) Connect your phone to your computer. Execute the following commands in fastboot. If you get an error that says "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" after the "flash zip" command just do it again..

fastboot oem rebootRUU

fastboot flash zip newhboot.zip

fastboot oem boot

6.) If you're on a Sense Jelly Bean rom your wifi will most likely be broken at this point. Find the wifi fix for JB roms in the dev forum and flash it in recovery.
[HTC One S] WCCobra:
Totally awesome :good:

The "Tampered" Warning is now gone. Thanks for your simple guide
[HTC One S] cat2115:
"Tempered" is gone.. thanks codf4ther
[HTC One S] jujusito:
Hi

in my case I have SuperCid, hboot 1.06 european and me modelid is PJ4010000

if i change

modelid: PJ4011000

cidnum: T-MOB010

mainver: 2.35.531.12

btype:0

aareport:1

hbootpreupdate:3

for

modelid: PJ4010000

cidnum: 11111111

mainver: 2.35.531.12

btype:0

aareport:1

hbootpreupdate:3

this work for me?, thanks.
[HTC One S] codf4ther:
You have SCID, it doesn't matter what cidnum is set to, that's the whole point of SCID. I'm pretty sure the modelid only checks the PJ401 piece, so it won't hurt if you change the last bit.
[HTC One S] jujusito:
Unzipped the OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip

extracted from firmware:

android-info.txt

hboot_2.15.0000_signedbyaa.nb0

radio.img

rcdata.img

wcnss.img

I have not made any changes to the txt

I recompressed it in newhboot.zip and i flashed it, all ok, but "TAMPERED" has not disappeared :crying:

I have new hboot and new radio
[HTC One S] bluebenno:
works

Worked for me and didn't break wifi - I included the rcdata (radio config?). I was going from (previously downgraded) 1.06 hboot and s-off, CM10.1. I didn't change the android-info.txt. Thanks a milion

My bootloader only shows unlocked, but that stupid red overlay is still spoling my moded boot splash!

Sanity testing shows this radio better than my last (1.08ts), it's abit faster at HSDPA+ (cat16).

# ls -al
total 56988
drwxr-xr-x 2 root root 4096 Feb 22 22:42 .
drwxr-xr-x 6 root root 4096 Feb 22 20:51 ..
-rw-r--r-- 1 root root 93 Jan 28 17:57 android-info.txt
-rwxr-xr-x 1 root root 1047808 Jan 28 17:50 hboot_ville_1.14.0005_signedbyaa.nb0
-rw-r--r-- 1 root root 35169280 Feb 22 20:55 radio.img
-rwxr-xr-x 1 root root 141 Jan 28 17:50 rcdata.img
-rw-r--r-- 1 root root 5242880 Feb 22 20:58 wcnss.img

# zip newzip.zip *
# fastboot oem rebootRUU
# fastboot flash zip newzip.zip ( I got the FAILED (remote: 90 hboot pre-update! please flush image again immediately)
# fastboot flash zip newzip.zip
# fastboot oem boot
[HTC One S] codf4ther:
Try following my guide exactly as written, then reboot and flash the 2.15 zip that you made. You are s-off right?
[HTC One S] codf4ther:
What rom are you using?
[HTC One S] jujusito:
Viper 2.1.0 with s-off
[HTC One S] codf4ther:
Viper 2.1 has the wifi fix cooked in already. Glad this worked for you guys.
[HTC One S] rootrider:
Guys, thanks for your work.

Came from downgraded 1.06 and flashed (back) to 2.15 - still tampered

flashed then 1.14.0002 - still tampered

then 1.14.0004 - tampered GONE

and back to 2.15 - tampered still gone

Thanks again. :good:
[HTC One S] blackwing182:
tampered, where? lol
[HTC One S] Opentang:
Hey codf4ther - thanks for sharing this information. I followed the steps exactly and fastboot commands successfully. However I am still seeing the same "tampered" messaging and hboot and radio remained the same. Have been on hboot 1.06 since day one.

Thoughts?
[HTC One S] rootrider:
Please read my post #40. Seems you must flash 1.14.0004 to get tampered going.
[HTC One S] codf4ther:
Doesn't seem like the flash worked at all. What kind of an error did you get when you flashed the RUU that you made in fastboot?
[HTC One S] bluebenno:
CM10.1 - from http://get.cm, nightly build 0217.
[HTC One S] blackwing182:
that doesemt matter, bootloader matters
[HTC One S] rootrider:
Now let me answer this question the way it worked for me.

I downloaded the attachments from here. Keep in mind they're fastboot flashable ones!

To flash them I followed step 5 in codf4athers post.

Also keep in mind it's the 1.14.0004 that removes 'tampered', being flashed from a lower hboot. 1.14.0002 doesn't work for this but might be helpful to downgrade your bootloader from 2.15 in case.

Last not least you can remove the red text warning by flashing any of these bootloaders from recovery. 'tampered' will still be gone.
[HTC One S] codf4ther:
Makes sense then, Only Sense based Jelly Bean roms need the wifi fix.
[HTC One S] adamfirari:
is that mean we can downgrade with that from 2.15 to 1.14.002 ?
[HTC One S] ascot17:
Yes you can, but if you are S-OFF there is no point!

All you have to do to remove the TAMPERED message (and the red warning on startup) is flash the 1.14.004 HBOOT from here
[HTC One S] real187:
i had that since the day i was s-off, with no extra effort. :(

i first ran a official ruu to test downgrade hboot (from then on it was gone), did the ota (3.16 wasnt there yet), recovery etc........
[HTC One S] AndroidAutobot:
booya. bootlader 1.14 did the trick =) good thread =)
[HTC One S] crispychips99:
Flashed via fastboot. No problems at all. Good tips guys. Cheers for the excellent work.
[HTC One S] djsubtronic:
Didn't work for me, S-OFF HBOOT 1.13.
[HTC One S] gbyrne2011:
Hey guys can you help me here?? I'm completely new to HTC's, this is my first ever it's the HTC One (Vodafone), coming from Galaxy S1 & 2 so rooted them and all that which was so much more easy that this. I got the phone yesterday and in my excitement I unlocked the bootloader, now I've noticed I'm one of the lucky first bath people with the gap at the top and glass popping out slightly and stuck with TAMPERED and UNLOCKED in the bootloader, I can RELOCK but still stuck with TAMPERED, to make matters worse I've now just noticed some dead pixels, yes I'm sure it can get worse.

M7_UL PVT SHIP S-On RH (Vodafone Ireland)

HBOOT-1.44.0000

RADIO-4A.14.3250.13

There's no RUU available at the moment I know off to fix this whole mess, so can I at least get rid of TAMPERED I can then RELOCK, pray and hope for the best the guys at the shop will send off the phone and swap it right out.
[HTC One S] ryanshew:
Wrong forum, that's the new "one" you got. This is the htc one S forum.

HTC_One_S | S-OFF | DeviantXone_2.0 | Twisted_III