Related
I rooted my phone with Unrevoked 3.21 and successful, but when I try to adjust a file in my phone (eg hosts and bootanimation) I don't seem to have any success.
In adb I can push it to the phone, but when I reboot my phone I get nothing. I tried to push the bootanimation to various maps that I found that have the bootanimation, but when I reboot I don't get the new animation to load.
When I try to replace the files in root explorer I always get a "not enough space" error and my phone reboots.
I don't know what I did wrong because I got the SU working but I can't get any file from the sd card or my pc on my phone successful.
This was the reason I rooted my phone because I want to edit my hosts file for no ads and a new bootanimation.
I added my bootanimation and the hosts file if anybody can check if maybe that’s the problem. (just remove the zip from the hosts file and open with notepad, I couldn't get it uploaded else)
Reboot recovery, then go partitions/mount system and ./adb push.
Edit : Just noticed.. you need a path.
There you go :
Code:
./adb push hosts /system/etc/hosts
./adb push bootanimation.zip /system/customize/resource/bootanimation.zip
./adb push bootanimation.zip /system/media/bootanimation.zip
Assuming you have those 2 files in your adb path of course..
I uploaded a screen from my cmd window, because I went in recovery and did the adb thing and I can see that my pc did something. But when I rebooted my phone I still get the same old white HTC bootanimation.
Edit: I got it to work with this, thanks for the help madwifi
power off
plug in usb cable
hold volume down+power
volume down once to select recovery and then hit power
now you should be at the clockworkmod recovery menu
select "partitions menu"
select "mount /system"
on my computer, click start, run, and then type "cmd" and hit enter to get a dos prompt
(For noobs like me I found this site: http://www.jonamerica.com/technology/howto-root-the-htc-droid-incredible/#bloat) where I found some extra information
Is there a way to change the Splash screen like with this flasher? http://forum.xda-developers.com/showthread.php?t=794638 on the Wildfire? because it has a lower resolution.
Not until we get the s-off patch from alpha rev
thanks for the information, I didn't know that
So to change the splash screen of your android phone 1st you need to Set up ADB if you already haven't..
Set up ADB from Here:
http://droidination.wordpress.com/2012/02/01/how-to-set-up-adb/
Now after setting up the ADB you need to Follow these instructionsto change your splash screen:
1.First you need to copy a cmd.exe file to Heimdall’s Folder like this
2.Now put your phone into download mode and open the file ZADIG in the drivers folder.
3.Install The drivers now
4.Now open Cmd and type the foll command:
heimdall flash –param /location/of/param.lfs
5.Now your phone will be rebooted and you will see the Download mode logo instead of your orignal logo
6.Now create your own logo using Photoshop or any other Photo Editor and make sure its in the ratio 480×800..
7.put the logo file in the platform tools folder in android sdk..
8.Paste and open the cmd in the platform tools folder..
9.Put your phone in download mode and Connect it to the computer..
10.Type in the following command in the CMD window:
adb push Logo.jpg /mnt/.lfs
adb reboot
11.You Will Now see your logo file Instead of the orignal one..
You Can Check out the orignal Post from here:
http://droidination.wordpress.com/2...e-splash-screen-of-your-galaxy-s-easiest-way/
Click the thanks button if i helped..
so...can I just make a logo.jpg and put into mnt/.lfs by root explorer?
(btw,and its funny to see i9003 and docomo logos in .lfs file)
Yes 1st u have to make a logo.jpg of resolution 480*800 only..
u can make it using Photoshop..
Then just open terminal emulator in your GTi9000.. if u dont have it download it from the android market..
Copy the logo.jpg file in the root of your SDCARD..
and type the following command:
"cp /mnt/sdcard/logo.jpg /mnt/.lfs" [Without Quotations]
Reboot your phone now..
now you will see your logo.jpg file as the boot image/splash screen..
It would not replace it by root explorer.."
Yes i was also shocked to see the i9003 and docomo logos..
click the thanks button if i helped..
I just made the splash screen by removing samsung logo from the original
(hey samsung you have made a big enough logo on our phones! no need to put one on boot!)
saved as /mnt/sdcard/logo.jpg 800×480 of course
opened terminal emulator, typed
Code:
cp /mnt/sdcard/logo.jpg /mnt/.lfs
and get the following code without logo.jpg replaced
Code:
cp: can't create '/mnt/.lfs/logo.jpg': File exists
also tried copying with root explorer, but it also turns out to be the original image
(even deleteing the original and put new logo.jpg to /mnt/.lfs)
(of course I have a backup of original image)
will this be something wrong with busybox?
EDIT:it seems everything that gets into /.lfs can't be deleted by RE or terminal emulator. weird...
First u have to type su to enable superuser access then type that command..
make sure u have busybox installed..!! if not just download the terminal IDE app from market then do the same thing this will work 4 sure..!!
To be clear, I have root, busybox 1.19.3 , superuser permitted terminal IDE,
typed su this time but still no luck.
(and when I tried to rm a accidentally copied jpg from /mnt/.lfs , terminal IDE even says 'operation not permitted' . WHAT? I have already "su"ed!)
Doubt that I must go through download mode in order to write in movinand.
Anyway thanks for providing all the info on splash screen replacement. Cheers.
playerzking said:
To be clear, I have root, busybox 1.19.3 , superuser permitted terminal IDE,
typed su this time but still no luck.
(and when I tried to rm a accidentally copied jpg from /mnt/.lfs , terminal IDE even says 'operation not permitted' . WHAT? I have already "su"ed!)
Doubt that I must go through download mode in order to write in movinand.
Anyway thanks for providing all the info on splash screen replacement. Cheers.
Click to expand...
Click to collapse
I second that. I am root and mounted /system as rw, it does not allow me to rm or even mv the /mnt/.lfs/logo.jpg to anywhere. Even root explorer cannot rename the default logo.jpg. Operation not permitted is the error I get. I am using gingerbread 2.3.6 GINGERBREAD.JPKPE build. Dont know if they added some second layer of protection...
I'm trying to install Amon_Ra's Recovery image via ADB but im getting the following errors:
Code:
C:\Windows\system32>adb push recovery-RA-hero-v1.7.0.1.img /data/local/
cannot stat 'recovery-RA-hero-v1.7.0.1.img': No such file or directory
When I type in "adb devices" it see's the phone
The recovery image is located:
Code:
C:\android-sdk-windows\platform-tools\recovery-RA-hero-v1.7.0.1.img
Any help on this would be great
Mikebyrne000 said:
I'm trying to install Amon_Ra's Recovery image via ADB but im getting the following errors:
Code:
C:\Windows\system32>adb push recovery-RA-hero-v1.7.0.1.img /data/local/
cannot stat 'recovery-RA-hero-v1.7.0.1.img': No such file or directory
When I type in "adb devices" it see's the phone
The recovery image is located:
Code:
C:\android-sdk-windows\platform-tools\recovery-RA-hero-v1.7.0.1.img
Any help on this would be great
Click to expand...
Click to collapse
You have to give the full path to your img file. eg:
adb push C:\android-sdk-windows\platform-tools\recovery-RA-hero-v1.7.0.1.img /data/local/
Or just copy the img file to C:\Windows\system32
Did you had a custom recovery before doing this? If you do, you can boot into recovery, mount your sdcard, put the image file to the root of your sd card and then follow the steps provided to install the image recovery through adb. I had this problem a few days ago but I had installed CWM as recovery and it was easy to flash the other one.
flashrec
download a flashrec aplication then, install and open,
do a Backup Recovery Image,
enter a recovery path , for example: /sdcard/recovery-RA-hero-v1.6.2.img
restart with home + power buttons and de recovery works
For unknown reason, my kindle fire bricked yesterday. After i unbricked it, i found myself unable to install any application.
I really doubt what i can do for my kindle. Please Help me, thank you.
create folder new with rootexploer and in adb write (file u-boot must be in folder tools of kfu:
adb push u-boot.bin /new
adb shell dd if=/new/u-boot.bin of=/dev/block/mmcblk0p2
and after flash other rom.
I had this problem after unbrick kf and only this method can help me.
Good luck
Deat7 said:
create folder new with rootexploer and in adb write (file u-boot must be in folder tools of kfu:
adb push u-boot.bin /new
adb shell dd if=/new/u-boot.bin of=/dev/block/mmcblk0p2
and after flash other rom.
I had this problem after unbrick kf and only this method can help me.
Good luck
Click to expand...
Click to collapse
thanks for your help. i pushed u-boot.bin.
However, "dd: can't open '/new/u-boot.bin': Not a directory" shown after i enter the second command. So, what can i do next?
did you create folder? i had this error first time when folder was not created.
Deat7 said:
did you create folder? i had this error first time when folder was not created.
Click to expand...
Click to collapse
oh...i found the problem is that i only can use adb in recovery mode. But everytime i reboot it, all changes i made will be erased automatically due to the limited storage i think. So, i created the folder and it just being erased.
i know it.
1. Turn on device
2. Create a folder
3. Run adb
4. Write commands.
Must write a lot of text after the second command. So fff installed. If you reboot kf after this, can see yellow triangle.
thank you so much Deat7
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Download the Magisk uninstall zip (same site where you load the Magisk zip file or see the how to root threads) and flash it with twrp (same way as you flashed the Magisk zip or see the how to root threads).
Next do the same as you did to unlock the bootloader, change the command from unlock to lock.
That should do it.
Sent from my OnePlus6T using XDA Labs
-MrMM- said:
Download the Magisk uninstall zip (same site where you load the Magisk zip file or see the how to root threads) and flash it with twrp (same way as you flashed the Magisk zip or see the how to root threads).
Next do the same as you did to unlock the bootloader, change the command from unlock to lock.
That should do it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
so I don't need to flash strock rom?
thanks!
lele90 said:
so I don't need to flash strock rom?
thanks!
Click to expand...
Click to collapse
EDIT: I'm not able to unistall it due to: "I cannot access /data please uninstall with Magisk Manager"
Currently I did a factory reset, software install (from 6t settings) and lock bootloader...
I was not able to unistall magisk with ZIP
lele90 said:
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Click to expand...
Click to collapse
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
MMM sorry I'm not a linux user...
But is enough to do a factory reset, restore the firmware (via software update in settings menu) ? Or I need to flash the stock firmware in that way: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 ?
lele90 said:
MMM sorry I'm not a linux user...
But is enough to do a factory reset, restore the firmware (via software update in settings menu) ? Or I need to flash the stock firmware in that way: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 ?
Click to expand...
Click to collapse
Try to flash the entire update file from OnePlus.com:
https://www.oneplus.com/support/softwareupgrade/details?code=9
Download the file, place it in your root internal storage (the parent dir of the Downloads folder), and flash it locally from the settings>system update>local upgrade menu.
ducted said:
Try to flash the entire update file from OnePlus.com:
https://www.oneplus.com/support/softwareupgrade/details?code=9
Download the file, place it in your root internal storage (the parent dir of the Downloads folder), and flash it locally from the settings>system update>local upgrade menu.
Click to expand...
Click to collapse
Already done and then locked my bootloader! Thanks
lele90 said:
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Click to expand...
Click to collapse
Why do you want to do all that? You can prevent applications from detecting root access using magisk. Just saying...
papadi said:
Why do you want to do all that? You can prevent applications from detecting root access using magisk. Just saying...
Click to expand...
Click to collapse
It does not work for my Home banking app ... I need it!
PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
I tried this and now am stuck on the unlocked bootloader screen (where is says your boot loader is unlocked and software integrity cannot be guarenteed...), any ideas?
dipole said:
I tried this and now am stuck on the unlocked bootloader screen (where is says your boot loader is unlocked and software integrity cannot be guarenteed...), any ideas?
Click to expand...
Click to collapse
Did you press power off button? if yes, you stopped the boot...
PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
lele90 said:
Did you press power off button? if yes, you stopped the boot...
Click to expand...
Click to collapse
I forgot the _a after boot (boot_a). i just rerooted to fix my issue so haven't tried with the correct boot_a.
Question though, shouldn't that be boot_a and boot_b? still trying to get my head around the two slots..
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img