Database Develop

Im a noob

Okay i'm sure ive become an annoyance in this section of the forum. I think i may have bricked my phone. This is what i did.
1. Unrooted myself and downgraded to RC29.
2. I formatted my sd card even though it already said fat32
3. Downloaded cyanogen recovery 1.4 image. And Hardspl and renamed it update.zip.
4. I connected to server 23 host in telnet and successfully typed in :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat cm-recovery-1.4.img > /system/recovery.img
5. The Hardspl part pretty much failed... i renamed it update.zip and downloaded it in recovery but once i hit reboot..it took me to recovery again and said : formatting cache:... and just stayed there. So i hit reboot again and it booted back to homescreen.
6. After this i figured i was rooted so i download cyanogen rom (http://forum.xda-developers.com/showthread.php?t=567610) and put it on my sd card.
7. I went to recovery and downloaded this zip file successfully.
My problem is: i can't get past the g1logo screen. I've tried reinstalling the rom and wiping data a couple times and it wont go past. Am i screwed?

okay nevermind this post i had to go to console and type in
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file to mount my sdcard so im goin back to RC29! may as well go to 1.6 til i can figure something out about rooting this is just ridiculous

kyram04 said:
okay nevermind this post i had to go to console and type in
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file to mount my sdcard so im goin back to RC29! may as well go to 1.6 til i can figure something out about rooting this is just ridiculous
Click to expand...
Click to collapse
anyway heres a website about how to root.....http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/

mount -a errors?

can anyone tell me why when i try the
Code:
mount -a
command i get the error
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Click to expand...
Click to collapse

Do you have an ext partition on your sdcard?

im sorry im mostly a noob when it comes to this... i just installed cyanogens mod, did not touch the sd card, let alone part it.

gooberguy said:
im sorry im mostly a noob when it comes to this... i just installed cyanogens mod, did not touch the sd card, let alone part it.
Click to expand...
Click to collapse
Then that is the reason you are getting that error, it is trying to mount the ext partition, which you do not have. Just ignore it and carry on

should i be ignoring though?
my cirucumstance is i'm trying to install apps2sd as well as deleting a battery stats file, both which instruct to use mount -a beforehand

gooberguy said:
should i be ignoring though?
my cirucumstance is i'm trying to install apps2sd as well as deleting a battery stats file, both which instruct to use mount -a beforehand
Click to expand...
Click to collapse
There is nothing to install for apps2sd, once you parition your sd card it's automatic
And as already mentions yes you can ignore the error, becuase it's telling you it can't mount /dev/block/mmcblk0p02 which means it can't access the 2nd partition on your sdcard, because you don't have one, so to delete batterystats.bin just use adb or console and
Code:
cd /data/system (enter)
rm batterystats.bin (enter)
and you're done

king

I would like to install the KiNgxKxKlair DroidEris2G1 v0.1 on my g1....I am not sure of the steps to install it though...I just purchased a 8gb class 6 card....My phone is rooted..Firmware 1.5....Baseband version 62.505.20.17h_2.22.1926I....Kernel Version 2.6.27-00392-g8312baf Jesusfreke spork#1....Build[/email] Number dream_devphone-userdebug 1.5 CRB43 148830 test-keys.......Please can someone help me with a step by step tutorial on how to get kings rom....PLEASE!!!!

Ok, this is pretty simple. Make sure your battery is near full. First thing you'll want to do is Download Amon_RA's latest recovery (carebears optional) and put it on the root of your SD card(not in any folder). Also copy king's v1.0 to the root of your SD card.
start the terminal app, and type this code:
$su
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img
#reboot recovery.
After this, your phone should shut off, and you will boot straight to recovery. Run a nandroid backup, then go to the wipe option and wipe everything. After you are backed up and wiped, click the apply any zip from SD card option, and select kings rom. Let it install (about 2 minutes), then reboot the phone(about 5-10 minutes til it boots up).
After this, you should be golden=p

Once your in recivery, you have to parition your sdcard before flashing the rom.
Select partition sd card.
96mb swap
512mb ext2
Fat32 the rest
When its done upgrade ext2 to ext3
When its done upgrade ext3 to ext4
Wipe data
Flash king rom

get 1.0 not 0.1

I am having a problem installing this King Rom....I installed the 1.6.2 recovery...I partitioned the card....wiped...and when i go to install king rom while copying it tell me cant chown/mod /system/xbin/nano
(no such file in directory)
e:failure at line 20:
set_perm 00 04755 SYSTEM:xbin/n

taino887 said:
I am having a problem installing this King Rom....I installed the 1.6.2 recovery...I partitioned the card....wiped...and when i go to install king rom while copying it tell me cant chown/mod /system/xbin/nano
(no such file in directory)
e:failure at line 20:
set_perm 00 04755 SYSTEM:xbin/n
Click to expand...
Click to collapse
Did you get the death spl and/or set up proper symlinks?

JAguirre1231 said:
Did you get the death spl and/or set up proper symlinks?
Click to expand...
Click to collapse
which is the death spl...i thought i had that already....how do u set up proper symlinks???

Turn phone off, turn it back on holding the Camera and Power button.
What does the screen you now see say, you need to know this info to know if DeathSPL is compatable.
and please be warned that flashing DeathSPL (DangerSPL) is known to cause bricks for some people, so you need to completly understand the risks before doing it.

mejorguille said:
Ok, this is pretty simple. Make sure your battery is near full. First thing you'll want to do is Download Amon_RA's latest recovery (carebears optional) and put it on the root of your SD card(not in any folder). Also copy king's v1.0 to the root of your SD card.
start the terminal app, and type this code:
$su
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img
#reboot recovery.
After this, your phone should shut off, and you will boot straight to recovery. Run a nandroid backup, then go to the wipe option and wipe everything. After you are backed up and wiped, click the apply any zip from SD card option, and select kings rom. Let it install (about 2 minutes), then reboot the phone(about 5-10 minutes til it boots up).
After this, you should be golden=p
Click to expand...
Click to collapse
when I insert mount -a It says no such files or directory

yeah that was the problem this whole time...I had the wrong spl...i thought i flashed it w while back but obviously i didnt...thankyou all for the help....lets see how this king rom is running

gmail is not working what did i do wrong????

Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -r /system
what does this code do....huh

taino887 said:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -r /system
what does this code do....huh
Click to expand...
Click to collapse
I wouldnt do it if i were you, depends on how keen you are to reinstall your rom.

[Proof of concept] Everything2SD

The basic idea of this mod is moving all partitions to the SD card, and running the full OS from the SD card.
There are many reasons why not to do this and probably is a bad idea, but the main reason behind this mod is just a proof of concept that can potentially result in a better internal and external memory utilization and speed improvements.
Reasons I can think of for not doing this:
- Reduced responsiveness and overall speed.
- Over stress on the SD card that can potentially leed to permanent damage to the card.
- The need to use modified boot and recovery images, thus leading to an install incompatible with any rom update (as it is) out there.
- Reduced battery autonomy.
- Many more I can't think of right now.
Reasons to do this:
- Because we can.
- As a proof of concept.
- For developing purposes.
- We get the ability to switch between 2 installations just by switching the SD card (of the same rom or roms with compatible boot images: kernel+ramdisk).
Don't do any of this if you don't know what you are doing!!!
Simplified steps (I've only tested this with Mik's CM7 (betas 6.2 and 6.3) + ClockWorkMod recovery on a Ubuntu machine):
- Download and flash ClockWorkMod recovery.
- Download and flash Mik's CM7.
- Do a full backup from recovery.
- Turn the phone off.
- Take out the SD card and put it on a Card reader on your PC.
- Backup the SD Card contents (including the full backup).
- Use Gparted (or any partition manager that has support for ext4 partition creation) to create the following partition structure:
Code:
num mount point size type
1: /sdcard REST fat32
2: /data 500M ext4
3: /system 190M ext4
4: /cache 64M ext4
The partition number is important, so you should calculate the fat32 partition beforehand or resize the existing one.
- Put new boot and recovery images on the fat32 partition. *
- Put the card on the phone and boot into recovery.
- Mount the sdcard trough menu.
- Connect the phone to your pc and start adb shell.
- Flash custom boot and recovery images:
Code:
flash_image boot /sdcard/boot-everything2sd.img
flash_image recovery /sdcard/recovery-everything2sd.img
- Reboot recovery.
- Through menu, mount all partitions.
- Connect trough adb shell and copy your data:
Code:
adb shell
cp -a /int-cache/* /cache/
cp -a /int-system/* /system/
cp -a /int-data/* /data/
- In adb shell, remove the sd_ext mount script:
Code:
rm /system/etc/init.d/05mountsd
- Reboot the phone.
Off course, no other method of storing the apps on the SD is desired as they are already there.
* I've attached custom boot and recovery images for Mik's CWM and CM7 beta 6.2 (updated boot images to Mik's CM7.02 beta 6.3 in post #3), but, the steps for creating them are next:
- Extract the original images (boot.img and recovery.img) from the root of the downloaded zips (signed-recovery.zip and cyanogen_thunderg-ota-eng.mik.zip).
- Unpack the images following this guide: HOWTO: Unpack, Edit, and Re-Pack Boot Images: Alternative Method (Perl scripts are attached, you'll need compiled mkbootfs and mkbootimg for your OS).
- On recovery ramdisk, change the etc/recovery.fstab file as follows:
Code:
# mnt pnt fstype device [device2] [fstype2]
/boot mtd boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p2
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 ext4
/system ext4 /dev/block/mmcblk0p3
/int-cache yaffs2 cache
/int-data yaffs2 userdata
/int-system yaffs2 system
- On boot ramdisk, change the init.rc file as follows (diff output):
Code:
[email protected]:~/Descargas/bootimages$ diff boot.img-orig_ramdisk/init.rc boot.img-ramdisk/init.rc
22d21
< export SD_EXT_DIRECTORY /sd-ext
68,69d66
< mkdir /sd-ext 0771 system system
<
100,103c97,100
< mount yaffs2 [email protected] /system
< mount yaffs2 [email protected] /system ro remount
< mount yaffs2 [email protected] /data nosuid nodev
< mount yaffs2 [email protected] /cache nosuid nodev
---
> mount ext4 /dev/block/mmcblk0p3 /system
> mount ext4 /dev/block/mmcblk0p3 /system ro remount
> mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev
> mount ext4 /dev/block/mmcblk0p4 /cache nosuid nodev
- Recreate the ramdisks and images following the guide posted above, changing the mkbootimg command line to (notice the base and cmdline parameters; for recovery, change boot to recovery on all instances):
Code:
mkbootimg --base 0x12800000 --cmdline 'mem=471M console=ttyMSM2,115200n8 androidboot.hardware=thunderg' --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz -o boot-new.img

Ahaha another sleepless night ahead to test this out. Any Quadrant Advanced I/O score for comparison?

I've updated boot images to Mik's CM7.02 beta 6.3, attached below.
I'm going to run a Quadrant Advanced and let you know. Anyway, I don't think I will get good results, as my SD card is cheap and buggy, half the time it doesn't get mounted, with or without this mod. Also, I think we'll get better scores with your tweaks, especially with the modded libsqlite.so.
The idea behind this is not to get impressive results or leave it as a definitive mod (as it is right now). Instead, the idea I have is to start moving some things back to the internal memory, for instance, mounting [email protected] as /data/dalvik-cache (just an idea). Basically, leaving the things that need fast reading times, but infrequent writes in the SD, and the things that are constantly being written to, in the internal memory.

Seems awesome. I already booted up perfectly with the modded .imgs, no issues.

so what class of sd card do you preffer?
still class 4 above?
well, sorry about what im going to say , but if **** happened and luckily sd card got corrupted, then the phone does as well?
ive not read all of your first post,
but if ever we are changing sd cards, like example upgrading from 4g-8g,
is it necessary to repeat the whole process or copy paste is enough?(i bet not due to ext)

cmangalos said:
so what class of sd card do you preffer?
still class 4 above?
well, sorry about what im going to say , but if **** happened and luckily sd card got corrupted, then the phone does as well?
ive not read all of your first post,
but if ever we are changing sd cards, like example upgrading from 4g-8g,
is it necessary to repeat the whole process or copy paste is enough?(i bet not due to ext)
Click to expand...
Click to collapse
If **** happened you could mount it in a computer with a card reader and perform a disk check + recovery. If the sd card broke, well.. I think there's still hope, since you may boot in recovery and replace the mount points back to the internal memory ( right ? )
As for the storage upgrade, well, it's not exactly copy-paste but you should be able to duplicate the partitions without much hassle..

I really like this idea,we could get 3000+ quadrant score
But can be potentially dangerous. If anything goes wrong i think that Phone can't boot anymore.

how abt two separate roms in 6 separate partitions ???? is the bootloader cracked ??? Can we have a grub like menu to select two roms ???Way 2: Maybe somebody cud mod android's initramfs and add options there to select two different fstabs ...just a thought

a dual boot would be cool... one rom on the internal nand memory and the other on SD card...

Having fastboot disabled is such a pain in the ass...

ciaox said:
I really like this idea,we could get 3000+ quadrant score
Click to expand...
Click to collapse
Not me, because my SD card is very buggy. Anyway, it depends very much on the card, the card reader and the kernel. Anyway, it's just a proof of concept and it opens a great window for experimentation.
ciaox said:
But can be potentially dangerous. If anything goes wrong i think that Phone can't boot anymore.
Click to expand...
Click to collapse
Not at all, recovery can boot even if the SD card is damaged or not present. Then you can flash the original recovery, boot it and flash any ROM without this mod.
Steps:
- Extract recovery.img from your desired custom recovery.
- Boot recovery.
- Mount /int-cache from mounts and storage menu.
Code:
adb push recovery.img /int-cache/recovery.img
adb shell
flash_image recovery /int-cache/recovery.img
- Reboot recovery
- Flash desired ROM from any SD card.
OR: Just flash an original (released by LG) ROM through emergency mode.
sarfaraz1989 said:
how abt two separate roms in 6 separate partitions ???? is the bootloader cracked ??? Can we have a grub like menu to select two roms ???Way 2: Maybe somebody cud mod android's initramfs and add options there to select two different fstabs ...just a thought
Click to expand...
Click to collapse
Bootloader isn't cracked yet, so it would have to be implemented on the boot.img (kernel and/or ramdisk), and I don't know how. Right now is easier to swith SD cards. Anyway, ROMs should be able to share boot.img (kernel + ramdisk).
ciaox said:
Having fastboot disabled is such a pain in the ass...
Click to expand...
Click to collapse
+1. But bootloader isn't cracked yet.

Just a little heads up, but if anyone is paying attention to the Nook Color development, this is exactly how the boot process on that device works, I am running one os off the sd card and if I remove it I am back to stock. The main point of my brining this up is you create the sd card with all it's partitions by flashing an image of the sd card with the WinImage application on windows. Might at least save you some steps. Hope this helps.

tsukisan said:
Just a little heads up, but if anyone is paying attention to the Nook Color development, this is exactly how the boot process on that device works, I am running one os off the sd card and if I remove it I am back to stock. The main point of my brining this up is you create the sd card with all it's partitions by flashing an image of the sd card with the WinImage application on windows. Might at least save you some steps. Hope this helps.
Click to expand...
Click to collapse
Possibilities seem to be limitless.
Sent from my LG-P500 using Tapatalk

Soft Brick pt7310? can't mount /data - /sdcard , bootloop

hi everybody.
yesterday i have flashed my p7310 from stock honeycomp to cm10.1-experimental.
descriped here: http://forum.xda-developers.com/showthread.php?t=2060530
works good, just the strange screen flickering after wakeup from standby.
see here: http://forum.xda-developers.com/showthread.php?t=1989398&highlight=wakeup
because this I tried to reflash it with GT-P7310_XAR_P7310UELA3.
descriped link above.
now I'm in a bad state.
actually cwm 5.5.0.4 is installed.
if I try to boot my rom it loops at samsung logo.
if I select "wipe data/factory reset" in cwm I get:
-- wiping data...
formatting /data
error mounting /data!
skipping format...
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure...
error mounting /sdcard/.android_secure!
skipping format...
data wipe complete
I have tryed to install stock rom P7310XXLPO_P7310XEULPO_XEU.zip via odin. install works, bootloop
installed ClockworkMod_Recovery_v5.5.0.4.tar via odin. install works
repartitioned via odin (p5_0614.pit) and install stock rom, install works, but still bootloop.
if i connect via adb i can push Clockwork_Recovery_6.0.0.8_GT-P7310.zip to /sdcard, but no access via cwm and "choose zip from sdcard". error: E: can't mount /sdcard/
if i list files via adb shell from /sdcard and /data there are no files.
can somebody help me?
greetz from germany
mitch
one more info.
in adb shell, if i try to mount /data manually, i get following message:
[email protected]:/ # mount /data
mount /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
i assume that this blk device has no filesystem. but how can i format it manually?

ok... i solved it.
who want's to know how i solved:
i formated /data with ext4 via adb shell.
[email protected]:/system/bin # /system/bin/make_ext4fs /dev/block/mmcblk0p8
where /dev/block/mmcblk0p8 is my /data (according to the fstab)
after that i was able to mount /data !!!
i flashed cwm 5.5.0.4 again via odin, flashed (odin) stock rom (works now!)

It seems that I have a similar (if not exactly the same problem). Problem is, I'm not exactly tech savvy enough to
understand/execute your solution on my own.

mitchgehtab said:
ok... i solved it.
who want's to know how i solved:
i formated /data with ext4 via adb shell.
[email protected]:/system/bin # /system/bin/make_ext4fs /dev/block/mmcblk0p8
where /dev/block/mmcblk0p8 is my /data (according to the fstab)
after that i was able to mount /data !!!
i flashed cwm 5.5.0.4 again via odin, flashed (odin) stock rom (works now!)
Click to expand...
Click to collapse
Can you tell us how you go about formatting your SDCARD? I have a similar problem and can't mount E: data/ whenever I try TWRP or CWM recoveries on my p7300. Can you give us step by step or at least a link where to start. Sorry, I am not familiar with ADB.
Thanks for your support with this tab.

mjramos15 said:
Can you tell us how you go about formatting your SDCARD? I have a similar problem and can't mount E: data/ whenever I try TWRP or CWM recoveries on my p7300. Can you give us step by step or at least a link where to start. Sorry, I am not familiar with ADB.
Thanks for your support with this tab.
Click to expand...
Click to collapse
Try to install a new twrp recovery using the following instructions. That fixed it for me:
http://forum.xda-developers.com/showthread.php?t=2602188