New recovery in OTA - G2 and Desire Z General

It appears the new OTA brought us a new recovery...
ORIGINAL:
Code:
[email protected]:~/Desktop/G2ROOT/G2-SHIPPING$ [B]ls -al recovery.img
-rw-r--r-- 1 unforgiven512 unforgiven512 4796416 2010-09-15 04:43 recovery.img[/B]
[email protected]:~/Desktop/G2ROOT/G2-SHIPPING$ [B]md5sum recovery.img
6a0c19b0e05dcc68e2a60e6cb6cf42bc recovery.img[/B]
OTA:
Code:
[email protected]:~/Desktop/G2ROOT/G2-OTA-11-03-2010$ [B]ls -al recovery.img
-rw-r--r-- 1 unforgiven512 unforgiven512 4763648 2008-12-31 11:00 recovery.img[/B]
[email protected]:~/Desktop/G2ROOT/G2-OTA-11-03-2010$ [B]md5sum recovery.img
1d5d280af717f9afd7ce1c3285c129bc recovery.img[/B]
Hmm?

It was stated in the OTA update changes log.
Sent from my T-Mobile G2 using XDA App

Where is this change log?

Related

[TUTORIAL] Unpack and repack boot.img + a2sd support for XXKPH

Hi ppl,
Today I will tell you howto unpack and repack your Galaxy Ace boot.img files. First the base and page size:
Code:
The base parameter is 0x13600000 and pagesize is 4096
- First get your boot.img from CWM backup / odin package / dump etc.
- In linux make a folder on your desktop called something like bootrepack
- Place your original boot.img there along with the extracted files from the attached zip.
- Run this command to split your boot.img
Code:
./split_bootimg.pl boot.img
This will split your boot.img in kernel and ramdisk.
If you get permission error try to chmod the file to 755
- Now extract your ramdisk to make modifications to init.rc for example.
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
cd ..
- Make the required modifications.
- You can also replace kernel by deleting boot.img-kernel, and replace it by zImage.
- After all the necessary modifications are done you can make a new boot.img using this:
Code:
./repack_bootimg.pl boot.img-kernel ramdisk bootnew.img
- Finally move your bootnew.img to a new location and rename it to boot.img. From there you can create update.zip to flash it using CWM
Always make sure you have a proper nandroid backup before you flash a new boot.img
If your repack fails you can always restore using CWM - > Backup and Restore - > Advanced Restore - > Date/time bla bla -> Restore boot
--------
Added bonus: I've edited coolya's ext4 kernel for XXKPH to also run install_recovery.sh for a2sd support. Flash using CWM -> Install zip -> ext4-a2sd-update.zip
--------
Sources:
- Android-dls on Unpacking and editing boot images
- Ysgace for base and pagesize
- k0mpresd/original author for repack script
nice job!!...will help people immensely to build their own ROMs!!...
Can you make a noob tutorial for enabling a2sd?
Sent from my Galaxy ace using Tapatalk
There already is one: Enabling Darktremor a2sd on Samsung s5830 Galaxy ACE
After apply this update ext4-a2sd-update.zip link2sd will be working on S5830XXKPH Rom and mount SD ext2 partition?
bizon69 said:
After apply this update ext4-a2sd-update.zip link2sd will be working on S5830XXKPH Rom and mount SD ext2 partition?
Click to expand...
Click to collapse
The kernel will run install-recovery.sh on boot
peeter123 said:
There already is one: Enabling Darktremor a2sd on Samsung s5830 Galaxy ACE
Click to expand...
Click to collapse
"This method has been tested on a rooted Galaxy ACE running Android 2.2.1. It might work on other devices, but I don't guarantee."
is this work on KPH ?
install_recovery.sh didnt work for me. i Flashed using CWM -> Install zip -> ext4-a2sd-update.zip.
Here's what "cat /system/etc/install-recovery.sh" shows:
#!/system/bin/sh
/system/bin/mount -t ext2 /dev/block/mmcblk0p2 /system/sd
/system/bin/sh /system/etc/init.d/dtapp
/system/bin/sh /system/etc/init.d/99complete
but didnt work a2sdgui
sametpoyraz said:
install_recovery.sh didnt work for me. i Flashed using CWM -> Install zip -> ext4-a2sd-update.zip.
Here's what "cat /system/etc/install-recovery.sh" shows:
#!/system/bin/sh
/system/bin/mount -t ext2 /dev/block/mmcblk0p2 /system/sd
/system/bin/sh /system/etc/init.d/dtapp
/system/bin/sh /system/etc/init.d/99complete
but didnt work a2sdgui
Click to expand...
Click to collapse
Did you chmod 755 install-recovery.sh?
yeah i did
i have S5830XXKPH rom. and kernel 2.6.35.7-perf-CL260130. what is the problem ?
can it work on jellybean?
peeter123 said:
- Now extract your ramdisk to make modifications to init.rc for example.
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
cd ..
- Make the required modifications.
Click to expand...
Click to collapse
Hi,
I have problem while extracting "boot.img-ramdisk.gz" file. I hope this is not getting created as zip file during the extracting process.
[email protected]:~/VIJAY/andriod/work2$ ./split_bootimg.pl boot.img
Page size: 2048 (0x00000800)
Kernel size: 3477896 (0x00351188)
Ramdisk size: 596322 (0x00091962)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[email protected]:~/VIJAY/andriod/work2$
[email protected]:~/VIJAY/andriod/work2$ ls
boot.img data/ LeWa_A919build.1.09.zip META-INF/ repack_bootimg.pl* split_bootimg.pl*
Bootimgutils.zip installbusybox logo.bin mkbootimg* sdcard/ system/
[email protected]:~/VIJAY/andriod/work2$ mkdir ramdisk
[email protected]:~/VIJAY/andriod/work2$
[email protected]:~/VIJAY/andriod/work2$
[email protected]:~/VIJAY/andriod/work2$ ls -lrt
total 336788
-rwxrwxrwx 1 vramaraj sw-team 28614 Dec 24 2010 mkbootimg*
-rwxrwxrwx 1 vramaraj sw-team 6773 Jul 17 2011 split_bootimg.pl*
-rwxrwxrwx 1 vramaraj sw-team 569 Jul 17 2011 repack_bootimg.pl*
drwxr-xr-x 3 vramaraj sw-team 4096 Oct 9 2011 data/
-rw-r--r-- 1 vramaraj sw-team 70 May 16 2012 installbusybox
drwxr-xr-x 4 vramaraj sw-team 4096 Oct 6 19:03 sdcard/
-rw-r--r-- 1 vramaraj sw-team 333103 Jan 10 16:02 logo.bin
drwxr-xr-x 16 vramaraj sw-team 4096 Jan 21 06:20 system/
-rw-r--r-- 1 vramaraj sw-team 4079616 Jan 21 21:07 boot.img
-rw-r--r-- 1 vramaraj sw-team 15413 Jan 31 21:58 Bootimgutils.zip
-rw-r--r-- 1 vramaraj sw-team 197379000 Jan 31 21:59 LeWa_A919build.1.09.zip
drwxr-xr-x 3 vramaraj sw-team 4096 Jan 31 21:59 META-INF/
-rw-r--r-- 1 vramaraj sw-team 3477896 Jan 31 22:00 boot.img-kernel
-rw-r--r-- 1 vramaraj sw-team 596322 Jan 31 22:00 boot.img-ramdisk.gz
drwxr-xr-x 2 vramaraj sw-team 4096 Jan 31 22:00 ramdisk/
-rw-r--r-- 1 vramaraj sw-team 138215424 Jan 31 22:14 YONIP_MP_A919_v1.zip
[email protected]:~/VIJAY/andriod/work2$
[email protected]:~/VIJAY/andriod/work2$ cd ramdisk
[email protected]:~/VIJAY/andriod/work2/ramdisk$ gunzip -c ../boot.img-ramdisk.gz | cpio -i
gunzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
[email protected]:~/VIJAY/andriod/work2/ramdisk$ unzip ../boot.img-ramdisk.gz
Archive: ../boot.img-ramdisk.gz
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of ../boot.img-ramdisk.gz or
../boot.img-ramdisk.gz.zip, and cannot find ../boot.img-ramdisk.gz.ZIP, period.
[email protected]:~/VIJAY/andriod/work2/ramdisk$ tar zvf ../boot.img-ramdisk.gz
tar: You must specify one of the `-Acdtrux' options
Try `tar --help' or `tar --usage' for more information.
[email protected]:~/VIJAY/andriod/work2/ramdisk$ tar xvf ../boot.img-ramdisk.gz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
tar: Read 2402 bytes from ../boot.img-ramdisk.gz
tar: Error exit delayed from previous errors
[email protected]-swe-09:~/VIJAY/andriod/work2/ramdisk$
[email protected]:~/VIJAY/andriod/work2/ramdisk$
Click to expand...
Click to collapse
I tried to read the contents in the file. But it has having binary code. Which confirms it is not a zip file. Any clues..?
---------- Post added at 11:53 AM ---------- Previous post was at 11:41 AM ----------
Update:
Is this the process it will do?
gzip decompresses the ramdisk archive to stdout, pipe it into cpio with the -i switch to read from stdin and it will correctly extract the data
Click to expand...
Click to collapse
.
But I am getting this..
Code:
[email protected]:~/VIJAY/andriod/work3/ramdisk$ gzip -dc ../boot.img-ramdisk.gz | cpio -i
[COLOR="Red"][B]gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive[/B][/COLOR]
[email protected]:~/VIJAY/andriod/work3/ramdisk$
Isn't this just copy + pasted from anonymous's kernel guide?:sly:
Sent from my GT-I9070 using xda premium
hello, please, its wat to decompile file "recovery" in "sbin" folder and translate it? I would like to translate recovery into my language.
Thanks....
hello mi have a problem with my scroll basic plus 54860 boot not starting do you have root to this tablet?? b1 and b

Amazon Kindle Fire Flash

my flash isn't working ...
i found these two, maybe the problem because I have 2?
# ls -l /system/app/oem_install_flash_player_signed_dcts.apk
-rw-r--r-- root root 46562 2008-08-01 08:00 oem_install_flash_player_signed_dcts.apk
# ls -l /data/app/com.adobe.flashplayer-1.apk
-rw-r--r-- system system 4693820 2011-11-29 00:15 com.adobe.flashplayer-1.apk
#
Click to expand...
Click to collapse

remount failed??

Problem fixed !!! Thansk!
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
would thing you get the $ prompt if you open the adb shell
enter "su" - the prompt should change to #
then the remount command should succeed
enter "su" - the prompt should change to # in shell mode
then type : # adb remount ?
could you get me a detail command set ?. because kindle fire is my first's android device , BIG THANKS!
this should be the way it works:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
the bold commands are the ones to enter ...
My file is saved in c:\apps\hk.cedime.inputmethod.apk
and also have a copy in c:\adb\hk.cedime.inputmethod.apk
Show many error ??? Any expert can help?
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# install c:\apps\hk.cedime.inputmethod.apk /system/app/
install c:\apps\hk.cedime.inputmethod.apk /system/app/
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
# install hk.cedime.inputmethod.apk /system/app/
install hk.cedime.inputmethod.apk /system/app/
install: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp hk.cedime.inputmethod.apk /system/app/
cp hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
Click to expand...
Click to collapse
it don't find the .apk file
i use to put the files to install in the directory where adb.exe resides
and do the command without a path ie: install hk.cedime.inputmethod.apk /system/app/
furthermore i'm not shure if the command works inside the adb shell
would also try (from command prompt):
adb install c:\apps\hk.cedime.inputmethod.apk /system/app/
or if .apk in current directory (where adb resides):
adb install hk.cedime.inputmethod.apk /system/app/
Adb command is my first choice
But the system show the error : can't find '/system/app/' to install
then it seems not to be mounted ...
try to check with:
"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system"
"cd \system"
"ls -l" -> any directory listing here ?
"cd app"
"ls -l" -> any apk's listed ?
OH! my God!
c:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
no problem - if it's not mounted it's hard to remount
would try:
"mount /system" in adb shell
or
"adb shell mount -o remount rw /system" from the command prompt
Sorry, many problem can't fix...............
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# ls -l
ls -l
dr-x------ root root 2012-03-19 05:51 config
drwxrwx--- system system 2012-03-20 07:00 dropbox
drwxrwx--- system cache 2012-03-19 05:51 cache
lrwxrwxrwx root root 2012-03-19 05:51 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-03-19 05:51 acct
drwxrwxr-x root system 2012-03-19 05:51 mnt
lrwxrwxrwx root root 2012-03-19 05:51 vendor -> /system/vendor
lrwxrwxrwx root root 2012-03-19 05:51 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-03-19 05:51 etc -> /system/etc
-rw-r--r-- root root 4203 1969-12-31 16:00 ueventd.rc
-rw-r--r-- root root 840 1969-12-31 16:00 ueventd.omap4430.rc
-rw-r--r-- root root 0 1969-12-31 16:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-01-19 04:27 system
drwxr-xr-x root root 2012-03-19 05:51 sys
drwxr-x--- root root 1969-12-31 16:00 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 14869 1969-12-31 16:00 init.rc
-rwxr-x--- root root 11357 1969-12-31 16:00 init.omap4430.rc
-rwxr-x--- root root 1677 1969-12-31 16:00 init.goldfish.rc
-rwxr-x--- root root 94200 1969-12-31 16:00 init
-rw-r--r-- root root 118 1969-12-31 16:00 default.prop
drwxrwx--x system system 2012-03-18 06:53 data
drwx------ root root 2012-01-09 22:20 root
drwxr-xr-x root root 2012-03-19 06:01 dev
# cd app
cd app
cd: can't cd to app
#
from your post #5:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
this has seemed to work - or was there allways a error message following up which you did'nt copy and paste ?
usually "mount /system" is sufficient - "mount -w /system" should work too
# cd app
cd app
cd: can't cd to app
Click to expand...
Click to collapse
if you look to the directory listing you are on the root - there is no directory or mountpoint "app" - it is in the system directory - the command should be:
"cd \system"
"ls -l" -> any directory listing here ?
and then if you are in "system"
"cd app"
"ls -l" -> any apk's listed ?
as in post #8
Expert ! Next step what can i do?
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd \system
cd \system
# ls -l
ls -l
drwxr-xr-x root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2012-03-19 05:49 app
drwxr-xr-x root shell 2012-03-17 18:19 bin
-rw-r--r-- root root 2151 2008-08-01 05:00 build.prop
drwxr-xr-x root root 2012-01-19 04:27 etc
drwxr-xr-x root root 2012-01-19 04:27 fonts
drwxr-xr-x root root 2012-01-19 04:27 framework
drwxr-xr-x root root 2012-01-19 04:27 lib
drwxr-xr-x root root 2012-01-19 04:27 media
drwxr-xr-x root root 2012-01-19 04:27 tts
drwxr-xr-x root root 2012-01-19 04:27 usr
drwxr-xr-x root shell 2012-01-19 04:27 vendor
drwxr-xr-x root shell 2012-03-17 20:51 xbin
# cd app
cd app
# ls -l
ls -l
-rw-r--r-- root root 2669573 2008-08-01 05:00 ATVAndroidClient.apk
-rw-r--r-- root root 233689 2008-08-01 05:00 AccountAndSyncSettings.ap
k
-rw-r--r-- root root 3581879 2008-08-01 05:00 AmazonVenezia.apk
-rw-r--r-- root root 29574 2008-08-01 05:00 ApplicationsProvider.apk
-rw-r--r-- root root 3574986 2008-08-01 05:00 AudibleAndroidApplication
-venezia.apk
-rw-r--r-- root root 164188 2008-08-01 05:00 CSApp-unsigned.apk
-rw-r--r-- root root 152004 2008-08-01 05:00 CalendarProvider.apk
-rw-r--r-- root root 116225 2008-08-01 05:00 CertInstaller.apk
-rw-r--r-- root root 4019454 2008-08-01 05:00 Cloud9-release-unsigned.a
pk
-rw-r--r-- root root 57208 2008-08-01 05:00 Cloud9SystemBrowserProvid
er-unsigned.apk
-rw-r--r-- root root 2049942 2008-08-01 05:00 Contacts.apk
-rw-r--r-- root root 145545 2008-08-01 05:00 ContactsProvider.apk
-rw-r--r-- root root 20748 2008-08-01 05:00 DefaultContainerService.a
pk
-rw-r--r-- root root 196150 2008-08-01 05:00 DownloadProvider.apk
-rw-r--r-- root root 106749 2008-08-01 05:00 DownloadProviderUi.apk
-rw-r--r-- root root 32432 2008-08-01 05:00 DrmProvider.apk
-rw-r--r-- root root 2315338 2008-08-01 05:00 Email.apk
-rw-r--r-- root root 16892 2008-08-01 05:00 Facebook.apk
-rw-r--r-- root root 833544 2008-08-01 05:00 Gallery3D.apk
-rw-r--r-- root root 22792 2008-08-01 05:00 HTMLViewer.apk
-rw-r--r-- root root 1685594 2008-08-01 05:00 IMDb-2.3.apk
-rw-r--r-- root root 16424244 2008-08-01 05:00 KindleForOtter.apk
-rw-r--r-- root root 1082002 2008-08-01 05:00 LatinIME.apk
-rw-r--r-- root root 12174497 2008-08-01 05:00 Launcher.apk
-rw-r--r-- root root 1140587 2008-08-01 05:00 LiveWallpapers.apk
-rw-r--r-- root root 51276 2008-08-01 05:00 LiveWallpapersPicker.apk
-rw-r--r-- root root 224152 2008-08-01 05:00 MagicSmokeWallpapers.apk
-rw-r--r-- root root 20778 2008-08-01 05:00 MarketIntentProxy.apk
-rw-r--r-- root root 62533 2008-08-01 05:00 MediaProvider.apk
-rw-r--r-- root root 149119 2008-08-01 05:00 MyAccount-unsigned.apk
-rw-r--r-- root root 253116 2008-08-01 05:00 OOBE-unsigned.apk
-rw-r--r-- root root 26983 2008-08-01 05:00 OTASilentInstall.apk
-rw-r--r-- root root 110563 2008-08-01 05:00 OtterAppManager.apk
-rw-r--r-- root root 1907710 2008-08-01 05:00 OtterTutorial.apk
-rw-r--r-- root root 122758 2008-08-01 05:00 PackageInstaller.apk
-rw-r--r-- root root 22282 2008-08-01 05:00 PicoTts.apk
-rw-r--r-- root root 10496 2008-08-01 05:00 Provision.apk
-rw-r--r-- root root 2305323 2008-08-01 05:00 Pulse-amazon.apk
-rw-r--r-- root root 412698 2008-08-01 05:00 QuickSearchBox.apk
-rw-r--r-- root root 320688 2008-08-01 05:00 QuickSettings.apk
-rw-r--r-- root root 6302776 2008-08-01 05:00 Quickoffice_AMAZON_4.1.46
7_VC.apk
-rw-r--r-- root root 3751962 2008-08-01 05:00 Settings.apk
-rw-r--r-- root root 48682 2008-08-01 05:00 SettingsProvider.apk
-rw-r--r-- root root 604484 2008-08-01 05:00 SystemUI.apk
-rw-r--r-- root root 30187 2008-08-01 05:00 TtsService.apk
-rw-r--r-- root root 16928 2008-08-01 05:00 UserDictionaryProvider.ap
k
-rw-r--r-- root root 165579 2008-08-01 05:00 VisualizationWallpapers.a
pk
-rw-r--r-- root root 34247 2008-08-01 05:00 VpnServices.apk
-rw-r--r-- root root 1669753 2008-08-01 05:00 Windowshop.apk
-rw-r--r-- root root 6113490 2008-08-01 05:00 air_runtime.apk
-rw-r--r-- root root 2109670 2008-08-01 05:00 amazonmp3-unsigned.apk
-rw-r--r-- root root 2500819 2008-08-01 05:00 com.amazon.dcp.apk
-rw-r--r-- root root 45888 2008-08-01 05:00 oem_install_flash_player_
signed.apk
-rw-r--r-- root root 843503 2008-02-28 10:33 Superuser.apk
-rw-rw-rw- root root 89707 2011-12-07 02:26 GoogleFeedback.apk
-rw-rw-rw- root root 1401398 2011-12-07 02:13 GoogleServicesFramework.a
pk
-rw-rw-rw- root root 1529836 2011-12-07 02:15 Vending.apk
-rw-rw-rw- root root 4089926 2011-12-07 02:22 GO_Launcher_EX_2.65.apk
-rw-rw-rw- root root 2053065 2012-03-19 05:49 hk.cedime.inputmethod.apk
#
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
as you run a unsecure kernel i think the command should be:
adb shell su -c "remount"
or
adb shell su -c "mount -o remount rw /system"
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
the second attempt succeeded - so your question seems to be answered or not ?
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
Click to expand...
Click to collapse
Expert!
i follow this link
http://forum.xda-developers.com/showthread.php?t=1364543
to fixed my problem, Thanks for your support again!!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

[Z00T] Possible corrupted /firmware file(s)

Hi,
A little while back, my Z00T stopped booting (would bootloop shortly after the splash screen). Even with stock.
Looks like logcat line 187 is kicking my butt.
I can get in TWRP with no issue, so I have been tracking down the problem from there, and now suspect a corrupt /firmware partition (or a few files within).
Can a Z00T owner with the MM bootloader (preferably June 2nd 2016 update, can verify with first command below), go into TWRP, mount the firmware partition (under Mounts) and run the following two commands?:
Code:
~ # ls -l /firmware/image/keymaste.*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rwxrwxrwx 1 root root 180 Jun 2 2016 /firmware/image/keymaste.b00
-rwxrwxrwx 1 root root 6568 Jun 2 2016 /firmware/image/keymaste.b01
-rwxrwxrwx 1 root root 126672 Jun 2 2016 /firmware/image/keymaste.b02
-rwxrwxrwx 1 root root 8132 Jun 2 2016 /firmware/image/keymaste.b03
-rwxrwxrwx 1 root root 6748 Jun 2 2016 /firmware/image/keymaste.mdt
~ # md5sum /firmware/image/keymaste.*
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
~ #
Please paste your results in a reply with the CODE tags for comparison (feel free to give me a mention or have a partial QUOTE in your reply).
Bonus points for (if you have the right date but a different hash)...
I will probably need a new firmware partition, and hope my internal SD is not dying.
If noone knows where I can find an official one, you can make one by first verifying the partition number (should be 41):
Code:
adb shell cat /proc/mounts | grep firmware
Then make an image copy to file with dd* to the external sd (using partition 41), download to PC:
Code:
adb shell dd if=/dev/block/mmcblk0p41 of=/sdcard1/firmware.img
adb pull /sdcard1/firmware.img
* Issue the command verbatim, or don't issue at all if not familiar with dd. If used incorrectly, dd can do some serious damage. Been there, done that, always check your work.
This will help me out in continuing to use this device for development purposes.
ZD551KL Selfi / Z00T. ROM CM13 for Z00T
Code:
C:\adb>adb shell ls -l /firmware/image/keymaste.*
-r--r--r-- root root 180 2016-08-05 04:59 keymaste
-r--r--r-- root root 6568 2016-08-05 04:59 keymaste
-r--r--r-- root root 126672 2016-08-05 04:59 keymaste
-r--r--r-- root root 8132 2016-08-05 04:59 keymaste
-r--r--r-- root root 6748 2016-08-05 04:59 keymaste
C:\adb>adb shell md5sum /firmware/image/keymaste.*
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
Well then...that blows that out of the water - the hashes match even with a different model num and OTA date.
Unless the partition is only readable under certain circumstances (system boot not being one of them but TWRP seems more forgiving), then I will need a replacement ZE551KL firmware.img. If it is still something else, I will then be unsure how to proceed since this is a problem across multiple boot.img's so it's not a kernel or ramdisk issue yet still prevents /vendor from getting set up before /vendor symlinks to /system/vendor.
Here is md5sum of my z00t ze601kl
Code:
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
Code:
-r--r--r-- system system 180 2016-08-03 00:38 keymaste.b00
-r--r--r-- system system 6568 2016-08-03 00:38 keymaste.b01
-r--r--r-- system system 126672 2016-08-03 00:38 keymaste.b02
-r--r--r-- system system 8132 2016-08-03 00:38 keymaste.b03
-r--r--r-- system system 6748 2016-08-03 00:38 keymaste.mdt

[ROOT][TWRP][v500] Lineage OS

Hi
I was finally able to root my device, install TWRP on it and install lineageOS.
The methods that I found before don't fully work due to the latest firmware versions, but I found a way around it. You can find the necessary files in a zip file. Unfortunately I have few posts so I can't post links... is there a way to post a link to the zip file?
The file is in dropbox with path:
dropbox.com/s/s1vcd8z3c2chf4o/v500.zip?dl=0
unzip and follow the commands described in root.sh they are a bit succint but it worked for me.
Afterwards, just use TWRP to flash the lineageos image + gapps
The commands that I executed are:
adb reboot recovery
# Sideload kk_root.zip
adb push twrp-3.1.1-0-v500.img /sdcard/
adb push ./aboot.img /sdcard/flash_tmp/aboot.img
adb push ./recovery.lok /sdcard/flash_tmp/recovery.lok
dd if=/sdcard/flash_tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/flash_tmp/recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# Copy stuff to /mnt/asec chmod a+x
# update super su
/mnt/asec # cp /storage/emulated/0/flash_tmp/* .
/mnt/asec # ls -l
-rw------- root root 524288 2017-09-13 01:52 aboot.img
-rw------- root root 524288 2017-09-13 01:52 aboot2.img
-rwxr-xr-x root root 1085140 2017-09-13 01:50 busybox
-rwxr-xr-x root root 76540 2017-09-13 01:52 loki_tool
-rw------- root root 11597824 2017-09-13 01:52 recovery.img
-rw------- root root 11001856 2017-09-13 01:52 recovery.lok
/mnt/asec # ./loki_tool
Loki tool v2.1
Usage
> Patch partition file image:
./loki_tool [patch] [boot|recovery] [aboot.img] [in.img] [out.lok]
> Flash loki image to boot|recovery:
./loki_tool [flash] [boot|recovery] [in.lok]
> Find offset from aboot image:
./loki_tool [find] [aboot.img]
> Revert Loki patching:
./loki_tool [unlok] [in.lok] [out.img]
/mnt/asec # ./loki_tool patch recovery aboot.img recovery.
recovery.img recovery.lok
/mnt/asec # ./loki_tool patch recovery aboot.img recovery.img recovery.lok
Loki tool v2.1
[+] Detected target International LG G Pad 8.3 build V50010a
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to recovery.lok
/mnt/asec # ./loki_tool flash recovery recovery.lok
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
/mnt/asec # ./loki_tool patch recovery aboot.img /st
/mnt/asec # ls -l /storage/emulated/0/twrp-3.1.1-0-v500.img
-rw-rw---- root sdcard_r 14444560 2017-09-13 01:18 twrp-3.1.1-0-v500.img
/mnt/asec # ./loki_tool patch recovery aboot.img /storage/emulated/0/twrp-3.1.1-
0-v500.img recovery.lok
Loki tool v2.1
[+] Detected target International LG G Pad 8.3 build V50010a
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to recovery.lok
/mnt/asec # ls -l
-rw------- root root 524288 2017-09-13 01:52 aboot.img
-rw------- root root 524288 2017-09-13 01:52 aboot2.img
-rwxr-xr-x root root 1085140 2017-09-13 01:50 busybox
-rwxr-xr-x root root 76540 2017-09-13 01:52 loki_tool
-rw------- root root 11597824 2017-09-13 01:52 recovery.img
-rw------- root root 14446592 2017-09-13 01:54 recovery.lok
/mnt/asec # ./loki_tool flash recovery recovery.lok
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!

Categories

Resources