yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] lorjay589:
TEAM REJECTZ QUICK FIX

OK I know somepeople still have problems with compiling apks and baksmali/smali

well your problems are over​

1. You need to make sure you have the latest java

2. Download Notepad++ (google it) lol

3. Download the Team Rejectz Quick Fix (the latest one) which is linked below

Instructions Decompile/Recompile​

1. UNzip and place the Quick Fix folder anywhere you like the script is prompt to locate the files

2. Since this is TW you should drag your framework-res.apk, twframework-res.apk, and systemUI.apk onto the apktool-if cmd file

3. Now time to decompile. You can actually drag your apk from where ever its located but i suggest you place them in the Quick Fix folder.

and drag and drop it on top of the Quick-Deompile cmd file

4. To get an error less decompile i prefer you to use the stock apk

5. Once the decompile process is done. you can go into the apks folder that was created and make your edits

warning if you create to many edits that would cause and error. then begin the process over but do them one by one​

6. Now its time to recompile ^^^^^^^^^remember the warning^^^^^^^ drag and drop the apks folder on top of the Quick-Recompile cmd file

7. Now once your done go into the apks folder you should see dist folder. Your new compiled apk is located there.

8. Don't worry about signing the apk. All of your edits besides the ones in drawable folder will be in the resource.arsc file

9. Drag that file into the apk thats in the rom your editing

10. If you decide to edit the decompressed .9 images you can check my Team Rejectz Theme Cheat Sheet located >>>Here<<< theres going to be an updated tutorial to quickly edit them

Baksmali/Smali​

1. Grab the apk/jar file you want to edit

2. Drag the classes.dex file out of the apk/jar file

3. Drag and drop the classes.dex file onto the Quick-Baksmali cmd file

4. A classout folder will be created

5. Now you can make your smali edit inside of the classout folder and close and save them.

6. After the edits and save, drag and drop the classout folder on top of the Quick-Smali cmd file

7. You should now see a new file called new-classes.dex. rename it to classes.dex

8. Finally drag the classes.dex file into the original apk/jar you pulled it from

If this helped you in anyway just hit that thanks button thanks!!!!!!!!!!

Download:

Team Rejectz Quick Fix

Mirror
[Samsung Epic 4G Touch] habitformer:
Doing Photoshop tonight than eventually this.Thanks for doing this it'll save me from getting a hold of you and timmetal.
[Samsung Epic 4G Touch] timmetal6669:
Great post LJ, THANKS for this.
[Samsung Epic 4G Touch] sleshepic:
This will def help some peeps, thanks LJ. Regardless of how simple you made it get ready for questions! Lol
[Samsung Epic 4G Touch] VeNuMuS:
Awesome dude this will help me out a lot. I think i will be the first to ask questions :D
[Samsung Epic 4G Touch] lorjay589:
lol i know, i already know
[Samsung Epic 4G Touch] timmetal6669:
Lol this is awesome.. Great post for team rejectz.
[Samsung Epic 4G Touch] cas8180:
Any instructions on possibly setting up a debugging environment say with eclipse or another ide so you can actually edit your code set break points and test the functionality possibily via emulator?
[Samsung Epic 4G Touch] lorjay589:
Lol are you joking or serious. Lol. But if not sorry this not that type or strong of a project its just a quick and simple way for people to compile and decompile
[Samsung Epic 4G Touch] lorjay589:
Well I try to help as much as possible
[Samsung Epic 4G Touch] lickarock:
Awesome man
[Samsung Epic 4G Touch] KingRedHot:
Thank You for this! I'll be looking into making a cm9/10 theme and I really needed this lol
[Samsung Epic 4G Touch] lorjay589:
your welcome!!!!!!
[Samsung Epic 4G Touch] timmetal6669:
Yes thanks.
[Samsung Epic 4G Touch] lickarock:
Alright, first time i have to decompile since you posted this. Lets give it a go!
[Samsung Epic 4G Touch] lorjay589:
cool, hope all goes well
[Samsung Epic 4G Touch] timmetal6669:
Can't thank you enough for this..my whole world is easier.
[Samsung Epic 4G Touch] lorjay589:
Lol I hope so. Your one of the reasons I had to step my game up.

I actually have a plan
[Samsung Epic 4G Touch] lickarock:
*lights up cigar* I love it when a plan comes together. ;)
[Samsung Epic 4G Touch] manufan721:
Gotta tell ya, i love that you guys posted this..love your roms and what you're doing for the community team rejects!!!!!!:)
[Samsung Epic 4G Touch] timmetal6669:
Thank you manufan, can't tell you how much that means to us/ me. great work with the calk rom remake too BTW.

---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------

Lol.. Love this. Made me actually lol. :) . How's that AOSP coming you sly dawg...?
[Samsung Epic 4G Touch] lorjay589:
Thanks a lot and no prob. We are just here to help
[Samsung Epic 4G Touch] timmetal6669:
I use this every day!
[Samsung Epic 4G Touch] lorjay589:
Me to lol. I'm addicted to my own product
[Samsung Epic 4G Touch] timmetal6669:
I love it... Its so easy... But most important it works!

edit. BLACK is coming
[Samsung Epic 4G Touch] lorjay589:
Hey man black been here. ( double eyebrow raise) lol
[Samsung Epic 4G Touch] timmetal6669:
Lmao.. I couldn't tell, i don't see no color with you LJ
[Samsung Epic 4G Touch] timmetal6669:
Oh hell, Im just gonna say it, This ought to be stickied.. For real... Couldn't live with out it.
[Samsung Epic 4G Touch] timmetal6669:
Or at least in original development.. Just ask some of the devs around who have used it....
[Samsung Epic 4G Touch] lorjay589:
Well I use this enough myself
[Samsung Epic 4G Touch] timmetal6669:
True, me too, but what do we have to do to get some respect? Make a whole new Android platform?
[Samsung Epic 4G Touch] timmetal6669:
All of you who have been asking me compiling questions, This is what you use... :)
[Samsung Epic 4G Touch] timmetal6669:
Its just the TR nature :)
[Samsung Epic 4G Touch] timmetal6669:
Still wondering why this isn't in original development for the E4GT? This tool makes apk tool look weak and non.user friendly. This by FAR is the easiest way to decompile... And LJ wrote the batch program for it from scratch... If making a kernel off of tw source is original, then i believe this is also.
[Samsung Epic 4G Touch] mrkevo3000:
Lorjay in step 2 am I dragging all three at the same time or one at a time, cause when I drop the framework-res.apk over it, it runs real fast but never open up.
[Samsung Epic 4G Touch] timmetal6669:
You need the latest java and jdk installed on your computer first. (google it , download and install) then pull your framework-res.apk, twframework-res, and system ui.apk's and place them in the quick fix folder. Now grab your framework Res apk and drag it over the apktool-if.cmd and drop it on top. That will load your framework-res as your resources. Now take your apk that you want to decompile and dragit on top of the quick.decompile.cmd .This will make a folder that's the same name as your apk. Now your apk is decompiled. Go into the apk folder and make your edits. When you're done editing your xmls then grab your framework res apk and once again drag it over the apktool-if.cmd. Now drag your edited apk folder on top of the quick recompile.cmd. This will force recompile your apk folder and give you a log of - if any errors for you to fix. Now open the archive of your original stock apk with 7 zip and open the archive of your new apk ( in the apk folder that you dropped to recompile is a "dist" folder. The new apk will be in there) Then drag any MISSI.NG files from the stock apk archive *do not in unzip, just drag and drop from archive to archive** (META.INzipF, CLASSES.DEX, ETC) AND drop into your newly modified apk archive.. Providing you didn't get a bunch of errors (which the log will give you a list to fix) then your newly made apk is ready to use in your ROM or.push to your system. :) Hope this helps. If so please hit my thanks button!
[Samsung Epic 4G Touch] lorjay589:
I see you been doin your, good f'ing job
[Samsung Epic 4G Touch] timmetal6669:
This is for indroid.... <LJdefault Thread text ="BUMP">
[Samsung Epic 4G Touch] timmetal6669:
Still the easiest way to compile.an decompile on the net! Thank you lj you are missed.

---------- Post added at 04:16 AM ---------- Previous post was at 04:10 AM ----------

Yip quick fix to the rescue!
[Samsung Epic 4G Touch] g_ding84:
Oh yes. Very easy to use. All I use. :)
[Samsung Epic 4G Touch] timmetal6669:
Get used to using this and you'll never use apktool again. Plus this works with out errors most of the time as long as your sdk , jdk, and java are up to date. I love this friggin fix... Can this be moved over to original development yet??? Or posted as a sticky for all DEVS to use? I have to link someone to this thing at least 20 times a week.... Jay??
[Samsung Epic 4G Touch] sleshepic:
No! It would make it too easy for people to do things! How are we gonna separate the bourgoise from the common folk?! Next thing we know people will be slicing their own bread too. Hide this gem deep in a cave somewhere lest everyone Smali/Baksmali with utter ease :)
[Samsung Epic 4G Touch] moparfreak426:
Will use thus
[Samsung Epic 4G Touch] g_ding84:
I know. Then ya have an idiot like me trying to do stuff. Lol
[Samsung Epic 4G Touch] lorjay589:
Im back baby lets have some fun. point me to the nearest update cause its bout that time
[Samsung Epic 4G Touch] timmetal6669:
First order of business is to get this in the ORIGINAL DEVELOPMENT section please! ?
[Samsung Epic 4G Touch] Mattix724:
Either that or a sticky...
[Samsung Epic 4G Touch] timmetal6669:
Oh I agree, sticky is good. :)
[HTC One V] FLBoy1991:
are the only for PrimoC??? if so... are there any Kernals for us PrimoC fellows???
[HTC One V] Lloir:
you mean are they only for PrimoU...and yes they are, there is NO PRIMOC kernel support yet, HTC Have not released the source code for the PrimoC kernel yet
[HTC One V] FLBoy1991:
O ok... Thanx for the clarification bro
[HTC One V] Ivo_Strojnica:
Is it possible?

Is it possible that kernel can kill a smartphone?

I flashed Titanium kernel yesterday on my HTC One V, and right after flashing, phone vibrated 3 times and now is dead.
[HTC One V] paarthdesai:
yes kernel flashing can kill your phone

and by kill i mean serious one

only a motherboard or ic replacement can make ur phone work again or else

u have a smart sexy looking paperweight :mad:

Sent from my HTC One V
[HTC One V] Ivo_Strojnica:
that then explains why my htc died two days ago, right after i flashed the titanium kernel #5.
[HTC One V] maxwen:
Actually this has nothing to do with the kernel in the first place!!!

I am flashing kernels daily since many weeks :)

The problem is "lower" since the V seems to have some real HW problems

it has been reported that this "bricking" can even happen on daily use

without any rooting or flashing at all

Regards

max
[HTC One V] jetfactor:
yes on a side note, something weird happened the other day. I made a backup of my ROM (stock) on CWM, then flashed CM9. decided to go back to stock. when I restored and asked for reboot, the phone simply turned off... and then wouldn't respond to a power button press for about five minutes.

for fun, I restored the backup of CM9 I had made before restoring stock- and what do you know! my phone rebooted just fine. weird.

-sent from space
[HTC Wildfire S] jonasdhondt:
@RobotoMOD developers

@dudeman1996

I have been trying for a couple of days to install RobotoMOD but every time when i want to reboot after installation it jams at the boot screen.

What can i do to solve this? I tried a dozen different installation combinations but the problem stays. I tried to not install Google apps or Google extras but it stays.

Also at the end of the installation it says:

"RobotoMOD has been installed. Installer Status: 0"

Please help me out, i really like to try this Mod.

Greets Jonas
[HTC Wildfire S] joemontana8:
Happened to me as well, and I solved the problem using the tip I found here.

unfortunately after installing the ROM PlayStore kept crashing and I couldn't even create a Google account, so I had to get back to the old ROM.

Pity, though - Robomod looked really great.....
[HTC Wildfire S] jonasdhondt:
Stuck at boot screen

It sure looked great.. I tried custom, and different installation options but didn't worked. it always gets stuck at the boot screen. I hope someone of the development team is going to help!
[HTC Wildfire S] jonasdhondt:
RobotoMOD developers please help. I can't post on the RobotoMod topic in the "Wildfire S Android Development" because I’m a new member...
[Samsung Galaxy Nexus] imablackhat:
Okay so I've had this issue on every jb ROM and Franco and Trinity kernel. Idk what else to do.

Proximity sensor doesn't work on the phone. But shutting the screen on and off works during phone call using the power button.

Downloaded an app. It recognizes the sensor and says I have one.

Proximity sensor works for a little while when I reset it by pulling the battery. Then it randomly stops working again until I pull the battery and do another reset.

What should I do? It's really annoying. The fact it works up until a certain uptime of me using the phone and such makes me think maybe something's conflicting with it? No screen protector is on blocking BTW.

I do have Verizon insurance and my phones under warranty. But I'd rather not... because nexus is banned. And I don't want a g3
[Samsung Galaxy Nexus] Zepius:
does it happen on ICS? if the answer is no, go back to stock and wait for the official JB from VZW
[Samsung Galaxy Nexus] imablackhat:
I don't know. I rooted day 1
[Samsung Galaxy Nexus] Zepius:
then go back to stock ICS and see
[Samsung Galaxy Nexus] imablackhat:
Meh. I'd prefer not to have to revert entirely back to stock. Seeing his other people I know are on the same phone and ROM don't have this issue

The light sensor works. Is that build into proximity sensor or separate. ?
[Samsung Galaxy Nexus] RoadHazard:
One thing to consider is that the proximity sensor only makes the screen turn off if the phone is held in an upright, vertical orientation. If held horizontally, the screen won't turn off during calls when the sensor is covered. No idea why this is, but maybe they assume that if you're holding the phone horizontally you're doing something with the sceen rather than holding it up to your ear, and thus the screen doesn't turn off if your hand gets too close to the sensor?

Anyway, are you positive this isn't what's going on?
[Samsung Galaxy Nexus] imablackhat:
Held up right. Put up to your ear or put hand over nothing happens. But when I pull the battery and reset the sensor it works flawless for a little while.
[Samsung Galaxy Nexus] Zepius:
i gave you a solution to see if its the phone or the rom/kernel. if it happens on stock, get a replacement. otherwise.. deal with it, or stick to ICS for now.
[Samsung Galaxy Nexus] netbuzz:
No one is saying you need to unroot your phone. They are saying that the way to see if there is a problem with your sensor or phone is to check it against the stock image. Make a NAND backup, revert to stock and test. Once you have an answer, restore from backup to your favorite ROM.

If this keeps occurring on stock, then you have a warranty case.
[Samsung Galaxy Nexus] imablackhat:
Is there an easy way to completely disable the sensor. I'd rather have it like that so I can turn the screen on and off during phone calls vs rely on something that doesn't work.
[Samsung Galaxy Nexus] yiannisthegreek:
Why wont you just make a Nandroid Backup in CWM and try a stock ICS ROM as was mentioned to you to try? You have nothing to lose by doing this and you can go right back to where you are now once you try it by restoring your Nand. At least then you will know for sure if its ROM related, possible Hardware issue, etc and THEN you can dig deeper from there.

Start at step one my friend and dont try to jump directly to step 10. Remember... Rome wasnt built in a day...
[Samsung Galaxy Nexus] akira02rex:
You aren't the only one who has experienced this. I had the same thing happen to me. I think it was a piece of dust in there causing it to malfunction. I reflashed the stock rom, and a couple others. I even tested it with a couple of apps, etc. Just out of the blue it randomly started working again! It happened several months ago, just once, and has been behaving normally ever since - beats me!! ::knocks on wood::

Edit:

Since when is the nexus banned??? It is back up for sale now as far as I know - it's available on Google's Play Store. Try lightly shaking the phone to see if it jolts any specks of dust out of the way of the sensor under the glass.
[Samsung Galaxy Nexus] imablackhat:
This is kind of why I'm against going back ICS. Plus my friend has the same phone and has followed me to every different jb ROM and doesn't share this same issue..

I did recently today pull the battery for a minute and let then phone sit to reset the proximity sensor this works every time. Now I'm at 5 hours uptime. When it stops working again that's when I'll try your shake method.

I do have apps to also test the sensor. And right now it works perfect. Clearly. Because I just calibrated it. It usually messes up within a 12 hour period.

If its dust in there. Don't you think the phone would stay off and not wake up seeing how its blocking the sensor

I really don't want to go back ICS. I'm hooked on paranoid android. And every ROM shares the same issue. And its not like I can just flash ICS to test it seeing how it takes a while for something to mess it up

Maybe there's an app conflicting with it?
[Samsung Galaxy Nexus] imablackhat:
After 14 hours uptime it doesn't work again. But now my light sensor works. Using android sensor box. Its either one or the other works. I know everyone is going to say just install stock ICS and see if it does the same thing... -_- i dont have a ics stock backup. The shaking method because of dust possibly didn't work either.
[Samsung Galaxy Nexus] harveydent:
Where did you buy the phone? If you have warranty, you can just get it replaced
[Samsung Galaxy Nexus] akira02rex:
I will say this.. mine mucked up using Paranoid Android - coincidence, I have no idea? That was back when PA was ICS based though. The apps I used to test the sensor always showed the sensor as being blocked if I remember correct. When I made a phone call the screen would never turn off. The funny part is that if I tapped around the sensor lightly or lightly shook the device it would cause the screen to flicker a few times randomly. After flashing a few roms (ended up sticking with CM9), it just randomly started working again. I can't make any rhyme or reason from it.
[Samsung Galaxy Nexus] imablackhat:
What cm are you using can you link? I just tried cm 10 king build
[Samsung Galaxy Nexus] akira02rex:
It was CM9 that i used. I'm currently on stock Jelly Bean w/ trinity kernel.
[Samsung Galaxy Nexus] imablackhat:
Cm9 rc1 rc2? They still make nightly for 9 don't they? When 10 is out? Idk I'm confused
[Samsung Galaxy Nexus] el_charlie:
I'm having this issue right now with stock rooted Jelly Bean.

I never tried ICS because I only have few weeks with the phone and went straight away to JB.

I think it's a combination of faulty hardware and software because by using "Proximity Sensor Finder" app I can tell the sensor is not working. BUT, if I turn the phone off (not battery pull, just power off by holding power button) and turn it on, the sensor it's working again. So, I can tell that it's something when the uptime reaches some hours that the sensor stops working.

Maybe, something on the hardware side triggers this behavior in the software side, I don't know.

In conclusion, I just need to power off the phone and turn it on again and the sensor works.

Cheers!
[Droid Incredible Q&A, Help & Troubleshooting] xLILxEVILx:
I really do hope that someone here has the answer im looking for...first off im currently running mcsense v2.6 and got to say its perfect in my eyes i got everything working on it mms internet everything im happy with it its flashed to cricket i had to figure out on how to get mms to finally work it was a major pain i got help over at cricket users...

anyway i love to flash roms and annoyed that with this great rom by mcd keeps giving me the annoying install uptate message so i just want to be able to try new roms ...i love to be able to theme roms like u can on CM7 CM9 etc...but as a cricket user seems like ur limited to what roms u can use as far as having everything working the APN method i have working is only working on 2.3.4 only ive tested this on other GB roms 2.3.5 CM7 and CM9 i also tried some methods that ive seen here and on cricket users and nothing ive searched all over and no luck so far....

heres what i got working using APN manager

apn:

cricket

proxy:

wap.mycricket.com

port:

8080

user name:

mynumber@mycricket.com

password:

cricket

server:

wap.mycricket

mmsc:

http://mms.mycricket.com/mycricket/mms.php

mms proxy:

wap.mycricket.com

mms port:

8080

mcc:

310

mnc:

120

apn type:

mms

not sure why this method works on mcsesnse v2.6 2.3.4 but not on 2.3.5 or CM7 etc can anyone tell me why this is the case please dont know were else to turn...IVE SEARCHED ALL OVER AND TRIED DIFFERENT METHODS...
[Droid Incredible Q&A, Help & Troubleshooting] cmlusco:
It could be that 2.3.4 is native to the incredible, while 2.3.5 is ported from sprint i believe. So your trying to restore an inc structured apn to a "sprint" rom. Have you tried manually entering the values from the incs apn backup to the new roms apn backup file, and then restore it? Just a shot in the dark, i may just be blabbering.
[Droid Incredible Q&A, Help & Troubleshooting] xLILxEVILx:
thanks for the help once again cmlusco i havent tried that yet but i will give that a spin even if its a shot in the dark...ill let u know what i come up with thanks...
[LG Optimus 2x] Spidergio:
I have got an italian optimus 2x with gingerbread 2.3.4. And the v20s. How can i root and install the CWR? Thanks in advance.
[LG Optimus 2x] SREEPRAJAY:
CHECK HERE
[LG Optimus 2x] Spidergio:
This update is of the 8 june 2012. These threads are of 2011. Then what should I take?
[LG Optimus 2x] grimmyrippy:
Search in google "optimus 2x root" and there's a result rooting for dummies something like that
[LG Optimus 2x] Spidergio:
I do it. methods are very old
[LG Optimus 2x] aragorn7:
I remember using a windows program called SuperOneClick to root mine a few months ago

It worked just like its name. Super noob friendly.
[LG Optimus 2x] grimmyrippy:
But it works on me
[LG Optimus 2x] Striatum_bdr:
Phone is old too.
[T-Mobile Samsung Galaxy S II SGH-T989] rmarquez1974:
Looking for an app that will determine which wireless APN has better reception an switch to that one automatically.

I am in an office where there are 3 wireless apn's, I get reception to all 3 no matter where I'm at yet if I'm connected to "a" and walk to the other side of the office, "b" is stronger yet my phone doesn't change. And at that point "a" only has a bar and this screws with email, Google searches, etc...

I can switch it via settings or turn wofo off the on again, but looking for something that does this behind the scenes and quickly.

Thanks.
[T-Mobile Samsung Galaxy S II SGH-T989] dankoman:
Tasker can do this. You need to use variables and it will require some set-up, but once you set it up, it will do it behind the scenes for you.
[Nexus 7 General] randpost:
So I initially purchased 2 8gb N7's, then I recently purchased 2 16gb nexus 7's. Both of my 8GB's are perfect, while both of my 16 gb's are going to be returned for screen separation issues.

Anyone else noticing this problem to be more rampant on the 16gb version? In my limited experience, I would say it is.
[Nexus 7 General] sashusmom:
So far my 16 is good.
[Nexus 7 General] randpost:
Maybe it was just luck of the draw.
[Nexus 7 General] endingcolt007:
doubt it. i own a 8GB and 16GB Nexus 7 and for the most part both are perfect. i think your mentioned situation is a coincidence rather than a trend!
[Nexus 7 General] linkinparkfan007:
My 16GB model had it as well.

Did the shim fix so far and it's working great.