Database Info

/efs not mounted - need help from Linux experts and others rooted i580x users!!!

After a sleepy ODIN flash, using SPICA ops with G3 firmware => STUPID??? NO, not done yet , next ODIN flash segment, accidentally stick clear phone EFS via Debug options (DOUBLE CRAZY!!!) NOW i lost the precious IMEI and /efs partitions corrupted as well.
i've got the fixed nv_data.bin and both stl4.img and bml4.img from [email protected] (attached). Thanks for his kindness and supportive to the community!
But even with those i still can't fix the issue!!!! /efs did not mounted via mount command...
as in a GOOD G3, mount command result will be as below:
Code:
rootfs / rootfs rw 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/stl6 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
[B]/dev/block/stl4 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0[/B]
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0702,dmask=0602,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
in my case the bold line just missing... so this is must be the problem.
I tried to do the same as SPICA's method as below:
Code:
$su
#dd if=/sdcard/bml4.img of=/dev/block/bml4
#reboot
It's OK then but...
Code:
$su
#dd if=/sdcard/stl4.img of=/dev/block/stl4
/dev/block/stl4: cannot open for write: Invalid agrument
With this error my /efs cannot be mount... and still missing from the mount command. I'm just a linux noob so pls help me out. How can i restore the stl4 partition properly???
My girlfriend now really mad at me due to she don't have her beloved phone this christmas already. OMG!!!!!
and to all rooted i580x user Pls kindly help compare your "good" /efs folder... maybe mine missing something???? due to one time Erase Phone EFS using Odin Debug Options.
Mine /efs now as below:
Code:
/efs/nv_data.bin
/efs/imei/.nvmac.info
/efs/.files/.dm33 (empty folder)
/efs/.files/.dx1 (empty folder)
/efs/.files/.mp301 (empty folder)
And if you can do adb shell, it'll be very kind of you by sharing your good backup stl4 and bml4 - for research purpose (those partitions did not content any of yours personal data - so PLS HELP!!!). Pls do the backup partions as below and share your img here if possible.
Code:
$su
#cat /dev/block/stl4 > /sdcard/efs_dev-block-stl4.img
#cat /dev/block/bml4 > /sdcard/efs_dev-block-bml4.img
TIA and Best Regards
P/S: when do the ls /dev/block/stl* the stl4 is there but cannot restore using the backup img. it's weird...
Code:
#ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
same for bml4...

I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.

Szaby59 said:
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Click to expand...
Click to collapse
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.

kenblat said:
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
Click to expand...
Click to collapse
fixed ur phone yet? noob idea: can u try flashing but this time with the right ops?

were you able solve the problem? I am facing exactly same problem.

Tester needed: Porting Guide to boot phone with fried emmc

Hello,
I developed a guide and software package to boot a phone with a fried emmc.
The trick is to use modified kernel files and mount all partitions to image files on SD card - however, kernel files and software are different from phone to phone.
My guide already works nice for HTC Desire Z / G2:
http://forum.xda-developers.com/showthread.php?t=1572924
To port that guide and the linked package to HTC Desire Z I need a tester with a custom rom (ClockworkMod recovery, 3Ext ...). For porting the package I need someone with a full working phone. For testing later someone with a fried emmc would be helpful.
If you want to support me then send me a private message on XDA or visit me on freenode IRC channel #G2ROOT (web interface: http://webchat.freenode.net - channel #G2ROOT)
Best regards,
Catherall

Excellent idea !
If you need tester with fully working phone - I'm in .
Especially as we can use this as some sort of dual boot on working phones to test new roms without installing it
R.

Hello,
I have fried emmc on htc desire s. I sent my phone about 10 days ago to local service. I will get my phone soon. If they don't succeed I will be your tester.
I had a call with service man 2 days ago and he said to me that they can repair it and repair will cost 15€. He said that they will reprogram emmc or something like that and they are waiting to receive 1 file for phone software and when it comes phone will be repaired.
If you need aditional info PM me.

How about the progress on porting to desire s?. I´m available if you look for a tester with a fried chip

All is working as I can say. But not sure if I can post needed files... Lets wait for catherall answer .
R.

He is offline since 23. april so if anyone know to make this work do it

Ok, all credits going to catheral. I'm tested this with working desire s and phone is booting from recovery without any problems. You just need to extract downloaded files to sdcard root and apply update.zip from recovery ...
https://www.dropbox.com/s/e5nusi7ojg65q8e/Saga_recovery_boot.rar
R.

Great! Thank you. This is big thing for desire s now because emmc problem is now fixed.
One question: When I restart or turn off phone do I need to do update in recovery again or this will be permanent ?

So im confused what does this do? Is there anyway to port it to the htc incredible s?
Sent from my Incredible S using XDA

first thanks for the great work which catherall has done.
Just put this on my sdcard and booted from recovery via update.zip. I can confirm that this rom is booting on my desire s with fried emmc. Overall the performance is pretty fast but there are few limitations:
Wlan doesn´t work
Each time when an app is trying to acess the internal memory, it crashes(since there is no internal memory due emmc brick)
Working (tested):
phone calls
text messages
acessing internet via HDSPA,Umts,...
everything which doesn´t need access to internal storage
app installs

Great!
Rolf can you fix wlan ?

Hey catherall.
I was just thinking when reading your thread..i don't have a fried emmc but it might help you or someone else develop a permanent fix for this issue.
If you can boot the phone from the sdcard via this "temp fix" which is brilliant btw (hats off to you)..i guess that you could try to do this natively.
Bear with me as i am no expert in android or any other programming development but i do have a technical inclination.
To my understanding the emmc holds these partitions: /system; /data; /cache
Also, the partition layout is dictated by the HBOOT (am i right?).
Thus, if HBOOT is functional after frying the emmc can't the hboot be reprogrammed so as to allocate the /system; /data; /cache to the sdcard thus natively run them on the sd and by this fixing the current issues? I'm thinking yes because if the rom is installed with the mentioned partitions being on the sd it will not try to access the emmc thus no failures, issues, kernel oops or panics.
Keep in mind that i'm not properly educated in this domain of expertise and what i wrote might just be a huge load of *$#& and that what i said is purely a principle based on what i understand about the android platform.. no idea how to code or reprogram HBOOT so i might be wrong.
P.S. sorry about cloning posts..

Hands up to the original Dev of this great project. this will help a lot of people. who are having problems with their fried chip. however once this ROM is stable you wont be able to upgrade it or anything so you will be stuck with this Rom. now. you can replace your chip for very little cash. you just need the brains to replace it with the old 1. Is this rom even good enough. i mean in eyes of people who are serial flasher's they are going to want to flash a new rom lol. and 2 is there any way we could just have a new development section that is FOCUSED on development with fried chip roms like this 1. i think this could be extended. i think if this can be done with cyanogen then it can be done with stock Rom also. im very intrested in asking the mod to set up a dev section for this so we can develope roms that are aimed at peple with fried chips. as this will help a lot of people. we could develope or mod the roms out at the moment for the people with fried chips. if anyone else agree's with me then please reply if enough peole on this forum want it done i say we get on it now

hey Paul.
Im with you 100% but i think that there needn't be specific emmc-fried roms (the rom components can be extracted and installed to the sd manually by each user if a guide is made). The problem i believe are the kernels as they are the subsystem that communicate to the hardware, not the rom itself.. if my previous post is right though, then i believe that the roms can be flashed normally and be directed to new partitions on the SD automatically.

xxmorph3u5xx said:
hey Paul.
Im with you 100% but i think that there needn't be specific emmc-fried roms (the rom components can be extracted and installed to the sd manually by each user if a guide is made). The problem i believe are the kernels as they are the subsystem that communicate to the hardware, not the rom itself.. if my previous post is right though, then i believe that the roms can be flashed normally and be directed to new partitions on the SD automatically.
Click to expand...
Click to collapse
in that case there would have to be a new kernel with every rom made for this. im my experience i would say that i wouldnt go ahead as ask for a dev section for this to be opend. i will infact tho test this out and see if the rom itself can be installed to a new partition on the sdcard. i will let you know if the rom is able to install onto the sdcard later tonight. i very much dont think it will tho. but worth a shot. if it does work then does that mean we could get this more stable and without crashes ?

The rom will definetly not boot if you just install it to sd..no need to test that.. The partition table needs to be rewritten for this to work (the partition layout being stored in the HBOOT to my knowledge). This is why i suggested rewriting the HBOOT, because if i am right the recovery will flash every rom and kernel to the new partitions on the "fake" emmc (SD that is).

xxmorph3u5xx said:
The rom will definetly not boot if you just install it to sd..no need to test that.. The partition table needs to be rewritten for this to work (the partition layout being stored in the HBOOT to my knowledge). This is why i suggested rewriting the HBOOT, because if i am right the recovery will flash every rom and kernel to the new partitions on the "fake" emmc (SD that is).
Click to expand...
Click to collapse
hmmmmm im curious about this. but then again would anyone with a fried emmc chip be willing to flash a re written hboot that has a chance or 50% bricking there phone lol ? too messy for me im going to stick to making my sense tablet rom for now
Hboot 0.98.00000 and 0.980002
Mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.eamobile.nfsshift_na_wf-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.fridgecat.android.atilt-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/pl.idreams.skyforcereloaded-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.ArtInGames.AirAttackHD-1 vfat ro,dirsync,nosuid,no
dev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
HBOOT 2.xxxxx
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

Hehe, good luck with your port..i really like your ICS tab_mod!
As for the "who would risk bricking their phone"...i don't think that with a fried emmc there's anything else to brick.
Anyway, on a serious note though, i have no idea how hard rewriting a HBOOT would be, nor if it will actually work..i am no experienced programmer, this is why i recommended the "method" to a more experienced user in hope that the emmc damaged guys could catch a break.
Sure, as you said, replacing the emmc is a waaaay better solution but hardware modifications are not that easy and should be done only by specialized personnel which can be $$$.

xxmorph3u5xx said:
Hehe, good luck with your port..i really like your ICS tab_mod!
As for the "who would risk bricking their phone"...i don't think that with a fried emmc there's anything else to brick.
Anyway, on a serious note though, i have no idea how hard rewriting a HBOOT would be, nor if it will actually work..i am no experienced programmer, this is why i recommended the "method" to a more experienced user in hope that the emmc damaged guys could catch a break.
Sure, as you said, replacing the emmc is a waaaay better solution but hardware modifications are not that easy and should be done only by specialized personnel which can be $$$.
Click to expand...
Click to collapse
above is the mount info from desire s hboot 0.98.0000 and below is for hboot 2.xxxxx.
Thanks my rom is nice lol . im making the same rom but with sense its going well just need to port rosie from flyer then its done

This information is available in this sticky
http://forum.xda-developers.com/showthread.php?t=1180513
Looking forward to sense tablet version
Sent from my HTC Desire S using xda premium

[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..

[BOUNTY] 30$ for unbricking my phone (Asus Padfone Infinity A80)

Hi everyone,
I have a bricked Asus A80, which is repairable if someone has the skills. But I don't. So I need someone's help.
I have tried a lot of procedures but none of them have worked. I will display the details below.
For the one who will give me the correct procedure to unbrick my phone, I will pay him 30$ with Paypal. A small buck, but I have nothing more right now. And all effort deserves reward.
Thanks for your assistance.
Problem :
- Phone stuck on boot screen with the message "Invalid Kernel !" written on the top of the screen.
Pros
- I can access fastboot
- I can boot custom recovery from fastboot
- I can access ADB from booted custom recovery
- I have another working Asus A80 to dump stuff if needed
Cons
- I can't boot to stock recovery
- Flashing complete roms from booted custom recovery works but does not change anything
- I can't flash boot.img nor recovery.img, or at least I did not succeed
Here is all the historic of what I've tried, what worked and what did not, with all the error messages :
http://padfoneclub.com/pl/forum/forum_viewtopic.php?12268.15
This where I am right now. So anyone willing to help?
Thanks guys.

Hello... I read your link. Maybe you are trying to write in a Read only partition(FAILED remote: Security is Enable, close 'flash' function !!)... Try to remount it like Read/Write...! But first you need to know the mount points.. To do that type:
Code:
adb shell su
adb mount
You will get some mounts points. So find the partition you want to mount and type:
Code:
adb mount -o rw,remount <mount point> <pertition name>
For example on SGS3 device the mount point of system is /dev/block/mtdblock3. So the command is:
Code:
adb mount -o rw,remount /dev/block/mtdblock3 /system
Are you that you have an insecure kernel and that your bootloader is unlocked...?

First of all, thanks for answering, I'm grateful. :good:
So the anwser is that no, bootloader is not unlocked, since I actually bricked my phone using Asus' unlocking tool apk. It did not unlock the bootloader, and it corrupted my recovery. And that's why I have this invalid kernel message (I guess).
And since I've tried flashing half a dozen roms after that, I don't have root access anymore. So I can't get su commands to work.
I tried your procedure, and here is what I've got :
Code:
C:\Android>adb shell su
/sbin/sh: su: not found
C:\Android>adb shell
~ # su
su
/sbin/sh: su: not found
~ # mount
mount
rootfs on / type rootfs (rw)
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)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nodev,noati
me,nodiratime,data=ordered)
~ #
So it seems every partition is read/write...

Okay then try thiw command and post the results..!
Code:
adb shell
adb cat /proc/mount
But if don't have root privileges then I think it's difficult to unbrick it...
If you can root it again by custom recovery...?

Yeah I know, that's why I've been struggling. Asus A80 has almost not dev community, so I have close to 0 solution. Bootloader unlocking is acheived with an app, for root I used framaroot...No root package to flash...But since I have another working Asus A80, maybe I can work something out?
So here are the results :
Code:
C:\Android>adb shell
~ # ←[6ncat /proc/mount
cat /proc/mount
cat: can't open '/proc/mount': No such file or directory
~ # ←[6n

Oh you write wrong the command it's:
Code:
adb shell
adb cat /proc/mounts
It's mounts not mount...!

Lol ok now it's working :
Code:
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p30 /data ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p30 /sdcard ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,relatime,data=ordered 0 0
~ # ←[6n

Okay I get condused...! I can't see the /system partition...! I don't know what is going on. I will try to root it again. Can you still boot onto recovery mode and install zips...?

Well that would explain certain things...But I dont' know why it doesn't not show up since I flashed several official roms and it did work the whole process to the end...
I can boot to CWM or TWRP, but not sure if I can flash unsigned code...

I can sign zips for CWM recovery...! But I don't know what files I have to install. I will inform you when I find out. I'm working on it..! :good:
When you boot on CWM can you mount the /system partition form there.I think there is an option tha you can mount /system

Yes it works, I can mount/unmount /system, or at least I have no error message when I do so...
Let me know if you need any other information or to try something else. :good:

Ok first I want you to try again the command:
Code:
adb shell
adb cat /proc/mounts
And then turn off you device and run the command
Code:
adb logcat > C:/Users/xxxx/Desktop/logcat.txt
When you execute this command turn on your device until you the error then open the file an tell me what it says.
To tell you the truth if we can't see the system partition it's difficult to unbrick it becuase we can't root it..!

When I do this, adb is stuck hanging on 'waiting for device'. When I turn it on, it shows splash screen with the 'Invalid Kernel' error message, but not adb access, only fastboot. To get adb access, I boot to cwm with "Fastboot boot recovery.img"...

What is your rom version...?

Just giving a suggestion, you said you tried flashing a new kernel and boot.img but nothing happened. How exactly did you flash these images?

I could not remember so I just flashed this one :
http://dlcdnet.asus.com/pub/ASUS/Mo...ity/WW_PFI_user_11_8_10_24_UpdateLauncher.zip
And CWM log for the flash was :
Code:
Restarting adb...
Finding update package...
Opening update package...
Installing update...
Writing sbl3 image...
Writing rpm image...
Writing sbl2 image...
Writing sbl1 image...
Writing tz image...
Writing aboot image
Writing modem image...
And then it just stopped, no reboot, it is written "script succeeded, result was [t]" under the droid...But I don't know if everything was properly formated and written...
After that, I tried mounts again, here is the result :
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
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)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nodev,noati
me,nodiratime,data=ordered)
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nodev,noatime,nodira
time,data=ordered 0 0
~ #
Do you have everything you need? I can do other stuff if you want. Remember that I have another Padfone Infinity, with root access, if you want to compare partitions...

TheArc said:
Just giving a suggestion, you said you tried flashing a new kernel and boot.img but nothing happened. How exactly did you flash these images?
Click to expand...
Click to collapse
Hello, thanks for your message.
I have access to fastboot, so I just boot the custom recoveries with "fastboot boot recovery.img".
I have cwm, twrmp, 4.1 stock recovery, and 4.4 stock recovery available. I can boot them, but not flash them.

On your other phone can you run the mount commands and post me the result..?
Thank you..!

Ok I just need to charge it a little bit. I will let you know in less than an hour.

Beretta93 said:
Hello, thanks for your message.
I have access to fastboot, so I just boot the custom recoveries with "fastboot boot recovery.img".
I have cwm, twrmp, 4.1 stock recovery, and 4.4 stock recovery available. I can boot them, but not flash them.
Click to expand...
Click to collapse
I believe you're supposed to place the boot.img in the adb folder and do this "fastboot flash boot boot.img" that will flash a new image.

Stuck on screen with android and polyhedron spinning

Hi,
I tried flashing CM on my TF700 but failed. Now it's stuck on a screen with an android and a polyhedron spinning in its belly. I can access adb but not fastboot. "adb reboot bootloader" does nothing - it gets stuck there until I ^C it. Rebooting with the volume button just brings me to that screen again (I know how it works, I've done it in the past, but now it's broken). Do I have a very expensive paperweight?

Well, what did you do?
That screen is the stock recovery spinning it's wheels most likely. Did you flash a custom recovery? If so which one?
What bootloader are you running and what exactly did you do to get into this pickle?
You have adb in recovery?? Post a picture of your cmd window with 'adb devices'

I tried following this guide here:
https://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
but I first accidentally tried flashing the zip from an older version of Clockwork Recovery that I had installed, and that gave errors. Then I realised what happened, flashed the newer recovery, and then tried flashing the zip. That was giving some errors about /cache but otherwise seemed to work. Then I rebooted and it was stuck in this state. Some other problem might be that I tried flashing without gapps - didn't want any gapps in my tablet, so I thought that flashing without those would have been fine.
Code:
> adb devices
List of devices attached
015d2d431f201e09 device
I even managed to get into adb shell:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
I can dd from /dev/zero into a file on / , but trying to dd anything from/to /dev/block/mmcblk0pX freezes until I reboot the tablet. I even tried to run "fdisk /dev/block/mmcblk0" but that also freezes. For /dev/block/mmcblk1 (my external microSD, I assume), fdisk works.

Ok, try this to kick the tablet back into the bootloader :
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
And then please give up on CWM recovery and CM as rom. They suck and are completely outdated.
Go for any of the Katkiss roms, latest version is Nougatella, and TWRP as recovery.
In between you may want to fastboot flash the stock blob just to get the tablet back to a known and working state, but that's up to you.

Thanks for your suggestion!
Bad news: it didn't work It rebooted to a state where the screen is off, "adb devices" and "fastboot devices" both detect nothing, but "lsusb" detects this:
Code:
Bus 001 Device 051: ID 0955:7030 NVidia Corp. Tegra 3 (recovery mode)
Any other ideas?
Also thanks for your suggestion regarding CWM/CM. As you can probably understand I've been out of touch for a few years (since I got my Fairphone, which comes Google-free), and now that I tried resurrecting the TF700, I went back to what I knew back then.

Sounds as if you killed it. Sorry.
You would have mentioned if you had generated your device specific nvflash blobs at some point to make it brick proof. If you didn't now is too late. RIP