I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
andreas1996 said:
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
Click to expand...
Click to collapse
Only one that can mount it will be twrp 2.7.1.1 (or the f2fs twrp released in dev)
If it has corrupted just format it back to ext4 and start again.
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Sent from my GT-I9505G using XDA Free mobile app
andreas1996 said:
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Click to expand...
Click to collapse
That's not a log, it's a screenshot. The log is in /tmp/recovery.log, so you can use adb pull to get it and post it. Or you can probably use the "copy log to SD card" option in the advanced menu.
Here is the log.I compressed the file because the log format is not supported to attachments.
andreas1996 said:
Here is the log.I compressed the file because the log format is not supported to attachments.
Click to expand...
Click to collapse
According to the log, your recovery can't access any partitions on your eMMC. To find out more, reboot to your recovery again and run on the connected PC:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
and read/post the resulting files.
Here is the two files your commands gave me
andreas1996 said:
Here is the two files your commands gave me
Click to expand...
Click to collapse
Your tablet's eMMC seems to have no partitions at all:
Code:
<6>[ 4.770320] mmcblk0: unknown partition table
What exactly did you do for "a F2FS conversion to Data Partition"? Did you format mmcblk0 instead of mmcblk0p8?
The only thing I did after f2fs conjversion is in Philz recovery I select wipe to install a new ROM.And the problem began.
andreas1996 said:
The only thing I did after f2fs conjversion
Click to expand...
Click to collapse
If you expect help, you need to answer my question. I did not ask what you did *after* the f2fs conversion - what exactly did you do to convert /data to f2fs?
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
andreas1996 said:
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
Click to expand...
Click to collapse
Friend! You got the attention of one of the few people who may be able to help you get your tab back! Use it!
Post DETAILED steps of what you did or _that is going to ignore you!
Which recovery and version thereof did you use?
What did you do afterwards? You mention 3 recoveries. Did you flash all of them?
What did you do in which order in each of them?
Provide as many details as you can!
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
Define "full wipe".
Which CROMi-X version did you try to flash?
Details, details....
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
sbdags said:
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
How would you format data without a data partition?
sbdags said:
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
andreas1996 said:
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
Click to expand...
Click to collapse
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
sbdags said:
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Click to expand...
Click to collapse
When I doing the command (make_ext4fs /dev/block/mmcblk0p8) I receive the message : Need size of file system.
Something seems to be wrong with your GPT. Unfortunately the busybox tools don't support big offsets to read it, so let's first see if the Tegra-specific partition table (which is not used by the kernel) is still there - that won't help you immediately but will show if the eMMC can be read at all and where the partitions are supposed to be. Post the output file of this command:
adb shell hexdump -s 0x300000 -n 2048 -C /dev/block/mmcblk0boot0 > pt.txt
Related
Hello guys,
being the ROM on my tablet the Cromi-x 5.2a, the whole thing started when I got a boot freezed on the boot animation after using the Xposed app (if I'm not confusing) to change something which I actually don't remember. Afterwards I read there was a bug which leaded to such problems so I reflashed the ROM and everything just worked fine.
Wanting to upgrade to the 5.2.4, with rom2sd and data2sd, I prepared my SD using Gparted as wonderfully described in other threads, I wiped everything to have a clean install, flashed it with the _thatv7 kernel, chosen the rom2sd option, and as a result (after some uncomfortable freezes in the aroma installer) when I prompted reboot on the TWRP at the end of the procedure the "No OS installed" warning appeared.
In fact no OS is booting, and after many attempts (the last of which includes the flash of the official firmware, as last try), my tablet stucks at the ASUS logo. I also reflashed the bootloader and the recovery by new.
I ask for help. Cannot post any logcat because it actually doesn't even begin the boot procedure.
Really thank you for all the job, and for your help in advance.
Feanob said:
Hello guys,
being the ROM on my tablet the Cromi-x 5.2a, the whole thing started when I got a boot freezed on the boot animation after using the Xposed app (if I'm not confusing) to change something which I actually don't remember. Afterwards I read there was a bug which leaded to such problems so I reflashed the ROM and everything just worked fine.
Wanting to upgrade to the 5.2.4, with rom2sd and data2sd, I prepared my SD using Gparted as wonderfully described in other threads, I wiped everything to have a clean install, flashed it with the _thatv7 kernel, chosen the rom2sd option, and as a result (after some uncomfortable freezes in the aroma installer) when I prompted reboot on the TWRP at the end of the procedure the "No OS installed" warning appeared.
In fact no OS is booting, and after many attempts (the last of which includes the flash of the official firmware, as last try), my tablet stucks at the ASUS logo. I also reflashed the bootloader and the recovery by new.
I ask for help. Cannot post any logcat because it actually doesn't even begin the boot procedure.
Really thank you for all the job, and for your help in advance.
Click to expand...
Click to collapse
Don't worry you are not bricked - you just have no OS on internal. ROM2SD boots need an OS on internal as well. You should have installed to interna first then reflash later with the ROM2SD version. When you wiped you wiped internal and then flashed ROM2SD - that is never going to work
Do this.
Either reflash CROMi-X as internal only or wipe data first then flash it. That should get you back up and running.
Also remember to turn on signature verification in TWRP first as you may also have a corrupted download which could be the cause of the issues you describe.
sbdags said:
Do this.
Either reflash CROMi-X as internal only or wipe data first then flash it. That should get you back up and running.
Also remember to turn on signature verification in TWRP first as you may also have a corrupted download which could be the cause of the issues you describe.
Click to expand...
Click to collapse
Thank you for the answer.
My signature verification was already turned on, and I fear I've already tried to flash to internal, having read in a previous post of yours how rom2sd works. Surprisingly I obtain the same result (no os installed).
Where are the boot information stored? Isn't the preinit code in the _that kernel writing in it? Couldn't I have corrupted something I shouldn't?
I thought that flashing the stock asus firmware would surely have fixed everything (and surely flash itself in the internal memory), but it gives me no OS installed as well! Maybe I messed up something in TWRP?
Bye
That sounds really strange. @_that any ideas?
sbdags said:
That sounds really strange. @_that any ideas?
Click to expand...
Click to collapse
("quite impolite answer" deleted, sorry, apparently OP knows exactly what he is doing)
With "everything" I mean everything I could select system, cache, internal storage, dalvik, data.
Quite impolite answer, anyway.
Anyway, you are basically right
Heeelp! My 650€ thing can only be used as a tray at the moment.
Try this - format data in TWRP, flash a rom (CROMi-X or STOCK - remember you flash the zip inside the zip if stock). What happens - does the flash complete? Error messages, where does it boot to?
Does TWRP indicate you have no OS installed? Do you have a nandroid of a good working setup? If not why not?
Go to TWRP, advanced, terminal emulator, select folder button. Type 'mount' what does it say about mmcblk0p8? What about 0p1 and 0p2?
WHat bootloader are you on? What version of TWRP?
etc etc etc. More details please.
sbdags said:
Try this - format data in TWRP, flash a rom (CROMi-X or STOCK - remember you flash the zip inside the zip if stock). What happens - does the flash complete? Error messages, where does it boot to?
Does TWRP indicate you have no OS installed? Do you have a nandroid of a good working setup? If not why not?
Click to expand...
Click to collapse
It's the last thing I've done, trying to flash the stock firmware (the zip inside the zip). The flash completes, no error messages. When trying to boot, it stucks on the ASUS logo (the one with "The device is unlocked" notice. TWRP indicates me "no OS installed", yes. Unfortunately no nandroid backup around, my mistake.
sbdags said:
Go to TWRP, advanced, terminal emulator, select folder button. Type 'mount' what does it say about mmcblk0p8? What about 0p1 and 0p2?
Click to expand...
Click to collapse
/dev/block/mmcblk0p8 on /data type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
/dev/block/mmcblk0p2 on /cache type ext4 (rw, relatime, user_xattr, acl, barrier=1)
Actually nothing on 0p1.
sbdags said:
WHat bootloader are you on? What version of TWRP?
Click to expand...
Click to collapse
Bootloader: 10.6.1.14.10
TWRP: v2.6.1.0
Anyway, this evening I'll retry to flash.
In my pure ignorance... isn't there a way to reflash the boot image?
Feanob said:
It's the last thing I've done, trying to flash the stock firmware (the zip inside the zip). The flash completes, no error messages. When trying to boot, it stucks on the ASUS logo (the one with "The device is unlocked" notice. TWRP indicates me "no OS installed", yes. Unfortunately no nandroid backup around, my mistake.
/dev/block/mmcblk0p8 on /data type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
/dev/block/mmcblk0p2 on /cache type ext4 (rw, relatime, user_xattr, acl, barrier=1)
Actually nothing on 0p1.
Bootloader: 10.6.1.14.10
TWRP: v2.6.1.0
Anyway, this evening I'll retry to flash.
In my pure ignorance... isn't there a way to reflash the boot image?
Click to expand...
Click to collapse
You sure about this one
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
According to that you no longer have a system partition.....
Can you also provide the recovery log from twrp after flashing stock - its in the advanced menu. You can also flash the boot loader from my CROMi-X thread.
sbdags said:
You sure about this one
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
Click to expand...
Click to collapse
/sdcard is /data/media, so it's plausible that it's the same partition.
sbdags said:
According to that you no longer have a system partition.....
Click to expand...
Click to collapse
AFAIR it's not mounted by default.
_that said:
/sdcard is /data/media, so it's plausible that it's the same partition.
AFAIR it's not mounted by default.
Click to expand...
Click to collapse
Ah of course
sbdags said:
You sure about this one
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw, relatime, user_xattr, acl, barrier=1, data=writeback)
Click to expand...
Click to collapse
Yes.
sbdags said:
You can also flash the boot loader from my CROMi-X thread.
Click to expand...
Click to collapse
My bootloader comes from there.
Solved
I finally recovered my tablet by doing as written here, running a check disk... After that I reflashed stock firmware. TWRP said still "no OS installed" but after rebooting it actually behaved differently as previously, taking much more time to load the blue bar and eventually booting the OS.
Anyway thanks for the help.
Moderator Notes: I was asked to sticky this thread as it seems to be a recurring issue and a couple of fixes are in the posts.
Sorry my bad english am latin.
Hi guys first thread here and i need your help. Here s the thing, i was using my tf700, browsering, and the tablet goes off, i tried start up and a bootloop appears. So i go to Recovery (latest TWRP) and i tried to flash a ROM (latest crombi kk), like always i tried to wipe cache and dav bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening, i never had troubles with the tablet. So i tried to get fastboot mode and run the fastboot erase cach command (i read in a forum dat some guy did that and work for him), so i download the adb fastboot files, i connect the tf700 to my laptop (windows 7 64bit) and a installing drivers message and i wait and the driver that is called Transformer did not install, i dont know where to get those drivers, i found a file Asus usb drivers and bla bla but when i unzip the file i get 3 folders and no .exe or installer. So i tried to continue and i enter fastboot mode in the tablet and connect usb tablet-pc, and now another driver installing message appears, now is a driver called Fastboot, so i wait anda again the driver did not install correctly. So i continue and open cmd and tried the comman for erase cache, and only appears the WAITING FOR DEVICE text. i donw know waht to do, i also tried flashing again a ROM, bt only bootloop, trie again to wipe cache and dav but is only unable to mount /data. Any ideas ????
formobicho said:
Sorry my bad english am latin.
Hi guys first thread here and i need your help. Here s the thing, i was using my tf700, browsering, and the tablet goes off, i tried start up and a bootloop appears. So i go to Recovery (latest TWRP) and i tried to flash a ROM (latest crombi kk), like always i tried to wipe cache and dav bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening, i never had troubles with the tablet. So i tried to get fastboot mode and run the fastboot erase cach command (i read in a forum dat some guy did that and work for him), so i download the adb fastboot files, i connect the tf700 to my laptop (windows 7 64bit) and a installing drivers message and i wait and the driver that is called Transformer did not install, i dont know where to get those drivers, i found a file Asus usb drivers and bla bla but when i unzip the file i get 3 folders and no .exe or installer. So i tried to continue and i enter fastboot mode in the tablet and connect usb tablet-pc, and now another driver installing message appears, now is a driver called Fastboot, so i wait anda again the driver did not install correctly. So i continue and open cmd and tried the comman for erase cache, and only appears the WAITING FOR DEVICE text. i donw know waht to do, i also tried flashing again a ROM, bt only bootloop, trie again to wipe cache and dav but is only unable to mount /data. Any ideas ????
Click to expand...
Click to collapse
More likely your data partition got corrupted.
Try wiping it or formatting /data in TWRP to see if that helps? You will lose everything if you don't have backups.
sbdags said:
More likely your data partition got corrupted.
Try wiping it or formatting /data in TWRP to see if that helps? You will lose everything if you don't have backups.
Click to expand...
Click to collapse
i already tried that, wiping (cache, dav, system, ata, factoty reset) anything gives the unable to mount /data error.
formobicho said:
i already tried that, wiping (cache, dav, system, ata, factoty reset) anything gives the unable to mount /data error.
Click to expand...
Click to collapse
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
sbdags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
first of all is an honor chat with the legend sbdags!!! second can u guide me step by step. i did enter in twrp and go to advanced then terminal command then a selection menu appear and said browse to starting folder and a list of folder appears and a botton with Select Folder, wich folder i must select now? i tried just hit the select folder button and then i put the command taht u said and in the terminal said mke2fs 1.41.14 (22-dec-2010) nothing more and nothing happen
sbdags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Thank you so much sbdags.
You're a life save thought I had softbricked my tf700
Muchas gracias
formobicho said:
first of all is an honor chat with the legend sbdags!!! second can u guide me step by step. i did enter in twrp and go to advanced then terminal command then a selection menu appear and said browse to starting folder and a list of folder appears and a botton with Select Folder, wich folder i must select now? i tried just hit the select folder button and then i put the command taht u said and in the terminal said mke2fs 1.41.14 (22-dec-2010) nothing more and nothing happen
Click to expand...
Click to collapse
Did you unmount data first?
---------- Post added at 07:25 AM ---------- Previous post was at 07:24 AM ----------
chukkie said:
Thank you so much sbdags.
You're a life save thought I had softbricked my tf700
Muchas gracias
Click to expand...
Click to collapse
You are welcome!
EDIT - somehow the format finally took.. after 5 or 6 reboots.. very strange
okay, i hate to bump this thread. but i have been searching for a few nights and i cannot find a solution. i am having the same problem as OP.
Essentially, my tablet was interrupted mid format. I believe my data partition is corrupted. I can access recovery/fastboot and the tablet accepts commands from my PC. i have TWRP 2.7.1.1 on the tablet right now.
i tried what sdbags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
this did not work. i got the same "mke2fs 1.41.14 (22-dec-2010)" output, and then the tablet rebooted back into TWRP over again. (data was not mounted, i cannot mount it at all)
some more output from my tablets TWRP console:
Code:
e:could not mount/data and unable to find crypto footer.
e:unable to mount '/data'
e:unable to recreate /data/media folder/
updating partition details...
e:unable to mount '/data'
e:unable to mount internal storage.
e:unable to mount /data/media during gui startup
full selinux support is present.
e:unable to mount /data/,edia/twrp/.twrps when trying to read settings file.
e:unable to mount '/data'
is there another way to fix my corrupted partition?
this did not work. i got the same "mke2fs 1.41.14 (22-dec-2010)" output, and then the tablet rebooted back into TWRP over again. (data was not mounted, i cannot mount it at all)
Click to expand...
Click to collapse
I have exactly same situation
edit: after running this command
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
it prompt
Starting Path : /external_sd
Click to expand...
Click to collapse
and there is also button "KILL" when I hit enter it prompt : /dev/block/mmcblk0p8 is appereatly in use by the system: Will not make a file system here!
Any advice? (sry for being this big noob!)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Wouw thanks for so fast reply :highfive:.
But I think I'll disepoint you "usb debugging is disabled"
---------------------------------------------------------------------------------------------------------------
Any way I can reinstall stock from fastboot? damn it......
brinza said:
Wouw thanks for so fast reply :highfive:.
But I think I'll disepoint you "usb debugging is disabled"
---------------------------------------------------------------------------------------------------------------
Any way I can reinstall stock from fastboot? damn it......
Click to expand...
Click to collapse
No idea how when and after what exactly but the installation of stock rom started by itself after couple of reboots and couple of command i tried. (I had a file : US_epad-user-10.6.1.14.10.zip on my SD card
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Probably a Bad Idea - you should unmount /data before formatting. Then it should also not hurt to keep the recovery running.
Unbrick my TF 700t
Accidentally, bricking my tablet
I try Advance and Terminal Command with TRWP at tablet, it did not work
but when I try with command from PC (desktop), it works like a charm. I was able to see internal storage
from that just re install Custom ROM. Thank alot to sdbag
Thanks
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Wow. you are a life saver. that worked for me.
player50 said:
Wow. you are a life saver. that worked for me.
Click to expand...
Click to collapse
Glad it worked. Everyone should keep those commands handy
Thanks a lot...
After a long research I have found your thread.
I have almost given up looking for this damn issue...
At last, It became real! You are a real life saver.
sbdags help!
1) i dont know how to unmount data .
2) when i click advanced then terminal command it opens- Browse to starting folder and gives the file manager kind of view.
3) so i tried using adb on computer
the first three command work(i think but the third gives this error not enough space) .
please suggest a solution. thank you in advance
device moto g xt1033
i tried downgrading from lollipop 5.0 brasilian to kitkat but it wont go past warning bootloader unlocked screen. when i flash cm from twrp, it gives 3 errors
E:/ unable to mount '/data'
E:/ unable to mount '/cache'
E:/ unable to mount internal storage
then when i start it just keeps on loading on cm logo
should i create a separate thread for all this?
'
SemiNoob314 said:
1) i dont know how to unmount data .
2) when i click advanced then terminal command it opens- Browse to starting folder and gives the file manager kind of view.
3) so i tried using adb on computer
the first three command work(i think but the third gives this error not enough space) .
please suggest a solution. thank you in advance
device moto g xt1033
i tried downgrading from lollipop 5.0 brasilian to kitkat but it wont go past warning bootloader unlocked screen. when i flash cm from twrp, it gives 3 errors
E:/ unable to mount '/data'
E:/ unable to mount '/cache'
E:/ unable to mount internal storage
then when i start it just keeps on loading on cm logo
should i create a separate thread for all this?
'
Click to expand...
Click to collapse
Question: Why don't you care to read the short thread from beginning?
das chaos said:
Question: Why don't you care to read the short thread from beginning?
Click to expand...
Click to collapse
i am really sorry if the earlier comment came out as rude.
actually i did all of those steps, using the command terminal, using adb from pc but none of them worked, all of them had some problem
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
I woke up to find my 1st Generation Moto G battery was depleted and on charging it a bit., I switched it on only to find it optimizing my apps. All these (battery getting depleted, app optimization) happen all the time and I wasn't the least worried.
I picked up my phone later thinking it must have been done with the app optimization only to discover it was totally dead while still connected to a power bank. When I try to switch it on, it is stuck on the "Unlock Bootloader" page. I have tried flashing a new stock rom and it does not work.
I attached the image I see when I try to use recovery to wipe. Basically, nothing works. Can anybody help as I just fixed the screen and also out of warranty?
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks lost101, I do know how to flash perfectly well with fastboot. The problem is it flashes successfully but the phone is still stuck on the Bootloader.
I get this particular message on my recovery when I try to wipe either userdata or cache.
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /userdata failed
formatting cache
and
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /cache
wiping clogo
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
lost101 said:
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
Click to expand...
Click to collapse
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
NaijaAndroid said:
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
Click to expand...
Click to collapse
Read again what I told you to do. I did not say for you to flash anything.
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Thanks.
NaijaAndroid said:
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Click to expand...
Click to collapse
Via PC, do the following wipe: (requires working ADB setup)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
You could then TWRP > Wipe > Format Data > Yes, and try flashing a custom ROM.
Edit: You should backup photos or important data before hand.
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Edit: I have done it.
NaijaAndroid said:
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Click to expand...
Click to collapse
Recovery mode ADB will work with Linux - unsure about Windows. You could boot into an Ubuntu LiveCD (without installing) and transfer the ROM to phone that way. Otherwise, an OTG usb pen would be another option.
adb push rom.zip /sdcard
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
NaijaAndroid said:
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
Click to expand...
Click to collapse
Try sideloading the ROM.
TWRP > ADB sideloadadb sideload rom.zip
lost101 said:
Try sideloading the ROM.
TWRP > ADB sideloadadb sideload rom.zip
Click to expand...
Click to collapse
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
So sorry for taking your time. Thanks.
NaijaAndroid said:
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
Click to expand...
Click to collapse
Try a CM13 ROM.
lost101 said:
Try a CM13 ROM.
Click to expand...
Click to collapse
Same problem as above. I got the same message.
On PC:
adb shelle2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
lost101 said:
On PC:
adb shelle2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
NaijaAndroid said:
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
Click to expand...
Click to collapse
TWRP > MOUNT > Untick /Data
lost101 said:
TWRP > MOUNT > Untick /Data
Click to expand...
Click to collapse
got this after unticking data and trying again:
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
NaijaAndroid said:
got this after unticking data and trying again:
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
Click to expand...
Click to collapse
A certain percentage of phones end up with corrupt emmc (internal storage) over time. This problem is a fairly common thing. I do recall someone managing to boot an use CM13, despite the read-only userdata. I'm guessing they must have flashed it via TWRP, with the ROM.zip on an OTG usb pen. It may have worked because /system was still partially / fully writeable.
Hello!
Recently I recevied "Encryption Unseccesful" message on my phone. I tried to restore backup, but twrp says: "failed to mount /data". So, internal storage is dead. Found this. But cant find "repartition" menu in the cwm.
Questions is:
1. Do I need older versions of cwm to repartition sdcard? (If you have one, please share )
2. Is there any ways of recovering phone?
Thanks in advance!
no, just go to TWRP, Wipe, Format internal sdcard
sandpox said:
no, just go to TWRP, Wipe, Format internal sdcard
Click to expand...
Click to collapse
tried this, but I think internal storage is corrupted. Is there a way to use sdcard as internal storage?
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
I made 2 partitions on sd:
4gb fat32
4gb ext4
But I cant bind /data to this ext4 partition. Can you help, please?
What i did:
With TWRP's terminal:
Code:
mount -t ext4 /dev/block/mmcblk1p2 /data
- Invalid argument (dunno why)
Code:
ln -s /dev/block/mmcblk1p2 /data
- but on phone boot i receive same "encryption unsuccesful" screen.
Edited /etc/fstab - same result.
Files and mount after reboot turn back to its previous condition.
Also installed stock ROM - same message screen.
[/QUOTE]
I got advice that i must do this things with init.d scripts. How can I do this? Already tried "xda's app2sd scripts" but they works if phone completely boots in OS.
remosam said:
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
Click to expand...
Click to collapse
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
blind_aquila said:
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
Click to expand...
Click to collapse
asked sostk or noname
@blind_aquila
try to flash stock rom with odin