Database Info

Rogers HTC Dream - froyo update

Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.

Bloodyskullz said:
Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.
Click to expand...
Click to collapse
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.

crz6662 said:
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.
Click to expand...
Click to collapse
I would say to try the ROM in my sig (the stock ROM)
works for g1 and 32B Magic

he is going to need the EBI1 kernel to go with the rom.

Ok I am reviving this thread because I want to make sure I am following the right steps in doing so. Don't want to mess this up.
Successfully rooted the phone following video I found in the second post of this thread. Can't link you to it because I am still a new member =S! I checked the radio version of the phone and it is 3.22.20.17. Which ROM is recommended?As I said, I just want to get rid of this terrible stock rom from rogers and put froyo (which in turn also allows me to get touch screen keyboard activated) on here.
Thanks in advance.

With that radio you will need to flash ebi1 kernels after you flash the roms.
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Sent from my HTC Hero using XDA App

asb123 said:
With that radio you will need to flash ebi1 kernels after you flash the roms.
Click to expand...
Click to collapse
Now you have more information in the link in your sig. Question: Can you re up the RS link you have there? Also, rooting the phone just means that you have the app called Superuser?
Now I get quite lost the moment you start explaining the options HTC Dream users have. Is there a recommended ROM to download for this phone considering its specs?
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Click to expand...
Click to collapse
Yes it is sad that rogers has done this. Do whatever they can to screw the consumers over. Just found out it is 1.5.

Any help on this?

Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?

Bloodyskullz said:
Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?
Click to expand...
Click to collapse
Think of what you need to do:
1) Obtain root access so that you can flash a new recovery
2) Replace recovery so that you can flash new SPL
3) Flash new SPL so that you can be more compatible with roms / kernels
4) Flash a new rom (IE/ Cyanogenmod 6), and a compatible EBI1 kernel (for instance, Brian Crook's ones on the Cyanogenmod website)
Without getting into huge detail, you do it in this order to prevent your device from being unable to boot / recover.

You can flash the new RADIO and SPL from here: http://forum.xda-developers.com/showthread.php?goto=newpost&t=831139
Along with that, you use the appropriate supported +14MB EBI0 kernel.
More RAM is good

Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?

Bloodyskullz said:
Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?
Click to expand...
Click to collapse
Andriod sdk has the adb component needed to initiate commands to your device from your computer. then you need the android windows usb drivers.after installing sdk to see if you have connection with your device, open console on your computer start>run>type cmd and hit enter at the prompt type adb you should get several lines back kind of an options menu. at next prompt type adb devices. if your device is recognized you will get back:
device XXXXXXXX (this will be an actual number).
if you dont get any devices back with your phone attached to usb then you probably need the driver. just google it.
as for flashrec I dont believe I used this. I used exploid to gain root and install 1.33.2005 spl

Where do I get the android driver for windows (7 64bit specifically)? Adb command aint working in my cmd.
So what do I do about flashrec? Man updating this thing is driving me nuts. So many unexpected curves.

I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)

beav_35 said:
I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)
Click to expand...
Click to collapse
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Build number 1.85.631.5.
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?

Bloodyskullz said:
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Click to expand...
Click to collapse
This doesn't mean that it can't find your phone, it means that it can't find the adb.exe.
Bloodyskullz said:
Build number 1.85.631.5.
Click to expand...
Click to collapse
That is a pre-911 build. Don't see too many of those any more. Rogers harassed everyone into updating.
Bloodyskullz said:
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?
Click to expand...
Click to collapse
http://www.bleepingcomputer.com/tutorials/tutorial76.html
http://forum.xda-developers.com/showthread.php?t=502010
http://www.youtube.com/watch?v=Z3SpI7m7mFI

Does the zip file for the android SDK make a difference if I can't install it through the .exe? It keeps saying that it doesnt detect the Java SDK when I try to install.

Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.

beav_35 said:
Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.
Click to expand...
Click to collapse
The only .exe file in the zip is the SDK Manager which isnt exactly an install.

I need an easier guide...

To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...

I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though

I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.

DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate

My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...

DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt

I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?

DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have

How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?

DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium

I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"

DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium

You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone

DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium

If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?

DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium

Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/

DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium

Is there perhaps any way to perform a ROM backup with ADB?

DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium

[Q] How to flash a rom after rooting

OK I apologize ahead of time for what is probably a ridiculously easy question for most.
The ATT 1X is my first android and this is the first phone that I've rooted.
I read for hours and followed the instruction to a T. I rooted, unlocked the bootloader and installed CWM.
I can get into Recover/Boot mode or whatever you call it on phone startup, I have the Super user icon in my files, but I have no idea what to do now.
I found a ROM that I thought was worth a shot (CleanROM 2.5) but I don't know what to do. I've read and researched for hours now and everyone's problems seem to be complicated but no one talks about this.
I downloaded the ROM to my computer but I don't know what to do with the files, I can't find a .bat file or anything to initialize it and I am stuck.
I've wiped the data and done everything in the steps but I'm stuck at actually installing it. I know I'm obviously doing something wrong but I feel like I'm very close to what needs to be done.
Any help is welcome, thanks

deblas66 said:
OK I apologize ahead of time for what is probably a ridiculously easy question for most.
The ATT 1X is my first android and this is the first phone that I've rooted.
I read for hours and followed the instruction to a T. I rooted, unlocked the bootloader and installed CWM.
I can get into Recover/Boot mode or whatever you call it on phone startup, I have the Super user icon in my files, but I have no idea what to do now.
I found a ROM that I thought was worth a shot (CleanROM 2.5) but I don't know what to do. I've read and researched for hours now and everyone's problems seem to be complicated but no one talks about this.
I downloaded the ROM to my computer but I don't know what to do with the files, I can't find a .bat file or anything to initialize it and I am stuck.
I've wiped the data and done everything in the steps but I'm stuck at actually installing it. I know I'm obviously doing something wrong but I feel like I'm very close to what needs to be done.
Any help is welcome, thanks
Click to expand...
Click to collapse
I recommend you check QA thread found in a sub forum under your devices section and you review the stickied post for ROM install or Google "android install custom ROM " (remove quotes). Too much info on this already to type it all back out here. Did you watch you tube newb video you agreed to have watched when getting an xda account?
Essentially you now made it so your phone has the ability via CWM Recovery to now boot to that to install ROM zip or continue to use rooted stock ROM (how you flashed that zip for superuser is baasically same as how you flash a cwm compatible ROM zip (MOST but not all ROMs)) which with SuperUser can now run privelleged code if it is made to or requires it to run.
Sent from my SGH-T989 using Xparent Green Tapatalk 2

Thanks. I know this must seem so stupid, but I've been searching this forum, google, youtube and pretty much everything else for how to do this and I get it all and understand what's happening.
I just don't know where to put this ROM (which folder) to get it to install.

deblas66 said:
Thanks. I know this must seem so stupid, but I've been searching this forum, google, youtube and pretty much everything else for how to do this and I get it all and understand what's happening.
I just don't know where to put this ROM (which folder) to get it to install.
Click to expand...
Click to collapse
So after all that searching you never came across instructions informing you to put the zip on your phones storage?
You should probably just hold off a bit on flashing anything then. Not being mean but it sounds like you are confused by the process and end result. Step back and do some basic checklisting.
Sent from my HTC One X using Tapatalk 2

Download the rom you want and DO NOT UN ZIP IT. THEN PLACE THAT ZIP ON PHONE STORAGE AND BOOT INTO YOUR CUSTOM RECOVERY . HIT INSTALL FROM SD CARD AND MAKE SURE THE ROM YOU DOWNLOADED IS LISTED BUT DONT FLASH YET. GO BACK THE THE MAIN SCREEN OF RECOVERY. NOW MAKE A BACKUP. WHEN THAT IS DONE GO BACK TO MAIN RECOVERY SCREEN AND HIT WIPE PHONE DATA AND THEN CONFIRM. THEN GO AND HIT CLEAR CACHE OPTION. THEN GO BACK AND GO TO ADVANCED AND CLEAR DALVICK CACHE. NOW YOUR READY TO FLASH. GO TO INSTALL ZIP FROM SD AND FLASH YOUR ROM. FIRST BOOT ALWAYS TAKES LONG AFTER FLASHING A NEW ROM :thumbup:
Sent from my HTC One X using XDA

Pirateghost said:
So after all that searching you never came across instructions informing you to put the zip on your phones storage?
You should probably just hold off a bit on flashing anything then. Not being mean but it sounds like you are confused by the process and end result. Step back and do some basic checklisting.
Click to expand...
Click to collapse
Been posting on the internet for decades, don't worry about being mean. I'm here to learn. I rooted, unlocked the bootloader and installed CWM so that I could take advantage before the phone asked me to update the software to the 1.85 version.
My phone works fine now, and I did everything correctly which is what I was setting out to do. I'm in no rush to flash a ROM, but now that I'm ready I'm itching to try it out.
Driggity420 said:
Download the rom you want and DO NOT UN ZIP IT. THEN PLACE THAT ZIP ON PHONE STORAGE AND BOOT INTO YOUR CUSTOM RECOVERY . HIT INSTALL FROM SD CARD AND MAKE SURE THE ROM YOU DOWNLOADED IS LISTED BUT DONT FLASH YET. GO BACK THE THE MAIN SCREEN OF RECOVERY. NOW MAKE A BACKUP. WHEN THAT IS DONE GO BACK TO MAIN RECOVERY SCREEN AND HIT WIPE PHONE DATA AND THEN CONFIRM. THEN GO AND HIT CLEAR CACHE OPTION. THEN GO BACK AND GO TO ADVANCED AND CLEAR DALVICK CACHE. NOW YOUR READY TO FLASH. GO TO INSTALL ZIP FROM SD AND FLASH YOUR ROM. FIRST BOOT ALWAYS TAKES LONG AFTER FLASHING A NEW ROM :thumbup:
Click to expand...
Click to collapse
This is the process as I understand it and as stupid as it sounds, I'm hung up on where in phone storage to place the zip file of the rom. I don't see a storage folder, an SD folder, nothing that seems obvious and nothing that is in any of the things I've been reading or watching.

deblas66 said:
Been posting on the internet for decades, don't worry about being mean. I'm here to learn. I rooted, unlocked the bootloader and installed CWM so that I could take advantage before the phone asked me to update the software to the 1.85 version.
My phone works fine now, and I did everything correctly which is what I was setting out to do. I'm in no rush to flash a ROM, but now that I'm ready I'm itching to try it out.
This is the process as I understand it and as stupid as it sounds, I'm hung up on where in phone storage to place the zip file of the rom. I don't see a storage folder, an SD folder, nothing that seems obvious and nothing that is in any of the things I've been reading or watching.
Click to expand...
Click to collapse
Plug phone into computer. When prompted, select Disk Drive. On computer, browse to your computer, open the 'disk drive', and copy the zip there. THAT is your sdcard as seen by your phone.

Pirateghost said:
Plug phone into computer. When prompted, select Disk Drive. On computer, browse to your computer, open the 'disk drive', and copy the zip there. THAT is your sdcard as seen by your phone.
Click to expand...
Click to collapse
Seriously?
Wow I feel dumb. I was looking for a sub folder or directory specifically for storage and backup.
Thanks, I think that should be enough for me to do this tonight.

deblas66 said:
Seriously?
Wow I feel dumb. I was looking for a sub folder or directory specifically for storage and backup.
Thanks, I think that should be enough for me to do this tonight.
Click to expand...
Click to collapse
Yeah, some phones you may have to drag down notifications and tap USB mode or USB connected notification (it has standard USB icon and only appears when phone attached to computer). Then tap either USB storage mode or the button to enable USB drives. Then on computer just like a thumb drive it adds drive letter. Copy anything there that is /mnt/sdcard or /sdcard on phone. BE SURE TO EJECT DRIVES BEFORE AND TAP TO DISABLE USB ON PHONE IN THAT ORDER THEN UNPLUG FROM USB (failure to do so COULD result in data loss or corruption which you DO NOT want to happen to a ROM zip)!
Then boot in to recovery choose install zip from sdcard (not apply update from sdcard) as install from allows you to browse for any zip and install. Usually Vol up and down moves through menus and power or search button is enter. BE SURE THE ROM YOU DOWNLOAD IS SPECIFICALLY MEANT FOR YOUR DEVICE OR YOU COULD EASILY BRICK YOUR DEVICE. PLEASE REVIEW HOW TO RUN NANDROID BACKUPS AND RUN ONE BEFORE INSTALLING A DIFFERENT ROM.
I CAN NOT STRESS ENOUGH IF UNSURE DON'T PROCEED, BE SURE YOU RUN NANDROID BACKUPS AND ENSURE YOU FOLLOW INSTALL DIRECTIONS INCLUDED WITH YOUR ROM. ALSO, NEVER FORMAT EMMC (AKA INTERNAL SDCARD) IT ALMOST GUARENTEES A BRICKED DEVICE.
Sent from my SGH-T989 using Xparent Green Tapatalk 2

Wow that was easier than I thought.
Thanks for the help guys and sorry I missed such an easy step.
ROM installed.

deblas66 said:
Wow that was easier than I thought.
Thanks for the help guys and sorry I missed such an easy step.
ROM installed.
Click to expand...
Click to collapse
Is all good, and now you see why we were kinda scratching our heads wondering what was up a little . Glad we could help get you going though welcome to the world of custom ROMs. Please just be careful and always do backups and take it slow and read things 2x before even attempting once. While it can be easy to do it is also easy to accidentally brick your device (make it not work and have to be sent out for repairs).
Sent from my SGH-T989 using Xparent Green Tapatalk 2

[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.