Related
Hi,
I'm trying to figure out the format of this boot animation file that is used in those cheap android tablets (Eken M00X etc)
Boot animation is writen to flash during update via uboot scriptcmdfile:
fatload mmc 0 0 script/logo.data
nand write 0 b80000 $(filesize)
textout -1 -1 "Upgraded logo successful!" ff00
and it's called later via bootcmd parameter:
setenv bootcmd 'nand read 7f80000 b80000 80000;nand read 0 0 300000;bootm 0'
the trouble is that I can't figure out what kind of file this is, I dont think it can be flash animation and it's (as far as I can say) not in the same format that i.e nexus boot animation is.
Can some one please guide how to root Iball slide tablet. Iball Tab information is given below
OS
Browser UserAgent : Mozilla/5.0 (Linux; U; Android 2.3; en-gb; iBall Slide i7011 Build/GINGERBREAD) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
Android ID : acbc4627cc4a9253
Uptime : 0 days, 1 hours, 53 minutes, 26 seconds
Uptime (without sleeps) : 0 days, 1 hours, 53 minutes, 26 seconds
BuildInfos
Android version : 2.3
Release Codename : REL
API LEVEL : 9
CPU ABI : armeabi-v7a
Manufacturer : unknown
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : smdkv210
Radio : unknown
Board : smdkv210
Brand : generic
Device : smdkv210
Display : MID Serials 2.3 GINGERBREAD 20110830.164011
Fingerprint : generic/full_smdkv210/smdkv210:2.3/GINGERBREAD/20110830.164011:eng/test-keys
Host : urbetter-linux01
ID : GINGERBREAD
Model : iBall Slide i7011
Product : full_smdkv210
Tags : test-keys
Type : eng
User : raymanfeng
Battery
Not charging...
Level : 50 %
Technology : Li-ion
Temperature : 20.0 °C (68.0°F)
Voltage : 7626 mV
Memory
Download Cache Max: 100MB/ Free: 86.45MB
data Max: 488MB/ Free: 367MB
External storage Max: 6.55GB/ Free: 6.26GB
Total RAM: 361MB
Free RAM: 159MB
Threshold RAM: 24.00MB
Low Memory Killer Levels
FOREGROUND_APP:__ 8.00MB
VISIBLE_APP:_________ 12.00MB
SECONDARY_SERVER: 16.00MB
HIDDEN_APP:________ 24.00MB
CONTENT_PROVIDER: 28.00MB
EMPTY_APP:__________ 32.00MB
Telephony
Data Activity: DATA_ACTIVITY_NONE
Data State: DATA_DISCONNECTED
IMEI(or MEID): null
IMEI/SoftVer: null
MSISDN: null
Registered MCC:
Registered MCC MNC:
Registered Operator Name:
Network Type: NETWORK_TYPE_UNKNOWN
Phone Type: PHONE_TYPE_GSM
SIM Country Code: us
SIM MCC MNC: 310004
SIM Operator Name: Verizon
SIM Serial Number: null
SIM State: SIM_STATE_UNKNOWN
Subscriber ID(IMSI): null
VoiceMail number:
Roaming: false
No Cell detected
Networks
Background Data Usage: true
type mobile[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_mms[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type mobile_supl[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type mobile_hipri[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type Network3gDataStateTracker[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type NetworkEthDataStateTracker[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
Wifi
State: WIFI_STATE_ENABLED
CPU
Processor ARMv7 Processor rev 2 (v7l)
BogoMIPS 998.15
Features swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer 0x41
CPU architecture 7
CPU variant 0x2
CPU part 0xc08
CPU revision 2
Hardware SMDKV210
Revision 0000
Serial 0000000000000000
Frequency Stats (time):
Screen
Resolution: 800 x 480
Refresh Rate: 68.0
X factor for DIP: 1.25
Density: 200 dpi
Pixel per inch X: 144.0 dpi Y: 144.0 dpi
OpenGL
As retreiving opengl infos can crash some device, it is not enabled by default. If you wish to, go in settings menu.
Sensors
mma7660-accel: 0.2 mA by urbetter
Gravity Sensor: 0.2 mA by Google Inc.
Linear Acceleration Sensor: 0.2 mA by Google Inc.
Rotation Vector Sensor: 0.2 mA by Google Inc.
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: mounted
External Storage Directory: /mnt/sdcard
Medias Directories
Alarms: /mnt/sdcard/Alarms
DCIM: /mnt/sdcard/DCIM
Downloads: /mnt/sdcard/Download
Movies: /mnt/sdcard/Movies
Music: /mnt/sdcard/Music
Notifications: /mnt/sdcard/Notifications
Pictures: /mnt/sdcard/Pictures
Podcasts: /mnt/sdcard/Podcasts
Ringtones: /mnt/sdcard/Ringtones
Features
android.hardware.location.network
android.hardware.wifi
android.hardware.nfc
com.google.android.feature.GOOGLE_BUILD
android.hardware.location
android.hardware.sensor.gyroscope
android.hardware.bluetooth
android.hardware.touchscreen.multitouch.distinct
android.hardware.microphone
android.hardware.sensor.light
android.software.live_wallpaper
android.hardware.telephony
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.sensor.barometer
android.software.sip
android.hardware.touchscreen.multitouch
android.hardware.sensor.compass
android.hardware.camera
android.software.sip.voip
android.hardware.sensor.proximity
android.hardware.location.gps
android.hardware.telephony.gsm
android.hardware.telephony.cdma
android.hardware.camera.front
android.hardware.sensor.accelerometer
android.hardware.touchscreen
glEsVers=2.0
JavaProperties
java.vendor.
java.class.path: .
java.class.version: 46.0
os.version: 2.6.35.7
java.vendor: The Android Project
user.dir: /
user.timezone: null
path.separator: :
os.name: Linux
os.arch: armv7l
line.separator:
file.separator: /
user.name:
java.version: 0
java.home: /system
Mount points
MountPoint
Name Type Options
- /
rootfs rootfs rw
- /
ubi0:rootfs ubifs rw,relatime
- /dev
tmpfs tmpfs rw,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /proc/bus/usb
none usbfs rw,relatime,devmode=666
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /data
/dev/block/mmcblk0p3 ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
- /cache
/dev/block/mmcblk0p2 ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
- /sys/kernel/debug
/sys/kernel/debug debugfs rw,relatime
- /mnt/sdcard
/dev/block/vold/179:1 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
- /mnt/secure/asec
/dev/block/vold/179:1 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
- /mnt/sdcard/.android_secure
tmpfs tmpfs ro,relatime,size=0k,mode=000
- /mnt/extsd
/dev/block/vold/179:8 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
- /mnt/asec/com.UCMobile.intl-1
/dev/block/dm-0 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.skype.raider-1
/dev/block/dm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.opera.mini.android-1
/dev/block/dm-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.eamobile.nfsshift_na_wf-1
/dev/block/dm-3 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.guidedways.iQuranPro-1
/dev/block/dm-4 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.dolphin.browser-1
/dev/block/dm-5 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/kz.mek.DialerOne-1
/dev/block/dm-6 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.adobe.reader-1
/dev/block/dm-7 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.google.earth-1
/dev/block/dm-8 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.electricsheep.asi-1
/dev/block/dm-9 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.joeykrim.rootcheck-1
/dev/block/dm-10 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
I tried ginger break but of no use superuser is install but not working, Here is the feedback from root Checker
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /system/busybox/bin /system/busybox/sbin /system/busybox/usr/bin /system/busybox/usr/sbin /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
-rwsr-sr-x 1 2000 2000 22228 Feb 28 2008 /system/bin/su
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
ls: /sbin/su: No such file or directory
Alternate su type binary location: ls -l /system/xbin/sudo:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your iBall Slide i7011 device by Root Checker version 3.9 from joeykrim in the Android Market
Please guide
Thanks in advance
any help from anyone regarding rooting iball slide i7011 android 2.3 tab. I have tried gingerbreak and also tried superoneclick as per guide but of no use.
both of them reports that the tab is rooted but when i try su command superuser wont give permission. its a mess up right now. and when i try to remove superuser its not done saying its a system app. and when i go to /system/apps/superuser its mounted as r/o.
can anyone help this ?????
I have tried almost all process from single click app to rooting via adb, bt failed. So I have changed its firmware, which includes a custom ROM...So using my iball slide with much more functions..
Bt there is one problem..The camera is not working..may be the device driver is not working, I am trying to develop this issue, and will be back when I will debug that..
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
ffarhan.s said:
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
first of all a big thanks to ffarhan.s.... thanks bro ur guide was fantastic and worked like charm. i rooted my tab without any glitch. thanks a lot buddy.
but something more to say for the newbies,
1. download gingerbreak.apk and save it in ur tab's sd card(which means internal 8gb memory)
2. ADB composite device may not show up in device manager so dont worry. but android adb interface must be shown in the path computer > Manage>device manager>android phones>android adb interface (its very necessary)
3. .. as ffarhan wrote > Then type [space cd space platform-tools] , without bracket.. its actually the path of your android sdk folder. assuming u have downloaded the sdk folder under c:\
so the path will be c:\android-sdk\platform-tools
then type adb devices press enter. the result may show like this :
List of devices attached
MID_serials devices
.... below this blank.dont worry its fine.
the main part is point 16 - 22. these should work as ffarhan wrote otherwise repeat the process from start.
anywyz, once again thanks ffarhan.s for the entire process. take care bro.
have a nice day
I have done this, bt for my case it was a temporary root..I think it has to be made permanent...
will "root explorer" go ?my i7011 is ok(Root Explorer 2.17).
it can mount / or other partitions as ro or rw?
btw, can u mail me the file "/system/bin/wpa_supplicant" , thanks a lot, [email protected]
ffarhan.s said:
8.Connect tab to your computer with OTG, wait until driver are installing
9.To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
Click to expand...
Click to collapse
the device manager on my computer does show any ADB interface or android Composite ADB interface. What am i doing wrong ?
New problem !!
ffarhan.s said:
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
on performing step 16, the $ sign pops up immediately and for the remaining steps i keep getting 'cannot find'. plz help me out.:fingers-crossed:
vivdutta said:
on performing step 16, the $ sign pops up immediately and for the remaining steps i keep getting 'cannot find'. plz help me out.:fingers-crossed:
Click to expand...
Click to collapse
That's not a bring problem . And the correction in 21st step that it is rm system not rm/system. Hope u get it
ffarhan.s said:
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
well i have a few problems...i have ADB interface...that means the the drivers are installed right?but when i open gingerbreak..it does the process...but my tab shuts off...i switch it on and superuser is also there...then i connect with OTG and i guess my drivers are installed...then i dont understand what you mean by Type CD.. until you reach to C:\...what exactly am i supposed to do??can u please post screenshots...or even better...if it is not too much trouble a video on how u did it!! i really want to root my tab...but i just cant get through to it!! :|
how to root iball slide with jelly bean (6309r)
can anybody please help me and tell how to root iball slide with jelly bean (6309r):crying:
This Procedure Works for every Iball Slide Tablets
http://forum.xda-developers.com/showthread.php?p=43037172#post43037172
Device: Arnova Gbook (ereader)
OS: Android 4.0.3
Kernel version: Linux 3.0.8
I was using my tablet at an airport and everything was fine before I shutoff my phone for the flight to take off. I turned it back on once the plane reached cruising altitude. I got an indicator that my SD card was damaged, which makes no absolutely no sense. also, my apps disappeared...
Problems are:
-When I connect to PC, tapping "Turn on USB storage" nothing happens, only the lile circle indicates that it is doing something but it does nothing...
-Settings>Storage: "Unfortunately, Settings has stopped."
next to the clock it says "Damaged SD card. SD card damaged, you may have to reformat it." There is not SD card in the slot, but it still says this.
-Cannot push an SD card into the slot: It doesnt stay there even if i push it to the maximum inside. No "click sound" either.
-Cant do anything only using the internet, internal storage is not reachable in any way thus i cant install newer rom too.
Did a factory reset (Settings>factory reset) but couldnt help, still the same... I beg you guyz for your help!
Anyone?
up
...having the Same Problem
dyingsoulwow said:
up
Click to expand...
Click to collapse
So it looks like I'm having the same problem with the same gear. I tried several cures to no avail.
But First the Tech Specs of my Arnova GBook:
Manufactor: VIMICRO
Model: ANGB
CPU: ARMv 7 rev 2 (v7l)
Memory: RAM 337, ROM 0.91, SDCard 0 MB (at the Moment more to that later)
Android: 4.0.3
BuildID: generic_vortex-userdebug 4.0.3 IML74K 1.0 test-keys
Linux Version: 3.0.8-vimicro([email protected]) (gcc Version 4.4.3)
I copied some files to the mounted exSDCard (4gb noname) when my tablet suddenly died and the only way to reanimate it was by factory resetting it.
The Problem istself seems to relate to the inability to mount a Nonformated SDCard that i can not format because it is not proberly mounted.
I have no clue how to root the tablet. I tried a set of instruction from a french website, but since i don't speak french i'm not sure if the google translator gave me the right directions.
I tried to mount it the SDCard via terminal. Format it connecting the gbook to an ubuntu box and a lot of system tools available via googles play store.
USB connection shows the drives but I'm not abel to mount or list the contents of it. In general the System is booting up and i am able to install apps from Google Play. Since i can't mount any external devices i am not abel to transfer files via other means because the gbook wants to copy them to the interna SDCard (wich is not available ).
I am looking for any possible solution. If there is an alternate Frimware i will try it.
Thanks in advance for any offered Help!
Lanman99
Still trying...
Any solution i found using Google, Bing and DuckDuckGo seems to require Root Access. Has somebody successfully rooted an Arnova GBook?
Or is there really no possibel solution for a dummy user to fix this problem. It seems to boil down that i cannot mount device mmcblk0 to sdcard because "access denied".
Did anybody face a similar problem and fixed it without root?
Tried several SDCard tools to no avail...
ES File Explorer is showing me that everthing i need is there but still, every try to mount the internal storage is leading to permission denied. I'm stating to love Android
Well if there is no root, is it possible to write a shell script to revive the internal SDCard and run that with elevated rights?
ES File manager is showing the directory entry with 0 MB. Since i am a novice in Android Systems i am just not sure if that means anything.
Maybe i'm wasting my time on a piece of chinaware but this nut i still too tempting to ignore. It's just that with my limited Linux knowlegde it seems that mounting a device and formating it afterward sounds not to troublsome or am i completely lost. After asking Google, bing and some other SEs it is not that uncommon but none of the cures i found worked for my GBook.
What am i missing?
Stil no answer from Arnova on my request for a stockrom Download. Somebody got an Idea where elsee i could find a ROM image for an Arnove GBook or does anybody know if there is an alternative Firmware available?
I was able to connect to my Device via ADB
mount is delivering the following:
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)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
ubi0_0 on /system type ubifs (ro,noatime,no_chk_data_crc,compr=lzo)
ubi1_0 on /data type ubifs (rw,nosuid,nodev,noatime,bulk_read,no_chk_data_crc,compr=lzo)
ubi2_0 on /cache type ubifs (rw,nosuid,nodev,noatime,bulk_read,no_chk_data_crc,compr=lzo)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
The list under /dev/block/vold has three entries:
179:0 179:1 and 7:0
Cat /proc/partitions delivers:
31 0 10240 mtdblock0
31 1 12288 mtdblock1
31 2 120832 mtdblock2
31 3 45056 mtdblock3
31 4 524288 mtdblock4
31 5 1048576 mtdblock5
31 6 262144 mtdblock6
31 7 2169856 mtdblock7
179 0 3909632 mmcblk0
179 1 3905536 mmcblk0p1
Please I am a complete Android Noob. Is there somebody able to guide me to a Point where i can start to patch all this together.
I am able to find pieces here, but i'm not getting the broad picture.
Next try...
using Root Many by Bin4ry http://forum.xda-developers.com/showthread.php?t=1886460 to get into my device I got following results:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.04.2013) v29 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Above file not found warning ARE NOT ERRORS, it is intended to be this way!
Normal Mode enabled!
.
Pushing busybox....
2207 KB/s (1085140 bytes in 0.480s)
Pushing su binary ....
2185 KB/s (380532 bytes in 0.170s)
Pushing Superuser app
2309 KB/s (1468798 bytes in 0.621s)
Making busybox runable ...
.
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
After reboot the gbook is throwing "unfortunately UI has stopped" and "unfortunately settings has stopped". Nothing works until i factory reset it again (at least something i am growing really good at) and I'm back to square one.
Other means of editing files within the system via ADB are only leading to access denied or system is in read only mode.
Any other ideas?
By using Archtablet.com's method: "http://www.arctablet.com/blog/forum/firmware-development/dumping-firmware-on-arnova-g2-arnova-g3-and-other-rockchip-based-tablets/" i tried to get an Firmwareimage. They tried to Help me out but again disaster struck. Ubuntu 13.04 with usblib installed failed to even recognize the GBook. Trying it with Windows and adb i need (what a surprise) root rights.
So next question is: Is there any general way to read out a tablet firmware without rooting or is it always up to the vendor to just screw things to their Liking ?
I know i should quit this beast, but stubborn as ever i keep banging my head against the wall .
Lanman99
Hello, xda-developers community! This is my first post here, and and I come to ask for help.
Yesterday, I ****ed out my tablet, I did it trying to install ClockworkMod Recovery from this thread: Clic here. Ok, I entered to my tablet's stock recovery, installed update from zip, selected cwm6028-a13-10part-v2.zip, rebooted my tablet, and here comes the problem. CWM stuck in a bootloop, I can't boot to Android, just CWM, and CWM can't mount /cache, /system, /data, etc... just the /sdcard. I have tried reinstalling the ROM with Livesuit, and Livesuit throws me a error: Upgrade fails : 0x162[random chars here], no matter what rom try putting on, always throws me that error. Ok, next solution: Change the recovery.img via fastbook, ha! my tablet can't enter to fastboot mode. Wipe data/cache: I can't, because /cache is not mounted. Factory reset: same. After hours of research, I figured my tablet partitions were screwed, why? Here is the answer:
Code:
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 nandf ram0
loop1 loop3 loop5 loop7 mmcblk0p1 platform ram1
/dev/block #
There must have more partitions, like nanda, nandb, nandc, nandd, nande, nandf, nandg, nandh, nandi and nandj. I tried every solution, but all fails. Here's some info from the tablet connected to adb (in Recovery mode):
Code:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
~ #
Code:
~ # mount /system
mount /system
mount: mounting /dev/block/nandd on /system failed: No such file or directory
~ #
Code:
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 181028 52 180976 0% /dev
tmpfs 181028 4 181024 0% /tmp
~ #
Code:
~ # cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 59.63
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : sun5i
Revision : a13b
Serial : [Hidden serial, i don't know if may have a problem with that, but hidden anyway.]
~ #
Video:
Link: http://www.youtube.com/watch?v=BjguNxLh-rQ
Btw, my bro has another tablet like this, but fully functional, no CWM, only rooted.
PDT: When installing the CWM, the tablet was still with the stock ROM.
PDT2: I can only access the terminal via ADB.
PDT3: Sorry for my bad English, my native lang is Spanish.
Thanks for all the help.
Bump :/
carl0sra1n said:
Bump :/
Click to expand...
Click to collapse
Bump
carl0sra1n said:
Bump
Click to expand...
Click to collapse
Bump
carl0sra1n said:
Bump
Click to expand...
Click to collapse
Bump.
exact same problem for me too. Please help. Here is my thread,
http://forum.xda-developers.com/showthread.php?p=45728817#post45728817
me too!
Sounds exactly like what I did!
Except that I have nandf, but as a file not a partition.
I have tried to recreate the partitions with fdisk, but it fails to write the partition table at the end. next reboot i get the same thing. Surely it must be possible to repartition the device, but this is taking me beyond the limits of my linux knowledge.
So annoying because I have each of the partitions backed up on my PC as an image file.
Have the exact same problem.
Anyone found a solution ?
ShironLive said:
Have the exact same problem.
Anyone found a solution ?
Click to expand...
Click to collapse
Bump
here's how i got out that mess.......
ShironLive said:
Bump
Click to expand...
Click to collapse
first of all i've been searching for the solution for 2 weeks now,
-get livesuit v1.11 and faaastjb v2 or v2.5 and flash ur android device :
-after ur done please tell me the progress so we can proceed with geting to fassboot mode
and flashing custom recovery,img via fastboot mode
Livesuit cant detect
atmolight said:
first of all i've been searching for the solution for 2 weeks now,
-get livesuit v1.11 and faaastjb v2 or v2.5 and flash ur android device :
-after ur done please tell me the progress so we can proceed with geting to fassboot mode
and flashing custom recovery,img via fastboot mode
Click to expand...
Click to collapse
Live suit cant detect my a13....says that NO DEVICE NEEDS UPGRADE
The only way that i can think of to solve this problem is to have someone with an ALLWINNER A13 Tablet which is in stock rom and nothing has been changed could make a back up of his or her tab and upload it here for us to recover in our restore option in the cwm recovery boot loop....
same problem have you found solution??
nvenezuela said:
Live suit cant detect my a13....says that NO DEVICE NEEDS UPGRADE
The only way that i can think of to solve this problem is to have someone with an ALLWINNER A13 Tablet which is in stock rom and nothing has been changed could make a back up of his or her tab and upload it here for us to recover in our restore option in the cwm recovery boot loop....
Click to expand...
Click to collapse
same problem have you fix it ?
same problem too
Anyone have a stock rom ?
thanks
I need help to root my Aligator S5065 Duo phone. It ha Andoid 7.0 and the chipset is Mediatek MT6580.
Here is some info from the phone:
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : XXX
IMEI2 : XXX
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : 010901MT000000000000003891_155648
The idea was:
1) make a full backup using MTK Droid Tool
2) flash TWRP using SP Flash Tool
3) boot TWRP and install Magisk
Problems:
1) MTK Droid Tool v2.5.3. doesn't support this chipset and I didn't found a newer version - so no full backup
I've tried to download a stock ROM or a full backup.
I have found MT6580__ALIGATOR__ALIGATOR_S5065__alps-mp-n0.mp2-V1_droi6580.weg.n__Android_7.0.ispff but it seems to need Infinity CM2 Dongle for flashing, which I don't own.
I have also found ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.02_OS_1.1_20170927.zip which seems to be usable but not exactly the same as I have in my phone, at least it contains a scatter file. With the help of this scatter file I have I've read back my phone but the read imgs are considerably bigger, than the original ones in the zip - that doesn't seem right?
2) I have downloaded TWRP_3.2.3-0_20180803_UNOFFICIAL_MT6580_N.zip which should be a TWRP recovery for my chipset and the same kernel version, so I hoped it could work. But when trying to flash it with SP Flash Tool I get "PMT changed for the ROM" error message. The suggested solution for this error seem to be very risky (formating the phone, atc.), so I didn't dare to try ...
Now I'm stuck and I don't know how to proceed.
Any help would be really appreciated
Some progress:
I got a custom TWRP recovery image from Matty1993 <- thank you very much
I flashed it using adb and fastboot:
adb devices - successfully listed my device
adb reboot bootloader
fastboot flash recovery c:\adb\recovery.img - got this error message: "FAILED (remote: 'not allowedin locked state')"
Locked bootloader, unlocking ...
fastboot flashing unlock
- (bootloader) Start unlock flow
- OKAY [ 18.800s]
- Finished. Total time: 18.816s
Flashing the recovery.img
fastboot flash recovery c:\adb\recovery.img
Sending 'recovery' (10226 KB) OKAY [ 0.359s]
Writing 'recovery' OKAY [ 0.640s]
Finished. Total time: 1.030s
Success
fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
fastboot erase cache (I don't know if it was a good idea but it was in the tutorial, I was following)
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.109s]
Finished. Total time: 0.125s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.016s
Now when booting the phone complains:
Orange state
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
In 5 second it starts to boot but it stays forever on the "POWERED BY android" logo
I can boot to TWRP recovery (also fastboot), so I did and flashed magisk (because the main goal was to root my phone) and selected to delete cache/dalvik.
I'm not able to switch off the phone, it reboots. I had tu pull the battery (luckily it's removable).
The phone info changed
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : unknown
IMEI2 : unknown
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : unknown
The IMEIs and Bar code are now "uknown".
What did I wrong and what to do, to fix it?
forget MTK Droid Tool it is outdated and does not support scatter for devices > 4 GB. you can use SP Flash Tool for full ROM dump. First thing you should do is backup your nvram partition, hopefully it is not too late...
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek
If you already have backup of stock boot.img:
- copy file to /external_sd/TWRP/BACKUPS folder
- rename it to boot.emmc.win
- create a backup of current boot (just in case)
- restore renamed stock boot.emmc.win from TWRP
regarding boot stuck:
- Format Data and Wipe Cache from TWRP, reboot recovery, wipe again (Wipe -> Format Data -> type yes)
- reboot TWRP, check if /system /data and /cache is mounted/mountable (you should see folders or files inside)
- reboot system and wait 5 minutes, first boot may take a while because the data partition is forced encrypt
- if android is completely booted, check IMEI
Now, if your device is in good condition, reboot recovery and make a full TWRP backup.
Thank you very much for your help.
I did a dump before, using the SP Flash Tool and the scatter from the downloaded ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.0 2_OS_1.1_20170927.zip file.
So I have a sort of a "backup"
Now I'm going to read and I'll report back how it went.
blakegriplingph said:
NVRAM data must have been wiped off somehow, as that's one reason as to why your serial numbers have gone kaput.
Click to expand...
Click to collapse
If this is the case, you can "download" (=flash) your backup files from SP Flash Tool. In scatter file change entries to "is_download: true". Open the edited scatter file with SP Flash Tool. Make sure you uncheck all checkboxes, except nvram, nvdata (and cache, if you still have problems with this partition). Double click on file name and select the file for each partition. Make sure EMMC_USER is selected. The file sizes must fit partition size. Do NEVER flash PRELOADER! Press start, then connect phone, then insert battery.
nvram.bin 5120 KiB (0x00500000)
nvdata.bin 32768 KiB (0x02000000)
cache.img 409600 KiB (0x19000000)
If done, hold Volume Up key while unplug + plug in USB cable, this will boot into recovery. Wipe Cache and Data
My sizes of the backup files:
nvram.bin 5 242 880 seems OK
nvdata.bin 33 554 432 seems OK
cache.img 419 430 400 bigger
Is there a way I can check the integrity of them before flashing?
And what when I get the "PMT changed for the ROM" error message?
I've attached the used scatter file
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Matty1993 said:
All good mate yeah orange state is because you unlocked bootloader and didnt factory reset [...]
If you still get dramas with orange state let me know ill manually patch the dm-verity out of your boot.img for you
Click to expand...
Click to collapse
Orange state just mean unlocked bootloader, you can't get rid of. Do not lock the bootloader again, just leave it orange state is fine...
I thought so and it doesn't really bother me
Matty1993 said:
Your device comes with out of the box encryption in your boot.img fstab your system path will be /dev/block/platform/mtk-msdc/******/msdc/by-name/system /system ext4 ro wait, "verify"
Click to expand...
Click to collapse
Zdendav said:
I did all the steps:
- wipe, format
- factory reset
hangs on the "POWERED BY android" logo, when trying to boot
- flashed boot.img in fastboot
- reboot
I was not fast enough to go onto TWRP, it tried to boot, hangs on the "POWERED BY android" logo
-reboot into TWRP
- wipe, format
- factory reset
still hangs on the "POWERED BY android" logo, when trying to boot
I can borrow exactly the same phone from a relative (fully working) - maybe I should do a full backup of it, then I'll have "clean" images of boot, recovery etc.
Meanwhile I did another full backup and this time I used WwR MTK v2.30 to create a correct scatter.
I attach both scatter files.
Click to expand...
Click to collapse
as @Matty1993 already figured out, your phone seems fine, just dm-verity prevents to boot because of recovery checksum mismatch. You have to disable dm-verity.
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
aIecxs said:
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Click to expand...
Click to collapse
I did try and I got the "PMT changed" even when I selected all partitons except preloader ..
I did borrow exactly the same phone from a relative and created a full backup and from it a proper scatter file. I compared both scatter files and there are differences (as expected)
I attach both scatter files
I don't know how to proceed.
1) Lock the bootloader?
2) Flash parts from the borrowed phone? Which parts?
PS I have also a backup of userdata taken in factory mode.
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
aIecxs said:
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
Click to expand...
Click to collapse
Done. Did it all in one go (without any reboot), then powered off.
Log is attached
aIecxs said:
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
Click to expand...
Click to collapse
Sorry I missed your post until I posted mine ...
I'll keep all backups until it's sorted out.
And thank you very much aIecxs and Matty1993 for all your help
thanks for the log. seems there is something wrong, maybe with TWRP or maybe with phone.
Code:
E:Primary block device '/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata' for mount point '/data' is not present!
Failed to mount '/cache' (Invalid argument)
Error installing zip file '/external_sd/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip'
Flash stock boot.img and stock recovery.img from fastboot. reboot into stock recovery. Wipe Data + Cache. reboot to bootloader. boot into TWRP from fastboot. copy log to sdcard and upload again. reboot your phone and wait 5 minutes.
I flashed the stock recovery and boot in fastboot in one go.
Then rebooted to recovery but there is only "Supported API: 3" in the lower left corner of the display and that's all.
What to do next?
Edit: It's even worse, I'm not able to enter fastboot, recovery etc., the phone doesn't react to the volume button and always show the orange message a boot to the Supported API: 3 screen.
This indicates something is wrong with cache partition. Usually a normal system boot from stock boot.img will fix this. If you can't enter fastboot mode, flash recovery from SP Flash Tool. Try this version it has changed fstab. This should fix the /data mount. Then you should be able to enter fastboot again.
Code:
[strike]/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata[/strike]
/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/metadata
Regarding /cache try following from fastboot:
Code:
fastboot format:ext4 cache
after this wipe cache again from stock recovery (you can boot stock recovery from fastboot without flashing it). if cache still not mounted in TWRP, your only choice left is flash backup of cache partition from your friends phone from SP Flash Tool
edit: attachment deleted
Flashed your recovery, now it always boots into twrp, volume buttons still seem to not work, I'm still not able to enter fastboot.
Edit: I was able to enter fastboot by "adb reboot bootloader" when in TWRP, strangely "adb reboot fastboot" booted into TWRP.
I formatted the cache, rebooted into stock recovery, formatted the cache again.
Rebooted into TWRP, in file manager the cache is empty, in the mount menu I'm not able to tick any of the listed partitions to mount it ...
I'm not able to post the new log, it copies it to /data/media but in the file manager the location is empty ...
i have added some mount points, please download and flash again. you can copy recovery.log from adb
Code:
adb pull /tmp/recovery.log C:\adb\recovery.log
please post output of df and mount
Code:
adb shell
mount
busybox df -aT
/ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/ # busybox df -aT
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 463204 44 463160 0% /dev
devpts devpts 0 0 0 0% /dev/pts
proc proc 0 0 0 0% /proc
sysfs sysfs 0 0 0 0% /sys
selinuxfs selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs tmpfs 463204 32 463172 0% /tmp
adb functionfs 0 0 0 0% /dev/usb-ffs/adb