Hi, i tried to backup my current rom image and installed TWRP from this webpage.
But after installing TWRP the software application continuously looping to its homescreen menu when i reboot every time.
I Tried fastboot but i dint turned on usb debug option in development settings before i install TWRP. my device is offline in adb devices from command prompt window. I cant turn on usb debug option until i boot into my device OS homescreen menu.
The terminal command is available from TWRP menu screen.
help me if i can turn on usb debug option through terminal command.
help me if i can recover my device from TWRP boot loop through the terminal commands.
Hope someone will fix my problem
st10user said:
Hi, i tried to backup my current rom image and installed TWRP from this webpage.
But after installing TWRP the software application continuously looping to its homescreen menu when i reboot every time.
I Tried fastboot but i dint turned on usb debug option in development settings before i install TWRP. my device is offline in adb devices from command prompt window. I cant turn on usb debug option until i boot into my device OS homescreen menu.
The terminal command is available from TWRP menu screen.
help me if i can turn on usb debug option through terminal command.
help me if i can recover my device from TWRP boot loop through the terminal commands.
Hope someone will fix my problem
Click to expand...
Click to collapse
Try:
Code:
adb kill-server
adb start-server
adb devices
fuser-invent said:
Try:
Code:
adb kill-server
adb start-server
adb devices
Click to expand...
Click to collapse
Thanks for your reply.
Tried these commands. device is offline in command prompt window.
st10user said:
Thanks for your reply.
Tried these commands. device is offline in command prompt window.
Click to expand...
Click to collapse
Have you tried flashing either of my ROM's from TWRP? I read in the other thread that you wiped /system so you probably don't have an operating system to boot into, that's why it keeps booting back into TWRP.
Yes bro, I tried flashing your roms through "apply update from EXT" but not worked for me.
I dont know how to flash through twrp terminal commands.
Plz help me.
which commands i need to flash through twrp?
Maybe you should try ADT android download tool
PM me if u need help
Sent from MOON......
You can't flash my ROM's through "apply update from EXT" because that is the stock recovery and they are built to be flashed in TWRP. You don't need to use terminal commands to flash anything in TWRP.
All you do is press the "Install" button, choose the zip files you want to flash and then swipe the button that shows up on the screen to the right to start the flashing process. When it's done, hit the "wipe dalvik and cache" button, flash it the ROM again, hit "wipe dalvik and cache" again and then reboot. For some reason on a lot of these tablets you need to double flash the firmware.
When i installing karbonn_custom_st10_v1.3.zip or karbonn_st10_stock_plus_v1.2.zip I receiving message like "skipping md5 check: no md5 file found."
After that everything installing successfully. But after reboot to system still my tablet stuck on twrp.
Help me.
st10user said:
When i installing karbonn_custom_st10_v1.3.zip or karbonn_st10_stock_plus_v1.2.zip I receiving message like "skipping md5 check: no md5 file found."
After that everything installing successfully. But after reboot to system still my tablet stuck on twrp.
Help me.
Click to expand...
Click to collapse
"skipping md5 check: no md5 file found." doesn't matter, you can ignore that.
Are you using the correct TWRP? There are two, one is for the ST8 and one is for the ST10.
Did you use the double flash method I suggested with the wipes? Have you tried flashing anything else before this? I'm hoping that you followed the instructions and didn't try to flash the stock+ ROM in TWRP, right?
The Stock+ ROM is for the stock recovery and the Custom ROM is for TWRP.
If there are more details, please write them. From what I understand this is where you are at so far and nothing more.
1. You downloaded TWRP
2. You flashed TWRP using ozadroid's instructions
3. You booted into TWRP and wiped /system
4. Your tablet reboots and is stuck in a boot loop.
fuser-invent said:
"skipping md5 check: no md5 file found." doesn't matter, you can ignore that.
Are you using the correct TWRP? There are two, one is for the ST8 and one is for the ST10.
Did you use the double flash method I suggested with the wipes? Have you tried flashing anything else before this? I'm hoping that you followed the instructions and didn't try to flash the stock+ ROM in TWRP, right?
The Stock+ ROM is for the stock recovery and the Custom ROM is for TWRP.
If there are more details, please write them. From what I understand this is where you are at so far and nothing more.
1. You downloaded TWRP
2. You flashed TWRP using ozadroid's instructions
3. You booted into TWRP and wiped /system
4. Your tablet reboots and is stuck in a boot loop.
Click to expand...
Click to collapse
I installed correct twrp for st10. I followed your guidance but still stuck with twrp loop. I uploaded a video of my st10 installing log here
Plz help me.
Same thing happend to me also.when I flashed twrmp .it doesn't boot to system or stock recovery. I gave it and serviced by service centre.
Sent from my Micromax A110 using xda premium
In the video you are flashing the Stock+ ROM. Flash the Karbonn Custom ROM in the same way instead. When it gets to the last step right before you hit the reboot button, remove your external SD card and then hit the reboot button with the SD card out. Let me know what happens, there could be something on your SD card forcing you to reboot into recovery instead of the ROM.
Also, it looks like ozadroid has released a newer version of TWRP than the one you are running, I would suggest downloading that and using it instead.
I flashed newer version of trmp but no change .my tab stuck again.it doesn't reboot to system.but stock recovery is available,I flashed stock rom.but no change it reboot again to trmp.now what should I do .my service center will not accept my tab again.
Sent from my Micromax A110 using xda premium
Okay, so it doesn't appear from the TWRP install video that the partitions are damaged but we should check that out, fun the following in adb from TWRP:
Code:
adb kill-server
adb start-server
adb devices
adb shell cat /proc/partitions
adb shell parted /dev/block/mtdblock0 print
adb shell parted /dev/block/mtdblock8 print
adb shell parted /dev/block/avnftli print
adb shell fdisk -l /dev/block/mtdblock0
adb shell fdisk -l /dev/block/mtdblock8
adb shell fdisk -l /dev/block/avnftli
If when you run "adb shell cat /proc/partitions" the partitions are labeled differently, then change the block name in the next section of commands. You should get something like this:
Code:
C:\adb>adb shell cat /proc/partitions
major minor #blocks name
31 0 8192 mtdblock0
31 1 8192 mtdblock1
31 2 8192 mtdblock2
31 3 8192 mtdblock3
31 4 8192 mtdblock4
31 5 524288 mtdblock5
31 6 262144 mtdblock6
31 7 1048576 mtdblock7
31 8 6504448 mtdblock8
250 32 6041600 avnftli
250 33 6024375 avnftli1
253 0 1906688 cardblksd
253 1 1905049 cardblksd1
Then this with "print" in "parted":
Code:
C:\adb>adb shell parted /dev/block/mtdblock0 print
Error: Can't have a partition outside the disk!
C:\adb>adb shell parted /dev/block/mtdblock8 print
Model: Unknown (unknown)
Disk /dev/block/mtdblock8: 6661MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 16.5MB 6185MB 6169MB primary
C:\adb>adb shell parted /dev/block/avnftli print
Model: Unknown (unknown)
Disk /dev/block/avnftli: 6187MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 16.5MB 6185MB 6169MB primary fat32
Then this with" fdisk":
Code:
C:\adb>adb shell fdisk -l /dev/block/mtdblock0
Disk /dev/block/mtdblock0: 8 MB, 8388608 bytes
255 heads, 63 sectors/track, 1 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mtdblock0p1 2 481 3855600 b Win95 FAT32
C:\adb>adb shell fdisk -l /dev/block/mtdblock8
Disk /dev/block/mtdblock8: 6660 MB, 6660554752 bytes
255 heads, 63 sectors/track, 809 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mtdblock8p1 3 752 6024375 b Win95 FAT32
C:\adb>adb shell fdisk -l /dev/block/avnftli
Disk /dev/block/avnftli: 6186 MB, 6186598400 bytes
255 heads, 63 sectors/track, 752 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/avnftli1 3 752 6024375 b Win95 FAT32
The main thing you want to be looking for is that they actually show up and don't read:
Code:
Error: /dev/block/mtdblock8: unrecognised disk label
or
Code:
Error: Partition doesn't exist.
or
Code:
Disk /dev/block/mtdblock8 doesn't contain a valid partition table
You also want to make sure that it says your partition tablet is "msdos" and the format is "FAT32"
Lastly, I wanted to ask you both which method you used to install TWRP, did you flash the zip in the stock recovery, did you place the TWRP "recovery.img" on your external SD card or did you use the "Android Partition Manager" app to flash it?
I used android partation manager.I will check wid adb
Sent from my Micromax A110 using xda premium
---------- Post added at 12:31 AM ---------- Previous post was at 12:18 AM ----------
Adb method not working
Sent from my Micromax A110 using xda premium
@ st10user
I think you have done something in the booting system. I have seen your video and saw that without pressing any keys combination your tab is just booting in TWRP.
I believe you have done the same mistake the other user done..You have flashed recovery.img in boot partition...
Solution should be now, to flash boot.img to boot partition and recovery.img to recovery partition...But not sure how to help you..
There should be some flashable file which you can use and flash thru TWRP..
--------------------------------------------------------------------------------------------
Edit: Here is your solution provided by great Fuser...
http://forum.xda-developers.com/showthread.php?t=2105692&page=65
Moonguy75 said:
Maybe you should try ADT android download tool
PM me if u need help
Sent from MOON......
Click to expand...
Click to collapse
Now my problem is solved. Thanks for your help.
KSKHH said:
@ st10user
.
I think you have done something in the booting system. I have seen your video and saw that without pressing any keys combination your tab is just booting in TWRP.
I believe you have done the same mistake the other user done..You have flashed recovery.img in boot partition...
Solution should be now, to flash boot.img to boot partition and recovery.img to recovery partition...But not sure how to help you..
There should be some flashable file which you can use and flash thru TWRP..
--------------------------------------------------------------------------------------------
Edit: Here is your solution provided by great Fuser...
http://forum.xda-developers.com/showthread.php?t=2105692&page=65
Click to expand...
Click to collapse
Now everything fine. Thanks for your help.
Thank you very much fuser-invent. You saved my tab.
Wish you all the best.
st10user said:
Thank you very much fuser-invent. You saved my tab.
Wish you all the best.
Click to expand...
Click to collapse
So please google and get some basic knowledge..that will help you in future..
Even I do not have much knowledge, however just playing with the things with common sense...:laugh:
after install the twrp my tab is dead
after install twrp in my smart tab 10 after one minute it is swzoff but still it not start then what i ll do please help me m hope less ....i charged it 1 day thare after also it not start ....plz help me......my email.id - [email protected]...
Related
EDIT: March 18th, 2012: See note at bottom regarding upgrade to Honeycomb with CWM installed.
Clockworkmod recovery for the Vizio VTAB1008
As promised here it is.
Use this carefully. Any wrong commands can potentially brick your system
I was able to port Clockwork Mod Recovery to the Vizio and boot into it.
Many thanks to fadefx for testing it.
The zip file is attached to this post. Please unzip and read the instructions in README.txt. It is also given below. Please also read the Caveats below.
### Here is Clockworkmod Recovery for the Vizio VTAB1008 ###
### Released on Dec 11th, 2011 -- rprr ###
### Based on cyanogenmod sources and with some ###
### Vizio VTAB1008 specific mods ###
### Requirements ###
### You need 'adb' access on a rooted device Vizio tablet ###
### AN EXTERNAL MICRO SDCARD MUST BE PRESENT IN ORDER TO ###
### MAKE AND RESTORE BACKUPS. ###
### Installation ###
### The following copies the file to the root of your sdcard ###
adb push recovery-cwm-vtab1008.img /sdcard/recovery-cwm-vtab1008.img
### Login to adb shell ###
adb shell
### Become root ###
su
### The following installs CWM to the recovery partition ###
### Make sure to not make any mistakes here ###
dd if=/sdcard/recovery-cwm-vtab1008.img of=/dev/block/mmcblk0p5 bs=512
### Logout as root ###
exit
### Exit adb ###
exit
### Reboot into recovery ###
### ENJOY !!!! Be careful. ###
### Exercise caution when using this. ###
Click to expand...
Click to collapse
CAVEATS:
Display is in landscape mode only
Cannot restore the kernel and ramdisk backups yet
No ROM manager support yet
Also the edifying scripting has some issues with the mount command. Any commands that begin with
mount(.........)
Click to expand...
Click to collapse
should be replaced as in the following example
run_program("/sbin/busybox", "mount", "/system");
Click to expand...
Click to collapse
Original Recovery
WARNING IF YOU WANT TO UPGRADE to Honeycomb:
Some of us including me have had problems when we attempted to upgrade to Honeycomb with CWM installed. This has resulted in non working devices. It maybe due to CWM. If so, it is possible that you may have to revert back to the stock recovery. I am attaching it to this post. You have to unzip it, move it to the sdcard and then install it. Remember that root will be lost if you follow this.
Code:
dd if=/sdcard/recovery-orig.img of=/dev/block/mmcblk0p5 bs=512
I don't think the bootloader is located on /sdcard/ this partition is fat formatted and the bootloader would be visible to the user in some way either through a filenrowser or when mounted to a windows machine.
FadeFx said:
I don't think the bootloader is located on /sdcard/ this partition is fat formatted and the bootloader would be visible to the user in some way either through a filenrowser or when mounted to a windows machine.
Click to expand...
Click to collapse
Thanks. Using the mmls tool from Ubuntu, I was able to dig up a little further to find unallocated partitions etc. Here is the list.
$ mmls -t gpt mmcblk0.img
GUID Partition Table (EFI)
Offset Sector: 0
Units are in 512-byte sectors
Slot Start End Length Description
00: Meta 0000000000 0000000000 0000000001 Safety Table
01: ----- 0000000000 0000015359 0000015360 Unallocated
02: Meta 0000000001 0000000001 0000000001 GPT Header
03: Meta 0000000002 0000000033 0000000032 Partition Table
04: 11 0000015360 0000017407 0000002048 sm0
05: ----- 0000017408 0000019455 0000002048 Unallocated
06: 07 0000019456 0000035839 0000016384 kernel
07: 00 0000035840 0000052223 0000016384 ramdisk
08: 01 0000052224 0000502783 0000450560 android_system
09: ----- 0000502784 0000666623 0000163840 Unallocated
10: 02 0000666624 0002239487 0001572864 android_data
11: 08 0002239488 0002255871 0000016384 reckernel
12: 04 0002255872 0002272255 0000016384 recovery
13: 05 0002272256 0002273279 0000001024 misc
14: 09 0002273280 0002277375 0000004096 uli_r
15: 10 0002277376 0002281471 0000004096 uli_w
16: 12 0002281472 0002285567 0000004096 HDCP
17: 06 0002285568 0002695167 0000409600 cache
18: 03 0002695168 0007729083 0005033916 mass_storage
19: ----- 0007729084 0007729151 0000000068 Unallocated
Click to expand...
Click to collapse
So far, I have tried various hacks but just cannot get CWM to run on this However, if you are good with Linux/Unix command line stuff and with adb it is possible to make backups of the various partitions. Thus far, I have backed up and restored the recovery partition successfully. This is obviously a very dicey thing to do as it is possible to brick this device.
rprr said:
So far, I have tried various hacks but just cannot get CWM to run on this However, if you are good with Linux/Unix command line stuff and with adb it is possible to make backups of the various partitions. Thus far, I have backed up and restored the recovery partition successfully. This is obviously a very dicey thing to do as it is possible to brick this device.
Click to expand...
Click to collapse
well is there any way we can just modify the existing recovery menu?
plus you did get adb to work with it but that was a simple fix
In order to change the options you have to build the recovery program from the Android source code.
Good Morning! Just a quick note to say thanks for working on this! Keep going...I think you can, I think you can, I can think you can etc etc etc. hahaha
Rprr, i think you have to specify the partition reckernel somewhere in board config as it seams the recovery has its own kernel there and it needs to know where it is located.
Edit: finally obtained root using a win7 64bit machine, pdanet drivers and d00ml0rd v3 and adb files from sdk.
----------------------------------------
tapatalked
Obsolete: Please see OP.
Still no luck with CWM port. Anyway, here is my method for enabling adb when in recovery. This requires linux/unix terminal line usage. On my VTAB the recovery partition is at /dev/block/mmcblk0p5. I assume that this is the case with all Vizio vtab1008 tablets.
Proceed carefully. You can potentially damage your device.
1. Quick Way
Download my recovery-new.img.zip file which is attached to this post and unzip it. You will have a file called "recovery-new.img". Copy this to your sdcard. Then open an adb shell and become root. Run the following command.
Code:
dd if=/sdcard/recovery-new.img of=/dev/block/mmcblk0p5 bs=512
Now reboot into recovery. You will have adb access.
2. Long Way for DIYers
On VTAB using adb as root:
Code:
dd if=/dev/block/mmcblk0p5 of=/sdcard/recovery.img bs=512
On my Mac (in terminal), Should work on linux as well:
Code:
adb pull /sdcard/recovery.img
cp recovery.img recovery.cpio.gz
gunzip -f recovery.cpio.gz
mkdir recovery
cd recovery
cpio -i -F ../recovery.cpio
Edit the 'default.prop' to make the needed changes. It should look like.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
On my Mac again:
Code:
cpio -i -t -F ../recovery.cpio | cpio -o -H newc -O ../recovery-new.cpio
cd ..
gzip recovery-new.cpio
dd if=/dev/zero of=recovery-new.img count=16384 bs=512
dd if=recovery-new.cpio.gz of=recovery-new.img conv=notrunc
adb push recovery-new.img /sdcard/recovery-new.img
On Vizio using adb as root:
Code:
dd if=/sdcard/recovery-new.img of=/dev/block/mmcblk0p5 bs=512
Now reboot VTAB into Recovery mode. You should have adb access.
PS: If you have made any mistakes, you can reflash the original recovery.
Code:
dd if=/sdcard/recovery-orig.img of=/dev/block/mmcblk0p5 bs=512
PPS: Once you have adb root shell access in recovery, you can backup and potentially restore the /system partition.
PPPS: I am also attaching the original recovery if you would like to flash it back using dd. It is called recovery-orig.img.zip. Please unzip it.
rprr said:
Still no luck with CWM port. Anyway, here is my method for enabling adb when in recovery. This requires linux/unix terminal line usage.
Proceed carefully. You can potentially damage your device.
On VTAB using adb as root:
Code:
dd if=/dev/block/mmcblk0p5 of=/sdcard/recovery.img bs=512
On my Mac (in terminal), Should work on linux as well:
Code:
adb pull /sdcard/recovery.img
cp recovery.img recovery.cpio.gz
gunzip -f recovery.cpio.gz
mkdir recovery
cd recovery
cpio -i -F ../recovery.cpio
Edit the 'default.prop' to make the needed changes. It should look like.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
On my Mac again:
Code:
cpio -i -t -F ../recovery.cpio | cpio -o -H newc -O ../recovery-new.cpio
cd ..
gzip recovery-new.cpio
dd if=/dev/zero of=recovery-new.img count=16384 bs=512
dd if=recovery-new.cpio.gz of=recovery-new.img conv=notrunc
adb push recovery-new.img /sdcard/recovery-new.img
On Vizio using adb as root:
Code:
dd if=/sdcard/recovery-new.img of=/dev/block/mmcblk0p5 bs=512
Now reboot VTAB into Recovery mode. You should have adb access.
PS: If you have made any mistakes, you can reflash the original recovery.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5 bs=512
PPS: Once you have adb root shell access in recovery, you can backup and potentially restore the /system partition.
PPPS: I am attaching my recovery-new.img. It is in zip format.
Click to expand...
Click to collapse
great tutorial i will give it a try, it would be nice if someone could do this and backup the system partition on a new vtab that way if something goes wrong you can reflash it
additional thoughts could this lead to rom porting as well http://android.modaco.com/topic/348695-guide-how-to-port-a-rom/
dylanparrish said:
great tutorial i will give it a try, it would be nice if someone could do this and backup the system partition on a new vtab that way if something goes wrong you can reflash it
Click to expand...
Click to collapse
Users cannot modify the system partition. Therefore the only difference between a new system partition and after rooting should be the root that were installed such as su, busybox etc.
PS: I assume that all Vizio tablets have the same partition structure with an 8MB recovery partition at /dev/block/mmcblk0p5.
rprr said:
Users cannot modify the system partition. Therefore the only difference between a new system partition and after rooting should be the root that were installed such as su, busybox etc.
PS: I assume that all Vizio tablets have the same partition structure with an 8MB recovery partition at /dev/block/mmcblk0p5.
Click to expand...
Click to collapse
But after root one can modify /system and thus brick the device. If wed have a backup we can dd it back while in recovery mode.
Yes, since there is only one vizio tablet model, all have the same partition layout.
----------------------------------------
tapatalked
Obsolete. Please see OP.
HOWTO: Backup/Recovery of /system using command line tools.
Once you have adb working in recovery mode this is what you can do to backup and recover your /system partition.
### Backup Procedure ###
Boot into recovery mode.
Code:
adb shell
You will get the following error. Ignore it.
Code:
sh: getcwd: No such file or directory
Now do the following. Assumes internal sdcard at mmcblk0p4 and /system at mmcblk0p2
Code:
cd /
mount -o rw -t vfat /dev/block/mmcblk0p4 /sdcard
dd if=/dev/block/mmcblk0p2 of=/sdcard/system.img bs=4096
The system.img file contains a backup of the /system. In principle one can recover from this.
### Recovery Procedure ###
Reboot into recovery.
Code:
adb shell
cd /
mount -o rw -t vfat /dev/block/mmcblk0p4 /sdcard
dd if=/sdcard/system.img of=/dev/block/mmcblk0p2 bs=4096
Reboot into normal mode.
I have not yet had a need to do the recovery part yet so that has not been tested by me.
HTH.
Linked in my howto thread...
----------------------------------------
tapatalked
I have not been able to get this to work. After booting into recovery my win7 sees the vtab as usb storage and not usb composite. I guess this is whats causing ADB to not see it as a device. Any suggestions?
grekco said:
I have not been able to get this to work. After booting into recovery my win7 sees the vtab as usb storage and not usb composite. I guess this is whats causing ADB to not see it as a device. Any suggestions?
Click to expand...
Click to collapse
I have been using a Mac. I don't know what would be causing this issue on Windows. In my situation I need to restart adb.
Good work as always rprr and fade... appreciate the time u guys are putting into this tab, i'm always checking the threads for updates.
error: device not found.
My computer says its connect and ready but adb not recognizing it. Any ideal?
abtxpress said:
error: device not found.
My computer says its connect and ready but adb not recognizing it. Any ideal?
Click to expand...
Click to collapse
Can you try "adb kill-server" followed by "adb start-server" before connecting the device? Then connect the device and do "adb devices".
Unfortunately I don't have easy access to a Windows machine.
Edit: I wonder if the Windows drivers required are different depending on whether one is accessing adb through recovery mode when compared to normal mode.
Update on CWM: Still no luck with CWM porting.
But,
I decided to go back to the android stock source source code for 2.3.2 which is on the Vizio tablet. This time I was able to build the recovery binary and then copy it to the recovery partition. I was able to get this to run but the graphics is all distorted in the following way.
1) I see 4 exclamation symbols in landscape mode and 2 recovery menus (see pic)
2) It does not respond to the volume buttons + power button
I am guessing that there are frame buffer issues + input issues.
UPDATE: Just found information at the following link, see below. Looks like you can't get better backup capability without unlocking the boot loader first. Doing so would destroy the DRM keys (No more Netflix's etc...) Guess I will live with my ROOTED Atrix 4G for now..
http://android.stackexchange.com/questions/15314/cant-boot-to-clockwork-recovery-on-atrix-several-methods-tried
My Atrix 4G phone is currently rooted but does NOT have the bootloader unlocked. I do not plan to (at least for the forseeable future) installing different ROM's but I would like to install (if possible) the CWM restore partition. Unlocking the bootloader wipes the device (backups can be performed to restore the wiped information); likewise, the DRM keys are removed during the bootloader unlocking procedure and there MIGHT be ways to restore them (watching streaming video is important to me).
From what I have read on this forum and others, I should be able to load the CWM restore partition WITHOUT unlocking the bootloader. There are a few methods documented to install the CWM werewithall onto the restore partition BUT would something like the following also work?
From an SSH connection to the rooted phone or an "adb shell" command window (via a USB connection between the Atrix and PC) perform the following:
Backup the current restore partition delivered my Motorola via the following command in case something goes wrong.
dd if=/dev/block/mmcblk0p10 of=/sdcard-ext/recovery.img
Copy the recovery.img file to your PC for additional safe keeping.
Zero out the restore partition before installing the new CWM recovery image.
dd if=/dev/zero of=/dev/block/mmcblk0p10
Copy the new cwm.img image to the recovery partition using the following command:
Note the replacement cwm image file can NOT be larger than 8192 blocks with each block being 512 bytes.
8192 * 512 * 2 = 8,388,608 bytes. If the cwm image is to big, I am not sure if the following dd command would write into the p11 boot partition (NOT good). Verify cwm.img size BEFORE issuing the following DD command.
dd if=/sdcard-ext/cwm.img of=/dev/block/mmcblk0p10
In the avent of a problem, you should be able to restore the original Motorola recovery.img to the /dev/block/mmcblk0p10 partition with the following command:
dd if=/sdcard-ext/recovery.img of=/dev/block/mmcblk0p10
FYI follows are the md5sums from my "Atrix 4g" as delivered original factory boot.img and recovery.img
/mnt/sdcard-ext/root_recovery_orig # cat md5sums.txt
bc6c254bd80bed5a9c0d3c7cd5c77b07 boot.img from /dev/block/mmcblk0p11
7580ad9c3bca264a563c13741162d9b8 recovery.img from /dev/block/mmcblk0p10
/mnt/sdcard-ext/root_recovery_orig # ls -al *.img
----rwxr-x 1 system sdcard_r 8388608 Nov 15 13:20 boot.img
----rwxr-x 1 system sdcard_r 8388608 Nov 15 13:19 recovery.img
I assume the factory LOCKED bootloader located on the first partition /dev/block/mmcblk0p1 does NOT effect booting into the new cwm recovery partition via the "adb reboot recovery" command or by holding the volume down while powering on the phone?
When booting into the new CWM recovery partition, what /dev/block/mmcblk0 partitions are mounted? If any partitions are mounted, are they mounted read-only?
Booting from the content of the CWM recovery partition, can I backup/restore the entire /dev/block/mmcblk0 device (all 18 partitions)? Nothing like creating a full device image (with nothing mounted r/w) for when disaster strikes.
Assuming any of the above is valid, I need get the cwm dd image for somewhere (pointers welcome)
Issuing DD commands can be VERY-VERY-VERY dangerous if done wrong. If you do not understand how dd works, PLEASE do NOT attempt anything you read in this post. Until other forum members comment on this post content, I do NOT plan do anything (neither should anyone else!!!!)
Regards, Ron
Request for info from someone with CWM installed in recovery partition
Could I get someone who has CWM working on their Atrix 4G to please run the following command from the su prompt on the smartphone and post the output.
# fdisk -lu /dev/block/mmcblk0
Also please indicate if you have the bootloader unlocked or not.
Regards Ron
rrolsbe said:
My Atrix 4G phone is currently rooted but does NOT have the bootloader unlocked. I do not plan to (at least for the forseeable future) installing different ROM's but I would like to install (if possible) the CWM restore partition. Unlocking the bootloader wipes the device (backups can be performed to restore the wiped information); likewise, the DRM keys are removed during the bootloader unlocking procedure and there MIGHT be ways to restore them (watching streaming video is important to me).
From what I have read on this forum and others, I should be able to load the CWM restore partition WITHOUT unlocking the bootloader. There are a few methods documented to install the CWM werewithall onto the restore partition BUT would something like the following also work?
From an SSH connection to the rooted phone perform the following:
Backup the current restore partition delivered my Motorola via the following command in case something goes wrong.
dd if=/dev/block/mmcblk0p10 of=/sdcard-ext/recovery.img
Copy the recovery.img file to your PC for additional safe keeping.
Zero out the restore partition before installing the new CWM recovery image.
388,608
dd if=/dev/zero of=/dev/block/mmcblkp10
Copy the new cwm.img image to the recovery partition using the following command:
Note the replacement cwm image file can NOT be larger than 8192 blocks with each block being 512 bytes.
8192 * 512 * 2 = 8,388,608 bytes. If the cwm image is to big, I am not sure if the following dd command would write into the p11 boot partition (NOT good). Verify cwm.img size BEFORE issuing the following DD command.
dd if=/sdcard-ext/cwm.img of=/dev/block/mmcblk0p10
In the avent of a problem, you should be able to restore the original Motorola recovery.img to the /dev/block/mmcblk0p10 partition with the following command:
dd if=/sdcard-ext/recovery.img of=/dev/block/mmcblk0p10
I assume the factory LOCKED bootloader located on the first partition /dev/block/mmcblk0p1 does NOT effect booting into the new cwm recovery partition via the "adb reboot recovery" command or by holding the volume down while powering on the phone?
When booting into the new CWM recovery partition, what /dev/block/mmcblk0 partitions are mounted? If any partitions are mounted, are they mounted read-only?
Booting from the content of the CWM recovery partition, can I backup/restore the entire /dev/block/mmcblk0 device (all 18 partitions)? Nothing like creating a full device image (with nothing mounted r/w) for when disaster strikes.
Assuming any of the above is valid, I need get the cwm dd image for somewhere (pointers welcome)
Issuing DD commands can be VERY-VERY-VERY dangerous if done wrong. If you do not understand how dd works, PLEASE do NOT attempt anything you read in this post. Until other forum members comment on this post content, I do NOT plan do anything (neither should anyone else!!!!)
Regards, Ron
Click to expand...
Click to collapse
Another question/Observation
It might be possible that the factory supplied locked bootloader checks the "Digitial Signature" of the recovery partition before booting into recovery mode is allowed??? If this is true, the signature check of the CWM image would FAIL thus requiring an unlock of the boot loader! Hopefullly, dd'ing the original saved recovery.img back onto the recovery partition would at least get back to factory configuration (IE.. allow booting into factory supplied recovery mode)!!
Again, Thanks for any help regarding this post!
Regards, Ron
rrolsbe said:
Could I get someone who has CWM working on their Atrix 4G to please run the following command from the su prompt on the smartphone and post the output.
# fdisk -lu /dev/block/mmcblk0
Also please indicate if you have the bootloader unlocked or not.
Regards Ron
Click to expand...
Click to collapse
Code:
[B]# fdisk -lu /dev/block/mmcblk0[/b]
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders, total 31083520 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 8191 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 8192 9215 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 9216 13311 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13312 31005695 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 14336 16383 1024 83 Linux
/dev/block/mmcblk0p6 16384 17407 512 83 Linux
/dev/block/mmcblk0p7 17408 18431 512 83 Linux
/dev/block/mmcblk0p8 18432 20479 1024 83 Linux
/dev/block/mmcblk0p9 20480 24575 2048 83 Linux
/dev/block/mmcblk0p10 24576 40959 8192 83 Linux
/dev/block/mmcblk0p11 40960 57343 8192 83 Linux
/dev/block/mmcblk0p12 57344 712703 327680 83 Linux
/dev/block/mmcblk0p13 712704 2285567 786432 83 Linux
/dev/block/mmcblk0p14 2285568 2326527 20480 83 Linux
/dev/block/mmcblk0p15 2326528 3637247 655360 83 Linux
/dev/block/mmcblk0p16 3637248 7831551 2097152 83 Linux
/dev/block/mmcblk0p17 7831552 8538111 353280 83 Linux
/dev/block/mmcblk0p18 8538112 31005695 11233792 83 Linux
As far as installing custom recovery with locked bootloader goes, I'm pretty sure that won't work, or else someone would've come up with that long long time ago.
Thanks!!
ravilov
Thanks for the information in your post. Since it appears that some owners have replaced their recovery partition with CWM having only rooting, I was hoping that the recovery partition might NOT be signed by Motorola and checked during the recovery boot process. BTW, my Atrix 4G is an International carrier unlocked version. I have another Atrix 4G on order, I might try DD'ing to the recovery partition and if that fails roll back the recovery.img backup. If the recovery partition is actually signed and checked during the boot process, returning the partition bit-for-bit with the original SHOULD revert to factory. From my reading, it some cases the recovery partition is NOT signed even though the bootloader/boot partition IS signed.
Again, Thanks Very Much for your post
Regards, Ron
DISCLAIMER: THIS IS VERY DANGEROUS COMPARED TO A NORMAL ROM FLASH. DO NOT DO THIS IF YOU DON'T KNOW WHAT YOU'RE DOING OTHER THAN FLASHING ROMS.
IF SOMETHING GOES WRONG, YOU HAVE ONLY YOURSELF TO BLAME. YOU HAVE BEEN WARNED.[/B]
To convert to Nexus 4
First off, there are a few issues.
-SDCard doesn't work.
-Capacitive buttons aren't working. No known way to fix it.
First off, lets flash the N4 Rom.
1) Install LGNPST - Use tSilenzio's AutoLGNPST - http://www.oudhitsquad.com/android/LGE/Firmware/Tools/AutoLGNPST-tSilenzio.zip
2) Download the Nexus 4 Image - https://www.androidfilehost.com/?fid=9390248398092765463
3) Rename the extracted .tot file to a .bin file
4) Put the phone in Download mode. Volume Up + Volume Down While inserting USB cable.
5) Open LGNPST and select the phone - Should be Com[Number]
6) In the DLL section, select LGNPST_LS970.dll
7) In the file selection, select the previously renamed Nexus 4 bin file.
8) Start the flashing process and hold your breath.
9) When it hits 67%, your phone should start booting. DO NOT UNPLUG YET.
10) At 85%, an error will occur saying that the phone was unplugged. Ignore it and close LGNPST. The image is fully flashed.
11) Hold Volume Up + Power to put the phone into FASTBOOT mode.
12) Download the recovery from here and place it into your fastboot directory. - http://forum.xda-developers.com/showthread.php?t=2010984
13) Download the following 3 files and place them on the MicroSD card. - http://d-h.st/cFA - http://d-h.st/yUQ - http://d-h.st/0dH
14) While still in fastboot, type "fastboot boot recovery.img" - This will put the phone on the custom recovery. Make sure the SD card is in.
---Here, we're going to fix the partition tables for 16GB of space and replace the backup GPT so that we can't hardbrick from the backup GPT.
15) Run adb shell to get into a root shell in recovery.
16) Copy the modified DD onto the phone
Code:
# cp /external_sd/dd /
# chmod 755 /dd
17) Backup the partition tables incase something goes wrong.
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/pgpt8G.img bs=512 count=34
# /dd if=/dev/block/mmcblk0 of=/external_sd/sgpt8G.img bs=512 skip=30777311
18) Unmount the filesystems so that you can overwrite the partition table.
Code:
# umount /data
# umount /cache
19) Make sure nothing is mounted. It should return this (Other than partition size):
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 911.7M 48.0K 911.6M 0% /dev
/dev/block/mmcblk1p1 59.4G 4.8G 54.6G 8% /external_sd
20) Move the partitions to their new locations. This may take a couple minutes.
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/DDR bs=512 skip=15267840 count=2015
# /dd if=/external_sd/DDR of=/dev/block/mmcblk0 bs=512 seek=30775296 conv=notrunc
21) Install the new partition tables.
Code:
# /dd if=/external_sd/sgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
22) Make sure no errors occurred. Run 'parted /dev/block/mmcblk0' and check that it returns the same as the below.
Code:
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) p
p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 15.8GB 14.1GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow
23) If something different was returned, run the below code to restore the previous partition tables.
Code:
# /dd if=/external_sd/sgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
24) Exit the shell and type 'adb reboot bootloader' or reboot the phone while holding Volume Up.
25) Check that you're in fastboot mode and exit the following commands - This will fix the filesystem to take up the entire partition.
Code:
fastboot erase userdata
fastboot format userdata
fastboot -w
26) Boot the phone and update as needed. Then, put this on the phone and flash in recovery.
27) You are now working other than the SD card and Capacitive buttons.
Credits:
http://forum.xda-developers.com/showthread.php?t=2117576
http://forum.xda-developers.com/showthread.php?t=2099784
http://forum.xda-developers.com/showthread.php?t=2160124
http://forum.xda-developers.com/showthread.php?t=2146816
To convert from Nexus 4
This assumes that you have read the Convert to section.
1) Wipe the phone. Go into fastboot mode [Vol Up + Power] and execute the following commands. This is to prevent corrupted data partitions.
Code:
fastboot -w
fastboot format system
fastboot format userdata
fastboot format cache
fastboot format data
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase data
2) LGNPST back to stock. You will do this twice to fix some issues.
To get into download mode, turn the phone off and hold Vol Up + Vol Down while inserting the USB cable.
3) Download these 2 images. Mar. 8, 2013 and Sept. 29, 2012
4) Flash the Mar. 8, 2013 firmware in LGNPST (See above for how to flash firmware in LGNPST. As before, the phone will start booting at 67% and LGNPST will show an error at 85%. Ignore the error and close LGNPST.
5) Restart the phone in download mode and now flash the Sept. 29, 2012 firmware. If you don't, your /SDCARD may be corrupted and you cant root.
6) Root the phone and unlock the bootloader. See here
7) If that doesn't work, try Teenybin.
8) Some partitions are broken. Go into CWM recovery and open an 'adb shell'.
9) Execute the following code. This will backup the broken partitions and wipe them.
Code:
dd if=/dev/block/mmcblk0p15 of=/sdcard/mmcblk0p15.bak
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16.bak
dd if=/dev/block/mmcblk0p19 of=/sdcard/mmcblk0p19.bak
mke2fs -T ext4 /dev/block/mmcblk0p15
mke2fs -T ext4 /dev/block/mmcblk0p16
mke2fs -T ext4 /dev/block/mmcblk0p19
---You should now be back to stock--- LGNPST again if you want 'True Stock'
Let me know if you see anything wrong and please leave nasty comments at the door.
Ok, granted. This is more about recovering from flashing to Nexus 4 than about flashing to it. Basically, DON'T DO IT, as it doesn't seem to be worth it. We have AOSP and Cyanogen, etc.
I just posted this because I bought a phone that was flashed and went through hours of work fixing it.
Please read this before you think about flashing. http://forum.xda-developers.com/showpost.php?p=36735476&postcount=149
Its not worth it so much now but it was great when first released and it doesn't take that long to revert your phone. I went back and fourth like 5 times and my phone is fine. I think there is a low chance of your phone bricking as long as you follow instructions. The conversion is still a good option to have.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Dr0!dFreek said:
Its not worth it so much now but it was great when first released and it doesn't take that long to revert your phone. I went back and fourth like 5 times and my phone is fine. I think there is a low chance of your phone bricking as long as you follow instructions. The conversion is still a good option to have.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it seems nice to have the ability to do so, which is why I wrote the guide (and to give a single comprehensive guide that works).
It's nice to have a perfectly working KitKat rom the day its released, which is why I converted (When KK was released), but now, it doesn't seem worth it (We have AOSP). If you want MultiRom and franco kernel (Like I did), then its nice to have, but otherwise, most people don't need it.
alastair53 said:
13) Download the following 3 files and place them on the MicroSD card. - http://d-h.st/cFA - http://d-h.st/yUQ - http://d-h.st/0dH
Click to expand...
Click to collapse
Is this part SPYWARE? the 3 files downloads a exe and is detetected as virus or something.
I'm porting myllo.setya (and BigMajster)'s script.
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
Requirement:
G2 Mini D620
Recovery (not the original)
30MB on external SD card
A rom zip or a nandroid
Install:
Boot in recovery
Install the script
Install a rom or restore stock
Mode:
Maximal- system partition have only 730mb so you can install only custom rom like CynogenMod
Optimal- system partition have 1,5gb so you can also install stock LG rom, but you still have more data.
Stock- this is orginal partition table
Download here
|
v
GOOD LUCK :silly:
I used modific SH for D620r and it delete: system, cache, data, internal and RECOVERY (TWRP) , restored system not working for me. -> bootloop (Now Im with not working system and no recovery , Its NOT becouse sh is bad (its working), but its because I didnt flash recovery, and system not working - no idea why ) Yeah its my problem ( I dont take care , Its my stupidity) but I want to tell u how to do it better than me
Hmmm some realy function way how to flash kdz ?? or something to get my phone woking ??
Thanks a lot.
For others who want to use it on D620r do it this :
1) check u have some ROM and TWRP ( recovery) on yours SD card (backup not working for me, I used optimal settings)
2) go to recovery ,flash PTT
3) phone will be reboot and go to recovery (last chance !!) (DO NOT remove batteri !)
4) flash clear ROM (+ gapps) and RECOVERY (TWRP) !!
5) reboot and it will be working (I thing )
WoytazZer CZ said:
I used modific SH for D620r and it delete: system, cache, data, internal and RECOVERY (TWRP) , restored system not working for me. -> bootloop (Now Im with not working system and no recovery , Its NOT becouse sh is bad (its working), but its because I didnt flash recovery, and system not working - no idea why ) Yeah its my problem ( I dont take care , Its my stupidity) but I want to tell u how to do it better than me
Hmmm some realy function way how to flash kdz ?? or something to get my phone woking ??
Thanks a lot.
For others who want to use it on D620r do it this :
1) check u have some ROM and TWRP ( recovery) on yours SD card (backup not working for me, I used optimal settings)
2) go to recovery ,flash PTT
3) phone will be reboot and go to recovery (last chance !!) (DO NOT remove batteri !)
4) flash clear ROM (+ gapps) and RECOVERY (TWRP) !!
5) reboot and it will be working (I thing )
Click to expand...
Click to collapse
Do you have fastboot init message on top along with the LG logo ? If yes, connect to usb and try:
Code:
fastboot devices
If it shows your device, you are fine. Now download TWRP recovery from http://forum.xda-developers.com/g2-mini/development/recovery-twrp-2-8-3-0-recovery-lg-d620-t2990196 and boot it via fastboot:
Code:
fastboot boot <recovery image file>
This will boot into recovery with MTP support ( you will see you device on pc ), then upload ROM to SDcard and install it right away from recovery. Don't forget to install recovery later ( I hope you have unlocked bootloader )
I've just gone through similar issue, I have flashed partition table for D618 a got stuck on fastboot ... this thread ( and zip ) saved me !
"Zdravim taky z jednoho mista blizko Prahy"
kkoouu said:
Do you have fastboot init message on top along with the LG logo ? If yes, connect to usb and try:
Code:
fastboot devices
If it shows your device, you are fine. Now download TWRP recovery from http://forum.xda-developers.com/g2-mini/development/recovery-twrp-2-8-3-0-recovery-lg-d620-t2990196 and boot it via fastboot:
Code:
fastboot boot <recovery image file>
This will boot into recovery with MTP support ( you will see you device on pc ), then upload ROM to SDcard and install it right away from recovery. Don't forget to install recovery later ( I hope you have unlocked bootloader )
I've just gone through similar issue, I have flashed partition table for D618 a got stuck on fastboot ... this thread ( and zip ) saved me !
"Zdravim taky z jednoho mista blizko Prahy"
Click to expand...
Click to collapse
Thanks , but I can not go to fastboot mode (I don t know how , yeah its bad , but I used it only once, I google for it but nothing ) +vol + power and connect usb or how I can go to fastboot mode ? (I dont have fastboot init message on top along with the LG logo) I see extended kernel adn after that cpa bootanimation - > goes to bootloop. dowload mode works.
But I want ot try flash TWRP like u wrote here.
http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6
Try to get adb access in different modes ( even during system boot you can already have adb access ), try it with "adb shell" from pc and then try to zero the LAF as suggested in the post above, after reboot you should have a fastboot access
re
kkoouu said:
http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6
Try to get adb access in different modes ( even during system boot you can already have adb access ), try it with "adb shell" from pc and then try to zero the LAF as suggested in the post above, after reboot you should have a fastboot access
Click to expand...
Click to collapse
hmm, what keys do u use for fastboot ??
after this http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6 can I go to dowload mode ? or not? (its look its last think whats working and I want to take it works), and next questin , where do i write this ?
"( Broken dtb.img in kernel / recovery or by zero-ing out laf partition (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf)"
By doing so, the phone can't enter Download mode.
hmmm probablyin adb shell on pc , is it true ?? or Im stil on bad way ?
WoytazZer CZ said:
hmm, what keys do u use for fastboot ??
after this http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6 can I go to dowload mode ? or not? (its look its last think whats working and I want to take it works), and next questin , where do i write this ?
"( Broken dtb.img in kernel / recovery or by zero-ing out laf partition (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf)"
By doing so, the phone can't enter Download mode.
hmmm probablyin adb shell on pc , is it true ?? or Im stil on bad way ?
Click to expand...
Click to collapse
You cannot enter fastboot via keys.
If you can enter adb shell ( yes on pc ), enter:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
After reboot you should be in fastboot mode and continue as written in my first post.
kkoouu said:
You cannot enter fastboot via keys.
If you can enter adb shell ( yes on pc ), enter:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
After reboot you should be in fastboot mode and continue as written in my first post.
Click to expand...
Click to collapse
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Its not name of internal or external order
Im in C./adb>
I wrote : adb shell
its show: started successfully
error: device offline
WoytazZer CZ said:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Its not name of internal or external order
Im in C./adb>
I wrote : adb shell
its show: started successfully
error: device offline
Click to expand...
Click to collapse
Sorry but these are basics ... try to google it - f.e. http://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands
kkoouu said:
Sorry but these are basics ... try to google it - f.e. http://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands
Click to expand...
Click to collapse
but with other phone Sony Ericsson live with walkman its work show me its code.
i dont know what im doing wrong , I will try it again after pc finish reboot.
WoytazZer CZ said:
I used modific SH for D620r and it delete: system, cache, data, internal and RECOVERY (TWRP) , restored system not working for me. -> bootloop (Now Im with not working system and no recovery , Its NOT becouse sh is bad (its working), but its because I didnt flash recovery, and system not working - no idea why ) Yeah its my problem ( I dont take care , Its my stupidity) but I want to tell u how to do it better than me
Hmmm some realy function way how to flash kdz ?? or something to get my phone woking ??
Thanks a lot.
For others who want to use it on D620r do it this :
1) check u have some ROM and TWRP ( recovery) on yours SD card (backup not working for me, I used optimal settings)
2) go to recovery ,flash PTT
3) phone will be reboot and go to recovery (last chance !!) (DO NOT remove batteri !)
4) flash clear ROM (+ gapps) and RECOVERY (TWRP) !!
5) reboot and it will be working (I thing )
Click to expand...
Click to collapse
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
sergioslk said:
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
Click to expand...
Click to collapse
yeah I m planing do that , but now im trying flash recovery via adb
http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664#post61015063
but i dont have luck to conect phone to pc
---------- Post added at 03:44 PM ---------- Previous post was at 03:27 PM ----------
sergioslk said:
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
Click to expand...
Click to collapse
yeah , Im trying cs_emergency and cse flash
and Im stil stop on 4% and said reconect phone - again again .....
sergioslk said:
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
Click to expand...
Click to collapse
hmm no lucky with kdz ,I can not MTP drivers get working , is it theproblem ??
WoytazZer CZ said:
hmm no lucky with kdz ,I can not MTP drivers get working , is it theproblem ??
Click to expand...
Click to collapse
http://forum.xda-developers.com/g2-mini/general/complete-guide-vademecum-lg-g2-mini-t2900073
i used this guide to unbrick.
I downloaded lg flash tool then entered my IMEI on the lg website to download stock rom.
connect my phone with usb on pc while on download mode and then do cse flash with the flash tool.
it opens stock lg softaware updater and then it goes smoothly after showing "cant access the lg server"or smthing.
IIRC i used cdma and diag.
did u already fixed this?, maybe i can help u, because i've tried this and i lost all data on internal storage, even download mode, and it says no OS installed
PTT_D620 I do not advise to use is not built for LG G2 mini. It contains errors.
Manual is easy using parted:
Backup complet /system, /data, /cache. Backup type file *.tar in recovery mode.
in pc adb shell in recovery mode
# 1,5GiB /system 1610613247B
# 100MiB /cache 104858111B
# 5,22Gib /userdata 5601378303B
parted -s /dev/block/mmcblk0 rm 32
parted -s /dev/block/mmcblk0 rm 33
parted -s /dev/block/mmcblk0 rm 34
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
Click to expand...
Click to collapse
Restore /system, /data, /cache
I was trying to do this but couldn't, i get stuck on fastboot mode and my pc doesn't recognize it. I tried the partition tool from D618, same! So for the last post i can't exactly understand what to do from adb shell! Just do my backups and then start giving the commands:
Code:
parted -s /dev/block/mmcblk0 rm 32
parted -s /dev/block/mmcblk0 rm 33
parted -s /dev/block/mmcblk0 rm 34
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
or there is something more to do??
????
Run phone recovery mode
Plug usb cable pc and phone
run cmd.exe -> adb shell
*show partitions
parted /dev/block/mmcblk0 p
*delete partitions 32 - system, 33 - cache, 34 - data
parted /dev/block/mmcblk0 rm 32
parted /dev/block/mmcblk0 rm 33
parted /dev/block/mmcblk0 rm 34
* create new resize partitions
parted /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
* format partitions
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
thank you :good: and one more!
this part:
Code:
parted /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
The sizes are on Byte (?) , because i want minimal partition.. (730MB System, 100MB cache, 6GB userdata) so i can change them...
Yes, unit byte. More info parted unit and parted syntax
Beware MB not MiB!
/ cache 100MiB = 104858111B = 104MB
Resizing LG G2 partition size​Must have: Latest TWRP Recovery, ADB experience and gdisk for arm in attached zip.
Clean /system partition (unused apps, bloatware, garbage and so on...)
Backup everything important from /sdcard.
Reboot to TWRP and connect ADB (if "ADB devices" fails, check windows "Device Management" and install "Android Sooner Single ADB Interface" for your unrecognized phone).
In TWRP backup /system and /data and download /sdcard/TWRP folder via MTP to your PC.
Now it's ADB time:
Code:
[B]# check /system used space (in Mb) and remember it, as we should cut no more than "Available" space:[/B]
adb shell "mount /system"
adb shell "df -m /system"
[B]# un-mount partitions:[/B]
adb shell "umount /system"
adb shell "umount /data"
adb shell "umount /sdcard"
adb shell "umount /cache"
[B]# unzip gdisk in your ADB folder and install it:[/B]
adb push gdisk /sbin
adb shell "chmod 0755 /sbin/gdisk"
[B]# check partitions info:[/B]
adb shell "/sbin/gdisk -l /dev/block/mmcblk0" >gpt.txt
[B]# open new gpt.txt file in your ADB folder
# now you should recalculate your new partitions (30-36) size and position (in sectors)
# partition start-sector should be even, end-sector should be odd
# to make it simplier, use formula: (new size in MB) * 2048 + 1 = (new size in sectors)[/B]
Check my examples:
Code:
default (4.4.2 firmware):
30 819200 6488063 2.7 GiB 0700 system
31 6488064 7733247 608.0 MiB 0700 cache
32 7733248 7897087 80.0 MiB 0700 tombstones
33 7897088 7929855 16.0 MiB 0700 spare
34 7929856 8028159 48.0 MiB 0700 cust
35 8028160 60948479 25.2 GiB 0700 userdata
36 60948480 61071326 60.0 MiB 0700 grow
my mod v1:
(30) 800000 3526297 1.3 GiB system
(31) 3526298 3853977 160 MiB cache
(32) 3853978 3858073 2 MiB tombstones
(33) 3858074 3862169 2 MiB spare
(34) 3862170 3866265 2 MiB cust
(35) 3866266 61067229 27.2 GiB userdata
(36) 61067230 61071326 2 MiB grow
my_mod_v2:
(30) 800000 2897153 1 GiB system
(31) 2897154 3122433 110 MiB cache
(32) --- --- deleted tombstones
(33) --- --- deleted spare
(34) 3122434 3126531 2 MiB cust
(35) 3126532 61071326 27.6 GiB userdata
(36) --- --- deleted grow
Important! It's only mine D802 4.4.2 example. You should calculate your own values, because of your /system used size, /cust size for unlock, etc.
/spare and /grow partitions unused on our phones. /tombstones is obesolete since it mounts from /data, anyway.
After all checks and calculations, let's do the magic:
Code:
[B]# run gdisk:[/B]
adb shell
cd /sbin
gdisk /dev/block/mmcblk0
[B]# no real changes applied to the phone, before "w" command.
# if you did something wrong, exit by "q" command
# you can check youreself with "p" command (partition list with virtual changes you made).
# OK, let's delete our old partitons and create them anew:[/B]
"d" command > enter partition number (for all 30-36 partitons).
"n" command > enter partition number > start > end > code (start & end = new values in sectors, code = 0700)
"c" command > enter partition number > name (system, cache, etc.)
[B]# if all seems fine, and you're pretty sure of youreself:[/B]
"w" command > "Y" answer
[B]# there is no FS on new partitions, so format them:[/B]
mke2fs -t ext4 /dev/block/mmcblk0p30
mke2fs -t ext4 /dev/block/mmcblk0p31
mke2fs -t ext4 /dev/block/mmcblk0p34
mke2fs -t ext4 /dev/block/mmcblk0p35
[B]# there is no point to format others, because they have no fs by default.
# if using kernel with F2FS support (like Dorimanx), you can format some of them as F2FS:[/B]
mkfs.f2fs /dev/block/mmcblk0p35
[B]# to make TWRP realise, horrors we just did - reboot it:[/B]
reboot recovery
[B]# after reboot, we can optimize /userdata a bit (ext4 only), with this:[/B]
adb shell "tune2fs -m 0 /dev/block/platform/msm_sdcc.1/by-name/userdata"
[B]# bring backups from PC to /sdcard via MTP and restore them, as usual
# now you can reboot to your system with custom-sized partitions!
# P.S. If you notice your /sdcard permissions glith a bit after all this - flash "sdcard Fix Permissions script" from [URL="http://forum.xda-developers.com/showthread.php?t=2239421"]this[/URL] thread.[/B]
Good luck.
Awesome :good: this guide will help 16GB user like me to increase data/sdcard partition
Too bad I don't have pc to play around with....
so, stock, user-usable fresh after format on KK4.4 we have 24GB on the /sdcard part. Would we want to use this to go smaller? Would there be a benefit to that? Or would I want to use it to go larger, shrinking my /sdcard
I know it can go both ways, but which are people more interested in here?
rancur3p1c said:
I know it can go both ways, but which are people more interested in here?
Click to expand...
Click to collapse
Who knows? It's not that hard, it takes 5 minutes, it gets you + 1-3 Gib on the phone (without SD-Card support), and it's safe - coz we don't touch bootloader or recovery partitions... It's worth it.
THIS is just pure awesome
I've followed the guide and successfully added almost 2gb to userdata on my 16gb d802
This is my gpt for now
30 791568 4158721 1.6 GiB 0700 system
31 4158722 4306179 72.0 MiB 0700 cache
34 4306180 4310277 2.0 MiB 0700 cust
35 4310278 30777310 12.6 GiB 0700 userdata
And this is my aim, if i have time to do it again
30 791568 3937297 1.5 GiB 0700 system
31 3937298 3961875 12.0 MiB 0700 cache
34 3961876 3965973 2.0 MiB 0700 cust
35 3965974 30777310 12.7 GiB 0700 userdata
Also, i've notice this in the gpt.txt file
Total free space is 230360 sectors (112.5 MiB)
So can we get even more from our phone?
Hello everybody
first of all I ll thank you for your guide Resizing LG G2 partition size.
But no I have problems with installing a new rom. Everytime I enter twrp I get the message "Can't mount /system". So its impossible for me to install a new rom.
All partitions seems to be fine. gdisk works perfect without any errors.
My partition table looks like:
Code:
30 819200 3686401 1.4 GiB 0700 system
31 3686402 4014083 160.0 MiB 0700 cache
34 4014084 4034565 10.0 MiB 0700 cust
35 4034566 30777310 12.8 GiB 0700 userdata
If someone have any idea how I can solve this problem?
Thanks
Chris
I am thinking to try this tool, but I would like to know if flashing kdz will work in case I screw things up, or am I risking to permanently brick the phone?
Okay, going back to stock partitions will fix my problem and my system partition is again 2.7 GB
With the customised partitions i was unable to install neither Resurrection Remix Rom nor Google Edition 1.5. Both return an error in twrp.
Backfisch said:
Everytime I enter twrp I get the message "Can't mount /system". So its impossible for me to install a new rom.
All partitions seems to be fine. gdisk works perfect without any errors.
Click to expand...
Click to collapse
I have the same problem. Did you fix it by any chance?
Yes, going back to the stock values of the partition using the gdisk again.
Its also import to make sure the partition format works correct. Better format twice....
Backfisch said:
But no I have problems with installing a new rom. Everytime I enter twrp I get the message "Can't mount /system". So its impossible for me to install a new rom.
Click to expand...
Click to collapse
Okay, the fix is that you have to restore TWRP backup, in my case CM13 booted all good. But now I have a different problem, the MTP connection is really unstable, disconnects and reconnects for no reason. Same problem using twrp mtp or cm mtp. Tried two different cables, two different pc, and resized the partitions twice using different values. Still no luck. Anyone had any similar experience?
EDIT: Seems my charging port is failing. Many cables have hard time being stable, but some of them work better.
Backfisch said:
Yes, going back to the stock values of the partition using the gdisk again.
Its also import to make sure the partition format works correct. Better format twice....
Click to expand...
Click to collapse
Back when I tried to resize the /system partition, all non-lg rom doesnt install because of that error, and they are the ones that has the most potential of freeing some space
you can only get some space from /cache and other partitions without getting errors
I have gained 2 Gb extra space on the internal memory, and it works great so far. The only problem is that flashing roms from twrp returns the error /system can not be mounted, and you have to install the rom by restoring twrp backups.
Am I right in thinking that you cant install an rom update with modified partitions by flashing it in twrp?
If restoring my backup is the only way to install my rom, I will delete some music and pictures on the userdata partition...
You can install roms with "system" folder and files in it, on modified partitions (if you have enough space in /system, of course).
But you won't be able to install CyanogenMod-based roms with partition image in them (system.img, system.bin, etc.)
I played with this a bit and something went wrong Now i can't flash any os neither TOT or KDZ. I dismantled my phone to enter 9006 mode and recover it from there. But with no success :c What should i do now? I have my stock values of 30f saved, but after flashing kdz and tot i have stock recovery. It doesn't have adb suppor so i can't start gdisk operation. And i can't push any rom or recovery by sideload. When recovery starts I have list of errors. It can't mount system, data etc. I think I bricked it quite well xd
SantoSubito said:
I played with this a bit and something went wrong Now i can't flash any os neither TOT or KDZ. I dismantled my phone to enter 9006 mode and recover it from there. But with no success :c What should i do now? I have my stock values of 30f saved, but after flashing kdz and tot i have stock recovery. It doesn't have adb suppor so i can't start gdisk operation. And i can't push any rom or recovery by sideload. When recovery starts I have list of errors. It can't mount system, data etc. I think I bricked it quite well xd
Click to expand...
Click to collapse
Did you fix it yet? Does download mode work? Why didn't work flashing kdz in the first place?
Yes it does. After flashing kdz phone enters recovery and I have list of errors. And when i tried to flash tot i have error something with laf partition and gpt. Yesterday i tried to recover it from 9008 but I'm also getting error :c
SantoSubito said:
And when i tried to flash tot i have error something with laf partition and gpt.
Click to expand...
Click to collapse
Try to flash TOT-firmware with modded dll (bypass gpt-error). One of this should do the trick.
Yeah it worked. But not in 100%. When its 94% my phone reboots and LG Tool shows:
...
CACHE
CACHE
CUST
Wiating for the device 120s
then device reboots and get bootloop
BoardDiag have this wierd dload error and also i cant do nothing with this tool