Related
Can anyone help me, i've found some boot animations of android peeing on apple logo, but i cannot get it to work. Any help?
kpkimmel said:
Can anyone help me, i've found some boot animations of android peeing on apple logo, but i cannot get it to work. Any help?
Click to expand...
Click to collapse
What you need?
how do i do it, i downloaded a signed zip of the android pee.zip and flash it via recovery but it doesn't work
kpkimmel said:
how do i do it, i downloaded a signed zip of the android pee.zip and flash it via recovery but it doesn't work
Click to expand...
Click to collapse
Flash in recovery mode? where did you read that you have to flash it? They clearly said to push it to the resource folder in the system.
Go back and read well please
could you point me to the thread. Thanks
Here is what you need to do:
Turn on USB Debug in your phone
Place the bootanimation.zip in your sdk/tools folder
CMD to your sdk/tools and do the commands:
1. adb devices - make sure your phone appears in the cmd window
2. adb remount
3. adb push bootanimation.zip /system/customize/resource/
4. adb reboot
where did you find the boot animation.zip..colnd't find that one
kpkimmel said:
where did you find the boot animation.zip..colnd't find that one
Click to expand...
Click to collapse
Rename the one you got with the name in the guide list I gave you.
says connot stat no such file or directory
kpkimmel said:
says connot stat no such file or directory
Click to expand...
Click to collapse
wat
yup, dont' get it
can you point me toward the one that works for evo
thanks, got it working, its the apple logo then droid eats and ****s it out..awsome..
sry to hijack the thread but how can i make a boot animatuon with the same white screen with the htc evo 4g and then instead of the sprint animation it goes into the nexus one animation?
Kykiskly you look familiar but anyway thanks for those commands I'll try them later.
Also got the one where the droid pees on the apple logo....luv it.....F U apple and your overpriced garbage.
gqstatus0685 said:
Kykiskly you look familiar but anyway thanks for those commands I'll try them later.
Click to expand...
Click to collapse
What you mean I look familiar?
Kykiskly said:
Here is what you need to do:
Turn on USB Debug in your phone
Place the bootanimation.zip in your sdk/tools folder
CMD to your sdk/tools and do the commands:
1. adb devices - make sure your phone appears in the cmd window
2. adb remount
3. adb push bootanimation.zip /system/customize/resource/
4. adb reboot
Click to expand...
Click to collapse
Followed those steps but for some reason the custom boot didn't load. I'm using Fresh's latest ROM and I still see his splash screen. Followed directions to a T.
gqstatus0685 said:
Followed those steps but for some reason the custom boot didn't load. I'm using Fresh's latest ROM and I still see his splash screen. Followed directions to a T.
Click to expand...
Click to collapse
The bootanimation is in /system/media on Fresh.
As a side note/favor. Where did you find that animation? I'd like to check it out.
Ok so i have looked at all the other posts on how to change the boot screen animation, but none of them seem to work. My phone is running on Android 2.2. Does anybody have any ideas on what i should do?
I JUST did this and it worked for me. I am on the 8/1 2.2 leak as well.
Plug in phone
reboot to recovery
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
It will give you this error. Thats fine (It's just saying it couldnt mount the sdcard which we dont need right now.)
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
now type exit to get back to your computer prompt.
Now push your bootanimation.zip you want to /system/customize/resource
Code:
adb push bootanimation.zip /system/customize/resource
now now get back in to adb shell and type
Code:
cd /system/customize/resource
then ls *.zip and it should look like this. l = lowercase L
Code:
/system/customize/resource # ls *.zip
ls *.zip
bootanimation.zip VZW_bootanimation.zip
Now we want to rename the vzw boot animation to .back to save it
Code:
mv VZW_bootanimation.zip VZW_bootanimation.back
Then we want to rename the new bootanimation to the vzw bootanimation
Code:
mv bootanimation.zip VZW_bootanimation.zip
OPTIONAL STEP: IF YOU DONT WANT THE DROID SOUND ON BOOT
Code:
mv Droid.mp3 Droid.back
type exit and adb reboot . It should now boot with your new boot animation.
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Check where I've been posting. Somewhere along the way I was in a thread that worked for me. I just can't remember where.
Utopia73 said:
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Click to expand...
Click to collapse
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
zerf said:
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
Click to expand...
Click to collapse
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Utopia73 said:
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Click to expand...
Click to collapse
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
zerf said:
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
Click to expand...
Click to collapse
Ok did that. Nothing happened
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
zerf said:
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
Click to expand...
Click to collapse
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Utopia73 said:
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Click to expand...
Click to collapse
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
zerf said:
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
Click to expand...
Click to collapse
Well i saw that...maybe its another mount but instead of mounting in prompt i just went to the partitions menu and did it there. Thank you very much!
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Utopia73 said:
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Click to expand...
Click to collapse
where are you seeing this (what directory) and what command are you trying to run?
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
zerf said:
where are you seeing this (what directory) and what command are you trying to run?
Click to expand...
Click to collapse
I was trying to run
Code:
adb push bootanimation.zip /system/customize/resource
Ok, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/customize/resource/bootanimation.zip': No space left on device
So maybe i tried to many times or something.
vbhines said:
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
Click to expand...
Click to collapse
I tried that too, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd
Click to expand...
Click to collapse
I tried that too, now its saying
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Click to expand...
Click to collapse
You have to push it while in Recovery until we have s-off/full NAND. If you're already doing it in Recovery, make sure you've mounted /system first.
Sent from my ADR6300 using XDA App
Hi, First I'm not a clever man, nor do I know what I did to brick it but, I used
"LCD Density Modder" on the market and bricked my phone.
https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&hl=en
My phone is bricked, it won't load anything past "Google", I've taken out the battery and put it back in MULTIPLE times, I've tried to reboot into Recovery Mode and get a red Triangle with an error.
I'm on 4.1.1 GSM model, Rooted and Stock ROM.
Is there anyway to fix this issue without completely wiping out my phone? The last backup I did was a week ago by hand, with click and drag.
Thanks for any help, I would appreciate it.
That's not bricking. And the red android is the stock recovery. Your going to need to flash a recovery and flash another ROM.
Sent From My Toro+ via White Tapatalk
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or this
Sent From My Toro+ via White Tapatalk
Oh, wow, thanks, and that will save my files?
Is there a step by step process? I...am not a clever man =| or if there's a keyword I can search. Thanks...
I'm asking because I can't transfer files via USB to my Galaxy Nexus, nor does my computer detect it.
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Ignore the post I just made,
I found it manually, and rebooted the phone but it's still black screen when I pushe d it to the phone.
"build.prop /system/" sounds wrong though...but I am still shocked I was able to pull it.
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
smartedpanda said:
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
Click to expand...
Click to collapse
So what did you do exactly? Did you pull the file from your ROM first, modify it, and then push it back?
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
smartedpanda said:
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
Click to expand...
Click to collapse
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
It's to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
efrant said:
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
Click to expand...
Click to collapse
- Didn't know it was a hassle, my apologizes. I'll try to do it the old school method.
trevd said:
Its to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I had a feeling it was a permissions issue, but wasn't sure how to fix it.
I'll start pulling up the command prompts...wish me luck, thanks for all the help so far guys. I'll do two backup a week from now on, instead of weekly.
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
smartedpanda said:
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
Click to expand...
Click to collapse
Probably missed this step:
efrant said:
In the CWM menu on your device, navigate the mounts menu and click mount /system
Click to expand...
Click to collapse
efrant said:
Probably missed this step:
Click to expand...
Click to collapse
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
smartedpanda said:
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
Click to expand...
Click to collapse
Did you change the permissions like trevd suggested?
While booted in CWM with /system mounted:
adb shell chmod 0644 /system/build.prop
If that still doesn't work after a reboot, I suggest you re-flash grab the system image for 4.1.1 from Google's site, extract the system.img, reboot your device into the bootloader, and type: fastboot flash system system.img. It won't wipe your device, but it should fix anything that was messed up. (It will also remove root and busybox and whatever else you have installed on the system partition.
)
FINALLY! SUCCESS! I forgot the permission like you mentioned, but it didn't work the first two times, guess I mistyped something, it worked the third time.
I honestly appreciate all the help, and all the inputs. My phone is at 100%, and I'm doing a backup as we speak now.
efrant said:
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Click to expand...
Click to collapse
I know this thread is dead but I would like to say that this is the single most useful post I've seen in ages! I was looking around for nearly an hour and every post resulted in saying "reflash rom"...
Then I saw this, and worked!! My phone is her old self again
thumbs up!
Hi all
I really messed my Kindle Fire up
I was rooting it following steps in this thread: http://forum.xda-developers.com/showthread.php?t=2075959
And i gave me success but nothing happened I still had my carousel kindle fire menu and I tried several times with no succes at all.
Then I read for about 3 hours on different sets and saw that someone rename a file in es file explorer/under system/app called launcher.apk to launcher default.apk. I restarted my kindle fire and here is the problem I can't even get my carousel kindle fire menu up now This time it comes up in black and flashes. So I don't know if it is crached for ever or I can fix this issue.
I just tried to reset to factory default with same result. black screen
Somebody in here know what to do would be appreciated?
Thanks!
Best regards
Frustrated kindle fire user
It's not lost....
You have two methods to fix this
If you can enter adb commands you just need to rename default.apk to launcher.apk..
Our you can just do a complete restore of your device..
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
It's not lost....
You have two methods to fix this
If you can enter adb commands you just need to rename default.apk to launcher.apk..
Our you can just do a complete restore of your device..
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
If I connect my kindle to my pc can I then do adb commands from there or how should I do this, sorry I am a rookie on this ;-(
But thx for qucik answer.
mrkhigh said:
It's not lost....
You have two methods to fix this
If you can enter adb commands you just need to rename default.apk to launcher.apk..
Our you can just do a complete restore of your device..
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
What's the difference between complete restore and the thing I tried with factory defualt settings that did not work?
dkabi said:
What's the difference between complete restore and the thing I tried with factory defualt settings that did not work?
Click to expand...
Click to collapse
Factory reset merely wipes your data partition and caches which removes your personal info and apps.
The SYSTEM partition is untouched (where your launcher is located) so it does you no good.
A complete restore actually will replace your system partition with the stock os. This will recover everything back to stock, including your launcher.
--
Sent from my mind to your screen.
mindmajick said:
Factory reset merely wipes your data partition and caches which removes your personal info and apps.
The SYSTEM partition is untouched (where your launcher is located) so it does you no good.
A complete restore actually will replace your system partition with the stock os. This will recover everything back to stock, including your launcher.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
OK how to make this complete restore? I do not have anything on it which is important?
dkabi said:
OK how to make this complete restore? I do not have anything on it which is important?
Click to expand...
Click to collapse
1. Search before asking. (It's in the xda rules)
2. Get a fastboot cable
3. Here it is. It's a sticky in the dev section. All you had to do was look.
http://forum.xda-developers.com/showthread.php?t=2035047
Edit: I apologize if I sound rude. But, answered the same questions over and over and over and over again. The answers are all available to those that just look. Scroll through the Q&A section and see what I mean.
Edit2: read this before you brick your device:
http://forum.xda-developers.com/showthread.php?t=2228539
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
1. Search before asking. (It's in the xda rules)
2. Get a fastboot cable
3. Here it is. It's a sticky in the dev section. All you had to do was look.
http://forum.xda-developers.com/showthread.php?t=2035047
Edit: I apologize if I sound rude. But, answered the same questions over and over and over and over again. The answers are all available to those that just look. Scroll through the Q&A section and see what I mean.
Edit2: read this before you brick your device:
http://forum.xda-developers.com/showthread.php?t=2228539
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
You not rude it is ok when answering same things over and over again. But now I succeded to connect the kindle again to the laptop and it can see it under devices. So maybe it is much easier to rename the launcher default.apk to launcher.apk but how do I get to the libary where the installed applications are? Then this will proberpably do the job with a restart? Sorry if I am asking to much but would really like my kindle to work again when I am going on job
dkabi said:
You not rude it is ok when answering same things over and over again. But now I succeded to connect the kindle again to the laptop and it can see it under devices. So maybe it is much easier to rename the launcher default.apk to launcher.apk but how do I get to the libary where the installed applications are? Then this will proberpably do the job with a restart? Sorry if I am asking to much but would really like my kindle to work again when I am going on job
Click to expand...
Click to collapse
You will have to use adb commands to rename the file.
This might help:
http://forum.xda-developers.com/showthread.php?t=891270
I believe the commands are like so:
Adb shell
Su
Mv oldfilename newfilename
Replace oldfilename and newfilename with the correct file names
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
You will have to use adb commands to rename the file.
This might help:
http://forum.xda-developers.com/showthread.php?t=891270
I believe the commands are like so:
Adb shell
Su
Mv oldfilename newfilename
Replace oldfilename and newfilename with the correct file names
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Tried to replace as you have written but it comes up with:
failed on launcher - no such file or directory - The original apk file is named launcher.apk last time I checked when my es file explorer worked if I remember correct
This is what I have done:
1. open cmd and goto ....\platform-tools
2. enter command: adb shell
3. enter su (to get superuser access to rename systemfiles)
4. enter mv Launcher default.apk Launcher.apk (also tried without extension same result)
How can I list the files in my installed applications folder on my kindle maybe I can see exactly the correct name so if the default name is launcher.apk when you buy a new kindle fire it can only be the name i have on the kindle fire now which is the problem.
dkabi said:
Tried to replace as you have written but it comes up with:
failed on launcher - no such file or directory - The original apk file is named launcher.apk last time I checked when my es file explorer worked if I remember correct
This is what I have done:
1. open cmd and goto ....\platform-tools
2. enter command: adb shell
3. enter su (to get superuser access to rename systemfiles)
4. enter mv Launcher default.apk Launcher.apk (also tried without extension same result)
How can I list the files in my installed applications folder on my kindle maybe I can see exactly the correct name so if the default name is launcher.apk when you buy a new kindle fire it can only be the name i have on the kindle fire now which is the problem.
Click to expand...
Click to collapse
The command is:
Ls
You can also try adb push to pout the original launcher back
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I just found out almost everything now just need the correct command for renaming correct. I am reading as hell on several pages to get my kindle up and running againg
This is what I have done:
1. open cmd and goto ....\platform-tools
2. enter: command: adb shell
3. enter: su (to get superuser access to rename systemfiles)
4. enter: pm list packages -f kindle
1. Found the package:/system/app/Launcher default.apk=com.amazon.kindle.otter
Tried to rename file from here with following commands:
5. enter: mv Launcher default.apk Launcher.apk (this gave me error: Launcher - No such file or directory)
6. enter: mv Launcher default.old Launcher.old (this gave me error: Launcher - No such file or directory)
7. enter mv Launcher default.apk=com.amazon.kindle.otter Launcher.apk=com.amazon.kindle.otter (this gave me error: Launcher - No such file or directory)
So what am I doing wrong here?
Mv default.apk newfilename.apk
Edit:
Or, may need to be formatted like so:
mv /system/app/oldname.apk /system/app/newname.apk
You just need the path and filename.. all that = stuff and the word launcher is unneccessary
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Mv default.apk newfilename.apk
Edit:
Or, may need to be formatted like so:
mv /system/app/oldname.apk /system/app/newname.apk
You just need the path and filename.. all that = stuff and the word launcher is unneccessary
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Tried both:
mv default.apk Launcher.apk (failed on default.apk - no such file or directory)
mv /system/app/Launcher default.apk /system/app/Launcher.apk (failed on /system/app/Launcher.apk - no such file or directory)
The interesting part here is in second try it fails on the new name and not the old name
We are close but not there yet
I'm not very good at adb commands but try "ls" .. I'm guessing you are not in system/app
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
I'm not very good at adb commands but try "ls" .. I'm guessing you are not in system/app
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I now tried this command to stand in system/app:
ls system/app
And this time I get a list where Launcher default.apk is coming up. This is the wrong name. I would now rename this to Launcher.apk so I get original back but tried all mv commands from last and still did not succeed
Any guess on how the command should be from here? or do you have a original kindle fire 2 launcher (carousel) that I can push back as an alternative maybe?
Just so you can see what I have done from the start this is what I have done in the cmd:
1. open cmd and goto ....\platform-tools
2. enter: command: adb shell
3. enter: su (to get superuser access to rename systemfiles)
4. enter: ls system/app
Then tried all mv commands from before and with no luck yet...
mv /system/app/default.apk /system/app/Launcher.apk
Not sure why you keep adding the word launcher
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
mv /system/app/default.apk /system/app/Launcher.apk
Not sure why you keep adding the word launcher
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Tried that and it fails
Ok. Try.
Cd /system/app
Mv default.apk launcher.apk
Also- for filenames- capitalization has to be exact
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Ok. Try.
Cd /system/app
Mv default.apk launcher.apk
Also- for filenames- capitalization has to be exact
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I tried following:
1. open cmd and goto ....\platform-tools
2. enter: command: adb shell
3. enter: su (to get superuser access to rename systemfiles)
4. enter: cd /system/app
5. enter: mv default.apk launcher.apk (fails on default name)
tried also
6. enter: mv Launcher default.apk Launcher.apk (fails on Launcher name)
It is like it want me to change this name strange or maybe some security issue here?
Keep give me all suggestions I would like this to work as hell
Hi, i installed Rbox's custom recovery earlier. When running the initial coomand from the adb shell i had to run it as su or i received a permission error. After running the reboot recovery command, the device rebooted, displayed the white Amazon logo, and then went to the Amazon update failed screen... after a minute or two it started up fine. Am i doing something wrong. Thanks!
It seems when you did the dd commands it didn't write the recovery. So you either typed the command wrong, or don't have root access which is needed for permission to write to the partition. Did your cursor change from an $ to # after running su?
Luxferro said:
It seems when you did the dd commands it didn't write the recovery. So you either typed the command wrong, or don't have root access which is needed for permission to write to the partition. Did your cursor change from an $ to # after running su?
Click to expand...
Click to collapse
i didn't notice to be honest, but i did get a message on the FireTV saying su access had been granted, and then the text in the shell (after i copied and pasted the command from the thread in) looked as if it worked... no errors. And yes, i had named my file the same as the example and had put it in the same location. Once i ran the reboot recovery command was where i got the Amazon updated unsuccessful screen. i had thought it would just reboot into the recovery menu. Thanks.
tavery said:
i didn't notice to be honest, but i did get a message on the FireTV saying su access had been granted, and then the text in the shell (after i copied and pasted the command from the thread in) looked as if it worked... no errors. And yes, i had named my file the same as the example and had put it in the same location. Once i ran the reboot recovery command was where i got the Amazon updated unsuccessful screen. i had thought it would just reboot into the recovery menu. Thanks.
Click to expand...
Click to collapse
What you saw was the stock FireTV recovery. I'd give it another try and make sure it switches to root access (#).
I started over as suggested and it worked as it was supposed to this time. I obviously must have missed something or had a typo the last time. Thanks for your help!