please don't try it if you don't know how to handle it
hello guys
i ported CWM recovery for our device b7510
but it still alpha and i hope some one can help me
the problem is stock kernel rfs i can't mount system or data and cache
only sdcard
i need help guys
Download
up .
can you post the output of:
Code:
mount
or the boot.img ?
hey
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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0002,dmask=0002,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,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=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.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
# ls -l /dev/block
ls -l /dev/block
brw------- root root 138, 14 2011-12-27 19:12 stl14
brw------- root root 138, 13 2011-12-27 19:12 stl13
brw------- root root 138, 12 2011-12-27 19:12 stl12
brw------- root root 138, 11 2011-12-27 19:12 stl11
brw------- root root 138, 10 2011-12-27 19:12 stl10
brw------- root root 138, 9 2011-12-27 19:12 stl9
brw------- root root 138, 8 2011-12-27 19:12 stl8
brw------- root root 138, 7 2011-12-27 19:12 stl7
brw------- root root 138, 6 2011-12-27 19:12 stl6
brw------- root root 138, 5 2011-12-27 19:12 stl5
brw------- root root 138, 4 2011-12-27 19:12 stl4
brw------- root root 138, 3 2011-12-27 19:12 stl3
brw------- root root 138, 2 2011-12-27 19:12 stl2
brw------- root root 138, 1 2011-12-27 19:12 stl1
brw------- root root 137, 14 2011-12-27 19:12 bml14
brw------- root root 137, 13 2011-12-27 19:12 bml13
brw------- root root 137, 12 2011-12-27 19:12 bml12
brw------- root root 137, 11 2011-12-27 19:12 bml11
brw------- root root 137, 10 2011-12-27 19:12 bml10
brw------- root root 137, 9 2011-12-27 19:12 bml9
brw------- root root 137, 8 2011-12-27 19:12 bml8
brw------- root root 137, 7 2011-12-27 19:12 bml7
brw------- root root 137, 6 2011-12-27 19:12 bml6
brw------- root root 137, 5 2011-12-27 19:12 bml5
brw------- root root 137, 4 2011-12-27 19:12 bml4
brw------- root root 137, 3 2011-12-27 19:12 bml3
brw------- root root 137, 2 2011-12-27 19:12 bml2
brw------- root root 137, 1 2011-12-27 19:12 bml1
brw------- root root 137, 0 2011-12-27 19:12 bml0!c
drwxr-xr-x root root 2011-12-27 19:12 vold
brw------- root root 7, 7 2011-12-27 19:12 loop7
brw------- root root 7, 6 2011-12-27 19:12 loop6
brw------- root root 7, 5 2011-12-27 19:12 loop5
brw------- root root 7, 4 2011-12-27 19:12 loop4
brw------- root root 7, 3 2011-12-27 19:12 loop3
brw------- root root 7, 2 2011-12-27 19:12 loop2
brw------- root root 7, 1 2011-12-27 19:12 loop1
brw------- root root 7, 0 2011-12-27 19:12 loop0
brw------- root root 1, 7 2011-12-27 19:12 ram7
brw------- root root 1, 6 2011-12-27 19:12 ram6
brw------- root root 1, 5 2011-12-27 19:12 ram5
brw------- root root 1, 4 2011-12-27 19:12 ram4
brw------- root root 1, 3 2011-12-27 19:12 ram3
brw------- root root 1, 2 2011-12-27 19:12 ram2
brw------- root root 1, 1 2011-12-27 19:12 ram1
brw------- root root 1, 0 2011-12-27 19:12 ram0
#
boot.img here
thanks
updated here cwm recovery
enjoy
thanks to Skin1980
updated
download here
thanks
Is it for the Gingerbread version? Thanks
netomx said:
Is it for the Gingerbread version? Thanks
Click to expand...
Click to collapse
no it is for froyo
Thanx for the efforts mazen, could u please re-upload the last file "recovery1" if not updated with another one.
i can't update it any more i lost my phone
ok i uploaded it to dropbox
download here
Thanx alot, and sorry about ur phone..
nothing for gingerbread???
soory about ur phone
it is work? anyone try this file on b7510?
pls answer galaxy pro user or anybody can help me for back up my stock rom?
it is not work.................
اهلا الاخ مازن ,,, انا وليد الهادي
اسف على الازعاج ,
حبيت اسالك ايش اللي صار في جوالك
is that still ALPHA?
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
is that still alpha version?
any updates to this?
Samsung Galaxy pro CWM
hiii........can you again post the download link as the link you have mentioned doesnt have any file or its been deleted...thanks
dropbox link is dead or blocked
vikd007 said:
hiii........can you again post the download link as the link you have mentioned doesnt have any file or its been deleted...thanks
Click to expand...
Click to collapse
Please share an updated link of CWM recovery for B7510
Thanks
Hey anyone still use galaxy pro?
Sent from my GT-I9300 using XDA Free mobile app
Related
Hey, after I flashed MIUI from CM7 I lost my network connection.
baseband: unknown
imei: unknown
I thought it was a problem with my efs/stl3 but I found a backup of both efs and stl3 partition and after restoring them (odin stl3) I still don't have network connection.
btw, when I am on stock JFD firmware and use adb to check what's inside /dev/block it shows all partitions but when I navigate to the block folder using root explorer it shows only an empty folder named vold. and the root is missing the folder radio. is that normal ?
also, I installed miui, and now adb is showing only the following files:
cd dev/block
# ls
ls
bml12 loop5 mtdblock0 mtdblock6 ram11 ram3 ram9
loop0 loop6 mtdblock1 mtdblock7 ram12 ram4 vold
loop1 loop7 mtdblock2 platform ram13 ram5
loop2 mmcblk0 mtdblock3 ram0 ram14 ram6
loop3 mmcblk0p1 mtdblock4 ram1 ram15 ram7
loop4 mmcblk0p2 mtdblock5 ram10 ram2 ram8
#
root explorer shows bml12 and vold, and now there is a folder radio on root.
what's wrong with the phone ?
is it reparable ?
Interesting update found from cheesecaking on the build.prop 676.226.3.XT910.Retail.en.EU. It has an upgrade to the cdt.bin so it may not be fastbootable from back to .33....
It is still 4.0.4 by looking at the updater-script.
http://crackflasher.com/dev/mattlgr...Blur_Version.676.226.3.XT910.Retail.en.EU.zip
Might as well post it, feel free to flash at your own risk, I sure am not though.
mattlgroff said:
Interesting update found from cheesecaking on the build.prop 676.226.3.XT910.Retail.en.EU. It has an upgrade to the cdt.bin so it may not be fastbootable from back to .33....
It is still 4.0.4 by looking at the updater-script.
http://crackflasher.com/dev/mattlgr...Blur_Version.676.226.3.XT910.Retail.en.EU.zip
Might as well post it, feel free to flash at your own risk, I sure am not though.
Click to expand...
Click to collapse
Thanks.. Will look into it & extract usable stuff
Update :
the new cdt.bin will remove webtop partition. Not good for those using my dual boot solution (BootMenu).
The main secure version is not upgraded, so it can be downgrade back to .33 cdt.bin. It's not a big problem now.
Not sure how it will be in official release though, but this is an early signed that Moto will removed the abandon webtop partition in future.
or maybe this file is for their internal use.(development unit) because this new cdt.bin also remove emstorage partitition.
post-build=RTGB/XT910_RTGB/umts_spyder:4.0.4/6.7.6_ICS_DUMMY/1341969974:user/release-keys
post-timestamp=1341967314
pre-build=RTGB/XT910_RTGB/umts_spyder:4.0.4/6.7.6-226_SPU-DE-TA-2/1340775289:user/release-keys
pre-device=umts_spyder
Click to expand...
Click to collapse
It's hard for an badass Crackflasher, not to try this. But if it will remove the Webtop Partition, it's not worth it.
The Fastboot ICS got no webtop in it, so there's no way to get this Partition back, right?
Gesendet von meinem XT910 mit Tapatalk 2
.33 cdt.bin still has webtop in its partition table.
But where did they relocate the space?
HSD-Pilot said:
It's hard for an badass Crackflasher, not to try this. But if it will remove the Webtop Partition, it's not worth it.
The Fastboot ICS got no webtop in it, so there's no way to get this Partition back, right?
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
If you fastboot back and restore someone's extracted webtop.img it should work fine... in theory?
I will try to patch whole system tmr and c if theres anything new on framework and app. (or something we could use without new cdt.bin)
I would try patch kernel as well but i won't test it on my phone(i dont rly like to mess with my cid)
Enviado desde mi XT910 usando Tapatalk 2
My Cid is dead already XD...should be an warning to myself not to try anything...
Gesendet von meinem XT910 mit Tapatalk 2
HSD-Pilot said:
The Fastboot ICS got no webtop in it, so there's no way to get this Partition back, right?
Click to expand...
Click to collapse
cdt.bin is like a partition table in PC.
farhanito said:
But where did they relocate the space?
Click to expand...
Click to collapse
the removed webtop partition space is assign to userdata (/data). You got a big data partition with this cdt.bin.
If this is happening, we'll multi-boot from userdata partition. It's a good thing, it solve the 2nd-system size limitation.
leisures said:
I would try patch kernel as well but i won't test it on my phone(i dont rly like to mess with my cid)
Click to expand...
Click to collapse
upgrading kernel like this is safe
Code:
fastboot flash boot ics_dummy.img
if it failed verification, jut flash again with previous flash-able version
i don't dual boot so there shouldn't be any reason not to flash this? :fingers-crossed:
Thanks for the leaks matt!
tomow said:
i don't dual boot so there shouldn't be any reason not to flash this? :fingers-crossed:
Thanks for the leaks matt!
Click to expand...
Click to collapse
You got my OK, so run Forest, run
Gesendet von meinem XT910 mit Tapatalk 2
tomow said:
i don't dual boot so there shouldn't be any reason not to flash this? :fingers-crossed:
Thanks for the leaks matt!
Click to expand...
Click to collapse
It's your phone, it's up to you. we have nothing to do with it. Just sharing info here
whirleyes said:
It's your phone, it's up to you. we have nothing to do with it. Just sharing info here
Click to expand...
Click to collapse
Thanks for the insight whirleyes, it seems like I found an interesting update here...
Hello just a request. Can someone make a tutorial for users like me who dualbooted or used the 2nd system to flash this new update?
Sent from my XT910 using xda premium
Thought by the file size that this was an update like 676 was. Wiped my whole system instead that's all my fault though. Runs very nicely though
tomow said:
Thought by the file size that this was an update like 676 was. Wiped my whole system instead that's all my fault though. Runs very nicely though
Click to expand...
Click to collapse
Can you share the output of these command (using adb)
Code:
adb shell mount
Code:
adb shell ls -la /dev/block/
Code:
adb shell df
Can you post an Screenshot of the Info (Baseband, Builddate and stuff)
Gesendet von meinem XT910 mit Tapatalk 2
thanks matt.
@Whirleyes
If they remove webtop partition, you said we'll dual boot from data partition. Does that mean that both system will use same data? Or different data on same partition?
i wonder if this update really update system or if it just a dummy to try the partition switching.
adb shell mount
C:\Android\platform-tools>adb shell 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
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/system /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/pds /pds ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barr
ier=1,data=ordered 0 0
/dev/block/preinstall /preinstall ext3 rw,nosuid,nodev,noatime,nodiratime,errors
=continue,barrier=1,data=ordered 0 0
/dev/block/userdata /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continu
e,barrier=1,data=ordered 0 0
/dev/block/cache /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,
barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/sdcard-ext vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
C:\Android\platform-tools>adb shell ls -la /dev/block/
lrwxrwxrwx root root 2012-07-17 07:47 boot -> /dev/block/mmcblk
1p14
lrwxrwxrwx root root 2012-07-17 07:47 cache -> /dev/block/mmcbl
k1p21
lrwxrwxrwx root root 2012-07-17 07:47 cdrom -> /dev/block/mmcbl
k1p16
lrwxrwxrwx root root 2012-07-17 07:47 cid -> /dev/block/mmcblk1
p18
lrwxrwxrwx root root 2012-07-17 07:47 kpanic -> /dev/block/mmcb
lk1p19
brw------- root root 7, 0 2012-07-17 07:47 loop0
brw------- root root 7, 1 2012-07-17 07:47 loop1
brw------- root root 7, 2 2012-07-17 07:47 loop2
brw------- root root 7, 3 2012-07-17 07:47 loop3
brw------- root root 7, 4 2012-07-17 07:47 loop4
brw------- root root 7, 5 2012-07-17 07:47 loop5
brw------- root root 7, 6 2012-07-17 07:47 loop6
brw------- root root 7, 7 2012-07-17 07:47 loop7
lrwxrwxrwx root root 2012-07-17 07:47 misc -> /dev/block/mmcblk
1p17
brw------- root root 179, 96 2012-07-17 07:47 mmcblk0
brw-rw---- root mot_tcmd 179, 97 2012-07-17 07:47 mmcblk0p1
brw------- root root 179, 0 2012-07-17 07:47 mmcblk1
brw------- root root 179, 32 2012-07-17 07:47 mmcblk1boot0
brw------- root root 179, 64 2012-07-17 07:47 mmcblk1boot1
brw-rw---- root mot_tcmd 179, 1 2012-07-17 07:47 mmcblk1p1
brw------- root root 179, 10 2012-07-17 07:47 mmcblk1p10
brw------- root root 179, 11 2012-07-17 07:47 mmcblk1p11
brw------- root root 179, 12 2012-07-17 07:47 mmcblk1p12
brw------- root root 179, 13 2012-07-17 07:47 mmcblk1p13
brw------- root root 179, 14 2012-07-17 07:47 mmcblk1p14
brw------- root root 179, 15 2012-07-17 07:47 mmcblk1p15
brw------- root root 179, 16 2012-07-17 07:47 mmcblk1p16
brw-rw---- root mot_tcmd 179, 17 2012-07-17 07:47 mmcblk1p17
brw-rw---- root mot_tcmd 179, 18 2012-07-17 07:47 mmcblk1p18
brw------- root root 179, 19 2012-07-17 07:47 mmcblk1p19
brw------- root root 179, 2 2012-07-17 07:47 mmcblk1p2
brw------- root root 179, 20 2012-07-17 07:47 mmcblk1p20
brw------- root root 179, 21 2012-07-17 07:47 mmcblk1p21
brw------- root root 179, 22 2012-07-17 07:47 mmcblk1p22
brw------- root root 179, 23 2012-07-17 07:47 mmcblk1p23
brw------- root root 179, 24 2012-07-17 07:47 mmcblk1p24
brw------- root root 179, 25 2012-07-17 07:47 mmcblk1p25
brw------- root root 179, 26 2012-07-17 07:47 mmcblk1p26
brw------- root root 179, 3 2012-07-17 07:47 mmcblk1p3
brw------- root root 179, 4 2012-07-17 07:47 mmcblk1p4
brw------- root root 179, 5 2012-07-17 07:47 mmcblk1p5
brw------- root root 179, 6 2012-07-17 07:47 mmcblk1p6
brw------- root root 179, 7 2012-07-17 07:47 mmcblk1p7
brw------- root root 179, 8 2012-07-17 07:47 mmcblk1p8
brw------- root root 179, 9 2012-07-17 07:47 mmcblk1p9
lrwxrwxrwx root root 2012-07-17 07:47 pds -> /dev/block/mmcblk1
p7
drwxr-xr-x root root 2012-07-17 07:47 platform
lrwxrwxrwx root root 2012-07-17 07:47 preinstall -> /dev/block/
mmcblk1p22
brw------- root root 1, 0 2012-07-17 07:47 ram0
brw------- root root 1, 1 2012-07-17 07:47 ram1
brw------- root root 1, 10 2012-07-17 07:47 ram10
brw------- root root 1, 11 2012-07-17 07:47 ram11
brw------- root root 1, 12 2012-07-17 07:47 ram12
brw------- root root 1, 13 2012-07-17 07:47 ram13
brw------- root root 1, 14 2012-07-17 07:47 ram14
brw------- root root 1, 15 2012-07-17 07:47 ram15
brw------- root root 1, 2 2012-07-17 07:47 ram2
brw------- root root 1, 3 2012-07-17 07:47 ram3
brw------- root root 1, 4 2012-07-17 07:47 ram4
brw------- root root 1, 5 2012-07-17 07:47 ram5
brw------- root root 1, 6 2012-07-17 07:47 ram6
brw------- root root 1, 7 2012-07-17 07:47 ram7
brw------- root root 1, 8 2012-07-17 07:47 ram8
brw------- root root 1, 9 2012-07-17 07:47 ram9
lrwxrwxrwx root root 2012-07-17 07:47 recovery -> /dev/block/mm
cblk1p15
lrwxrwxrwx root root 2012-07-17 07:47 system -> /dev/block/mmcb
lk1p20
lrwxrwxrwx root root 2012-07-17 07:47 userdata -> /dev/block/mm
cblk1p23
lrwxrwxrwx root root 2012-07-17 07:47 utags -> /dev/block/mmcbl
k1p8
drwxr-xr-x root root 2012-07-17 07:47 vold
brw------- root root 253, 0 2012-07-17 07:47 zram0
C:\Android\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 420M 76K 420M 4096
/mnt/asec 420M 0K 420M 4096
/mnt/obb 420M 0K 420M 4096
/system 770M 751M 19M 1024
/pds 3M 1M 2M 1024
/preinstall 8M 3M 5M 1024
/data 1G 786M 524M 2048
/cache 708M 16M 691M 4096
/mnt/sdcard 1G 786M 524M 2048
/mnt/sdcard-ext 14G 8G 6G 8192
C:\Android\platform-tools>
sevenup30 said:
thanks matt.
@Whirleyes
If they remove webtop partition, you said we'll dual boot from data partition. Does that mean that both system will use same data? Or different data on same partition?
i wonder if this update really update system or if it just a dummy to try the partition switching.
Click to expand...
Click to collapse
Opps... the /data partition didn't grow.
the /mnt/sdcard-ext (fat) grow to 14GB?
thanks HSD-Pilot
But sdcard-ext doesn't count, right?
He's using 16Gb microsd
/mnt/sdcard is shrunk to 1Gb?
Hi,
i rooted my T15A tablet with "Root_with_Restore_by_Bin4ry_v17" tool and then installed/flased "SuperCharger_Starter_Kit_RC12". After the flash my internal storage shows up with 0 byte and i am not able to install any app. A factory reset did not help too.
I´ve got another original T15A tablet and want to create a full backup of this and flash it to the bricked one.
I found some guides on how to create a backup by connecting to an adb shell. This guides are all device specific and i now dont know
what to backup under /dev/blocks/ ....
- Any idear/guide how to do a full backup / restore?
- Maybe we just can fix the 0 byte error (but i didnt find generic solution about that)
Code:
[email protected]:/ # ls -al /dev/block/
ls -al /dev/block/
brw------- root root 7, 0 2012-12-04 22:12 loop0
brw------- root root 7, 1 2012-12-04 22:12 loop1
brw------- root root 7, 2 2012-12-04 22:12 loop2
brw------- root root 7, 3 2012-12-04 22:12 loop3
brw------- root root 7, 4 2012-12-04 22:12 loop4
brw------- root root 7, 5 2012-12-04 22:12 loop5
brw------- root root 7, 6 2012-12-04 22:12 loop6
brw------- root root 7, 7 2012-12-04 22:12 loop7
brw------- root root 93, 0 2012-12-04 22:12 nanda
brw------- root root 93, 8 2012-12-04 22:12 nandb
brw------- root root 93, 16 2012-12-04 22:12 nandc
brw------- root root 93, 24 2012-12-04 22:12 nandd
brw------- root root 93, 32 2012-12-04 22:12 nande
brw-rw-rw- system system 93, 40 2012-12-04 22:12 nandf
brw------- root root 93, 48 2012-12-04 22:12 nandg
brw------- root root 93, 56 2012-12-04 22:12 nandh
brw------- root root 93, 64 2012-12-04 22:12 nandi
brw------- root root 93, 72 2012-12-04 22:12 nandj
brw------- root root 1, 0 2012-12-04 22:12 ram0
brw------- root root 1, 1 2012-12-04 22:12 ram1
drwxr-xr-x root root 2012-12-04 22:12 vold
[email protected]:/ # 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,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 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/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
*bump* (is this allowed here?)
Solved, after opening the tablets back cover and searching for the mainboard model i found out that the generic "T15A" tablet uses the same covers and the same mainboard than the goclever.com tablets. So i used the goclever stock rom and flashed it, works quite nice now.
Mod, please close.
Hi devs,
I recently bought a iBerry CoreX4 tablet 9.7 inch tablet. It houses a Samsung Exynos 4412 processor. We are able to root the tab using the Exynos Exploit apk. Being new to the market the tab has no CWM. I tried flashing Galaxy Note 10.1's recovery image. All the procedures I've seen in the internet for flashing recovery images failed with this tab. So I just tried the following.....
iBerry recently released a firmware. I replaced the ramdisk-recovery-uboot.img with recovery.img ( changed ) of galaxy note 10.1 and then upgraded the firmware. The upgradation was successful. But when I tried to enter the recovery mode it just restarts the tab.
Now I have the following questions?
1. Did i do it right?
2. Is the CWM based on the processor? If yes, why cwm recovery for 10.1 did not work with iBerry?
3. Is there any other recovery image you could suggest that would replace the custom one?
Please do help us (iBerry Users) in this one..... as we are not able to flash any custom ROM's ( i guess CWM is needed for flashing ROMs )
Thank you again.....
Tab Specs:
Processor - Samsung Exynos 4412
Quad Core 1.6 GHz
RAM - 2 GB
Display - 9.7 inches
No hard keys except volume control and power button
Rooting done using ExynosAbuse.apk thanks to alephzain and chainfire
i had posted the thread link in the facebook on OFFICIAL IBERRY INDIA PAGE...
ANYONE WILL SURELY HELP YOU OUT
HOPE FOR THE BEST
Thanks
tipu006 said:
i had posted the thread link in the facebook on OFFICIAL IBERRY INDIA PAGE...
ANYONE WILL SURELY HELP YOU OUT
HOPE FOR THE BEST
Click to expand...
Click to collapse
Thanks tipu....
CWM
Tried flashing the Note 10.1 and Note 2 recover image to the recovery partition mmcblk0p4 using dd. Flashing succeded. But when tried to boot on recovery it says
Error:Can't mount /cache
and the stock recovery is set again ( thank God the phoned did not brick )..... In the experiment I corrupted the sd card .......
I found ways to flash the recoveries ( well i hope ).... All we need is a proper CWM.
Am learning the error that was displayed. Please guys, do help in the error produced.......
Step By Step Method of rooting using exynos exploit.
samsylvestertty said:
Hi devs,
I recently bought a iBerry CoreX4 tablet 9.7 inch tablet. It houses a Samsung Exynos 4412 processor. We are able to root the tab using the Exynos Exploit apk. Being new to the market the tab has no CWM. I tried flashing Galaxy Note 10.1's recovery image. All the procedures I've seen in the internet for flashing recovery images failed with this tab. So I just tried the following.....
iBerry recently released a firmware. I replaced the ramdisk-recovery-uboot.img with recovery.img ( changed ) of galaxy note 10.1 and then upgraded the firmware. The upgradation was successful. But when I tried to enter the recovery mode it just restarts the tab.
Now I have the following questions?
1. Did i do it right?
2. Is the CWM based on the processor? If yes, why cwm recovery for 10.1 did not work with iBerry?
3. Is there any other recovery image you could suggest that would replace the custom one?
Please do help us (iBerry Users) in this one..... as we are not able to flash any custom ROM's ( i guess CWM is needed for flashing ROMs )
Thank you again.....
Tab Specs:
Processor - Samsung Exynos 4412
Quad Core 1.6 GHz
RAM - 2 GB
Display - 9.7 inches
No hard keys except volume control and power button
Rooting done using ExynosAbuse.apk thanks to alephzain and chainfire
Click to expand...
Click to collapse
Hi i am new to android and core x4 is my first android device. will you please post the method of rooting with exynos apk. also how to unroot it after for claiming warranty
Root using ExynosAbuse.apk
gamerzone said:
Hi i am new to android and core x4 is my first android device. will you please post the method of rooting with exynos apk. also how to unroot it after for claiming warranty
Click to expand...
Click to collapse
The apk is developed by chainfire and the related post is this.
Click here to download the apk. Install the apk ( if you don't know the installation procedure please look below ) .
Open the application. You have options to either root or unroot. Click it. The root process will start. During the process you will be prompted to grant / deny the application. Choose grant and your device is rooted.
Installing an apk
1. Take the apk to your tablet
2. Use ES File Explorer to browse to the file
3. Just click the ExynosAbuse.apk file and follow the procedures
And rooting Core X4 doesn't make any difference. Cos there are no CWMs or Custom ROMs for the tablet at present. You can still try applications that need elevated permissions to run ( titanium backup etc ) after rooting.....
If you have doubts pls ping back
Tried various methods. Learnt little things about Core X4
Core X4 has 5 partitions
1. mmcblk0 - boot
2. mmcblk0p1 - Internal Storage
3. mmcblk0p2 - System
3. mmcblk0p3 - Data
4. mmcblk0p4 - Cache
used
Code:
cat /proc/partitions
cat /proc/mounts
to find out the partition info
No separate partition for recovery. It resides in the boot partition.
Tried to copy the boot partition by using dd...
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/boot.img
but the boot image's size was more than 4 GB and was not supported by our internal storage.... Also tried to use a pen drive ( NTFS 8 GB ) for dd'ing but it says Read Only File System and fails
Any Help .....
any one who can help us.....
Sent from my AUXUS CoreX4 3G using xda app-developers app
samsylvestertty said:
Tried various methods. Learnt little things about Core X4
Core X4 has 5 partitions
1. mmcblk0 - boot
2. mmcblk0p1 - Internal Storage
3. mmcblk0p2 - System
3. mmcblk0p3 - Data
4. mmcblk0p4 - Cache
used
Code:
cat /proc/partitions
cat /proc/mounts
to find out the partition info
No separate partition for recovery. It resides in the boot partition.
Tried to copy the boot partition by using dd...
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/boot.img
but the boot image's size was more than 4 GB and was not supported by our internal storage.... Also tried to use a pen drive ( NTFS 8 GB ) for dd'ing but it says Read Only File System and fails
Any Help .....
Click to expand...
Click to collapse
Hmmm...well, if the Samsung Note II that has the same Exynos 4412 SOC chipset puts their recovery in the boot.img, then maybe we could use one from that tab? I've done some similar experimentation with my Hyundai T7s Exynos 4412 tab and I've not had any luck yet.
samsylvestertty said:
Tried flashing the Note 10.1 and Note 2 recover image to the recovery partition mmcblk0p4 using dd. Flashing succeded. But when tried to boot on recovery it says
Error:Can't mount /cache
and the stock recovery is set again ( thank God the phoned did not brick )..... In the experiment I corrupted the sd card .......
I found ways to flash the recoveries ( well i hope ).... All we need is a proper CWM.
Am learning the error that was displayed. Please guys, do help in the error produced.......
Click to expand...
Click to collapse
Hello,
I've managed to compile CWM (using latest CM10.1) for Hyundai T7s.
The partition map used came from ramdisk-recovery-uboot and it's like this:
mmcblk0 - boot
mmcblk0p1 - Internal Storage
mmcblk0p2 - System
mmcblk0p3 - Data
mmcblk0p4 - Cache
I cannot find a way to flash this image. Tried replacing ramdisk-recovery-uboot with the ramdisk image produced by CM10.1, but the tablet reboots.
I'll upload recovery.img and relative files later and post link here to test.
Frontier said:
Hello,
I've managed to compile CWM (using latest CM10.1) for Hyundai T7s.
The partition map used came from ramdisk-recovery-uboot and it's like this:
mmcblk0 - boot
mmcblk0p1 - Internal Storage
mmcblk0p2 - System
mmcblk0p3 - Data
mmcblk0p4 - Cache
I cannot find a way to flash this image. Tried replacing ramdisk-recovery-uboot with the ramdisk image produced by CM10.1, but the tablet reboots.
I'll upload recovery.img and relative files later and post link here to test.
Click to expand...
Click to collapse
Hi Frontier,
Congrats on your new CWM compilation. As I told earlier, the Exynos 44** based devices does not have a separate partition for recovery. The recovery resides with the boot partition. That leaves you with two options ( IMHO ).
1. Flash the entire boot partition with a boot.img file that has your compiled recovery
2. Take an image of your device's boot partition. Replace the stock recovery related files with your custom one.
The second option needs Linux based OS. There are commands to pack and repack img files.
Or in windows you can use CYGWIN ( you can do it to some extent )
It's been a long time involving in these topcis . I sold my tablet too.... It's being used by some android developers for creating custom recovery. Hope to hear a good news from them..... Maybe we can get a clear idea after that....
I've uploaded to GitHub my work regarding porting CM10.1 to T7S.
These files *PRODUCE* a ROM but I wouldn't flash it to a tablet.
Needs work with drivers (blobs) for MTK6620 combo chip (GPS, WiFi, BT and guess what: the T7s has also FM radio).
Maybe someone more knowledgable than me can work on this and produce something that works.
https://github.com/Frontier314/t7s_cm10.1
Frontier said:
Hello,
I've managed to compile CWM (using latest CM10.1) for Hyundai T7s.
The partition map used came from ramdisk-recovery-uboot and it's like this:
mmcblk0 - boot
mmcblk0p1 - Internal Storage
mmcblk0p2 - System
mmcblk0p3 - Data
mmcblk0p4 - Cache
I cannot find a way to flash this image. Tried replacing ramdisk-recovery-uboot with the ramdisk image produced by CM10.1, but the tablet reboots.
I'll upload recovery.img and relative files later and post link here to test.
Click to expand...
Click to collapse
You are wrong in partition, the boot is installed in mmcblk0boot0, and not where you have it pointed out.
assasa said:
You are wrong in partition, the boot is installed in mmcblk0boot0, and not where you have it pointed out.
Click to expand...
Click to collapse
There is no mmcblk0boot0.
[email protected]:/ # ls -l /dev/block
brw------- root root 254, 0 2013-06-26 15:45 dm-0
brw------- root root 254, 1 2013-06-26 15:45 dm-1
brw------- root root 254, 10 2013-06-26 15:45 dm-10
brw------- root root 254, 11 2013-06-26 15:45 dm-11
brw------- root root 254, 12 2013-06-26 15:45 dm-12
brw------- root root 254, 13 2013-06-26 15:45 dm-13
brw------- root root 254, 14 2013-06-26 15:45 dm-14
brw------- root root 254, 15 2013-06-26 15:45 dm-15
brw------- root root 254, 16 2013-06-26 15:45 dm-16
brw------- root root 254, 17 2013-06-26 15:45 dm-17
brw------- root root 254, 18 2013-06-26 15:45 dm-18
brw------- root root 254, 19 2013-06-26 15:45 dm-19
brw------- root root 254, 2 2013-06-26 15:45 dm-2
brw------- root root 254, 20 2013-06-26 15:45 dm-20
brw------- root root 254, 21 2013-06-26 15:45 dm-21
brw------- root root 254, 22 2013-06-26 15:45 dm-22
brw------- root root 254, 23 2013-06-26 15:45 dm-23
brw------- root root 254, 24 2013-06-26 15:45 dm-24
brw------- root root 254, 25 2013-06-26 15:45 dm-25
brw------- root root 254, 26 2013-06-26 15:45 dm-26
brw------- root root 254, 27 2013-06-26 15:45 dm-27
brw------- root root 254, 28 2013-06-26 15:45 dm-28
brw------- root root 254, 29 2013-06-26 15:45 dm-29
brw------- root root 254, 3 2013-06-26 15:45 dm-3
brw------- root root 254, 30 2013-06-26 15:45 dm-30
brw------- root root 254, 31 2013-06-26 15:45 dm-31
brw------- root root 254, 32 2013-06-26 15:45 dm-32
brw------- root root 254, 34 2013-06-26 15:46 dm-34
brw------- root root 254, 35 2013-06-26 15:46 dm-35
brw------- root root 254, 36 2013-06-26 15:46 dm-36
brw------- root root 254, 37 2013-06-26 15:46 dm-37
brw------- root root 254, 38 2013-06-26 15:46 dm-38
brw------- root root 254, 39 2013-06-26 15:46 dm-39
brw------- root root 254, 4 2013-06-26 15:45 dm-4
brw------- root root 254, 40 2013-06-26 15:46 dm-40
brw------- root root 254, 41 2013-06-26 15:46 dm-41
brw------- root root 254, 42 2013-06-26 15:46 dm-42
brw------- root root 254, 43 2013-06-26 15:46 dm-43
brw------- root root 254, 44 2013-06-26 15:46 dm-44
brw------- root root 254, 45 2013-06-26 15:46 dm-45
brw------- root root 254, 46 2013-06-26 15:46 dm-46
brw------- root root 254, 47 2013-06-26 15:46 dm-47
brw------- root root 254, 48 2013-06-26 15:46 dm-48
brw------- root root 254, 49 2013-06-26 15:46 dm-49
brw------- root root 254, 5 2013-06-26 15:45 dm-5
brw------- root root 254, 6 2013-06-26 15:45 dm-6
brw------- root root 254, 7 2013-06-26 15:45 dm-7
brw------- root root 254, 8 2013-06-26 15:45 dm-8
brw------- root root 254, 9 2013-06-26 15:45 dm-9
brw------- root root 7, 0 2013-06-26 15:45 loop0
brw------- root root 7, 1 2013-06-26 15:45 loop1
brw-rw---- root root 7, 10 2013-06-26 15:45 loop10
brw-rw---- root root 7, 11 2013-06-26 15:45 loop11
brw-rw---- root root 7, 12 2013-06-26 15:45 loop12
brw-rw---- root root 7, 13 2013-06-26 15:45 loop13
brw-rw---- root root 7, 14 2013-06-26 15:45 loop14
brw-rw---- root root 7, 15 2013-06-26 15:45 loop15
brw-rw---- root root 7, 16 2013-06-26 15:45 loop16
brw-rw---- root root 7, 17 2013-06-26 15:45 loop17
brw-rw---- root root 7, 18 2013-06-26 15:45 loop18
brw-rw---- root root 7, 19 2013-06-26 15:45 loop19
brw------- root root 7, 2 2013-06-26 15:45 loop2
brw-rw---- root root 7, 20 2013-06-26 15:45 loop20
brw-rw---- root root 7, 21 2013-06-26 15:45 loop21
brw-rw---- root root 7, 22 2013-06-26 15:45 loop22
brw-rw---- root root 7, 23 2013-06-26 15:45 loop23
brw-rw---- root root 7, 24 2013-06-26 15:45 loop24
brw-rw---- root root 7, 25 2013-06-26 15:45 loop25
brw-rw---- root root 7, 26 2013-06-26 15:45 loop26
brw-rw---- root root 7, 27 2013-06-26 15:45 loop27
brw-rw---- root root 7, 28 2013-06-26 15:45 loop28
brw-rw---- root root 7, 29 2013-06-26 15:45 loop29
brw------- root root 7, 3 2013-06-26 15:45 loop3
brw-rw---- root root 7, 30 2013-06-26 15:45 loop30
brw-rw---- root root 7, 31 2013-06-26 15:45 loop31
brw-rw---- root root 7, 32 2013-06-26 15:45 loop32
brw-rw---- root root 7, 33 2013-06-26 15:45 loop33
brw-rw---- root root 7, 34 2013-06-26 15:46 loop34
brw-rw---- root root 7, 35 2013-06-26 15:46 loop35
brw-rw---- root root 7, 36 2013-06-26 15:46 loop36
brw-rw---- root root 7, 37 2013-06-26 15:46 loop37
brw-rw---- root root 7, 38 2013-06-26 15:46 loop38
brw-rw---- root root 7, 39 2013-06-26 15:46 loop39
brw------- root root 7, 4 2013-06-26 15:45 loop4
brw-rw---- root root 7, 40 2013-06-26 15:46 loop40
brw-rw---- root root 7, 41 2013-06-26 15:46 loop41
brw-rw---- root root 7, 42 2013-06-26 15:46 loop42
brw-rw---- root root 7, 43 2013-06-26 15:46 loop43
brw-rw---- root root 7, 44 2013-06-26 15:46 loop44
brw-rw---- root root 7, 45 2013-06-26 15:46 loop45
brw-rw---- root root 7, 46 2013-06-26 15:46 loop46
brw-rw---- root root 7, 47 2013-06-26 15:46 loop47
brw-rw---- root root 7, 48 2013-06-26 15:46 loop48
brw-rw---- root root 7, 49 2013-06-26 15:46 loop49
brw------- root root 7, 5 2013-06-26 15:45 loop5
brw------- root root 7, 6 2013-06-26 15:45 loop6
brw------- root root 7, 7 2013-06-26 15:45 loop7
brw-rw---- root root 7, 8 2013-06-26 15:45 loop8
brw-rw---- root root 7, 9 2013-06-26 15:45 loop9
brw------- root root 179, 0 2013-06-26 15:45 mmcblk0
brw------- root root 179, 1 2013-06-26 15:45 mmcblk0p1
brw------- root root 179, 2 2013-06-26 15:45 mmcblk0p2
brw------- root root 179, 3 2013-06-26 15:45 mmcblk0p3
brw------- root root 179, 4 2013-06-26 15:45 mmcblk0p4
brw------- root root 179, 16 2013-06-26 15:45 mmcblk1
brw------- root root 179, 17 2013-06-26 15:45 mmcblk1p1
drwxr-xr-x root root 2013-06-26 15:45 platform
brw------- root root 1, 0 2013-06-26 15:45 ram0
brw------- root root 1, 1 2013-06-26 15:45 ram1
brw------- root root 1, 10 2013-06-26 15:45 ram10
brw------- root root 1, 11 2013-06-26 15:45 ram11
brw------- root root 1, 12 2013-06-26 15:45 ram12
brw------- root root 1, 13 2013-06-26 15:45 ram13
brw------- root root 1, 14 2013-06-26 15:45 ram14
brw------- root root 1, 15 2013-06-26 15:45 ram15
brw------- root root 1, 2 2013-06-26 15:45 ram2
brw------- root root 1, 3 2013-06-26 15:45 ram3
brw------- root root 1, 4 2013-06-26 15:45 ram4
brw------- root root 1, 5 2013-06-26 15:45 ram5
brw------- root root 1, 6 2013-06-26 15:45 ram6
[email protected]:/ # ls -l /dev/block
brw------- root root 254, 0 2013-06-26 15:45 dm-0
brw------- root root 254, 1 2013-06-26 15:45 dm-1
brw------- root root 254, 10 2013-06-26 15:45 dm-10
brw------- root root 254, 11 2013-06-26 15:45 dm-11
brw------- root root 254, 12 2013-06-26 15:45 dm-12
brw------- root root 254, 13 2013-06-26 15:45 dm-13
brw------- root root 254, 14 2013-06-26 15:45 dm-14
brw------- root root 254, 15 2013-06-26 15:45 dm-15
brw------- root root 254, 16 2013-06-26 15:45 dm-16
brw------- root root 254, 17 2013-06-26 15:45 dm-17
brw------- root root 254, 18 2013-06-26 15:45 dm-18
brw------- root root 254, 19 2013-06-26 15:45 dm-19
brw------- root root 254, 2 2013-06-26 15:45 dm-2
brw------- root root 254, 20 2013-06-26 15:45 dm-20
brw------- root root 254, 21 2013-06-26 15:45 dm-21
brw------- root root 254, 22 2013-06-26 15:45 dm-22
brw------- root root 254, 23 2013-06-26 15:45 dm-23
brw------- root root 254, 24 2013-06-26 15:45 dm-24
brw------- root root 254, 25 2013-06-26 15:45 dm-25
brw------- root root 254, 26 2013-06-26 15:45 dm-26
brw------- root root 254, 27 2013-06-26 15:45 dm-27
brw------- root root 254, 28 2013-06-26 15:45 dm-28
brw------- root root 254, 29 2013-06-26 15:45 dm-29
brw------- root root 254, 3 2013-06-26 15:45 dm-3
brw------- root root 254, 30 2013-06-26 15:45 dm-30
brw------- root root 254, 31 2013-06-26 15:45 dm-31
brw------- root root 254, 32 2013-06-26 15:45 dm-32
brw------- root root 254, 34 2013-06-26 15:46 dm-34
brw------- root root 254, 35 2013-06-26 15:46 dm-35
brw------- root root 254, 36 2013-06-26 15:46 dm-36
brw------- root root 254, 37 2013-06-26 15:46 dm-37
brw------- root root 254, 38 2013-06-26 15:46 dm-38
brw------- root root 254, 39 2013-06-26 15:46 dm-39
brw------- root root 254, 4 2013-06-26 15:45 dm-4
brw------- root root 254, 40 2013-06-26 15:46 dm-40
brw------- root root 254, 41 2013-06-26 15:46 dm-41
brw------- root root 254, 42 2013-06-26 15:46 dm-42
brw------- root root 254, 43 2013-06-26 15:46 dm-43
brw------- root root 254, 44 2013-06-26 15:46 dm-44
brw------- root root 254, 45 2013-06-26 15:46 dm-45
brw------- root root 254, 46 2013-06-26 15:46 dm-46
brw------- root root 254, 47 2013-06-26 15:46 dm-47
brw------- root root 254, 48 2013-06-26 15:46 dm-48
brw------- root root 254, 49 2013-06-26 15:46 dm-49
brw------- root root 254, 5 2013-06-26 15:45 dm-5
brw------- root root 254, 6 2013-06-26 15:45 dm-6
brw------- root root 254, 7 2013-06-26 15:45 dm-7
brw------- root root 254, 8 2013-06-26 15:45 dm-8
brw------- root root 254, 9 2013-06-26 15:45 dm-9
brw------- root root 7, 0 2013-06-26 15:45 loop0
brw------- root root 7, 1 2013-06-26 15:45 loop1
brw-rw---- root root 7, 10 2013-06-26 15:45 loop10
brw-rw---- root root 7, 11 2013-06-26 15:45 loop11
brw-rw---- root root 7, 12 2013-06-26 15:45 loop12
brw-rw---- root root 7, 13 2013-06-26 15:45 loop13
brw-rw---- root root 7, 14 2013-06-26 15:45 loop14
brw-rw---- root root 7, 15 2013-06-26 15:45 loop15
brw-rw---- root root 7, 16 2013-06-26 15:45 loop16
brw-rw---- root root 7, 17 2013-06-26 15:45 loop17
brw-rw---- root root 7, 18 2013-06-26 15:45 loop18
brw-rw---- root root 7, 19 2013-06-26 15:45 loop19
brw------- root root 7, 2 2013-06-26 15:45 loop2
brw-rw---- root root 7, 20 2013-06-26 15:45 loop20
brw-rw---- root root 7, 21 2013-06-26 15:45 loop21
brw-rw---- root root 7, 22 2013-06-26 15:45 loop22
brw-rw---- root root 7, 23 2013-06-26 15:45 loop23
brw-rw---- root root 7, 24 2013-06-26 15:45 loop24
brw-rw---- root root 7, 25 2013-06-26 15:45 loop25
brw-rw---- root root 7, 26 2013-06-26 15:45 loop26
brw-rw---- root root 7, 27 2013-06-26 15:45 loop27
brw-rw---- root root 7, 28 2013-06-26 15:45 loop28
brw-rw---- root root 7, 29 2013-06-26 15:45 loop29
brw------- root root 7, 3 2013-06-26 15:45 loop3
brw-rw---- root root 7, 30 2013-06-26 15:45 loop30
brw-rw---- root root 7, 31 2013-06-26 15:45 loop31
brw-rw---- root root 7, 32 2013-06-26 15:45 loop32
brw-rw---- root root 7, 33 2013-06-26 15:45 loop33
brw-rw---- root root 7, 34 2013-06-26 15:46 loop34
brw-rw---- root root 7, 35 2013-06-26 15:46 loop35
brw-rw---- root root 7, 36 2013-06-26 15:46 loop36
brw-rw---- root root 7, 37 2013-06-26 15:46 loop37
brw-rw---- root root 7, 38 2013-06-26 15:46 loop38
brw-rw---- root root 7, 39 2013-06-26 15:46 loop39
brw------- root root 7, 4 2013-06-26 15:45 loop4
brw-rw---- root root 7, 40 2013-06-26 15:46 loop40
brw-rw---- root root 7, 41 2013-06-26 15:46 loop41
brw-rw---- root root 7, 42 2013-06-26 15:46 loop42
brw-rw---- root root 7, 43 2013-06-26 15:46 loop43
brw-rw---- root root 7, 44 2013-06-26 15:46 loop44
brw-rw---- root root 7, 45 2013-06-26 15:46 loop45
brw-rw---- root root 7, 46 2013-06-26 15:46 loop46
brw-rw---- root root 7, 47 2013-06-26 15:46 loop47
brw-rw---- root root 7, 48 2013-06-26 15:46 loop48
brw-rw---- root root 7, 49 2013-06-26 15:46 loop49
brw------- root root 7, 5 2013-06-26 15:45 loop5
brw------- root root 7, 6 2013-06-26 15:45 loop6
brw------- root root 7, 7 2013-06-26 15:45 loop7
brw-rw---- root root 7, 8 2013-06-26 15:45 loop8
brw-rw---- root root 7, 9 2013-06-26 15:45 loop9
brw------- root root 179, 0 2013-06-26 15:45 mmcblk0
brw------- root root 179, 1 2013-06-26 15:45 mmcblk0p1
brw------- root root 179, 2 2013-06-26 15:45 mmcblk0p2
brw------- root root 179, 3 2013-06-26 15:45 mmcblk0p3
brw------- root root 179, 4 2013-06-26 15:45 mmcblk0p4
brw------- root root 179, 16 2013-06-26 15:45 mmcblk1
brw------- root root 179, 17 2013-06-26 15:45 mmcblk1p1
drwxr-xr-x root root 2013-06-26 15:45 platform
brw------- root root 1, 0 2013-06-26 15:45 ram0
brw------- root root 1, 1 2013-06-26 15:45 ram1
brw------- root root 1, 10 2013-06-26 15:45 ram10
brw------- root root 1, 11 2013-06-26 15:45 ram11
brw------- root root 1, 12 2013-06-26 15:45 ram12
brw------- root root 1, 13 2013-06-26 15:45 ram13
brw------- root root 1, 14 2013-06-26 15:45 ram14
brw------- root root 1, 15 2013-06-26 15:45 ram15
brw------- root root 1, 2 2013-06-26 15:45 ram2
brw------- root root 1, 3 2013-06-26 15:45 ram3
brw------- root root 1, 4 2013-06-26 15:45 ram4
brw------- root root 1, 5 2013-06-26 15:45 ram5
brw------- root root 1, 6 2013-06-26 15:45 ram6
brw------- root root 1, 7 2013-06-26 15:45 ram7
brw------- root root 1, 8 2013-06-26 15:45 ram8
brw------- root root 1, 9 2013-06-26 15:45 ram9
drwxr-xr-x root root 2013-06-26 15:45 vold
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
255 heads, 63 sectors/track, 1915 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 219 1908 13568000 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 9 53 358400 83 Linux
/dev/block/mmcblk0p3 53 181 1024000 83 Linux
/dev/block/mmcblk0p4 181 219 307200 83 Linux
Partition table entries are not in disk order
Click to expand...
Click to collapse
Frontier said:
There is no mmcblk0boot0.
Click to expand...
Click to collapse
I have Hyundai T7s tablet and here is my partitions list:
[localhost /extsd]# ls -l /dev/block/m*
brw------- 1 0 0 179, 0 Jul 30 04:07 /dev/block/mmcblk0 <--- Internal sd card
brw------- 1 0 0 179, 8 Jul 30 04:07 /dev/block/mmcblk0boot0
brw------- 1 0 0 179, 16 Jul 30 04:07 /dev/block/mmcblk0boot1
brw------- 1 0 0 179, 1 Jul 30 04:07 /dev/block/mmcblk0p1 <-- Internal storage ----- mounted as /sdcard
brw------- 1 0 0 179, 2 Jul 30 04:07 /dev/block/mmcblk0p2 <-- System partition ----- mounted as /system
brw------- 1 0 0 179, 3 Jul 30 04:07 /dev/block/mmcblk0p3 <-- Data partition ----- mounted as /data
brw------- 1 0 0 179, 4 Jul 30 04:07 /dev/block/mmcblk0p4 <-- Cache partition ----- mounted as /cache
brw------- 1 0 0 179, 24 Jul 30 04:07 /dev/block/mmcblk1 <--- External sd card
brw------- 1 0 0 179, 25 Jul 30 04:07 /dev/block/mmcblk1p1 <--- Partition on the external sd card
mmcblk0 - represents a whole storage, therefore this is not a boot partition.
I also noticed that System partition starts not from the beginning of the card.There is 131071 sectors (65 534 kb) in the beginning of the card.
[localhost /extsd]# fdisk -u -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders, total 30535680 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 4251648 30404607 13076480 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 131072 1179647 524288 83 Linux
/dev/block/mmcblk0p3 1179648 3227647 1024000 83 Linux
/dev/block/mmcblk0p4 3227648 4251647 512000 83 Linux
Partition table entries are not in disk order
I´m very interesting on this thread, I bought a Voyo A15 with Exynos 5250 and partitions it´s same that T7s.
Hardly waiting for a cwm for iberry auxus core x4 exynos 4412 processor, we need devs support fot this..
Request to all devs to joins this thread.
Btw iberry auxus core x4 recently got jb 4.2.2....
Sent from my GT-P3100 using xda premium
iBerry auxus core x4 has the same hardware with Hyundai T10.
Regarding CWM for this tablet, you can try this.
waseem.gani said:
Hardly waiting for a cwm for iberry auxus core x4 exynos 4412 processor, we need devs support fot this..
Request to all devs to joins this thread.
Btw iberry auxus core x4 recently got jb 4.2.2....
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Thanks for your help, will try it and let you know.
The jb 4.2.2 provided by iberry is very unstable, so want to try custom rom, can you share some link for cuayom roms.
Sent from my GT-P3100 using xda premium
Tried your cwm.zip and I bricked my tablet.so I have sent it to iberry service center.even firmware upgrade didnt helped and it was not switching on.
Devs need your help please can any one build a working cwm for iberry auxus core x4.
Sent from my GT-P3100 using xda premium
Hi Guys,
I've an Amlogic MX based Tablet and played a little around with some Kernel and ROMs and now I have the problem that my Data-Partition (/dev/block/data) is gone.
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,size=410328k,nr_inodes=74092,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 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 /proc/bus/usb usbfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /storage/external_storage tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=775,gid=1000 0 0
/dev/block/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /factory yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/253:1 /storage/external_storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Code:
ls -l /dev/block/
brw------- root root 250, 28 2014-07-26 11:21 cache
brw------- root root 253, 0 2014-07-26 11:21 cardblksd
brw------- root root 253, 1 2014-07-26 11:21 cardblksd1
brw------- root root 250, 24 2014-07-26 11:21 factory
brw------- root root 7, 0 2014-07-26 11:21 loop0
brw------- root root 7, 1 2014-07-26 11:21 loop1
brw------- root root 7, 2 2014-07-26 11:21 loop2
brw------- root root 7, 3 2014-07-26 11:21 loop3
brw------- root root 7, 4 2014-07-26 11:21 loop4
brw------- root root 7, 5 2014-07-26 11:21 loop5
brw------- root root 7, 6 2014-07-26 11:21 loop6
brw------- root root 7, 7 2014-07-26 11:21 loop7
brw------- root root 31, 0 2014-07-26 11:21 mtdblock0
brw------- root root 31, 1 2014-07-26 11:21 mtdblock1
brw------- root root 31, 2 2014-07-26 11:21 mtdblock2
brw------- root root 31, 3 2014-07-26 11:21 mtdblock3
brw------- root root 31, 4 2014-07-26 11:21 mtdblock4
brw------- root root 31, 5 2014-07-26 11:21 mtdblock5
brw------- root root 31, 6 2014-07-26 11:21 mtdblock6
brw------- root root 31, 7 2014-07-26 11:21 mtdblock7
brw------- root root 31, 8 2014-07-26 11:21 mtdblock8
drwxr-xr-x root root 2014-07-26 11:21 platform
brw------- root root 1, 0 2014-07-26 11:21 ram0
brw------- root root 1, 1 2014-07-26 11:21 ram1
brw------- root root 1, 10 2014-07-26 11:21 ram10
brw------- root root 1, 11 2014-07-26 11:21 ram11
brw------- root root 1, 12 2014-07-26 11:21 ram12
brw------- root root 1, 13 2014-07-26 11:21 ram13
brw------- root root 1, 14 2014-07-26 11:21 ram14
brw------- root root 1, 15 2014-07-26 11:21 ram15
brw------- root root 1, 2 2014-07-26 11:21 ram2
brw------- root root 1, 3 2014-07-26 11:21 ram3
brw------- root root 1, 4 2014-07-26 11:21 ram4
brw------- root root 1, 5 2014-07-26 11:21 ram5
brw------- root root 1, 6 2014-07-26 11:21 ram6
brw------- root root 1, 7 2014-07-26 11:21 ram7
brw------- root root 1, 8 2014-07-26 11:21 ram8
brw------- root root 1, 9 2014-07-26 11:21 ram9
brw------- root root 250, 20 2014-07-26 11:21 system
drwx------ root root 2014-07-26 11:21 vold
If I flash an older Stock-ROM with UBIFS the Data-Partition is there, but not as Ext4-Partition.
Code:
ubi0_0 /system ubifs rw,relatime 0 0
ubi1_0 /data ubifs rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
After flashing back to a newer Stock-Rom with Android 4.2.2 (EXT4-ROM), I have the same issue as above,
Recovery stops with following output:
Code:
Finding update package...
Openning update package...
Verifying update package...
Installing update...
Formatting /cache...
Formatting /data...
Formatting /cache...
Data wipe failed.
Formatting /cache...
Cache wipe failed.
CWM is a little more verbose with this:
Code:
E:format_volume: make_extf4fs failed on /dev/block/data
Anyone a Idea how to recover Ext4-Data-Partition?
Thanks.