Hello. While I was copying the .pgm files out of the boot directory, (with hopes of editing and replacing) I accidentally rebooted my NT. The boot partition was mounted at via :
Code:
mount -o rw /dev/block/mmcblk0p1 /sdcard/mnt
My NT now shows no signs of life except for the power LED glowing while charging. It still shows the screen of the app where the reboot was initiated from. I have tried to boot it using a SD card with a fresh touchnooter image, but there has been no change in my NT. Could anyone suggest what I should do next?
Kind regards.
I will try out n2T-Recover_0.2.img . TY for the good info and tools. Time for sleep.
Worked like a charm
Related
Hi the question is in the title.
I got it working on quarx's cm7 RC 1.0(only with directory method), but on WIUI 2.2.3 i get errors.
On startup i get this error:
Internal tests failed!
-Kernel config is not known becouse /proc/config.gz file is not found. /this was present on cm7 too/
Here i click override.
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Loop method:
Creating and formating the loop finishes fine.
When i click mount loop it says: "Can't mount BLOCK Part: Did you forget to format? I think this ext version is not supported!"
however i'm using the ext2 file format, which is included in the application. In the log i found this line: "MountLoop > Error:mount mounting /dev/block/loop1 on /data/local/mnt/Linux failed: No such device"
I think this is the source of the error. Beside that i didn't found any strange entries in the log.
I managed to get it working.
All i had to do is remount /data with dev option. After that the directory method is working on internal memory. I've also tried to install linux on sdcard, but that fails, because when i try to change the "Chroot point" in the setup i get "Directory is nodev!, not saved", even after remounting /mnt/sdcard with dev option.
Anybody have an idea to fix this?
for me it worked!
..unfortunetly only for debian squeeze :/ would like to get at least ubuntu 10.4.
i had to manually umount my sdcard.
i'm not shure if this was necessary, but i also remounted all devices that where mounted as nodev.
my mountpoint was /data/local/linux
EDIT: *sigh sorry i forgot to say, i'm on atrix,not on defy.. but the point is, that i also get those errors whenever i try to install any ubuntu while debian squeeze works fine.
I have the same problem
Hi!
I have the same problem,I tried all the 3 roms (Wiui,CM,Miui)+the stock with root,but on these roms,the linux installer sends the same message: "Kernel features is not know because the /proc/config.gz file is not found"
I tried to install Ubuntu too with the ubuntu installer app from market ,it didn't work too.
Is there anybody,who use any linux on his/her Defy?
I' sorry for my English.
On CM10 the application named "Complete Linux Installer" is working fine. Unfortunately i'm still not able to use loop method on CM7. If you really need this on your phone you should try CM10.
By the way i would happy to hear about anybody who have a working loop device setup on CM7.
jumika said:
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Click to expand...
Click to collapse
I may have partially solved this if you haven't already. Here's what I did to install using BLOCK method:
First, used an old HTC Dream that had an Amon RA recovery on it to format the SD card. The recovery has an automated option to make an ext2, 3, or 4 partition + swap on the sdcard. I first made an ext2, then coverted it into ext3, then into ext4. I then put the sdcard back into my main phone. My main phone did not support the Amon RA recovery and that's why I needed to use another phone.
Then I used another app called "Linux Deploy" to see what the ext4's /dev/block was. The app has a menu option called "sysinfo". I think you can also just use that command in Terminal Emulator. Look at the partition sizes carefully. Remember the filesize you used to create your EXT (the swap partition is right under your EXT as well). Use that block device in the Linux Installer setup menu. You shouldn't see the "nodev" anymore.
What happens is that the sdcard itself is usually formatted as FAT32 (vfat) and will always be "nodev". Partition some or all of the space as EXT + SWAP and it will be fine. I've successfully installed to sdcard using this way. Let me know how this works for you or if I need to clarify some things.
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
you must use e2fsck in order to check the EXT partition before mounting, esp if you are using it for DATA.
also, if you try to mount a bad partition it won't mount as r/w, instead it will mount as r/o (read only). that's why you were having the read-only issue.
regarding java, you need to install JDK. if you have a x64 system, you need both x86 and x64 variants.
hope this helps
blastsound said:
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
Click to expand...
Click to collapse
How are you mounting /data to EXT? If you are using my method, I have included a accept that scans at boot and then mounts if the partition is clean. Mounted partitions can't be scanned, they have to be unmounted before scanning.
Swyped from my HTC HD2 using XDA Premium
Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:
Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...
My phone was slowly corrupting some files inside the external sd card, but I thought it might have been because I had named a file with a $ sign and it had some problems when I plugged the usb.
After I had taken the file out and deleted the corrupted files (Some of my game saves died too :crying, I thought it was going to be okay, but the corruption did go on after some time.
One day, when I was using the phone, suddenly, I got a white line accross the screen and the phone rebooted, then every time it turned on, it worked for 1~3 seconds then, again, white line and reboot.
Tried to fix it in various ways, turning off wi-fi, changing the brightness and things like that in the moment before it rebooted, but I couldn't make it work.
After some tries/time, it gave me an error saying it needed to be wiped and reseted, but I really need some files inside of it, so I didn't wipe it, and now it just stops at the samsung logo.
I can get it into recovery mode or that "custom rom" screen, by using the volume buttons when booting up, and I could even get it to show in adb when in recovery mode, but I can't mount the sd card with it (It always tells me I can't do it, something about privileges, I think).
I just wanted to get some files from the internal memory, after that, I think I'll be flashing it with CyanogenMod so it'll be a Android 4.4
But, for now, what can I do to recover those files?
Thanks in advance
Edit: Recovery menu says:
--init-recovery...
E: failed to mount /data (invalid argument)
can't mount /data (invalid argument)
Then it tries to apply "multi-csc" and after it "successfully applies" it, then it shows the "failed to moun /data" error again
Well the easiest way would be to flash TWRP recovery and use the file manager to copy the files that you need to your mem card... if u couldn't access the internal memory just mount it manually either from the option "mount sdcard" or use the a shell command.. I believe there is a terminal emulator there
The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...
Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.
nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.
ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...
Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!