[PROJECT CLOSED] Horsing around

[aus9]

From post 8 using adb to get into recovery mode
you may notice an option to do a factory reset.

I have not found any way of getting into this mode other than thru adb.

I have found a way of booting with vol down but that gets me to safe mode - normal mode.

Anyhow I have just tested factory reset and it works as expected.

The documentatation supplied by M-Horse is poor and I pity anyone buying this phone.....yes I pity myself.

[aus9]

ok getting somewhere slowly

from adb

Code:

adb shell
mount | busybox grep /system
/dev/ubi0_system /system ubifs ro,relatime,compr=lzo 0 0

Code:

mount -o remount,rw /dev/ubi0_system /system
mount: Operation not permitted

yep looks like I need that flashboot adapter

[linr76]

oh wow, ubifs, good luck with that.
you really wanted to make it hard on yourself eh?
;)

[aus9]

yes this phone is very secure.

Not that there is anything wrong with that.

[aus9]

Ok starting to look at fastboot....but adapter not yet arrived

using adb reboot bootloader command I can get to a "blank screen" which has a bluish tinge but no text or icons

adb now fails but fastboot now works

/var/log/messages snippet

Aug 18 18:24:09 asus kernel: [ 5458.806128] usb 3-2: new high-speed USB device number 20 using xhci_hcd
Aug 18 18:24:09 asus kernel: [ 5458.822554] usb 3-2: New USB device found, idVendor=18d1, idProduct=0fff
Aug 18 18:24:09 asus kernel: [ 5458.822562] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=10
Aug 18 18:24:09 asus kernel: [ 5458.822567] usb 3-2: Product: fastboot Gadget
Aug 18 18:24:09 asus kernel: [ 5458.822571] usb 3-2: Manufacturer: Spreadtrum

this means I shall update my ini file so it now reads

0x1782
0x18d1

However, local user can not use fastboot, permission denied so I need to create the root file
/root/.android/adb_usb.ini
and restart server

2) new reboot and go into recovery thru adb reboot recovery as per previous page and image.....offers adb update
----going into it....offers adb sideload

at this point adb and fastboot are no longer working in Linux.

In fact....." adb sideload filename.zip" fails as adb is no longer recognising any device........this is a road block.

There is no way of using buttons in Android to get any where

In other words I am no closer to any result but have at least eliminated some errors.

cheers

---

added that new string to udev rules solves my fastboot permissions for local user

[aus9]

from mounts, I can see the following

/dev/ubi0_system /system ubifs ro,nosuid,nodev,relatime,compr=lzo 0 0
/dev/ubi0_userdata /data ubifs rw,nosuid,nodev,noatime,compr=lzo 0 0

Code:

adb shell ls -al /dev/ubi0_userdata
crw-rw---- system   system   243,  21 2014-08-19 13:28 ubi0_userdata
gordon@asus:~$ adb shell ls -al /dev/ubi0_system
crw-rw---- system   system   243,  17 2014-08-19 13:28 ubi0_system

Heck----give me a break

[aus9]

after a bit of a search, I can find NO roms for m-horse s51 anywhere

but searching for sc7715 (chipset) gives me an unrooted pac Rom
[Only registered and activated users can see links Click here to register]

running strings against the unpack shows a close match.....closer than anything else

Code:

strings orro.pac | grep sc7715
chip_phy_sc7715.c
sc7715_mmu_config.c
sc7715_clock_cfg.c
sc7715_audio_cfg.c
Project Version:   sc7715_modem
MMI Version:       sc7715_modem
HW Version:        sc7715_sc7715_modem
Project Version:   sc7715_cp2
HW Version:        sc7715_modem
soc_is_sc7715
dsc7715
sc7715_sc7715_modem
soc_is_sc7715

My build.prop has string

ro.build.id=KOT49H

Code:

strings orro.pac | grep KOT49H
ro.build.id=KOT49H
ro.build.display.id=KOT49H test-keys
ro.build.description=scx15_sp7715ebplus-user 4.4.2 KOT49H eng.qiy.20140804.105318 test-keys
ro.build.fingerprint=ORRO/scx15_sp7715ebplus/scx15_sp7715eb:4.4.2/KOT49H/eng.qiy.20140804.105318:user/test-keys

fingerprint is different, mine is
Spreadtrum/c935w_jhm_e08plus_UUIhvga/c935w_jhm_e08:4.4.2/KOT49H/7715_4.4.2_c935w_jhm_e08_V05:user/test-keys

but its a step closer so I can watch for anyone rooting this device.

2) trying to google the specs of this device Orro G108 is not so good

Ahh well....I dream of getting my factory adapter one day

---

unbelievable I have had my first good fortune.

Mediatek perl scripts that I have posted about in this forum don't work with SPD recovery images. They report an error and only unpack the kernel image.

2) I discovered that Android Image Kitchen, which has Windows and Linux version do unpack recovery images.

3) I can't grrr still get root to get mine.....but I have downloaded someone elses that has a different chipset and its weird!

4) I will show just the list

Code:

ls
authors.txt  bin  cleanup.sh  ramdisk  repackimg.sh  sc8810np.img  split_img  unpackimg.sh

ramdisk is similar to a mediatek ramdisk....anyone who has modded one should feel comfortable here .....the problem is split_img and here is why

5)

Code:

ls split_img/
sc8810np.img-base   sc8810np.img-cmdline    sc8810np.img-pagesize     sc8810np.img-ramdisk.cpio.gz  sc8810np.img-tagsoff
sc8810np.img-board  sc8810np.img-kerneloff  sc8810np.img-ramdiskcomp  sc8810np.img-ramdiskoff       sc8810np.img-zImage

Any Linux user can recognise the kernel is zimage and its size is 5.7 Mb unpacked.

b) the cpio.gz file unpacks to cpio then finally you can unpack it and it looks like a mediatek ramdisk....those other files (luckily) are text files

eg

Code:

file *page*
sc8810np.img-pagesize: ASCII text

#################

If I could extract either my boot image or kernel image I might be able to mod it to CWM or CTR and flash it.....thats the sticking point

thanks for reading

[aus9]

a kind member informed me there is a Linux package of impactor here
[Only registered and activated users can see links Click here to register]

I chose to run the 32 bit on my laptop.

gui starts and attempts to root.....but it could not find a data file in its database to match so rooting could begin.

Ahh well.

I think at this point we can muse

I am flogging a dead HORSE