Database Info

[ROOT][ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM

SliPer ModRecovery and G1345 RootROM. What are they?
By now combination of these two is the only way to obtain root privileges on Gigabyte GSmart G1345 with the following ROM software builds installed:
0.56.4 build 1962.124.2931#EEU,
0.56.5 build 1677.124.2667#RUS,
0.56.5 build 1621.124.2855#Stellar,
0.56.6 build 1898.124.2952#CHT,
1.4.2 build 1970.124.2847#EEU,
1.4.3 build 1736.124.2969#WEU.
That's because no known exploit works on these builds.
SliPer ModRecovery is a custom Andriod system recovery. G1345 RootROM is a custom ROM for Gigabyte GSmart G1345/Mc Onsen MCG1345/Cherry Mobile Stellar smartphone with Dual-SIM support. Several versions of G1345 RootROM correspond to different builds, each designed for a specific region or reseller.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1345 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1345 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4;
adbd runs with root permissions and "USB Debugging" is turned on for logging of the boot process by default;
G1345 RootROM preserves SliPer ModRecovery on ordinary boot for further use (if stock ROM is installed, on each ordinary boot recovery partition is being rewritten with the original recovery image formed by patching original boot image with binary diff file recovery-from-boot.p).
Interface and kernel are derived from the original ROM.
Will I lose the warranty after installing G1345 RootROM by using SliPer ModRecovery?
Before calling for service install G1345 RootROM for your region, then install original ROM for your region. This is required to restore original ROM and recovery. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1345 RootROM?
WARNING! ALL userdata will be erased during G1345 RootROM installation process, so it's highly recommended to backup your valuable data!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1345 RootROM by using SliPer ModRecovery.
There're 2 types of G1345 model. They differ in WLAN hardware being used in their design. The first type of G1345 uses AR6002 WLAN platform and these devices can be flashed with the following ROM software builds (each of these builds is located in the root directory of the corresponding ROM archive update1.zip/update.zip): 0.56.4 build 1962.124.2931#EEU, 0.56.5 build 1677.124.2667#RUS, 0.56.5 build 1621.124.2855#Stellar, 0.56.6 build 1898.124.2952#CHT, 1.4.2 build 1970.124.2847#EEU, 1.4.3 build 1736.124.2969#WEU. The second type of G1345 uses AR6003 WLAN platform and these devices can be flashed with the following ROM software builds (each of these builds is located in "la" directory of the corresponding ROM archive update1.zip/update.zip): 0.56.4_1 build 1963.124.2931#EEU, 0.56.5_1 build 1678.124.2667#RUS, 0.56.6_1 build 1899.124.2952#CHT, 1.4.2_1 build 1971.124.2847#EEU, 1.4.3_1 build 1739.124.2969#WEU.
WARNING! IN ORDER TO INSTALL SliPer ModRecovery and G1345 RootROM CORRECTLY YOU SHOULD KNOW THE TYPE OF YOUR G1345 MODEL (THESE TYPES ARE THE FIRST OR THE SECOND TYPE MENTIONED ABOVE)! You're able to check this by installing original ROM for your region/reseller and selecting "Menu"->"Settings"->"About phone"->"Build number":
Original 0.56.4_EEU ROM
Original 0.56.5_RUS ROM
Original 0.56.5_Stellar ROM
Original 0.56.6_CHT ROM (registration required)
Original 1.4.2_EEU ROM (registration required)
Original 1.4.3_WEU ROM (archive password required )
Download one of G1345 RootROMs:
G1345-0.56.4_EEU.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Cz/
G1345-0.56.5_RUS.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Russia/
G1345-0.56.5_Stellar.zip - based on the original ROM from Cherry Mobile official website http://www.cherrymobile.com.ph/products/smart-social/stellar (FOR THE FIRST TYPE OF G1345 ONLY!)
G1345-0.56.6_CHT.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Taiwan/
G1345-1.4.2_EEU.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Eng/
G1345-1.4.3_WEU.zip - based on the original ROM from Mc Onsen official website http://www.mconsen.com/mcg1345.php
Then extract configure (THIS FILE IS REQUIRED ON G1345 FOR THE AUTOMATION OF ROM INSTALLATON PROCESS, BECAUSE DURING THE FIRST PHASE OF THIS PROCESS TOUCHSCREEN IS TURNED OFF) and update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable FOR YOUR TYPE OF G1345 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder. If you've got the first type of G1345, you should extract recovery.img from the root directory of update1.zip/update.zip archive, otherwise if you've got the second type of G1345, you should extract recovery.img, which is located in "la" directory inside update1.zip/update.zip archive.
Then turn off your device, insert SDCard (with configure and update1.zip/update.zip files located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. The first phase of installation process is automated (if configure is located in SDCard root directory) and performed with touchscreen turned off. After reboot touchscreen will be turned on and the installation process will be continued. At the end of the update process you'll get installed software version on the screen along with reboot request. Confirm reboot. Device will reboot in ordinary mode with SU and BusyBox properly installed. Enjoy!
In order to check whether you've got SliPer ModRecovery properly installed, delete/move configure and update1.zip/update.zip from the root of SDCard, reboot in recovery mode by holding volume up button + power button until blue LED blinks 3 times. If you get the following screen, then SliPer ModRecovery has been installed properly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1315 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1355 RootROM

root
Welcome sliper123!
I have a problem! I would be really grateful if you could help ...
1.4.2 EEU # 1970 ... is the rom on my device.
SD card root directory of the "configure" and "update1.zip" file, but in vain, after I run flasher.bat fastboot file, reboot, and delete only offers.
It is possible that something is not doing well ....
Thanks in advance for the help!
netjoe3

G1342
Hi,
I have G1342 from gsmart and i need root.
Android Version: 2.3.5
BaseBand Version: 1.8.0 build 1780#std
Build Number: 18.0 buid 1780.0124.3014# GSmart.
How to obtain root access.
Regards
Bluffmaster

Thanx man. Just what I needed. Works perfectly!

Great job
Hi SliPer,
I've just installed G1345-1.4.2_EEU.zip RootROM, it works perfectly. Thanks, excellent job.
My only problem is the lack of Kernel support for 2 way call recording.
Could you share your opinions how to patch or do something for 2wcr feature?
Thanks.
Best regards,
rocky

can i install the 0.56.5 update on my Stellar even though im using a 0.52 RUS Rom? please reply.
i think my phone is bricked
after i use the flasher bat the transfer went fine but after that the phone doesnt respond anymore.. also stuck at the Gsmart logo
Messaged Sent to sir Sliper
hello sir.. please help me.. i have a Cherry Mobile Stellar 1st Type of G1345
my phone got bricked when i tried your RootROMs... before i tried your RootROMs im in 0.52.2 RUS Rom so what i did is download the 0.56.5 RUS RootROMs then i prepared all the files that is needed like the ModRecovery Script and copied recovery.img of 0.56.5 RUS RootROM in the ModRecovery Folder.. i have installed all the drivers including the fastboot drivers... so here what happens.. i turned off my phone then go to fastboot mode.. then i opened flasher.bat and pressed Enter.. but after that nothing happens in my phone the LED just turned RED it doesnt boot and its not responding.. after waiting for 30 mins of black screen still nothing.. so i assumed that my phone is Soft Bricked.. and can you please help me recover from this brick sir? i have tried all update1 files all your RootROMs and even Stock ROMs but they cant be detected by the Recovery Mode so my phone is like a stuck right now gathering dust.. please reply to my message ASAP sir.. thanks !

[ROOT][ROM][RECOVERY]SliPer ModRecovery + G1355 RootROM

SliPer ModRecovery and G1355 RootROM. What are they?
Combination of these two is the only way to obtain root privileges on Gigabyte GSmart G1355 by now, as no known exploit works on it.
SliPer ModRecovery is a custom Andriod system recovery. G1355 RootROM is a custom ROM for Gigabyte GSmart G1355 smartphone with Dual-SIM support. Update script of this ROM is modified so that no images are being flashed during ROM installation process, except recovery image. Recovery image is restored by applying binary patch file recovery-from-boot.p to boot image on boot up. So the tasks, which are being performed during installation of this ROM, are just copying of several files to /system/app, /system/bin and /system/xbin, creating of symlinks and setting owner and rights for copied files.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1355 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1355 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4.
Stock interface and kernel are derived from currently installed ROM.
Will I lose the warranty after installing G1355 RootROM by using SliPer ModRecovery?
Before calling for service remove all symlinks from /system/xbin and the following files: /system/app/Superuser.apk, /system/bin/su and /system/xbin/busybox. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1355 RootROM?
NO userdata will be erased during G1355 RootROM installation process, but it would be better to backup your valuable data anyway!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1355 RootROM by using SliPer ModRecovery.
Download G1355 RootROM:
G1355-SU-BB-noflash.zip
Then extract configure (THIS FILE IS REQUIRED ON G1355 FOR THE AUTOMATION OF ROM INSTALLATON PROCESS, BECAUSE DURING THE FIRST PHASE OF THIS PROCESS TOUCHSCREEN IS TURNED OFF) and update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable for your G1355 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder.
Then turn off your device, insert SDCard (with configure and update1.zip/update.zip files located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. The first phase of installation process is automated (if configure is located in SDCard root directory) and performed with touchscreen turned off. After reboot touchscreen will be turned on and the installation process will be continued. At the end of the update process you'll get installed software version on the screen along with reboot request. Confirm reboot. Device will reboot in ordinary mode with SU and BusyBox properly installed. Enjoy!
In contrast to G1345 model SliPer ModRecovery hasn't been saved for further use in G1355 model. Why?
This is done intentionally to provide users with opportunity to roll back the changes made by G1355 RootROM.
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1315 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM

sliper123 said:
SliPer ModRecovery and G1355 RootROM. What are they?
Combination of these two is the only way to obtain root privileges on Gigabyte GSmart G1355 by now, as no known exploit works on it.
SliPer ModRecovery is a custom Andriod system recovery. G1355 RootROM is a custom ROM for Gigabyte GSmart G1355 smartphone with Dual-SIM support. Update script of this ROM is modified so that no images are being flashed during ROM installation process, except recovery image. Recovery image is restored by applying binary patch file recovery-from-boot.p to boot image on boot up. So the tasks, which are being performed during installation of this ROM, are just copying of several files to /system/app, /system/bin and /system/xbin, creating of symlinks and setting owner and rights for copied files.
What are the differences between SliPer ModRecovery and stock recovery?
The only difference between SliPer ModRecovery and stock recovery is that during ROM installation process Gigabyte signature verification is disabled in SliPer ModRecovery. So you're able to install any stock/custom ROM (suitable for your device). The only restriction, while installing stock ROM (not custom!), is that BUILD_SW_PROJ field in update_ver.txt file of already installed ROM and BUILD_SW_PROJ field in update_ver.txt file inside update1.zip/update.zip package on SDCard should be equal.
What are the differences between G1355 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1355 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4.
Stock interface and kernel are derived from currently installed ROM.
Will I lose the warranty after installing G1355 RootROM by using SliPer ModRecovery?
Before calling for service remove all symlinks from /system/xbin and the following files: /system/app/Superuser.apk, /system/bin/su and /system/xbin/busybox. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install G1355 RootROM?
NO userdata will be erased during G1355 RootROM installation process, but it would be better to backup your valuable data anyway!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install G1355 RootROM by using SliPer ModRecovery.
Download G1355 RootROM:
G1355-SU-BB-noflash.zip
Then extract configure (THIS FILE IS REQUIRED ON G1355 FOR THE AUTOMATION OF ROM INSTALLATON PROCESS, BECAUSE DURING THE FIRST PHASE OF THIS PROCESS TOUCHSCREEN IS TURNED OFF) and update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable for your G1355 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder.
Then turn off your device, insert SDCard (with configure and update1.zip/update.zip files located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. The first phase of installation process is automated (if configure is located in SDCard root directory) and performed with touchscreen turned off. After reboot touchscreen will be turned on and the installation process will be continued. At the end of the update process you'll get installed software version on the screen along with reboot request. Confirm reboot. Device will reboot in ordinary mode with SU and BusyBox properly installed. Enjoy!
In contrast to G1345 model SliPer ModRecovery hasn't been saved for further use in G1355 model. Why?
This is done intentionally to provide users with opportunity to roll back the changes made by G1355 RootROM.
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846
--------------------
ROMs and ModRecoveries for other Gigabyte Dual-SIM Android phones:
[ROM][RECOVERY]SliPer ModRecovery + G1310 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1315 RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1317D RootROM
[ROM][RECOVERY]SliPer ModRecovery + G1345 RootROM
Click to expand...
Click to collapse
Hi SliPer -
I have cooked a CWM recovery for G1355 to overcome the restrictions and to provide the users with an interface they've always liked
http://www.mediafire.com/?a5ldlcojf8usakh
If you like it you could move it to the OP giving credits - I have to give you credit tough because I based my initrd (ramdisk) on yours which you have cooked for G1345
Note: Initially the recovery won't allow the user to select any menu item - to map the "power" button as a selection key keep clicking VOL+ until a message stating that "Back menu button enabled".
Thanks,
~Brightidea

It's not a very good idea to use CWM Recovery for G1345 here, as G1355 has no select (camera) button. However the trick you've mentioned to overcome this works well. I've fixed some bugs in CWM 5.5.0.4, but have got little free time to finish this cleanup. But I'll do it as soon as possible.

sliper123 said:
It's not a very good idea to use CWM Recovery for G1345 here, as G1355 has no select (camera) button. However the trick you've mentioned to overcome this works well. I've fixed some bugs in CWM 5.5.0.4, but have got little free time to finish this cleanup. But I'll do it as soon as possible.
Click to expand...
Click to collapse
Agreed - I have patched the program "recovery" inside the CWM image so that the default is to have the back menu button activated.
http://www.mediafire.com/?crgo39boamtf0qa
This should serve as the only CWM based recovery offered for this device until you release your fixed one
~Brightidea

[CWM][ROM][ROOT]ClockworkMod Recovery 5.5.0.4 + G1345 RootROM

ROM installation itself is performed by using SliPer ModRecovery, which has no Gigabyte digital signature check in contrast to the original recovery.
ClockworkMod Recovery (CWM Recovery) and G1345 RootROM. What are they?
By now flashing G1345 RootROM is the only way to obtain root privileges on Gigabyte GSmart G1345 with the following ROM software builds:
0.56.4 build 1962.124.2931#EEU,
0.56.5 build 1677.124.2667#RUS,
0.56.5 build 1621.124.2855#Stellar,
0.56.6 build 1898.124.2952#CHT,
1.4.2 build 1970.124.2847#EEU,
1.4.3 build 1736.124.2969#WEU.
That's because no known exploit works on these builds.
Refer to CyanogenMod Wiki for more information about ClockworkMod Recovery. G1345 RootROM is a custom ROM for Gigabyte GSmart G1345/Mc Onsen MCG1345/Cherry Mobile Stellar smartphone with Dual-SIM support. Several versions of G1345 RootROM correspond to different builds, each designed for a specific region or reseller.
What are the differences between G1345 RootROM and stock ROM?
In general, a custom ROM may differ from a stock ROM in everything ranging from the custom user interface to the modified kernel.
These are the differences of G1345 RootROM comparing to the stock ROM:
disabled BUILD_SW_PROJ check in the update script;
ROM is already rooted;
added BusyBox 1.19.4;
adbd runs with root permissions and "USB Debugging" is turned on for logging of the boot process by default;
G1345 RootROM preserves CWM on ordinary boot for further use (if stock ROM is installed, on each ordinary boot recovery partition is being rewritten with the original recovery image formed by patching original boot image with binary diff file recovery-from-boot.p).
Interface and kernel are derived from the original ROM.
Will I lose the warranty after installing G1345 RootROM by using SliPer ModRecovery?
Before calling for service install G1345 RootROM for your region, then install original ROM for your region. This is required to restore original ROM and recovery. After that clear cache and erase userdata by using stock recovery, remove SDCard from the device.
How to install CWM and G1345 RootROM?
WARNING! ALL userdata will be erased during G1345 RootROM installation process, so it's highly recommended to backup your valuable data!
You should install smartphone drivers if they haven't been installed yet.
It's important that you DON'T need root privileges to install CWM and G1345 RootROM by using SliPer ModRecovery.
There're 2 types of G1345 model. They differ in WLAN hardware being used in their design. The first type of G1345 uses AR6002 WLAN platform and these devices can be flashed with the following ROM software builds (each of these builds is located in the root directory of the corresponding ROM archive update1.zip/update.zip): 0.56.4 build 1962.124.2931#EEU, 0.56.5 build 1677.124.2667#RUS, 0.56.5 build 1621.124.2855#Stellar, 0.56.6 build 1898.124.2952#CHT, 1.4.2 build 1970.124.2847#EEU, 1.4.3 build 1736.124.2969#WEU. The second type of G1345 uses AR6003 WLAN platform and these devices can be flashed with the following ROM software builds (each of these builds is located in "la" directory of the corresponding ROM archive update1.zip/update.zip): 0.56.4_1 build 1963.124.2931#EEU, 0.56.5_1 build 1678.124.2667#RUS, 0.56.6_1 build 1899.124.2952#CHT, 1.4.2_1 build 1971.124.2847#EEU, 1.4.3_1 build 1739.124.2969#WEU.
WARNING! IN ORDER TO INSTALL CWM AND G1345 RootROM CORRECTLY YOU SHOULD KNOW THE TYPE OF YOUR G1345 MODEL (THESE TYPES ARE THE FIRST OR THE SECOND TYPE MENTIONED ABOVE)! You're able to check this by installing original ROM for your region/reseller and selecting "Menu"->"Settings"->"About phone"->"Build number":
Original 0.56.4_EEU ROM
Original 0.56.5_RUS ROM
Original 0.56.5_Stellar ROM
Original 0.56.6_CHT ROM (registration required)
Original 1.4.2_EEU ROM (registration required)
Original 1.4.3_WEU ROM (archive password required )
Download one of G1345 RootROMs (all of them include CWM Recovery 5.5.0.4):
G1345-CWM-0.56.4_EEU.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Cz/
G1345-CWM-0.56.5_RUS.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Russia/
G1345-CWM-0.56.5_Stellar.zip - based on the original ROM from Cherry Mobile official website http://www.cherrymobile.com.ph/products/smart-social/stellar (ONLY FOR THE FIRST TYPE OF DEVICES!)
G1345-CWM-0.56.6_CHT.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Taiwan/
G1345-CWM-1.4.2_EEU.zip - based on the original ROM from Gigabyte official website http://www.gigabytecm.com/Eng/
G1345-CWM-1.4.3_WEU.zip - based on the original ROM from Mc Onsen official website http://www.mconsen.com/mcg1345.php
Then extract configure (THIS FILE IS REQUIRED ON G1345 FOR THE AUTOMATION OF ROM INSTALLATON PROCESS, BECAUSE DURING THE FIRST PHASE OF THIS PROCESS TOUCHSCREEN IS TURNED OFF) and update1.zip/update.zip from archive to the root of SDCard which will be used to update ROM.
Download ModRecovery_BootScript.zip and unpack it somewhere to your PC. This is a "script" for booting up smartphone with recovery.img in fastboot mode. "Script" file flasher.bat itself is located in ModRecovery_BootScript folder. Extract recovery.img suitable FOR YOUR TYPE OF G1345 from previously copied to SDCard update1.zip/update.zip archive to ModRecovery_BootScript folder. If you've got the first type of G1345, you should extract recovery.img from the root directory of update1.zip/update.zip archive, otherwise if you've got the second type of G1345, you should extract recovery.img, which is located in "la" directory inside update1.zip/update.zip archive. Don't use recoveries located in cwm and la\cwm directories!
Then turn off your device, insert SDCard (with configure and update1.zip/update.zip files located in SDCard root directory) into it, turn the device into fastboot mode by holding volume down button + power button until blue LED blinks once. Then connect the device to PC, wait until fastboot mode drivers will be completely installed and run flasher.bat. The first phase of installation process is automated (if configure is located in SDCard root directory) and performed with touchscreen turned off. After reboot touchscreen will be turned on and the installation process will be continued. At the end of the update process you'll get installed software version on the screen along with reboot request. Confirm reboot. Device will reboot in ordinary mode with SU and BusyBox properly installed. Enjoy!
In order to check whether you've got CWM Recovery properly installed, reboot in recovery mode by holding volume up button + power button until blue LED blinks 3 times. If you get the following screen, then CWM has been installed properly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Donations
All donations are strictly voluntary. But I really appreciate any help, because I've got some financial troubles now.
PayPal
Donate
WebMoney Transfer
Z135745021429
E301654453478
R160707042034
U897012425686
QIWI Wallet
9167226205
Yandex Money
410011384134846

Hi sliper123
Thanks a lot for your great job. I had the GSmart_G1345_V1.4.2_EEU rom and I put yours rooted rom G1345-CWM-1.4.2_EEU as easily as you said. Every thing was fine in first day but... after that my phone reboot 4-5 times per day apparently without reason.
Do you have any ideea?
Thanks.

gabitu13 said:
Hi sliper123
Thanks a lot for your great job. I had the GSmart_G1345_V1.4.2_EEU rom and I put yours rooted rom G1345-CWM-1.4.2_EEU as easily as you said. Every thing was fine in first day but... after that my phone reboot 4-5 times per day apparently without reason.
Do you have any ideea?
Thanks.
Click to expand...
Click to collapse
i guess its a rom issue. maybe u should clear cache or something not really sure. does this also happen on a non rooted rom? in my case when i used 1.4.2 rom i also experienced random reboots thats why i switched to 56.4 eeu rom and never experience any random reboots.
sorry for editing cant post on dev page due to minimum posts, but would like to know if there is a way to port ics of gsmart g1342 to our g1345?

This issue may be caused by the short circuit (some devices of this model have this issue and it's confirmed by Gigabyte; you may call for service if this happens not only on RootROM, but also on the original ROM) or may be derived from the original ROM, which has been used as a base for RootROM.

Problem solved
Hi guys and thanks for your interest.
I have read your post and after that I decided to switch the sims. Fortunately, I have not experiencing any reboot. Thanks again.

Hi, Your rom works fine, but how can I return to stock rom or how can I create my custom update files for CWM recovery???
May I Open update1.zip and delete all except META-INF, system and boot.img?
I need restore /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq to 245760, 122880 is bad. But I don´t know how....
Thanks for Your answer.

can i install the 0.56.5 update on my Stellar even though im using a 0.52 RUS Rom? please reply.
i think my phone is bricked
after i use the flasher bat the transfer went fine but after that the phone doesnt respond anymore.. also stuck at the Gsmart logo
Messaged Sent to sir Sliper
hello sir.. please help me.. i have a Cherry Mobile Stellar 1st Type of G1345
my phone got bricked when i tried your RootROMs... before i tried your RootROMs im in 0.52.2 RUS Rom so what i did is download the 0.56.5 RUS RootROMs then i prepared all the files that is needed like the ModRecovery Script and copied recovery.img of 0.56.5 RUS RootROM in the ModRecovery Folder.. i have installed all the drivers including the fastboot drivers... so here what happens.. i turned off my phone then go to fastboot mode.. then i opened flasher.bat and pressed Enter.. but after that nothing happens in my phone the LED just turned RED it doesnt boot and its not responding.. after waiting for 30 mins of black screen still nothing.. so i assumed that my phone is Soft Bricked.. and can you please help me recover from this brick sir? i have tried all update1 files all your RootROMs and even Stock ROMs but they cant be detected by the Recovery Mode so my phone is like a stuck right now gathering dust.. please reply to my message ASAP sir.. thanks !

[AOSP] 4.1.1 JellyBean for Herotab C8

DISCLAIMER I (or any contributor) cannot be held responible in any way for any sort of damage caused for using this ROM or its derivatives.
This is the AOSP-based Android 4.1.1 Jellybean ROM using custom kernel 3.0 for Herotab C8/Dropad A8/Haipad M7/iBall Slide and compatible tablets.
The Herotab C8 and its siblings are one hackable device; It supports Android 2.2, 2.3, 3.0, 3.2, 4.0, and 4.1. It runs on a single-core Samsung S5PV210 1Ghz Processor and 512mb RAM. Pretty low spec, however with the right tinkering it can be one powerful device.
What works:
Display
Hardware acceleration
Touchscreen (thanks violet's ft506 driver and przemo27 for figuring the alternate data format)
Audio\Microphone (thanks to Asure's CM7 build for audio HAL; and mg3100's details on kernel)
Wi-Fi (thanks to violet's ar6000 driver and jolocotroco for locating source for a wpa_supplicant8 dependency)
Bluetooth
Accelerometer (thanks to Asure's port of mango210 kernel)
Battery Indicator
USB Host
USB OTG
Camera
Market, GoogleApps
Root
What does not work:
HDMI
3G dongle
(NOTE This list is not exhaustive; this build is still a Beta and not intended to be a daily driver)
Steps for flashing (using script; this will make 512MB system, 256MB cache and 1GB data partition and erase your existing settings and apps):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these to the root of an external SD.
Download the attachment posted here and extract them to the root of the external SD. You should now see 6 files in the root of the external SD. (utscript, utscript_sd, utscript.sh, zImage.debug, zImage, rootfs.tgz).
Insert the SD card and boot your tablet using Menu+Power. This will flash your tablet.
Steps for flashing (using custom recovery):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these into a folder (path muwst have no spaces) in your external SD card.
Boot into custom recovery.
Go to "Advanced", then "Partition SD card". Select partition sizes (make sure system partition > 320MB) and wait for it to format the partitions. Existing settings and apps will be lost.
[You can skip this step if your tab's system partition is > 320 MB]
Now return to the main menu, and select "Flash ROM". Give it the path where you stored the ROM in step 1. Wait for it to flash the ROM.
Return to main menu and select "Shutdown".
Turn on your tablet normally, and enjoy!
Links:
http://www.embedupload.com/?d=85OERSGVNV (Embedupload)
NOTE: I didn't make this ROM. The guys over at slatedroid did it, so credits all go to them. But you can thank me for sharing

Custom recovery for herotab c8
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Download: https://github.com/namko/midRecovery/downloads
Source: https://github.com/namko/midRecovery
Key assignments:
Herotab C8/Dropad A8/Haipad M7/iBall Slide -- HOME to select, MENU/BACK to scroll
Coby 7024 -- HOME to select, POWER to scroll
Function list:
Flash ROM - Flashes the ROM on SD card (external or internal) located in a specific folder.
This does not erase 'data' partition. If you downgrade Android, make sure to erase the 'data' partition (or at least erase dalvik-cache from advanced menu) for maximum compatibility.
This does not repartition the internal SD, so if you want a different layout, make sure to change before flashing.
This flashes only the kernel (no other partition e.g. logo, recovery, boot arguments, boot loader)
Apply patch/update - Prompts you to select a patch/update to apply.
Wipe data/factory reset - Erases the 'data' partition. This is equivalent to doing a factory reset.
Wipe cache - Erases the 'cache' partition.
Backup/Restore - Create a new backup (system = firmware, data = your settings/apps) or restore a previously created backup. Essentially this is a NANDROID backup.
Partitions/Storage - To backup or flash individual partitions (e.g. logo, kernel, recovery, boot arguments, bootloader, etc.)
Advanced - To repartition the internal SD card, erase Dalvik-cache, view log, etc.
You can flash ROM (or apply updates) from .ZIP files as well; but it doesn't support the "standard" format because they sometimes contain executables that must be executed to properly apply the patch.

Fixes and patches
Kernel fix (just update it via recovery -> apply patch/update -> update kernel):
http://www.4shared.com/zip/M_ZcGiSF/zImage.html
Wifi Patch:
http://www.4shared.com/zip/3T9hUxnt/wifipatch.html
Here's a patch implementing changes suggested by jolocotroco. To apply this patch:
Extract the zip into your external SD card (anywhere)
Boot into recovery
Select "Apply patch/update"
Select the extracted file ("wifi.patch.tgz")
Reboot after applying patch
It is also possible to apply the patch using adb. Remember to stop WiFi first. This will apply the patch and reboot your device.
adb push wifi.patch.tgz /mnt/sdcard
adb shell
su
mount -o rw,remount /
mount -o rw,remount /system
stop wpa_supplicant
stop hostapd
tar xvf /mnt/sdcard/wifi.patch.tgz -C /
reboot
Click to expand...
Click to collapse

bump

don't work
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?

j.valeron said:
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?
Click to expand...
Click to collapse
It should work, what steps did you took to install the kernel?

Custom Recovery for C8/A8/M7
I nearly forgot this. Sorry.
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Click to expand...
Click to collapse
Github:
https://github.com/namko/midRecovery/downloads
BootExtRecovery:
http://www.4shared.com/zip/HxPitG3B/BootExtRecovery.html

mid recovery is not working on 8024
the recovery is not working on 8024, i have just a black screen...
please help
Sorry it is working...

Now we have Jelly Bean 4.2 form SlateDroid
Please refer for the following hyperlink
http://www.slatedroid.com/topic/42771-romcm101android-421-build-1/
[WORKING]
- Audio
- Video
- Wifi
- Touchscreen
- Most regular things
[NOT WORKING]
- Bluetooth
- 3G

awesome will try it on my dropad A8 its a shame hdmi is not working

[FIX]Repair White Screen, Bootloop, Soft Brick etc. the quick & dirty way

Most guides suggest reflashing stock rom for this, however that means you would have to re-root your device and also install a new recovery again. Any other data on your system will get lost as well.
I had a white screen problem with my SGA+ and according to a post about Indian and Chinese SGA+ phones, I needed to flash a European stock rom first before I was able to use certain roms (e.g. kk) at all. Because of various reasons Odin was not an option, so I had to use heimdall. With heimdall all partitions are flashed in sequence and you can choose which ones you want to flash. In other words, you can flash a partial stock without touching anything that would be flashed by your custom rom anyway.
Tested with a Chinese SGA+
This will flash all partitions that are not affected by custom roms and rooting.
Requirements:
heimdall --- (google for it. XDA's spam filter prevented me from posting the link, lol)
stock rom --- If your phone is an Indian or Chinese SGA+, choose an S7500XX rom. Mine was S7500XXNB1_S7500OXXNA1_XSK. Getting a relatively new rom is also not a bad idea.
zip, tar capable archive manager
Tutorial:
1. Unzip your stock rom.
2. Rename the xx.tar.md5 file to xx.tar.
3. Untar / extract the tar file.
4. Open a terminal and move to the extracted directory.
5. Put your SGA+ in download mode (turn your phone off and boot with Power+Volume down+Home pressed).
6. Connect your USB cable.
7. Check your partitions with heimdall (as root on Linux systems)
Code:
heimdall print-pit
This step should be optional, but it's always good to be on the safe side. Check if the partition names and image names correspond with the following table:
Code:
[B]partition[/B] [B]image[/B]
HIDDEN hidden.img.ext4
APPSBL appsbl
OEMSBL oemsbl
QCSBL qcsbl.mbn
CFG_DATA qcsblhd_cfgdata.mbn
8. Flash all five partitions with heimdall (as root on Linux systems)
Code:
heimdall flash --HIDDEN hidden.img.ext4 --APPSBL appsbl --OEMSBL oemsbl --QCSBL qcsbl.mbn --CFG_DATA qcsblhd_cfgdata.mbn
9. Re-flash your custom rom if necessary.