Database Info

recovery mode not working

Ok, so I was trying to reflash the modified rc30 update to start from scratch because when trying to do the auto rotate browser tweak I kept getting the not enough space message. I rebooted into recovery mode thinking all I had to do was run the update and it didn't do it. I thought maybe I needed to reflash the modified recovery image so I did that, but now when I reboot into recovery mode I get the G1 logo and then a blank screen. I tried pushing home+back to restart and get nothing. So I used adb to push the recovery image on the device and I get "no space left on device" Tried doing a factory reset and it hangs up on a blank screen there too. can I just wipe the data partition to fix it then reflash the recovery image to the device? The phone works fine, I just can't do anything with recovery. Can someone help me out here in getting back recovery mode? Thanks

When you tried to push the recovery image, did you do so to the sdcard?
I am referencing these pages:
http://android-dls.com/wiki/index.php?title=Keeping_Root
http://code.google.com/android/reference/adb.html

Just remount /system as rw and adb push the recovery.img directly in. Also, if you have the engineering bootloader installed, you could try using fastboot to reflash the recovery partition from the bootloader.

doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?

jdwme said:
doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?
Click to expand...
Click to collapse
If you're on RC30 v1.2 put the recovery.img in /data not /system

so then my it should look like this?
mount -o remount,rw /dev/block/mtdblock3 /data
cd /data
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img

jdwme said:
so then my it should look like this?
mount -o remount,rw /dev/block/mtdblock3 /data
cd /data
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img
Click to expand...
Click to collapse
mtd3 is system. mtd5 is userdata. Don't execute that first step! userdata partition is rw anyway. Just start with step 2.

ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data

jdwme said:
ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data
Click to expand...
Click to collapse
Not sure. What do you get if you type mount with no args in the terminal emu?

nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?

jdwme said:
nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?
Click to expand...
Click to collapse
Really? What it should do is return a list of mounted devices, like so (this is a Mod RC30 v1.2 device):
Code:
# mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/loop0 on /system/modules type cramfs (ro)
/dev/block/loop1 on /system/xbin type cramfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8)
Stock bootloader can't be used to flash images to the mtd partitions.

ok i misunderstood, i did type just mount now and it shows what you posted. could i have two modified recovery images on there and it cant pick one so thats causing the problem?

Did you change directory to /data? If you can't get it to work from the terminal, as long as you have the recovery.img in /data, just power the G1 off completely and power it back on. It automatically writes the recovery partition every time you cold boot.
Btw make sure that in the mount report the following two lines read exactly as such:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)

yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.

jdwme said:
yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.
Click to expand...
Click to collapse
On your cold reboots were you seeing the flashing screen (arrow onto chip) before booting into Android?

nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode

jdwme said:
nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode
Click to expand...
Click to collapse
Are you sure you have the recovery.img in the /data directory? Strange. Maybe someone else has some ideas about whats going on here?

So I decided to show all my partitions listed on the system using cat
/proc/partitions and this is what I got. Does this look normal? Not sure
what it looks like on anyone else device
major minor #blocks name
7 0 2248 loop0
7 1 3176 loop1
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 69120 mtdblock3
31 4 69120 mtdblock4
31 5 76544 mtdblock5
179 0 7977472 mmcblk0
179 1 7973376 mmcblk0p1
I pushed it to the data directory before, followed the instruction thread, but using oi file manager recovery.omg shows in system, nothing shows in data

so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader

jdwme said:
so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader
Click to expand...
Click to collapse
Give me an IM if you want. I may be able to help fix your recovery mode. (debugging things like that is such a pain on a forum. real-time is much easier)

[06/06/09] Haykuro 6.0r1 boot.img with atime+ext3 mod (and now hero)

Well, there was a lot of chatter today about the speed increases on cyanogen's JF-1.51 ROM today, attributed to some changes in the ramdisk (see below). Attached is a boot.img with the same modifications but for Haykuro's 6.0r1 build - go ahead and download it now or read on for more details. Note: you'll only notice a difference if you run your apps/cache from your SD card.
The Changes
The only change is to mount your SD card's ext2 partition with the 'noatime' option. This is exactly what cyanogen did in his JF build, as per his post here. I also added the 'nodiratime' option. This is merely a very minor change in the runme.sh script of the boot ramdisk. [See below for more info on the ext3 mod, added 05/27/09]
By default, ext2 maintains the last access time ('atime') of every file and directory in the filesystem. This means that every time you access (read or write to) a file, this time will be reset and you'll be writing to your SD card. Two problems: 1) SD cards are slow as it is; requiring a write every time you access a file is going slow your whole system down. 2) SD cards fail after enough writes to the same location, so you're reducing your card lifetime by not having these options.
ext3 'auto' mod
Cyanogen added this to his latest build, so again, merely making this available for Haykuro 6.0r1 users. He wrote a bit more detail here which is working reading too.
In short: No other ROMs or app2sd solutions handle a clean shutdown of the ext2 partition, and Android doesn't have fsck tools. The result is that shutting down or crashing can corrupt your ext2 partition and you can lose data. Meanwhile, ext3 is a journaling file system; it recovers gracefully from unclean shutdowns. It's also backwards compatible, you can still mount an ext3 as ext2, you just lose journaling capability.
The mod mounts the 2nd SD partition as type 'auto', which means it will read your existing partition as ext2 and in the future as ext3 if you upgrade. This is more for advanced users but I'll try post some simple instructions below. Make sure you download the boot-haykuro-6.0r1-atime-ext3.zip image.
What about hero? (added 06/06/09)
This is a modded kernel 2.6.29 with unionfs support from daproy. Besides the atime+ext3 stuff, by request I also added support to run /system/init.rc and /data/init.rc (needed by some scripts).
http://turtle.wastelands.net/dragon/...uto-initrc.zip
See also:
1) Daproy's release: http://forum.xda-developers.com/showthread.php?p=3905574#post3905574
2) Release in this thread: http://forum.xda-developers.com/showpost.php?p=3909682&postcount=10
Note: you also need to
1) adb remount
2) push wlan.ko /system/lib/modules
How to apply
Download and unzip the file to get your new boot.img
Option 1:
Code:
adb push boot.img /sdcard
adb shell
# cat /dev/zero > /dev/mtd/mtd2 write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
(or mount your SD card, copy the image, and run the above commands in a terminal).
Option 2:
1. Boot into fastboot mode (boot with power+camera)
2. fastboot flash boot boot.img
How to check if it's working
Type 'mount' in an adb shell or your phone's terminal, and look for the 'noatime' and 'nodiratime' option on your ext2 mount point. (If you go ahead with the ext3 mod and upgrade, you'll see it will show up as ext3 in the mount list below).
Code:
$ adb shell
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,[b]noatime,nodiratime[/b],errors=continue 0 0 <--
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0
If things go wrong
If for some reason you can't boot after trying this, you can restore your system simply by reapplying Haykuro's image (boot with power+home and alt-s). Alternatively, I'm attaching the original boot.img as well, which you could reflash with option 2 above.
How to upgrade your ext2 partition to an ext3
I found this really easy on Linux. People can write about alternative methods, but this worked great for me: (substitute /dev/sdb2 below as necessary)
1. Connect to USB and mount your SD card in Android
2. Unmount your ext2 partition from inside linux (e.g. sudo umount /dev/sdb2)
3. sudo tune2fs -j /dev/sdb2 (this adds a journal to the filesystem)
4. adb shell, reboot (or just reboot phone without tapping 'turn off USB storage')
Even though I found this really simple and didn't even bother to make a back up first, I'm really familiar with Linux and linux filesystems -- this should be considered advanced use, and I'm not responsible for you losing your entire ext3 partition.
Note - I agree with cyanogen; I don't think the journal writes is a big performance impact or will wear out your card. This is a relatively small amount of extra data on each write... very low performance/wear impact and for me very worth the benefits.
References
1. Original launch thread of cyanogen's JF 1.51 build
2. Boot Image how to referenced by cyanogen's post
I'm also attaching my compiled versions of mkbootfs and mkbootimg in case anyone wants to play around without downloading and compiling the 2.3 GB Android source.

Worked like a charm thanks man!

This worked perfectly for me! Great job on this; noticable speed improvements for me

Not a great improvement.. Apps are starting circa a second faster..

anyone try this or have a method for Haykuro's Hero build?

boot.img for JACHero r1.4
jroid said:
anyone try this or have a method for Haykuro's Hero build?
Click to expand...
Click to collapse
Which build? I think beta 4 is out yes? I haven't moved over to Hero yet because of the bluetooth issue. Nevertheless, I just made a boot.img for JACHero1.4 - it's untested, but can't imagine it giving any problems... you can always just reapply the update.zip if things go wrong (I still take no responsibility though ). It will probably work with the recent hero builds, let me know how it goes.

I was reffering to the official build he dropped w/ rosie.
thanx I'll give it a shot

confirmed. works on hero build.
very noticeable speed improvement. thanks
# cat /dev/zero > /dev/mtd/mtd2 write: No space left on device
cat /dev/zero > /dev/mtd/mtd2 write: No space left on device
write: No space left on device
# flash_image boot /sdcard/boot.img
flash_image boot /sdcard/boot.img
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0
# reboot
reboot
C:\>adb shell
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0
#
Click to expand...
Click to collapse

confirmation #2 it works on hero w/ Rosie

From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
daproy said:
Ok I reverted the recent commits to the 2.6.29 tree and camera works fine again and I patched in UnionFS. Sorry for the mess guys. I guess it shows I should have tested it before uploading. I put the kernel zImage in there separate as well in case people wanted to make their own boot.img
http://drop.io/tgbvqky
Click to expand...
Click to collapse
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip

Kinslayer81 said:
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Click to expand...
Click to collapse
Hey thanks for the new kernel package.
Simple question.
I had now problem fastbooting the boot.img or adb pushing the wlan.ko but what do I do with the kernel file? Anything, or is it just there in case I want to make changes to the boot or wlan.ko files?

Ext3 on flash media drastically reduces the lifetime because of the frequent writes to the journal, a simple search on google brings up tons of things against the idea, yaffs2 or jffs would be a better decision because it is optimized for flash media and has a journal, not everyone has a class 6 sdhc, and ext3 will cause curruption in any lower class sd, and it will reduce a class's lifetime as well, there is plenty of docs and specs on this, if u prefer speed over reliability/sd lifetime have fun

defconoi said:
Ext3 on flash media drastically reduces the lifetime because of the frequent writes to the journal, a simple search on google brings up tons of things against the idea, yaffs2 or jffs would be a better decision because it is optimized for flash media and has a journal, not everyone has a class 6 sdhc, and ext3 will cause curruption in any lower class sd, and it will reduce a class's lifetime as well, there is plenty of docs and specs on this, if u prefer speed over reliability/sd lifetime have fun
Click to expand...
Click to collapse
This has been discussed ad nauseam.
Even in average high use (compiling the linux kernel!), ext3/journalling with the noatime option results in LESS THAN A 4% INCREASE IN WRITES. Even an abnormal case ('make clean' on the linux kernel, i.e. deleting literally thousands of files) maxed out at a 40% increase, which for deletes really isn't such a big deal. http://thunk.org/tytso/blog/2009/03/01/ssds-journaling-and-noatimerelatime/
Yaffs2, etc, ARE WORSE FOR YOUR SD CARD, which implements it's own hardware anti wear levelling. If you have the hardware and software both swapping around locations, you're doing more work, making things slower, and shortening the life of your card. Flash file systems are contra indicated for SD and other such media.
And it's not about preferring speed over reliability. Ext3 will be slightly slower than ext2, but it's definitely more reliable, because when you shut down, your phone crashes or something else goes wrong, it can recover gracefully instead of YOUR EXT2 PARTITION BECOMING CORRUPT and you losing your data.
I hope this issue is closed now.

ccyrowski said:
Hey thanks for the new kernel package.
Simple question.
I had now problem fastbooting the boot.img or adb pushing the wlan.ko but what do I do with the kernel file? Anything, or is it just there in case I want to make changes to the boot or wlan.ko files?
Click to expand...
Click to collapse
Yea I did the steps with the boot.img and wlan.ko and it appears to be working (noatime and nodiratime are showing). But whats the deal with the kernal file?

sacredsoul said:
Yea I did the steps with the boot.img and wlan.ko and it appears to be working (noatime and nodiratime are showing). But whats the deal with the kernal file?
Click to expand...
Click to collapse
It was included by daproy for ROM developers. I just left it in there to provide the complete package. You can safely ignore it

Kinslayer81 said:
It was included by daproy for ROM developers. I just left it in there to provide the complete package. You can safely ignore it
Click to expand...
Click to collapse
Ah. Thanks man! Enjoying my speedy JACHero Optimized build with this boot.img.

i pushed the wlan and use fastboot to flash the boot.img but when i check with the "mount" command it shows :
i'm using Jac's ROM
/dev/block/mmcblk0p2 /systemsd ext2 rw,errors=continue 00
instead of this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0

I get a wifi unable to start.
ifconfig tiwlan0 in Terminal returns No such device. Any help guys? Yes I tried rebooting already.
EDIT: Posted this on JACHero thread too. Posting here to get more response...
adb remount
adb push wlan.ko /system/lib/modules
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Shanker>cd C:\android-sdk-windows-1.5_r1\tools
C:\android-sdk-windows-1.5_r1\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r1\tools>adb push wlan.ko /system/lib/modules
1117 KB/s (676043 bytes in 0.591s)
C:\android-sdk-windows-1.5_r1\tools>
Click to expand...
Click to collapse
I rebooted and I still cant start wifi. Btw I am using the kinslayer81 boot.img for JACHero 1.4...

namsir said:
i pushed the wlan and use fastboot to flash the boot.img but when i check with the "mount" command it shows :
i'm using Jac's ROM
/dev/block/mmcblk0p2 /systemsd ext2 rw,errors=continue 00
instead of this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
Click to expand...
Click to collapse
i got the samething.... when i check to see if its working with "mount"
it doesnt show the noatime, nodiratime :\

Kinslayer81 said:
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Click to expand...
Click to collapse
can we do aufs/unionFS on Haykuro's original hero build? I've got the new boot.img and wlan.ko and ext3 FS, just wondering what I would need to do.

[HELP] Phone F****D after XXLE4

i just updated to XXLE4 yesterday from cm9
followed the usual process KPE(twice)>XXLE4(twice)
everything was working well but after a reboot i got nasty hangups so i switched off and put my phone in charging
i removed from charginig an hour later and switched on
the phone went to recovery said DELETING CRYPTION DATA and rebooted
since then it showed NO SD CARD in file manager, and UNKNOWN in settings for both internal sd and external sd
i tried factory data reset and wiping partition cache , but i got boot loop
also everytime in recovery it said copying media files
i tried reflashing XXLE4 but again boot loop
i finally flashed full kpe but again boot loop
in recovery this is what the dialogue is
E:failed to mount /data (no such file or directory)
--copying media files...
E :failed to mount /sdcard (file exists)
E :copy_cache_media :cant mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions.
Media file copy failed
and the rest was usual manual mode
applying multi csc.....
when wiping data it says
--wiping data..
formatting /data...
E:format_volume : rfs format failed on /dev/block/mmcblk0p3
formatting /dbdata..
formatiing /cache..
data wipe failed
also i inserted my external sd card in my pc to check and it showed 11.7 of 11.7gb free
whereas it was about 9gb full and is and 16gb card
so is my sd card f****ed too ?
so is this real bad like service centre bad(no warranty)?
any solutions?

try flash a .pit to make a repartition, and then try flashing a froyo stock rom, then ginger / value pack ginger

frapeti said:
try flash a .pit to make a repartition, and then try flashing a froyo stock rom, then ginger / value pack ginger
Click to expand...
Click to collapse
i tried with the pit file of xxkpe and flashed xxkpe but again i got boot loop
you are saying i use the pit file of xxkpe(ginger) and flash a froyo rom?

Now this is called a soft brick (no service center needed), but the fact that all these issues even after reflashing xxkpe are still there is worrying.
Are you sure you are doing all the steps correctly?
Try xxkpe with .pit (twice - the pit part once) --> XXKPQ
If that doesn't work then i can't help any further.

Skander1998 said:
Now this is called a soft brick (no service center needed), but the fact that all these issues even after reflashing xxkpe are still there is worrying.
Are you sure you are doing all the steps correctly?
Try xxkpe with .pit (twice - the pit part once) --> XXKPQ
If that doesn't work then i can't help any further.
Click to expand...
Click to collapse
yes pretty sure i followed everything correctly
but no success
now i am really worried

akashsgpgi said:
yes pretty sure i followed everything correctly
but no success
now i am really worried
Click to expand...
Click to collapse
E:format_volume : rfs format failed on /dev/
block/mmcblk0p3
From this line I can say that I think ur internal sd card is broken which is really a serous issue. But I have flashed my phone 100 times but flashing never causes curruption of internal sd card.

akashsgpgi said:
i tried with the pit file of xxkpe and flashed xxkpe but again i got boot loop
you are saying i use the pit file of xxkpe(ginger) and flash a froyo rom?
Click to expand...
Click to collapse
I think there's only one .pit file... but i can confirm that doing a flash of Froyo, then into GB, can fix some issues. I haven't had this problem in particular, though.

boot loop with froyo
any idea how much will the repairs would cost in india

Try hard reset dude.. samseng service center is the last resort
Sent from my GT-I9003 using XDA

Ave666 said:
Try hard reset dude.. samseng service center is the last resort
Sent from my GT-I9003 using XDA
Click to expand...
Click to collapse
by hardreset u mean factory data reset+wiping cache partition?
or reflashing xxkpe with?
i have tried both
even tried froyo

Are you still able to boot into recovery or download mode.
If yes, then you still have some chance to recover your device, yourself.
As a last resort consider doing this.
If you could boot into download, then install any custom Kernel, so as to have root priviledge
and a good bash environment in recovery.
Now boot into recovery and check filesystem type of each partition, if it is correct.
And then try formatting them by yourself.
Here is my partition table information. (for Cyanogenmod9 alpha6 ROM)
Code:
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 248564 32 248532 0% /dev
df: /mnt/.lfs: Function not implemented
/dev/block/stl11 31484 4148 27336 13% /cache
tmpfs 248564 0 248564 0% /mnt/asec
tmpfs 248564 0 248564 0% /mnt/obb
/dev/block/stl9 326552 270852 55700 83% /system
/dev/block/mmcblk0p3 1935128 257784 1677344 13% /data
/dev/block/stl10 74072 4148 69924 6% /dbdata
/dev/block/stl3 6064 5155 909 85% /efs
/dev/block/vold/179:17
3870240 3794432 75808 98% /mnt/emmc
/dev/block/vold/179:1
1595136 1340832 254304 84% /mnt/sdcard
/dev/block/vold/179:1
1595136 1340832 254304 84% /mnt/secure/asec
/dev/block/dm-0 6236 4424 1812 71% /mnt/asec/com.teamviewer.teamviewer.market.mobile-2
/dev/block/dm-1 6236 4508 1728 72% /mnt/asec/com.natenai.glowhockey-2
1|[email protected]:/ # mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
/dev/block/stl11 on /cache type ext4 (rw,nodev,noatime,nodiratime,commit=20,barrier=1,nobh,data=ordered,noauto_da_alloc)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type ext4 (ro,noatime,commit=20,barrier=1,nobh,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p3 on /data type ext4 (rw,noatime,commit=20,barrier=1,nobh,data=ordered,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,commit=20,barrier=0,nobh,nodelalloc,data=ordered,noauto_da_alloc)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
debugfs on /debug type debugfs (rw,relatime)
/dev/block/vold/179:17 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.teamviewer.teamviewer.market.mobile-2 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.natenai.glowhockey-2 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
[email protected]:/ #
akashsgpgi said:
by hardreset u mean factory data reset+wiping cache partition?
or reflashing xxkpe with?
i have tried both
even tried froyo
Click to expand...
Click to collapse

yes i will try a custom kernel as soon i return from school

i tried to recover using cwm recovery but it did not work
any idea how much would it cost for repair at samsung service centre
my pocket money is roasted

akashsgpgi said:
i tried to recover using cwm recovery but it did not work
any idea how much would it cost for repair at samsung service centre
my pocket money is roasted
Click to expand...
Click to collapse
u need to change motherboard.

vishal24387 said:
u need to change motherboard.
Click to expand...
Click to collapse
any idea vishal bhaiyya how much that would cost ox10)

akashsgpgi said:
any idea vishal bhaiyya how much that would cost ox10)
Click to expand...
Click to collapse
No idea buddy. But surely it is really costly. But I will say that try in every possible way. I think in general section there is a thread regarding solution for this. May 3-4 pages back u will get that thread.
Edit :---
This will help u
http://translate.google.com/transla...es/2012/05/la-resurreccion-del-i9003.html?m=1
Try this also
http://forum.xda-developers.com/showthread.php?t=1241574

vishal24387 said:
No idea buddy. But surely it is really costly. But I will say that try in every possible way. I think in general section there is a thread regarding solution for this. May 3-4 pages back u will get that thread.
Edit :---
This will help u
http://translate.google.com/transla...es/2012/05/la-resurreccion-del-i9003.html?m=1
Try this also
http://forum.xda-developers.com/showthread.php?t=1241574
Click to expand...
Click to collapse
thank you , tomorrow i try my best and as always will revert to xda for any help require
after panicking now i am relaxed

abaout hard reset. Its not just factory data reset. Open up your case, in the middle of the camera and the speaker there is soo tiny hole. You use hairpin or any pointed material to push it. Just read in an article before i forgot. Try it. Not bad for trying for yours is already soft bricked. Just try.\\
EDIT- i forgot the real step but that is the hard reset i think FOR THE READERS PLEASE CORRECT ME IF IM WRONG JUST TRYING TO HELP THE GUY with all the possibilities. Try it with power on/off or while pushing both home or power i dont know try everything with this button.
I remembered it, pushing it while doing the download mode combo.

akashsgpgi said:
i tried with the pit file of xxkpe and flashed xxkpe but again i got boot loop
you are saying i use the pit file of xxkpe(ginger) and flash a froyo rom?
Click to expand...
Click to collapse
the .pit file is the same for any rom, I think it just have info about the partitions and how to do them, just flash latona_20110114.pit, remove the battery, and then, make sure u have a working stock rom, I use XXKC1 ie, if it stills with errors I think its a serious issue

frapeti said:
the .pit file is the same for any rom, I think it just have info about the partitions and how to do them, just flash latona_20110114.pit, remove the battery, and then, make sure u have a working stock rom, I use XXKC1 ie, if it stills with errors I think its a serious issue
Click to expand...
Click to collapse
Everyone said that already, if you have something new to add, go on, if everything is already said, don't post..

TWRP cannot mount /data; nothing 'sticking' using fastboot

Hi all,
hoping on the off-chance someone's still monitoring the Nexus 5 forums here
So decided to dust off the old Nexus 5 (now with extra COVID-19 time on my hands!) to use as a backup device, but having serious issues getting it up and running. I had it rooted years ago, and had no issues installing custom roms.
Now I'm having the following situation:
I cannot flash the factory image using fastboot, nor anything is 'sticking' to the phone when I try to re-flash individual component for the factory image. I've also tried to flash TWRP, but again, it doesn't stick and the only way i can boot into TWRP is by using
Code:
fastboot boot recovery.img
.
However in recovery, the data partition is not mounting and all the tutorials/guides I read about fixing it aren't working (e.g. repairing the partition-- get a 'unable to repair data' error; changing from EX4 to EX2 and back-- get 'failed to mount '/data' error).
Ran the following command in the terminal window in TWRP
Code:
cat /etc/fstab
and got the following output:
Code:
/dev/block/mmcblk0p25 /system ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/mmcblk016 /persist ext 4 rw 0 0
/dev/block/mmcblk0p1 /firmware vfat rw 0 0
/usb-otg vfat rw 0 0
tried using the make_ext4fs command, but again- nothing happens.
Using TWRP 3.3.1-0 by the way
Any ideas? is the phone completely bricked? it's stuck in a bootloop where the google colours come up but freeze within half a second, repeat and continue.
Any advice would be very much appreciated!

Question Device bootlooping after installing the April 2nd LOS for microG release on bluejay.

Hey everyone, My phone started bootlooping after I installed the LineageOS for microG 402-nightly image. I forgot to disable magisk before updating, and after I rebooted it just started bootlooping until I was kicked into LOS recovery. Trying to reflash the older image resulted in a `kInstallDeviceOpenError` (the infamous error 7), and so did the new one. I tried everything, from flashing different versions of boot.img from different releases and from both los for microG and official los, to even trying to reflash vanilla, but nothing worked, and trying to mount any partition from /dev just results in it saying '/dev/sdaXX'->'/mnt': no such file or directory. I have data on this device that I forgot to back up, is there any way to at least extract the photos from this thing?
many thanks in advance.

As long as you could enter the recovery and use adb, you could access to the file system or push update etc.
TWRP offers File Transfer and OTG

yes, but how, *exactly*? I got a pixel 6a and twrp doesnt support m ydevices yet, so i can I mount /data or /storage in LineageOS recovery?

ezntek said:
yes, but how, *exactly*? I got a pixel 6a and twrp doesnt support m ydevices yet, so i can I mount /data or /storage in LineageOS recovery?
Click to expand...
Click to collapse
I remember you could use adb and mount /system or /data
Every LineageOS recovery differs

Yep, I tried.
Here is the output of cat /etc/fstab:
```
/dev/block/platform/14700000.ufs/by-name/efs /mnt/vendor/efs ext4 defaults 0 0
/dev/block/platform/14700000.ufs/by-name/efs_backup /mnt/vendor/efs_backup ext4 defaults 0 0
/dev/block/platform/14700000.ufs/by-name/modem_userdata /mnt/vendor/modem_userdata ext4 defaults 0 0
/dev/block/platform/14700000.ufs/by-name/modem_a /mnt/vendor/modem_img ext4 context=ubject_r:modem_img_file:s0,barrier=1 0 0
/dev/block/platform/14700000.ufs/by-name/metadata /metadata ext4 data=journal,commit=1 0 0
/dev/block/platform/14700000.ufs/by-name/userdata /data f2fs discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,atgc,checkpoint_merge 0 0
=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,atgc,checkpoint_merge /dev/block/platform/14700000.ufs/by-name/userdata /data <
```
so of course I issued
`mount -t f2fs -o discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,atgc,checkpoint_merge /dev/block/platform/14700000.ufs/by-name/userdata /data`
and the output was
`mount: '/dev/block/platform/14700000.ufs/by-name/userdata'->'/data': Invalid argument`
mount -a outputs the same thing.