• Content count

  • Joined

  • Last visited

  • Days Won


MJonMoDaCo last won the day on February 28 2015

MJonMoDaCo had the most liked content!

Community Reputation

32 Excellent

About MJonMoDaCo

  • Rank
  • Birthday 03/14/1982

Profile Information

  • Location
    Nelson, NZL
  • Interests
    PCs, Phones, Cars, Sports of all sorts.

Previous Fields

  • Your Current Device(s)
    ZTE Skate Acqua LG Optimus One

Recent Profile Visitors

1,223 profile views
  1. How to root Zte blade A310?

    I'm not sure, but please don't use anything from this forum to do it with, as that phone is NOT a Blade 3.
  2. Device / ROM is corrupted. What steps can be taken?

    Yes. Because of this, you would probably be better installing ClockWorkMod, and disabling the Signature verification to flash your ROM. It's effectively a custom ROM anyway, so you might as well. Perhaps your friend may help you, although I'm not so sure how necessary that will be. Good luck though.
  3. Device / ROM is corrupted. What steps can be taken?

    Hi Meir, Yes a factory reset may work, but it may also lead to the same problems happening again before too long, but it would seem the best course of action is to reinstall the ROM, at which point I have to say you need ZTE's keys to make alterations to a stock ROM, which I highly doubt you'll get a hold of. A full wipe and fresh install would be the ticket. If symptoms persist check your hardware.
  4. ZTE Blade III stock ROMs

    I know you have Android 3e recovery, but is it for the same country as the firmware you have? You need to flash the right recovery for the country ROM you are downloading. That is why the signature check is failing.
  5. ZTE Blade 3 spontaneously bricked

    If you're positive it had CM7 on it, then you may have a Blade 1 (which came with Gingerbread 2.3), and not a Blade 3. But it looks like it has failed, which, after all these years, if it is a Blade 1, is still an impressive effort.
  6. Bricked Blade 3

    You normally need to turn on adb bridging on the phone before the computer will see it (using adb devices command). CWM recovery has the option to, but I know you don't have that recovery. Can you get to your stock ROM recovery (Hold Volume up while pressing power button for about 10 seconds)? If you can, you should be able to do a system reset. If that doesn't work, then it means that Android needs re-installing, The only ROM in the forum for VIP Serbia available for download is here. You will need to download it if you can't do a system reset. If you download it, and it works, then please back it up somewhere (I put NZ Rom on Dropbox account, for example), because you don't know when they'll be gone for good. You'll only need to install CWM if you can't get your current ROM working again. Let's try to get to recovery first.
  7. MTP Problems whith CM mod.

    That's odd. Is it recognizing your device properly? I still have the full set of drivers for them if you haven't already installed them (and they are for both Blade III and Skate Acqua). But using MTP isn't something I normally use, yet that's the first thing I'd check if it isn't working, because it needs to have the phone's exact drivers, in order to use the MTP function properly (the MTP drivers are in the package too, but not fastboot).
  8. Status 7 ZTE Blade III when trying to flash custom rom

    1) Please don't shout 2) You're English is fine. Grammar could do with some work. Doesn't everybody's? 3) Please post to the right thread. The CWM recovery thread, where KonstaT says: And so that's what you do. Flash it from ClockworkMod.
  9. AnTuTu benchmark record?

    On the exact same phone? You'll need more than just a screenshot. You'll need proof it's the exact same phone by using a video camera. In either case, it's extremely doubtful you'll get anywhere close. Even after 1 year my phone dropped a couple of thousand. Expect the same.
  10. AnTuTu benchmark record?

    You still don't get it: New motherboard = New CPU + New RAM chip (both embedded!) = higher scores, because they haven't been worn out yet. I'm sure if I did this I would be leaving your score of 6856 in the DUST. There is no need to try it. It speaks volumes of sense, even to a layman. New phone, in an old case, hence the newer (overclocked) score of 11003. I repeat: There is nothing special about this.
  11. android 5.0

    Probably best not to try it. These phone's of ours aren't going to be able to cope with it very well... This phone has reached the end of it's life (by a good year, to be honest) and it would take a lot of effort for something that won't work properly, at least in the beginning, and probably ever. We are far better off to get newer phones, and even the lower end phones are leaving ours (hardware spec wise) in the dust. But they will always be classics. Probably ZTE's best phone thus far in terms of it's user base (devices sold). But with a new phone, means being able to get Android 5.x and possibly 6.x
  12. AnTuTu benchmark record?

    Yes. It. Will. Do you even read what you're posting? On your own thread? The first test posted on the 14th of January is 6856!! The "record" you're talking about is 11003 posted here - which was dated 13 of February, an entire month later, after you'd bricked, repaired and re-flashed the device: Which therefore leads to assertions such as: When really....
  13. AnTuTu benchmark record?

    It's only worthwhile as a test against the same phone after periods of time. Comparing tests against other phones (even the same type) isn't going to be a fair test if the phones tested against have had more use. Make sense? It's pretty obvious. Again, it's only useful for benchmarking (that's the word used) the performance of the phone over a period of time! The reason why your newer phone would have a better benchmark, is because it would be newer with (I'm assuming) better performance capability. You can use it as a benchmark against your Blade 3, but it's really only useful over time for itself, and the further in time you go, the less useful for comparing with other phones, and only the phone itself.
  14. AnTuTu benchmark record?

    Considering the state that it is currently in, who really is going to care? It's nothing special, I assure you. If you'd done it on the phone that you had bricked, perhaps - it wasn't in a "new" state. Unfortunately for you, I don't see you getting a score as high as the high 12,000's (I wish I could show you) but this was straight from factory floor, and not overclocked :o Watching you try now is a recipe for madness. Trying it on your new phone is far more likely, but nobody is going to care. This attempt at trying to swing the big one is utterly pointless - it's a bench-marking program, designed to show the current life capability of the device over time, and not a good way to try comparison against the life of other phones with differing usage i.e. not all people use their phones constantly for gaming, or have it constantly overclocked, flash the guts out of it with every ROM they see etc. Some people just use their phone, as a phone, and that would lead to slightly better performance over time than those that don't, despite having the phone for the same amount of time. So take the test on your new phone, as a scientific fair test, do nothing to it (ie overclocking) and then try it again in a year's time (assuming you haven't bricked that) and see if you get anywhere close to that mark again. Comprende vu?

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.