Related
Hello and thank you ahead of time for reading my thread. I spent a good deal of time searching for solutions in your forums but couldn't find anything related, so apologies if this is a repost.
I recently flashed my stock htc incredible with the leaked 2.2 ROM. While the flashing and installation of the new OS was successful, the phone itself is now acting really weird.
First, it is incredibly slow. There is a noticeable lag between the time I touch the screen and the time the touch actually registers. For example, to dial a number, I have to long press every button for it to register.
The second and much more annoying issue is the phone starts doing all sorts of things on its own. When sending a text message for example, all these keys are randomly pressed, it goes to the desktop, back to sending a text, inputs all these random characters, and sometimes frustratingly on occasion sends the text message on its own. This happens on and off and I haven't been able to figure out what triggers.
My question is, what can I do to fix it? I've reinstalled the ROM several times already and the problems appear every single time.
If I can't fix it, I'd love to go back to my previous stock rom and just wait for HTC's update.
Your help is greatly appreciated it.
Thanks.
have you cleared data and cache? do you have clockworkmod recovery install? please go through all the steps you went through to install the 2.2 leak
If ur rooted then u have clockworkmod installed...you should do a factory reset thru clockworkmod and wipe all data and cache ...
Then after that perhaps try a good and stable ROM ..
Wow thank you for such a prompt response.
I followed the steps in this thread:
[ROM]Leaked Stock 2.2 with Sense [LEAKED ROM - SOME BUGS!!]
(it's on the development front page, I would post a link but since I am a new member I am not allowed to).
In summary, I first updated to Radio version indicated in that thread (version 2).
I then ran unrevoked 3 which installed clockworkmod recovery. Then, I did a wipe. After, in the recovery screen I installed from the zip file of the mod that was in my SD card.
This is all I have done to date.
gxs1 said:
Wow thank you for such a prompt response.
I followed the steps in this thread:
[ROM]Leaked Stock 2.2 with Sense [LEAKED ROM - SOME BUGS!!]
(it's on the development front page, I would post a link but since I am a new member I am not allowed to).
In summary, I first updated to Radio version indicated in that thread (version 2).
I then ran unrevoked 3 which installed clockworkmod recovery. Then, I did a wipe. After, in the recovery screen I installed from the zip file of the mod that was in my SD card.
This is all I have done to date.
Click to expand...
Click to collapse
Okay...good to go.
You should boot into recovery aka clockworkmod...
Then do factoryreset wipe cache and data...
And I would recommend u install a ROM that u would like and u should be fine.
if ya like sense do skyraider....if ya like vanilla do CM6 test 8....and ya should be okay
If ya get stuck feel free to pm me and I can give u my Gtalk and can help furthur if ya need.
Cheers
I was having this problem too. I solved it by cleaning the screen and making sure my hands werent sweaty before use. I think thays why it didnt register the touch
Sent from my ADR6300 using XDA App
jdkoreclipse said:
I was having this problem too. I solved it by cleaning the screen and making sure my hands werent sweaty before use. I think thays why it didnt register the touch
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
These were my thoughts too initially but I've checked and double checked and cleaned the screen thorouhgly.
gxs1 said:
These were my thoughts too initially but I've checked and double checked and cleaned the screen thorouhgly.
Click to expand...
Click to collapse
With an eyglass cleaninn cloth? That worked for me.
I first came across the problem while testing the rom i made, jdfroyo, so initially thought it was my rom. I wiped my hands (which were sweaty) and then thoroughly cleaned my phone off. I havent had issues since.
Sent from my ADR6300 using XDA App
gxs1 said:
These were my thoughts too initially but I've checked and double checked and cleaned the screen thorouhgly.
Click to expand...
Click to collapse
I have heard that cleaning screen with a certain product (don't remember if it was like soap or alcohol) is not recommended as it leaves an almost invisible layer and can send it to that whacko stage of doing weird stuff. Double check on that... Otherwise, I am with the others > Wipe data/cache > then do a ROM re-flash.
tats_06 said:
I have heard that cleaning screen with a certain product (don't remember if it was like soap or alcohol) is not recommended as it leaves an almost invisible layer and can send it to that whacko stage of doing weird stuff. Double check on that... Otherwise, I am with the others > Wipe data/cache > then do a ROM re-flash.
Click to expand...
Click to collapse
You are very very right!
The screen is not his issue...noobness is jke ...I am helping him on Gtalk ..
Cheers and Olta u are far from ur home
Hi,
Thanks all for your help. And thanks to acid for helping me out on gtalk.
After trying several different ROMs, my phone continues to be really laggy. For example, I can type an entire word in the keyboard before it appears on the screen, and usually only the first few letters register.
I think my screen is just malfunctioning and it happened to coincide with the day I flashed my phone so I am just going to do a warranty exchange.
Thanks again everyone!
First of all, I am sorry for posting this here, but I am kind of in a bind, and hope someone can help me out..
EVO, rooted with new unrevoked, running stock everything, on a mac
I downloaded and installed LCD Density Changer today, and changed my number form 240 to 200, as everyone suggested.
When I rebooted, my boot screen started, but then the display went blank, and I keep hearing the Sprint music, but the phone's display wont come up..
I can get into recovery mode, so I am thinking of just doing a wipe data/factory reset, and starting all over, which wont be a problem, since I am all backed up.
someone suggested doing an ADB push, but I am on a mac, and cant find detailed instructions on how to do that..
Can someone give me a idea on which way to go?
I am fine with wiping data/factory reset, if it gets my phone started again..
Again, sorry if I posted this in the wrong place, but I know there are some great people here that will give me some direction
thanks so much!
i don't know what this has to do with development... but restore the backup that you made before you did the patch. didn't backup? wipe.
yup... no back up... shame on you..
your only choice is to wipe.
i dont know why people use this app, just edit the build.prop file yourself with rootexplorer or what ever app you have that can browse and edit the phones files.
Depending on what ROM you're running, you may also have to option of simply flashing it again without wiping. This would revert your build.prop and keep your installed apps and settings provided the updater-script in the ROM doesn't format /data/. I would try this before you go all out and wipe everything.
I really recommend you get ADB set up.
good news; got it to work with a zip file that a great member of this board gave to to flash; sorry if this post was placed in the wrong spot, and mods you are welcome to delete /lock it now..
BTW, doing a nandroid backup IMMEDIATELY!
you guys are the best, and SHAME on me for not doing that the minute I was rooted...
illogic6 said:
Depending on what ROM you're running, you may also have to option of simply flashing it again without wiping. This would revert your build.prop and keep your installed apps and settings provided the updater-script in the ROM doesn't format /data/. I would try this before you go all out and wipe everything.
I really recommend you get ADB set up.
Click to expand...
Click to collapse
can you do ADB on a mac computer?
thanks
wase4711 said:
can you do ADB on a mac computer?
thanks
Click to expand...
Click to collapse
If your Mac is of the Intel-based flavor, yes.
http://developer.android.com/sdk/index.html
illogic6 said:
If your Mac is of the Intel-based flavor, yes.
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
thank you, it is an Intel!
I appreciate the link
Hey guys. I have a problem and not sure how to go about this. My Evo was at 2.2 rooted for a long while and all of a sudden it started acting up. It would always freeze and had to be rebooted constantly. So I had a back that I went back to successfully but it is at 2.1 now (Baseband 2.15.00.09.01)
Now I'm not getting the OTA update to 2.2. I go into HTC software update and it says no available updates for my phone.
So how do I get to 2.2 or 2.3 rooted?
FYI after going into bootlaoder and choosing Recovery, I get Clockworkmod Recovery. Is this normal?
You need to flash the stock rooted ROM for the latest OTA update. I would suggest trying out some different Roms, though. That's the best part of rooting.
And ClockworkMod is the most popular recovery for the Evo, so yeah that's probably right.
http://forum.xda-developers.com/showthread.php?t=838448
Sounds like the perfect time to throw CM7 on there and see what you think about AOSP Gingerbread.
blackroseMD1 said:
Sounds like the perfect time to throw CM7 on there and see what you think about AOSP Gingerbread.
Click to expand...
Click to collapse
You are speaking a different language to me lool. I'm new to this so I don't know exactly what your talking about or how to go about doing that.
nawaf88 said:
You are speaking a different language to me lool. I'm new to this so I don't know exactly what your talking about or how to go about doing that.
Click to expand...
Click to collapse
It's pretty easy actually. Once you have root again (if you don't already), go to http://mirror.teamdouche.net/?device=supersonic and download either the newest nighly (30) or RC2 to your memory card.
Boot into Clockwork and go to backup and restore, and choose nandroid backup or backup (I'm not using clockwork, so I don't know the exact verbiage). Once the backup is complete, do a full system wipe by clicking on wipe data/factory reset.
Once that is done, choose install zip from sdcard, scroll down to cm_supersonic_full-30.zip and select it. It will install and then ask you to reboot. Go ahead and reboot.
Once your phone is up and running again, you'll want to get back into recovery so that you can flash GoogleApps, which you can find here: http://goo-inside.me/gapps/latest/7/universal/.
You'll flash these just like you did CyanogenMod 7 a minute ago, although you will want to wipe your cache and dalvik cache (which is located under "advanced" in the Clockwork menu) first.
All you have to do then is boot back up, go through the walkthrough to set up your google account, and then you'll be running (close to) stock Gingerbread 2.3.
If you need any help, feel free to ask.
Awesome!!! Thanks blackroseMD1!! I'll give it a try when I get home from work tonight. I'm not rooted right now. The last time I rooted I used unrevoked because it was so easy. Would that be good enough to get the process rolling?
nawaf88 said:
Awesome!!! Thanks blackroseMD1!! I'll give it a try when I get home from work tonight. I'm not rooted right now. The last time I rooted I used unrevoked because it was so easy. Would that be good enough to get the process rolling?
Click to expand...
Click to collapse
I'd actually use the link that CheesyNutz posted up there. Universal Auto Root works better than Unrevoked, from what I've heard.
blackroseMD1 said:
I'd actually use the link that CheesyNutz posted up there. Universal Auto Root works better than Unrevoked, from what I've heard.
Click to expand...
Click to collapse
Ok thanks. I'll try that and will keep you updated. Hopefully I have enough time tonight to do this.
nawaf88 said:
Ok thanks. I'll try that and will keep you updated. Hopefully I have enough time tonight to do this.
Click to expand...
Click to collapse
Shouldn't take long. Probably a half hour, tops, not counting download times. Let me know if you have any issues, and I'll see what I can do to help.
blackroseMD1 said:
Shouldn't take long. Probably a half hour, tops, not counting download times. Let me know if you have any issues, and I'll see what I can do to help.
Click to expand...
Click to collapse
I really appreciate your help. I just bought a xoom so I want wireless tethering working on my evo.
So you're good to go now?
blackroseMD1...I just followed your instructions and I'm up and running on CM7. Wow its so different then what I had before. You are the man!!! Thanks a lot for your help and everyone elses input in this thread.
I was scared going in, but wow was it easy to do. Thanks again to everyone and the hard work you put in to provide us noobs with a great experience
nawaf88 said:
blackroseMD1...I just followed your instructions and I'm up and running on CM7. Wow its so different then what I had before. You are the man!!! Thanks a lot for your help and everyone elses input in this thread.
I was scared going in, but wow was it easy to do. Thanks again to everyone and the hard work you put in to provide us noobs with a great experience
Click to expand...
Click to collapse
Awesome! Glad to hear it man. Everyone should take an AOSP rom out for a spin at least once, and CM7 is the best one out there. If you have any questions about it, feel free to hit me up. Glad I could help.
blackroseMD1 said:
Awesome! Glad to hear it man. Everyone should take an AOSP rom out for a spin at least once, and CM7 is the best one out there. If you have any questions about it, feel free to hit me up. Glad I could help.
Click to expand...
Click to collapse
Yea it looks great and loving the change so far
One last question. Is there a tethering app built into CM7 or do I need to get wireless tether from the marketplace?
Edit...Nevermind I think I found it right underneath bluetooth settings
nawaf88 said:
Yea it looks great and loving the change so far
One last question. Is there a tethering app built into CM7 or do I need to get wireless tether from the marketplace?
Edit...Nevermind I think I found it right underneath bluetooth settings
Click to expand...
Click to collapse
Yeah, built in tethering works fine. Seems like you found it. Enjoy Gingerbread.
Many recommend wiping data/factory reset (which I know was suggested and you've done), but also cache and dalvik BEFORE flashing any new ROM. Also, with CM, is it not suggested that you use Format_All?
totalanonymity said:
Many recommend wiping data/factory reset (which I know was suggested and you've done), but also cache and dalvik BEFORE flashing any new ROM. Also, with CM, is it not suggested that you use Format_All?
Click to expand...
Click to collapse
I only started using Format All recently, and never had any trouble before that with just a factory reset. Different phones react differently though...
another question is voicemail is not working. I get a text message saying Android has sent younansprint voice message and to call a number. Then it has this long string of letters and numbers. So how do inset this up
nawaf88 said:
another question is voicemail is not working. I get a text message saying Android has sent younansprint voice message and to call a number. Then it has this long string of letters and numbers. So how do inset this up
Click to expand...
Click to collapse
Your best bet is to use YouMail, which is free in the market. It's a lot like Sprint's Visual VoiceMail that you have on Sense roms, but with more features. I use it, and I love it.
When installing FXP113 to my phone, I found that on bootup I would get an error on the phone process and I had no service. After trying a few different things, I finally found the solution: Install FXP112 first, then install FXP113 over it without wiping data. Here is a step by step tutorial on installing FXP113 on the R800x. It probably would work the same for all Xperia Plays.
Required: Rooted Xperia Play and unlocked bootloader.
Needed Files: FXP112 as modified by Chevyowner
FXP113 as modified by Chevyowner
Replacement build.prop file for R800x
Fastboot - Fastboot+ADB+Fastboot_Drivers.zip
Sony Drivers
Recommended: Boot into recovery and make a Nandroid backup before continuing.
1. Copy the files for FXP112 and FXP113 to your sdcard. You will need to access these from recovery.
2. Install Fastboot. Unzip the file into C:\fastboot.
5. 2. Extract the boot.img of your choice to the fastboot directory. You may use the one in FXP113, or DarkForest3.img or DarkForest4.img (available here.)
5. Enter into Fastboot Mode. - Turn off phone. Hold search button down. Plug in USB cable. The power light should be blue The first time you do this, you will be prompted for the fastboot drivers. They will be in C:\fastboot\fastboot drivers.
6. To flash the new boot image, go to a command prompt and change to the c:\fastboot directory. Then use the following command:
fastboot -i 0x0fce flash boot boot.img <----- the name of your boot image.
7. When finished, remove the usb cable. Power on the phone and enter into Recovery. On some kernels, you will press repeatedly the volume down button; on others, you will press repeatedly on the back button or possibly the search button.
8. You MUST clear Data, Cache and Dalvik Cache. It is also recommended by some people to clear the battery stats.
9. Install zipfile from sdcard. Select the FXP112 file first. Allow it to install and then reboot the phone. (I usually clear data, cache and dalvik again just to be sure.)
10. Activate your phone on the Verizon network.
11. Now shut down and reboot into Recovery again.
12. This time, clear ONLY cache and dalvik cache. Do NOT clear data.
13. Install zipfile from sdcard. Select the FXP113 file this time. Allow it to install and then reboot the phone.
14. Copy the build.prop file into /system. You may want to rename the current one first.
15. Reboot and enjoy! You should be up and running with full data, wifi access now.
re
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
FPlusPS3 said:
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
Click to expand...
Click to collapse
#10 There is no charge to activate the phone if you already have service. It's like dialing *228 and choosing option 1, only the system does it for you.
#14 Yes, you can just copy it to \system, but don't forget to change access to RW before pasting. You may also want to rename the old file first as a backup, although I never have.
Sent from my R800x using XDA
my phone gets stuck at the android screen after i flash fxp112
johnboyjr said:
my phone gets stuck at the android screen after i flash fxp112
Click to expand...
Click to collapse
What kernel did you use?
Did you clear data, cache and dalvik cache before you installed FXP112?
If yes, just for kicks, go clear it again.
Also, remember, the first boot after a clean install takes longer than normal.
Sent from my R800x using XDA
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
johnboyjr said:
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
Click to expand...
Click to collapse
OK. Well, if it were me, the next thing I would do is to flash back to totally stock and get that working. Then try it again.
Sent from my R800x using XDA
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
crono141 said:
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
Click to expand...
Click to collapse
I think it was just edited to identify the phone properly as an R800x. PaxChristos told me to use it when he helped me install FXP111 and I have used it ever since. I haven't had any issues at all with it, so you might give it a try if you're on Verizon.
Sent from my R800x using XDA
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
*22899 is the shortcut for activating service in case anyone wanted to just store it for future reference
-and you can also use flashtool to flash back to stock or flash a new kernel
*228 worked fine for me. semcsuite.apk won't show up in my app drawer. I moved it to /system/app and fixed permissions. Still not there.
Sent from my R800x using XDA
Wallrunner said:
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
Click to expand...
Click to collapse
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
re
Does Psxperia or XPERIA GAMEPAD games even work on cm9
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
FPlusPS3 said:
Does Psxperia or XPERIA GAMEPAD games even work on cm9
Click to expand...
Click to collapse
From what I have read... no. That is why I have not jumped ship to CM. Otherwise I would be there right now. So until they get the touchpads working I will wait, although I have also read they are working on creating from scrathc their own drivers for the touchpads as the current drivers now require SE framework...... so cross your fingers.
Nighty0 said:
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
Click to expand...
Click to collapse
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
agraceful said:
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
Click to expand...
Click to collapse
Yes, giving their release to us is amazing, but saying that camera works on changelog, and not even the basic apps like gtalk and camera works, this barely can be considered as working.
As a software engineer I label as a beta, not RC anything. beta is to fix stopper bug like this, RC is for the little annoyances lonely.
For example, my work friend installed another rom on their htc sensation, labeled as beta and all features works, with jagged areas here and there.
And yep, I know the Team FreeXperia is a one guy team
I'm happy with all this releases, only frustrated because the thing is being labeled as working, when not. So I made a report here to make sure another person doesn't make the same mistake as me.
netizenmt said:
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
Click to expand...
Click to collapse
actually this build.prop works better it lets Plants Vs Zombies and Asphalt 6 RUN and work
How do install install the custom rom and set up fastboot?
Hellions
all things related to x0xhellx0x rom's and other HellfireJelly tweaks / fixes / add-ons
So first off this is pretty much going to house the same information that the g2x guide that TOG565 and I did. Obviously this will be for the SGS3. The original post here.
This is the place where we ease the burden on HELL and utilize open source for its' intended purpose...to help one another for FREE! Kinda like kickin apple, windows, etc. directly in the balls. Please ask your questions regarding issues here. If we cannot figure it out, they will be forwarded to the master. While this is an open thread there are a few rules:
1.) Stop what you are doing and go thank HELL...we'll wait..... (if your out of thanks use the xda premium app, you get unlim thanks)
2.) READ!!!!! And when you think you've read enough....READ some more!
3.) No complaining about tweaks the DEV built into the ROM. More than likely it is just eye candy which is easily removed. Personally, most enjoy the eye candy and is what separates DEV's from each other. Remember, they do this for us for free and could easily dev their rom as they like it and share it with no one. If you do not like something, o.k. ill say it i.e. flames, just read up on how to change it.
4.) For specific issues regarding rom's daily driver performance or if you find something that has helped, please submit via xda PM to me so we can keep the thread clean and reader friendly. If you like certain themes, apps, apps that created an issue, etc. you can post here with screen shots. Let's open it up a bit but stay on task.
For the noobs, not a bad word, we were all there at one point too, please seek-out other threads for CWM / rooting issues. These have been addressed by some great dev's on here. Give them their due and seek-out the answers on their threads; thanking them appropriately.
Here we go........
HELPFUL HINTS:
1.) DO NOT use CWM mount/storage to load zip files onto your SD. There has been a known issue with CWM corrupting the files during transfer. Use a stick/adapter and load directly from PC. INSTEAD FOR THE SGS3 I RECOMEND TWRP FOR YOUR CHOICE OF RECOVERY
2.) Ensure you have at least 50% battery left
3.) DO NOT touch the Galaxy for AT LEAST for ten minutes after first boot. Allow the ROM to 'move in' before changing the furniture.
4.) Complete several on/off cycles BEFORE you report an issue.
5.) Reboot at least once daily so that things can get moved back to their proper spots after the party.
6.) UPDATE your apps when installing an updated rom!!!!! Apps are one of the biggest causes of issue's with new roms as the app dev's struggle to keep-up with the master. Worst case you have to uninstall and re-install some apps.
7.) SEEK your answer first...i.e. slow data - check your settings, is the proper one checked, cycle through them all to see if it repairs itself, etc.
8.) When in doubt wipe it out, fix the permissions and reboot
9.) Ensure you have updated super user or supersu and checked unknown sources under security in settings.
10.) If you have done it all and first boot isn't running right...do it over but skip Google load on first run. Follow through everything else, let sit, reboot then load. If you are still having issue's then, and only then, should you be asking for help.
11.) If all resources are exhausted and you are standing on a ledge....ask away but please, please include what you have done to your phone after ruining its' Virginesque state. i.e. ov'd, uc'd, donkey punched, v6'd, dropped in the toilet, changed kernels, etc. We use this info to compare with other known issues or to try and replicate your exception/process failure while "seeing" what the source of the issue is.
***These are just SUGGESTIONS - don't be the one moron who asks why it is so or that you've never done these and your phone could beat up my phone, etc. If you use them great, if you do not great, if you lit yourself on fire great........etc., etc.
x0xHELLx0x's SGS3 Rom's:
HellFire Jelly, TMOUS
http://forum.xda-developers.com/showthread.php?t=1904120
HellFire Jelly, ATT
http://forum.xda-developers.com/showthread.php?t=1971952
INSTALL GUIDE:
*****If you use a link here THANK the respective DEV's!!!!!!!!!!!!!!!!!!!!!!!!
*****ensure you have CWM, or TWRP installed and are ROOTED*****
search threads on how to's or if you are unsure
CWM Touch
http://forum.xda-developers.com/showthread.php?t=1766552
TWRP <- just basically use this. It’s really sweet!
http://forum.xda-developers.com/showthread.php?t=1771946
The Install:
1.) Backup your current setup to make sure have something to go back to thats stable just in case
2.) Download and transfer ROM zip & other file(s) to SD Card in Galaxy
3.) Power down, then power into recovery.
4.) Factory wipe with format of /system and the caches
5.) Flash Rom and fix permissions.
6.) Reboot
*****DO NOT touch the lil hellion no matter how he temps you for 10 minutes
*****If you notice after 10 minutes that you have no data connection, IMMEDIATELY reboot*****
7.) Set-up, reboot
8.) Enjoy
That’s it for now. Will add lots more later. Thanks to TOG565 for letting me liberate his words. Thanks to Hell for doing what he does. Thanks for all the devs who work tirelessly on XDA to provide us with such awesomeness!! And of course thanks end users just like you.
ADDONS / TWEAKS / MODS AND SUCH.
So first at bat we have Jblah's amazing page: Sig/Avatar/Wallpaper/Themes/Others] HellFire Rom
Yes its listed in the g2x forum and yes you can use any of the images there. Feel free and enjoy!! Dont forget to use that thanks button!
KERNELS
****If you notice an issue after flashing/installing these please go to DEV's page and present it there****
Ktoonsez -> [KERNEL][TMO][AOSP/Touchwiz][JELLYBEAN & ICS]
http://forum.xda-developers.com/showthread.php?t=1871946
morfic -> [DER KERNEL] Trinity GST - TMO [ICS/CM9/CM10]
http://forum.xda-developers.com/showthread.php?t=1777472
faux123 -> d2-tmo/att/vzw-ICS/JB[Linux 3.0.43]kernel for AOSP/AOKP/CM9/10 ROMs
http://forum.xda-developers.com/showthread.php?t=1777472
Log_Cats
Ok so sone folks have no clue how to get a log_cat to show errors or FC's, here is how to do it:
1. Grab your self a log_cat app such as aLogcat (free) - logcat or Log Viewer (logcat) or similar.
2. If your issue IS NOT CONSTANT REBOOTS then after installing one of the above apps or similar then open it up and attempt to do what you did to get the error or FC. Then go back to the log_cat app and export the file for us to view.
3. Edit the log_cat if your familiar to show the error or not if your unfamiliar.
4. If your issue is constant reboots then you need to plugin via usb to your pc and get the log_cat via adb or using an adb app for win or ubuntu such as Android Commander or Droid Explorer
5. Once log_cat is exported/gathered POST IT IN THIS THREAD. Dont matter how. Link it, use '[ code ] [ /code ]' (<- without spaces of course), or your choice just get us the info
ok so ima take this post to post a wicked tip to make your xda reading ability much better. Some peeps know, some dont.
So basically in the xda app via your pc click on your USER CP -> Edit Options -> Number of Posts to Show Per Page -> select 50.
In the xda android app go to (if your rocking the latest version btw) more -> settings -> Posts per page -> select 50.
I cant tell you how many times Ive read peeps complaining about having to go through hundreds of pages to read 10 posts at a time. Please do your self a favor and change the above two settings. You wont regret it.
after flashing the rom successfully im still not getting any data activation ive tried all three kernals and still not working
but when i flash back to wn rom it works fine
any idea?
thanks
sky14 said:
after flashing the rom successfully im still not getting any data activation ive tried all three kernals and still not working
but when i flash back to wn rom it works fine
any idea?
thanks
Click to expand...
Click to collapse
Did u flash gapps?
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
I loved your rom man. But my only issue was the battery. drain for 100% to 1% in 4 hours maximum. I had to go back to TW roms again.
NICEGYPT said:
Did u flash gapps?
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
I loved your rom man. But my only issue was the battery. drain for 100% to 1% in 4 hours maximum. I had to go back to TW roms again.
Click to expand...
Click to collapse
No worries.. the very first release can't an always be perfect. The beta for 1.1 I'm rocking now I'm getting at least 17hrs on it.
Sent from my SGH-T999 using xda premium
sky14 said:
after flashing the rom successfully im still not getting any data activation ive tried all three kernals and still not working
but when i flash back to wn rom it works fine
any idea?
thanks
Click to expand...
Click to collapse
So since this a guide thread and u didnt state the obvious, did u follow the guide? If so you shouldn't have those issues.. u need a full wipe before installing Hellfire Jelly.
Sent from my SGH-T999 using xda premium
error when flashing
Hopefully somebody on here can help me, sorry ahead of time if I'm doing something stupid.
I just rooted my t-mo sgs3 using the one-click samsung snapdragon tool kit. I got superuser, titanium backup works just fine. When trying to flash this rom (version 1.1) I did a full wipe, wiped cache, wiped dalvik, flash the rom and i get the following error message:
assert failed: getprop("ro.product.device") +== "
d2tmo" || getprop("ro.build.product") = "d2tmo"
E:Error in /sdcard/samsungHFJ1.zip
(Status 7)
Installation aborted
Any ideas why this will not flash? I tried downloading to the computer and transferring the file as well as downloading straight to the phone.
---------- Post added at 02:37 AM ---------- Previous post was at 01:47 AM ----------
Ok, figured it out. My recovery was bad so I changed to twrp and now its working great