Hi,
I have a bunch of ME176CX Asus Memopad 7's that I wanted to be identical with their settings, apps, etc. and also have a base "image" of that for if I needed to restore it over time.
I rooted them all (Android 5.0.), installed TWRP on them all and then customized one to be exactly what I wanted - removed bloatware, got the settings to what they needed to be, etc.
I then backed up that tablet and restored it on the rest. They are working fine and everything is as expected except with wifi.
The tablets now all have the same identical MAC address and because of that are all attempting to grab the same DHCP ip address and are constantly knocking each other off by duplicating the IP.
I looked around and found that the mac address on other android devices is defined in nvram.txt in /data/misc/wifi however that does not exist on these.
I'm assuming it has to be defined somewhere as otherwise they wouldn't all have the same Mac... and essentially wherever that is being defined is where it could be changed to either revert back to their old Macs or just create new ones.
(Setting them to static ip's is not an option, I need their macs to be different)
Anyone have any insight to fixing this?
So while the tablet is running with wifi off I can change /config/wifi/mac.txt to a be a new mac, and turn wifi on and it will change it. However upon reboot this gets reset back to that original mac address.
Further development...
It was copied by the backup accidently having boot checked off in TWRP and then restoring with that. The serial/mac appear to be contained in the boot partition.
Recovery log for the boot:
I:Reading '/dev/block/mmcblk0p4', writing '/external_sd/TWRP/BACKUPS/01234567890123456789/zzz/boot.emmc.win'
/boot | /dev/block/mmcblk0p4 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p4
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
So now I guess the only way to fix that would be to somehow edit that boot.emmc.win
or
edit the mac, and re-backup the boot with the new mac address to restore it on the other devices
Related
This thread will list and link to all core device essential stuff.
PM me if there is new stuff please
STOCK ASUS FIRMWARE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
Seperate Sd update for WW versions to recover from wrong released OTA, when unzipped place it on MicroSdcard and reboot:
WW_10_26_1_18_SDupdate.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
TW_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
US_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_42_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
Altered CWM Recovery V6.0.3.7. for 4.2.2.*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery CWMrecovery4.2.2.img [where CWMrecovery4.2.2.img is the name of the file image you downloaded]
There is at the moment no CWM-Recovery or TWRP-Recovery for 4.3. version yet!!!
* With thanks to Drgravy for his work on that.
CUSTOM ROM'S
None available yet.
Will be released by Sbdags when there is a custom recovery for 4.3. available.
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!
Odd that you just started this thread and it's outdated ;P
Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/showthread.php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/showthread.php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/showthread.php?t=2621028
Sorry folks. Thread closed as it already exists in the General Forum.
MD
Hi guys,
I have been checking most threads for the past two days and have tried quite a lot of stuff finally leading me back to this post.
I have a HTC 802w which I bought when I was living in China. I was happily on Sense 5.5 with the 4.4.2 update and thought I would atleast root the phone and remove all the Chinese bloatware.
My phone is S-ON with an unlocked bootloader. I then flashed on a CWM 6.0.3. But after the flash ( which was successful),whenever I boot, I was always redirected to the bootloader screen (FASTBOOT)
I've tried the following options:
a) fastboot erase cache - Reboot
b) Flashed TWRP (for 802w) and then flashed Maximus HD 2.0.0 (which is one of the few ROMs that the HTC One 802w supports)
TWRP : http://forum.xda-developers.com/showthread.php?t=2467536
After these two, nothing happened. I was still stuck at bootloader and able to go through TWRP recovery as well.
c) I flashed stock recovery, relocked the bootloader (fastboot oem lock) and attempted to install the 4.4.2 RUU for 802w
fastboot oem rebootRUU
fastboot flash zip <zipfile>
Stock Recovery from : http://forum.xda-developers.com/showthread.php?t=2617159
RUU : http://forum.xda-developers.com/showpost.php?p=43177948&postcount=369 ( 4.4.2 RUU for Chinese Version)
-> Same result.
C:\Users\Downloads\HTC1_802W Root>fastboot flash zip latestfirmware.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1128400 KB)...
OKAY [ 53.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.042s
This is the getvar of my device:
C:\Users\Downloads\HTC1_802W Root>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.14.3509.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.1402.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: H*******************
(bootloader) imei: 3********************
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTCCN703
(bootloader) battery-status: good
(bootloader) battery-voltage: 4301mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 4.013s
I am still researching other posts ( I know how most of you hate the same question being asked. I don't like it too) . But I vastly underestimated the resource base of the 802w phones. So if anyone of you guys out there is able to give me a few pointers, you got a beer waiting for you next time you visit the Bay Area..
Cheers!
UPDATE:
I flashed on Maximus HD again (with unlocked bootloader and same TWRP as above) -> Stilll on the same problem. I tried checking the file system contents. Here, I saw the messages:
E: Unable to mount '/data'
E: Unable to mount ''cache'
E: Unable to mouth internal storage.
Your not S-Off. .You are S-On. You need to unlock your bootloader.. and then regain S-Off. Once S-Off there is no need to lock your bootloader to flash an RUU.
Sent from my GT-I9505 using XDA Premium 4 mobile app
bored_stupid said:
Your not S-Off. .You are S-On. You need to unlock your bootloader.. and then regain S-Off. Once S-Off there is no need to lock your bootloader to flash an RUU.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My bad. I am on S-ON. However, With me not being able to go anywhere except bootloader/recovery, should I go for S-OFF now?
I tried again to flash Maximus HD Rom (4.4.2). The AROMA installer completed its work and i tried rebooting. Same result. Back to Bootloader.
I saved the recovery log though. I've attached it here. But what was worrying is that it showed my /data and /external_sd as 0. Is that normal?
Any pointers here would be good.
Apart from help on that, I have one question: Would it be possible for me to achieve firewater S-OFF in this state?
The first step in firewater is to adb reboot. Seeing that I have no ROM to reboot into, would it work if I was doing it from recovery instead?
I don't know what other options I have.
Partition Logs:
/boot | /dev/block/mmcblk0p36 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p37 | Size: 15MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p37
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/system | /dev/block/mmcblk0p38 | Size: 2330MB Used: 1225MB Free: 1105MB Backup Size: 1225MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p38
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/cache | /dev/block/mmcblk0p39 | Size: 377MB Used: 6MB Free: 371MB Backup Size: 6MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p39
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/data | /dev/block/mmcblk0p40 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p40
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/external_sd | /dev/block/mmcblk1 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: SD Card
Storage_Name: SD Card
Backup_Path: /external_sd
Backup_Name: external_sd
Backup_Display_Name: SD Card
Storage_Path: /external_sd
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
/usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: USB OTG
Storage_Name: USB OTG
Backup_Path: /usb-otg
Backup_Name: usb-otg
Backup_Display_Name: USB OTG
Storage_Path: /usb-otg
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
I:Loading package: TWRP (/script/ui.xml)
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p40
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
E:Unable to mount /data/media during GUI startup.
YAAY! I did it.
I think changing recoveries did the trick.
I switched to CWM Touch from here : http://d-h.st/qls. Flashed on just the recovery.img
Then flashed SuperSu-1.94 (Just to make sure)
Installed Maximus HD 4.4.2 . And when I rebooted, I was welcomed with the HTC One logo!
PHEW.. I'm so glad that it started working again.
Hello. Three days ago i made a backup of vanir rom using cwm , then i flashed miui ( philz touch recovery) and now i cant restore my vanir backup, only system backup. I cant restore even from cwm. I guess backup is not corrupted , as it was made without problems and i didnt touched it. I also tried to mount /data ,format ..still fail to restore /data. I attached an recovery log.
Any idea? Thanks.
I saw that recovery log didnt got attached first time, so here is it : http://m.uploadedit.com/b044/1421324866971.txt .
Force said:
Hello. Three days ago i made a backup of vanir rom using cwm , then i flashed miui ( philz touch recovery) and now i cant restore my vanir backup, only system backup. I cant restore even from cwm. I guess backup is not corrupted , as it was made without problems and i didnt touched it. I also tried to mount /data ,format ..still fail to restore /data. I attached an recovery log.
Any idea? Thanks.
Click to expand...
Click to collapse
Try to flash some other kernel with CWM and do restore with it.
According to the recovery log, the backup is somewhat restoring to the wrong directory. Seems the data partition was corrupted before making the backup.
Code:
I:data/
I:data/lost+found/
I:data/lost+found/#16436/
I:data/lost+found/#16436/softap.conf
I:data/lost+found/#16436/p2p_supplicant.conf
I:data/lost+found/#16436/wpa_supplicant.conf
I:data/lost+found/#16436/entropy.bin
I:data/lost+found/#16440/
shut_down said:
Try to flash some other kernel with CWM and do restore with it.
Click to expand...
Click to collapse
Still fail. I also tried TWRP (it doesnt see my backup) and Philz recovery.
Jtfk said:
According to the recovery log, the backup is somewhat restoring to the wrong directory. Seems the data partition was corrupted before making the backup.
Code:
I:data/
I:data/lost+found/
I:data/lost+found/#16436/
I:data/lost+found/#16436/softap.conf
I:data/lost+found/#16436/p2p_supplicant.conf
I:data/lost+found/#16436/wpa_supplicant.conf
I:data/lost+found/#16436/entropy.bin
I:data/lost+found/#16440/
Click to expand...
Click to collapse
Damn
Anyway, i took a log with philz recovery too:
Code:
>> Restoring /data...
couldn't find old .img format
Found new backup image: /storage/sdcard1/clockworkmod/backup/2015-01-10.08.44.32//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Press Back to cancel.
tar: can't remove old file data/lost+found/#115233: Is a directory
Error while restoring /data!
press any key to continue.
I:skiping set_bootloader_message: no /misc
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Force said:
Still fail. I also tried TWRP (it doesnt see my backup) and Philz recovery.
Damn
Anyway, i took a log with philz recovery too:
Code:
>> Restoring /data...
couldn't find old .img format
Found new backup image: /storage/sdcard1/clockworkmod/backup/2015-01-10.08.44.32//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Press Back to cancel.
tar: can't remove old file data/lost+found/#115233: Is a directory
Error while restoring /data!
press any key to continue.
I:skiping set_bootloader_message: no /misc
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Click to expand...
Click to collapse
did you tried to flash kernel with which you made CWM backup ?
if not try it
and it seems your partitions are corrupt so 1st install stock firmware via odin and then flash kernel with which u made back and after that wipe "all" thingsand then restore backu
jineshpatel30 said:
did you tried to flash kernel with which you made CWM backup ?
if not try it
and it seems your partitions are corrupt so 1st install stock firmware via odin and then flash kernel with which u made back and after that wipe "all" thingsand then restore backu
Click to expand...
Click to collapse
I tried what you said and it didnt work. I guess there is nothing i can do...
Force said:
I tried what you said and it didnt work. I guess there is nothing i can do...
Click to expand...
Click to collapse
That's sad...take 3-4 hrs spare to setup entire settings n phone again -_-
Btw one suggestion from me...next time when you make backup (or one more backup) using "temporary cwm" by shaan it works over all roms and kernel.
jineshpatel30 said:
That's sad...take 3-4 hrs spare to setup entire settings n phone again [emoji14] -_-
Btw one suggestion from me...next time when you make backup (or one more backup) using "temporary cwm" by shaan it works over all roms and kernel.
Click to expand...
Click to collapse
Thanks for suggestion. By the way, my backup size was 2gb and i dont remember all my stuff
Hello,
I installed some ROMs and I believe I destroyed some partitions.
It would be great if someone could post their partitions info. This can be done by saving the recovery.log in TWRP to the sdcard. At the beginning there is a section "Partition Logs".
Mine currently looks like this:
Code:
Partition Logs:
/data | /dev/block/mmcblk0p38 | Size: 5637MB Used: 34MB Free: 2907MB Backup Size: 34MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p38
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media/0
Current_File_System: f2fs
Fstab_File_System: f2fs
Backup_Method: files
Mount_Flags=0x 0, Mount_Options=inline_xattr
MTP_Storage_ID: 65537
/cache | /dev/block/mmcblk0p35 | Size: 525MB Used: 8MB Free: 516MB Backup Size: 8MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p35
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/system | /dev/block/mmcblk0p36 | Size: 1086MB Used: 1054MB Free: 32MB Backup Size: 1054MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/boot | /dev/block/mmcblk0p31 | Size: 9MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p31
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p32 | Size: 10MB
Flags: IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p32
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/pds | /dev/block/mmcblk0p26 | Size: 3MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p26
Display_Name: PDS
Storage_Name: PDS
Backup_Path: /pds
Backup_Name: pds
Backup_Display_Name: PDS
Storage_Path: /pds
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: USB OTG
Storage_Name: USB OTG
Backup_Path: /usb-otg
Backup_Name: usb-otg
Backup_Display_Name: USB OTG
Storage_Path: /usb-otg
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
MTP_Storage_ID: 65538
/sdcard1 | /dev/block/mmcblk1p1 | Size: 3360MB Used: 0MB Free: 3360MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Display_Name: External SDCard
Storage_Name: External SDCard
Backup_Path: /sdcard1
Backup_Name: sdcard1
Backup_Display_Name: External SDCard
Storage_Path: /sdcard1
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
MTP_Storage_ID: 65539
I believe I messed something up here. I can't install any ROM. Because it can't mount /dev/block/platform/msm_sdcc.1/by-name/system and I get an error like this:
Code:
ioctl failure. errno 5
Code:
Installing '/sdcard/TitanPrimeROMv1.0.2-XT1068-69.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
installing gptupgrade updater extensions
format system
blk: partition "" size 1036288 not a multiple of io_buffer_size 524288
blk: partition "" size 2387968 not a multiple of io_buffer_size 524288
blk: partition "" size 1036288 not a multiple of io_buffer_size 524288
blk: partition "" size 1077248 not a multiple of io_buffer_size 524288
blk: partition "" size 10444800 not a multiple of io_buffer_size 524288
blk: partition "" size 10526720 not a multiple of io_buffer_size 524288
blk: partition "" size 560070656 not a multiple of io_buffer_size 524288
blk: partition "" size 5912788992 not a multiple of io_buffer_size 524288
blk: partition "" size 3530999808 not a multiple of io_buffer_size 524288
blk: partition "" size 512000000 not a multiple of io_buffer_size 524288
blk: partition "" size 32289792 not a multiple of io_buffer_size 524288
Attempting to mount /dev/block/platform/msm_sdcc.1/by-name/userdata as ext4
Failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data error Device or resource busy
Can't mount userdata partition for validating erase
Formatting partition /dev/block/platform/msm_sdcc.1/by-name/system of length 45000000 starting at 2a100000
Aligning offset to 400000 boundary by moving 300000 bytes
Failed to wipe /dev/block/platform/msm_sdcc.1/by-name/system partition. ioctl failure. errno 5
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/system failed
script aborted: assert failed: format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system")
assert failed: format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system")
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/TitanPrimeROMv1.0.2-XT1068-69.zip'
Error flashing zip '/sdcard/TitanPrimeROMv1.0.2-XT1068-69.zip'
Updating partition details...
I:Data backup size is 34MB, free: 2907MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
It would be great if somebody could post a valid partition info
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=428000k,nr_inodes=107000,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=428000k,nr_inodes=107000)
/dev/block/mmcblk0p38 on /data type f2fs (ro,seclabel,relatime,background_gc=off,user_xattr,inline_xattr,acl,errors=continue,active_logs=6)
/dev/block/mmcblk0p38 on /sdcard type f2fs (ro,seclabel,relatime,background_gc=off,user_xattr,inline_xattr,acl,errors=continue,active_logs=6)
/dev/block/mmcblk0p35 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (ro,seclabel,nodev,noatime,nodiratime,data=ordered)
XT1068 [5.0.2][OFFICIAL][XT1068]Lollipop Indian OTA Captured
Except data, system and sdcard1 (it is clear) is exactly what you got
Code:
Partition Logs:
/data | /dev/block/mmcblk0p38 | Size: 5637MB Used: 2730MB Free: 2425MB Backup Size: 2730MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p38
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media/0
Current_File_System: f2fs
Fstab_File_System: f2fs
Backup_Method: files
Mount_Flags=0x 0, Mount_Options=inline_xattr
MTP_Storage_ID: 65537
/cache | /dev/block/mmcblk0p35 | Size: 525MB Used: 8MB Free: 516MB Backup Size: 8MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p35
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/system | /dev/block/mmcblk0p36 | Size: 1086MB Used: 1049MB Free: 37MB Backup Size: 1049MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/boot | /dev/block/mmcblk0p31 | Size: 9MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p31
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p32 | Size: 10MB
Flags: IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p32
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/pds | /dev/block/mmcblk0p26 | Size: 3MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p26
Display_Name: PDS
Storage_Name: PDS
Backup_Path: /pds
Backup_Name: pds
Backup_Display_Name: PDS
Storage_Path: /pds
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: USB OTG
Storage_Name: USB OTG
Backup_Path: /usb-otg
Backup_Name: usb-otg
Backup_Display_Name: USB OTG
Storage_Path: /usb-otg
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
MTP_Storage_ID: 65538
/sdcard1 | /dev/block/mmcblk1p1 | Size: 7648MB Used: 4803MB Free: 2845MB Backup Size: 4803MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Display_Name: External SDCard
Storage_Name: External SDCard
Backup_Path: /sdcard1
Backup_Name: sdcard1
Backup_Display_Name: External SDCard
Storage_Path: /sdcard1
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
MTP_Storage_ID: 65539
Hi,
My J7 Prime G610F (Android 6.0.1) has a "Micro SDcard: 0MB" problem in TWRP (3.2.2). It's working fine in normal system but not in recovery.
My device is rooted, no-verity-opt.....6.0zip loaded. I checked the "last_log"
xxxxxxxxxxx
278. /external_sd | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: can_be_mounted can_be_wiped wipe_available_in_GUI Removable Is_Storage
primary_block_device: /dev/block/mmcblk1p1
Alternate_block_device: /dev/block/mmcblk1
display_name: Micro SDcard
storage_name: Micro SDcard
backup_path: /external_sd
backup_name: /external_sd
Backup_Display_Name: Micro SDcard
storage_path: /external_sd
Current_File_System: vfat
Fstab_file_System: vfat
Backup_Method: files
291. MTP_Storage_ID: 65538
xxxxxxxxxxx
Why TWRP think the SD Card is 0MB? In fact I don't think the problem is TWRP. Stock Recovery wasn't reach SD Card also.
note: My PC runing on XP Home Edition. The device system was Android 8.0 but downgraded to 7.0 and next 6.0.1.
Formatting the SD card to another format and back to fat32 didn't help.
Diskpart clean and format trick didn't help.
Please help. I'm tired.
Dude, If you had carefully checked the xda thread for G610x TWRP, you'd have known that this is a bug actually.
It's written as, Bug: Cannot mount External SD Card in TWRP.
So Use your internal storage to flash zips, files or the better option use OTG.
Thank you friend. I know that. But It was written that this was a bug of TWRP. At least in my case, maybe it's different. Because my phone cannot connect to SD card even without TWRP. The stock recovery giving "E:failed to mount /sdcard (No such file or directory)". This is not a TWRP bug. Isn't it?
SenTiKo said:
Thank you friend. I know that. But It was written that this was a bug of TWRP. At least in my case, maybe it's different. Because my phone cannot connect to SD card even without TWRP. The stock recovery giving "E:failed to mount /sdcard (No such file or directory)". This is not a TWRP bug. Isn't it?
Click to expand...
Click to collapse
I don't know about stock recovery but in G610f, all custom recoveries be it Orange fox , SHRP ,TWRP, etc has a SDCard bug.