Related
Well this is a easy tool for editing /system/etc/hw_config.sh directly on your PC, and add things like multitouch, etc, without needed to edit on your phone (bored)
Attached some screenshots.
Requirements:
Windows OS (For vista & 7 please run as admin, for xp users, don't needed that), or Linux OS (only tested on Ubuntu, but tecnically should work on any linux OS)
Device Drivers
Java
On linux, chmod +x hw_editor.jar
You
Features:
Easy Editing Hw_config.sh
Automatic Backups
Easy Pull & Push, you just need to press a Button
Please be sure of connecting your device first to pc, and turn on USB debugging, otherwise the software will give you a lot of errors
.rar for linux, .zip for windows
Stop making awesome ****!
s0ftcorn said:
Stop making awesome ****!
Click to expand...
Click to collapse
Lol
Uploaded a new bug fixed version ( now it returns the RO state at end of pushing )
wooow great think nice working
only suggest could it be added for build.prop to?
it will be easier for newbies.
Great work buddy, thanks alot for your time making this
Eyama said:
wooow great think nice working
only suggest could it be added for build.prop to?
it will be easier for newbies.
Click to expand...
Click to collapse
I will see if i do it tomorrow
Kennnn said:
Great work buddy, thanks alot for your time making this
Click to expand...
Click to collapse
Im glad you like it
@ All : Uploaded new version, now sets chmod 755 for hw_config.sh, and uses a sh script to mount and unmount rw, seems to be better this way , also need testers from other devices
i have problems :/ i press pull and sucessfully pulled then i press edit and i got message java.io.FileNotFoundException: C:\temp.sh and then opens empty editor. backup map is empty. do i have to unzip to a particular place?
EDIT: i have it on desktop
Eyama said:
i have problems :/ i press pull and sucessfully pulled then i press edit and i got message java.io.FileNotFoundException: C:\temp.sh and then opens empty editor. backup map is empty. do i have to unzip to a particular place?
EDIT: i have it on desktop
Click to expand...
Click to collapse
Wait some time after pressing pull, and before pressing edit , also after you press pull please be sure if on C:\ are 2 files, one mountScript.sh and the another one temp.sh, please notify me
EDIT: Uploaded a new version with more sleep time (3sec after pressing pull)
no i dont get those files in C:\
Eyama said:
no i dont get those files in C:\
Click to expand...
Click to collapse
Did you press pull first right ?, so it's really weird, try with the new one, and be sure that your device it's connected with debugging mode on, try open adb, and write adb start-server
yes i did.i have debugging mode on and usb storage on.i tried the new one with sleep 3. just one think where do i need to unzip those files? in Android SDK/tools or i can have it on my desktop.
Eyama said:
yes i did.i have debugging mode on and usb storage on.i tried the new one with sleep 3. just one think where do i need to unzip those files? in Android SDK/tools or i can have it on my desktop.
Click to expand...
Click to collapse
You dont need to have USB storage on, but anyway i dont think that's the problem, it should work on any folder, for me works on any folder
EDIT: Wait what's your OS?
ok i tried with usb storage off, unzipet on desktop in xxxx folder. i start the Hw_Config Editor.jar press pull wait for message press ok. check in C:\ for those 2 files and they arent there. then press edit en same message for mising file. i dont know what is wrong maybe im too dumy for this hehe
Eyama said:
ok i tried with usb storage off, unzipet on desktop in xxxx folder. i start the Hw_Config Editor.jar press pull wait for message press ok. check in C:\ for those 2 files and they arent there. then press edit en same message for mising file. i dont know what is wrong maybe im too dumy for this hehe
Click to expand...
Click to collapse
Please say me what's your Operative System, if you're on windows vista or windows 7 you need to run as admin the .jar
yes im on win 7 im going to try with adimn run
Edit: i dont have an option for run as adnim this is strange :/
Eyama said:
yes im on win 7 im going to try with adimn run
Edit: i dont have an option for run as adnim this is strange :/
Click to expand...
Click to collapse
chumby_666 confirmed that works running as admin
EDIT: Download the last one and run .bat as admin , thanks to chumby for the bat
EDIT: Packed all in a .exe and run on background the .bat, also added a NICE icon
thanks to you both it is working now
o just for those who have antivirus protection turn it off before unpack zip an using the program.
D4rKn3sSyS, you really are making things easier for us.
BTW, downloaded this, got a virus warning message:
Trojan:Win32/Delfsnif.DX
Category: Trojan
Description: This program is dangerous and executes commands from an attacker.
Click to expand...
Click to collapse
I ignored it and allowed your awesome program to run. You might want to edit the first post to say that antivirus may give a false positive.
EDIT: For the extremely paranoid out there (D4rKn3sSyS is the man! Why doubt his program?), I ran the program through VirusTotal. RESULT: 5/ 42 (11.9%) returned "infected".
Works fine on mine, win 7 x64/x10 mini pro, using Avast free, no virus warning.
thx
Uploaded Linux version, tested on ubuntu, need testers on fedora and other linux OS
For linux, only will work on the root of your user Folder for ex: d4rk/files here
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
SummonerOfDeath said:
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
Click to expand...
Click to collapse
Pull me a recovery.log when you try installing the zip, and I'll have a look for you.
Sent from my HTC Hero using XDA Premium App
S.O.D. proudly presents.... recovery.log!
Here it is, i attached my own update.zip (rosie-signed.apk), maybe you could have a look at it as i don't know where the fault may be.
greets SOD
I would already be happy if you managed to solve the update.zip issue (would help me with other updates) but the main prob is adb noch really working, seems like some system part is blocking this?
my hero was originally a t-mobile google g2, created goldcard, rooted, custom recovery, new radio and custom rom.
a few details:
device HTC Hero (T-Mobile Google G2, the black one )
rom Salsasense RC2 (at the moment...)
recovery CWM 2.0.5.7 (think so, but im sure i got the latest)
sd 2gb
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
SummonerOfDeath said:
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
Click to expand...
Click to collapse
Fixed your update-script, new line for each command is needed
/facepalm
JieeHD said:
Fixed your update-script, new line for each command is needed
/facepalm
Click to expand...
Click to collapse
not serious no? /facepalm -.-" thanks will try that right now xD will give feedback if my device is still alive afterwards xDD
greets, S.O.D.
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
stroobach said:
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
brick after flashing modified rom.
push to /system/app didnt work.
flashing restarts recovery.
jieehd's tip of single lines for every command doesnt work, same as above.
error 0 = apk is not made for your device/rom, wont install.
error 7.. dunno, think its not matching binary or parsing error.
files from my thread? as post above says one is a log and the other is defect^^
i doubt weather will work as its eating HUGE amount of resources. if u want this lockscreen, maybe try salsasense, has got a 3.0 alike lock...
holidays now, wish good luck in coding would be happy if u found a solution
greets, SOD
were can i find HTCG2/hboot/PC10IMG.zip been looking all over for it and its no were to be find
Got some questions.
1. You want WHAT? And what is the purpose?
2. In how far is this related to this topic?
3. If u give us a path to this file, why do u ask where it is? Maybe try dowloAding some random rom (probably some ruu) and do extract & search..
4. Are you really willing to contribute to this topic? I dont see the point of posting this.
5. Obey forum rules. If u have got a question, post it directly in q&a section, not in some random topic or directly explain the connection to the actual topic.
Greets, s.o.d.
agnostic900rr said:
I dunno, no idea
Click to expand...
Click to collapse
what don't you know? may we help you? whats the purpose of all these posts?
i think i'll give it a last try next time wenn i got salsa sense installed and either find a solution instantly or give it up, as noone is willing to support me and i can't do much more with my poor coding skills.
seems like we have to admit that hero's dying and i have to wait for my contract to end so i get a new phone.
greets, s.o.d.
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.
This disables the full-screen message when you connect USB and have no ADB enabled.
This app has no user interface. Enable it in Xposed - reboot - done.
IMPORTANT
Xposed needs root access for installation and requires Android 4.0.3 and up
Website: http://tinyurl.com/nq32zze
Play Store: http://tinyurl.com/k9qzp2x
Xposed Repository: http://tinyurl.com/lrlouoh
APK download: http://tinyurl.com/mzert7f
Why this app? The pop-up is annoying.
bro can u share the source code plz? actually @liudongmiao wants to help back-porting it to gb & also asking ur permission,if u plz share & give the permission it would be a pleasure! thanks.
Hi, this dialog does not exist for before Android 4
defim said:
Hi, this dialog does not exist for before Android 4
Click to expand...
Click to collapse
ohh! thank u for ur reply.
problemo...
Hellooo this is not working for me... The USB screen still pops up. I have it enabled in xposed, I've rebooted but I'm not sure what else I'm supposed to osince there is no ui... But it is not working.
I have Xposed 2.4 on a ROM that is stock based and very minimally modded,.. Running ICS 4.0.3 something or other ha. On a zte engage... Any ideas? I noticed it says 'have no ADB enabled' maybe that's it... What is adb?
AsinineRepublic said:
Hellooo this is not working for me... The USB screen still pops up. I have it enabled in xposed, I've rebooted but I'm not sure what else I'm supposed to osince there is no ui... But it is not working.
I have Xposed 2.4 on a ROM that is stock based and very minimally modded,.. Running ICS 4.0.3 something or other ha. On a zte engage... Any ideas? I noticed it says 'have no ADB enabled' maybe that's it... What is adb?
Click to expand...
Click to collapse
It shows not if adb (for debugging etc) is enabled. Have you some errors in Xposed log? As the pop-up is a "full screen notification" you could also use NotifyClean if you have the donate version
defim said:
It shows not if adb (for debugging etc) is enabled. Have you some errors in Xposed log? As the pop-up is a "full screen notification" you could also use NotifyClean if you have the donate version
Click to expand...
Click to collapse
Hmm... Yes, there was like a paragraph of errors that shows in the log after I plug my USB in (and this attempts to launch) It was a bunch of .java errors... I tried to download the NotifyClean to see if that would do anything for me, but as you stated I would need the donate version because the free version did nothing for me... I'm fairly new to all this Xposed stuff so what I am going to do is disable this for right now... and come back later when i know more and see if I can get it working. I appreciate your response and also for making and sharing this module, im sure its helping a lot of people out :good:
AsinineRepublic said:
Hmm... Yes, there was like a paragraph of errors that shows in the log after I plug my USB in (and this attempts to launch) It was a bunch of .java errors...
Click to expand...
Click to collapse
If you could catch them sometime, please post here!
I wouldn't even know where to start... haha... The log is HUGE and the errors (that i THINK apply to this particular module) are like 15 paragraphs long... How about if i just upload the .log file?? (instead of posting like a million paragraphs on here...)
It's down at the end of the log.... what im talking about. all the java. errors....
AsinineRepublic said:
I wouldn't even know where to start... haha... The log is HUGE and the errors (that i THINK apply to this particular module) are like 15 paragraphs long... How about if i just upload the .log file?? (instead of posting like a million paragraphs on here...)
It's down at the end of the log.... what im talking about. all the java. errors....
Click to expand...
Click to collapse
That are many errors. Best would be to enable only one module, check log and report it to the developer.
But I have not found errors by this module
smart idea ^^^ but all my other modules work fine... this is the ONLY one i have that isnt working. but i will do as you suggested right now and upload the new .log. thanks for the idea smart thinking haha
EDIT: okay, now I did that... and now it doesnt ever say anything except 'loading class' ... even after i attempt to plug in USB, full screen alert still pops up, but no errors are logging. hmmmmm ... ? haha i'll attach log again...
AsinineRepublic said:
smart idea ^^^ but all my other modules work fine...
Click to expand...
Click to collapse
Unbelievable with all these errors :laugh:
AsinineRepublic said:
EDIT: okay, now I did that... and now it doesnt ever say anything except 'loading class' ... even after i attempt to plug in USB, full screen alert still pops up, but no errors are logging. hmmmmm ... ? haha i'll attach log again...
Click to expand...
Click to collapse
Should work, maybe you vendor has applied some custom reminder. I have only 2 devices to test
**does not yet work for 7.1.1**
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Excellent! This works perfectly! Thank you so much for posting this.
J320A PC9 worked perfectly!
March security patch
Hi man, this method support the march security patch, or are still in january security patch
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
This works perfectly. Thank you!
I suggest you put 'root' in the tile, otherwise google cannot find it.
I googled 'j320a root', google only links to ashyx's post which doesn't... well maybe only mine phone.
I am new to this root bit.
Possibly I have done something wrong. I read your instructions carefully and quit didn't understand where the unzipped files should go. Do any of these have to be placed in the phone's directory?
Failed on my AT&T SM-J320A
I wonder if it has anything to do with the new update pushed out recently
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
DamienMc said:
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
Click to expand...
Click to collapse
Hello DamienMc Thank you for your reply and help. I figured it out. I had to put my phone in "Download Mode" by holding down Volume Down, Home Button and Power button while booting. Then I was able to use Odin without failing. This solved all my problems thank you
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
sonic0504 said:
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
Click to expand...
Click to collapse
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are noticable tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Ragheb Alama said:
Hi man, this method support the march security patch, or are still in january security patch
Click to expand...
Click to collapse
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
DamienMc said:
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are "noticeable" tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Click to expand...
Click to collapse
Thanks, I just needed to install this to use adb to uninstall an update I did to System UI because it would continuously crash.
SBCarr said:
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
Click to expand...
Click to collapse
Probably the eng_boot we use, it breaks the flashlight and wifi passwords too... it does work on j320a July update, so I assume it'll work on j320az update too
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
ScSoluciones said:
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
Click to expand...
Click to collapse
Reflash CSC as well, that'll wipe your device but fix your problem.
Are you sure you waited long enough after the phone booted before rooting?
If at any time during the script you see it say "adb server out of date. Killing..." something is wrong. You can x the command prompt and do root.bat again.
DamienMc said:
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Click to expand...
Click to collapse
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
james2ya said:
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
Click to expand...
Click to collapse
@james2ya If you are talking about the pop that either says something in the order of "Unathorized activities where made" go to the play store, download and install SecurityLogAgent Fix, Open it up and click "Disable Securitylogagent" then restart phone when it asks. This should help get rid of that popup.
works great for me! now i just need a custom rom. is it possible to install trwp on j320a?