honeypot62

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About honeypot62

  • Rank
    Newbie

Previous Fields

  • Your Current Device(s) ZTE Racer
  1. This will install a custom recovery image with rooted ROM, and should be able to fix a 'bricked' Racer (i.e., will not boot into the normal 'FTM' recovery mode with the vol. down button pressed on power up). Files have been uploaded to here https://www.mediafire.com/folder/wj19vfnvoj3cv/ZTE_Racer 1) download the ROM file 'update.zip' - this somehow needs to be transferred to the SD card in the Racer 2) download and uncompress the recovery image file 'rickywyatt.rar': unrar x ./rickywyatt.rar 3) add executable permissions to enable `fastboot-linux` to run: chmod 755 ./fastboot-linux 4) `install-recovery-linux.sh` runs an incorrect command, it is necessary to flash the recovery manually as follows: i. attach the Racer to the USB port and reboot while pressing the vol. down key - a green android image should appear and the LED turn red (if 'bricked', otherwise presumably the normal 'FTM' recovery screen) ii. run the following command: ./fastboot-linux flash recovery ./recovery.img 5) reboot the Racer holding the vol. up key, this should boot into recovery 6) use the vol. buttons to move around menu, home button to select i. clear / delete any cache, etc. as thought needed (I'm not entirely sure what this is all about myself, but I usually clear and reset the lot) ii. select the menu option to flash the update image from SD card iii. select the reboot menu option On reboot you should find a rooted desktop, there is a widget not found error but this can be dragged into the bin.   NOTES The ZTE Racer kernel source code is available on the ZTE website (also uploaded to the same website as the recovery and ROM)) which presumably can be used to build the original recovery and a ROM that is not rooted. If the mobile is not 'bricked' then presumably the ZTE Windows update tool will reflash the device  (the instructions aren't particularly clear here, the Racer needs to be in recovery mode before this software will work - reboot pressing the vol. down key until the letters 'FTM' appear).    
  2. I doubt if there is anyone actually left in this nick of the woods nowadays, however on the off chance someone passes by in a time machine, would anyone happen to know if the original 3 network stock ROM and recovery image (originally to be found http://raceroms.co.uk/ - now a dead link) can still be downloaded from anywhere? The stock recovery image was the only one I could get to recover a bricked Racer, so I could do with that in particular.
  3. Android 4.0.x on ZTE Racer

    US Cellular Launches The ZTE Imperial, A 4G LTE Android 4.1 Handset Available Online Today, In Stores Tomorrow There seem to be a few JellyBean ZTE kernels at this point... http://support.zte.com.cn/support/ I'm not sure what if any hardware compatability there is with the Racer amongst these models, but can any of these be reconfigured and recompiled?
  4. green_hacker's GrEeN_MoDe_2.3.7_Rom (Jan. this year, 2.3 kernel) works very smoothly, however does not have the latest CM7 patches (which shouldn't be too much of a problem for most). RacerMod-1.5-alpha-1-Racer.zip by mikeioannina (build from Jan. this year, 2.6 kernel)) works fine with the accompanying kernel update RacerMod-1.5-alpha-2-kernel-racer.zip. Note though the kernel update introduces a few seconds of screen corruption (green/ blue strippy lines) shortly after the green Android appears on boot. Builds after that and keyboard bugs (namely ghost characters) reappear (i.e., the 'phone is not usable). mikeioannina's CWM-5.0.2.8-1.3.zip recovery image has input issues also (only the vol. up/down buttons seem to work, the remaining buttons somewhat erratically if at all) so I have fallen back on Raceroms' ClockworkMod Recovery 4.0.1.4. Reading through the Jelly Bean threads, CM7 seems to be discontinued at this point, but it is believed that the only only issue to move to Android 4 is a build of a new kernel which should fix touch screen bugs. (At least a few months ago reported as being worked on.) *** If anyone working on Jelly Bean would like to delegate some development tasks can I suggest they post here. *** For newbies a quick refresh of install instructions: - download a ROM (approx. 80M), and copy across to the SD card - install fastboot ('apt-get install fastboot/unstable' on Debian 6; ref. also the Raceroms site under extras) - download a recovery image (e.g., ref. above Raceroms link) - attach to PC with USB cable, and reboot depressing the vol. up key (screen will stop at the green Android) - run the command 'fastboot -w flash recovery [downloaded recovery .img file]' - take the battery and cable out and reboot depressing the vol. down key into recovery, vol. up/down to select a menu option, left rocker button selects, right is back (may vary depending on version of recovery and 'phone) - you can at this point (it might save some problems occuring later on) wipe data/factory reset, wipe the cache partition, under advanced wipe the Dalvik Cache - finally install the zip from sd card To reset the 'phone back to factory condition, source the original ROM (Raceroms has a collection of these) and follow the same instructions as above. It is sometimes useful after installing a mod'd ROM to extract the recovery image from the manufacturer's ROM and using fastboot flash it back to the 'phone (it then takes slightly more work to hack the 'phone - ref. instructions above to flash recovery). By way of an anecdote, I bought a Racer when it became the first sub-£100 Android device on the market (thought I would have a look to see what it was all the fuss was about). I then asked for a refund on account of the VPN drivers not being installed (and a few other minor bugs, but I needed the VPN to work), and was duly referred by ZTE (China) to the carrier, who would not make the refund but however did leave me with a second Racer! I then complained to the consumer ombudsman (as I still would have preferred a refund), who concluded it was the responsibility of ZTE (who did not at that point have a UK website), to make the refund, not the carrier. And at that point exhaustion setting in I duly started to lose the will to live (the thought of going through extracting a refund from a Chinese manufacturer). Hence I am now the proud owner of no less than two ZTE Racers ;) Thanks to the developers working on this 'phone :)
  5. Racer II Official Rom Free

    http://raceroms.co.uk/
  6. OpenVPN on Android 2.1+??

    I'm told 2.1 is missing drivers for OpenVPN - if you haven't already installed these. Myself I attempted to get a refund out of Three as the device clearly should connect using OpenVPN (and other VPN protocols, the menu options etc. are all there) but does not (out of the box that is). Three gave me a second ZTE and told me to try that (which likewise duly did not work). After going to the ombudsman Three legally referred me to their Chinese suppliers, at which point and after over a year of all this I started to lose the will to live, and gave up (ZTE did not have a European presence at the time). You could reflash an updated version of Android (if we have one, am about to look), that should do it.
  7. cyanogenmod RC0 seems to work OK also http://android.modaco.com/topic/349337-cyanogenmod-7-builded-from-sources-ready/
  8. ZTE Reflash broken??

    This one is largely answered here http://android.modaco.com/topic/349626-zte-wont-factory-reset-nor-access-ftm-mode/page__gopid__1863883#entry1863883
  9. OK, I can confirm 4.0.1.4 will vol- into recovery but not using Recovery Manager (nor the current ROM Manager which will not install throwing parser errors), but using fastboot: fastboot flash recovery recovery-clockwork-4.0.1.4-mooncake-gen1.img The link to the fastboot download is above, but see also this thread http://android.modaco.com/topic/345525-stuck-on-green-android-screen/page__p__1863799__fromsearch__1#entry1863799. In recovery vol buttons and the call-control bar (silver bar at the base of the ZTE) control the menu - the left rocker selects, right is the back button. Following the reflash instructions here http://android.modaco.com/topic/346723-roms-latest-237-cm7-racerboy-roms/... And 15 mins later I seem to have a 2.3.7 Android up and running :)) Many thanks to all the coders and hackers, u know who u are >:-)
  10. Stuck on Green android Screen

    This could be it http://android.modaco.com/topic/346061-guide-fastboot-recovery-for-racer/ (linked to on this page). If that doesn't work there is at least one other fastboot exe that can be downloaded (it seems not to be included in the Android SDK at the moment - which I assume is where it was to be found originally).
  11. Not sure of the versions that I used initially, I had stuff hanging around from a while ago -- can't get ROM Manager to install at all at the moment, see this thread... http://android.modac...reflash-broken/ Update: OK, will have a read of the page later, cheers.
  12. Aiming to reflash http://android.modaco.com/topic/345122-roms-4pda-235-cm7-nightlies/ ROM Manager linked to on http://clockworkmod.com/rommanager is returning a parse error and downloading from Market Place only ROM Manager premium is available on the app.(still have to install the free version to use) and the website is returning a your device is not supported error https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en&rdid=com.koushikdutta.rommanager&rdot=1&pli=1 Does anyone know how to role back to a previous version?
  13. OK, back in FTM mode. Found the fastboot exe linked to here http://dottech.org/tipsntricks/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/ (does not seem to be included in the sdk nowadays ref. http://developer.android.com/sdk/index.html, and adb would not recognise the Racer - could have messed around with installing the sdk drivers but didn't get round to this, e.g. , http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/). Booting the Racer with vol- down did not work (fastboot couldn't see it), but booting with vol+ and fastboot found a fastboot device. The command to reflash: >fastboot.exe flash recovery recovery.img (image downloaded from http://raceroms.co.uk/index.php/stock-roms) Useful reference page here http://wiki.cyanogenmod.com/wiki/Fastboot
  14. battery out back in press & hold vol down button power on just hangs at the android logo (remove battery to reset) Is this technically known as 'bricked'?

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