Related
Hello!
I'm trying to find out where to see a list of parameters I can use in there.
I'm using the ClockworkMod recovery (even if I think it's just universal that part), but if I write in that cache file "boot-recovery --nandroid" nothing happens when I reboot into recovery, if I set just "--nandroid" it says "E: invalid arguments"...
What I want to achieve is to execute a nandroid backup and then one or more update zip files. Is it possible?
Thanks!
no one has any idea?
Hi everyone, this is my first thread
I recently rooted my 16gb WiFi only nexus 7. After installing 3 different roms (touchwiz, cyanogenmod 10, and xenon HD) I didn't like touch wiz or cyanogenmod, and I'm currently running xenon HD. However, when I opened my storage today, of said I had 3.6gb remaining. I thought it may have been all the apps, so I factory reset it, reset the partition, and deleted all data via recovery mode. That gave me about 1 more gigabyte. I opened ES file explorer and deleted everything there. I still have only 4.6 gigabytes usable. Anyone else have this issue?
Thanks
Sent from my Nexus 7 using xda app-developers app
Well, I deleted some old backups and now I have 7.5 gb of storage, which should do for now. But I still have that 6 GB leftover, anyone know whats wrong?
Thanks
Sent from my Nexus 7 using xda app-developers app
OK. Now I mucked around in the mounting/unmounting stuff, and now it won't boot. It's stuck at the Google screen. Someone help please???
Sent from my Nexus 7 using xda app-developers app[/QUOTE]
You are not the only person who has experienced this.
Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard
Either the "format data" option in TWRP, or using fastboot.
Code:
fastboot erase userdata
fastboot format userdata
I've had the latter create short file systems - and also not create short file systems.
Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. Ugh - I hope your luck is better than mine.
Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.
Long boring thread, but related.
http://forum.xda-developers.com/showthread.php?t=2184486
good luck
Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.
bftb0 said:
You are not the only person who has experienced this.
Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard
Either the "format data" option in TWRP, or using fastboot.
Code:
fastboot erase userdata
fastboot format userdata
I've had the latter create short file systems - and also not create short file systems.
Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. Ugh - I hope your luck is better than mine.
Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.
Long boring thread, but related.
http://forum.xda-developers.com/showthread.php?t=2184486
good luck
Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.
Click to expand...
Click to collapse
I basically have nothing I need on my tablet, so I'm fine deleting everything on it, if that's what you mean. I'll try, but thanks:good:
nicetaco said:
I basically have nothing I need on my tablet, so I'm fine deleting everything on it, if that's what you mean. I'll try, but thanks:good:
Click to expand...
Click to collapse
Wait, is that for getting back the storage or actually letting it boot up? Because right now the storage is the least of my concerns.
What I described is for getting back lost space (by recreating from scratch the ext4 filesystem in the userdata partition).
As it doesn't touch either the boot partition or the system partition, your tablet should certainly be able to boot. If you don't do a restore of /data from a backup, the result will be like a factory reset of whatever rom you had on the tablet.
Just make sure to check the size of the data partition before you start re-customizing or restoring data from backups to make sure that you got the full size of the partition.
bftb0 said:
What I described is for getting back lost space (by recreating from scratch the ext4 filesystem in the userdata partition).
As it doesn't touch either the boot partition or the system partition, your tablet should certainly be able to boot. If you don't do a restore of /data from a backup, the result will be like a factory reset of whatever rom you had on the tablet.
Just make sure to check the size of the data partition before you start re-customizing or restoring data from backups to make sure that you got the full size of the partition.
Click to expand...
Click to collapse
Ughhh its still not turning on...
nicetaco said:
Ughhh its still not turning on...
Click to expand...
Click to collapse
Please re-read this quote from your 2nd thread in this fiasco.
Nico_60 said:
How do you want to know what's happening to your device if don't tell us which commands you have done exactly with fastboot and why ?
Click to expand...
Click to collapse
If you screwed around with your system partition and it wouldn't boot before, then with a freshly formated and empty /data filesystem, of course it still will not boot. The instructions I provided in this thread only involved the userdata partition!
But you didn't say "I did such and such and it still hangs during the initial boot phase where the X logo is flashing on the screen"; instead you said:
"Ughhh its still not turning on".
WTF? Has your problem now morphed into a dead battery problem, or is the language you are using just incredibly imprecise?
Anyway, Flash a new ROM using the custom recovery. Any ROM - you pick. Maybe not that Xenon ROM or whatever it is called. See if the new ROM boots. And then immediately after it boots, check to see what size the /data partition is.
And if you come back into this thread anymore please be specific about what you are attempting and exactly what symptoms you are observing.
good luck
bftb0 said:
Please re-read this quote from your 2nd thread in this fiasco.
If you screwed around with your system partition and it wouldn't boot before, then with a freshly formated and empty /data filesystem, of course it still will not boot. The instructions I provided in this thread only involved the userdata partition!
But you didn't say "I did such and such and it still hangs during the initial boot phase where the X logo is flashing on the screen"; instead you said:
"Ughhh its still not turning on".
WTF? Has your problem now morphed into a dead battery problem, or is the language you are using just incredibly imprecise?
Anyway, Flash a new ROM using the custom recovery. Any ROM - you pick. Maybe not that Xenon ROM or whatever it is called. See if the new ROM boots. And then immediately after it boots, check to see what size the /data partition is.
And if you come back into this thread anymore please be specific about what you are attempting and exactly what symptoms you are observing.
good luck
Click to expand...
Click to collapse
OK. I tried to install a new rom, but I can't because I have USB debugging off, which I can't turn on
bftb0 said:
You are not the only person who has experienced this.
Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard
Either the "format data" option in TWRP, or using fastboot.
Code:
fastboot erase userdata
fastboot format userdata
I've had the latter create short file systems - and also not create short file systems.
Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. Ugh - I hope your luck is better than mine.
Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.
Long boring thread, but related.
http://forum.xda-developers.com/showthread.php?t=2184486
good luck
Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.
Click to expand...
Click to collapse
Thank you, bftb0!
I was looking around for this after I discovered my lack of space. I read about it before, but couldn't dig up the post. Thanks for informing us! Enjoy the thanks!
nicetaco said:
OK. I tried to install a new rom, but I can't because I have USB debugging off, which I can't turn on
Click to expand...
Click to collapse
ADB is available in the custom recovery... so long as you have the right drivers installed on your PC. And that is NOT controlled by some setting in the most recent ROM that you flashed - it is always running in the custom recovery.
One of the quirks about ADB in the recovery with the Nexus7 is that it claims a different USB address than "ADB Composite Interface" that the regular OS does. This might mean that ADB works correctly with the regular OS booted, but not when the custom recovery is booted, depending on what drivers you have installed. Yes, you need yet another driver installed even though they are both "ADB" connections. But that is a Windows driver issue, not a problem with the N7.
You can also use an OTG cable and a USB drive with TWRP if that is easier. Put your ROM on the memory stick and then use TWRP's "external memory". To be most compatible, make sure the USB stick is formatted in a FAT format. (I don't know if TWRP can handle NTFS).
upichie said:
Thank you, bftb0!
I was looking around for this after I discovered my lack of space. I read about it before, but couldn't dig up the post. Thanks for informing us! Enjoy the thanks!
Click to expand...
Click to collapse
I wonder if I can I trade them in for some coupons or something
@bftb0, I was not able to use adb while in TWRP but i found THIS and it was the solution, what do you think about this "fix"?
bftb0 said:
ADB is available in the custom recovery... so long as you have the right drivers installed on your PC. And that is NOT controlled by some setting in the most recent ROM that you flashed - it is always running in the custom recovery.
One of the quirks about ADB in the recovery with the Nexus7 is that it claims a different USB address than "ADB Composite Interface" that the regular OS does. This might mean that ADB works correctly with the regular OS booted, but not when the custom recovery is booted, depending on what drivers you have installed. Yes, you need yet another driver installed even though they are both "ADB" connections. But that is a Windows driver issue, not a problem with the N7.
You can also use an OTG cable and a USB drive with TWRP if that is easier. Put your ROM on the memory stick and then use TWRP's "external memory". To be most compatible, make sure the USB stick is formatted in a FAT format. (I don't know if TWRP can handle NTFS).
I wonder if I can I trade them in for some coupons or something
Click to expand...
Click to collapse
Holy crap I forgot about the OTG cables. Thanks, I'll try it!
nicetaco said:
Holy crap I forgot about the OTG cables. Thanks, I'll try it!
Click to expand...
Click to collapse
Thank you so much. That did it.
First problem fixed through XDA developers
Enjoy my thanks
Nico_60 said:
@bftb0, I was not able to use adb while in TWRP but i found THIS and it was the solution, what do you think about this "fix"?
Click to expand...
Click to collapse
The ADB daemon - "adbd" is definitely sitting there running inside the custom recovery. Even if you can't communicate with it because of a lack of a driver, you should nevertheless be able to see it as an unknown device in the PC's device manager.
I have done the same hack - hand editing the .INF file - with both the Google SDK drivers and the Asus drivers, and in both cases it worked fine (one driver for everything: ADB in the OS, ADB in TWRP/CWM, and fastboot with the bootloader).
I have also used the Google SDK driver without modification plus the XDA Universal Naked driver. That means using the Google driver for fastboot and ADB when the OS is booted, and the XUN driver for custom recoveries only.
At the present time the ONLY driver I have installed is a hacked version of the Asus drivers.
Win 7 complains about signing when doing this (for the Asus drivers for sure, I can't remember if the Google driver is signed or not).
As I mentioned, Win 7 Pro x64. I suppose the whole "violated signing" might make life even more difficult with Win 8 though.
bftb0, did you personally experience the problem of losing space on the internal memory? I tried your advice, but it didn't work. I'm on PAC(man) ROM. I booted into TWRP, did the data wipe (not factory reset, the full wipe that wipes the everything) but I still only have 13 gb available (on my 32 gb Nexus 7). I rebooted into TWRP and did a factory reset AND wipe data, but I am still missing half of my internal memory.
Do you need to do this on the stock ROM for it to work? Any other tips would be greatly appreciated.
upichie said:
bftb0, did you personally experience the problem of losing space on the internal memory? I tried your advice, but it didn't work. I'm on PAC(man) ROM. I booted into TWRP, did the data wipe (not factory reset, the full wipe that wipes the everything) but I still only have 13 gb available (on my 32 gb Nexus 7). I rebooted into TWRP and did a factory reset AND wipe data, but I am still missing half of my internal memory.
Do you need to do this on the stock ROM for it to work? Any other tips would be greatly appreciated.
Click to expand...
Click to collapse
Yes, it really did happen to me.
After it happened I took the trouble to download 4 different versions of TWRP (2.4.1.0-2.4.4.0), and I re-created the ext4 filesystem with:
- each of the different versions of TWRP and
- fastboot format userdata
after each, I did a "e2fsck -f -n <block-device>" on the (unmounted) userdata partition to see that they were clean, and I also dumped the output of "tune2fs -l <block-device>" to a file for comparison. Other than things that I would expect to be different (e.g. partition UUID identifier strings and timestamps), I noticed no differences. And also, I couldn't reproduce the problem for the life of me.
Above you mention full "data wipe". In TWRP (v2.4.1.0), this is presented as a separate button in the "Wipe" sub-menu where it (the last button in the first column) is labeled "Format Data". I suppose this is what you mean, but thought I would be explicit to avoid any confusion. (The "factory reset" procedure in the two custom recoveries - both CWM and TWRP - can not possibly re-create the ext4 filesystem in /data, as the /data/media/0 SD card files are in there. But the "Format Data" button does destroy & recreate the whole filesystem).
If you press on this button and at the same time capture the output of the "ps" command, you will see that TWRP recovery invokes the /sbin/make_ext4fs in the following way
Code:
make_ext4fs -l -32768 /dev/block/mmcblk0p<PARTNUM>
(CWM probably uses a different external command as it does not seem to have a "make_ext4fs" command in it's ramdisk. Probably mke2fs with ext4 options on the command line)
Anyways, I can't say I have my finger on exactly how to resolve the problem as I can not re-created it. But it did happen to me.
One thing you can try rather than using TWRP's "make_ext4fs" command (underneath that button "Format Data") is to reboot into the bootloader from TWRP, and do the file system formatting in fastboot instead of TWRP, as in:
Code:
fastboot format userdata
(noobs: caution, this is a full userdata wipe)
and then bop back into the recovery and check things with "tune2fs" report
Code:
tune2fs -l /dev/block/mmcblk0p<PARTNUM>
My 32G N7 shows a total block count of 7503608 (x 4k/block = 29.3 GiB) doing this.
As I mentioned before, it's a good idea to check to see you have the right size before you start restoring stuff to avoid wasting time. You can do it above with "tune2fs -l", or because TWRP seems to want to mount /data and /sdcard when it boots, just run
adb shell df -k /data
to get a report of total and used size.
Sorry this isn't more definiitve. I would have spent more time looking at this, but it is tedious as you need to unload the whole d*mn SD card in order to experiment. Thank goodness my 30GB partition only has about 10Gigs of stuff on it.
good luck
bftb0 said:
Yes, it really did happen to me.
After it happened I took the trouble to download 4 different versions of TWRP (2.4.1.0-2.4.4.0), and I re-created the ext4 filesystem with:
- each of the different versions of TWRP and
- fastboot format userdata
after each, I did a "e2fsck -f -n <block-device>" on the (unmounted) userdata partition to see that they were clean, and I also dumped the output of "tune2fs -l <block-device>" to a file for comparison. Other than things that I would expect to be different (e.g. partition UUID identifier strings and timestamps), I noticed no differences. And also, I couldn't reproduce the problem for the life of me.
Above you mention full "data wipe". In TWRP (v2.4.1.0), this is presented as a separate button in the "Wipe" sub-menu where it (the last button in the first column) is labeled "Format Data". I suppose this is what you mean, but thought I would be explicit to avoid any confusion. (The "factory reset" procedure in the two custom recoveries - both CWM and TWRP - can not possibly re-create the ext4 filesystem in /data, as the /data/media/0 SD card files are in there. But the "Format Data" button does destroy & recreate the whole filesystem).
If you press on this button and at the same time capture the output of the "ps" command, you will see that TWRP recovery invokes the /sbin/make_ext4fs in the following way
Code:
make_ext4fs -l -32768 /dev/block/mmcblk0p<PARTNUM>
(CWM probably uses a different external command as it does not seem to have a "make_ext4fs" command in it's ramdisk. Probably mke2fs with ext4 options on the command line)
Anyways, I can't say I have my finger on exactly how to resolve the problem as I can not re-created it. But it did happen to me.
One thing you can try rather than using TWRP's "make_ext4fs" command (underneath that button "Format Data") is to reboot into the bootloader from TWRP, and do the file system formatting in fastboot instead of TWRP, as in:
Code:
fastboot format userdata
(noobs: caution, this is a full userdata wipe)
and then bop back into the recovery and check things with "tune2fs" report
Code:
tune2fs -l /dev/block/mmcblk0p<PARTNUM>
My 32G N7 shows a total block count of 7503608 (x 4k/block = 29.3 GiB) doing this.
As I mentioned before, it's a good idea to check to see you have the right size before you start restoring stuff to avoid wasting time. You can do it above with "tune2fs -l", or because TWRP seems to want to mount /data and /sdcard when it boots, just run
adb shell df -k /data
to get a report of total and used size.
Sorry this isn't more definiitve. I would have spent more time looking at this, but it is tedious as you need to unload the whole d*mn SD card in order to experiment. Thank goodness my 30GB partition only has about 10Gigs of stuff on it.
good luck
Click to expand...
Click to collapse
.
I'm a total command prompt beginner here, so could you explain where I'm doing the fastboot format command? In a terminal on the device? Using adb on my windows machine? I tried all that I could think of, but none of it worked. No form of wiping the device (yes, via "format data" in TWRP) seems to work. I'm still missing half of my storage.
EDIT: Okay, so I ran the command--I had to have the device in the bootloader, duh. Unfortunately, it still did not work. When recreating the file system, it said there was a total of ~3.5 million blocks--half what I saw reported in the other thread. Not surprising, since I'm missing half of my storage. How come this is working for other people but not me? I tried doing both at the same time, but to no avail. This is getting stupid.
upichie said:
EDIT: Okay, so I ran the command--I had to have the device in the bootloader, duh. Unfortunately, it still did not work. When recreating the file system, it said there was a total of ~3.5 million blocks--half what I saw reported in the other thread. Not surprising, since I'm missing half of my storage. How come this is working for other people but not me? I tried doing both at the same time, but to no avail. This is getting stupid.
Click to expand...
Click to collapse
Arrgh. Did you do the "fastboot erase userdata" first?
Here's what the fastboot format looked like on my device when I did this last (3/13):
Code:
$ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.974s]
finished. total time: 4.979s
$ fastboot format userdata
erasing 'userdata'...
OKAY [ 4.454s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 30734811136
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7503616
Block groups: 229
Reserved block group size: 1024
Created filesystem with 11/1875968 inodes and 161774/7503616 blocks
sending 'userdata' (139197 KB)...
writing 'userdata'...
OKAY [ 33.733s]
finished. total time: 38.194s
As I said, I was unable to reproduce the problem even though I tried. But it almost seems like the creation of the new filesystem is inferring something from somewhere (but where?) about the userdata partition size which is incorrect. Almost like it happens because of something it sees in the prior filesystem (which is being destroyed). So it becomes irreproducible unless you can recreate the same starting condition.
There's other mysterious crap going on here too. See the output above? The part where it says "sending 'userdata' (139197 KB)" ? It will say this no matter where you run the command from, and there is no 139 MB "userdata.img" file in the folder it runs from!!! 139 MB? For a filesystem which is empty when you mount it?
I don't know. Here's one more thing to try, though. In addition to doing the "erase" & "format" commands, perhaps you could actually flash the userdata image from the stock ROM
Code:
fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img
and then when you boot to the custom recovery, perform a "factory reset" - or try doing the "Format Data" thing in TWRP after (or before?) the above steps.
If none of this works, I suppose you could try the equivalent sorts of things with CWM and see if you get a different result.
You don't need to permanently install CWM with a hard flash - you can just soft-boot it for a single session:
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
Sorry this is so vague, but you know how it goes - you stumble into a problem, start fooling around until it gets fixed - and because you weren't really expecting the problem in the first place, you haven't written down the exact conditions and steps. Like I said, I tried to re-create the problem a variety of ways - but failed at that effort.
good luck
I've been flashing N7 with no issues as recently as over the weekend. Today I tried to flash a new ROM and it failed. Tried a second, different ROM, same result. Do not know what I did. Any thoughts?
Error log would help greatly.
How do I get/generate the log? Haven't had to do it before.
Thanks,
Paul
The logs= errors displayed on the screen provided by the interface you use to flash the rom (recovery, computer...)
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
do I need to create a partition? Never get more details despite the tease.
Thanks,
First -
Try and download a different (NEWER) TWRP. Re-flash TWRP. Try again
or
Have you tried completely wiping the device? And pushing a ROM from ADB or using a USB OTG and Memory stick?
I had issues with my nexus becoming VERY unstable. Leading to issues.
I completely, and I mean completely, wiped. To the point that all that device basically had was a recovery, and a bootloader.
I proceeded to flash again, BOOM all fixed up.
Is there a new TWRP?
I did a factory restore after wiping everything thing, if that is what you mean?
It was working as expected last week, don't know what I did to screw it up
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
ibsk8 said:
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this, and it said it copied but I am unable to locate it. It says 0\media\data But that folder structure doesn't exist, at least according to file expert
Will a complete wipe/restore create a partition?
pmgreen said:
Will a complete wipe/restore create a partition?
Click to expand...
Click to collapse
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
pmgreen said:
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
Click to expand...
Click to collapse
Focus your efforts here; it certainly looks like a first-order problem.
bftb0 said:
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
Focus your efforts here; it certainly looks like a first-order problem.
Click to expand...
Click to collapse
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
pmgreen said:
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
Click to expand...
Click to collapse
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
bftb0 said:
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
Click to expand...
Click to collapse
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
pmgreen said:
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
Click to expand...
Click to collapse
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ su
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
bftb0 said:
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ such
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
Click to expand...
Click to collapse
Thanks bftb, you are correct it's a can't open zip. No error than fail and it can't open the zip. It says updating partition but nothing changes
The file names are from the developers, once of which I recently successfully flashed. Tried coping the log to the SD card, but unable to find /data/media/0. Do I need to recreate a partition?
(FYI there was an auto-correct typo in my prior post - "su" not "such". Derp)
pmgreen said:
Do I need to recreate a partition?
Click to expand...
Click to collapse
No. (There is no way to do that with the tools we have anyway)
Unless what you mean by "recreate" is rebuild/reinitialize a filesystem in a partition - that's a possibility.
You need to try and figure out why you can't read files.
As a workaround, you can put files on a USB key (FAT formatted, not NTFS) and using TWRP access them by putting the USB key on the other end of a OTG cable.
Your posts are a bit vague - I can't even tell if you have tried other ROM files, whether you checked them to see if they are the correct size/checksum, etc.
pmgreen said:
Tried coping the log to the SD card, but ...
Click to expand...
Click to collapse
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
bftb0 said:
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
Click to expand...
Click to collapse
I am not familiar using ADB pull. Tried using a root file manager to access the log but don't see.
Greatly appreciate your help, let me know what other info I should paste.
Thanks,
A while back my nexus 10 started behaving strangely. First of all google play force closes. The storage option in settings shows 27gb available.
Here are some responses from other apps:
Gallery : No external storage available
Camera: Unfortunately camera has stopped.
Apps cannot be installed unless through adb install
I have tried to flash stock images and interestingly only 4.4.4 works. 5.0 or 5.1 does not. I have tried flashing all files individually too.
I installed ES File Explorer and
the first toast is /sdcard/ not found.
/storage/ has two folders
/storage/emulated/ has a FILE named legacy which appears to be a shortcut.(Tapping it opens the open as menu)
storage/usbdisk/ is empty
/storage has one FILE named sdcard0 which also appears to be the same type of shortcut( tapping opens the open as menu)
/mnt/media_rw is empty
/data/media/0 has the files i need. I think this needs to be linked to the /storage/emulated directory? I'm not sure. Would a symlink solve the problem? If so please guide me with the command or any other way to fix this issue. I have wiped the data multiple times.
Hello,
please use this command's before flashing:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot erase recovery
And then flash FactoryImage: 5.1.1 (LMY48T)
After repeated attempts to fix it, it finally worked but I do not know what did the trick. I erased system userdata cache recovery boot and also formatted them. I tried to flash separately not using the flash all script. I flashed everything except the recovery and it worked. It still work but sometime it runs into problems if i try to flash a custom rom. It always gets stuck mounting cache even when i am using twrp.
Hello,
please use this Recovery: twrp-2.8.7.0-manta.img
Change the filesystem of cache to Ext2 and then move back to Ext4. You will find this option under the point "wipe".
Should I do that now? or in case it starts acting up again. Its working fine now.Thank you so much! The only answer Samsung had was to change the logic board.
Only in case it starts acting up again. No problem
Hi, I cant get to install any roms on my phone after updating via OTA (Lineage 17.1)
I can access to twrp but when I try installing any rom half bar is completed and after that, it crashes and boot loop.
I have tried to install different roms but same result. Can anyone help please?
Already tried:
Factory reset
wipe: data/cache/ system
Restore firmware via fastboot flash.
Change SD card
Installed 3 different stock roms via fastboot and they boot but after few seconds reboot on setup (Gboard and maps apps crash warning)
View attachment 5130605
No solution anyone?
dawe0120 said:
No solution anyone?
Click to expand...
Click to collapse
Post your recovery.log and I will tell you what's wrong with your phone.
TWRP main screen > advanced > create log
Please rename it from recovery.log => recovery.txt or .zip it to upload the file here.
WoKoschekk said:
Post your recovery.log and I will tell you what's wrong with your phone.
TWRP main screen > advanced > create log
Please rename it from recovery.log => recovery.txt or .zip it to upload the file here.
Click to expand...
Click to collapse
Thanks for the response here it is.View attachment 5131037
dawe0120 said:
Thanks for the response here it is.View attachment 5131037
Click to expand...
Click to collapse
This log doesn't show anything about your error. Reproduce the error and than grep the log.
Ok done, here is what I did:
Wiped side b (to make sure there's no other rom installed), then tried to install pixel experience rom and the twrp crash at mid bar happened again. (Same process as shown in screenshot)
After that rebooted to twrp and created the log.
View attachment 5131307
dawe0120 said:
Ok done, here is what I did:
Wiped side b (to make sure there's no other rom installed), then tried to install pixel experience rom and the twrp crash at mid bar happened again. (Same process as shown in screenshot)
After that rebooted to twrp and created the log.
View attachment 5131307
Click to expand...
Click to collapse
Ok, due to the crash TWRP does not record the error. But you can try this :
Before you are going to flash the ROM connect your device with your PC. Open ADB cmd line and first of all check the connection with
Code:
adb devices
After that run
Code:
adb logcat >> recovery.txt
When TWRP crashes you'll find the recovery.txt inside of your ADB folder on your PC.
WoKoschekk said:
Ok, due to the crash TWRP does not record the error. But you can try this :
Before you are going to flash the ROM connect your device with your PC. Open ADB cmd line and first of all check the connection with
Code:
adb devices
After that run
Code:
adb logcat >> recovery.txt
When TWRP crashes you'll find the recovery.txt inside of your ADB folder on your PC.
Click to expand...
Click to collapse
I did what you told me, but the only thing in the recovery.txt is:
/sbin/sh: logcat: not found
First command: displays my S/N - recovery
So comm is not the problem.
dawe0120 said:
I did what you told me, but the only thing in the recovery.txt is:
/sbin/sh: logcat: not found
First command: displays my S/N - recovery
So comm is not the problem.
Click to expand...
Click to collapse
The connection is ok but logcat isn't included in TWRP.
Ok, next try:
When TWRP crashes check connection again with adb devices. Got a connection? Then go ahead with
Code:
adb pull /tmp/recovery.log recovery.txt
and upload it here.
WoKoschekk said:
The connection is ok but logcat isn't included in TWRP.
Ok, next try:
When TWRP crashes check connection again with adb devices. Got a connection? Then go ahead with
Code:
adb pull /tmp/recovery.log recovery.txt
and upload it here.
Click to expand...
Click to collapse
Ok, here is what I did:
Wiped side B again(to clean the previous failed installation)
Installed P.E. rom (same crash issue happened)
Then reboot to twrp. Put de communication command (everything ok S/n and recovery displayed)
And finally wrote the adb pull command successfully
HEre's the file: View attachment 5131657
dawe0120 said:
Ok, here is what I did:
Wiped side B again(to clean the previous failed installation)
Installed P.E. rom (same crash issue happened)
Then reboot to twrp. Put de communication command (everything ok S/n and recovery displayed)
And finally wrote the adb pull command successfully
HEre's the file: View attachment 5131657
Click to expand...
Click to collapse
A reboot clears the log so I still got no information. Either you grep the log when TWRP crashes or the log buffer will be cleared with next reboot.
How did you wipe slot b?
WoKoschekk said:
A reboot clears the log so I still got no information. Either you grep the log when TWRP crashes or the log buffer will be cleared with next reboot.
How did you wipe slot b?
Click to expand...
Click to collapse
Ok, this time what I did is to run the pull command just before the crash (at mid bar) I tried to run it at the freezing but obviously the communication with the device was suspended.
I hope this made any difference.
View attachment 5131691
What I mean by saying wiping slot b is selecting it via twrp and then wipe data, cache, system etc.
dawe0120 said:
Ok, this time what I did is to run the pull command just before the crash (at mid bar) I tried to run it at the freezing but obviously the communication with the device was suspended.
I hope this made any difference.
View attachment 5131691
What I mean by saying wiping slot b is selecting it via twrp and then wipe data, cache, system etc.
Click to expand...
Click to collapse
The log ends at 40% of your installation process but no error is shown.
All I would recommend is to flash the stock ROM and download a new Pixel ROM (from official source!). Since it's not possible to take any logs showing your error I don't have a better solution for that.
This process is a Google implementation and not a simple flash script like older ROMs use it. So it's really hard to find an error, even if you know the complete Java source (and I don't ).
Wiping slot _b: There's no need to wipe data for that. Your data partition has got no slots, it's only /data.
Let me explain you in short what's the meaning of all those options:
cache = /data/cache
dalvik-cache = /data/dalvik-cache
internal = /data/media
data = all of /data, except 'media' (internal storage) directory
So, you can see that those options for choosing what to wipe are all stored under /data. The easiest way to wipe them all together would be to format data completely. One step and you're done! If you like to...
WoKoschekk said:
The log ends at 40% of your installation process but no error is shown.
All I would recommend is to flash the stock ROM and download a new Pixel ROM (from official source!). Since it's not possible to take any logs showing your error I don't have a better solution for that.
This process is a Google implementation and not a simple flash script like older ROMs use it. So it's really hard to find an error, even if you know the complete Java source (and I don't ).
Wiping slot _b: There's no need to wipe data for that. Your data partition has got no slots, it's only /data.
Let me explain you in short what's the meaning of all those options:
cache = /data/cache
dalvik-cache = /data/dalvik-cache
internal = /data/media
data = all of /data, except 'media' (internal storage) directory
So, you can see that those options for choosing what to wipe are all stored under /data. The easiest way to wipe them all together would be to format data completely. One step and you're done! If you like to...
Click to expand...
Click to collapse
I have tried to flash 3 different stock roms via fastboot. They boot but then the system crashes at setup and reboots. I get warnings that maps and gboard stoped unexpectedly.
Honestly I dont know what else to try, the only thing I did is to update via OTA (didnt know I shouldtn have) =(
https://forum.xda-developers.com/g6-plus/development/rom-pixel-experience-t4069215 this is the rom Im trying to install and it's an official release.
If I format data instead of wiping will I lose twrp recovery?
View attachment 5131731
Does this info help?
dawe0120 said:
I have tried to flash 3 different stock roms via fastboot. They boot but then the system crashes at setup and reboots. I get warnings that maps and gboard stoped unexpectedly.
Honestly I dont know what else to try, the only thing I did is to update via OTA (didnt know I shouldtn have) =(
https://forum.xda-developers.com/g6-plus/development/rom-pixel-experience-t4069215 this is the rom Im trying to install and it's an official release.
If I format data instead of wiping will I lose twrp recovery?
Click to expand...
Click to collapse
Your Pixel ROM is fine, it's the official release.
Format /data or wiping /data completely is nearly the same. Both methods will erase all stored data. But format will build up a new partition. It's like formatting a USB-Stick in Windows for example.
But none of them would delete your recovery. TWRP is a part of /boot (boot.img) which is only another partition besides /data.
As long as you're not able to boot up your device with the stock ROM you won't be able to boot the Pixel ROM, too. Pixel is only a overlay for stock.
Which three stock ROMs did u try to flash? Build no and source/links would be helpful.
This is the current build for your device: (software channel RETLA is guess??)
XT1926-6_EVERT_RETLA_DS_9.0_PPWS29.116-11-23
Download it and flash it with the attached flashfile.bat (for uploading purposes I had to zip it)
The commands are taken from the flashfile.xml inside the firmaware .zip
WoKoschekk said:
Your Pixel ROM is fine, it's the official release.
Format /data or wiping /data completely is nearly the same. Both methods will erase all stored data. But format will build up a new partition. It's like formatting a USB-Stick in Windows for example.
But none of them would delete your recovery. TWRP is a part of /boot (boot.img) which is only another partition besides /data.
As long as you're not able to boot up your device with the stock ROM you won't be able to boot the Pixel ROM, too. Pixel is only a overlay for stock.
Which three stock ROMs did u try to flash? Build no and source/links would be helpful.
This is the current build for your device: (software channel RETLA is guess??)
XT1926-6_EVERT_RETLA_DS_9.0_PPWS29.116-11-23
Download it and flash it with the attached flashfile.bat (for uploading purposes I had to zip it)
The commands are taken from the flashfile.xml inside the firmaware .zip
Click to expand...
Click to collapse
I flashed it via fastboot the flash didn't show any errors.
The phone starts and says "verity mode disabled", then this happened:
View attachment 5131805
(Video on rar file)
dawe0120 said:
I flashed it via fastboot the flash didn't show any errors.
The phone starts and says "verity mode disabled", then this happened:
View attachment 5131805
(Video on rar file)
Click to expand...
Click to collapse
Oh... that doesn't look good at all!
It seems to be a kind of hardware failure and not only a software bug. Was the OTA update that led to your problem successful?
Boot into TWRP and see if you could find some logs in /sys/fs/pstore and /data/vendor/dontpanic.
WoKoschekk said:
Oh... that doesn't look good at all!
It seems to be a kind of hardware failure and not only a software bug. Was the OTA update that led to your problem successful?
Boot into TWRP and see if you could find some logs in /sys/fs/pstore and /data/vendor/dontpanic.
Click to expand...
Click to collapse
Yes de OTA update was successful, the phone worked flawlessly the whole day(Wednesday) without problems, then I went to sleep that day and when I woke up my phone was bricked. (No I didn't drop my phone or anything like that) These are the files I found on the pstore folder (nothing on the dontpanic folder)
View attachment 5132711
View attachment 5132713
After some research I found posts about the same issue as me :
https://forums.republicwireless.com/t/screen-flickering-with-moto-g-6/21309
So If it's a hardware problem wow just wow. I only have had this phone for nearly 2 months and It's already dying? (Never dropped it or anything like that)
I'll never buy anything from motorola again for the rest of my life.
dawe0120 said:
Yes de OTA update was successful, the phone worked flawlessly the whole day(Wednesday) without problems, then I went to sleep that day and when I woke up my phone was bricked. (No I didn't drop my phone or anything like that) These are the files I found on the pstore folder (nothing on the dontpanic folder)
View attachment 5132711
View attachment 5132713
After some research I found posts about the same issue as me :
https://forums.republicwireless.com/t/screen-flickering-with-moto-g-6/21309
So If it's a hardware problem wow just wow. I only have had this phone for nearly 2 months and It's already dying? (Never dropped it or anything like that)
I'll never buy anything from motorola again for the rest of my life.
Click to expand...
Click to collapse
I guess it could be hardware issue because a full factory image like I linked above covers almost all of your device. You get the kernel and all drivers.
I'll study your logs later that day.