Originally Posted by Baracuda86
I have an Alcatel OT 918 (not N/D or anything else) running under v 2.3.6.
I tried the easy solutions (SuperOneClick & UnlockRoot) but as expected nothing worked.
I'd like to use the method proposed above, but as my phone is a 918 and not 918N, will the files in the links work, or will I simply brick my phone?
I bricked my OT-918 Android v2.3.6 when I tried alternative methods...
I guess it's waiting untill another exploit comes
I downloaded the scatter file from noxxious' attachment but because I bricked a phone already I decided to look up what those files actually are.
The ARM development tools use scatter files to describe load regions, each of which might contain one or more execution regions
Also saying: Wrong scatter file would mean wrong memory is overwritten which will obviously lead to a brick (eg, phone tries to find OS, but because OS is not written in the correct place it cannot load it. Exactly what happened to my phone)
After some searching I discovered that you can easily retrieve the memory regions with ADB.
adb shell "cat proc/*" > device_info.txt
This will give you a nice text file with much information about your device...
Interesting part is this:
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00080000 00020000 "pro_info"
mtd3: 00300000 00020000 "nvram"
mtd4: 00020000 00020000 "seccnfg"
mtd5: 00060000 00020000 "uboot"
mtd6: 00600000 00020000 "boot"
mtd7: 00600000 00020000 "recovery" <- Seems like we need this region
mtd8: 00120000 00020000 "secstatic"
mtd9: 00060000 00020000 "misc"
mtd10: 00300000 00020000 "logo"
mtd11: 000a0000 00020000 "expdb"
mtd12: 07300000 00020000 "system"
mtd13: 09100000 00020000 "custpack"
mtd14: 03c00000 00020000 "cache"
mtd15: 09fa0000 00020000 "userdata"
If you think logically (and know a little about hexadecimal stuff) there is no space between the regions...
Meaning we can calculate the addresses of all memory pages. For example (we start at 0x0)
PRELOADER = 0x0 (with size 0x00040000) out of this follows that the next region should be at 0x0+0x00040000 = 0x00040000
DSP_BL = 0x40000 (size = 0xC0000)
following that PRO_INFO should be located at 0x40000+0xC0000=0x100000
I'm just posting a little of my research... Maybe someone with more experience knows if I can use the same scatter file as noxxious attached...
@others with an OT-918/918N/D/M: Please also try to retrieve the memory regions so we can compare... Maybe those regions are dynamic. I don't know any android developing