Cwm v5.0.2.7 For LG Nitro HD (P930) /Optimus LTE
Current Status: Operational
Installation/Update Instructions:
Before installing make sure that your phone is rooted
Code:
Backup your existing recovery:
1) [COLOR="Magenta"]cat /dev/block/mmcblk0p13 > /sdcard/recovery-backup.img[/COLOR]
Flash the new recovery by:
1) Download the bc64-recovery.rar and extract it
2) Copy the extracted bc64-recovery.img to your /sdcard
3) via terminal emulator or adb shell execute:
[COLOR="Magenta"]
su
cd /sdcard
cat bc64-recovery.img > /dev/block/mmcblk0p13[/COLOR]
All Done!
Now to Boot into recovery , press the vol down+pwr button , when it asks you to factory reset , tap twice the pwr button to confirm (dont worry it wont format your device)
Screenshots:
Video:
Code:
http://www.youtube.com/watch?v=okr8PWeQ30E
ChangeLog:
Code:
v0.2 B20120124
Changes:
* Added postrecoveryboot.sh to clear out boot command
* Added Partition/fs Utils (useful for rom dev in formatting/checking ext4 fs)
-e2fsck_static
-mke2fs_static
-resize2fs_static
-tune2fs_static
v0.1 B20120120 (Initial Release)
Known Issues:
Code:
wrong timestamps
Tested On:
Code:
Atnt LG Nitro HD (P930)
LG Optimus LTE (SU640)
Thanks To:
Code:
schwin97
[email protected]
Malnilion
repherb
aquariuz23
gte460z
and everyone else who contributed to this thread :P
Download:
Code:
http://www.mediafire.com/?mnf53sxmp5aifd9
Source Code (Sorry , too lazy for github fttb):
Code:
http://www.mediafire.com/?f27d8j8d7mc8qi8
For Rom Developers:
It seems that default cwm format is messing up (due to ext4 file system) , Please use (edify) the following script to format the data and cache partition (or System)
Code:
#Format Data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
#Format Cache
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p28
# After Format Verify the FIle System
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p28
Edify (To Format System):
Code:
run_program("/sbin/mke2fs_static", "-t" , "ext4" "/dev/block/mmcblk0p27");
AND
run_program("/sbin/e2fsck_static", "-y", "/dev/block/mmcblk0p27");
/proc/mtd doesn't exist...
Don't know if this any help:
http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32
Images Added based on the info provided :
Code:
http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32
Is this suppose to be Clockwork Mod for the Nitro? Wat's with the 5? Version 5?
Can you teach me how to make the recovery.img.
My device is LG Optimus LTE SU640 which has the most same hardware with P930.
Yes this is version 5
@belth219 ill port it for you once i get confirmation for this image
Ok,thanks.
@belth219 could you do a "cat /proc/partitions" on your cell and post its results?
Also providing the results for the above command for nitro HD would also be very usefull.
This is the result of my lu6200
Another version of p930
# su
su
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1048576 mmcblk0p26
179 27 327680 mmcblk0p27
179 28 1548288 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 229376 mmcblk0p31
259 0 4096 mmcblk0p32
179 32 7774208 mmcblk1
179 33 7773184 mmcblk1p1
#
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p26 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p29 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p31 /lgumsg ext4 rw,nosuid,nodev,relatime,barrier=1,data=order
ed 0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
My phone is LU6200,too. Could you tell me if I can install this mod on my phone? The only difference of 2 device is the CPU
I dont think it would work on your device as im sure it has diffrent kernel , upload your boot.img , i will port it once i get nitro hd confirmation
SU640
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 860160 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 3072 mmcblk0p29
179 30 1957638 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 2048 mmcblk0p32
179 32 15622144 mmcblk1
179 33 15618048 mmcblk1p1
254 0 2110 dm-0
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p27 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p30 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.cyandroid.pianofull-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
OK...
I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...
---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------
Upon using anreboot to boot into recovery I get...
Code:
Enter the fastboot...
Enter the fastboot...
Long time no see!
And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...
Now to see if I can reboot normally?
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
And it still boots normally and is fully functional when it does boot!!! Good progress so far. Now, does anyone know how to determine the driver it is looking for? I think if I find the right driver I can get into fastboot mode and do anything else that is necessary?
schwin97 said:
OK...
I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...
---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------
Upon using anreboot to boot into recovery I get...
Code:
Enter the fastboot...
Enter the fastboot...
Long time no see!
And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...
Now to see if I can reboot normally?
Click to expand...
Click to collapse
Why did you ran cat /dev/zero > /dev/block/mmcblk0p27?
as of this http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32 post your recovery partition should be /dev/block/mmcblk0p27
so To be me steps would have been:
1) Backing up recovery partition using dd
2) Remounting System partiton as read write
3) copying recovery.img to /system and flashing the recovery.img
4) booting into recovery
For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html
I agree, but when I miss the part about putting the recovery image in the system directory for it to automatically reflash, I started running the steps to flash the recovery image as people flash the boot image...
An extra step that luckily didn't have any bad consequences...
---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------
bytecode64 said:
For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html
Click to expand...
Click to collapse
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
what about USB drivers and Modem?
Did you installed http://s3.amazonaws.com/lgforum.com/resources/assets/680/original/LGP930.zip?1322664514
?
I have uploaded my boot.img & recovery.img to dropbox.
But I can not post any links now.It needs 8 posts.
Sure did. I have the drivers that are needed when the phone boots up normally? Just when it boots up in this new recovery mode that it is asking for a new driver? It shouldn't be asking for anything new, but it is... Another question - after it loads up the new recovery image from the /system directory should it remove the recovery image? If so, then if the recovery image is still in the system directory we may have a problem?
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I had thought - recovery.img is still in the system directory... Does this indicate a problem?
schwin97 said:
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
Click to expand...
Click to collapse
You should install the LGMobile update which can be downloaded from LG official website.
That is a useful tool.
Hi, similar to couple of threads, but - I believe - specific enough to start a new dedicated one. I have endeavoru HOX, cid HTC__032. Some time ago I damaged partition layout. It was complete ignorant era - I was doing things I should have read about before I bought used HOX with stock 3.14.401.31 (OTA update applied in the meantime as far as I rmember), I was experiencing some problems with it so unlocked, pushed CWM recovery and installed CM 10.1.3. Unfortunately, gapps kept crashing so I decided to do some cleaning and apparently did the factory reset in custom recovery. I guess this brought me to the state my HOX is in now.
So, how the things look like:
1. This is my current HOX info:
Code:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.401.31
(bootloader) serialno: *****
(bootloader) imei: *****
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) devpower: 54
[B](bootloader) partition-layout: None[/B]
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
2. I can connect via fastboot/adb - flash, use adb shell, etc. I can also push files, create and write files in adb shell, so it looks like the card is not entirely dead
3. I can flash recovery (tried TWRP and CWM) - so no problem with charging anymore
4. No partition layout and I can’t mount storage:
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
4 heads, 16 sectors/track, 954240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
(parted) print
print
Error: /dev/block/mmcblk0: unrecognised disk label
(parted) mklabel msdos
mklabel msdos
(parted) print
print
Error: /dev/block/mmcblk0: unrecognised disk label
Code:
~ # ls -la /dev/block/
drwxr-xr-x 3 root root 300 Nov 4 21:11 .
drwxr-xr-x 9 root root 2320 Nov 4 21:07 ..
brw------- 1 root root 7, 0 Nov 4 21:07 loop0
brw------- 1 root root 7, 1 Nov 4 21:07 loop1
brw------- 1 root root 7, 2 Nov 4 21:07 loop2
brw------- 1 root root 7, 3 Nov 4 21:07 loop3
brw------- 1 root root 7, 4 Nov 4 21:07 loop4
brw------- 1 root root 7, 5 Nov 4 21:07 loop5
brw------- 1 root root 7, 6 Nov 4 21:07 loop6
brw------- 1 root root 7, 7 Nov 4 21:07 loop7
brw------- 1 root root 179, 0 Nov 4 21:07 mmcblk0
-rw-r--r-- 1 root root 0 Nov 4 21:12 mmcblk0p13
-rw-r--r-- 1 root root 0 Nov 4 21:12 mmcblk0p15
-rw-rw-rw- 1 root root 1088 Nov 4 21:12 mmcblk0p17
drwxr-xr-x 3 root root 60 Nov 4 21:07 platform
[I]-- (but this mmcblk0pxx are there only because I tried to format - unsuccessfully - related partitions through recovery) --[/I]
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p15 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p14 /sdcard auto rw
~ # cat /etc/recovery.fstab
# mount point fstype device [device2]
/recovery emmc /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p4
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p15
/sdcard auto /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/misc emmc /dev/block/mmcblk0p17
~ # cat /proc/emmc
dev: size erasesize name
mmcblk0p5: 00800000 00001000 "recovery"
mmcblk0p4: 00800000 00001000 "boot"
mmcblk0p12: 50000000 00001000 "system"
mmcblk0p13: 14000000 00001000 "cache"
mmcblk0p17: 00200000 00001000 "misc"
mmcblk0p1: 00600000 00001000 "wlan"
mmcblk0p2: 00200000 00001000 "WDM"
mmcblk0p20: 00200000 00001000 "pdata"
mmcblk0p3: 00600000 00001000 "radiocab"
mmcblk0p14: 650000000 00001000 "internalsd"
mmcblk0p15: 89400000 00001000 "userdata"
mmcblk0p19: 01600000 00001000 "devlog"
mmcblk0p16: 00200000 00001000 "extra"
On TRWP/CWM/Philz I get (more or less the same) logs/messages:
Code:
E:Can’t open /dev/block/mmcblk0p17
(No such file or directory)
E: Can’t mount /cache/recovery/command
E: Can’t mount /cache/recovery/log
E: Can’t open /cache/recovery/log
[I](...) eg. Wipe Data/Factory Reset:[/I]
-- Wiping data…
Formating /data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formating /cache
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
Formating /sd-ext
Formating /sdcard/.android_secure…
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
5. Tried RUU that ought to be correct for my HOX & hboot version: (RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe) RUU software says it was flashed successfully, but when I restart the HOX it gets stucked on “HTC quitely brilliant” logo. Also, if I try to flash boot and system images manually (extracted from the ROM.zip from this RUU) the latter fails with “heap not enough” error (tried flashing on 32-bit Windows 7 and 64-bit OS X). This way or another, I don’t expect it to work, as there’s a problem with partition.
6. In the recovery I can’t wipe/erase a single thing (as in the example above)
7. As a result, no way to install a zip from recovery (due to missing partition layout) and no way to restore from backup (as it requires to mount /sdcard and it can't)...
8. ADB sideload doesn’t work (on TWRP: big red FAIL).
9. Some interesting lines from recovery.log:
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p5 (null) 0
2 /boot emmc /dev/block/mmcblk0p4 (null) 0
3 /cache ext4 /dev/block/mmcblk0p13 (null) 0
4 /data ext4 /dev/block/mmcblk0p15 (null) 0
5 /sdcard auto /dev/block/mmcblk0p14 (null) 0
6 /system ext4 /dev/block/mmcblk0p12 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /preload during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
(...)
W:failed to mount /dev/block/mmcblk0p13 /cache ext4 (No such file or directory)
stat /dev/block/mmcblk0p17 try 1: No such file or directory
(...)
failed to stat /dev/block/mmcblk0p17
E:Can't open /dev/block/mmcblk0p17
(...)
ro.build.display.id=cm_endeavoru-userdebug 4.2.2 JDQ39E eng.root.20130419.224121 test-keys
[I](...) - leftovers from cyanogenmod?[/I]
ro.build.description=4.18.401.2 CL231174 release-keys
[I](...) - is it the reason? Are these problems because I’m actually downgrading?[/I]
ro.aa.customizationid=559204
ro.aa.romver=4.18.401.2
ro.prot=true
ro.aa.maincid=HTC__001
ro.aa.rid=302
ro.aa.modelid=PJ4610000
ro.aa.report=com
ro.aa.project=ENDEAVOR_U_JB_50_S
ro.aa.skulist=401
ro.aa.taskid=330269
ro.aa.mainsku=401
So the most interesting part is the partition-layout: None is found with fastboot getvar all. I noticed that in almost all (all?) threads where people have problems with unsuccessful stock restore (RUU) or other "stuck on logo" and share their info from getvar there's a one common issue: partition-layout: None. Does anyone have idea what's the reason and how to get it back to partition-layout: Generic (this is the correct one as I assume looking at other threads)? I believe founding a fix for this one general problem would solve all of the mentioned not-booting/stuck-on-logo/soft-bricked issues.
I have no more ideas as I browsed through tons of posts and tried a lot of possible solutions with no effect. I believe there's a need to apply some low-level system "magic" I don't feel like being able to figure out myself. If you have any idea on how to proceed I’d be more than happy to try it out. My last try would be to flash a rom with more up-to-date android, but I'm afraid it would involve updating hboot and no chance to use RUU anymore.
Also, if you think it’s all useless given the state the HOX is in, please share, so I stop to waste my (and your) time - I already spent 2 weeks on it, learned a lot, read hundreds of threads on XDA - If I’d only knew that much before
On the other hand, if any member with magic skills would like to use my HOX to perform remote surgery to try to find a general solution for that problem, I'd be more than happy (well, just happy, I would be more if I could fix it ) to sacrifice my HOX even if there's a chance to kill it definitely.
Any clues guys? Maybe I should ask different question: do you know a method to check if the internal storage is faulty (chkdsk kind of thing)? Maybe my case is helpless (why I can read/write it from recovery, though).
Also, I was thinking about booting recovery (fastboot boot recovery - NOT fastboot flash recovery), hoping it won't read from storage but from memory, thus allowing me to unmount the storage and format (am I correct here? would it help anyway?). The thing is fastboot boot recovery won't work on HOX, but maybe there's a specific way that overrides kernel commandline (fastboot -c ... ) known already.
My HOX is stock, locked and working perfectly, and when I do a fastboot getvar all I also see partition-layout: none, so that cannot be the problem.
webpatrick said:
My HOX is stock, locked and working perfectly, and when I do a fastboot getvar all I also see partition-layout: none, so that cannot be the problem.
Click to expand...
Click to collapse
Thank you webpatrick, good to know that. So this one is not a problem.
I suspect bad sectors then (I wonder if that could be a reason for my HOX to restart on stock and gapps keep crashing on CWM back in the days it was alive). Any idea how to verify that and maybe fix?
Ok, so browsing (way) outside One X forum, I found GPT fdisk compiled for android. It is available in this thread: http://forum.xda-developers.com/showpost.php?p=24805392&postcount=74 or directly http://dl.dropbox.com/u/64885133/gptfdisk.zip. I could use it to load partition data from a backup file, but - obviously - I don't have one.
Could any of you guys run gdisk from the zip, back up GPT data to a file and post it?
Code:
./adb push gdisk /sbin
./adb shell
~ # gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Command (? for help): b
Enter backup filename to save: backup.gpt
The operation has completed successfully.
Command (? for help): q
Thanks in advance!
Couple points more:
1) To clarify, as I believe it matters, I have 32GB version, so I'd enjoy GPT back up for this one. Anyone, pleeeeease?
2) Also, one more question. Correct me if I'm wrong, but I believe that:
a) If I flash firmware manually, I don't have to change the name of the zip file
b) If I "flash" automatically, I need to change the name of the firmware zip to the specific one, PJ46IMG.zip in my case, before I put it on the sd card
Not that I could try b), but just wondering if I've been trying a) in the correct way
Long-time UNIX guy here, but relatively new to the world of Android.
I have recently purchased an Asus MemoPAD (ME103K) ; I then became root, and took a `dd` image of the read-only `system` partition to the external SD card:
Code:
$ su
# dd if=/dev/block/platform/msm_sdcc.1/by-name/system \
of=/storage/MicroSD/system.img bs=1M
# ls -l /storage/MicroSD/system.img
-rw-r--r-- 1 root root 2147483648 Sep 27 13:15 system.img
The size (exactly 2GiB) was a bit suspicious - could it be that this was because of the FAT32 partition on the SD card?
No, it was not - `tune2fs -l` revealed that this was indeed, a valid EXT4 image, exactly sized at 2GiB, which passed `fsck -f` with no errors at all.
And `fastboot` (from the linux machine attached to the tablet) concurred, after an `adb reboot bootloader`:
Code:
linuxbox# fastboot getvar all
(bootloader) version-bootloader: 3.03
(bootloader) version-hardware: rev_c
(bootloader) variant: LEOPARDCAT 16G
(bootloader) version-baseband: H00_0.16.F_0521
(bootloader) serialno: 0a3dXXXX
...
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000080000000
That size, is indeed 2GB:
Code:
linuxbox# python2 -c 'print 0x0000000080000000'
2147483648
So, all is good - I have a backup of the image. Now to test restoring it.
I try to flash the system.img back to the tablet - to make sure I can recover from anything, the sort of bullet-proof backup we do in the Unix world (*e.g. restore contents of a drive via `dd if=backup.image of=/dev/sdXXX`*).
Everything related to `adb` and `fastboot` work flawlessly - so I try...
Code:
linux_box# fastboot devices
0a3dXXXX fastboot
linux_box# mount /dev/sdcard /mnt/sdcard
linux_box# cp /mnt/sdcard/system.img .
linux_box# fastboot flash system system.img
error: cannot load 'system.img'
Hmm. I download and build the `android-tools-5.1.1` of my distribution from sources, adding debug information - and step in the debugger, to see this failure:
Code:
# gdb --args fastboot flash system system.img
...
(sorry, can't paste links yet - see this image: http i stack imgur com 9bIEM.png
Interesting - even though I am in a 64bit machine, apparently there are issues that turn the file size "negative" (in a 32bit world, the file size of my image, 2^31, is indeed considered negative - to be exact, `-2147483648`.
OK, fine - how do they flash large image files in Android?
Googling, searching - turns out they use this `make_ext4fs` tool, that creates flashable images. In fact it is part of what I just compiled, so I might as well use it:
Code:
# mkdir /system
# mount -o loop,ro system.img /system
# ls -l /system
total 208
drwxr-xr-x 106 root root 8192 Sep 17 22:24 app
drwxr-xr-x 3 root 2000 8192 Sep 26 21:08 bin
-rw-r--r-- 1 root root 6847 Sep 12 16:59 build.prop
drwxr-xr-x 19 root root 4096 Sep 26 21:08 etc
drwxr-xr-x 2 root root 4096 Aug 11 22:27 fonts
drwxr-xr-x 4 root root 4096 Sep 12 16:56 framework
drwxr-xr-x 10 root root 16384 Sep 12 16:59 lib
drwxr-xr-x 2 root root 4096 Jan 1 1970 lost+found
drwxr-xr-x 3 root root 4096 Aug 11 22:18 media
drwxr-xr-x 59 root root 4096 Aug 11 22:29 priv-app
-rw-r--r-- 1 root root 126951 Aug 1 2008 recovery-from-boot.p
drwxr-xr-x 3 root root 4096 Aug 11 21:02 scripts
drwxr-xr-x 3 root root 4096 Aug 11 21:02 tts
drwxr-xr-x 11 root root 4096 Sep 26 21:08 usr
drwxr-xr-x 8 root 2000 4096 Aug 11 22:29 vendor
drwxr-xr-x 2 root 2000 4096 Sep 26 21:09 xbin
# ../extras/source/extras/ext4_utils/make_ext4fs \
-l 2048M new_system.img /system
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 2666/131072 inodes and 375014/524288 blocks
Cool - so I can apparently build system images from plain old folders. The sky will be my limit - I'll be able to add anything I want to this image.
Let's burn it...
Code:
# fastboot flash system new_system.img
erasing 'system'...
OKAY [ 0.064s]
sending 'system' (2088960 KB)...
^C
I waited for 1h before hitting that Ctrl-C. And had to power-cycle the tablet, which booted back in fastboot mode.
This is not looking good.
What if I build a smaller image? Maybe the 2GB are somehow an issue, and this partition is not used to full capacity - it has free space:
Code:
# ../extras/source/extras/ext4_utils/make_ext4fs \
-l 1536M new_system.img /system
# ./fastboot flash system system.img
erasing 'system'...
OKAY [ 0.065s]
sending 'system' (1572864 KB)...
OKAY [ 51.039s]
writing 'system'...
OKAY [235.080s]
finished. total time: 286.183s
OK, this looks very promising (and only took 5 min). I guess I can now reboot back and everything should be normal, yes?
No
(sorry, can't paste links yet - see this image: http i stack imgur com U7wiX.png
I don't mind a temporarily bricked device, as long as I **do** get to control it in the end (machines that I am not a master of, are machines I don't care to operate
Any ideas on what I did wrong and what I can do to fix this?
Thanks in advance.
P.S. I checked the Asus support page for my tablet - they only provide the sources for the kernel, and the Over-the-air .zip file. That in turn contains a file-system level backup from the root - i.e. the `system` folder exists in there as just a folder, not an image, not a `system.img` that I can flash - so that doesn't really help me.
[SOLVED] Booted from external sd.
I documented how I solved it in android stack exchange, article 124344 (can't post links - the url is formed from .... http android.stackexchange.com questions 124344 trying-to-flash-a-system-img-i-took-with-dd-failing )
Executive summary - I edited my custom boot image /fstab.qcom to point /system to the external SD card, and dd-ed my image there.