After an unfortunate restart yesterday from a misbehaving app, my phone has decided that the whole of the userdata partition is going to be read-only. At the very least, it's stopping me, fastboot, adb, and even the home launcher (when it boots) from running anything. Here's a video of the crash: http://youtu.be/8orBg5ivxsQ?t=1m3s
Now I've spent hours trawling through the various threads, and the ones that has got me closest to anything useful has been this one:
XDA Nexus 5 - [HOWTO][GUIDE] Repairing corrupted /data partition
Now the commands work well, and I have a list of the Moto G (16gb version) superblocks here:
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,relatime,background_gc=on,discard,user_xattr,inline_xattr,acl,errors=recover,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=writeback)
/dev/block/platform/msm_sdcc.1/by-name/fsg on /fsg type ext4 (rw,seclabel,nodev,noatime,nodiratime)
/dev/block/platform/msm_sdcc.1/by-name/modem on /firmware type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/persist on /persist type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
Running e2fsk works on all but the userdata superblock, which is the one I cannot write to. It fails with the message
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: e2fsck -b 8193 <device>
Clearly I can't e2fsck the f2fs partition (and I have no fsck), does anyone have any suggestions?
----
Tried and failed:
Nandroid restore (none found and can't write a new one to storage)
ADB Shell reading/deleting anythign from /data/media/0/
fasboot flash *anything*
mfastboot flash *anything*
Enter Bootloader screen (power on with vol down held)
Option (1) - Try flashing the gpt.bin included in the Motorola Firmware Image. Fastboot command:
fastboot flash partition gpt.bin
Option (2) - Flash the entire firmware image by following this tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
NB. fastboot erase userdata - will wipe all photos, music etc. Linux and some versions of windows will give you access to ADB in Custom Recovery. From there you can backup photos / internal storage by running the command: adb pull /sdcard/ C:/motog/
Tell me what model you have and I can link you to the Motorola Firmware Image.
Thanks.
Running Option (1) gives me the messages "(bootloader) Preflash verification failed" and "FAILED (remote failure)" in cmd, and the error version downgraded for primary_gpt on the phone screen. I have also attempted Option 2, but again that apparently has no effect. Even flashing a different recovery image (CWM, TWRP, Stock) does not change anything.
Even something simple like running a nandroid backup command fails through recovery- hence me thinking that the partition has gone read-only.
The model is a 16gb UK XT1032.
You need to use a 4.4.4 firmware image. See the FAQ regarding 'Preflash verification failed.'
Retail UK 4.4.4:
http://forum.xda-developers.com/showthread.php?p=54872143
I downloaded the firmware file (you're correct, I was probably previously using a 4.3 image) and tried to flash it using both fastboot and mfastboot.
Despite both methods giving no errors, it has absolutely no effect on the recovery, or once the phone boots (still the same wallpaper that I can see through the lockscreen before I unlock it and everything crashes).
Here's a video of it crashing, just for reference (note that xposed is clearly installed, but flashing the 'remove xposed' zip also does nothing): http://youtu.be/8orBg5ivxsQ
Are you using fastboot or mfastboot? What commands have you used? Do the 'flash system system.img' commands actually match the filenames of the firmware you have downloaded?
I have tried both actually. Here's the log from using mfastboot but it's the same for both. No errors reported in cmd or on the phone, but it doesn't make any actual changes to anything. Bizarre.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot is not user-friendly because it is meant for use by engineers. You will not be given helpful error messages. Please see this related post about the danger of misusing fastboot: http://forum.xda-developers.com/showpost.php?p=56123415&postcount=23
Try all three versions of fastboot in this zip: https://www.androidfilehost.com/?fid=23578570567719065
To be clear, here is the full list of required Fastboot commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
NB. Are system.img_sparsechunk.0 / .1 / .2 the actual file-names? Some firmware images include a forth sparsechunk.
I have not knowingly run fastboot erase all (I didn't know that was a command actually, perhaps for the best).
I can confirm that the commands I am running are exactly as you suggest, and with all the correct files. I have written three different .bat files not that I can run from from the command line, using fastboot, mfastboot and fastboot-moto-windows.
No luck unfortunately, despite the positive messages from cmd and the bootloader.
Have you tried converting 'userdata' to ext4 and back to f2fs in custom recovery?
TWRP > Wipe > Advanced > Repair > select 'data' - then choose repair
Afterwards reflash sparsechunks if necessary.
I'm using Philz custom recovery, but I have found a similar option.
I have tried turning on the f2fs <-> ext4 option in Custom Recovery Options and run it on /data and /data/media.
Selecting etx4 the first time, no effect.
Selecting f2fs the second time, no effect.
(despite both times it saying it had succeeded)
Silently said:
I'm using Philz custom recovery, but I have found a similar option.
I have tried turning on the f2fs <-> ext4 option in Custom Recovery Options and run it on /data and /data/media.
Selecting etx4 the first time, no effect.
Selecting f2fs the second time, no effect.
(despite both times it saying it had succeeded)
Click to expand...
Click to collapse
hi
I have my moto g doing the exact same thing as yours in your video I cant even flash a custom recovery to mine if I flash anything it says its completed but its done nothing completely read-only your the only person ive found on the net with the same problem as me.
Have you got any where with your G?
thanks
Skinpipe said:
hi
Have you got any where with your G?
thanks
Click to expand...
Click to collapse
No luck, I'm afraid.
Silently said:
No luck, I'm afraid.
Click to expand...
Click to collapse
I have same issue. Hard reset/ wiped many times but it goes back to same screen. Ask same password (I know password) but when I type password it keep on crashing on each and every program. Also when I do repair file system it just keep on repairing. Any help??
talkways said:
Also when I do repair file system it just keep on repairing. Any help??
Click to expand...
Click to collapse
From what I understand, the actual memory of the phone has become corrupted (a bit like when a memory stick formats itself as RAW) and there's no way to fix it.
If memory is corrupted, it should not load Android operating system at all. :S
Any more advices??
Silently said:
From what I understand, the actual memory of the phone has become corrupted (a bit like when a memory stick formats itself as RAW) and there's no way to fix it.
Click to expand...
Click to collapse
I've exactly the same problem with my XT1032 4.4.4. No solution yet
talkways said:
If memory is corrupted, it should not load Android operating system at all. :S
Click to expand...
Click to collapse
Well that's a damn good point. I assume it is something to do with the block structure of the underlying file system then, and it is something there which is preventing disk writes.
Good. We figured out the problem. Any solution??
I have tried many recoveries but it goes to standard recovery. Only way to go to custom recovery is boot via command fastboot boot recovery.img.
Device bootloader is unlocked.
Hi, anyone fixed the problem? This happened to my wife's phone few days ago.
Bootloader unlocked
Recovery TWRP
rom Paranoid (based on 4.4.4 android)
please help
Related
So it has become prudent to me that I update this info to the general public within the home of our One SV. Most of you may already be aware of the recent OTA Enhancement that the k2_cl has been receiving or already received. I have just learned after trying some modifications within my device that some commands were changed. I have not been able to figure out what all commands have been changed however one that I am aware of and the very one I constantly use as a safety hazard on my own device is booting vice flashing while in fastboot usb. Originally you all may have known the command to be fastboot boot recovery recovery.img (as an example). Its common for people to flash being the command: fastboot flash recovery recovery.img. As for me I ALWAYS BOOT before I flash to insure it's integrity while operating on my device. Thank of it as running within a virtual window to dumb this down for the less understanding individuals. Back on track, this command has been changed. fastboot boot boot boot.img (as an example) no longer works. They changed the command to: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img. That code functions respectively no different than as we would use to type: fastboot boot recovery customrecovery.img. Why they made such changes I am not sure. So be cautious of these changes. I made this thread to all who may come to learn about other changes with other commands and if so then please come back here and shar this knowledge as it will be VERY USEFUL TO US ALL. Thanks.
EDIT:
"fastboot boot" command DOESN'T work with the recent 4.1.2 OTA enhancement so you need to SPECIFY a kernel commandline to use "fastboot boot" command.
A list of commands with a quick summary on them.
/boot
This is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
As the name suggests, this partition contains the entire Android OS, other than the kernel and the ramdisk. This includes the Android GUI and all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
This is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it.
/data
Again as the name suggest, it is called userdata partition. This partition contains the user’s data like your contacts, sms, settings and all android applications that you have installed. While you are doing factory reset on your device, this partition will wipe out, Then your device will be in the state, when you use for he first time, or the way it was after the last official or custom ROM installation.
/cache
I hope you have some idea about cache, as you are expert on internet browsing. This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip flashall flash boot + recovery + system flash <partition> [ <filename> ] write a file to a flash partition erase <partition> erase a flash partition getvar <variable> display a bootloader variable boot <kernel> [ <ramdisk> ] download and boot kernel flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it devices list all connected devices continue continue with autoboot reboot reboot device normally reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache -s <serial number> specify device serial number -p <product> specify product name -c <cmdline> override kernel commandline -i <vendor id> specify a custom USB vendor id -b <base_addr> specify a custom kernel base address -n <page size> specify the nand page size. default:
Edit
---------- Post added at 06:30 PM ---------- Previous post was at 06:21 PM ----------
V1sual1mpact said:
That code functions respectively no different than as we would use to type: fastboot boot recovery customrecovery.img.
EDIT:
"fastboot boot" command DOESN'T work with the recent 4.1.2 OTA enhancement so you need to SPECIFY a kernel commandline to use "fastboot boot" command.
Click to expand...
Click to collapse
The correct cmd to boot a recovery.img before flashing is :
Code:
fastboot boot recovery.img
NOT fastboot boot recovery recovery.img
:thumbup:
russellvone said:
Edit
---------- Post added at 06:30 PM ---------- Previous post was at 06:21 PM ----------
The correct cmd to boot a recovery.img before flashing is :
Code:
fastboot boot recovery.img
NOT fastboot boot recovery recovery.img
:thumbup:
Click to expand...
Click to collapse
Actually, the command I gave is also correct (it's based on optional command) . But thanks for the input. The command has always been the command which I used. However, since that OTA I can not use it anymore.
help
V1sual1mpact said:
Actually, the command I gave is also correct (it's based on optional command) . But thanks for the input. The command has always been the command which I used. However, since that OTA I can not use it anymore.
Click to expand...
Click to collapse
OK, so I'm a bit confused here....What would be the proper command line to actually flash custom recovery....I keep getting an unknown error message using fast flash recovery custom recovery.img...
Rename the recovery.img to recovery.img.
Code:
fastboot flash recovery recovery.img
http://forum.xda-developers.com/showthread.php?p=47471643
Sent from my C525c using XDA Premium 4 mobile app
Hi, I want to (re-)flash the stock 4.1.2 rom on my Photon Q, because I recently run into some problems of the phone sending messages to the number 8737 even after I had removed the stock sms app.
This should be the right rsd file:
Code:
asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (MD5: 88f43a03d313bbcc262db78f15ac957c)
I'm on linux and I don't have any Windows system I could install and run RSDLite on. So I decided to take the fastboot way: I unzipped the above file and tried flashing the rom manually. But I always run in to the following error output:
Code:
# fastboot flash cdrom cdrom
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 22923264 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Note that "fastboot devices" lists the Photon Q as "T069503UAP fastboot". The same or a similar error messages applies to "fastboot flash system system.img" etc. I use fastboot from the Fedora 20 "android-tools" package (version 20130123git98d0789-2).
Any ideas what's the problem here? Solution?
Thanks in advance!
It's dangerous to try and fastboot the items yourself. Would be better to borrow a Windows PC or something to use RSD (virtual machines are also NOT recommended for this).
But perhaps you should just try to fastboot the other partitions. Not sure 'cdrom' is needed. Either way, I strongly, STRONGLY advise against doing what you are doing.
Okay, thanks for your advice!
The same or similar error messages appear when flashing the other partitions (as already mentioned in the first post). Unfortunately, it's really hard to find somebody with a Windows system, at the moment. I thought RSDLite uses fastboot internally anyway.
I'm not sure if the FXZ images can be flashed as they are, via fastboot.
I believe they should be converted to the standard ext4 format via the simg2img.py pytoon script, before being usable.
I repeat I'm not sure, but I believe that hardly motorola's own format is handled correctly by the fastboot command.
Whatever, for your convenience, I attach the mentioned converter script.
Aside fastboot, can be used for a variety of other purposes, the ext4 images can be mounted straight in Linux via loopback device or extracted in windows with a bunch of tools, personally I use Ftk Imager.
Thanks, that tool is great! After conversion, I was indeed able to mount the system partition as follows:
Code:
# mount -o ro,loop system_converted.img /some/mnt/path
But it doesn't help with the other files (cdrom, boot.img, recovery.img), because they seem to have a different format. However, the system partition was all I wanted. Now, instead of reflashing, I'm going to compare the system partition's files (especially in the "app" folder) and see what might have caused my problem.
tuxor1337 said:
But it doesn't help with the other files (cdrom, boot.img, recovery.img),
Click to expand...
Click to collapse
The boot, recovery and similar partitions aren't written on top of a filesystem like /system or /data.
they are written as they are on top of the physical media.
you can safely flash them in any way: fastboot, restore by recovery and so on.
unlike the filesystem based partitions, they are always in the same format.
If you need to edit the boot or recovery content you need a special script to unpack and repack them, many android kitchens have it
I was just wondering whether flashing on Linux will work when using "moto fastboot" like this one: http://forum.xda-developers.com/showthread.php?t=1138092
I don't really need this functionality anymore. But out of curiosity: What do you think?
My photon has a broken USB connector, so I can't test it in first person.
Btw, I believe that testing is the only way to understand what is flashable and what not, obviously taking handy a good full nandroid backup.
Hi guys. I've been struggling with going back to stock for ages... Been flashing different firmware like 100 times... But always get the same error: "max_sparse_size 256Mb"... Or something like that... It happens when I flash system bits through fastboot or mfastboot. My model is 1032 UK unlocked. On CM snapshot at the moment. If anyone has managed to break through this problem, please help me. Thanks in advance.
Sent from my HTC One_M8 using Tapatalk
ekabon said:
Hi guys. I've been struggling with going back to stock for ages... Been flashing different firmware like 100 times... But always get the same error: "max_sparse_size 256Mb"... Or something like that... It happens when I flash system bits through fastboot or mfastboot. My model is 1032 UK unlocked. On CM snapshot at the moment. If anyone has managed to break through this problem, please help me. Thanks in advance.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Try this with mfastboot (not the normal one).
mfastboot format system
mfastboot format userdata
mfastboot format cache
or
mfastboot format /system
mfastboot format /userdata
mfastboot format /cache
If nothing happens or it says the path is incorrect use these
mfastboot format /dev/block/platform/msm_sdcc.1/by-name/system
mfastboot format /dev/block/platform/msm_sdcc.1/by-name/userdata
mfastboot format /dev/block/platform/msm_sdcc.1/by-name/cache
If you succeed doing this, then try flashing stock 4.4.2 via the normal procedure and see what heppens.
liveroy said:
Try this with mfastboot (not the normal one).
mfastboot format system
mfastboot format userdata
mfastboot format cache
or
mfastboot format /system
mfastboot format /userdata
mfastboot format /cache
If nothing happens or it says the path is incorrect use these
mfastboot format /dev/block/platform/msm_sdcc.1/by-name/system
mfastboot format /dev/block/platform/msm_sdcc.1/by-name/userdata
mfastboot format /dev/block/platform/msm_sdcc.1/by-name/cache
If you succeed doing this, then try flashing stock 4.4.2 via the normal procedure and see what heppens.
Click to expand...
Click to collapse
Thanks for your time will do in a bit
Sent from my HTC One_M8 using Tapatalk
ekabon said:
Thanks for your time will do in a bit
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Now I`ve also notice you got error when flashing the /system
It could be that you input wrong filename, because most guides I've seen are okay but ppl copy-paste the commands w/o even checking the actual file names of the chunk files.
For most 4.4.x stock roms these are:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
and in the guides they are:
system.img_sparsechunk.1 or system.img_sparsechunk1
system.img_sparsechunk.2 or system.img_sparsechunk2
system.img_sparsechunk.3 or system.img_sparsechunk3
which will cause the fastboot to always spit an error on first one.
liveroy said:
Now I`ve also notice you got error when flashing the /system
It could be that you input wrong filename, because most guides I've seen are okay but ppl copy-paste the commands w/o even checking the actual file names of the chunk files.
For most 4.4.x stock roms these are:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
and in the guides they are:
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
which will cause the fastboot to always spit an error on first one.
Click to expand...
Click to collapse
ekabon said:
Thanks for your time will do in a bit
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I did try this, didn't help. And I tried doing things from your first post and it didn't work... says something about raw file system. I've attached a screenshot.
huh from the screenshot I see that the /system partition is raw, which shouldn't be (or the stupid fastboot defaults to "raw" partition if ext4 is not specified ...)
What happnes when you try to flash the system chunks?
liveroy said:
huh from the screenshot I see that the /system partition is raw, which shouldn't be (or the stupid fastboot defaults to "raw" partition if ext4 is not specified ...)
What happnes when you try to flash the system chunks?
Click to expand...
Click to collapse
All good now!) So silly, I didn't notice that in firmware folder spareschunkes have periods before number!) And in the restoring threat they don't have them!) Thanks anyway, man!!!
Sent from my HTC One_M8 using Tapatalk
ekabon said:
All good now!) So silly, I didn't notice that in firmware folder spareschunkes have periods before number!) And in the restoring threat they don't have them!) Thanks anyway, man!!!
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Glad that it worked after all :good:
Any help would be greatly appreciated. I recently flashed the new TRWP using fastboot. Went fine. I then tried to wipe and flash the newest version of KatKiss. I thought it also went fine but after reboot, it bootloops TWRP. I can tell the tablet to boot Android, but it just hangs. Then when I try to boot back into TWRP, it starts the bootloop all over again. Here is what it's doing during bootloop.
Running OpenRecoveryScript
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'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
-- Wiping DATA Partition...
Formatting Cache using make_ext4fs function.
After about 1 minute it will follow with...
E:Unable to mount '/data'
-- Data Partition Wipe Complete!
Done processing script file
It will then reboot within 3 seconds after displaying the last line, and begin it all over again.
I'm hoping someone can tell me what options I have at this point. Would I be able to return to stock using fastboot and ASUS's blob from their website? Again, any help is greatly appreciated!
Solved.
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Recreate the partition
anim0sity said:
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Click to expand...
Click to collapse
anim0sity
What happened if you dont have the blob???
I had a tab, i complete erase all the partition and i cannot install any app, always had error 963
How i can recreate all the partition of my tablet?
It running android 5 lollipop
Regards,
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
anim0sity said:
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Anim0sity
I downloaded the package and starting doit the process
H:\android-sdk\platform-tools>fastboot devices
015d15b4fc481208 fastboot
H:\android-sdk\platform-tools>fastboot erase system
_
Now is hanging here what i can do it??
Thanks
successful
Hi
After many tries and plug the usb cable in the back of my tower i successful install the firmware
Regards,
HI to rstore to stock using twrp, is it as simple as downloading the file to the tablet, unziping once then flashing the resulting file, or is it a bit more difficult than that?
Hello,
I have an issue trying to readback and then flash userdata partition.
In one device it worked without issues (I actually dd from linux the userdata in that device).
But in a second device its just does not work. I tried dd, I tried readback, but after programming the image, it fails to boot.
Using twrp backup/restore works.
I don't understand why userdata partition can't be backup and restored with sp flash.
I also noticed a very strange issue, that the text in this device gives only 1.6G to userdata, while dd and /cat/partitions shows 5.5G.
I tried to change the text to 5.5G but it did not help neighter...
Please help.
Regards,
ranran