Archos79neon
De JoN@an
Révision de 14 mars 2016 à 01:57 par Jonathan (discussion | contributions)
Architecture
- RK3188T
- RAM 1GB
- Flash 8GB
- WiFi 2.4GHz
- Android 4.2.2 (20140212)
Root
Success
- attempt 1: adb fail (both adb shell (id=shell not root) and adb root)
- attempt 2: apply superuser.zip as update.zip fail (not recongnized as an update)
- attempt 3: dump rom/modify/reflash (WIP) never done
- attempt 4: Try TPSparky method #fail: unable to access /data (/data rwxrwx--x system system ... so no read nor right access to do the trick)
- attempt 5: Use kingo root from windows (apk didn't work) [1] But i wonder how it work?!
Recovery
Start recovery mode manually: ?
adb reboot recovery ;)
recovery functions: apply update.zip reboot/wipe
CWM recovery
- fail
flash CWM recovry as update.zip #fail
Use flash tool #fail (i was at least able to flash my backup)
Flash tool
Download mode: Power & vol +
RK batch tool 1.7 : working
ROM_Flash_Tool_21 :working => usefull to dump NAND
adb
windows 7: working (drivers?!)
adb shell => shell not root
adb root => adbd cannot run as root in production builds
Dumping NAND
source: Freaktab
parameter file (NAND split)
FIRMWARE_VER:1.0.17 MACHINE_MODEL:Archos 79 Neon MACHINE_ID:007 MANUFACTURER:RK30SDK MAGIC: 0x5041524B ATAG: 0x60000800 MACHINE: 3066 CHECK_MASK: 0x80 KERNEL_IMG: 0x60408000 #RECOVER_KEY: 1,1,0,20,0 CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand: 0x00002000@0x00002000(misc), 0x00004000@0x00004000(kernel), 0x00008000@0x00008000(boot), 0x00010000@0x00010000(recovery), 0x00020000@0x00020000(backup), 0x00040000@0x00040000(cache), 0x00002000@0x00080000(kpanic), 0x0017fd00@0x00082000(system), -@0x00201d00(userdata)
Sucess full backup made ;) (tested recovery and working)