Database Info

is it possible to recreate the Data partition ?

Hello everyone,
i bricked my a511 because i had the stupid idea to set go back factory defaults with the old cwm.
so, i know that the problem is the damaged data partition, is it possible to recreate this partition ?

I had the same Problem. I flashed a data.img. This works. you can even mount the system partition? and the cache?
The Fastboot commands are "fastboot flash userdata C:\[your path to the data.img]" and "fastboot flash system C:\[your path to the data.img]"
and "fastboot flash cache C:\[your path to the data.img]"
Webitu

No, it's not the partition that's damaged, but the NAND chip itself.

[Q] Sdcard became a file

my sdcard in root explorer became read only and a file and is now legacy. this first started when i tried to boot into TWRP 2.8 and did not boot so i tried to fastboot erase cache and that is when i had problems. I also don't have an IMEI number but i have a backup. TWRP can read the sdcard though

Try fastboot flashing the cache.img.

Wakamatsu said:
Try fastboot flashing the cache.img.
Click to expand...
Click to collapse
Fixed becasue i had a back up and just restored the cache and efs from another ROM

is the sdcard mounted in cache or something?

dirtbikerr450 said:
is the sdcard mounted in cache or something?
Click to expand...
Click to collapse
No but you mentioned that you erased the cache in fastboot. Normally, the cache should reformat. If it doesn't, you lose your cache file system. The phone is still useable but may exhibit odd behavior.

crombi-kk e: unable to mount /sd-ext data2sd with f2fs

Hello, I have an issue that will hopefully be resolved with some help from you guys.
I have a tf300t, a 64gb class 10 sandisk card, and I was running cromi 5.3 with data2sd before switching to crombi-kk. I used gparted and formatted the second partition on my microsd to fsfs. I then did the following to start fresh on the tablet
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
fastboot -i 0x0B05 reboot
I then flashed twrp 2.7.0.1 omni version from the link on the tf300t crombi-kk page.
I then installed crombi with data2sd with f2fs. I used that kernel. Install went fine and went to the wipe dalvik,home, buttons were at the bottom and it said updating partioning details or whatever.
It then said e:unable to mount /sd-ext and a bunch more e: ones. I rebooted and the penguins showed up and it said
Well I couldn't remember what the first one had said but the second said
Data on i/data on microsd for data2sd/rom2sd
/system on microsd for rom2sd
And it booted up normally and I setup crombi.
I now keep getting freezes and I find myself having to hit the power button and enter my pin. Sometimes I will get the message systemui has stopped or something, do you want to wait? Or something along those lines.. I guess the only thing I didn't do is factory reset before installing crombi-kk. I am going to reformat the f2fs partition on the microsd in gparted again, then I will do all of this
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
fastboot -i 0x0B05 reboot
And flashed twrp 2.7.0.1 omni version. Then factory reset. Should I have anything extra checked off in the advanced section of the factory reset page?
Then I will install crombi with data2sd option with f2fs and use _that kernel in the aroma installer.
I will report back
Thanks for the help!

[Q] Help i may have doomed my tablet.

So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.

supernova0 said:
So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.
Click to expand...
Click to collapse
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!

das chaos said:
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!
Click to expand...
Click to collapse
I was able to that, but the filesystem that I was using was f2fs so when I booted to the stockrom it said" encryption unsuccessful" so i had to format my data partition to a compatible format. so i flash twrp recovery, but I had the same problem, the screen flashes and then it stays at the twrp splash screen. then I thought it might be a problem with my data partition, so I erased my whole data partition using fastboot, with the command
fastboot format userdata
it worked and the recovery is working also, but my filesystem is on ext3 and I know ext 4 is better than ext 3, so using the twrp recovery I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.

supernova0 said:
..... I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.
Click to expand...
Click to collapse
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!

das chaos said:
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!
Click to expand...
Click to collapse
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.

supernova0 said:
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.
Click to expand...
Click to collapse
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.

das chaos said:
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.
Click to expand...
Click to collapse
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--

bretzke said:
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--
Click to expand...
Click to collapse
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh

lj50036 said:
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh
Click to expand...
Click to collapse
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1

bretzke said:
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1
Click to expand...
Click to collapse
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.

bretzke said:
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.
Click to expand...
Click to collapse
See you found your own answer and I like that ..... :good:
Thx Josh

Phone is Extremely Weirdly Bricked

So first, I transferred a file to my phone. I was quite low on storage (about 3 gb left) before the transfer, but the file was around 2.4gb, so it fit. I wanted to transfer that file to another computer, so when I plugged it in the other computer, a local disk drive shows up as opposed to mtp. I figure that it was probably a glitch. When I restart the phone, it boots, but instead of having 600 mb of free space left, it has 1134mb left. Somehow the available space just increased, so I decide to reboot again. The bootloader shows up, but then it simply goes to a black screen with no boot logo. When I plug my phone back into the computer, it opens 4 disk drive prompts saying I need to format the drive so that it can be used, and one that shows something. When I go in the "drive", there is one folder called image, and in the folder there is a bunch of files like modem.b00 as shown in the image attached..
It seems that instead of mounting the internal storage, it is mounting the firmware.
I am able to boot into recovery however, but nothing I have done seems to help. I have tried flashing several firmwares again with different recoveries (2.8.7.0.5 and 3.0.0) and restoring the efs partition again. I cannot delete any files off my phone through recovery as it yields an ERROR=1 and through MTP when I delete a file, it appears the file is deleted, but when I unplug and plug the phone back in, the file is back. I can however transfer files from my phone to the computer, but not vice versa.
It is also able to read but not write, meaning that my internal storage may be faulty, or that the file caused a corruption on my phone. If anyone has any ideas on how to fix it or has any experience with this, please let me know.

Can you access fastboot?
Sounds like it may be an issue with the userimage data try a reflash using the link below but edit the bat file (or .sh file) to only include the following line:
Code:
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
you can grab a zip with the entire OS here and you will need to setup fastboot drivers properly (which sounds like you would have already done)
Return OPO to 100% Stock

itechy said:
Can you access fastboot?
Sounds like it may be an issue with the userimage data try a reflash using the link below but edit the bat file (or .sh file) to only include the following line:
Code:
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
you can grab a zip with the entire OS here and you will need to setup fastboot drivers properly (which sounds like you would have already done)
Return OPO to 100% Stock
Click to expand...
Click to collapse
Yep, fastboot works and I already have the drivers set up. Do I only need to restore the userdata?

f41lbl0g said:
Yep, fastboot works and I already have the drivers set up. Do I only need to restore the userdata?
Click to expand...
Click to collapse
Flashing the userdata partition via fastboot will wipe all data so I hope you have your stuff backed up. Best solution now is to fastboot flash COS12.1.1 and see if it turns on
Sent from my A0001 using Tapatalk

Renosh said:
Flashing the userdata partition via fastboot will wipe all data so I hope you have your stuff backed up. Best solution now is to fastboot flash COS12.1.1 and see if it turns on
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm currently in the process of backing everything up, but can't I just format /data through recovery since TWRP works?
Tried flashing the userdata_64G.img, here is what I get:
C:\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.829s]
sending 'userdata' (56 KB)...
OKAY [ 0.016s]
writing 'userdata'...
FAILED (remote: Bogus size sparse and chunk header)
finished. total time: 3.860s

f41lbl0g said:
I'm currently in the process of backing everything up, but can't I just format /data through recovery since TWRP works?
Click to expand...
Click to collapse
You can try that but no guarantees it will work.
You can either wipe everything (/system /data /internal storage /cache and /dalvik) with advanced wipe for TWRP 2.8.6.0 (recommended version) then transfer the flashable version of COS12.1.1 from link below and flash
http://forum.xda-developers.com/showthread.php?t=2906746
Or you can fastboot flash the entire COS12.1.1 fastboot using commands manually from the previous link the other poster gave you. You will run into some problems if you decide you wanna try some AOSP ROMs after flashing the userdata from COS12.1.1 but if you stick to CM you'll be fine
Sent from my A0001 using Tapatalk

Renosh said:
You can try that but no guarantees it will work.
You can either wipe everything (/system /data /internal storage /cache and /dalvik) with advanced wipe for TWRP 2.8.6.0 (recommended version) then transfer the flashable version of COS12.1.1 from link below and flash
http://forum.xda-developers.com/showthread.php?t=2906746
Or you can fastboot flash the entire COS12.1.1 fastboot using commands manually from the previous link the other poster gave you. You will run into some problems if you decide you wanna try some AOSP ROMs after flashing the userdata from COS12.1.1 but if you stick to CM you'll be fine
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok I had to fastboot flash the entire COS2.1.1, and it is working well now. Why is there an issue with AOSP roms after flashing the userdata?

f41lbl0g said:
Ok I had to fastboot flash the entire COS2.1.1, and it is working well now. Why is there an issue with AOSP roms after flashing the userdata?
Click to expand...
Click to collapse
I don't know what is up with the userdata image for COS12.1.1 but its corrupted in some way and you cannot flash ROMs like Omni and OxygenOS. It acts as if you've encrypted the OS when you haven't, solution is to wipe using an older userdata partition like the one from COS12.1 or earlier.
Sent from my A0001 using Tapatalk

Renosh said:
I don't know what is up with the userdata image for COS12.1.1 but its corrupted in some way and you cannot flash ROMs like Omni and OxygenOS. It acts as if you've encrypted the OS when you haven't, solution is to wipe using an older userdata partition like the one from COS12.1 or earlier.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Do you have a link to an old userdata partition?

f41lbl0g said:
Do you have a link to an old userdata partition?
Click to expand...
Click to collapse
Sorry I don't you'll have to download from the link I shared earlier an entire fastboot zip to be able to do it
Sent from my A0001 using Tapatalk