Hey guys. I am working on a total recovery method for this device to assist you guys in making a Hard Bricked device work properly. I need to create a stock firmware package. I've been working my ass off trying to make this a reality.. I've downloaded 10 firmware packages with no success. So, now the only option left is to rebuild from a working device.
Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
So, in this thread I'm asking for community help. I'll post the task and anyone can execute the commands:
1. use a terminal emulator on your phone and execute 'su' and 'mount'
2. copy-paste from the terminal emulator into the forums so we can locate the proper devices per partition
3. execute some commands to dump some partitions which will be determined by step 2
4. post the dumped partitions here.
Anyone can participate in any of these steps... Lets do this quickly!
Task1:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copypasta the results of the mount command here.
Hello, I appreciate your work! Will this be able to fix a brick no matter how screwed it is?
The reason I ask is because I believe I have messed up something concerning the pit file.
I was about to send it into samsung to repair, but if this could fix it...
iJimaniac said:
Hello, I appreciate your work! Will this be able to fix a brick no matter how screwed it is?
The reason I ask is because I believe I have messed up something concerning the pit file.
I was about to send it into samsung to repair, but if this could fix it...
Click to expand...
Click to collapse
I need this information to develop a total recovery solution.
I'm breaking this down really simple. Please don't clutter this thread. I probly should have posted in development
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copy and paste the results of the mount command here.
Hope this helps
Also would you be able to create a rom for this device say ICS ?
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# 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/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/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,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
AdamOutler said:
Hey guys. I am working on a total recovery method for this device to assist you guys in making a Hard Bricked device work properly. I need to create a stock firmware package. I've been working my ass off trying to make this a reality.. I've downloaded 10 firmware packages with no success. So, now the only option left is to rebuild from a working device.
Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
So, in this thread I'm asking for community help. I'll post the task and anyone can execute the commands:
1. use a terminal emulator on your phone and execute 'su' and 'mount'
2. copy-paste from the terminal emulator into the forums so we can locate the proper devices per partition
3. execute some commands to dump some partitions which will be determined by step 2
4. post the dumped partitions here.
Anyone can participate in any of these steps... Lets do this quickly!
Task1:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copypasta the results of the mount command here.
Click to expand...
Click to collapse
I can make this for you but do you need a US or EU version. Because I have a EU version. And for recovery it's recovery.bin? or .img?
---------- Post added at 01:16 PM ---------- Previous post was at 12:27 PM ----------
Here my mount command. Hope this helps.
Code:
$ su
su
# mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,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)
none on /acct type cgroup (rw,relatime,cpuacct)
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 rfs (ro,relatime,vfat,log_off,check=no,gid/uid/r
wx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p2 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no
,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,
gid/uid/rwx,iocharset=utf8)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,n
oatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codep
age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,no
dev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utim
e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe
xec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,
codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k
,mode=000)
alright. Now task 2,3 and 4.. Anyone can do this.
I need a copy of working partitions from a device. You must trust me that I will perform a master clear. I will not post your personal partitions. I need a template to work with in order to get this device working.
2: execute the following code on your device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere and send me a PM. If you would like, I have a private FTP site at ftp://adamoutler.com and I will give you a login/password to log into my personal network attached storage and upload the zip file containing the partitions.
zaclimon said:
I can make this for you but do you need a US or EU version. Because I have a EU version. And for recovery it's recovery.bin? or .img?
Click to expand...
Click to collapse
It does not matter.. US, EU.. They're all fine. I think I can make a recovery.bin.
Rueben_ said:
Hope this helps
Also would you be able to create a rom for this device say ICS ?
Click to expand...
Click to collapse
That's possible. I don't own a device to work with, but a total recovery solution comes before any development. You have to have a way to get back to stock.
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
AdamOutler said:
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
Click to expand...
Click to collapse
I can't help you with this. I have an error which is said there is no such files or directory.
zaclimon said:
I can't help you with this. I have an error which is said there is no such files or directory.
Click to expand...
Click to collapse
You may have typed it wrong. Please try again.
Another method for those of you with Linux or any type of SSH terminal like the windows tool puTTY, is to use an app like SSHDroid then terminal in to your device and copy-paste the code block in.
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
I have the same error coming up ? :/
Error: cannot open for write: No such file or directory
Rueben_ said:
I have the same error coming up ? :/
Error: cannot open for write: No such file or directory
Click to expand...
Click to collapse
Do you have an SDCard in your device?
try the same lines with /sdcard instead of /mnt/sdcard.
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs
AdamOutler said:
Do you have an SDCard in your device?
try the same lines with /sdcard instead of /mnt/sdcard.
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs
Click to expand...
Click to collapse
It's not working either. I think the player don't have these blocks.
zaclimon said:
It's not working either. I think the player don't have these blocks.
Click to expand...
Click to collapse
The player has these blocks, you can't write them to the sdcard. it says can't write.
Code:
Error: cannot open for write: No such file or directory
what is the sdcard called on the filesystem?
try changing the blocksize... i belive it was 512 on this device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs bs=512
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs bs=512
I can get these files directly from your device if you want to add me on google talk.. we need to get market app wireless adb installed and put your device into the DMZ on your router. *myusername* @gmail.com
AdamOutler said:
try changing the blocksize... i belive it was 512 on this device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs bs=512
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs bs=512
Click to expand...
Click to collapse
I checked my mount and used the stl block instead of mmcblk0p block. Is this matter? What is DMZ? I think data will take a little more time.
Ok I have my files. What do I do now?
EDIT: My blocks and Rueben_'s are different. That's why it don't work with me.
zaclimon said:
I checked my mount and used the stl block instead of mmcblk0p block. Is this matter? What is DMZ? I think data will take a little more time.
Click to expand...
Click to collapse
DMZ on a router is where you unrestrict the IP address of a device on your network. Everything is directed to that IP. Othewise I need ports 22 and 5555 directed to the IP address of your device running adbwireless.
AdamOutler said:
DMZ on a router is where you unrestrict the IP address of a device on your network. Everything is directed to that IP. Othewise I need ports 22 and 5555 directed to the IP address of your device running adbwireless.
Click to expand...
Click to collapse
It seems difficult to configure it on my router. It would be easier to upload it no?
zaclimon said:
It seems difficult to configure it on my router. It would be easier to upload it no?
Click to expand...
Click to collapse
PM sent with my information, login and password.
I hope this works, just in case, can you ALSO get the BML blocks for this?
Related
We have bought GT-S5830 to all our employees. Emediatly I rooted the device and tried out different ROMs. I didn't find one that I was satisfied with, and now I want to flash back the stock ROM. It came with Android 2.3.3 with these "packages:
PDA: S5830XWKPU, PHONE: S5830XWKP7, CSC: S5830OXFKP3
I haven't found this stock ROM anywhere (and no stock 2.3.3 ROM I tried had support for Swedish keyboard), so I wonder how I could use one of the "untouched" ones and make a backup to my phone.
This is what I've done so far... Took our secretarys phone and did a complete wipe (Settings -> Privacy -> Factory data reset -> Checked Format SD Card and Reset phone -> Erase everything). Rooted with SuperOneClickv2.2-ShortFuse. Opened a adb shell
Code:
$ su
# mount
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
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard 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
/dev/block/vold/179:1 /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
I then wanted to remove the Superuser app and su from the phone to erase evidence if we need to use our warranty.
Code:
# find / -name *uper*
find / -name *uper*
/system/app/Superuser.apk
/data/dalvik-cache/[email protected]@[email protected]
# find / -name su
find / -name su
/system/xbin/su
# mount -o remount,rw /dev/stl12 /system
mount -o remount,rw /dev/stl12 /system
# rm /system/app/Superuser.apk
rm /system/app/Superuser.apk
# rm /data/dalvik-cache/[email protected]@[email protected]
rm /data/dalvik-cache/[email protected]@[email protected]
# rm /system/xbin/su
rm /system/xbin/su
# mount -o remount,ro /dev/stl12 /system
mount -o remount,ro /dev/stl12 /system
Q1. Does this remove all evidence of breaking the warranty, or does SuperOneClickv2.2 add something more I have left out?
I found (gailly.net / android / android-tips.html) <- here which files should be in each Odin-package.
BOOT: arm11boot mibib oemsbl qcsbl
PHONE: amss
PDA: boot.img recovery.img data.rfs system.rfs
CSC: csc.rfs
I found (kaskus.us / showthread.php?t=9912955&page=252) <- here how to dump the files for the Odin PDA-package.
Code:
# dd if=/dev/block/bml8 of=/sdcard/boot.img bs=4096
dd if=/dev/block/bml8 of=/sdcard/boot.img bs=4096
2048+0 records in
2048+0 records out
8388608 bytes transferred in 0.785 secs (10686124 bytes/sec)
# dd if=/dev/block/bml9 of=/sdcard/recovery.img bs=4096
dd if=/dev/block/bml9 of=/sdcard/recovery.img bs=4096
2048+0 records in
2048+0 records out
8388608 bytes transferred in 0.768 secs (10922666 bytes/sec)
# dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096
dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096
53696+0 records in
53696+0 records out
219938816 bytes transferred in 61.234 secs (3591776 bytes/sec)
# dd if=/dev/block/stl14 of=/sdcard/data.rfs bs=4096
dd if=/dev/block/stl14 of=/sdcard/data.rfs bs=4096
6464+0 records in
6464+0 records out
26476544 bytes transferred in 1.621 secs (16333463 bytes/sec)
Q2. Is the partitiontable ROM-specific, as the reffered webpage claimed that the data-partition is /dev/block/stl14 while the mount command showed that it pointed to /dev/stl13?
Q3. How do I dump the rest of the files nedded for a complete Odin-restore (arm11boot, mibib, oemsbl, qcsbl, amss, csc.rfs)?
Then I guess I just have to compress the files...
Code:
tar -H ustar -c arm11boot mibib oemsbl qcsbl > BOOT_S5830XWKPU_CL484646_REV1.tar
md5sum -t BOOT_S5830XWKPU_CL484646_REV1.tar >> BOOT_S5830XWKPU_CL484646_REV1.tar
mv BOOT_S5830XWKPU_CL484646_REV1.tar BOOT_S5830XWKPU_CL484646_REV1.tar.md5
tar -H ustar -c amss > PHONE_S5830XWKP7_CL484646_REV1.tar
md5sum -t PHONE_S5830XWKP7_CL484646_REV1.tar >> PHONE_S5830XWKP7_CL484646_REV1.tar
mv PHONE_S5830XWKP7_CL484646_REV1.tar PHONE_S5830XWKP7_CL484646_REV1.tar.md5
tar -H ustar -c boot.img recovery.img data.rfs system.rfs > PDA_S5830XWKPU_CL484646_REV1.tar
md5sum -t PDA_S5830XWKPU_CL484646_REV1.tar >> PDA_S5830XWKPU_CL484646_REV1.tar
mv PDA_S5830XWKPU_CL484646_REV1.tar PDA_S5830XWKPU_CL484646_REV1.tar.md5
tar -H ustar -c csc.rfs > CSC_S5830OXFKP3_CL484646_REV1.tar
md5sum -t CSC_S5830OXFKP3_CL484646_REV1.tar >> CSC_S5830OXFKP3_CL484646_REV1.tar
mv CSC_S5830OXFKP3_CL484646_REV1.tar CSC_S5830OXFKP3_CL484646_REV1.tar.md5
I'm sure that SuperOneClick has an unroot option
Sent from my GT-S5830 using XDA App
This might help you: http://forum.xda-developers.com/showthread.php?t=926546
Ummm, just download the Firmware from samfirmware.com and flash it with Odin, how could there be any evidence?
I think everything is deleted when using Odin.
Greetings
PS. The language can be changed in Settings to any European I think
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
I'm sure that SuperOneClick has an unroot option
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Thats correct, but if I click unroot my adb session gets disconnected and I loose my root-previlegies. I need root-privilegies to dump the partitions.
If I root the device, connect and dump the partitions, then unroot the device there is no evidence on the phone, but su, Superuser.apk and busybox(?) is still in the dump...
Thats why I root the device, and when logged in as root, delete su and Superuser.apk and THEN dump the partitions.
traduz said:
This might help you: http://forum.xda-developers.com/showthread.php?t=926546
Click to expand...
Click to collapse
I'm not sure, but I think this article only apply for Samsung Continuum...
On this device it looks like system is mapped to /dev/block/stl9 but on the S5830 system is mapped to /dev/block/stl12 as far as I know...
ohwarumbloss said:
Ummm, just download the Firmware from samfirmware.com and flash it with Odin, how could there be any evidence?
I think everything is deleted when using Odin.
Greetings
PS. The language can be changed in Settings to any European I think
Click to expand...
Click to collapse
Yes, the firmwares on sammobile.com's official roms section are "clean", but none of the 2.3.3-2.3.5 ROMs are for the Scandinavic market. It is possible to select Swedish as a display language, but no one includes Swedish keyboard...
Beliaz said:
Yes, the firmwares on sammobile.com's official roms section are "clean", but none of the 2.3.3-2.3.5 ROMs are for the Scandinavic market. It is possible to select Swedish as a display language, but no one includes Swedish keyboard...
Click to expand...
Click to collapse
There is a "svenska" Keyboard in Settings ! Isn´t this swedish ?!
ohwarumbloss said:
There is a "svenska" Keyboard in Settings ! Isn´t this swedish ?!
Click to expand...
Click to collapse
Yes, Svenska is Swedish in swedish . What is the filename? I only found Froyo ROMs with swedish keyboard... But anyway. If the ROMs are not for this region I guess that they will claim that the warranty is void if they notice the PDA-, PHONE- and/or CSC-version is not correct.
It feels like I'm so close! Just need to find out which partitions to dump for each Odin-restorefile ...
Beliaz said:
Yes, Svenska is Swedish in swedish . What is the filename? I only found Froyo ROMs with swedish keyboard... But anyway. If the ROMs are not for this region I guess that they will claim that the warranty is void if they notice the PDA-, PHONE- and/or CSC-version is not correct.
It feels like I'm so close! Just need to find out which partitions to dump for each Odin-restorefile ...
Click to expand...
Click to collapse
I think flashing with Odin is as simple as can be ! Maybe you´r running into something while wanting this so badly lol
Just look at this : http://www.sammobile.com/showthread.php?t=34
You need to be registered, download the KS9 Firmware posted in #2
- Flash as they say with Odin !
- Do a factory reset after flashing if you get into bootloop
- The standard language is dutch I think
- Go into Settings (Instellingen) then Language (Landinstelling en tekst)
then Language (Taal selecteren) then Svenska
- Now your Phone speaks swedish
This means that the swedish dictonary will work already
This Firmware is as official as can be and noone will or can ever harm your guarantee for this. Because it is Stock and Official.
I really hope this helped, not so easy, I am from germany
-
restoring with odin is cumbersome than restoring in cwm recovery
[ this is more of a question than solution]
cant it be like first you make a backup of stock from someone else's mobile.. thn restore it to your's ?????
only problem in tht i suppose would be that stock cant be restored on custom roms ( rfs n ext problem) ... so you can flash any stock rom using odin and thn restore the backup which you made............
I'm trying to work past an issue so that I can use Adam's Ubuntu total wipe/restore. Right now it stalls on the first step of writing zeros to MLO. In this post Celtic was able to get past it using parted but I'm having trouble using the tool. When I run it in an ADB shell it tells me "Device not found" or something similar...Any suggestions?
Facts:
1) ADB is working fine. I can get a shell and browse the NT.
2) I'm unable to mount any partitions except these:
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)
/dev/block/mmcblk1p1 on /sdcard type vfat
Thanks to Celtic, I've got this licked. It's running Adam's awesome Ubuntu recovery as I type
If anyone has trouble with this, do the following.
1) Copy parted out of snowball-mod\snowball-mod\nook-update-package.zip\nook-update-package\system-x\bin. Put it in a folder with ADB.
2) 'adb push parted /'
3) 'adb shell'
4) 'parted /dev/block/mmcblk0 print'
5) answer yes, fix, fix.
Moved To Q&A
Please post all questions in the Q&A section
thanks I will link this how-to to my FAQ
Sent from XDA premium using my Nook Tablet
Can anyone help with this...
The phone is called the n7103, It's a chinese phone and the specs can be found here: https://my.dx.com/MyOrders/OrderDetail/130421001070495638
Root: Yes
Version: 4.1
Carrier: Three (UK)
My hosts files are wrong, so I can't connect to the play store and use some apps, my hosts file currently read:
127.0.0.1 localhost
#74.125.93.113 android.clients.google.com
#74.125.93.113 mtalk.google.com
Click to expand...
Click to collapse
I presume this is correct, if not please do correct me.
Now I want to use ADB to send the to the phone, however I can't for the life of me make the system read/write, The reason being I dont know what to mount, so I found the following instructions:
Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts)
Click to expand...
Click to collapse
I have looked in the /proc/mounts file and get the following read out:
rootfs / rootfs rw,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
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
/[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected]_ro /system/secro ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:96 /mnt/sdcard2 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
/dev/block/vold/179:6 /mnt/sdcard 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
/dev/block/vold/179:6 /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
Click to expand...
Click to collapse
So basically I get stuck at this part as I don't know what to type:
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 .........
I have looked for other methods including using totalcommander with root to edit hosts file but to no avail.
I can't push the file as the destination is not read write. I have also tried using terminal and chmoding the system folder as 777 but no joy.
There is also an app called "HOSTS EDITOR" however it wont allow me to insert the "#" character.
I am sorry for the very long post, I'd appreciate any help!
Thanks :good:
mount -o remount, rw /system
Click to expand...
Click to collapse
This returns no errors however when i then try the follwing command it fails.
[email protected]:/ # adb push hosts /etc/hosts
adb push hosts /etc/hosts
error: device not found
Click to expand...
Click to collapse
This phone was gently placed in a bin.
Sent from my GT-I9505 using XDA Premium 4 mobile app
adb is a program in your PC, not in Android itself, so this command:
philipkroberts said:
adb push hosts /etc/hosts
Click to expand...
Click to collapse
should be typed outside of the Android shell (type exit after you remount system, then try that command again).
hi
I am no no-ob when it comes to linux, however I am still learning the android and the linux kernel.
I wanted one of the developers to peek at the following evolving post..
http://forum.xda-developers.com/showpost.php?p=48748094&postcount=48
I am looking into one of the unhacked devices, and need some help into looking
how I can unlock the bootloader.
I want to understand which of the partition contains the bootloader and which contains the recovery...
Is there any guide to looking at the partitions in a hex-editor or something and determining if its a
boot, recovery etc...
G
assuming the device is rooted and got busybox installed, if from windows cmd just
Code:
adb shell
mount
or
Code:
adb shell
busybox mount
or if directly from phone terminal
Code:
mount
or
Code:
busybox mount
then it'll produce output of partition names and mountpoints.
an0nym0us_ said:
assuming the device is rooted and got busybox installed, if from windows cmd just
Code:
adb shell
mount
or
Code:
adb shell
busybox mount
or if directly from phone terminal
Code:
mount
or
Code:
busybox mount
then it'll produce output of partition names and mountpoints.
Click to expand...
Click to collapse
Here are some more points...
1. Device is "rooted" however this devices does not seem to be so much popular on XDA, so there is only one "Chinese root and SU" available for the device. There is no busybox or the conventional SU
2. I have (cross)compiled busybox for arm32 and bash4.1 for arm32 and installed it on the phone using adb
3. The bootloader on the device is still not unlocked, not is there any clear cut way of unlocking the bootloader on this device (LG E-455)
4. Here are some of the outputs...
Code:
$ ./adb shell /system/xbin/busybox
BusyBox v1.21.1 (2013-12-29 07:49:16 EST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices.
$ ./adb shell /system/xbin/busybox mount -v
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)
none on /acct type cgroup (rw,relatime,cpuacct)
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)
[email protected] on /system type ext4 (rw,relatime,noauto_da_alloc,commit=1,data=ordered)
[email protected] on /data type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered)
[email protected] on /cache type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
[email protected]_lg on /persist-lg type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /persist type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /mpt type ext4 (rw,nosuid,nodev,relatime,data=ordered)
/[email protected]_ro on /system/secro type ext4 (ro,relatime,data=ordered)
/dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
$ ./adb shell /system/xbin/busybox cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 0000f400 00002800 "sec_ro"
emmc_p3: 00014800 00004000 "persist_lg"
emmc_p4: 00018800 00003000 "persist"
emmc_p5: 0001b800 0000b000 "mpt"
emmc_p6: 0002b800 00005000 "swap"
emmc_p7: 00031000 0021d800 "android"
emmc_p8: 0024f000 0009a800 "cache"
emmc_p9: 002ea000 00443000 "usrdata"
emmc_p10: 0072d800 00005800 "fat"
G
Also...
I dont know the right forum to ask these android hacking questions..
The "Android Development*" forums which typically have a lot of developer presence seem to be for
the Solutions from Android Development, rather than Questions and HowTO natively hack.
The Q/A forums don't seem to have a lot of developer presence...so questions dont get answered, as most of the
Q/A viewers are no-obs or newbies.. .
G
Hi. Everyone knows that FB app saves its downloaded images in DCIM folder. At the same time, Google Photo doesn't allow to select subfolders elegible to media auto-backup. So my idea is to create a symbolic link between that Facebook subfolder and another one on different location, and so properly save photos and videos on a different folder.
There's any way to do it? I found different procedures on different site but nothing seems to work (btw, i don't know is a procedure fault or an android 10 fault), naturally using Magisk root permissions.
peppe1996 said:
Hi. Everyone knows that FB app saves its downloaded images in DCIM folder. At the same time, Google Photo doesn't allow to select subfolders elegible to media auto-backup. So my idea is to create a symbolic link between that Facebook subfolder and another one on different location, and so properly save photos and videos on a different folder.
There's any way to do it? I found different procedures on different site but nothing seems to work (btw, i don't know is a procedure fault or an android 10 fault), naturally using Magisk root permissions.
Click to expand...
Click to collapse
When you download a photo from within the Facebook app, it is stored in DCIM/Facebook. When you launch the Gallery app, the image shows up right under "Photos". Also in the gallery app if you click on the "COLLECTIONS" tab, it shows up there under "Camera".
FYI: Creating a symlink basically doesn't require Android is got rooted, unless you want to create symlinks in Android's /system partition.
I think it's really easy to create symlinks on Android.
Example:
Code:
adb devices
adb shell "mkdir -p /data/DCIM-Facebook 2>/dev/null"
adb shell "cp -a /DCIM/Facebook /data/DCIM-Facebook"
adb shell "rm -rf /DCIM/Facebook"
adb shell "ln -sf /data/DCIM-Facebook /DCIM/Facebook"
adb shell "ls -l /DCIM/Facebook"
jwoegerbauer said:
When you download a photo from within the Facebook app, it is stored in DCIM/Facebook. When you launch the Gallery app, the image shows up right under "Photos". Also in the gallery app if you click on the "COLLECTIONS" tab, it shows up there under "Camera".
FYI: Creating a symlink basically doesn't require Android is got rooted, unless you want to create symlinks in Android's /system partition.
I think it's really easy to create symlinks on Android.
Example:
Code:
adb devices
adb shell "mkdir -p /data/DCIM-Facebook 2>/dev/null"
adb shell "cp -a /DCIM/Facebook /data/DCIM-Facebook"
adb shell "rm -rf /DCIM/Facebook"
adb shell "ln -sf /data/DCIM-Facebook /DCIM/Facebook"
adb shell "ls -l /DCIM/Facebook"
Click to expand...
Click to collapse
Thanks for the answer man. I tried your procedure and this is what happened https://ibb.co/py7mkfK
This is the classic error that i had with other procedures.
@peppe1996
My fault was to NOT tell you that symlinks only are possible on partitions that support it, means their filesystem is either ext2 or ext3 or ext4 or yaffs2.
Internal sdcard /storage/emulated/0 where folder DCIM resides has filesystem /dev/fuse. Hence my script example was totally wrong.
Sorry for this.
jwoegerbauer said:
@peppe1996
My fault was to NOT tell you that symlinks only are possible on partitions that support it, means their filesystem is either ext2 or ext3 or ext4 or yaffs2.
Internal sdcard /storage/emulated/0 where folder DCIM resides has filesystem /dev/fuse. Hence my script example was totally wrong.
Sorry for this.
Click to expand...
Click to collapse
NP man. So can I do nothing about?
@peppe1996
IMHO an alternative is to create a so-called bind mount. A bind mount is an alternate view of a directory tree. Classically, mounting creates a view of a storage device as a directory tree. A bind mount instead takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount are the same as the original. Any modification on one side is immediately reflected on the other side, since the two views show the same data.
Example pseudo code:
Code:
mount -o bind /some/where /else/where
In your case this should problemfree work because both /sdcard/DCIM/Facebook and /sdcard/Pictures have the same filesystem.
FYI: mount command by default is available in any Android version.
IMPORTANT: Such a bind mount isn't persistent: you have to get it created everytime when Android boots up. That in turn requires to have an init.d script what does the job.
jwoegerbauer said:
@peppe1996
IMHO an alternative is to create a so-called bind mount. A bind mount is an alternate view of a directory tree. Classically, mounting creates a view of a storage device as a directory tree. A bind mount instead takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount are the same as the original. Any modification on one side is immediately reflected on the other side, since the two views show the same data.
Example pseudo code:
Code:
mount -o bind /some/where /else/where
In your case this should problemfree work because both /sdcard/DCIM/Facebook and /sdcard/Pictures have the same filesystem.
FYI: mount command by default is available in any Android version.
IMPORTANT: Such a bind mount isn't persistent: you have to get it created everytime when Android boots up. That in turn requires to have an init.d script what does the job.
Click to expand...
Click to collapse
Thanks mate for tips, but i think this is not i need for my scope. If I'll have the same file tree in both path, Facebook images must remain in the original folder and Google Photo will upload them. If i can preserve some file to be binded, I could try to insert a .nomedia file in DCIM/Facebook. So, DCIM/Facebook will be hidden to Google Photo and i can continue to see Facebook downloaded images in Pictures folder (on the contrary, also .nomedia will be copied and also Pictures/Facebook will be not visible on Google Photo).
@peppe1996
IMHO an alternative is to create a so-called bind mount. A bind mount is an alternate view of a directory tree. Classically, mounting creates a view of a storage device as a directory tree. A bind mount instead takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount are the same as the original. Any modification on one side is immediately reflected on the other side, since the two views show the same data.
Example pseudo code:
Code:
mount -o bind /some/where /else/where
In your case this should problemfree work because both /sdcard/DCIM/Facebook and /sdcard/Pictures have the same filesystem.
FYI: mount command by default is available in any Android version.
IMPORTANT: Such a bind mount isn't persistent: you have to get it created everytime when Android boots up. That in turn requires to have an init.d script what does the job.
Click to expand...
Click to collapse
Hello, i just bring this here up again because i have a similar problem.
I tryed your command and it passed without errors. But without the wished effect.
Code:
:/ # mount -o bind /storage/231A-1B1B/DCIM /storage/emulated/0/DCIM
This is the output of "mount"
Code:
:/ # mount <
rootfs on / type rootfs (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=891960k,nr_inodes=163101,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
none on /dev/memcg type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
none on /dev/cpuctl type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
none on /dev/bfqio type cgroup (rw,relatime,bfqio)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
tmpfs on /mnt type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=891960k,nr_inodes=163101,mode=755,gid=1000)
/dev/block/vold/public:179,65 on /mnt/media_rw/9FE1-FB0F type exfat (rw,dirsync,nosuid,nodev,noexec,noatime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,symlink=0,bps=512,errors=remount-ro)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
/dev/block/mmcblk0p23 on /system type ext4 (ro,seclabel,relatime,discard)
none on /acct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
none on /config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/block/mmcblk0p24 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p25 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
tmpfs on /sbin type tmpfs (rw,seclabel,relatime,size=891960k,nr_inodes=163101,mode=755)
/sbin/.magisk/block/cache on /sbin/.magisk/mirror/cache type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=ordered)
/sbin/.magisk/block/system on /sbin/.magisk/mirror/system type ext4 (ro,seclabel,relatime,discard)
/sbin/.magisk/block/data on /sbin/.magisk/mirror/data type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=ordered)
/sbin/.magisk/block/data on /sbin/.magisk/modules type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=891960k,nr_inodes=163101,mode=755,gid=1000)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
tmpfs on /storage/self type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=891960k,nr_inodes=163101,mode=755,gid=1000)
/dev/block/vold/public:179,97 on /mnt/media_rw/231A-1B1B type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
/mnt/media_rw/231A-1B1B on /mnt/runtime/default/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/231A-1B1B on /mnt/runtime/read/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/231A-1B1B on /mnt/runtime/write/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/231A-1B1B on /storage/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/231A-1B1B on /storage/emulated/0/DCIM type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
The last line appears after i try to mount the folder. Does anybody k ow what goes wrong here?
Marco