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 ?
It seems that nobody is talking about deodexing the Droid X2. Just thought I would let everyone know that xUltimate 2.2.8 works on the Droid X2 with the newest drivers installed. I am currently manually deodexing my root GB Droid X 2.
Some Members Might Not Wanna Take The Risk. With All The ROMs Are Already Deodexed. Me Personally I've Had That Program Downloaded Since The First Time It Was Posted And Have Used It Numerous Times. Now That You Mentioned This, You Should Go Bump That Thread.
If anyone can instruct me on how to successfully create an update zip I would gladly do it for those that don't want to take the risk of deodexing manually. But I am really shocked that a deodexed GB is not in the TBH App and no one seems to be talking about it.
I'm Gonna PM You A Few Websites To Learn How To Do It.
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
dimitri407 said:
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
You Need To Manually Transfer Them Over USB First. Both App And Frame Place Them On Your SD Card.
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
dimitri407 said:
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
Click to expand...
Click to collapse
When You Did "su", Did You Grant The Superuser Request On The Phone?
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
dimitri407 said:
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
Click to expand...
Click to collapse
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
I can't figure it out either. I did this to my Droid X with no problems. But the Droid X 2 just wants to be a pain when I am trying it.
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
I am wondering, since it is not working in adb shell then could I do it in the terminal?
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
So I finally got everything to work but to do so I had to copy the done_app and the done_frame folders to /data/local/tmp then run the cp commands.
For some reason, I could not get to the SD Card or the External SDCard.
you both need to quit hijacking threads and grow up. If I was the mod I would ban both of you.
Sent from my DROID X2 using XDA App
mistawolfe said:
Lol. You beg for 'em. Signature...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Can we please stop hijacking my thread. This is suppose to be about Deodexing the Droid X 2.
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
dimitri407 said:
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
Click to expand...
Click to collapse
Oh God Yes. It's Gonna Faster And Smoother. The Point Of Deodexing Is It Recompiles The Odex Inside The Apk For Easier Themeing And The System Is Able To Read The Apks Faster. Definitely Gonna Help Battery If The System Isn't Working As Hard.
when you connect USB, you MUST be in "charge only" mode w/ usb debugging enabled. ANY OTHER MODE will fail to allow complete access to /sdcard or /sdcard-ext...
or at least that was my experience.
I'll Challenge That I Used PC Mode To Run The Deodex App And Then To Transfer The Completed Files Without Switching Modes. Anytime I Run ADB Operations My Phone Is In PC Mode.
I will check both settings today. But by mounting the partition, it should become available either way. But we will see.
--THIS IS FOR THE VERIZON DROID RAZR--
Go here for the test files for international version: http://forum.xda-developers.com/showpost.php?p=19900530&postcount=11
I have enough confirmations that I can now confirm this is working, However the on screen controls appear not to be launching currently, but webtop launches.
What this mod does:
It removes the device ID string check from PortalApp, and enables the webtop option in DockService. Replacing these two apk files effectively allows the webtop to launch without proprietary hardware.
Click to expand...
Click to collapse
What this means to you:
Webtop mode over any HDMI without an expensive dock.
Click to expand...
Click to collapse
Installation:
Method 1: Flashable ZIP
Flash THIS zip.
Click to expand...
Click to collapse
Method 2: ADB install
Download the attached apk files.
First Get the files to the device and remount /system as rw:
Code:
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o remount,rw /system
Backup the original files:
Code:
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
Copy the modded files over fix permissions and reboot:
Code:
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
chmod 644 /system/app/DockService.apk
chmod 644 /system/app/PortalApp.apk
reboot
Click to expand...
Click to collapse
Appreciate my work? Buy Me a Beer:
You are awesome!! Thank You. As soon as I find a spare HDMI port on my TV I'm installing this.
Edit: Is there a way to revert back to stock without doing a ND restore. Only for warranty purposes of course, can't imagine anyone would even know though. <<Ignore that.
love you.
10<3
ah jeeze... just noticed it's for the Verizon RAZR, will it by any chance work on a GSM version?
Just installed it, and on the bionic after connecting to the tv, the phone became a mouse. Here the screen goes black and doesn't respond to touch.
You on a Verizon device? Did the webtop or dock option list come up at all?
Yes, Verizon phone. Everything comes up great on the tv, The webtop option comes up on the list to choise from, when i hit webtop the tv comes on, the phone goes black, but no control of pointer at all.
That's a good sign at least. Did you install via the flash method or the adb method?
Flash. I flashed BigDX ics theme yesterday, maybe it has something to do with it, so restoring a nandroid backup of before and will flash the webtop hack again.
---------- Post added at 10:41 PM ---------- Previous post was at 10:12 PM ----------
Nope. Same. Phone screen goes black, no control of pointer.
That sucks stevessvt, maybe try installing via adb instead and see what happens.
I really want to try it on my GSM RAZR... Don't know what the difference would be. Anyone...?
EDIT:
My stock DockService.apk is 109kb - odex is 173kb, the PortalApp.apk is 1.21mb - odex is 591kb
Can anyone confirm the Verizon file sizes for me?
opensourcefan said:
You are awesome!! Thank You. As soon as I find a spare HDMI port on my TV I'm installing this.
Edit: Is there a way to revert back to stock without doing a ND restore. Only for warranty purposes of course, can't imagine anyone would even know though. <<Ignore that.
Click to expand...
Click to collapse
Try this one with method 2 for the international version: http://www.cheatersedge.org/android/RazrWebtopMod.rar
I'll try to look into the on screen mouse/keyboard issue. It may be slow going seeing as I don't actually have one of these devices to test on.
Sent from my SGH-I777 using XDA App
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
oh now i just got mad since the OTA i lost root so no Webtop for me. i don't wanna loose the OTA so i'm just gonna wait for somebody to find a way to get root again.. since i don't know how to do that.
opensourcefan said:
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
Click to expand...
Click to collapse
You can change the permissions with Root Explorer: Long hold on each file, and set RW- R-- R--, and then reboot, that ought to go it.
As for the command for the adb method it might be "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" Where "/dev/block/mtdblock3" is replaced with the actual block device for /system. You can check this by just typing "mount" and looking at the entry for /system.
only Verizon? not for EU GSM devices?
Doesn't work on mine. As faras I know there are different version for gsm that could be the problem
Sent from my Razr XT910 using xda premium
shady_lanem said:
Doesn't work on mine. As faras I know there are different version for gsm that could be the problem
Sent from my Razr XT910 using xda premium
Click to expand...
Click to collapse
you have a Vaarizon?
9100_it said:
you have a Vaarizon?
Click to expand...
Click to collapse
Download link for international version is posted on top of this page
opensourcefan said:
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
Click to expand...
Click to collapse
You have to do
su
To login as root before.
Sent from my awsome Motorola RAZR
Perfect!
I've asked to teach me how to make it, but it's the same. The important thing is that it is available, even if my curiosity reaches an unknown level.
Thanks!
P.S.: Please, edit the thread title to reflect this section rules!
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.
I've tried using twrp and cwm to backup my system image but i havent been able to, with twrp i had system.ext4.win when i backed up only the system. Is their a tool or do i need to do it with adb ?
Thanks!
could you specify your phone/tablet model?
fantamedo said:
could you specify your phone/tablet model?
Click to expand...
Click to collapse
Galaxy s3
First make a full nandroid backup in CWMR, then on your phone navigate to mint/sdcard/clockworkmod then copy the folder of the backup you made (It should be the date of the backup by default) and transfer it to your computer. Once you transfer it to your computer open the backup folder and inside should be the system.img file.
You can also type these commands in terminal emulator to get your system.img:
Code:
su
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/system.img bs=4096
Then just transfer the system.img from your sdcard to your computer. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
It didn't work with cwmr but I haven't tried out the terminal command
Sent from my SCH-I535 using xda premium
CovXX said:
It didn't work with cwmr but I haven't tried out the terminal command
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Like I said try out the terminal command I suggested and let me know how it goes .
Sent from my SCH-I535 using xda premium
shimp208 said:
First make a full nandroid backup in CWMR, then on your phone navigate to mint/sdcard/clockworkmod then copy the folder of the backup you made (It should be the date of the backup by default) and transfer it to your computer. Once you transfer it to your computer open the backup folder and inside should be the system.img file.
You can also type these commands in terminal emulator to get your system.img:
Code:
su
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/system.img bs=4096
Then just transfer the system.img from your sdcard to your computer. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
thanks man, just the command i was looking for, and it works like a charm.. :good:
So how about for a Razr M XT907 ? I ran the term command, but the img size was wayyy too small.
Find out what your system partition is and change command accordingly
Sent from my Nexus 4 using xda premium
livinginkaos said:
So how about for a Razr M XT907 ? I ran the term command, but the img size was wayyy too small.
Click to expand...
Click to collapse
You can find out your which partition your /system partition is by running the following commands either from terminal or adb shell as the root user:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
For example on my Nexus 10 the platform name is "dw_mmc.0" so the command would look like:
Code:
ls -l /dev/block/platform/dw_mmc.0/by-name
To figure out your platform name first cd into the platform directory then list the contents of the platform directory to figure out what your platform name is:
Code:
cd /dev/block/platform/
ls
After you have then figured out what your platform name is you can run the command:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
Once you have figured out your system partition you can dump it to your phones storage by running a command similar to:
Code:
cat /dev/block/block_of_system_partition > /mnt/sdcard/system.img
Let me know if you still have questions .
Awesome guys ! Thanks a bunch.
OK, so I have gotten the img. I've done it both ways with the dd and the cat. The image size comes up close to 1.5Gb. I know this is too large. The fastboot img file is normally in the 800-900 Mb range. Am I missing something here?
livinginkaos said:
OK, so I have gotten the img. I've done it both ways with the dd and the cat. The image size comes up close to 1.5Gb. I know this is too large. The fastboot img file is normally in the 800-900 Mb range. Am I missing something here?
Click to expand...
Click to collapse
Have you installed any additional system apps or placed any other files in the system folder? Because if you have modified the /system folder contents the file size will be greater then the normal 800-900 MB file range you listed since that file size if for an unmodified completely stock /system image.
Actually not really. I had done an erase data, roll back fxz, root, update and cache/dalvik wipe. Was trying to get a somewhat clean system.img
shimp208 said:
You can find out your which partition your /system partition is by running the following commands either from terminal or adb shell as the root user:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
For example on my Nexus 10 the platform name is "dw_mmc.0" so the command would look like:
Code:
ls -l /dev/block/platform/dw_mmc.0/by-name
To figure out your platform name first cd into the platform directory then list the contents of the platform directory to figure out what your platform name is:
Code:
cd /dev/block/platform/
ls
After you have then figured out what your platform name is you can run the command:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
Once you have figured out your system partition you can dump it to your phones storage by running a command similar to:
Code:
cat /dev/block/block_of_system_partition > /mnt/sdcard/system.img
Let me know if you still have questions .
Click to expand...
Click to collapse
When we come to Android 5.0 ages, we have new problems:
Method1 Using the dd we really can get the system.img, but in my 8994 device with busybox 1.23.1, it will 2.5GB fixed size, same as the system partition size.
so what I can found it works is , use sparsecoverter in this forum http://forum.xda-developers.com/showthread.php?t=2749797, we can remove the sparse bytes and make it a 1.4GB around and fastboot back to devices, that works fine, NOTE, that is not from dd nandroid backup. not from who only have TWRP and CWM backups;.
Method2 Using TWRP/CWM system.ext4.win/data.ext4.win, we can use
tar -xvf /storage/sdcard1/twrp/backup/abcd/2015-03-29-09-00-00/system.ext4.win
tar -xvf /storage/sdcard1/twrp/backup/abcd/2015-03-29-09-00-00/data.ext4.win
to gotten a folder, I run this on my target device under adb root and adb shell, but it will have many errors, tar remote link .... function not implement, so I think we need a cygwin according this post, but next step since Android 4.0 should be make_ext4fs, which will need a special build to avoid Permission Denied. which I still not success to finish it.
so, if Android successful tar -xvf and make_ext4fs story, please share here, thank you very much!
any news to help me forward?