www.chinaphonearena.com

Quote: I say this because it was just when I tried to install a rom for MT6577 I made ​​my unstable NGM Wilco.

let me try to explain this.

at needrom you will find tens or hundreds of roms for chipset mt6577.
By your logic they should all work.

each rom has 5 main software components in no particular order they are

1) a kernel known to work on target device
2) kernel modules known to work on target device
3) shared objects ( roughly cousins to kernel modules) known to work on target device
4) various executables that can be transferable
5) text files like build.prop not transferable

I can not help you any further.

###########
crude advice is

weigh up is this a good phone?
----if yes buy a second one and copy all firmware off it using flashtools including nvram
-------------flash your original phone ....give original phone a new IMEI and sell it

If phone is crap.....read these forums on what other people recommend
or ask what to buy based on how you intend to use phone.

good luck

Why people never make a backup before trying any flashing is beyond me....
Would they also dismantle their cars without being a mechanic?
I would only try that having a second exact same (backup) car....

@aus9 : yep, patience is the word my dear Watson.

(2014-10-25, 00:04)mirandam Wrote: [ -> ]Why people never make a backup before trying any flashing is beyond me....
Would they also dismantle their cars without being a mechanic?
I would only try that having a second exact same (backup) car....

@aus9 : yep, patience is the word my dear Watson.

But no, the phone despite the failed attempt to install a rom is ok thanks to a my Nandroid backup ....
The fact is that they simply do not have the stock recovery, or with the firmware download them from the site NGM would have already ended.

thanks

---

updating

Hardware: MT6577
Model: Wilco
Build number: Wilco
Build UTC dates: 20130128-124713
Android v: 4.0.4
Baseband v: MAUI.11AMD.W12.22.SP.V5.P9, 01/10/2013 20:34
V Kernel: 3.0.13 (Android @ Android-Desktop3) (gcc version 4.4.3 (GCC)) # 1 SMP Mon Jan 28 20:41:32 CST 2013
Uboot build v: MAIN2.2.ubt.3123
LCD Driver IC: 1-gn_hx8369_dsi

After much research online I am aware of the various tools MKT I thought I used to just flash the stock rom. From first use MTK droid for a full backup of the rom and its block preparation for SP flash tool.

I would also add that I can not install from the Droid MKT CWM recovery screen and the program from this error:

--- ERROR: Boot unthe public mailing list [email] [email protected] [/ email]

I proceed installing on my PC with Win 8.1 drivers preloader excluding the control of the digital signature and then start the SP flash tool (actually I tried both ver. 3 that the 5). Unzipp the stock firmware in which I find a file that scatter SP flash does not load because of the lack of braces between the blocks. Duly recompile the file and finally SP flash sees and loads all of the blocks that make up the stock rom. All happy, I click on download, I connect the phone without battery, now part of the red bar up to 100% but then I have to display something like this error: "Ricognized rom etc etc. "

This is the content of my stock rom:



At this point I say, "and if you upload my backup from MTK droid made ​​by excluding the recovery?" Ok I proceed, load the file excluding the scatter blocks preloader, sec_ro and recovery with the hope that the reboot I finally compare the stock recovery. Seee n word ... I show you the two errors found after clicking on download and have connected my Wilco without batteries:



So how do I restore this phone to its original state? Thanks to those who want to give me the cue just and excuse me if I have dwelt but I wanted to be as accurate as possible.

hello

Just search for BROM error on this forum, you will find lots of posts and answers.

motoniko77, see this post for your Cygwin errors. [Only registered and activated users can see links Click here to register]
Just download the files and replace the current ones in the MTK Droid Tools installation folder.
Your BROM errors might also be driver-related. Try the first part of the post for your driver issues.

Good luck!

Thank you