ExSpiver, try building and installing CWM through the link aus9 gave. Once you have it, go into recovery then using ADB run the cat /proc/cpuinfo command. That will be more truthful about the phone's hardware, i believe.
Let us know what comes up, so we can find out how accurate Droid Tools, and other apps are.
Actually you have 2 choices
android terminal and adb with PC
PC stulff needs adb to be setup and you may not have it,
its actually easy to achieve in Linux and here is PC commands
My results
not OP
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
adb shell cat /proc/cpuinfo
Processor : ARMv7 Processor rev 3 (v7l)
processor : 0
BogoMIPS : 2072.57
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3
Hardware : MT6582
Revision : 0000
Serial : 0000000000000000
2) If adb is hard for you to set up
download playstore app ....search for android terminal
install it and run it....as non-root
(2014-08-29, 12:09)Athos Wrote: [ -> ]ExSpiver, try building and installing CWM through the link aus9 gave. Once you have it, go into recovery then using ADB run the cat /proc/cpuinfo command. That will be more truthful about the phone's hardware, i believe.
Let us know what comes up, so we can find out how accurate Droid Tools, and other apps are.
Ok i tried Aus9's recommendation and i stop at the very beginning. When i load my scatter file there is some information missing. The cache information that i need is not in the FlashTools when i load the scatter file. When i open it with a notepad i see this:
CACHE
file_name: cache.img
is_download: false
i have no idea what to do next... i will try aus9's new thingy and see what will happen
Is this a newly created scatter map?
At the very beginning -- step 5? The information you need is just the start address of the cache to mark up to where you will have flash tool do the read back.
Does the read back fail?
Ok sorry for the late response...
using aus9 android terminal thingy i found out that my processor is ARMv9 processor rev10(v71) which again is totaly different from what i knew about this device...
On second look i saw the hardware is MT6589... ok so what now?...
Athos - yes a newly created scatter map using the guide you gave me at step 5 i cant get to the read back because the scatter file its self does not contain cache information so i cant begin the read back without the proper info i guess
OP I would like you to know that Athos and I are Android partners
giggles
he handles Flashtools stuff because I can't use it and I offer some alternatives
####################
Are you able to root this device?
See the rooting tools and try framaroot first
framaroot third option worked for me, you need to reboot to test though.
###########
if and when you are rooted, we can then extract via either
adb
android terminal
your known to work boot.img....otherwise you can't get into normal boot
b) an unknown recovery image....likely to be a broken image based on your testing so far.
c) I will then need your dumchar information which gives hex values of where and what size various sections of your flash media are
d) I can then offer to build a CWM/CTR risk to be borne by you and none by me
################
this is only a suggestion and will require
root
android terminal and me guiding you thru some commands
you can get an idea of what that might be by viewing
[Only registered and activated users can see links Click here to register]
BEST OPTION get Athos to guide you.
I am second best.
aus9, Yup, I think ExSpiver's phone is rooted.
ExSpiver, have you made a backup of your phone with Droid Tools? If you haven't, do so. Then proceed with the Ranpha CWM method.
If you already have a backup, just go back into MTK Droid Tools, under the root, backup, recovery tab, selecct To choose boot.img, then click on the recovery and boot button.
Agree to create CWM, and decline to install patched files.
The patched recovery image made is the image file you update your recovery with via Mobileuncle Tools.
The more detailed tutorial can be found here
[Only registered and activated users can see links Click here to register]
Ok well im glad that i get helped by both of you
Yes my device is indeed rooted i will try aus9's suggestions after 2 days (when my nightshifts are over)
Athos i have tried that already and i end up with only boot.img and not recovery.img and i dont know why that is happening so i get stuck at that point...