Database Users

Cannot Get Phone To Start Anymore

So today i rooted my phone installed JF1.41, i partitioned my sd card IN MY G1, since i have a mac and for some reason it wont partition the card right. Then i did the apps2sd deal... Then i wanted to use a theme, well that screwed everything, and it wouldnt get back to normal or even start again. So completely formatted my card, which now has NO PARTITIONS(i guess just 1), and i think the phone is trying to read files on a partition that dont exist now, and NOTHING is working. Anyone on here that can help? I am rather smart with this stuff, but really am going to need someone to help me. I need my phone tomorrow.
Thanks.

How did you reformat your sdcard? Did you check in parted to see that you in fact only had 1 partition again? I suggest you flash a new updated ROM like Cyanogen 4.2.5. That has apps2sd script built into the rom. It will do it automatically so you don't have to mess with all that.

ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1

illthinking said:
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
Click to expand...
Click to collapse
you're going to need a second partition for apps2sd to work. I suggest you do that first before you flash a rom, or else you will just have to end up reflashing.

Ok Downloaded Cyanogen4.2.5
This is the problem i keep having when i try to apply the update it say
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
So i think it has to do with the fact it wants to read /dev/block...etc from the partition of the sdcard that is now non existent

problem is i have a mac and cant properly fromat the 2nd partition (ext2)
unless you know of a way
the way i first did it was using some code i got off of here to have the phone do it itself... now that i cant start the phone i cant do the partition

what recovery do you have? I suggest you put this one on your phone.
http://forum.xda-developers.com/showthread.php?t=566669
It partitions your sd card for you.
Also for Cyanogen, you need to flash the htc OTA update one, then flash his update for those to work.

ok...
so i found some plugins for the new Snow Leopard OS for mac called MacFuse 2.0 along with its counterpart fuse-ext2 and i partitioned my card

you might want to upgrade to ext3. it's faster than ext2 and runs smoother

just tried to flash the recovery found here
http://forum.xda-developers.com/showthread.php?t=566669
with no avail and tried to start the phone(power+camera) and said no image
heres what it said for the recovery
/ # mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on / system/modules failed: No such file or directory
mount: mounting /system/xbin.cramfs on /system/xbin failed: No such file or directory
I mean, what i want to know is how to build the file format back on my sd card so itll work, or build it so it will look on my actual phone... People put up the code to have it switch where it reads things from, there MUST be a way to switch it back manually as well

Use fastboot and write the recovery image
here's a link to fastboot
http://developer.htc.com/adp.html
then when thats running plug in your G1 and turn on holding Power and camera when the screen turns on you might have to press back to enable FB but once its enabled type in terminal
Code:
cd *where ever your recovery image is*
fastboot flash recovery *recoveryname*.img
reboot

can someone hook up a quick step by step on how to hook my phone up fastbooted? I have a mac and i can get the phone to say fastboot, but im lost after that... If you want to reroute me to a different thread, please verify that it REALLY has the info before posting it.

i have been trying to find the name of the device and im getting
/dev/tty.Bluetooth-Modem as the device name, but a Permission Denied thing... now i cant just go click something in the phone menus, since i cant get the phone to start, so is there a way to get permissions through the Terminal application?

that error you get when you type mount -a is normal continue as instructed:
flash_image recovery /(whatever your recovery image is called)
if you have adb you could try parted /dev/block/mmcblk0 and type print to see your parttitions.

so i can get it to say it flashes the recovery, but still not starting

so when i try to do any updates it says SDCARD wont mount
any input?

Looks like im going to go for a broken record, until SOMEONE can help me figure my phone out... I need to get it running, and i know someone can figure it out

NEED HELP PLEASE deleted partitions off emmc

Been semi bricked for hours... I messed up the emmc partitions using adb gparted dev/block/mmcbkl0 and now nook won't boot.. not even off SD card
the only thing i can get to boot off sd card image is rootpack which boots me into recovery.. i tried everything but no matter what I do in recovery i always get errors regarding the mounting of my cache and data, which obviously is because i deleted the partitions...
when i try to edit the partition table from adb parted denies me permission
please help... i'm very new to the nook and everything I just said I learned in the past 4 hours that i have been reading through forums trying to fix it..
thank you

In this very forum..
http://forum.xda-developers.com/showthread.php?t=958748
Besides, what makes you think you deleted the partitions? Did you?

on adb parted i went through every single one of the partitions and deleted them... only left one intact.. so i'm pretty sure i deleted them..
I have already tried flashing this and it flashed just fine however when I go back into the recovery menu I get the same error
E:\ something something can't mount data/recoverylog.log
E:\ something something can't mount cache/recoverylog.log
and four others just like it..

if anyone is willingto help the errors i get in clockwork recovery are
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log

ralphsancho said:
on adb parted i went through every single one of the partitions and deleted them... only left one intact.. so i'm pretty sure i deleted them..
I have already tried flashing this and it flashed just fine however when I go back into the recovery menu I get the same error
E:\ something something can't mount data/recoverylog.log
E:\ something something can't mount cache/recoverylog.log
and four others just like it..
Click to expand...
Click to collapse
And why in gods name did you do that?
Anyway, get the repartition/fix tool that's in these forums.. I think in Development, might be in General. It just works.

[Q] "Damaged SD Card" notification?

What does this notification really mean? I'm running CM7 off an 8G SanDisk. The /sdcard filesystem appears intact, it mounts properly on CM7 and Linux, but this notification won't go away.
fsck on Linux reports no problems.
Might something be confused about partitions? I can't mount /emmc for some reason, CWM can't mount it when I tell it to format it, and USB mode doesn't export it, although it looks like it's trying to; Linux reports a /dev/sde (along with /sdcard at /dev/sdd), but it can't be used:
Code:
# fsck /dev/sde
e2fsck: No medium found while trying to open /dev/sde
Any ideas?
Thanks!
Dennis

Fixed it!
To recap, I'm running CM7 from SD. I was getting a "Damaged SD Card" notification, and my /emmc vanished, and it wouldn't export via USB ("No media present" was the error reported by Linux, although /dev/sde was created), and CWM couldn't format it for me (why not?).
Both were apparently from the same cause. I repaired mmcblk0p8, and now my /emmc is back and the Damaged notification is gone.
So, if you're getting that notification, it may not be about your SD card!
Details: I couldn't use dd from Linux, but I could dd if=...blk0p8 within Terminal Emulator. My busybox doesn't have mkfs.vfat, so I used dd to copy /boot onto the partition; this gives it a (small but sane) filesystem. I rebooted to get /emmc mounted properly (check fstab.vold for the gory details), connected the cable to my Linux PC, checked that the expected contents were on /dev/sde, unmounted it (command line, not via GUI) and ran sudo mkfs.vfat -I -n MyNookColor /dev/sde from the Linux command line. All is now well.

i hv the same issue but since i'm a noob at nook color and i dont knw anything abt linux... i hv no clue what your are talking about...
it would be a gr8 help to me and others who are not well versed with linux, if you could tell me exactly what did u do to fix this problem.
please help me with this issue.
ty
sd

stavan_d said:
i hv the same issue but since i'm a noob at nook color and i dont knw anything abt linux... i hv no clue what your are talking about...
it would be a gr8 help to me and others who are not well versed with linux, if you could tell me exactly what did u do to fix this problem.
Click to expand...
Click to collapse
Android is just as much a Linux system as Ubuntu or Fedora.
This applies if and only if Settings/Storage claims that you have no /emmc or /mnt/emmc, and if you've installed CM7 to emmc. Read the headers carefully.
Start Terminal Emulator.
In this window, type su. The prompt changes to #.
Type df.
If there's a listing for /mnt/emmc or just /emmc, try something else; this isn't for you.
We're going to reconstruct /emmc by copying /boot onto it. THIS WILL ERASE /emmc!!!
Type VERY CAREFULLY:
dd if=/dev/block/mmcblk0p1 of=/dev/block/mmcblk0p8
That's blk zero pee one and blk zero pee eight.
This will grind away for quite some time.
When it's done, reboot.
If you still get the notification, you have some other problem.
You now have a tiny /emmc instead of the 5G partition that should be there. Plug the cable into your PC, enable USB mounting, and verify that one of the volumes looks like a boot partition. If you run a Linux PC, check the device name (mine was /dev/sde, yours is probably different), unmount it, and do the mkfs I showed before.
If you run Windoze, tell it you're done with the /boot drive (like you would do with a thumb drive), and format that device (E:, F:, whichever it was) by (IIRC) right-clicking on it in an Explorer window and selecting Format. Again, SELECTING THE WRONG DEVICE WILL SCREW YOU UP. I am not responsible.
If you're not sure about ANY of these steps, please get expert local help.
Good luck!
Sent from my NookColor using XDA Premium App

i m booting cm7 from the sd card... and settings/storage/additional storage/mnt/emmc Unavailable...
so how do i fix this...
also when i plug NC in boot OS it shows 2 partitions, 1.undefined and 2. 4.98gb... instead of 5gb single partition originally present...

[Q] Anybody had success with "Linux Installer" app on WajkIUI?

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.

Restore Rom Install Failed (Simple Touch) Tried Everything - no Dice. Please Help :)

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!