Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About excel0

  • Rank
  • Birthday 11/27/1997

Contact Methods

Profile Information

  • Location
  • Your Current Device(s)
    Cherry Mobile OMEGA HD 2.0
  1. May I ask or can you please ask them where the ROM is ported from? I can't reply cuz my Rep is too low. Thank you :)
  2. Thank you for your reply and I'm really happy that this helped someone :D . I will be posting the ROMS soon :) . Please take note that flashing these might brick your device :excl: . Even though they're basically the same phones, the original Q1000 and the OHD2.0 (rebranded) have differences and the ROMS I will be posting are for/ported for the OHD2.0. And one more danger is that I have no idea what build number (Build 7/Build 49) should be used for the original Q1000. But the only difference so far in my experience regarding Build 7 and 49 ROMS are their boot.img. So I guess you should extract the boot.img of YOUR phone and replace the one in the ROM with it. Although I am not exactly sure if it would work and THERE WILL STILL BE HAZARDS :excl: . Please "up" my post if it helped you (in this case it did) it really helps me a lot. Thank you :D
  3. ClockworkMod Recovery: SP Flashtool Method: *with (some) Pictures Download the following: a. SP Flashtool - Direct Link: http://goo.gl/6nlbkH (SP_Flash_Tool_v3.1328.0.183.7z, 3.24 MB) b. MT6589 scatter file - Direct Link: http://goo.gl/OYlHLx (MT6589_Android_scatter_emmc.txt, 523 KB) c. MT6589 Drivers - Direct Link: http://goo.gl/IspeSa (MT6589 drivers.zip, 402.77 KB) d. Recovery Image - Direct Link: http://goo.gl/fgLL40 (recovery_6028.img, 5.85 MB) Extract "MT6589 drivers.zip" Run "install_driver.exe" if you are on a 32bit/x86 OS and "installdrv64.exe" if you are on a 64bit/x64 OS. It is highly recommended to do a system reboot after the driver installation. Extract "SP_Flash_Tool_v3.1328.0.183.7z" Run "Flash_tool.exe". In the program window with the name "Smart Phone Flash Tool (Runtime Trace Mode)" that showed up, click "Scatter-loading" (see: Figure 1.1). Figure 1: In the pop up explorer window showed up, navigate to the "MT6589_Android_scatter_emmc.txt" file. Select it and click "Open" (see: Figure 1.2). Figure 1.2: The table in the program window will be filled up. Tick the box for "RECOVER" in the "name" column, then click the word itself (See: Figure 1.3). Figure 1.3: On the pop up explorer window, navigate to the "recover_6028.img". Select it and click "Open" (see: Figure 1.4). Figure 1.4: On the device, go to Settings > Developer options, and tick the USB debugging box Turn off the device and remove the battery. Connect the device to the PC with a USB Data Cable On the PC, click download and click yes to the warning pop up. Now place back the battery. The program should start downloading the file to the device and finally a pop up windows with a green circle should be seen. Close the program, remove the data cable and remove the battery of the device. Place back the battery in the device and boot to "recovery mode" by pressing "power + volume up". It should boot you to "CWM Recovery v6.0.2.8" Congratulations! You now have a (better) custom recovery! Mobileuncle Tools Method (very easy): Download the following: a. MobileUncle Tools - Play Store Link: http://goo.gl/OncwbY (Mobileuncle MTK Tools, 1.2 MB) b. Recovery Image - Direct Link: http://goo.gl/IspeSa (recovery_6028.img, 5.85 MB) Place the "recovery_6028.img" on the root of your SD Card Launch Mobileuncle Tools and tap "Recovery Update" (see: Figure 2.1) Figure 2.1: tap "recover_6028.img" under "Recovery file in SDCard". If you haven't placed the "recovery_6028.img" on the root of your SDCard at this point, you will not see and be able to do this (see: Figure 2.2). Figure 2.2: Tap "OK" to flash recovery (see: Figure 2.3). Figure 2.3: Now that you have a full featured custom recovery go down below to install custom ROMS.
  4. Rooting: Framaroot Method: Download Framaroot - Direct Link: http://forum.xda-developers.com/attachment.php?attachmentid=2293503&d=1380569629 (Framaroot-1.6.1.apk, 908.2 KB) Forum Thread: http://forum.xda-developers.com/showthread.php?t=2130276 Copy the apk to your SD Card or Phone Storage Go to Settings > Security, and tick the Unknown sources box Install the apk and launch it Simply tap Boromir and it should tell you to reboot WITHOUT FORCE CLOSING. If it does FC, just do it again and it should eventually work the second time. Reboot! You have now successfully rooted your phone. The next thing to do is to update SuperSU if an update is available.
  5. OMEGA HD 2.0 XOLO Q1000 Device Information: The OMEGA HD 2.0 is a 5" smartphone by the local Philippine mobile phone brand, Cherry Mobile. It is simply a rebranded Xolo Q1000. Its specifications are completely the same as the Q1000 except for the camera resolution. Even though the OHD2 is said to have a 12MP camera it only has an 8MP one which is interpolated to capture a 12MP image. You may also notice that the OHD2 is labelled to have a qHD screen on the brand's website but this is false as the OMEGA HD 2.0 is indeed HD. Specifications: Operating System: Android Jellybean 4.2.1 Chipset: MTK 6589 CPU: 1.2 GHz Quad Core MT6589 GPU: PowerVR SGX544 Memory: 4GB ROM (1GB Internal Memory, 1GB Phone Storage/Internal SD Card, remaining for misc partitions) 1GB RAM Micro-SD card, up to 32GB Display: IPS LCD Capacitive Touchscreen 720 x 1280 pixels, 5.0", ~294ppi 5 point Multitouch Primary Camera: 12.6MP, 4096 x 3072 pixels, Interpolated LED Flash, Autofocus 1080p video recording @ 30fps Secondary Camera: 1.9MP 1600 x 1200 pixels Battery: Li-on 2100 mAh Dual SIM SIM1 - 2G, 3G SIM2 2G only More Information: Because the OHD2 has a Mediatek Chipset it does not have that much freedom for development of custom ROMS because Mediatek does not provide device source codes openly unlike Qualcomm and a few others. Although some source codes have been released for the MTK 6589, there isn't seem to be much interest in developing custom ROMS like Cyanogenmod or AOKP for this phone or any other Mediatek phones. But because a lot of devices share the same Chipset as the OHD2 many have ported ROMS from these devices to this phone. The OHD2 also has 2 build numbers, 49 and 7. These can be found in the "About phone" option in "Settings". The build number is crucial when flashing ROMS because some ROMS cannot support both builds. Next post: Rooting
  6. hmm ok. If this works correctly for my blade I'm gonna go 10.1/4.2 forever :D
  7. I don't want to seem like one of those people who whine for changes and fixes but is there a possibility that you could um... like... I dunno... fix... S2E completely? please... :unsure:
  8. Flashed! *GASP* :o You included Apollo?! :blink: Thank You! Thank You! Thank You! :D Also, thank you for returning the nav bar resize option. :)
  9. Nice job fixing the white texture bug. :) I though it was just my IO scheduler (noop) so I switched to sio but still had the problem. Anyway, why did you disable HW Acceleration on the Lockscreen? :mellow:
  10. well that was unnecessarily offensive. I just ASKED for a simple (or so it seems) fix that's all, but yeah I already reverted back to CM10 (cont. by daemond) and still suffer the same issues. Why do these new ROMS not feature nav bar resizing, why? :(
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.