i prefer the vanilla lockscreen but i like sense after i unlock.
im running nfinite45x's stock .6 rom with v4 710 oc kernel. is there any way possibly to achieve the vanilla lockscreen?? thank you
tailsthecat3 said:
i prefer the vanilla lockscreen but i like sense after i unlock.
im running nfinite45x's stock .6 rom with v4 710 oc kernel. is there any way possibly to achieve the vanilla lockscreen?? thank you
Click to expand...
Click to collapse
I can't say for sure if the vanilla lockscreen is included in nfinite45x's stock rom, BUT, you can try this to see if it works:
go into command prompt on a windows computer and type
Code:
adb remount
then type:
Code:
adb shell mv /system/app/HtcLockScreen.apk /system/app/HtcLockScreen.apk.bak
then type:
Code:
adb reboot
If it worked okay, then YaY!
If it did not work and you're stuck with a broken lock screen or nothing at all, then keep u'r phone on where it is, get back in and do the following:
Code:
adb remount
then type:
Code:
adb shell mv /system/app/HtcLockScreen.apk.bak /system/app/HtcLockScreen.apk
then type:
Code:
adb reboot
Now, you're HTC Sense lockscreen should be back to normal again Hope that helps some. Again, I'm not sure if the vanilla lockscreen is included in the stock rom... so, as always, nandroid u'r rom first. Happy coding!
That will not work with the nfinite stock rom to get the vanilla lock. If you look under that rom you will find people working on it but no solutions have worked. He announced a new version for later this week, maybe he will add it but not sure if its possible, something to do with the .6 framework. Someone in the forum got the vanilla rotary lock to work somehow though.
Sent from my HERO200 using XDA App
thank you...
tailsthecat3 said:
i prefer the vanilla lockscreen but i like sense after i unlock.
im running nfinite45x's stock .6 rom with v4 710 oc kernel. is there any way possibly to achieve the vanilla lockscreen?? thank you
Click to expand...
Click to collapse
Easily done. Pull the android.policy.jar file from the newest fresh rom and push it to ur phone then delete the htclockscreen.apk from ur phone. U can do the same thing with the rotary lock from my blue echo rom. Then to get the oc u can dl darchshiz #4 or #15. Difference is #15 has undervolt included. Find it in the development forum
Papa Smurf151 said:
Easily done. Pull the android.policy.jar file from the newest fresh rom and push it to ur phone then delete the htclockscreen.apk from ur phone. U can do the same thing with the rotary lock from my blue echo rom. Then to get the oc u can dl darchshiz #4 or #15. Difference is #15 has undervolt included. Find it in the development forum
Click to expand...
Click to collapse
that easy huh? enter adb and push? then rm htclock? im using #4 and my device is super fast/responsive.
wait, can i get the policy file via windows? i dont have to install fresh...?...
thanks!
edit: im using infinite's .6 odex version...
tailsthecat3 said:
that easy huh? enter adb and push? then rm htclock? im using #4 and my device is super fast/responsive.
wait, can i get the policy file via windows? i dont have to install fresh...?...
thanks!
edit: im using infinite's .6 odex version...
Click to expand...
Click to collapse
U might have to find fresh rom that is odexed and pull the file from there but yeah u can open it from windows using 7zip. Go to system/framework and ull find it there. Then push via adb to the same place. I know fresh had an odexed version of his ron out. Its not .6 its .5 but there isn't any difference with the android policy files. I'm using the rotary lock from a .5 version on my .6 rom and there is no differences
Well if papa smurf says...
Papa Smurf151 said:
U might have to find fresh rom that is odexed and pull the file from there but yeah u can open it from windows using 7zip. Go to system/framework and ull find it there. Then push via adb to the same place. I know fresh had an odexed version of his ron out. Its not .6 its .5 but there isn't any difference with the android policy files. I'm using the rotary lock from a .5 version on my .6 rom and there is no differences
Click to expand...
Click to collapse
alright then the search is on for an odex fresh...seems like the first step
edit: thanks for the help. hopefully ill have the vanilla lockscreen tonight
I have nfinite45x rom and have the vanilla lock screen. I have had it since I downloaded his rom. I have the deoxed version, so dont know if this method will help but....
http://forum.xda-developers.com/showthread.php?t=665652
Do option 2, thats what I did and it is working fine. Do a nandroid before trying just in case.
Related
Check out Fightspit's original thread:
You can see the different styles here:
http://forum.xda-developers.com/showthread.php?t=724778
Check out bahnburner's Evo 4G Black Bar Mod Thread:
You can see how it looks here:
http://forum.xda-developers.com/showthread.php?t=744524
backup your framework-res.apk before you flash
"adb pull /system/framework/framework-res.apk", or you can you a file manager and copy it to your sdcard right on the phone.
How to install:
this does not work with rom manager
copy the file over to the root of your sdcard, rename it update.zip, reboot into recovery mode, select "reinstall packages"
I897UCJH7 / I897UCJH3 / I897UCJH2 / I897UCJF6 (captivate only)
Version A: http://www.ponack.net/designgears/battery_mod/I897UC_version_a.zip
Version B: http://www.ponack.net/designgears/battery_mod/I897UC_version_b.zip
Version C: http://www.ponack.net/designgears/battery_mod/I897UC_version_c.zip
Version D: http://www.ponack.net/designgears/battery_mod/I897UC_version_d.zip
Version E: http://www.ponack.net/designgears/battery_mod/I897UC_version_e.zip
Version F: http://www.ponack.net/designgears/battery_mod/I897UC_version_f.zip
Version G: http://www.ponack.net/designgears/battery_mod/I897UC_version_g.zip
With Evo Black Bar Mod:
Version A: http://www.ponack.net/designgears/battery_mod/I897UC_version_a_EBB.zip
Version B: http://www.ponack.net/designgears/battery_mod/I897UC_version_b_EBB.zip
Version C: http://www.ponack.net/designgears/battery_mod/I897UC_version_c_EBB.zip
Version D: http://www.ponack.net/designgears/battery_mod/I897UC_version_d_EBB.zip
Version E: http://www.ponack.net/designgears/battery_mod/I897UC_version_e_EBB.zip
Version F: http://www.ponack.net/designgears/battery_mod/I897UC_version_f_EBB.zip
Version G: http://www.ponack.net/designgears/battery_mod/I897UC_version_g_EBB.zip
If you like this, please consider buying me a beer!
what about the uninstall?
Awesome!! Worked perfect on my I897UCJH2!
Thanks man and keep it up!
Edit: Now I can remove Battery Indicator and free up some resources!
A.VOID said:
what about the uninstall?
Click to expand...
Click to collapse
backup your framework-res.apk before you flash
astrocrep said:
Awesome!! Worked perfect on my I897UCJH2!
Thanks man and keep it up!
Edit: Now I can remove Battery Indicator and free up some resources!
Click to expand...
Click to collapse
Same here, hated not being able to see the actual percent.
What avout jf6
Sent from my SAMSUNG-SGH-I897 using XDA App
No love for the JF6?
Smallsmx3 said:
What avout jf6
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
kenjindomini said:
No love for the JF6?
Click to expand...
Click to collapse
send me the framework-res.apk... I will kick it out in about 5min
JP3 version works just fine
it applied update.zip fine from recovery but that didn't change anything so pushed it manually and used chmod 644 on it after. rebooted and worked without a problem
Nice work designgears
Tayutama said:
JP3 version works just fine
it applied update.zip fine from recovery but that didn't change anything so pushed it manually and used chmod 644 on it after. rebooted and worked without a problem
Nice work designgears
Click to expand...
Click to collapse
did you use stock recovery or clockwork? clockwork doesnt actually flash anything
got it applied. looks gorgeous.
designgears said:
did you use stock recovery or clockwork? clockwork doesnt actually flash anything
Click to expand...
Click to collapse
ahh might be why since clockwork is built into this JP3... using Paul's version
Btw that JP3 works just fine on a I9000 since that is what i'm using
Can someone pleaseeeee get this mod to work on my European samsung galaxy s I9000 running XWJM5. I will donate 10 dollars if anyone can do it thank you
XeQtuR said:
Can someone pleaseeeee get this mod to work on my European samsung galaxy s I9000 running XWJM5. I will donate 10 dollars if anyone can do it thank you
Click to expand...
Click to collapse
coming right up
I don't think I can post the apk for jf6. Im a noob. Can someone help
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
coming right up
Click to expand...
Click to collapse
brilliant thank you !!!!!!
So i just moved it straight over onto phone?
XeQtuR said:
Can someone pleaseeeee get this mod to work on my European samsung galaxy s I9000 running XWJM5. I will donate 10 dollars if anyone can do it thank you
Click to expand...
Click to collapse
http://www.multiupload.com/YX3NOYCZSU
there ya go, let me know how it goes...
JakeH said:
So i just moved it straight over onto phone?
Click to expand...
Click to collapse
read the "how to isntall" on the OP
Call me an idiot but I can't figure out how to install this...
Via ROM Manager (recovery mode update.zip)?
Or from the phone itself? When I try to run the apk I get "Application Not Installed"
Smallsmx3 said:
I don't think I can post the apk for jf6. Im a noob. Can someone help
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
copy /system/framework/framework-res.apk using root explorer to /sdcard/sd so it is viewable when you connect your phone to windows and mount it for data transfer. then you can copy it to your computer.
I wouldve done it already but my drivers crapped out on the work lappy and now its time to leave work.
If no one gets this done by the time I log on tonight from home, I will upload the jf6 framework-res.apk
kenjindomini said:
copy /system/framework/framework-res.apk using root explorer to /sdcard/sd so it is viewable when you connect your phone to windows and mount it for data transfer. then you can copy it to your computer.
I wouldve done it already but my drivers crapped out on the work lappy and now its time to leave work.
If no one gets this done by the time I log on tonight from home, I will upload the jf6 framework-res.apk
Click to expand...
Click to collapse
twframework-res.apk is the closest thing I found - hopefully that's it
EDIT: this is pulled from a JF6
http://www.mediafire.com/?1ysidnz56t3s86m
This was packaged with an early version of voodoo lag fix - and i believe it is part of SRE - not sure who the author is - DG maybe?
It is the stock blue battery meter with a number in the middle and about 25 increments instead of the stock 4.
This would be a great update.zip or apk.
Anyone know where to get this by itself?
just grab the framework-res.apk from /system/app from SRE and put it in the same place on your phone
Thanks!
For some reason i thought there was more to it then that.
update.zip
here you go- just tested on stock and it works fine. thanks for the idea, and credit to the original icon set creator
Thank you.
thanks for this!
can i see a screenie of it in action?
how do i install this? i'm a bit of a noob when it comes to theming , for now.
Little Dragon said:
thanks for this!
can i see a screenie of it in action?
how do i install this? i'm a bit of a noob when it comes to theming , for now.
Click to expand...
Click to collapse
to install, copy the zip over to the root of your sdcard, reboot into recovery mode and select "reinstall packages"
designgears said:
just grab the framework-res.apk from /system/app from SRE and put it in the same place on your phone
Click to expand...
Click to collapse
I just tried that, no luck, would it be easier to just run it as the update.zip root method, then reinstall packages? Or maybe DroidExplorer was just being a POS again and didn't copy my files.
will this work on my I9000 Eclair rom??
Little Dragon said:
will this work on my I9000 Eclair rom??
Click to expand...
Click to collapse
I installed the framework-res.apk and it messed up my phone with JM8. I had to restore with clockwork.
EDIT: Tried using the update.zip file through recovery and gave me an error.
Thank you, i was looking for this
For some reason my sound isn't working after installing this. How do I uninstall this to check if it's my problem?
Sent from my SAMSUNG-SGH-I897 using XDA App
RuizGT said:
For some reason my sound isn't working after installing this. How do I uninstall this to check if it's my problem?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You just need to replace the new framework-res.apk with the original. If you did not back yours up, there is a stock one located here. You can use an update.zip if it is easier for you that way.
illestChronicle said:
I installed the framework-res.apk and it messed up my phone with JM8. I had to restore with clockwork.
EDIT: Tried using the update.zip file through recovery and gave me an error.
Click to expand...
Click to collapse
can anyone else confirm?
edit: just tried with my Eclair i9000 mod and it gave me an error 7 in recovery mode
Little Dragon said:
can anyone else confirm?
edit: just tried with my Eclair i9000 mod and it gave me an error 7 in recovery mode
Click to expand...
Click to collapse
i think you'll have to take your own framework-res and modify it with the graphics and xml source files manually to get it working. they can be taken from the sre apk
can you get this to be the default green? or maybe like black with white lettering.
This is great. Worked perfectly and its clean looking! Gracias!!!
Xtwo007 said:
i think you'll have to take your own framework-res and modify it with the graphics and xml source files manually to get it working. they can be taken from the sre apk
Click to expand...
Click to collapse
EDIT: Nevermind
Thanks! The update.zip worked great.
Can anyone confirm this works on JH7?
This is kennethpenn's stock system.img from BriefMobile. I deodexed the system and framework and rooted it.
This is a stock deodexed app and framework. That is all. Use ./moto-fastboot flash system system.img to install it. I made this so i can keep data as i continue to build from stock up. If something gets borked i just flash the .img and start over will all data and most settings in tact. I am posting it to share for anyone who wants to have a stock deodexed image to base their personal rom off of. Begin with the deodexed system and hack away. if you break something flash the system again and keep all data.
Thanks to ...
kennethpenn for stock 4.5.91
Jug6ernaut for doo iit
s0dhi for the extra push
and xeudoxus for xUltimate
DOWNLOAD HERE
this one address the issue when batteries apk/odex been deodexed?
@PAulyhoffman
Would you be kind to do the same for the ORFR 2.3.4 please?
FabricioGS said:
@PAulyhoffman
Would you be kind to do the same for the ORFR 2.3.4 please?
Click to expand...
Click to collapse
Perhaps tomorrow
mramirezusa said:
this one address the issue when batteries apk/odex been deodexed?
Click to expand...
Click to collapse
No, this is basically stock. you will want to flash Jug6ernaut fix 2 on top of this if you want. or adb push the files
PAulyhoffman said:
Perhaps tomorrow
Click to expand...
Click to collapse
Thank you!
PAulyhoffman said:
This is kennethpenn's stock system.img from BriefMobile. I deodexed the system and framework and rooted it.
Click to expand...
Click to collapse
Cold you also create a CWM update zip with this kernel? Would be so much easier to use it. [email protected]!
xploited said:
Cold you also create a CWM update zip with this kernel? Would be so much easier to use it. [email protected]!
Click to expand...
Click to collapse
If you want a cwm zip of the system it is basically the same thing as Kennethpenn's beta 4.5. IMO cwm is more of a PITA than fastboot ever will be.
I won't have to because faux123 already did HERE
PAulyhoffman said:
If you want a cwm zip of the system it is basically the same thing as Kennethpenn's beta 4.5. IMO cwm is more of a PITA than fastboot ever will be.
I won't have to because faux123 already did HERE
Click to expand...
Click to collapse
I have used faux's and edgan's kernels before but I thought it would be nice to have a clean stock one as well in case I need it. (I often revert back and forth between stock and custom stuff).
Anyway, I thought your's is the closest to stock but with deodex and root.
If you say kenneth's is pretty much the same, I will use that.
Can this be flashed on a stock and locked ATRIX running 4.5.91 OTA to deodex using moto-fastboot?
I know it states in the OP to use moto-fastboot, but doesn't clarify if you need to be unlocked or not. I know you can use fadtboot to flash preinstall for root being locked but curious as to the system.img
SGTShark said:
Can this be flashed on a stock and locked ATRIX running 4.5.91 OTA to deodex using moto-fastboot?
I know it states in the OP to use moto-fastboot, but doesn't clarify if you need to be unlocked or not. I know you can use fadtboot to flash preinstall for root being locked but curious as to the system.img
Click to expand...
Click to collapse
You can install this in a rooted phone with locked bootloader
put the system.img on your device /sdcard/
Code:
adb shell
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p12
xploited said:
I have used faux's and edgan's kernels before but I thought it would be nice to have a clean stock one as well in case I need it. (I often revert back and forth between stock and custom stuff).
Anyway, I thought your's is the closest to stock but with deodex and root.
If you say kenneth's is pretty much the same, I will use that.
Click to expand...
Click to collapse
the link i gave was for Stock Kernel. Faux123 uploaded it. did you want a cwm of the system.img? Because yes kenneths is nearly the same.
PAulyhoffman said:
You can install this in a rooted phone with locked bootloader
put the system.img on your device /sdcard/
Code:
adb shell
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p12
Click to expand...
Click to collapse
Thanks. This will be my quick route to deodex!
I'm gonna try this tonight.
Sent from my MB860 using XDA App
i tried from fastboot and it says image is to large...
chaosjh said:
i tried from fastboot and it says image is to large...
Click to expand...
Click to collapse
You need to use moto-fastboot to flash this file.
Sent from my MB860 using XDA Premium App
Can you flash this on 2.2.2 gibgerblur?
Sent from my MB860 using XDA App
Hm...I can only install this through moto-fastboot? Can I install this zip through CWM?
Edit: so nevermind. I was able to install this but I am now missing the settings? Don't know what else could be missing. Any thoughts ?
Edit: Nevermind...I guess it was just a bad flash. I re-flashed it and everything is normal again. Thanks
Exactly what I was looking for. Installed this over rooted stock GB.
@filmusikat After digging around a bit, I decided skipping the moto-fastboot erase recovery command. Just flashed it over the existing system.img. Thanks again!
ghost_og said:
Exactly what I was looking for. Installed this over rooted stock GB.
@filmusikat After digging around a bit, I decided skipping the moto-fastboot erase recovery command. Just flashed it over the existing system.img. Thanks again!
Click to expand...
Click to collapse
Hey let me know which themes work for u... cuz not all the 4.5.91 themes work for this... when I flashed most of them on this... some things disappeared... like settings..and the camera... pretty weird?
Sent from my MB860 using Tapatalk
Warning! There is a huge risk that you will permanently loose root with no way to regain root. Do not flash s-on before you flash this RUU. You will permanently loose root if you do!!!
Incredible_C_GB_S_VERIZON_WWE_4.06.605.2_Radio_2.1 5.10.07.07_NV.zip - 180.6 MB
MD5 Sum: 096d841530dd2f223ef4a1b701c7d429
Install Instructions:
•Rename the file to PB31IMG.zip
•Drop it on the root of the SD Card
•Boot into the bootloader
•Flash as usual
Next go here* to learn how to get root back. Your phone must still be s-off in order to regain full root.
*Sorry guys link is down. I'll add in the instructions here tomorrow.
Want to contact unrEVOked on IRC about the root situation and how you can help?You can speak to the unrEVOked team live.
Go to: unrEVOked IRC
IRC Instructions:
1. Type in a nickname into the nickname box. This is your name that will be displayed during the chat.
2. Type in the captcha.
3. Press connect.
Once connected the page will load and give some brief info. The page will fully load and you will notice a list of usernames on the right. These are all the people currently in the IRC chat. You will also notice a text box at the very bottom of the page. Just type what you want to ask or say there and press [enter] on your keyboard to send your message. Just wait after you send your message. Someone will soon reply. The IRC is similar to an instant messenger, its just web based.
Hopefully this will help some of you to know where to go to get the info you need for this issue.
Disclaimer Please do not abuse this IRC channel. I'm sure unrEVOked is very busy trying to keep up with all these demands for new root patches. Lets not spoil this line of communication while we have it. Keep your questions clear and to the point. Also try to include only important information during your chat. Most importantly, be respectful and professional.
Click to expand...
Click to collapse
now someone pull the radio from this and post it.
k.electron said:
now someone pull the radio from this and post it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1227215
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
tiny4579 said:
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
Click to expand...
Click to collapse
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
So everybody who did this is unrooted now or what
Ignore: I'm goofy and flashed the old zip instead of the new.
evilstewie23 said:
So everybody who did this is unrooted now or what
Click to expand...
Click to collapse
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
tiny4579 said:
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
Click to expand...
Click to collapse
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.
evilstewie23 said:
So everybody who did this is unrooted now or what
Click to expand...
Click to collapse
Yes if you flash this as is you are now unrooted.
I got the nag on first boot but havent after that
tiny4579 said:
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
Click to expand...
Click to collapse
K thanks guess ill just wait to get this when I unroot for the official ota as soon as it cones out and someone discovers another rooting method for 2.3
davwman said:
I got the nag on first boot but havent after that
Click to expand...
Click to collapse
I rebooted a few times and got it every time. Hmm... I wonder if it's just me. I think I've figured out how to stop it though. Testing to make sure.
EDIT: LOL! I may have flashed the original one I had. Let me double check.
I'm pretty sure I flashed the original instead of the new. I had them named to close to the same. Sorry.
wildstang83 said:
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.
Yes if you flash this as is you are now unrooted.
Click to expand...
Click to collapse
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
tiny4579 said:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
Click to expand...
Click to collapse
+1 just tried it and ADB is disabled.
jermaine151 said:
+1 just tried it and ADB is disabled.
Click to expand...
Click to collapse
Do you know how to edit and repack boot.img files?
If so all you have to do is to unpack and change default.prop to this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
davwman said:
I got the nag on first boot but havent after that
Click to expand...
Click to collapse
Okay, after enough reboots I can say the following about the location nag:
1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.
2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag after every reboot. I guess we'll have to hack it to get rid of that.
3) If "Fast Boot" is disabled and you power down, then boot up, you get nagged.
I still see no reason why they delayed the OTA since nothing seems to be changed.
tiny4579 said:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
Click to expand...
Click to collapse
jermaine151 said:
+1 just tried it and ADB is disabled.
Click to expand...
Click to collapse
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
jermaine151 said:
Okay, after enough reboots I can say the following about the location nag:
1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.
2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag again. I guess we'll have to hack it to get rid of that.
I still see no reason why they delayed the OTA since nothing seems to be changed.
Click to expand...
Click to collapse
Maybe because of the wifi issue. Has anybody checked to see if we have wifi back now?
wildstang83 said:
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
Click to expand...
Click to collapse
Yep, that's with USB debugging enabled.
tiny4579 said:
Do you know how to edit and repack boot.img files?
If so all you have to do is to unpack and change default.prop to this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
Click to expand...
Click to collapse
Are you saying you got adb to be enabled?
Here is the OTA update zip.
http://www.androidfilehost.com/?fid=22946563261203148
d0c70dc593bdd729b14688a1be473102
http://tinyw.in/RwRh
d0c70dc593bdd729b14688a1be473102
Dammit, beat me to the punch lol. Thanks bud!
Sent from my SPH-L720 using Tapatalk 2
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
shabbypenguin said:
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
Click to expand...
Click to collapse
Will do. Running a backup right now and will install after that.
Putting stock back on.
Wiping Data
Installing update
Yep it is blocked.
crawrj said:
Yep it is blocked.
Click to expand...
Click to collapse
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
shabbypenguin said:
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
Click to expand...
Click to collapse
Yeah I plan on it. Attached the gz.
Pulling source now to run a diff and see what has changed in kernel beyond the obvious.
Be interested to see if they left that in the defconfig since they know someone will probably flip it back.
anyone check to see if kies would update em? would be a nice thing to have the tar for it as well
Just to confirm the obvious rooting did not work.
Installing the stock MDC kernel allows rooting.
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Well, that diff was actually productive.
They have made the change in the common defconfig for all i9505 variants.
So expect this to be coming to the rest of them soon.
Looks like on the kernel side a majority of the changes are to 3 files:
firmware/ssp_rev03.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1_fac.fw.ihex
Beyond those 3, many of the changes pertain to ATT and EUR variants.
Attaching a zip of the diff file for reference as I'll be spreading the word.
Guess I'll get with Agat to make an MDL kernel with that flipped off...
*Update 2* As Shabby mentioned, only Tmo and Sprint have seen this so far... so AT&T results can be ignored.
www.shabbypenguin.com/OUDstuff/Sams...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
sorry for teh delay, had to make breakfast for my daughter this is a MDL source built kernel, but with MDC ramdisk until i can get MDL ramdisk. it will allow root however
shabbypenguin said:
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Click to expand...
Click to collapse
The boot.img is in the update.zip already. Or do you still need it DD?
crawrj said:
The boot.img is in the update.zip already. Or do you still need it DD?
Click to expand...
Click to collapse
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
I haven't looked at the at&t threads but I would say they are wrong. You can install root but the kernel kills it. So it won't run. I have tried all three methods of install and it doesn't work.
1. Installing custom recovery and flashing supersu
2. Oding CFAutoRoot
3. Moto
shabbypenguin said:
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Click to expand...
Click to collapse
So you have the new kernel working? Where is that same old link again And thanks!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
crawrj is correct, its not a matte rof re-rooting its the binary is being killed as it tries to launch. att didnt get it in an update yet, only tmo and sprint for the us carriers.
crawrj said:
So you have the new kernel working? Where is that same old link again And thanks!
Click to expand...
Click to collapse
http://www.shabbypenguin.com/OUDstu...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
I have not rooted yet and im trying to push the OTA update now. once it goes through, you want me to try one of the rooting methods???