Related
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
After flashing a 16go kdz in my lg g2 d802 I lost my 32go memory, I followed this tuto http://forum.xda-developers.com/showthread.php?t=2470207&page=3
What I did ; used lg flash tools 2014 to flash 32 go kdz [doesn't solve the problem, just 10.7go] then I rooted my phone with iroot25,check root with root checker, copy files and overwrite by Total Commander to system/bin after making it RW, but when I set permissions to 755 and apply doesn't saved check again and found 602 so I can't use ADB to modify partitions and got permissions denied also I lose my root.
if I reboot phone I lose network
where is the problem??
I really appreciate your help, thank you very much
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
07459cead6cc4ddf device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # adb devices
adb devices
List of devices attached
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC 032G96 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 15.7GB 11.6GB ext4 userdata
36 15.7GB 15.8GB 37.7MB grow
(parted) quit
quit
quit
@ANDROID:/system # quit
quit
sh: quit: not found
127 @ANDROID:/system # ./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512
seek=61071327 conv=notrunc
of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: ./dd: not found
127 @ANDROID:/system # dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 se
ek=61071327 conv=notrunc
=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: dd: can't execute: Permission denied
126 @ANDROID:/system # /dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 s
eek=61071327 conv=notrunc
f=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: /dd: not found
127 @ANDROID:/system #
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Goona work hhh
Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Yes very true I learned a lot but this solution works for a lot of users, im just struggling with system/bin permissions, I know something wrong with SU or root or kdz or lg tools 2014, so im looking for the generosity of experts or people who had the same issue, im very sure its gonna work, in the same time, im trying to be familiar with android/Linux, lol, thank you for your reply
Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Everything is possible with Linux, you may learn something new from this thread too, lol
thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?
RE
Yoinx said:
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?
Click to expand...
Click to collapse
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man
thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
thequietman1979 said:
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man
Click to expand...
Click to collapse
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.
Solved
Yoinx said:
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.
Click to expand...
Click to collapse
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Yes Thanks for mentioning that : su in folder xbin and not system/bin
kindly try with this last 2 commands
2.
adb shell
su
cd /system
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
where can i find the files to download?
http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/
Hello! Please help!!! I try to paste the last two lines
./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
and when press enter it says : sh: ./dd: not found
I also try and these :
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
but with the same results!!
Which link process is the final? And where is a link with the finally sdparted-recovery-all-files?
Which firmware can i use before process? 4.2.2 or 4.4.2?
Which root i can use? With SuperSU or Superuser?
Which programe to use? Total commander or Root explorer??
PLease help me!
if i flash the correct kdz without doing anything else does it fix the problem ??
Please explain
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
How you root your phon, thats my biggest problem
Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
You need to root it before following the tutorial to get back 32go
http://forum.xda-developers.com/showthread.php?t=2470207&goto=newpost
To root your phone use iroot
Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448887
thequietman1979 said:
http://forum.xda-developers.com/showthread.php?t=2448887
Click to expand...
Click to collapse
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me
Ebaharloo said:
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me
Click to expand...
Click to collapse
What s the model of your lg g2?
If its d802 try to flash it back to kitkat using lg flash tool 2014 than root it using iroot or iroot 10, than follow the tuto, u gonna restore your memory
Root lg g2 d802 : http://forum.xda-developers.com/lg-...ols-how-to-install-twrp-bump-d80230a-t3072186.
Manual method: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
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
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!
Hello,
I am trying to install USB host-mode on my rooted nook simple touch so that I can use a keyboard or a mouse as a page turner. I am running 1.2.1, and rooted the nook using nook manager https://forum.xda-developers.com/showthread.php?t=2040351. This completed successfully. Then I installed a terminal app (can't find the link but it's called jackpal.androidterm.apk, can attach if needed) by putting it on a micro sd card and installing the file using relaunch (a file explorer app that appeared after rooting). Then I followed the instructions on https://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Replacing_boot_files writing
su
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
into the terminal app. It asked for permissions after su, which I granted and the other lines produced no errors but also no outputs. Now I am trying to find the /boot partition to replace uImage, as per the instructions, but I can't find /boot. It appears nowhere in the file explorer, and under advanced functions, the nook lists the following disks/partitions: /rom, /system, /data, /cache, /sdcard, /media, but no /boot
Any ideas? Really unsure as to why it's not showing up, because the commands that are supposed to create it seemed to complete without issue.
p.s. I also checked show hidden files in folders in the advanced settings
I dunno. Your "File Explorer" may be leading you astray.
Just do an ls -l in terminal and check.
ls -l produces:
drwxrwx--- system system 1969-12-31 16:00 rom
drwxrwxrwt root root 2018-02-26 11:11 sqlite_stmt_journals
d---rwxr-x system sdcard_rw 1969 -12-31 16:00 sdcard
drwxrwxr-x system sdcard_rw 1969 -12-31 16:00 media
drwxrwx--- system cache 2018-02-15 11:23 cache
drwxrwxrwx root root 2018-02-26 11:11 tmp
lrwxrwxrwx root root 2018-02-26 11:11 etc -> /system/etc
-rw-r--r-- root root 118 2018-02-15 12:03 init.rc.orig
-rw-r--r-- root root 118 2018-02-15 12:19 default.prop.orig
drwxr-xr-x root root 2018-02-05 12:19 system
drwxr-xr-x root root 1969-12-31 16:00 sys
drwxr-x--- root root 2018-02-15 12:03 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 1677 2018-02-15 12:03 init.goldfish.rc
-rwxr-x--- root root 128000 2018-02-15 12:03 init
-rwxr-x--- root root 324 2018-02-15 12:03 env.txt
drwxrwx--x system system 2018-02-15 11:24 data
-rw-r--r-- root root 118 2018-02-15 12:03 default.prop
-rwxr-x--- root root 19284 2018-02-15 12:03 init.rc
drwx------ root root 2012-12-07 14:34 root
drwxr-xr-x root root 2018-02-26 11:11 dev
Further, I tried to copy uImage into /boot using the terminal and it acted as if /boot didn't exist, so I'm pretty sure that it isn't there for some reason.
Thanks
Well, something you're doing isn't working.
The commands are correct.
Code:
su
Did this work? Do you get a # prompt? Type "id", does it say you're root?
Code:
mount -o rw,remount rootfs /
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
Code:
mkdir /boot
Apparently this didn't work because you should see an empty directory at least.
Code:
mount -t vfat /dev/block/mmcblk0p1 /boot
Apparently this didn't work.
Did this work? Do you get a # prompt? Type "id", does it say you're root?
su produces a # prompt, and id produces: uid=0(root) gid=0(root), so i think this part worked.
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
mount produces: rootfs / rootfs rw 0 0, and then a bunch of other stuff, so i think this worked too.
mkdir /boot
this produces nothing, just another # prompt, so this might be the problem
mount -t vfat /dev/block/mmcblk0p1 /boot
this also produces nothing, just another # prompt.
Any idea why mkdir /boot would fail?
Thanks for being so helpful!
Well, the mkdir should have created an empty directory.
You should be able to "ls -l /" it.
If not, you could mkdir and mount anywhere.
Code:
cd /data/local/tmp
mkdir mybooty
mount -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mybooty
There's nothing special about the name "boot".
Okay,
That solved the problem. Thanks for all your help!