why does my hero boot up in safe mode?
been flashing new roms and some seem to force phone to boot in safe mode, tried wiping phone and all ext all re flashing?
any ideas..
and what is "safe mode"? first time i hear of a hero running in "safe mode"...
when in safe mode, it seem to run as bare rom no installed apps can be seen and no apps can be installed
you do know that a rom can wipe your phone during flashing?
what happens when you try to install an app, why does it not work etc...
edit: i might have an idea, give me the output of these three commands (while your phone is in "safe mode"):
Code:
adb shell mount
adb shell df -h
adb shell ls -al /data/
cheers when installing the just dont show in launch or shortcust but market shows they installed. when typrin mount get
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
none /dev/cpuctl cgroup rw,cpu 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 ext3 rw,noatime,nodiratime,errors=continue,data=
ordered 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
hope the above means something to someone, I've no longer in Safe Mode flash ahearo v4 and back normal for now.
but clues on how to get out Safe Mode as its happened a few time
I think most on here (including me) are still confused on what this "safe mode" actually is.
Lennyuk said:
I think most on here (including me) are still confused on what this "safe mode" actually is.
Click to expand...
Click to collapse
exactly. i am still 100% convinced there is no such thing as safe mode, and it was just something gone wrong with his phone. but since people just want help and are not able and/or willing to follow instructions here we will probably never find out...
kendong2.. next time i get safe mode what do you want? I tried to mount and posted the reply. the phone displays Safe Mode in bottom left of the screen
kendong2 said:
exactly. i am still 100% convinced there is no such thing as safe mode, and it was just something gone wrong with his phone. but since people just want help and are not able and/or willing to follow instructions here we will probably never find out...
Click to expand...
Click to collapse
It most certainly does exist!
See here.
Power off and reboot whilst holding down "Menu" all the way to the home screen to get into safe mode.
Regards,
Dave
cheers foxmeister, ive possible got bad button then andits not result of bad flashing as i dont need hold any button down and phone was booting into safe made
ive got it out of safe mode your suppose to just old menu and power while it boots.
after many attemptrs got out by removing battery and holdt phone menu and power while it boots completely
foxmeister said:
It most certainly does exist!
See here.
Power off and reboot whilst holding down "Menu" all the way to the home screen to get into safe mode.
Regards,
Dave
Click to expand...
Click to collapse
so i stand corrected... good find, and interesting stuff! anybody knows how it works? and how and what for we can abuse it?
foxmeister said:
It most certainly does exist!
See here.
Power off and reboot whilst holding down "Menu" all the way to the home screen to get into safe mode.
Regards,
Dave
Click to expand...
Click to collapse
Edit: I just give it a try and... My thumb aches really bad... I finally find the watermark. Thanks.
jokies said:
Safe mode? I think it's called recovery. Since it's developer call it so...
Click to expand...
Click to collapse
I suggest you *try* it before commenting further, because it clearly calls itself "Safe Mode" and it totally unrelated to the recovery console!
Regards,
Dave
Related
I soft bricked my Vibrant after installing Bionix 1.4 w/Jacs OC/UV/Voodoo kernel. I used Odin to flash back to stock rom which was unsuccessful. It allowed me to boot to the samsung logo and then go black.
Grasping at straws I used clockwork recovery to do a nandroid restore to the vibrant9 rom I was running before (with the KingKlick kernel, but as I understand it nandroid doesnt backup or restore kernels). I thought maybe the kernel got switched back to the stock one but I'm lacking a ROM? Anyway, nandroid restored the system files but when going to restore data it gave me an error about not finding mmcblk0p2, when I go into adb shell and type mount, it tells me I have mmcblk0p3.
Is there any way for me to fix this so I can restore from my nandroid backups? I have everything in titanium and I can still access all the data on the sd card, but I'd really like to just have things back to how they were before installing the Bionix.
Thanks!
Here is a complete copy of what comes up when I hit mount if it helps. Could really use some assistance here, I try to do as much on my own as possible but I've hit a dead end.
Code:
$ mount
mount
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx
,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/loop0 /data/data1 j4fs rw,noatime,nodiratime 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
$ adb reboot recovery
Ok, thanks for all the help guys....
Anyway, for anyone who is having the same problem, I found my solution to be to get into download mode via instructions here: http://forum.xda-developers.com/showthread.php?t=741027&highlight=unbrick
And then follow the instructions in Fix 1 here: http://forum.xda-developers.com/showthread.php?t=782027
I had to upgrade to froyo then downgrade to get my file system back.
I'm now on stock Vibrant kernel and rom, but flashing Bionix 1.5 in a moment (NO VOODOO!!!)
Exact same thing
i had to do the exact same thing this morning. except mine would boot up fully. i couldnt get the internal memory to recognize at all so i couldnt disable the lagfix
blah blah blah... odin and fix 1 worked. i wished i had backups on my computer i should know better by now too. thats the stupid part. all that data lost.
Yea, I'm not new to this sort of thing, just this piece of hardware. I felt really confident after flashing a few ROM's and always read instructions for each new install, I was really surprised to find myself in that pickle. At least I learned something.
Going forward I'm being very dilligent about organizing a backup of my nandroid backups, different ROM's, everything needed to get back to stock, and most importantly the contents of my internal SD card! Nothing had ever messed with that partitioin before so I thought it would be fine, I also thought that nandroid or titanium would backup all my e-books since they were imported into Aldiko, WRONG-O!, it just saves the library index, gotta re-import over 600 books :O
Gotta love nothing ever being good enuf, now I'm off to fix what I broke on my car...
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
icezar1 said:
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
Click to expand...
Click to collapse
Ok, i'll try now to pack my first worlwide rom!
kawa636r said:
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Click to expand...
Click to collapse
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
winwiz said:
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
Click to expand...
Click to collapse
seems to be yes, because samsung apps stay forever in background.
I'm trying to take nexus s keyboard and port to s2, but where are keyboard files located?
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
In shell type mount and see on what stl is mounted /system. I DONT OWN A SGS 2! If you don't have some basic linux knowledge and dont know how the phone works, don't do this! I'm really serious!
But if you wanna go ahead you will need to find out your mount points. Is vital!
How i can see on what stl is mounted system? there isn't an fstab file?
kawa636r said:
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
Click to expand...
Click to collapse
SGS2 has different mount points. I see mention of RFS as well, which is wrong for the SGS2...
# mount
rootfs / rootfs rw,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
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 /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
nil /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
Somebody can help me for the commands that i must do for creating a ROM?
kawa636r said:
Somebody can help me for the commands that i must do for creating a ROM?
Click to expand...
Click to collapse
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
pulser_g2 said:
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
Click to expand...
Click to collapse
from my response of mount command you can't help me?
kawa636r said:
from my response of mount command you can't help me?
Click to expand...
Click to collapse
Nope, sorry. I need the device to figure it out really, as I've not worked with a Samsung before. And I don't know about repackaging a ROM into a tar for ODIN based on a dump.
I wouldn't want to try and help either, as I need the device to actually check it properly, and wouldn't want you or someone else to have to try reflashing after messing something up...
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
pulser_g2 said:
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
Click to expand...
Click to collapse
Yes, but stock rom come with odin files format.
If i want to cook a rom i must start from sources, from a system dump, or from a zip rom (in nexus s i remember that rom are packaged in zip)....
Me too
I have the same problem, do you have find a solution?
I don't want to ruin your mojo, the more people interested in android, the better... but I'm a bit worried if inexperienced people give other inexperienced people things to flash with Odin. Since your ROM doesn't bring anything new (all other roms have this already), why not put some more time in it, polish it a bit, and maybe you will get some original ideas to add to it, instead of rushing it like this, and possibly brick some phones?
The probleme is that i have no time to do this, i have created a system and i have modivied the cyanogenmod to work with this system, the probleme is that i should to find a better methode to install the cyanogenmod rom from a pc, it is not for me is for other simple users.
Hi All,
(Reposting this as previous post was on more generic forum... I've read tons of Threads here, but not yet found a solution).
My Galaxy Tab 10.1 is useless right now as it cannot write to internal storage.
Lots of apps crashing on use and doing a factory reset from the recovery menu does not help (Tablet is in exact same state aon reboot).
So, I've been using adb:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Here's the mount information from shell
[email protected]:/mnt/asec $ mount
mount
rootfs / rootfs ro,relatime 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
debugfs /sys/kernel/debug debugfs rw,relatime 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Click to expand...
Click to collapse
So, I've tried to mount manually from adb shell:
[email protected]:/ $ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]:/ $
[email protected]:/ $ mount -o remount,rw -t rfs /dev/block/stl9 /system
mount -o remount,rw -t rfs /dev/block/stl9 /system
mount: Operation not permitted
Click to expand...
Click to collapse
But, I have no SU command:
[email protected]:/ $ su
su
/system/bin/sh: su: not found
Click to expand...
Click to collapse
I've got the su binary from downloading off aforum, but I cannot copy that up either (even to seemingly writable mount points)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push su /cache
failed to copy 'su' to '/cache/su': Permission denied
Click to expand...
Click to collapse
So then I followed a guide I found linked on a forum to get the Tablet Restocked to factory settings.
However, when I try to write via Odin, I get an error message on the tablet in Red:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
Click to expand...
Click to collapse
Is my tablet bricked ?
Cheers,
Ro
Same issue here. Every reboot resets it to the same state.
froalskiner said:
Same issue here. Every reboot resets it to the same state.
Click to expand...
Click to collapse
why don't you just download new firmware from sammobile.com abdominal flash it via odin..
Enviado desde mi GT-P7500 usando XDA Premium HD app
msedek said:
why don't you just download new firmware from sammobile.com abdominal flash it via odin..
Enviado desde mi GT-P7500 usando XDA Premium HD app
Click to expand...
Click to collapse
Doesn't look like that will work as the disk is mounted in read-only mode.
Using Odin, I get an error message on the tablet in Red:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
Click to expand...
Click to collapse
Do you have an already flashed cwm recovery?If yes try going to advanced/fix permissions.
nighthawk696969 said:
Do you have an already flashed cwm recovery?If yes try going to advanced/fix permissions.
Click to expand...
Click to collapse
Nope, never flashed the Tablet.
robilco said:
Nope, never flashed the Tablet.
Click to expand...
Click to collapse
Then maybe it's a hardware failure. Claim warranty from Samsung.
Panos_dm said:
Then maybe it's a hardware failure. Claim warranty from Samsung.
Click to expand...
Click to collapse
Yep, in an ideal world I'd deffo do this.
But I bought a refurbished Tablet so only came with a 90-day warranty.
Plus, I bought it in the US and I live in Ireland, so European service centre's won't touch it.
My only option is to ship it to a company in Texas, for €60 then attempted repair for $199 + $80 shipping back to Ireland.
Its a little too much .... So, I'm on the lookout for a smashed tablet that I can buy and recover a mainboard from.
Hi robilco,
Did you ever find a solution to your problem? I'm experiencing this exact problem. In fact, I've tried just about everything you did mentioned in this thread and more including trying to an upgrade/restore from Kies and no luck.
I can't do anything from Odin because I'm getting the same errors as you. Can't write or transfer anything via adb just like you. Since it's not rooted, I can't change permissions and because everything appears to be read-only, I can't root it!
It was working fine until the end of June. I turned off my tablet for an extended period because I was not using it. When I turned it back on I noticed that it was taking a long time to start up. It was stuck on the Samsung Galaxy Tab 10.1 logo for about 10 minutes before it finally proceeded to the load up. When it finally starts up, it will start to run all the updates after which it will freeze up and stay frozen until the battery drains or I force a hard reboot, after which again it will stay on the Samsung Galaxy Tab 10.1 logo for another 10 minutes when I turn it on again.
I was able to get around the update freezing by immediately shutting off the internet once it loads up and turning off all automatic updates.
Also every time it starts up, it will start back up in the same state it was before. That is, if I change any settings, adjust the date/or time, install any new software, or anything like that, it will reset to the previous state once I restart the tablet again. I suspect the operating system is stuck in some sort of read-only state since I cannot make any permanent change.
I also cannot perform any factory reset on it. I've tried both the software reset through the Android settings menu and doing a factory hard reset by going into the Android System Recovery <3e> mode and it always returns to the same state it was mentioned earlier.
I also cannot perform the Ice Cream Sandwich update because after it downloads, it needs to reset and again it will be stuck on the logo for about 10 minutes before returning to the aforementioned state. I've tried the upgrade about 3 times now.
The issue is definitely not related to the battery since it is always fully charged when I try making changes and I have 12.68GB space left on a 13.11GB capacity.
Yep - Looks like we have the EXACT same issue and tried all the same resolutions.
I've also been trying the 'nvflash' tool but no luck there (yet)
I've been told the only option is to return it to samsung and get it fixed.
But since I bought my table in USA and I'm now in Europe, Samsung Europe have no interest in helping me and it would cost too much to get it repaired.
I'm on the lookout for a smashed tablet that I can get on eBay or a replacement mainboard so I could just switch out the component.
Ro
sienarot said:
Hi robilco,
Did you ever find a solution to your problem? I'm experiencing this exact problem. In fact, I've tried just about everything you did mentioned in this thread and more including trying to an upgrade/restore from Kies and no luck.
I can't do anything from Odin because I'm getting the same errors as you. Can't write or transfer anything via adb just like you. Since it's not rooted, I can't change permissions and because everything appears to be read-only, I can't root it!
It was working fine until the end of June. I turned off my tablet for an extended period because I was not using it. When I turned it back on I noticed that it was taking a long time to start up. It was stuck on the Samsung Galaxy Tab 10.1 logo for about 10 minutes before it finally proceeded to the load up. When it finally starts up, it will start to run all the updates after which it will freeze up and stay frozen until the battery drains or I force a hard reboot, after which again it will stay on the Samsung Galaxy Tab 10.1 logo for another 10 minutes when I turn it on again.
I was able to get around the update freezing by immediately shutting off the internet once it loads up and turning off all automatic updates.
Also every time it starts up, it will start back up in the same state it was before. That is, if I change any settings, adjust the date/or time, install any new software, or anything like that, it will reset to the previous state once I restart the tablet again. I suspect the operating system is stuck in some sort of read-only state since I cannot make any permanent change.
I also cannot perform any factory reset on it. I've tried both the software reset through the Android settings menu and doing a factory hard reset by going into the Android System Recovery <3e> mode and it always returns to the same state it was mentioned earlier.
I also cannot perform the Ice Cream Sandwich update because after it downloads, it needs to reset and again it will be stuck on the logo for about 10 minutes before returning to the aforementioned state. I've tried the upgrade about 3 times now.
The issue is definitely not related to the battery since it is always fully charged when I try making changes and I have 12.68GB space left on a 13.11GB capacity.
Click to expand...
Click to collapse
robilco said:
Yep - Looks like we have the EXACT same issue and tried all the same resolutions.
I've also been trying the 'nvflash' tool but no luck there (yet)
I've been told the only option is to return it to samsung and get it fixed.
But since I bought my table in USA and I'm now in Europe, Samsung Europe have no interest in helping me and it would cost too much to get it repaired.
I'm on the lookout for a smashed tablet that I can get on eBay or a replacement mainboard so I could just switch out the component.
Ro
Click to expand...
Click to collapse
I've found a few posts from users with what sounds like the same issue as ours but no solution either. I've also tried going through the Samsung route but at this point they haven't been very responsive. Their only response was a canned message asking me for my contact info -- something I already provided them with when I submitted my trouble ticket. They haven't even followed up with that or my repeated attempts to get a response.
Way to go Samsung.
Greetings,
I'm looking for help in the following scenario: some days ago I found that my Galaxy Note had rebooted, and got stuck at the Samsung logo. The phone has the stock rom, it is not rooted and is running Jellybean.
Recovering from this situation hasn't been possible. I tried:
- pulling the battery
- rebooting from recovery mode
- wiping cache partition.
I haven't tried a factory reset because the problem appeared as I was on vacation and there are some some photos I'd like to recover.
Taking this also as a learning experience, I have read several documents on recovery mode, adb, etc. So far I have managed to access via ADB. I could successfully run adb pull, however it seems not all data came through.
I don't have /mnt visible, no DCIM folder, and sdcard or sdcard1 have no contents. I've attached the screenshot of the Android Device Monitor.
For example, adb pull /sdcard returns 0 files.
I think maybe something is not properly mounted...? I tried to search similar issues it's not clear to me how to proceed. Anyway this is the output of 'mount' in case is helps:
[email protected]:/dev $ mount
mount
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/mmcblk0p9 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
Thank you in advance for your help!
So after spending some time experimenting and reading about filesystems, ADB, sideloading, recovery mode (even went to a Samsung repair centre (they answered straight "no" regarding getting data from the internal memory)), I had to go with the factory reset.
So I answered 'yes' to all the warnings about losing all data, took a deep breath and waited...
Phone turns back on, usual out-of-the-box wizards etc, and then I start realising some options are the same as I had them... then I open the camera and notice a known picture in the gallery thumbnail... so, in a Christmas miracle, all my photos and personal files were NOT touched by the factory reset! It all lies inside /storage/sdcard0 and apparently this isn't touched by the reset.
Hi all
I have in my hands a Samsung YP G70 with this problem: I need to format it, clean it COMPLETELY.
I tried the following things:
1-Using the stock recovery, clean data and cache
2-Flash via Odin (different processes): his original firmware (same version), another firmware, a Kernel that should included the CWM Recovery
3-Root with Kingo
4-Tried to flash the TWRP flashable version into his stock recovery
5-Restore at factory default from the player
No one worked
After the reboot I will always have the same data (same accounts, same photos, same apps)
If I add a file, after a reboot, the file disappear; if I delete a file, after a reboot, the file re-appear.
So: how can I completely clean it? Or should I trash cause the memory allocator gone crazy?
Thanks a lot
GeniusJack said:
Hi all
I have in my hands a Samsung YP G70 with this problem: I need to format it, clean it COMPLETELY.
I tried the following things:
1-Using the stock recovery, clean data and cache
2-Flash via Odin (different processes): his original firmware (same version), another firmware, a Kernel that should included the CWM Recovery
3-Root with Kingo
4-Tried to flash the TWRP flashable version into his stock recovery
5-Restore at factory default from the player
No one worked
After the reboot I will always have the same data (same accounts, same photos, same apps)
If I add a file, after a reboot, the file disappear; if I delete a file, after a reboot, the file re-appear.
So: how can I completely clean it? Or should I trash cause the memory allocator gone crazy?
Thanks a lot
Click to expand...
Click to collapse
Please post the output of "mount" after a normal boot ( not in recovery )
You can do this in adb by doing:
adb shell
su
mount
or in a terminal app
su
mount
Then copy the output here or a screenshot with the info is fine...
$ su
su: not found
$ mount
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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/u
id/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/
uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,no
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Is it ok?
GeniusJack said:
$ ...
Click to expand...
Click to collapse
If you have the USA variant try flashing this with Odin:
http://www.4shared.com/zip/hFJmoXTiba/YP-G70-UEKI8-Stock-USA-Meticul.html?
Flashed via Odin3 v1.87 into PDA but after the reboot I have the same data as before, so not worked...
GeniusJack said:
Flashed via Odin3 v1.87 into PDA but after the reboot I have the same data as before, so not worked...
Click to expand...
Click to collapse
Hmm.. Not sure whats goin' on.... When did this start???
I really don't know
A friend gave it to me asking for a check because he noticed that when installed an application, after a reboot the app disappears.. He thought about a virus so he asked to clean it...
GeniusJack said:
I really don't know
A friend gave it to me asking for a check because he noticed that when installed an application, after a reboot the app disappears.. He thought about a virus so he asked to clean it...
Click to expand...
Click to collapse
You could try the "getto lagfix":
This converts your file systems from rfs to ext4...
It's been a long time since I messed with stock GB so read and understand carefully before attempting...
http://forum.xda-developers.com/showthread.php?t=1445840&page=9
But I don't have a CWM, everything is stock, without root etc...
GeniusJack said:
But I don't have a CWM, everything is stock, without root etc...
Click to expand...
Click to collapse
So even if you flash a kernel it does not change?
Nope... Tried but not works... Same kernel after the reboot from Odin
GeniusJack said:
Nope... Tried but not works... Same kernel after the reboot from Odin
Click to expand...
Click to collapse
Seems like a hardware issue. Check dmesg/kmsg for errors...
Noob question coming.....
How?