No idea if this will help anyone, but here's the log file from my update that was applied today. Maybe there's a clue in there somewhere...?
interesting... so recovery takes commands from /cache/recovery/command
thanks for posting... I checked system and am downloading ver 1.41.xxxx something... I'll know more when its done... (here in MI)
thor2002ro said:
interesting... so recovery takes commands from /cache/recovery/command
Click to expand...
Click to collapse
Perhaps you guys could set up commands and try out some things there?
Hey Users.
I hope this is the right Forum to post this Question. Like you can see im new at this Forum but I'm an enthusiastic guy
My Problem is:
If I'm trying to restore a backup via CWM, I get the error:
E:format_volume failed to unmount "/system"
Error while formatting /system!
Click to expand...
Click to collapse
I searched google and this Forum to get an answer, but the only thing i found was this post in another Thread. And because I'm new, I don't even understand a bit.
I am having the same problem with Darky v10 RC6 and v10 FINAL and DarkCore kernel v2.2. Here is what worked for me:
while phone is in CWM recovery, get a shell: "adb shell"
# /system/xbin/ps aux |grep /system/
for me this gave /system/bin/tvoutserver with some PID 123 (first number in a row)
# /system/xbin/mount -o remount,rw /system
# mv /system/bin/tvoutserver /system/bin/tvoutserver-bak
# kill 123
# exit
Then try restoring the CWM backup again. (Note that renaming the binary "tvoutserver" is necessary so it is not automatically restarted.)
Click to expand...
Click to collapse
Is there any other way to get the backup work? Or could you explain me, how to do the steps above? Hope you can help me...
nightm4r3
I'm not 100% sure if this relates to your exact situation, but did you rename the backup by any chance ? when adding spaces in the name the backup for some reasont fails to restore...again, not sure if that has to do with your error...
Sent from my GT-I9000 using Tapatalk
No I didn't changed the name. So the reason could be a change in the Folder?
EDIT: No changes were made. But some time ago I had 5-6 backups. No there are only the two latest.
nightm4r399 said:
No I didn't changed the name. So the reason could be a change in the Folder?
Click to expand...
Click to collapse
hmm, if you haven't changed the name it should be fine...not 100% sure otherwise sorry...maybe try change kernel ? (probably wont do anything)
Sent from my GT-I9000 using Tapatalk
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,
I am trying to build the latest CM and I keep getting this error:
Code:
./../jf-common/extract-files.sh: 26: ./../jf-common/extract-files.sh: Syntax error: "(" unexpected (expecting "done")
Any help would be greatly appreciated!
chrisc93 said:
I am trying to build the latest CM and I keep getting this error:
Code:
./../jf-common/extract-files.sh: 26: ./../jf-common/extract-files.sh: Syntax error: "(" unexpected (expecting "done")
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Getting the same error, did you manage fix it?
HazAnwar said:
Getting the same error, did you manage fix it?
Click to expand...
Click to collapse
Yeah. I reverted this: https://github.com/CyanogenMod/andr...mmit/bfa301a70901897142e42cbfe8fa53110594ef15
cd to device/samsung/jf-common
then do git revert bfa301a70901897142e42cbfe8fa53110594ef15
This works, but there has got to be a better way lol
chrisc93 said:
Yeah. I reverted this: https://github.com/CyanogenMod/andr...mmit/bfa301a70901897142e42cbfe8fa53110594ef15
cd to device/samsung/jf-common
then do git revert bfa301a70901897142e42cbfe8fa53110594ef15
This works, but there has got to be a better way lol
Click to expand...
Click to collapse
It worked thanks lol. I'm on developing for the jfltexx, strange bug but thanks for the tip
I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.
Restl3ss said:
I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.
Click to expand...
Click to collapse
Hey bro you are doing such a good thing for developers so please continue this thread and make some thing new
All the best :good: