Database Info

Rom manager.

I just downloaded Rom manager and it says i need clockwork recover installed. So i select it.
It gives me 4 choices.
1. Google nexus S
2. Google nexus S 4G
3. Samsung epic 4G
4. Samsung Galaxy S i9000
I have a Samsung Galaxy Captivate i896 (Rogers).
Which one do i select?
Im guessing the i9000 but i will await a reply!
Thanks.

Satstalker said:
I just downloaded Rom manager and it says i need clockwork recover installed. So i select it.
It gives me 4 choices.
1. Google nexus S
2. Google nexus S 4G
3. Samsung epic 4G
4. Samsung Galaxy S i9000
I have a Samsung Galaxy Captivate i896 (Rogers).
Which one do i select?
Im guessing the i9000 but i will await a reply!
Thanks.
Click to expand...
Click to collapse
You'll need option 5: None of the above.
Seriously, though, Rom Manager doesn't work that well for the Captivate. You'll be in much better shape if you do the things that Rom Manager normally handles by yourself.

jmtheiss said:
You'll need option 5: None of the above.
Seriously, though, Rom Manager doesn't work that well for the Captivate. You'll be in much better shape if you do the things that Rom Manager normally handles by yourself.
Click to expand...
Click to collapse
Really!!! Damn. I just bought Rom manager premium and was going to flash CyanogenMod on my phone and i found a video using rom manager and it seems a lot easier to do with it.
Im wondering if its because i changed the stock kernel so i could root the phone! I put the mtcareys-kernel on following a user post.
I bet that's why i does not recognize the phone.

Sorry to hear you spent the money, but maybe it's not entirely bad - Rom Manager works on a lot of other devices, and you can (I believe) transfer the program between devices.
Rom Manager might not recognize your device if the build.prop file was edited. That could be why it's showing the I9000 option.
As far as flashing CyanogenMod, it's fairly straightforward:
1. Flash a kernel that will let you use CWM Recovery (Corn Kernel should have it - Boog's kernel does too, and if you need Froyo, look for speedmod).
2. Once in Recovery, flash the CM update.zip (you may have to do this twice. If so, reboot to recovery again, and flash again).
That should get you to CyanogenMod.

jmtheiss said:
Sorry to hear you spent the money, but maybe it's not entirely bad - Rom Manager works on a lot of other devices, and you can (I believe) transfer the program between devices.
Rom Manager might not recognize your device if the build.prop file was edited. That could be why it's showing the I9000 option.
As far as flashing CyanogenMod, it's fairly straightforward:
1. Flash a kernel that will let you use CWM Recovery (Corn Kernel should have it - Boog's kernel does too, and if you need Froyo, look for speedmod).
2. Once in Recovery, flash the CM update.zip (you may have to do this twice. If so, reboot to recovery again, and flash again).
That should get you to CyanogenMod.
Click to expand...
Click to collapse
Clockwork mod recover. Is that the blue writing that comes up when you press and hold volume up and down and then power? If so then yes i do have that. I used that to root the phone with the corn kernel. Little green guy with a yellow corn a boot up!
I did down load the latest stable version of CM. (update-cm-7.1.0-Captivate-signed)
It says to Place the CyanogenMod update.zip file on the root of the internal memory. But then it says Select Install zip from sdcard.
Also where is the update.zip file? And does it go on the root of the sd card or the root of the internal memory!
I'm following the guide here. http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide#Before_you_do_anything_.E2.80.94_Make_a_backup

The actual name of the file you downloaded isn't that important. You can leave it with whatever it comes as. The "update.zip" they're referring to is the CM build you downloaded.
What you'll need to do is to copy the .zip file onto your phone Internal SD (the 13 GB partition) at a place you can find it easily. Once you've done that, reboot into CWM recovery (the menu with about 7-9 options, including "install zip from sdcard". It may have blue writing, depending on which build it is. If it only has 4 options, you don't have CWM recovery, but stock recovery.).
Once you're there, select the install zip from sdcard option, and navigate to where you put that zip file. Choose to install it and let it run.
If you're confused about whether you're putting an item on the internal sd card or not, you can connect your phone (including doing the "connect usb storage" dialog) and see what the drive sizes are. Once you know for sure which is your internal SD (13 GB), and which is your external SD (GB based on your card size), you can then re-label them in Windows (e.g. Internal SD and External SD). Those labels will usually stick pretty well.

oops
i was going thru my file manager to get rid of some old downloads and files and i deleted update.zip. i am now pretty sure it was for rom manager or cwm and remember seeing somewhere that it is supposed to stay on the phone.
how to fix this? download new rom manager?
I have noticed lately that when i want to reboot to recovery from rom manager to flash something it just reboots the phone.

bradddo said:
i was going thru my file manager to get rid of some old downloads and files and i deleted update.zip. i am now pretty sure it was for rom manager or cwm and remember seeing somewhere that it is supposed to stay on the phone.
how to fix this? download new rom manager?
I have noticed lately that when i want to reboot to recovery from rom manager to flash something it just reboots the phone.
Click to expand...
Click to collapse
1. Don't worry about the .zip
2. Don't use ROM manager for this device
Sent from my SGH-I777 using xda premium

That s what I was hoping. I don't know what I have actually used this for , I just thought I needed it. I Normally boot to recovery and flash from there. Can I delete it, or is there a purpose for it?
Sent from my SGH-I897 using xda app-developers app

The update.zip contained cwm and was used during the eclair 2.1 days. Now days to get access to cwm we have custom kernels and we can use the extended power button menu of dev roms, button combo, apps, etc. to boot into recovery...so yep, don't worry about keepin it, unless u plan on goin back to eclair.
Sent from my SGH-I897 using xda premium

[GUIDE]How to load CM9 on GSIII

**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.

Very informative. Would read again.
Sent from my Transformer Prime TF201

dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html

I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.

Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium

dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.

is the data not working due to the ril??

suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out

I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.

Will these same instructions work for the CM10 build that is in the server list?

17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium

neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.

17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium

i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?

seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.

Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.

17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium

DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.

HDC Galaxy S3 G9300 - ROOT

Has anyone got a root method that works for the HDC Galaxy S3 G9300?
Have tried Bin4ry v18 and another script but they didn't work.
The phone has JB 4.1.1. The Kernel is 3.4.0 dated Dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
Thanks for any help or advice.
Is now rooted, read on..

garyo said:
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
...
Thanks for any help or advice.
Click to expand...
Click to collapse
Me too. I've spent probably 6 hours today messing around with the 1.8 version script, on both windows 7 and Linux. It always fails the same place, with mount permission denied ... are you root?
I have other issues with the G9300 that I'd like to tackle, like WiFi range, but digging in requires root access. Here's hoping somebody smarter than I can find a way to root this thing.

wseverin said:
Me too. I've spent probably 6 hours today messing around with the 1.8 version script, on both windows 7 and Linux. It always fails the same place, with mount permission denied ... are you root?
I have other issues with the G9300 that I'd like to tackle, like WiFi range, but digging in requires root access. Here's hoping somebody smarter than I can find a way to root this thing.
Click to expand...
Click to collapse
Same here. I need root to build a custom CWM recovery.
Anyone has rooted phone that can help rip out the rom?

..

Finally. I've rooted my HDC G9300.
See my post in another thread here:
http://forum.xda-developers.com/showthread.php?t=1886460&page=165
My phone is now nicely rooted with no problems. But it's not an easy process.

wseverin said:
See my post in another thread here:
http://forum.xda-developers.com/showthread.php?t=1886460&page=165
My phone is now nicely rooted with no problems. But it's not an easy process.
The tutorial isn't clear about how to run Android Kitchen. In the Android Kitchen folder is a script called 'menu' that has to be executed by cygwin. Launch cygwin first with the .bat file in its install folder. Then, navigate to the 'menu' script. Hint: '/cygdrive/c/<path to Android Kitchen>/menu'
Nowhere does the tutorial say to copy 'Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip' onto your sd. You will want to do that before beginning the final recovery step.
Click to expand...
Click to collapse
Its great you figured out a root method, and thanks for sharing it :good:
I have just run through it on my phone and all has gone well until I got to where mobileuncle tools flashes the recovery.img. It needs Superuser access to do that and I don't have it. I am thinking it must be something to do with the Menu script you mentioned. How to you run that script? What is the command for it?
Thanks for any help!

Sounds like you're 95% there
garyo said:
I have just run through it on my phone and all has gone well until I got to where mobileuncle tools flashes the recovery.img. It needs Superuser access to do that and I don't have it. I am thinking it must be something to do with the Menu script you mentioned. How to you run that script? What is the command for it?
Thanks for any help!
Click to expand...
Click to collapse
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.

wseverin said:
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
Click to expand...
Click to collapse
Finally, you rooted the phone. Do you think you could upload the rom somewhere? Others can just download it and flash without going through the entire process. Good Job!!

wseverin said:
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
Click to expand...
Click to collapse
Hi - Yes you are right, I have created the recovery.img and transferred it to the phone.
Thanks for the tip that I don't need to use mobileuncle.. So I have booted up into CWM and have the su-superuser-busybox zip on my sd card. Trouble is CWM doesn't recognise the sd card and says E: unknown volume. That is strange because android sees it fine when the phone starts.
I am still wondering if my problem is from the the android kitchen part. I wasn't able to run android kitchen. I think I better run through the process again. How did you bring up the 'menu' in kitchen? I ran cygwin first and then navigated to kitchens path and used /menu and also ./menu but just got an error message. Even dumped all of kitchens files into cygwins root directory in case I had messed up the navigation path but still got the same error message whenever I tried to run menu. How did you get it to run please?
Thanks for your help :fingers-crossed:

GT35pro said:
Do you think you could upload the rom somewhere? Others can just download it and flash without going through the entire process.
Click to expand...
Click to collapse
I have uploaded the recovery.img that I created here. Remember, because it works on my phone is no guarantee that it won't break yours. You use it solely at your own risk. Also, you will still need to use CWM to install the su+superuser+busybox zip from your sd.

Next problem - no 3G
Having the phone rooted, I've gone on to the next problem that has no ready solution.
That is, no 3G. I use the AT&T network in the USA. AT&T uses WCDMA on 850MHz and 1900MHz for their 3G service. The HDC G9300+ doesn't support WCDMA at 1900MHz, which is the band that AT&T uses most. Where I am (Phoenix AZ) there is only 1900MHz service, which means that I can't get any 3G. Only 2G "Edge".
The problem *might* be remedied through software - or maybe not. If the MTK6577 radio doesn't support 1900MHz in some hardware sense, then the game is over. But I doubt that for two reasons. First, from a marketing standpoint, the AT&T network is too big to just ignore when designing a generic platform like the MTK6577. Second, from a hardware standpoint, the transceiver frequencies are synthesized from one base oscillator through a set of on-chip frequency multipliers and dividers. If the MTK6577 can generate frequencies in the 2100MHz band it can almost surely generate frequencies in the 1900MHz band. What's required is a software driver that properly sets the multipliers and dividers.
My bet is that somewhere out there in the world there is a software driver for the phone's radio that can set the chip to work in the 1900MHz band.
Can somebody find that driver so that we can bundle it into a ROM for this phone? Or a tool to adjust the driver that's bundled with the phone?

Please tell me
garyo said:
has anyone got a root method that works for the hdc galaxy s3 g9300?
Have tried bin4ry v18 and another script but they didn't work.
The phone has jb 4.1.1. The kernel is 3.4.0 dated dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
thanks for any help or advice.
Click to expand...
Click to collapse
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone

wseverin said:
I have uploaded the recovery.img that I created here. Remember, because it works on my phone is no guarantee that it won't break yours. You use it solely at your own risk. Also, you will still need to use CWM to install the su+superuser+busybox zip from your sd.
Click to expand...
Click to collapse
Thanks for uploaded your recovery file. I thought I would try that before going through the process of redoing mine. This time it kicked straight into CWM without any sdcard errors, so was able to install the zip file. It is now nicely rooted and has been running for several hours, and as yet I have found no problems.
Great job and thanks for sharing your knowledge :good:

joneswilson02 said:
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
Click to expand...
Click to collapse
http://www.fastcardtech.com/goods.php?u=53399&id=8113
First time I purchased from them, found them very good and had no problems. Took about 15 days to get it. Considering there were xmas & new year holidays at the time it was pretty good.

How to root your HDC Galaxy S3 G9300+
For those wanting to root their HDC Galaxy S3 G9300+ phones follow these steps;
Download wseverin's 'recovery.img' from post #10.
Download my 'MT6577_Android_scatter_emmc.txt', 'su+superuser+busybox.zip', 'SP_Flash_Tool_v3.1224.01.rar' and 'MT657x_USB_Win7_Driver.zip' files that I have attached to this post.
Install the USB drivers to your computer if you don't already have them.
Copy the su+superuser+busybox.zip file to your phones SD Card.
Run Flash Tool (Flash_tool.exe) in administrator mode.
Load my scatter file.
Next, backup your original recovery file (This is very important in case something gets messed up) Do this using the 'Read-Back' function. Select Hex and enter 0x1588000 for Start Address and 0x600000 for Length. Before clicking the Read Back button, shutdown your phone and remove the battery and USB cable. Next click Read Back, plug in the USB cable and replace the battery (But do not switch the phone on) The software will backup the file and come up with an OK window if successful.
Next flash your phone with wseverin's recovery.img. Do this from the Download tab in Flash Tool and tick the Recovery option. Before pushing the Download button you will also need to shutdown the phone, remove the battery and USB cable as above.
Next start the phone holding the volume-up + power buttons. This will boot the phone into CWM. Choose 'Install zip from sdcard', then 'choose zip from sdcard', navigate to the su+superuser+busybox.zip file and select yes to install it.
That's it! So easy!!
If you followed the steps correctly, after you reboot the phone it should have root access.. However, be warned that your phone could be bricked if something goes wrong or your phone is a different model, so do this at your own risk and backup your original first!
PS: thanks to wseverin for the modded recovery file and being the 1st to root this phone.

joneswilson02 said:
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
Click to expand...
Click to collapse
Do I detect a hint of cynicism?
It seems to be a decently built phone. The display is good; actually better resolution than many competing models. Fit and finish are as good as you'll get anywhere. The capacitive touch screen is just fine. GPS, WiFi, and Bluetooth all work well except that the WiFi range is a bit anemic. Software is pretty much standard Android Jelly Bean. I consider it worth what I paid for it, especially since I am not about to spend 3X that for a cell phone. Oh, and it actually makes and receives phone calls!

help me
Help me please, i've bricked my g9300+.
i need a rom.zip to flash with recovery or complete rom to flash with spflashtool.
help me!!!!

bersarak said:
Help me please, i've bricked my g9300+.
i need a rom.zip to flash with recovery or complete rom to flash with spflashtool.
help me!!!!
Click to expand...
Click to collapse
How do you have brick your phone?
With the garyo's guide?
Thanks
I have a G9300+ and I want to root it

root Star G9300+
garyo said:
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
Have tried Bin4ry v18 and another script but they didn't work.
The phone has JB 4.1.1. The Kernel is 3.4.0 dated Dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
Thanks for any help or advice.
Is now rooted, read on..
Click to expand...
Click to collapse
Hello,
First of all, please excuse my english...
I have a Star G9300+ smartphone with the same JB 4.1.1, same kernel (3.4.0 dated Dec 3 2012), same build number (e1920_v77_zlh_9p017_asx_20121203) than yours, but 1Gb RAM memory.
Could I use the same method to root my smartphone? How much RAM have yours?
Thanks!

xnicks said:
Hello,
First of all, please excuse my english...
I have a Star G9300+ smartphone with the same JB 4.1.1, same kernel (3.4.0 dated Dec 3 2012), same build number (e1920_v77_zlh_9p017_asx_20121203) than yours, but 1Gb RAM memory.
Could I use the same method to root my smartphone? How much RAM have yours?
Thanks!
Click to expand...
Click to collapse
Yes mine is also 1Gb RAM. I have read that HDC and Star are the same, however I don't know this for sure. This is where I purchased my phone;
http://www.fastcardtech.com/goods.php?u=53399&id=8113
Does yours look the same??
If yours looks the same you could always try it I suppose, but make sure you backup your phones entire ROM first. That way you can reinstate the original in case it doesn't work.

Flash image gui app

Hello, Im tired of connecting the phone to my laptop everytime im going to flash a new rom, because i have the new hboot so i have to flash the image thru fastboot first than flash rom. So i found this app on the market is called FLASH IMAGE GUI, theres no free version for this its around 3 bucks to buy. What this does is you can flash any kernel (image) from the phone instead of doing it thru fastboot. You might need to download a file manager like " astro file manager " for example, than look for the room on your phone open it with astro and find the boot image file. Once you do find it copy and create a new folder so you wont get confused, for example if you have joker rom copy the boot image and create a folder called something like "joker boot image" it will be easier to find once you lauch FLASH IMAGE GUI app. Launch flash image gui app and browse for the image, once find it open it and the app will give you a CAUTION warning, read it and after that click yes if you want to continue.Than click on the "flash image" button once you do it is going to give you another message saying that you will need to reboot the phone otherwise the android UI will be unstable, is going to give you three options. Click on the option to boot into recovery , once you are in recovery do the same steps as usual when install a rom and install the rom for the image that you flashed thru the FLASH IMAGE GUI APP. After that reboot and enjoy!! preety simple. KEEP IN MIND THAT I ONLY HAVE TRIED THIS GOING FROM CM10/AOKP TO A SENSE ROM, I HAVENT TRIED GOING FROM A SENSE TO ANOTHER SENSE ROM SINCE CM10/AOKP ARE ROOTED WITH THE OPTION TO GO INTO RECOVERY MODE.

You can view the video here by Team Nocturnal on how to use it : http://www.youtube.com/watch?v=EP5dX23aZ1M
Here is where you can get the free version that I have been using : http://forum.xda-developers.com/showthread.php?p=33463871
AT&T HTC One X
Andriod 4.1.1
Venom XL

Nice!! thanks man!!

ooopss!!! i dint know that some else posted this, im going to delete this thread

cal4877 said:
ooopss!!! i dint know that some else posted this, im going to delete this thread
Click to expand...
Click to collapse
Don't delete it please. Noobs like me may find this useful and it may save a few phones,
AT&T HTC One X
Android 4.1.1
ViperXL

ofcourse delete it, [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
you can also select the whole zip file and flashimagegui will copy the needed modules and flash the boot.img for you.
it will have problems with roms that stick the boot.img in other folders though, for those you will need to extract the boot.img though.

DvineLord said:
ofcourse delete it, [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
you can also select the whole zip file and flashimagegui will copy the needed modules and flash the boot.img for you.
it will have problems with roms that stick the boot.img in other folders though, for those you will need to extract the boot.img though.
Click to expand...
Click to collapse
Thanks for clearing that up. I have scrapped the free and bought the paid version from the market.
AT&T HTC OneX
Andriod 4.1.1
VenomXL

Venomtester said:
Thanks for clearing that up. I have scrapped the free and bought the paid version from the market.
AT&T HTC OneX
Andriod 4.1.1
VenomXL
Click to expand...
Click to collapse
the free xda version is the exact same as the market pay version. i bought it myself to give thanks, great app.

Thread closed as this information is already available as stated above.
XDA Moderator

Please help me ROOT LG H410?

I tried methods with Send_command.exe on LG H410 Smart Wine (Lilipop 5.1.1) and also receiving #FAIL from Send_Command . But LEAVE command is working fine and restarts the phone. How can I make root?
Firmware v10c:
drive.google.com/file/d/0BzNfkgQOM0SudTREcFNQZTNhdmc/view?usp=sharing
opensource firmware v10a:
drive.google.com/file/d/0B2QhEXa2ySgkX21kZzl0TC1FQlU/view?usp=sharing
if it help

Soft-Man said:
I tried methods with Send_command.exe on LG H410 Smart Wine (Lilipop 5.1.1) and also receiving #FAIL from Send_Command . But LEAVE command is working fine and restarts the phone. How can I make root?
Firmware v10c:
drive.google.com/file/d/0BzNfkgQOM0SudTREcFNQZTNhdmc/view?usp=sharing
opensource firmware v10a:
drive.google.com/file/d/0B2QhEXa2ySgkX21kZzl0TC1FQlU/view?usp=sharing
if it help
Click to expand...
Click to collapse
If not all but most except maybe certain samsung devices are easily rootable without PC by using kingroot v4.5.2 latest version, download and install and sit back watch successfully root your phone
Sent from my SM-N920C using Tapatalk

[email protected] said:
If not all but most except maybe certain samsung devices are easily rootable without PC by using kingroot v4.5.2 latest version, download and install and sit back watch successfully root your phone
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I tried kingroot kingoroot and other similar techniques, none of them does not give the desired result.

Soft-Man said:
I tried kingroot kingoroot and other similar techniques, none of them does not give the desired result.
Click to expand...
Click to collapse
Have you tried latest version of kingoroot?
Also try PC and android version of v/iROOT
Sent from my SM-N920C using Tapatalk
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
There's also rootgenius PC version that have worked #!
Sent from my SM-N920C using Tapatalk

[email protected] said:
Have you tried latest version of kingoroot?
Also try PC and android version of v/iROOT
Sent from my SM-N920C using Tapatalk
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
There's also rootgenius PC version that have worked #!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Yes, tried. Not working. and where is samsung if LG?

http://www.kingoapp.com/root-tutorials/how-to-root-lg.htm
That's what I've used for mosT LG and never failed, you're first to say this ain't working, always try latest version of way ever you're using
Sent from my SM-N920C using Tapatalk

[email protected] said:
that's what I've used for mosT LG and never failed,
Click to expand...
Click to collapse
in this case it does not work
Yes, of course I use the latest versions of software

Soft-Man said:
I tried methods with Send_command.exe on LG H410 Smart Wine (Lilipop 5.1.1) and also receiving #FAIL from Send_Command . But LEAVE command is working fine and restarts the phone. How can I make root?
Firmware v10c:
drive.google.com/file/d/0BzNfkgQOM0SudTREcFNQZTNhdmc/view?usp=sharing
opensource firmware v10a:
drive.google.com/file/d/0B2QhEXa2ySgkX21kZzl0TC1FQlU/view?usp=sharing
if it help
Click to expand...
Click to collapse
Have you found a solution to your problem yet?
BTW, which version of the smartphone are you using? Europe/USA/carrier etc... ?

hey there soft-man !
obviously you found a a solution to install twrp on the h410, i saw it at http://4pda.ru/forum/index.php?showtopic=682101
could you please make a small tutorial in english and post it here ?
.. and reupload the tools we need to install twrp (LG_H410__Flash_Recovery.rar) << dead link
i already installed root and crashed my device by deleting to the wrong system app ... reinstall fw via lg flash tool fails
now twrp is my only hope !
thanks a zillion !!!

If there is a chance to root the LG h410, i totally supportswitcher's request for a english tutorial and new links for the tools needed. Thanks in advance

+1 for translation from Russian forum

once again: does anybody here managed to (re)flash the firmware on the h410 ?
my device is trapped at the android logo ;(
what i did is unsuccessfully tried to flash a *.kdz with flashtool 2014. lg bridge is aborting update and lgup shows device not supported
download modus is available but cant connect device via adb.
any help is greatly appreciated

Ok, after spending a few hours on my LG smart wine (EU version) and with the help of the guys on 4PDA, here is my little how to for rooting our LG H410:
Beware, I'm not responsible if anything goes wrong with the manipulation on your phone and all this was only possible thanks to the people over at 4PDA.ru, thanks to them! I am/was on firmware V10e-EUR-XX official.
1) Use Kinguser apk to get root on your device (don't worry, you can uninstall it later through superSU).
2) Install Flashify and backup your current/original recovery. You'll need to be root to use flashify, that's why we need #1) first. You'll find flashify on the play store.
3) Install TWRP recovery either through flashify or with flash.bat found in LG_H410__Flash_Recovery.rar (this one will be russified, but you can always go through flashify and install the english version afterwards !EDIT!: Since the file was too large to upload, I took the russian recovery.img out of the zif archive. You'll will have to unpack it, copy the recovery_en.img provided after having renamed it to recovery.img, and it should work).
4) Install latest stable or Beta superSU.zip (search google for the official maintainer/version and copy it on your microSD card) from within TWRP.
5) Restart the phone
6) If you open superSU, it will ask you possibly to update the binaries and then to uninstall the other software that might interfere (it's Kinguser). So just say yes and it will take care of everything.
7) (optional) If you're like me needing more storage place on your device, install Link2SD from the play store. If I'm right, you'll need to have a second partition on your SD card (Ext4 file system), after the Fat32 one, to be able to move your apps to the SD card with Link2SD. I even bought the Plus version in order to be able to move the whole app.
You can use MiniTool Partition Wizard Free to set your partitions on th card. Add the new primary partition in Ext4 AFTER the Fat32 one, otherwise windows won't recognise your card.
I forgot to backup my stock recovery before flashing the new one, but all should be fine for you if you do it in the order above.
You have to unpack recovery_en.zip and flash the .img you have in the folder, don't flash the zif through TWRP, it won't work. And don't forget to rename it to recovery.img if you use it within the LG_H410__Flash_Recovery folder.
Once again, thank the people who did the job over at 4PDA, especially Soft-Man for trying out things, they did all the work. I'll try to attach the files needed here.
Hope it will help someone, have fun with your phone!

Sure it is interesting .... just one wuestion ... what about if i stop after step 1? If kinguser gets me root i personally don't have any need to go further ...

Of course you can, if you want to keep the official recovery (probably better if you want to be able to install official OTA updates).
I would still install SuperSU through flashify though (I think you can do so without having a modded recovery installed, but I'm not sure), and get rid of Kinguser the way I described it. Thing is I don't really trust those rooting apk, you never know what they install and what they keep track of on your phone... Not sure what's left of it when you uninstall it either.
Tell us how it worked for you.

:laugh:
Vuche said:
Ok, after spending a few hours on my LG smart wine (EU version) and with the help of the guys on 4PDA, here is my little how to for rooting our LG H410:
Beware, I'm not responsible if anything goes wrong with the manipulation on your phone and all this was only possible thanks to the people over at 4PDA.ru, thanks to them! I am/was on firmware V10e-EUR-XX official.
1) Use Kinguser apk to get root on your device (don't worry, you can uninstall it later through superSU).
2) Install Flashify and backup your current/original recovery. You'll need to be root to use flashify, that's why we need #1) first. You'll find flashify on the play store.
3) Install TWRP recovery either through flashify or with flash.bat found in LG_H410__Flash_Recovery.rar (this one will be russified, but you can always go through flashify and install the english version afterwards !EDIT!: Since the file was too large to upload, I took the russian recovery.img out of the zif archive. You'll will have to unpack it, copy the recovery_en.img provided after having renamed it to recovery.img, and it should work).
4) Install latest stable or Beta superSU.zip (search google for the official maintainer/version and copy it on your microSD card) from within TWRP.
5) Restart the phone
6) If you open superSU, it will ask you possibly to update the binaries and then to uninstall the other software that might interfere (it's Kinguser). So just say yes and it will take care of everything.
7) (optional) If you're like me needing more storage place on your device, install Link2SD from the play store. If I'm right, you'll need to have a second partition on your SD card (Ext4 file system), after the Fat32 one, to be able to move your apps to the SD card with Link2SD. I even bought the Plus version in order to be able to move the whole app.
You can use MiniTool Partition Wizard Free to set your partitions on th card. Add the new primary partition in Ext4 AFTER the Fat32 one, otherwise windows won't recognise your card.
I forgot to backup my stock recovery before flashing the new one, but all should be fine for you if you do it in the order above.
You have to unpack recovery_en.zip and flash the .img you have in the folder, don't flash the zif through TWRP, it won't work. And don't forget to rename it to recovery.img if you use it within the LG_H410__Flash_Recovery folder.
Once again, thank the people who did the job over at 4PDA, especially Soft-Man for trying out things, they did all the work. I'll try to attach the files needed here.
Hope it will help someone, have fun with your phone!
Click to expand...
Click to collapse
Thank you very much.
When I work as the indicated method from you, root has come. (LGS01 of a Japanese local edition of H410).
By the way I can't start bootloader moode in LGS01, can you start it in H410?
When it's done, please tell me the way which can be done.
I'd like to use LGS01 by a DIAG mode.
(I'd like to add a frequency.).

Vuche said:
Of course you can, if you want to keep the official recovery (probably better if you want to be able to install official OTA updates).
I would still install SuperSU through flashify though (I think you can do so without having a modded recovery installed, but I'm not sure),
Click to expand...
Click to collapse
Yeah, i get it. My goal is just to get root and being able to install titanium backup. No need for further modding. I will investigate about installing SuperSU through flashify with stock recovery.
:good:

still looking for a way to flash my bricked h410
..sorry to bother you guys, but where else to ask for help if not at xda ?

After finally reactivating my phone i like to share some bugs in stock firmware.
First of all LED notification: Is there a workaround for the blinking time, i find 15 seconds are much to long, i like to have 2 seconds. Tried some third party apps but the ideal solution would be by modyfing the stock app.
Second the T9: Its horrible ! Is there a way to switch it off ? By deleting the XT9. apk i totally messed it up and only have the numbers left.
Third of all, the keyboard .. Is there a good alternative with bigger (resizable) keys. Currently am using big buttons keyboard but am not really happy with it

I try to root LG H410 (EU version) but after installing Kinguser apk, root was not available so Flashify rapport an error about impossibility to access root.
My version of software is V10c-260-01