Database Develop

[Release] HTC Sense Transparent LockScreen

Very old mod. Probably no longer works. Use at own risk. No longer supported by me.
ROOT REQUIRED
ONLY works on ROMS that include HtcLockScreen.odex.
So it wont work if you've flashed lwp patches, Sprint ROMS or anything that removes the .odex file.
-------
Originally created by JsChiSurf over in the Hero forums via my encouragement This version is made for the Eris, it is not the same as the Hero version (which doesn't work properly for us).
This is a modification of the STOCK HTC Sense lockscreen that removes the background so you can see your homescreen behind it.
*Users need to already be comfortable with using 'adb' I won't be providing support on that since there are numerous threads with instructions all around.*
**Before** pushing the apk into that folder, you'll need to FIRST perform the following steps to remove the stock lock wallpapers from loading, as well as any cached custom wallpaper you have applied. You can perform these via adb as listed, or if you have Root Explorer (on the marketplace), you can navigate to the folders listed and delete the items that way.
Code:
adb remount
adb shell
cd /data/misc/lockscreen
rm *
cd /system/customize/resource
rm htc_wallpaper*
exit
Note: You may or may not have anything to delete in /system/customize/resource, so if you get an error message while using adb, don't worry.
HtcLockScreen.zip MD5: 9423D8C3D6CBBF3E084CD185130F9649
*APK NOTE: APKs are case sensitive, be sure you install this without renaming it, or it wont overwrite your original APK*
After you extract the zip to your sdk/tools directory perform the following (case sensitive):
Code:
adb push HtcLockScreen.apk /system/app
adb reboot
If you get "read-only" errors, try "adb remount" OR "adb shell", then, "su", then "mount -o rw,remount /dev/block/mtdblock3 /system" and then the other commands.
EDIT: Clock-less version now available for download! Same instructions apply.
Clock-less Info: **Since some users may have performed the 'experienced users' steps below, an Android image has been added to 'lockscreen_topedge.png' so that it isn't 100% transparent.
If you want to remove this image: First, download the ZIP below with the PNGs, take any one of those and rename it to 'lockscreen_topedge.png, open the lock apk in your favorite zip file manager (winzip, winrar, 7-zip), navigate to "res\drawable-normal-mdpi" and drag your newly-renamed PNG in there. If a dialog pops up, be sure you select the option that has NO compression, this is usually called "Store."**
Make a post if you have any problems NOT related to 'adb.' Again, support is not provided for that.
Clockless Lock.zip MD5: B604B530E02C47DA81AD8B4563BE71D2
__________________
Now some optional additional steps for **experienced users only** (I suck at tech support so if you ask something, I'll try to answer, but no guarantees):
If you put the PNGs included in the zip below into 'com.htc.resources.apk\res\drawable-mdpi', it will remove the HTC "Arc" on the lockscreen. Now, to create your own Arc replacement, all you'll need to do is go into 'HtcLockScreen.apk\res\drawable-normal-mdpi' and change the lockscreen_topedge.png to your liking A much easier change than fiddling with your resources apk everytime and its only 1 image to change, instead of trying to line up three. Of course, if you remove the Arc and do not change your lockscreen_topedge.png, you will have a completely invisible lockscreen, so don't freak yourself out, just make something for that PNG.
*Does not seem to work with Hero or Legend ROMs*

I've used adb push (to change my boot animation) but I can't say I know how to use it.
Can you specify which commands to use?
EDIT: do you have to have root for this?

Yes you have to have root. You would do 'adb install HtcLockScreen.apk'.

wshuman3 said:
You would do 'adb install HtcLockScreen.apk'.
Click to expand...
Click to collapse
waahhh no X_X this isn't an app to be installed. you are overwritting the old one (after youve backed up!) the "install" command installs to data/app, which isn't what we want (but thanks for keepin an eye on the thread for me wshuman3 )
if you put the apk in your sdk\tools directory, then the command would be
Code:
adb push HtcLockScreen.apk system/app
you were correct about needing root tho

oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?

Lemcott said:
oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?
Click to expand...
Click to collapse
please read the first post again before you post. your question is answered in both the thread title as well as the second line.
thanks!

no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?

Lemcott said:
no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?
Click to expand...
Click to collapse
i believe it should still show you the home screen, considering with the normal lock app by htc in order to unlock it with the dot pattern, you have to pull the slider down, then it shows you the pattern. so going off of that, then it should still do the same thing, but instead of showing a pic on the lock screen, it shows the home screen, then you slide it down to unlock, which i would assume that it would then pop up the dot pattern.

ECLIPS3's explanation is entirely correct. locking will not hide your homescreen. but then, if someone wanted to see your homescreen with the normal lockscreen, they would just have to slide down the Arc most of the way and they'd see most of it. not secure either way.
but i dont think thats what you were even worried about Lemcott. but explained it anyway

yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?

Lemcott said:
yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
it will look like the normal lock screen, just transparent. but you could edit the transparent lock screen to look like jameselles, just transparent. im sure someone would be willing to do that for you. i might, just dont have time right now.

I'll give it a whirl, but if anyone wants to race me be my guest, I'm pretty noobish when it comes to android/linux, but I'll give it my best.

Lemcott said:
if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
99.9% sure your senseable lock would be in-tact, just transparent. since your senseable lock's graphics are stored in com.htc.resources.apk and this is only a change to your HtcLockScreen.apk

Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot
and when your phone boots back up, you'll be looking at a shiny new transparent lockscreen.

Arcalyth said:
Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Click to expand...
Click to collapse
NOTE!: the code is case sensitive, make sure you capitalize as follows:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot

When I try this I always get the nexus 1 lock screen. I'm running Ivan's latest build.
I will try again on a fresh flash since I have been messing with stuff.
Edit: OK, fresh flash without wiping allowed me to change to the Transparent Lock Screen. Thanks gohamstergo.
btw, I have no idea what I changed to not allow this mod.

@silver: not sure but youre not the only one with the issue. no idea what causes it. seems rare tho

AWW, I thought I was special.
But, If anyone ever needs any "rare issues or bugs" found....

Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!

TheAtheistReverend said:
Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!
Click to expand...
Click to collapse
If read the "advanced" directions in the OP, it basically explains how to do this, even though he was trying to tell you how to AVOID doing that. but I agree, I'd like it too. It would almost be like a security feature cuz only you would know where to swipe to unlock

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.

This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions

Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.

Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html

elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you

Yes this method definitely works. I have market working now and can search for protected apps etc.

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.

he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.

I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/

Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.

LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.

Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?

Yes, it requires an edit to a file that you can only be edited when rooted

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!

OP has been updated with original build.prop

Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input

will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.

Thanks for the reply.

[Mods] Mods by Jewremy - v5! NOTIFICATION POWER WIDGET!!!!!

Oh boy...been working on CM7 and have had a whole bunch of other crap going on. Was forced to deodex to port over a certain something by a certain Mr. DroidJunk. ;]
Also, this is a pretty advanced mod. About 6 hours of amp-fueled work for me to do this right. If you want to kang it, I'll gladly teach you. I know we have a bunch of fledgeling devs on the Droid3.
So. Time to DEODEX - I haven't tried it on an odexed system, but the drop in performance is barely noticeable. Flash steeldroid or figure out how to deodex. The method for the DroidX with XUltimate 2.3.2 works.
v5 has this nifty thing. DroidJunk made it for the Bionic. I ported it to the Droid3, changed it to .9.pngs for the backgrounds and indicators, removed the auto-sync toggle, re-did the layout and moved the data toggle next to Bluetooth.
Honeycomb themed everything, sliding door lock screen...just flash it. You'll see.
Oh, also installs bash and nano as well.
DOWNLOADS
v5 - http://bit.ly/oj0y92
v4 - http://db.tt/w4Qs3QPJ
Make a backup first, then flash in recovery.
If you can't figure out how to do that, go home.
Also added a custom loadpreinstalls.sh to keep shell root after a reboot.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Don't flash this unless you know what you're doing and are comfortable with ADB and rescuing yourself from a brick. Remember, we have an sbf to reflash the Droid3 now. You can disregard the rest of this paragraph, unless you're too lazy to download and learn moto-fastboot, in which case you have just the system dump. Seriously, go get moto-fastboot and the restore files. See that Droid 3 Android Development link above? Click it and find the thread. Worth it. It will save your...phone.
Anyway...
I pulled apart and modified framework-res to my liking
Turned off boot sound.
Car dock stays in portrait as opposed to not rotating at all - tried enabling dock rotation, something about blur breaks the feature and causes the dock to not launch at all.
circle battery with numbers from UOT - uot.dakra.lt
old-style motorola lockscreen (two sliders)
cut animation times in half - Short 75ms, Normal 150ms, Long 300ms
Set lockscreen to skip sliders/slidingdoor if device lock is enabled (pin lock, pattern lock, etc)
Enabled menu key to unlock
A few other mods that I cannot find.
Enabled ethernet connectivity...not sure how to use it, though. My guess is that USB OTG is possible with the right cable.
Modified build.prop to enable AOSP USB notifications, set wifi scan time to 180, CDMA as default mode, increased max events and VM Heap size, couple other things that I don't remember.
Installer is an update.zip - use Droid3 bootstrapper from the market or elsewhere.

That is amazing. Kudos to you. I'm really gunning to try this since it has so many of the things I miss from my OG, but am a little nervous without a proper recovery available yet.
Sent from my Hitchhiker's Guide mark 2

I underdstand this but to an extent care to explain in just a little more detail please and thank you.
Sent from my Droid using XDA App

Awesome work Jewremy. But for some reason, it wont work for me. I was rooted the hard way, even did "su" to ask for perms, and it is still my normal stuff. Also tried to redo root with 1 click, and im rooted (says [email protected]) but i type su and [email protected] ...any other advice?
Edit: I noticed it doesnt do anything after it adb shell. so i did it manually after that point.
No white glow.

saintlikesniper said:
I underdstand this but to an extent care to explain in just a little more detail please and thank you.
Sent from my Droid using XDA App
Click to expand...
Click to collapse
What do you need to know? I decompiled framework-res.apk, modified and recompiled.
Visegrad said:
That is amazing. Kudos to you. I'm really gunning to try this since it has so many of the things I miss from my OG, but am a little nervous without a proper recovery available yet.
Sent from my Hitchhiker's Guide mark 2
Click to expand...
Click to collapse
My script backs the originals up for you. Just push them back if you need.
Meibs said:
Awesome work Jewremy. But for some reason, it wont work for me. I was rooted the hard way, even did "su" to ask for perms, and it is still my normal stuff. Also tried to redo root with 1 click, and im rooted (says [email protected]) but i type su and [email protected] other advice?
Click to expand...
Click to collapse
Not sure what's going on. I'll take a look. You do need to have busybox installed, but the 1-click root did that for you. The script backs everything up for you and puts the modded files at /sdcard/modkit/, so you might as well run it manually. Here's the code to run in adb shell. You can do it from your phone, but skip the "stop" command in that case.
Code:
su
stop
busybox mount -o remount,rw /system
busybox cp /sdcard/modkit/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
busybox cp /sdcard/modkit/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
busybox cp /sdcard/modkit/build.prop /system/build.prop
reboot
Also, make sure you don't have Mass Storage mode on. Put it in Charge only, otherwise it'll fail (can't write to SDcard if it can't see it.)

You could just use root explorer and overite the 3 files also. Worked great for me.

im a noob so...once i do this mod, will there be any way to go back just in case?

suzook said:
You could just use root explorer and overite the 3 files also. Worked great for me.
Click to expand...
Click to collapse
Bad idea. Too much can go wrong.
Sent from my DROID3 using Tapatalk

Jewremy i need help

Would this work on the DX2?

im bootlooping after trying the root explorer method -__- it happened after i replaced SystemUI.apk how can i fix this.

royolpunk said:
Jewremy i need help
Click to expand...
Click to collapse
Okay. What do you want me to do?
skwoodwiva said:
Would this work on the DX2?
Click to expand...
Click to collapse
No. Don't even try it. You'll have to SBF

royolpunk said:
im bootlooping after trying the root explorer method -__- it happened after i replaced SystemUI.apk how can i fix this.
Click to expand...
Click to collapse
Try to get ADB access, push your originals back. Might not be able to push to /sdcard, in which case push to /data/local then cp from there. Don't forget to chmod 644 /system/app/SystemUI.apk

i can't get adb access. for some reason...

can't get adb access..

royolpunk said:
can't get adb access..
Click to expand...
Click to collapse
You try BP tools forum.xda-developers.com/showthread.php?t=1236465

yeah. its bootlooping and i tried bp tools

I saw it the first time. No need to repeat yourself. Try the thread in the dev forum for rescuing.

People shouldnt be messing with system files until we get an sbf file, or at the very least a custom recovery. Too many things can go wrong.

There's a typo in the first line of the script
adb pull /system/framework/framwork-res.apk framework-res.orig

Next Launcher crash Loop

Okay, so I feel like I'm right on the cusp of figuring this out but I just can't seem to get the last few steps to work, here is where I'm at.
I have a successfully rooted kindle Fire 2nd Gen. Running on 10.3.1. I installed Next Launcher and it is a nightmare, crashes and loops back after hitting okay. Nothing has fixed it so I found this comment yesterday...
onemeila said:
Since you have root access you can use adb to remove a system apk,
Use these commands:
Code:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
mount -o remount,ro -t rfs /dev/stl5 /system
If you need to look up a list of apk names on the device:
Code:
cd /system/app
ls *.apk
Hope this works for you.
Click to expand...
Click to collapse
I followed everything to a tee. When I get to the point where I enter: rm -r /system/app/[AppName].apk
I listed the apps installed and Next launcher shows up as: "Next LAuncher 3D" so I entered: rm -r /system/app/Next LAuncher 3D.apk
Yes, I've tried without spaces, underscores, everything, nothing. How can I get my CMD to read the launcher so I can delete it, cause my kindle is useless right now. Any help guys, many thanks.

rekindle said:
Okay, so I feel like I'm right on the cusp of figuring this out but I just can't seem to get the last few steps to work, here is where I'm at.
I have a successfully rooted kindle Fire 2nd Gen. Running on 10.3.1. I installed Next Launcher and it is a nightmare, crashes and loops back after hitting okay. Nothing has fixed it so I found this comment yesterday...
I followed everything to a tee. When I get to the point where I enter: rm -r /system/app/[AppName].apk
I listed the apps installed and Next launcher shows up as: "Next LAuncher 3D" so I entered: rm -r /system/app/Next LAuncher 3D.apk
Yes, I've tried without spaces, underscores, everything, nothing. How can I get my CMD to read the launcher so I can delete it, cause my kindle is useless right now. Any help guys, many thanks.
Click to expand...
Click to collapse
Try com.gtp.nextlauncher.apk or com.gtp.nextlauncher-1.apk

No go. . .
BELASCO said:
Try com.gtp.nextlauncher.apk or com.gtp.nextlauncher-1.apk
Click to expand...
Click to collapse
Neither worked. I just don't get it, I've tested using the same method on other apps, works like a charm. For this one, no go.

rekindle said:
Neither worked. I just don't get it, I've tested using the same method on other apps, works like a charm. For this one, no go.
Click to expand...
Click to collapse
Just tried it myself; also no go. It returned a line that looked terribly like it was blowing a raspberry at me. Hopefully someone cleverer than myself will chime in.

BELASCO said:
Just tried it myself; also no go. It returned a line that looked terribly like it was blowing a raspberry at me. Hopefully someone cleverer than myself will chime in.
Click to expand...
Click to collapse
Me too, I hope someone knows cause I've researched, this hasn't come up much at all.

Try
Code:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
cd system
cd app
rm -r "Next LAuncher 3D.apk"
mount -o remount,ro -t rfs /dev/stl5 /system
Sent from my air conditioner unit running ParanoidAndroid

Do you have any time between crashes? Or any launcher ability?
I had that error with the keyboard so that it crashed but I could get one button press per crash and remedied it that way...if also assume a reset to factory defaults would fix it in the kindle recovery...it would reset your default launcher b ut WARNING RESET TO FACTORY DEFAULT WILL TURN OFF ADB
Sent from my GT-P3110 using xda app-developers app

mrkhigh said:
Do you have any time between crashes? Or any launcher ability?
I had that error with the keyboard so that it crashed but I could get one button press per crash and remedied it that way...if also assume a reset to factory defaults would fix it in the kindle recovery...it would reset your default launcher b ut WARNING RESET TO FACTORY DEFAULT WILL TURN OFF ADB
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I have a solution step 1. Download kindle fire first aide and follow all directions exactly as they are written. (Link on bottom of page) step 2. Once completed all of the necessary steps open up KF First aide and click y then enter. Step 3. Go down to option 13 (backup entire kindle to kindlebackups folder) and follow the easy instructions on screen. This will take a little bit so be patient. Step 4. Find (restore entire kindle from kindle backups folder). Follow the onscreen instructions for restoring the Kindle. Make sure the computer is plugged in and the Kindle won't accidentally get unplugged from the computer during this process. When it asks you if you would like to instal blank partition always click y. WHEN IS SAYS WIPE USER DATA AND CASH CLICK Y. Follow all the on screen instructions carefully. If this doesn't work tell me I have one more thing but it should.
http://forum.xda-developers.com/showthread.php?t=2096888

Next Launcher is buggy. The last three updates they've come out with have all addressed bug fixes and FC's. It's a work in progress and they know it's still buggy. You can either keep Next and wait for updates if the bugginess is tolerable or grab a different launcher for now and go back to it at some point in the future.

droidit! said:
next launcher is buggy. The last three updates they've come out with have all addressed bug fixes and fc's. It's a work in progress and they know it's still buggy. You can either keep next and wait for updates if the bugginess is tolerable or grab a different launcher for now and go back to it at some point in the future.
Click to expand...
Click to collapse
listen to me very carefully bcause im freaking out right now. Forget about ever getting next launcher. I tried it yesterday put it in my system app folder. Restarted the kindle fire hd and now im in a boot loop. Yep im soft bricked forget about this launcher.

Well, take a breath and take your time, you're not hard bricked or nothing. Just use what you know (you had a pretty good post above), and I'm sure you'll get out of it fine. If you get stuck at any point along the way just let somebody know. That's what a lot of the community is here for. I have bricked a Kindle (hard bricked ) before, just don't rush. Oh BTW, there's no need to make a launcher a system app, they work just fine installing like any other app and then just wiping data from original launcher :thumbup:

DroidIt! said:
Well, take a breath and take your time, you're not hard bricked or nothing. Just use what you know (you had a pretty good post above), and I'm sure you'll get out of it fine. If you get stuck at any point along the way just let somebody know. That's what a lot of the community is here for. I have bricked a Kindle (hard bricked ) before, just don't rush. Oh BTW, there's no need to make a launcher a system app, they work just fine installing like any other app and then just wiping data from original launcher :thumbup:
Click to expand...
Click to collapse
Yes but does that work for kindle fire hd. It didn't allow picking default launcher unless in system apps. And by the way I am now un bricked. For some reason after turning it on to try something to fix it the app actually started to work thus allowing the Kindle to actually boot up. I deleted the app right away and that completely fixed it no more boot loop. I must be one of the only people to have there kindle fire hd 7 UN brick itself!!!

Hmm, that's strange. Might want to try downloading a launcher from the play store, just stay on the page until it finishes downloading and then hit open on the app page in the play store. Then hit your home button, an option should pop up asking you which launcher you want to use. If that doesn't work, you could try going to the default launcher in your app manager and deselect it as the default app for launching (do all that after installing new launcher).

DroidIt! said:
Hmm, that's strange. Might want to try downloading a launcher from the play store, just stay on the page until it finishes downloading and then hit open on the app page in the play store. Then hit your home button, an option should pop up asking you which launcher you want to use. If that doesn't work, you could try going to the default launcher in your app manager and deselect it as the default app for launching (do all that after installing new launcher).
Click to expand...
Click to collapse
Yes that would work on a normal device but the Kindle Fire is running a forked version of androud 4.0.3. Amazon found a way to stop the default launcher popup from happening unless you put it us system apps. Amazon is stupid like that.

JORDANZ1998 said:
Yes that would work on a normal device but the Kindle Fire is running a forked version of androud 4.0.3. Amazon found a way to stop the default launcher popup from happening unless you put it us system apps. Amazon is stupid like that.
Click to expand...
Click to collapse
IDK, I wrote that cause that's the way it worked for me. So if it doesn't work for you, then honestly, I'm at a deadend for ideas
from my Viped out one x

DroidIt! said:
IDK, I wrote that cause that's the way it worked for me. So if it doesn't work for you, then honestly, I'm at a deadend for ideas
from my Viped out one x
Click to expand...
Click to collapse
Well try running it in CyanogenMod, or Kinology.
Sent from my air conditioner unit running CyanogenMod

dugoy13 said:
Well try running it in CyanogenMod, or Kinology.
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Yeah, like I said, I've run it on every ROM I've tried and it's always worked straight away no problems :thumbup:

DroidIt! said:
Yeah, like I said, I've run it on every ROM I've tried and it's always worked straight away no problems :thumbup:
Click to expand...
Click to collapse
Do either of you guys own a Kindle???
BTW I'm running stock is

JORDANZ1998 said:
BTW I'm running stock is
Click to expand...
Click to collapse
Well that would have been nice to know like 2 days ago, that makes a big difference. If you're stock it has to be in system/app. You need to find the apk off the internet, put it in system/app and change permissions to read/write -->read-->read. Don't install the app just place it in system/app, change the permissions and reboot. You should automatically get a pop up then asking which launcher you want to use.

DroidIt! said:
Well that would have been nice to know like 2 days ago, that makes a big difference. If you're stock it has to be in system/app. You need to find the apk off the internet, put it in system/app and change permissions to read/write -->read-->read. Don't install the app just place it in system/app, change the permissions and reboot. You should automatically get a pop up then asking which launcher you want to use.
Click to expand...
Click to collapse
Should I change all the third party apps in my system app folder to rw-r-r. And what does this do exactly. Because Utah I never changed the permissions for next launcher 3d all were selected like r-w-e-r-w-e-r-w-e is this what put my kindle into the boot loop before not changing the permissions.

wpa_supplicant keeps getting replaced

Hi
I have successfully rooted my phone and have taken the wpa_supplicant.conf file from my previous phone, I have copied it through adb numerous times and everytime I reboot it is replaced with a blank file.
I tried copying it through twrp which partially worked; the file was full however wifi would not work. I checked and this was because the permissions were set to root:root, I switched it to system:wifi and rebooted. No go the file was replaced with a blank one... at least wifi is working again!
Is there another part of the phone that is checking the file and reverting it? I have trawled google and struggled to find anything similar.
thanks

horse178 said:
Hi
I have successfully rooted my phone and have taken the wpa_supplicant.conf file from my previous phone, I have copied it through adb numerous times and everytime I reboot it is replaced with a blank file.
I tried copying it through twrp which partially worked; the file was full however wifi would not work. I checked and this was because the permissions were set to root:root, I switched it to system:wifi and rebooted. No go the file was replaced with a blank one... at least wifi is working again!
Is there another part of the phone that is checking the file and reverting it? I have trawled google and struggled to find anything similar.
thanks
Click to expand...
Click to collapse
you can try to change the owner and group of the file to wifi:
PHP:
mount -o rw,remount /system
chown wifi:wifi /data/misc/wifi/wpa_supplicant.conf
ls -la /data/misc/wifi/wpa_supplicant.conf
-rw-rw---- wifi wifi 2343 2016-07-11 10:31 wpa_supplicant.conf

kativiti said:
you can try to change the owner and group of the file to wifi:
PHP:
mount -o rw,remount /system
chown wifi:wifi /data/misc/wifi/wpa_supplicant.conf
ls -la /data/misc/wifi/wpa_supplicant.conf
-rw-rw---- wifi wifi 2343 2016-07-11 10:31 wpa_supplicant.conf
Click to expand...
Click to collapse
Thanks, I have just tried this and it also doesn't work. The phone is presently locked to vodafone, and there is always an entry in the replaced supplicant file that is "VodafoneWiFI". Also even though the phone is rooted I have removed the stock facebook app amongst others and everytime I reboot these are replaced like nasty little viruses lol.

horse178 said:
Thanks, I have just tried this and it also doesn't work. The phone is presently locked to vodafone, and there is always an entry in the replaced supplicant file that is "VodafoneWiFI". Also even though the phone is rooted I have removed the stock facebook app amongst others and everytime I reboot these are replaced like nasty little viruses lol.
Click to expand...
Click to collapse
Stock rom will reinstall all stock apps on reboot.
try this
PHP:
su -c "cat /data/misc/wifi/wpa_supplicant.conf > /storage/sdcard1/wifi-networks.txt"
Make the necessary changes and revert
PHP:
su -c "cp /storage/sdcard1/wifi-networks.txt /data/misc/wifi/wpa_supplicant.conf"
you should be able to see the info inside the .conf file with any notepad and recover the passwords

kativiti said:
Stock rom will reinstall all stock apps on reboot.
try this
PHP:
su -c "cat /data/misc/wifi/wpa_supplicant.conf > /storage/sdcard1/wifi-networks.txt"
Make the necessary changes and revert
PHP:
su -c "cp /storage/sdcard1/wifi-networks.txt /data/misc/wifi/wpa_supplicant.conf"
you should be able to see the info inside the .conf file with any notepad and recover the passwords
Click to expand...
Click to collapse
Ahh so there's not much I can do against the stock rom to prevent it from reinstalling apps apart from flashing a custom rom? I suppose the stock rom is replacing the file also? thanks for the above although recovering the passwords isn't my problem I was hoping to have it use the new configuration and not have to put passwords everytime I connect to a network I have been to before.
I was amassing quite the city network lol

horse178 said:
Ahh so there's not much I can do against the stock rom to prevent it from reinstalling apps apart from flashing a custom rom? I suppose the stock rom is replacing the file also? thanks for the above although recovering the passwords isn't my problem I was hoping to have it use the new configuration and not have to put passwords everytime I connect to a network I have been to before.
I was amassing quite the city network lol
Click to expand...
Click to collapse
you can try and copy paste like i said.
apps like facefook you can disable them.
go to apps>all>facebook
close disable and wont show.

kativiti said:
you can try and copy paste like i said.
apps like facefook you can disable them.
go to apps>all>facebook
close disable and wont show.
Click to expand...
Click to collapse
Success! Apparently copy and paste works any ideas why? or that it's just picky? Thanks very much, and I had forgotten disable was possible which will have to do till I s-off and remove it totally.

horse178 said:
Success! Apparently copy and paste works any ideas why? or that it's just picky? Thanks very much, and I had forgotten disable was possible which will have to do till I s-off and remove it totally.
Click to expand...
Click to collapse
it works because its the same file (permitions intact) you just put more info