Develop Bugs

[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD

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.

[Q] how to install a boot.img file

Hi guys,
I have a Linux partition on my sdcard and I want to have it mount at boot. I checked out this page( a page that I am not permitted to link to that might or might not contain this text "wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images") on how to do it and I have put together a boot.img file I want to flash. The instructions call for this maneuver:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
but the Note 8 doesn't have a MTD device:
[email protected]:/storage/sdcard0 # ls -l /dev/mtd*
/dev/mtd*: No such file or directory
what do I do?

mounting at boot time
Hi guys,
It has been about a week since I posted this question here. The reason I am trying to edit the boot.img file is to add a persistent mount point to a Linux partition on my sdcard. After fussing with several third party kernels and not succeeding in creating my own working ramdisk, I tried adding init.d support and putting the mount command in a startup script. It looks like the sdcard is not mounted by the time the init process is finished. I tried editing the vold.fstab file. I tried adding this line to the end:
dev_mount debian /storage/extSdCard/debian 50 /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
No dice.
what is the format of this file? Where can I find a man page or a doc?
These are my partitions:
1|[email protected]:/sdcard # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 2621440 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10518528 mmcblk0p12
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 27343750 mmcblk1p1
179 50 2929687 mmcblk1p2
[email protected]:/sdcard #
these have changed since I updated to 4.2.2 about a week ago. Is there some way to have the config persist through device upgrades?

[Q] Optus HTC One X on HBoot 1.36 - Restoring to Stock - RUU not available

Hi,
I have a HTC One X that I'm trying to restore to stock - it seems pretty borked at the moment, /sdcard won't mount in recovery (CWM), wifi/mobile aren't working etc.
I've also tried partitioning the SDCard through CWM, and I think I may have used the wrong options (1024 Mb, and 128Mb swap?). I have no idea how to restore partition layouts on HTC phones? (Do they use a .PIT file?).
Anyhow, on bootup, it shows the following:
Code:
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW SEcure boot: enabled
MODEM PATH : OFF
Nov 16 2012,18:32:39
FASTBOOT USB
...
My fastboot variables:
Code:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.36.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.980.27
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4008mV
(bootloader) devpower: 92
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
If I'm reading the above correctly, it's on HBoot 1.36, with a Optus CID, so I tried looking for a RUU here
http://www.androidruu.com/index.php?developer=Endeavor
and unfortunately couldn't find anything matching it - the newest is 1.29 for Optus.
I'm then thought I'd try following the instructions here for restoring from Nandroid:
http://forum.xda-developers.com/showthread.php?t=1975140
I downloaded the Nandroid backup from here:
Nandroid Backup / Mirror 3.14.980.27 CID OPTUS001 thanks to mafia187
http://uploaded.net/file/bvcpzcgl
The RAR file from this download doesn't contain a zipfile, however, it does contain a folder with the following:
nandroid.md5
cache.ext4.tar
data.ext4.tar
system.ext4.tar
boot.img
recovery.img
I tried flashing this with adb restore as a folder, and also compressing it to a zipfile, and flashing it, and it didn't seem to do anything, but simply returned right away both times with:
Code:
192-168-1-102:platform-tools victorhooi$ ./adb restore ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47
2012-12-19.21.27.47/ 2012-12-19.21.27.47.zip
192-168-1-102:platform-tools victorhooi$ ./adb restore ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47.zip
Now unlock your device and confirm the restore operation.
I then thought I'd try to erase/flash the partitions manually.
When I try to erase them I get a "remote: not allowed" error:
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.136s
When I try to flash, I get a "heap not enough" error:
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot flash system ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47/system.ext4.tar
sending 'system' (1100991 KB)...
FAILED (remote: Heap not enough)
finished. total time: 0.098s
I thought maybe the bootloader was still locked (I was actually a bit confused, as it says UNLOCKED at the top, but it says S-ON for getvar?).
I tried to following the official unlock procedure on the HTCDev site.
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot flash unlocktoken ~/Downloads/Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.222s]
finished. total time: 0.364s
and I don't get the unlock screen, as they mention in the HTC instructions?
What are your thoughts on what to try next? Any help at all greatly appreciated.
Cheers,
Victor

You're in the wrong forum, this is the HTC One XL / AT&T One X forum. You need to ask in the HTC One X forum.
Sent from my Evita

Cheers on the size of your post though
Sent from my HTC One XL

Oh by the way, you really should edit out your IMEI above. Never post your IMEI publicly. Also I've reported this thread to be moved to the correct device forum.
Sent from my Evita

Hi,
@timmaaa - Aha, thanks for moving the post and sanitising the IMEI number =). Appreciate that.
Let me know if there's any other details you need me to provide.
Cheers,
Victor

Unfortunately nobody here can help you because we're not familiar with your device. Once your thread is moved to the right forum the folks there should be able to assist though. Good luck.
Sent from my Evita

1. Unlock bootloader using normal method (if not already unlocked)
2. Flash latest clockworkmod recovery
3. go to recovery -> mount usb storage
4.Place contents of RAR file inside sdcard/clockworkmod/backup folder,
5. go to recovery and restore from that folder you created.
btw, there ARE instructions on the nanodroid backup page, follow those and you'll be all good.

Hi,
@tomascus - When I try to mount USB storage, it doesn't seem to work - it can't seem to access /sdcard (see first post). When I get home, I can paste the exact error message.
Cheers,
Victor

victorhooi said:
Hi,
@tomascus - When I try to mount USB storage, it doesn't seem to work - it can't seem to access /sdcard (see first post). When I get home, I can paste the exact error message.
Cheers,
Victor
Click to expand...
Click to collapse
What is your recovery ????

Hi,
@virgolib: My recovery is ClockworkMod Recovery v5.8.4.0.
@tomascus: If I go into Mounts and Storage, then "mount USB storage", then on my OSX, I get:
Code:
The disk you inserted was not readable by this computer.
Initialize... / Ignore / Eject
If I go into Mounts and Storage, then "mount /sdcard", on the phone I get:
Code:
Error mounting /sdcard!
If I try to use "Mounts and Storage menu", then "format /sdcard", I get:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
My output from cat /proc/partitions:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
And from mount:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
Does the above look right?
And is the bootloader actually unlocked correctly?
Cheers,
Victor

victorhooi said:
Hi,
@virgolib: My recovery is ClockworkMod Recovery v5.8.4.0.
@tomascus: If I go into Mounts and Storage, then "mount USB storage", then on my OSX, I get:
Code:
The disk you inserted was not readable by this computer.
Initialize... / Ignore / Eject
If I go into Mounts and Storage, then "mount /sdcard", on the phone I get:
Code:
Error mounting /sdcard!
If I try to use "Mounts and Storage menu", then "format /sdcard", I get:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
My output from cat /proc/partitions:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
And from mount:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
Does the above look right?
And is the bootloader actually unlocked correctly?
Cheers,
Victor
Click to expand...
Click to collapse
Just try with Philz_Touch recovery ... http://d-h.st/users/philz_touch/?fld_id=16046#files
You have to wait about 3minutes for mounting USB storage.

Hi,
@virgolib - I was able to flash with PhilZ Touch Recovery 5.15.9-endeavoru, as suggested
I started it up in recovery mode, and selected "format /sdcard"
It then gave me a prompt asking to select the filesystem type (the or) - I chose vfat.
After this, I was able to ./adb push files onto /sdcard/clockworkmod/restore, and then do a Nandroid restore via PhilZ Touch recovery.
At this point I was returned to stock - I booted it up, and checked that it could boot, and wifi was working.
I then flashed a CM10.2 nightly based on the instructions here - http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru
Basically - flash the image and Gapps via PhilZ touch recovery, then use flashboot to flash the boot.img (kernel) - I'm assuming that step is still needed these days?
Also - I'm curious though - what's the difference between ClockworkMod and PhilZ Touch recovery? As in, why was PhilZ Touch recovery able to format the /sdcard successfully? Should I flash back ClockworkMod or leave Philz Touch recovery? And why is PhilZ touch recovery not more commonly known about? (To be honest, this was the first I'd even heard of it, I only knew CWM and TWRP).
Also, I checked my partitions just now:
Code:
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 485.9M 64.0K 485.9M 4096
/mnt/secure 485.9M 0.0K 485.9M 4096
/mnt/asec 485.9M 0.0K 485.9M 4096
/mnt/obb 485.9M 0.0K 485.9M 4096
/mnt/fuse 485.9M 0.0K 485.9M 4096
/system 1.2G 473.6M 786.3M 4096
/cache 315.0M 5.2M 309.7M 4096
/rca 5.9M 4.2M 1.7M 4096
/rfs 5.9M 4.0M 1.9M 4096
/devlog 21.6M 10.9M 10.7M 4096
/data 2.1G 307.2M 1.8G 4096
/storage/sdcard0 25.2G 1.6G 23.7G 16384
/mnt/secure/asec: Permission denied
/mnt/asec/com.grofsoft.tripview-1 5.0M 4.0M 1.0M 4096
The /sdcard one seems to be 25.2 Gb - which I assume is the correct size. When I went in before via ClockworkMod, and chose to partition it as 1024 Mb - did that simply not take? Or did the subsequent Nandroid restore, or flashing CM10.2 change it?
Cheers,
Victor

You have to install cm10.2 & gapps via recovery then flash boot.img of cm10.2. I'm just a user only not expertise so cannot answers by specify, Philz recovery is the most compatible at the moment. You seemed to be OK now and do as you wish restore or install cm rom.

Need assistance....I did a bad, bad thing....

I have two Verizon HTC Ones (silver and blue) I recently was looking around and saw all the "convert your HTC one to developer/gpe edition" talk and thought, "why not." I figured everything was okay and didn't do as much reading as I normally do. I changed the MID (had SuperMID from java card s-off) to developer edition and, flashed GPE firmware then tried flashing RUUs and when that wouldn't work tried a ROM (Android Revolution HD 5.1). Well, obviously none of this is compatible with a Verizon HTC One and there are now.......issues. As, i said, both of the phones were s-off via java card. Now the silver is S-on, there is no hboot. I can flash recovery, flash roms, etc (they won't boot). But cant figure out how to flash firmware/hboot with s-on. I am using the Blue variant now with Insertcoin ROM and it is great. but the Blue suffers from a severe case of the "pink camera." whereas the silver does not. Is there anyway to fix this or is it bricked. Attached a few pics of the devastation.

RUU should fix it as long as you can get to bootloader.

RUU
yourunlikegus said:
I have two Verizon HTC Ones (silver and blue) I recently was looking around and saw all the "convert your HTC one to developer/gpe edition" talk and thought, "why not." I figured everything was okay and didn't do as much reading as I normally do. I changed the MID (had SuperMID from java card s-off) to developer edition and, flashed GPE firmware then tried flashing RUUs and when that wouldn't work tried a ROM (Android Revolution HD 5.1). Well, obviously none of this is compatible with a Verizon HTC One and there are now.......issues. As, i said, both of the phones were s-off via java card. Now the silver is S-on, there is no hboot. I can flash recovery, flash roms, etc (they won't boot). But cant figure out how to flash firmware/hboot with s-on. I am using the Blue variant now with Insertcoin ROM and it is great. but the Blue suffers from a severe case of the "pink camera." whereas the silver does not. Is there anyway to fix this or is it bricked. Attached a few pics of the devastation.
Click to expand...
Click to collapse
Have you tried to boot into RUU just to see what happens??

lj50036 said:
Have you tried to boot into RUU just to see what happens??
Click to expand...
Click to collapse
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic

Feedback
yourunlikegus said:
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Click to expand...
Click to collapse
Have you tried flashing the firmware in post 2 ??

yourunlikegus said:
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Click to expand...
Click to collapse
Are you unzipping the signed zips? There may be a .exe inside
If you are using the cmd window to flash you should be able to flash the decrypted RUU
Edit check the Sprint RUU thread see if your RUU is setup like ours

lj50036 said:
Have you tried flashing the firmware in post 2 ??
Click to expand...
Click to collapse
From the thread I posted? yes...hangs at parsing index. The .zip i can open is a bunch of .img files. the rest i cant open, says they are invalid

Hang Tight
yourunlikegus said:
From the thread I posted? yes...hangs at parsing index. The .zip i can open is a bunch of .img files. the rest i cant open, says they are invalid
Click to expand...
Click to collapse
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------
List all the .img files here so I can see what is there.....

lj50036 said:
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
Click to expand...
Click to collapse
Yeah, I've tried both and it either hangs or errors out. Attached is shot of flashing firmware...just sits there at that point.

BD619 said:
Are you unzipping the signed zips? There may be a .exe inside
If you are using the cmd window to flash you should be able to flash the decrypted RUU
Edit check the Sprint RUU thread see if your RUU is setup like ours
Click to expand...
Click to collapse
Will download and attempt it but I'm pretty sure the sprint stuff will be incompatible too. When I tried to run the developer edition ruu.exe it said connection error, plug usb cable in, etc. (not sure of exact error code)
And after succesfully botting into RUU, after the failed attempts and hangs, I cannot fastboot reboot-bootloader, that just hangs too. I have to hold the power button down.

yourunlikegus said:
Yeah, I've tried both and it either hangs or errors out. Attached is shot of flashing firmware...just sits there at that point.
Click to expand...
Click to collapse
Give me a list of all the .img files that you see from the firmware zip
I think I have a solution maybe.. With the bootloader unlocked we can still us fastboot not RUU... We will just have to flash them from fastboot one at a time... give me a list I will work on it....

lj50036 said:
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------
List all the .img files here so I can see what is there.....
Click to expand...
Click to collapse
Well, I can't open the signed zips that are for the vzw (says windows cant, invalid) but I can open 1 of the developer edition ruus that i have...not sure if that really helps

yourunlikegus said:
Well, I can't open the signed zips that are for the vzw (says windows cant, invalid) but I can open 1 of the developer edition ruus that i have...not sure if that really helps
Click to expand...
Click to collapse
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues

yourunlikegus said:
Will download and attempt it but I'm pretty sure the sprint stuff will be incompatible too. When I tried to run the developer edition ruu.exe it said connection error, plug usb cable in, etc. (not sure of exact error code)
And after succesfully botting into RUU, after the failed attempts and hangs, I cannot fastboot reboot-bootloader, that just hangs too. I have to hold the power button down.
Click to expand...
Click to collapse
What I mean is check your RUU and see if it's setup the same as Sprint not flash it
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
yourunlikegus said:
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
Click to expand...
Click to collapse
You can't flash older firmware or RUUs if you are s-on

BD619 said:
What I mean is check your RUU and see if it's setup the same as Sprint not flash it
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
You can't flash older firmware or RUUs if you are s-on
Click to expand...
Click to collapse
ok. I'll have to figure out which one is hboot 1.54

yourunlikegus said:
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
Click to expand...
Click to collapse
On that forum did you try to get one of those RUU and upack it?? A newer one like 2.10.605.1 decypted???
2.10.605.1 is hboot 1.54 for sure try to flash that one from RUU just so we know

lj50036 said:
On that forum did you try to get one of those RUU and upack it?? A newer one like 2.10.605.1 decypted???
2.10.605.1 is hboot 1.54 for sure try to flash that one from RUU just so we know
Click to expand...
Click to collapse
Downloading both ruu and firmware for 2.10.605.1. Will flash soon and see what happens. i think i have tried this one already but i can't remember lol

Pic of files in 2.10.605.1 firmware.zip

Partition Table
yourunlikegus said:
Downloading both ruu and firmware for 2.10.605.1. Will flash soon and see what happens. i think i have tried this one already but i can't remember lol
Click to expand...
Click to collapse
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Here is a list of the partitions... If you were to match up the img with the partition, Im sure you would be able to flash from fastboot
An example of a command work be like this
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
This is just an example.... I would have no idea in which order you would want to flash them...

lj50036 said:
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Here is a list of the partitions... If you were to match up the img with the partition, Im sure you would be able to flash from fastboot
An example of a command work be like this
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
This is just an example.... I would have no idea in which order you would want to flash them...
Click to expand...
Click to collapse
wont let me erase...remote not allowed. I was able to flash boot, but so far everything else i try is failed remote not allowed also for rcdata and adsp get signature verify fail

How extract the Pit file ?

Can anybody confirm that the follow strings working on the T805?
Use Terminal Emulator and enter follow:
su (Enter)
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176 (Enter)
Click to expand...
Click to collapse
This Code is from the Galaxy S5 but i think that the mmcblk0 is the same or i wrong?
Here are the partition from the S10.5 and S8.4 Tab
Code:
Größe Device Name Kommentar Mountpoint
15388672 mmcblk0
4096 mmcblk0p1 BOTA0
4096 mmcblk0p2 BOTA1
20480 mmcblk0p3 EFS EFS Filesystem /efs
4096 mmcblk0p4 m9kefs1 EFS Filesystem
4096 mmcblk0p5 m9kefs2 EFS Filesystem
4096 mmcblk0p6 m9kefs3 EFS Filesystem
4096 mmcblk0p7 CARRIER Modemfirmware
8192 mmcblk0p8 PARAM Param
8192 mmcblk0p9 BOOT Kernel
10240 mmcblk0p10 RECOVERY Recovery
10240 mmcblk0p11 OTA FOTA Partition
4096 mmcblk0p12 CDMA-RADIO Modemfirmware
49152 mmcblk0p13 RADIO Modemfirmware
4096 mmcblk0p14 TOMBSTONES
4096 mmcblk0p15 TDATA
12288 mmcblk0p16 PERSDATA /persdata/absolute
4096 mmcblk0p17 RESERVED2
2447360 mmcblk0p18 SYSTEM System Partition /system
204800 mmcblk0p19 CACHE Cache /cache
235520 mmcblk0p20 HIDDEN Hidden Partition
12333056 mmcblk0p21 USERDATA Userdaten /data
4096 mmcblk0rpmb
4096 mmcblk0boot1
4096 mmcblk0boot0

Chrack said:
Can anybody confirm that the follow strings working on the T805?
Click to expand...
Click to collapse
Did you find out which dd values would do the trick ?
I want to save PIT from my Tab S and A5.... http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668

gggg said:
Did you find out which dd values would do the trick ?
I want to save PIT from my Tab S and A5.... http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668
Click to expand...
Click to collapse
Efs professional

ashyx said:
Efs professional
Click to expand...
Click to collapse
It cannot read PIT on A5 this is why I want to dd, but I need the right params ... please reply here:
http://forum.xda-developers.com/gal...t-efs-rest-t3169643/post62128668#post62128668