Database Users

Hero's Kryptonite?

I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!

Unbelievable

CC CEO said:
I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Click to expand...
Click to collapse
i would recommend to go back to your backup (you did do a backup right?)
just flash the data, system, and boot .img files back
since you're doing Hero im guessing you have the newer SPL
you might run into a roadblock trying to fastboot so if you cant get the fastboot to work then boot into recovery mode and then go into a command prompt and run the following:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
this will let you access your memory card
get the HardSPL from here
copy it into your card as "update.zip"
now apply the update with ALT+S
after its done you can reboot back into the bootloader with ALT+X and typing
reboot bootloader
Click to expand...
Click to collapse
now you should be able to flash you backups like usual

nope didnt make a backup...i know..
but...
i was able to format my sdcard back to its original state and i flashed google ion back on the phone. question is are there any lingering affects to the phone itself? in setting up the ext2 or anything on the stock card might i have pushed or pulled something i shouldnt have from the internal storage if i didnt create a backup??
if so. how would i fix this?

if you Alt+W'd the phone there wont be any lingering effects,,,, its wiped and wont bother you no sunder!

I was having the same problem as you, as I too am only using the stock 1gb sdhc that came w/ the g1.
just did searching on here and I got it up n running.
I'm thinking maybe you did like me and pushed the /app_s/ folder while the SD was mounted to your pc, this is what I am guessing was my issue.
I've come to that conclusion since I've done the push w/o mounting the SD
Also I found that I had to be in the app_s folder on my computer to push it right, at first I was pushing it and it was going into /system/sd/app_s/app_s
Here's Haykuro's original instruction's
Installation:
1. Download http://www.droiddeveloper.com/hrbuilds/app_s.zip
2. extract "app_s" into your sdcard's ext2 partition.
3. Download http://www.droiddeveloper.com/hrbuilds/hero-signed.zip
4. Place on regular sd card.
5. Reboot into recovery, wipe and flash.
6. Enjoy.
--
for step 2... make sure you are in the actual app_s folder when you do the following command and make sure the sd card is NOT mounted.
adb push app_s /system/sd/app_s
--
follow the rest of the instruction's as stated and you should be fine.
now, to get it running smoother...
follow the tutorial here...
http://forum.xda-developers.com/showthread.php?t=521251
also within the thread there's tip's on moving the Rosie.apk along w/ widget's to internal memory, I just focused on the larger widget's, the largest being the weather one.
hope this help's.
just one noob tryna help another noob out ;-)

please help
When i am doing the update.. i am getting this error.. .
E: Can't chown/mod /system/xbin (not such file or dir)
E: Failure at line 12: set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
installation aborted."
please help!!

DDMS Error

When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?

Mdawg112 said:
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Click to expand...
Click to collapse
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.

smw6180 said:
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
Click to expand...
Click to collapse
Ha, I feel stupid now.

Mdawg112 said:
Ha, I feel stupid now.
Click to expand...
Click to collapse
Happens to everyone at times. Don't sweat it

So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/

jubi23 said:
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
Click to expand...
Click to collapse
Good question. Unfortunately I have no idea. Never seen it fail. theoretically there's a command line you can run in adb shell to mount the FS read/write, but I can't remember it off the top of my head.
Something like mount -o rw /dev/m3blk (as I said I can't remember the exact filesystem name). I'd do a search for 'mount -o' on the forums. It's been posted more than once and I'm too lazy to find it for you

I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw

Yeah, I'm having the same problem as you sometimes. Other times it works. It's very strange! It annoys me. Anyone have any idea on a fix?

jubi23 said:
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Click to expand...
Click to collapse
Yeah that's the one, thanks.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Sounds like you've checked anything else I would have thought of...wish I could help.

Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Click to expand...
Click to collapse
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying

jubi23 said:
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
Click to expand...
Click to collapse
That could be it. ext4 doesn't play nicely with ext3 based stuff. It's 'semi' backward compatible (meaning you can mount ext4 as ext3) but it seems to have some serious inconsistencies that way. I'd recommend a re-partition and then upgrade ext3->ext4 AFTER you install the new ROM.
Heh. I had all KINDS of problems restoring an ext3 based nandroid after upgrading to ext4. Had to repartition and then restore the nandroid to get it to work.

well, loaded recovery, re-partitioned my sdcard, upgraded to ext3 and left it there, still nothing

the sd card wouldnt have any bearing on the ability to adb remount.
the /system partition is stored on the phone itself, so the mount -o ..yadda yadda
remounts the /system partition in this case /dev/block/mtdblock3.
the only reason a sd card would come to play is if youre runnign a2sd, in which case it makes symlinks (shortcuts) to the sdcard, if the sdcard is formatted improperly then a2sd will either cause a bootloop, or crash and then youre phone should boot normally but you wont have access to your ext4 partition (the partition with your apps).
im not sure how to fix a problem with adb remount, perhaps try a new version of the SDK or just a clean one.
good luck

I'm wondering if there is something wrong with my mounting
When i'm in the shell
if i cd /sdcard
then do a ls
nothing is returned
I've also directly copied the recovery image from my computer to the sdcard, and attempted to run the flash_image command and it says no such file or directory
I do have usb debugging enabled and am selected to mount the sdcard, is there some other step or something i'm missing?

nenn, i had actually just a little bit ago downloaded the latest sdk on a completely different machine and still same results

Alrite, so I was able to copy the image recovery from
explorer and flash from.terminal on my phone
Although I'd prefer to work from the pc, anyone have any other possible ideas?! I'm at a loss
-------------------------------------
Sent from my HERO200

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.

Galaxy Tab Internal SD Card Damage workaround

I used this hardware mod on all 50 of the tablets with great success. Just be careful to not remove any of the other little chips, I used heat to loosen the glue.
http://forum.xda-developers.com/showthread.php?t=1877585
Good luck
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse

Reference Material:
Fix for the P1000 - This is exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1711150
Fix for the Atrix 4G - Again, exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1766939
Another Example
http://forum.xda-developers.com/showthread.php?t=1463756&highlight=ics
Re-partition steps:
http://forum.xda-developers.com/showthread.php?t=845708 <- this did not work
Heimdall Suite re-partition with known good pit file <- This did not work

I'm on the exact same place, attempting the exact same, currently I was trying to edit vold.fstab as well as init.rc but it seems you have a better grasp of this.
I use a Sprint sph-p100, a CDMA version just like yours and as far as I know fully compatible with anything (save modem but I only use wi-fi).
I've tried your first link with a GB rom and failed (didn't pass first Samsung logo), but I will keep trying and post back anything I achieve.
If you indeed make a kernel or image that makes them boot please share it with us and I will GLADLY test it out.
I'm also aware that an easy solution is to open up the hardware and remove the internal SD Card (the kernel will assume the external is mmcblk0 instantly) but I dislike doing butchery and maybe breaking my device.

Chris... much progress has been made on this... first off. I am dumping the Gingerbread Verizon images for the CyanogenMod 9 Rc1 for P1c. I am currently following the kernel rebuild instructions from the device developer "cdesai" is working on. Those instructions are here:
http://forum.xda-developers.com/showpost.php?p=20162940&postcount=3
with repo setup here:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
With the instructions on how to build just the kernel I will modify the initramfs.list among other files to get the required results. What I will need to help you is do the exact same thing, just with the initramfs.list for your P100 device ??
Are you willing to use CyanogenMod 9? I have pretty much abandon Gingerbread unless someone can hook me up with a known working P1c Gingerbread git.

CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.

ChrisCTX said:
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
Click to expand...
Click to collapse
Mine is detected too. But fails when you try and fdisk is. I have several devices with the same results. If you want try to fdisk /dev/block/mmcblk0
Tell me if that eventually shows up as a 32mb disk with an empty partition
The correct commands are
adb shell
su
fdisk /dev/block/mmcblk0
p
q

Don't have a rooted rom on it now (can't really install anything besides flashing), but I tried it minus "su" and it didn't do anything at all.

Update the status. I have made the changes to support booting from the SDCard. For the first time I can mount the /data directory via the recovery. There is an install sequence that I haven't yet mastered. Will be in touch

Sounds great Jim, thanks for all the effort so far

I am waiting for the release of this. My tab internal SD crapped out also.

please help
im on the same boat if in need to take of the internal storage let me know i will do it just tell me some directions

Same issue
JimRich said:
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Hey guys I am having the same issues (as far as i can tell) with my Verizon Samsung Galaxy Tab SCH-i800. so the first issue is i tried to install a stock rom to fix a corrupted cache partition. now it tries to boot US Cellular. As of this moment the error i get when i put the device in recovery mode:
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
I am wondering if i can just create a new partition on a new SD card? i bought this device on ebay a couple weeks ago and i don't want to continue attempting sketchy leads for fear of hard bricking it. All help is greatly appreciated. I really don't want to give up on this thing because i feel like the soultion is out there... I am very good with performing commands via command prompt if that is nessasary, also i have access to an Ubuntu 12.4 computer if that would make things easier? Please help?
***Also as far as i know this is equipped with android Froyo and the issue developed after the previous user attempted to update. Please email me a reply or reply to my post.
Thanks,
-Andy

I switched to a hardware modification. This worked great!
http://forum.xda-developers.com/showthread.php?t=1877585

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!