Related
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
Code:
adb shell
mkdir 21system
mount -o rw /dev/block/mtdblock2 /21system
If you're lucky it will mount your 2.1 system partition as /21system
Most likely it will say "Device or resource busy"... But worth trying anyway.
Cheers
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
I did the same thing at least twice. I was able to save it without restoring by replacing my framework-res.apk before it rebooted or froze.
Basically, try to adb into it while it is still at the Sony logo or if you get the blackscreen after the logo.
One weird thing I did notice was that I was able to replace the framework-res.apk file apparently without using 'su'. After I killed it when I was doing adb at/after the logo I tried to 'su' but it gave some error and remained at the '$' prompt. I then did the 'dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk' command and it completed. Rebooted and it worked again.
Think my whole thing was tested second time with a script.
Try making a frameworkfix.cmd file and putting this in it.
@echo off
@echo.
@echo Installing Framework
@echo.
@adb shell su
@adb push framework-res.apk /sdcard/framework-res.apk
@adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
The keep trying to run it while at the Sony logo. Give it a few runs before you give up, I swear it worked for me.
thermoska said:
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
Heck just try the following from folder with your original framework.
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
or
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
thanks guys , but I do not need commands,
I know them already , I had permissions problem.
Instructions mentioned above did not worked for me
I've got permission denied
anyway thanks
thermoska said:
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
You can access the 2.1 /system partition through 2.2 with adb.
Use this to unmount 2.2 /system
Code:
su
busybox umount /dev/block/loop1
You can check if all worked well this way:
Code:
busybox ls -1d /system/* | grep xbin
If it gives you anything, it's 2.1 -- if not, try
Code:
busybox umount -l /dev/block/loop1
Now, you should have the old 2.1 /system structure available. Ignore all errors appearing *on the phone* it'll be screwed up, unusable. Until a restart.
Now through adb you can overwrite your 2.1 framework apk with dd
(assuming you already have it on the sdcard, else, well, push it there (adb push framework.apk /mnt/sdcard/ )
Code:
dd if=/mnt/sdcard/framework.apk of=/system/framework/framework.apk
for remount system, just do
Code:
busybox mount -o remount,rw /system
after you have the 2.1 system available.
I installed 2.2 to my nand (almost fully working) at one point this way =3
Or...
You can flash again just using system.bin and everything you had would be there.
;-)
You also will need loader.sin
I did this a couple of times and work for me; I only need to root again
Good luck!
PS: In the firmware folder, you need to leave ONLY this 2 files: System.sin and loader.sin. Backup and delete all other files like amss.sin, cache.sin, etc.
well thank you
This a good idea ..
Unfortunatelly I already reflashed the phone
Hope it will help to somebody in the future
ttxdragon said:
I installed 2.2 to my nand (almost fully working) at one point this way =3
Click to expand...
Click to collapse
Thought that would work, was going to do it with .003, but I guess the recovery tool will do that for us - now we see what Z has been working on - excellent news
Just curios. Any speed improvements when extracting the img files to nand and mount/run it from there ?
Even running from sdcard img files is a perfect backup solution by just copy the img files away from time to time. But of course r/w cycles of the card are increased --> less lifetime.
But otherwise running from images is nice, as you're able to mount them. (diskinternals linux reader but R-only)
Anyone knows a win32 prog to mount the img files r/w ?
Hi,
I uninstalled TW4 from my phone and put GO Launcher into system. It was playing up today so I uninstalled it then reinstalled it...
Unfortunately I forgot to push it back into system before rebooting the phone. Now I have a lockscreen and then a crashing phone!
I can adb into it still and would like to know how to get either a launcher from my Titanium Backup into system/app, or from an apk I have on my desktop into system/app?
In adb I can't currently use remount for whatever reason.
I'm using CF-Root 3.5 kernel.
Thanks guys!
Stupidly lost launcher Huston We Have A Problem.
Factory reset ???
jje
Factory reset wont work I dont think due to the lack of TouchWiz at all!!
Also, trying to avoid a reset.
Thinking maybe I can launch Titanium via ADB and then I can sort it from there?
TheMathMan said:
Factory reset wont work I dont think due to the lack of TouchWiz at all!!
Also, trying to avoid a reset.
From recovery is how .
jje
Click to expand...
Click to collapse
Could you elaborate jje?
Code:
mount -o rw,remount /system
Posted by Chainfire himself in the kernel thread.
Then push normally with adb to system. You might need to use "su" before mounting but i don't think so with adb.
Edit:
Factory resets won't change anything since they don't touch the system partition, only data.
TheGhost1233 said:
Code:
mount -o rw,remount /system
Posted by Chainfire himself in the kernel thread.
Then push normally with adb to system. You might need to use "su" before mounting but i don't think so with adb.
Edit:
Factory resets won't change anything since they don't touch the system partition, only data.
Click to expand...
Click to collapse
Right... no joy. It mounted fine and a SU request came up on screen and all is good.
Then exiting shell and doing adb pus I get a permission denied error.
I can't enter adb push from # as it doesnt like it!
What am I doing wrong?
Also, what would be the am command to launch Titanium Backup from adb?
OK... read somewhere that you cant push directly to system/app with a secured kernel.
So I have pushed to sdcard and then cp to system/app... fingers crossed!
....
HURRAH!!!!
It reset the homescreen default and the menu popped up. Phew!
Hi all,
happened to me a mishap.
I had done a full wipe but forgot to push the stock launcher back on it, well now the launcher is missing and I can not do anything.
Would have otherwise update the Asus HC recorded but do not know how that should go without Launcher
Who has an advice what I could do?
sorry, trying to understand...
Had you done some sort of modification that removed the stock launcher? There isn't any reason why the stock launcher wouldn't be present. Can you try another factory reset using vol up + power? i don't recall exactly what the sequence is.
Its ok,
my english is not the best.
I delete the stock launcher with a script and forgot to restore it.
And then i do a factory resett..........
No Launcher anymore.........
A Androiddevice without an launcher become a bootloop or something similar
Did you uninstall the APK "launcher2.apk" and it's odex "launcher2.odex"?
I made that mistake and what i had to do was use ADB to install a 3rd party launcher (I found an APK for launcher pro and used that) and then once I had a working launcher, I downloaded Root explorer (I was rooted) and moved the "Launcher2.apk" and "launcher2.odex" into the /system/app folder. From there, I rebooted and everything was gravy
It is essential to include both the .apk and the .odex. Also, you have to have the files from the same build version you are. (You can't use an odex from 8.8.3.29 on a tablet running 8.8.3.33)
does ADB see your device? If so maybe you can push launcher API back to /system/app then set the permissions and you should be all set.
Sent from my Transformer Prime TF201 using xda premium
bscotth said:
Did you uninstall the APK "launcher2.apk" and it's odex "launcher2.odex"?
I made that mistake and what i had to do was use ADB to install a 3rd party launcher (I found an APK for launcher pro and used that) and then once I had a working launcher, I downloaded Root explorer (I was rooted) and moved the "Launcher2.apk" and "launcher2.odex" into the /system/app folder. From there, I rebooted and everything was gravy
It is essential to include both the .apk and the .odex. Also, you have to have the files from the same build version you are. (You can't use an odex from 8.8.3.29 on a tablet running 8.8.3.33)
Click to expand...
Click to collapse
Yes i uninstall the launcher2_apk and odex file.
ADB dont see my device.
I think its a mistake in the USB driver.
I pluged the prime in and MTP doesnt install correctly.
cooper1988 said:
Hi all,
happened to me a mishap.
I had done a full wipe but forgot to push the stock launcher back on it, well now the launcher is missing and I can not do anything.
Would have otherwise update the Asus HC recorded but do not know how that should go without Launcher
Who has an advice what I could do?
Click to expand...
Click to collapse
cooper1988, what you have to do is download a new launcher in your pc, put it in your sd card and apply it with the recovery mode in "apply any zip from sd".
ajmdve said:
cooper1988, what you have to do is download a new launcher in your pc, put it in your sd card and apply it with the recovery mode in "apply any zip from sd".
Click to expand...
Click to collapse
prime doesnt have a recovery (locked bootloader)
Power + Vol D --> Wipe or boot Android
well, then you might try flashing a new rom. sorry but if your pad doesnt have recovery, the it is the only way i see.
ajmdve said:
well, then you might try flashing a new rom. sorry but if your pad doesnt have recovery, the it is the only way i see.
Click to expand...
Click to collapse
won't it try to flash whatever image is on the sd card with that combo, effectively a hard reset?
Year
ADB show my device.
But i cant push the apk to /system/app or /data/app
failed to copy 'launcher.apk' to '/data/app/launcher.apk': Permission denied
a hard reset is not useful in this case because the launcher in not in the system folder anymore. he have to flash the pad with odin or any other method alike.
cooper1988 said:
Year
ADB show my device.
But i cant push the apk to /system/app or /data/app
failed to copy 'launcher.apk' to '/data/app/launcher.apk': Permission denied
Click to expand...
Click to collapse
I believe you have to mount /system in order to do that push
c:\android-sdk\platform-tools>adb shell mount /system
mount: permission denied
i dont have root on the prime and nachoroot doesnt work ( i have hc)
c:\android-sdk\platform-tools>adb push nachoroot.bin /data/local/
1140 KB/s (15182 bytes in 0.013s)
c:\android-sdk\platform-tools>adb shell chmod 777 /data/local/nachoroot.bin
chmod: permission denied
a hard reset wont do anything
tdrussell said:
won't it try to flash whatever image is on the sd card with that combo, effectively a hard reset?
Click to expand...
Click to collapse
a hard reset wont do anything, because it restores all by default, but, if the launcher isn't in the system folder, the phone wont make it appear from nowhere.
he should flash a new rom using odin or some other tools alike.
I am in a similar situation I am stuck in a boot loop! Not able to get passed the asus logo loading sign!
I can not get in ADB because of dumb asus sync I still need to try using ADB on linux! Because that does not need the asus sync
Sent from my PC36100 using Tapatalk
how it happens?
Wordlywisewiz said:
I am in a similar situation I am stuck in a boot loop! Not able to get passed the asus logo loading sign!
I can not get in ADB because of dumb asus sync I still need to try using ADB on linux! Because that does not need the asus sync
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
how it happens?
ajmdve said:
how it happens?
Click to expand...
Click to collapse
Well idrk either the system apps I froze or the changing the build.prop (added enable. Facelock) but even after I had done that I had rebooted Atleast twice
But maybe it only checks those things on a kernel panic
Sent from my PC36100 using Tapatalk
you rebooted twice and it starts completelly or it always get stuck in the boot logo?
cooper1988 said:
c:\android-sdk\platform-tools>adb shell mount /system
mount: permission denied
i dont have root on the prime and nachoroot doesnt work ( i have hc)
c:\android-sdk\platform-tools>adb push nachoroot.bin /data/local/
1140 KB/s (15182 bytes in 0.013s)
c:\android-sdk\platform-tools>adb shell chmod 777 /data/local/nachoroot.bin
chmod: permission denied
Click to expand...
Click to collapse
before you did factory reset , u removed the launch apk right ? so you had root before you did factory reset , you should still have it now , because factory wipe does not remove root.
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
the problem was in the file permissions. i had to remove write permissions to the group. (rw-r--r--)
You can fix permissions using adb
Sent from my GT-S5830 using xda premium
the.fuzzy.guy said:
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
Click to expand...
Click to collapse
First of all DO NOT WIPE DATA / FACTORY RESET
This will remove adb access. Depending how far you can boot, do you get adb in recovery or normal. Can you use adb shell? If you can you can us adb shell chmod 644 /system/build.prop
EDIT:
Failing that try to install a zip. Sell my links for both current and older zips
Hi all
I have a problem with a clone (HDC model). That I did a factory reset and reformatted the storage. After that I suddenly don't have my bootanimation anymore. Instead it shows a silver grey "android" logo in the middle of the screen when I boot the phone, and the same when I shut it off.
I have checked my system/media folder and the phone actually have all the bootanimation.zip shutdownanimation.zip etc. in there, and they are also the original ones. But for some reason the phone don't use them by boot or shutdown.
Also I tried with "Boot Animations -root-" app from the Playstore, but it also don't change anything. I tried to place bootanimation.zip in data/local also but no change.
I checked the permissions of the files and they are also good. And tried all kind of codes on the phone, but none have worked so far.
So what the heck can be wrong?
s7yler said:
Hi all
I have a problem with a clone (HDC model). That I did a factory reset and reformatted the storage. After that I suddenly don't have my bootanimation anymore. Instead it shows a silver grey "android" logo in the middle of the screen when I boot the phone, and the same when I shut it off.
I have checked my system/media folder and the phone actually have all the bootanimation.zip shutdownanimation.zip etc. in there, and they are also the original ones. But for some reason the phone don't use them by boot or shutdown.
Also I tried with "Boot Animations -root-" app from the Playstore, but it also don't change anything. I tried to place bootanimation.zip in data/local also but no change.
I checked the permissions of the files and they are also good. And tried all kind of codes on the phone, but none have worked so far.
So what the heck can be wrong?
Click to expand...
Click to collapse
just delete bootanimation.zip
it will load the stock files if available
&
next time post in Q &A forum
Vaibhav Chauhan said:
just delete bootanimation.zip
it will load the stock files if available
&
next time post in Q &A forum
Click to expand...
Click to collapse
That don't help anything, I want it to display the bootanimation.zip in system/media (and currently it don't show that one at bootup!)
deleting it, just still shows the stock with android in silver at bootup.
It don't seem that you understand the problem.
s7yler said:
That don't help anything, I want it to display the bootanimation.zip in system/media (and currently it don't show that one at bootup!)
deleting it, just still shows the stock with android in silver at bootup.
It don't seem that you understand the problem.
Click to expand...
Click to collapse
i think the permissions for using custom animation is changed in your phone as you have reset the phone
Vaibhav Chauhan said:
i think the permissions for using custom animation is changed in your phone as you have reset the phone
Click to expand...
Click to collapse
Okay, but the phone is rooted and I have set the same permissions on the files.
Or how can it then be fixed? "permissions for using custom animation" where is that set?
s7yler said:
Okay, but the phone is rooted and I have set the same permissions on the files.
Or how can it then be fixed? "permissions for using custom animation" where is that set?
Click to expand...
Click to collapse
its not a name of permissions
please conform there is system/bin/bootanimation available
Vaibhav Chauhan said:
its not a name of permissions
please conform there is system/bin/bootanimation available
Click to expand...
Click to collapse
Yes it is there
s7yler said:
Yes it is there
Click to expand...
Click to collapse
try to flash the file in the thread
http://forum.xda-developers.com/showthread.php?t=2186155
&
replace the bootanimation.zip with yours
Vaibhav Chauhan said:
try to flash the file in the thread
http://forum.xda-developers.com/showthread.php?t=2186155
&
replace the bootanimation.zip with yours
Click to expand...
Click to collapse
Ok i flashed it with CWM, but now the bootup is just a blackscreen for 10 seconds.... tried to replace the bootanimation.zip with the original.
Still just a black screen at bootup. But at least it boots into the system still.
s7yler said:
Ok i flashed it with CWM, but now the bootup is just a blackscreen for 10 seconds.... tried to replace the bootanimation.zip with the original.
Still just a black screen at bootup. But at least it boots into the system still.
Click to expand...
Click to collapse
now replace your bootanimation.zip in system/media
Vaibhav Chauhan said:
now replace your bootanimation.zip in system/media
Click to expand...
Click to collapse
Already tried to replace it with the original bootanimation.zip, still just a black bootup. Also tried others that I download from Bootanimation app from the play store. Still just black, it is strange....
Ok I gave up fixing this manually, so I ended up restoring my whole phone from a previous CWM backup. So now I am back again and have the stock bootanimation. Never found out where or why it couldnt be fixed. But thanks for your time and answers.
s7yler said:
Ok I gave up fixing this manually, so I ended up restoring my whole phone from a previous CWM backup. So now I am back again and have the stock bootanimation. Never found out where or why it couldnt be fixed. But thanks for your time and answers.
Click to expand...
Click to collapse
:good:
Vaibhav Chauhan said:
just delete bootanimation.zip
it will load the stock files if available
&
next time post in Q &A forum
Click to expand...
Click to collapse
thanks, this worked for my problem, i didn't have any boot screen, and when I restarted or turned off my phone it didn't turn off... now it didn't show anything though but i just placed the files manually in there again, now it works again
Thanks!
Sorry for reviving this thread, I had the same issue and I managed to fix it, my steps:
1. you must change your /system folder to read-write mode, to do that you must execute the following command:
mount -o rw,remount /system
2. then, move your bootanimation.zip to, in my case, /system/media , it should be like: (if you execute ls -la command there)
dolphin-fvd-p1:/system/media # ls -la
total 94704
drwxr-xr-x 3 root root 4096 2019-05-02 16:35 .
drwxr-xr-x 17 root root 4096 1969-12-31 19:00 ..
drwxr-xr-x 6 root root 4096 2018-11-22 22:42 audio
-rw-r--r-- 1 root root 5588643 2018-11-22 22:42 bootanimation.bkp
-rw-rw---- 1 root root 572218 2019-05-02 16:35 bootanimation.zip
*Note about the read-write-execute the bootanimation.bkp has -rw-r--r-- and my customized bootanimation.zip has -rw-rw----
with that the android logo kept showing over and over...
Ok, enough talk, what I did was just to fix the permissions there, to do that execute the command:
chmod 644 bootanimation.zip
Do not forget to rollback the /system back to read-only mode, to do that execute the command:
mount -o ro,remount /system
I have with this answer I have helped someone that like me found this thread on google.
digoo said:
Sorry for reviving this thread, I had the same issue and I managed to fix it, my steps:
1. you must change your /system folder to read-write mode, to do that you must execute the following command:
mount -o rw,remount /system
2. then, move your bootanimation.zip to, in my case, /system/media , it should be like: (if you execute ls -la command there)
dolphin-fvd-p1:/system/media # ls -la
total 94704
drwxr-xr-x 3 root root 4096 2019-05-02 16:35 .
drwxr-xr-x 17 root root 4096 1969-12-31 19:00 ..
drwxr-xr-x 6 root root 4096 2018-11-22 22:42 audio
-rw-r--r-- 1 root root 5588643 2018-11-22 22:42 bootanimation.bkp
-rw-rw---- 1 root root 572218 2019-05-02 16:35 bootanimation.zip
*Note about the read-write-execute the bootanimation.bkp has -rw-r--r-- and my customized bootanimation.zip has -rw-rw----
with that the android logo kept showing over and over...
Ok, enough talk, what I did was just to fix the permissions there, to do that execute the command:
chmod 644 bootanimation.zip
Do not forget to rollback the /system back to read-only mode, to do that execute the command:
mount -o ro,remount /system
I have with this answer I have helped someone that like me found this thread on google.
Click to expand...
Click to collapse
So I'm having the same issue on my OnePlus 6T. I already have my bootanimation (flashable zip) in /system/media.
I ran the command "chmod 644 bootanimation.zip," which returned "chmod bootanimation.zip to 100644: read-only file system". I'm still getting the gray android word though.
(And thanks for reviving the thread )
clarkcant said:
So I'm having the same issue on my OnePlus 6T. I already have my bootanimation (flashable zip) in /system/media.
I ran the command "chmod 644 bootanimation.zip," which returned "chmod bootanimation.zip to 100644: read-only file system". I'm still getting the gray android word though.
(And thanks for reviving the thread )
Click to expand...
Click to collapse
If you're using Magisk then open it's settings and select "core only mode", reboot, then try again. Magisk has problems mounting the system properly when modules are enabled. Also, if your device is treble enabled, then your boot animation might be in /oem/media instead. My G6 play has one in /system/media and also /oem/media, but only the one in /oem gets used on my device. You might have something similar going on.
clarkcant said:
So I'm having the same issue on my OnePlus 6T. I already have my bootanimation (flashable zip) in /system/media.
I ran the command "chmod 644 bootanimation.zip," which returned "chmod bootanimation.zip to 100644: read-only file system". I'm still getting the gray android word though.
(And thanks for reviving the thread )
Click to expand...
Click to collapse
Look like you haven't done the very first step I have mentioned. if you are using adb and/or console you should get it by typing the mount command.