Related
I did quite a few searches about ROM's, Launchers, and other stuff. I have come to conclusion that I'll give CM7 a try. But currently I only know a few stuff, like, the CM7 will replace my stock ROM and I can choose AOSP to replace HTC Sense etc but I'm not sure if my GO Launcher will cross over to CM7. What about my apps? What about the apps placements on my home screens, would they be all reset or gone or what? I see a settings in GO Launcher that says it'll back up my GO Launcher configurations, would this restore my placements of apps on home screens? Also, I'm assuming the GO Launcher as the Desktop Dock apps for Windows and the CM7 as the OS of the computer. Am I assuming things right?
What's not working for HTC EVO 3D on CM7? I saw a video on youtube saying that the 3D video capturing doesn't work on CM7.
Regards
You're absolutely right. 4G and 3Ddo not work. But as development progresses, we're bound to be surprised.
Some widgets are ''Sense'' based so you might not see them cross over since cm removes sense. Apps should work.
I say dive in brother! Make sure to nandroid so that you can easily restore if you find its not your cup of tea.
kaphtc said:
I did quite a few searches about ROM's, Launchers, and other stuff. I have come to conclusion that I'll give CM7 a try. But currently I only know a few stuff, like, the CM7 will replace my stock ROM and I can choose AOSP to replace HTC Sense etc but I'm not sure if my GO Launcher will cross over to CM7. What about my apps? What about the apps placements on my home screens, would they be all reset or gone or what? I see a settings in GO Launcher that says it'll back up my GO Launcher configurations, would this restore my placements of apps on home screens? Also, I'm assuming the GO Launcher as the Desktop Dock apps for Windows and the CM7 as the OS of the computer. Am I assuming things right?
What's not working for HTC EVO 3D on CM7? I saw a video on youtube saying that the 3D video capturing doesn't work on CM7.
Regards
Click to expand...
Click to collapse
Essentially, when moving from any type of Sense based ROM to an type of AOSP based ROM, you will probably lose all your settings, including Wifi passwords, brightness preferences, google accounts sync'd to the device, etc.
On the spectrum of ROMs available, view Sense on one end and AOSP on the other. Some ROMs try to sit in the middle and have features of both, but they always have to pick either Sense or AOSP as the base.
Sometimes you can move between different sense based ROMs and keep your settings/3rd party applications and sometimes you can't. Same goes for AOSP based ROMs.
If you've ever used a google device, G1, Nexus One, or Nexus S, they run pure AOSP by default. CM7 will be fairly similar to that type of experience plus some CM7 "tweaks/goodies".
Making a nandroid, as suggested above, is probably the best way to backup everything currently on the device, in case you want to revert. It will also help provide confidence when testing out new ROMs knowing you'll be able to revert to a previous one if something goes wrong.
To save you some time and help provide information on the next step, once you've selected a ROM and kernel how to make sure they are loaded properly.
If you're using the HTC unlock method on your device, there are basically two ways to load the kernel:
I've answered this type of question a few times in other posts. I've edited my answer from earlier this morning to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Click to expand...
Click to collapse
Let us know if you have any other questions! Hope that helps!
Oh! So I have to choose a ROM (I chose, CM7), Sense or AOSP and ALSO a kernel? My main purpose of flashing a custom ROM is to improve my battery life, get more customization options and cooler effects, no lags.
My status right now is I have S-OFF with Revolutionary tool and only GO Launcher installed. Where do I go now? Install Sense or AOSP (which one do you recommend), I understand E3D comes with HTC Sense 3.0 if that's the same sense we're talking about in above posts. Then install CM7? Which one goes first?
PS: I'm going to follow this tutorial: http://www.phonedut.info/tutorial-install-cyanogenmod-7-cm7-on-htc-evo-3d/
Can you check for me if it's correctly written?
kaphtc said:
Oh! So I have to choose a ROM (I chose, CM7), Sense or AOSP and ALSO a kernel? My main purpose of flashing a custom ROM is to improve my battery life, get more customization options and cooler effects, no lags.
My status right now is I have S-OFF with Revolutionary tool and only GO Launcher installed. Where do I go now? Install Sense or AOSP (which one do you recommend), I understand E3D comes with HTC Sense 3.0 if that's the same sense we're talking about in above posts. Then install CM7? Which one goes first?
PS: I'm going to follow this tutorial: http://www.phonedut.info/tutorial-install-cyanogenmod-7-cm7-on-htc-evo-3d/
Can you check for me if it's correctly written?
Click to expand...
Click to collapse
since you have the revolutionary tool, you're all set. i read thru the guide and it seems good.
good luck! hopefully you enjoy cm7!
joeykrim said:
since you have the revolutionary tool, you're all set. i read thru the guide and it seems good.
good luck! hopefully you enjoy cm7!
Click to expand...
Click to collapse
One more thing, if you don't mind. In the tutorial, it says it's for CDMA. Mine is GSM. Is there a difference between the two? If you say, yes, I'll look for another tutorial.
kaphtc said:
One more thing, if you don't mind. In the tutorial, it says it's for CDMA. Mine is GSM. Is there a difference between the two? If you say, yes, I'll look for another tutorial.
Click to expand...
Click to collapse
Yea, that is a problem. As far as I've seen, there is no CM7 release for the GSM version.
A great location to look for GSM compatible EVO 3D ROMs will be on the EVO 3D GSM developer board.
My buttons won't work when i press them not exactly sure whats wrong but this began happening within the past few days. I've been running WTSB 3.5 latest update of 2.4 and Olympus Prime both of which use's a chad kernel which i'm not sure may or may not be the source of the problem. Can anyone offer any suggestions?
Selebrity said:
My buttons won't work when i press them not exactly sure whats wrong but this began happening within the past few days. I've been running WTSB 3.5 latest update of 2.4 and Olympus Prime both of which use's a chad kernel which i'm not sure may or may not be the source of the problem. Can anyone offer any suggestions?
Click to expand...
Click to collapse
By LED buttons I'm going to assume you're referring to the 4 capacitive buttons across the bottom, Home, Menu, Back and Search.
Never really heard of any software disabling these buttons, either intentionally or accidently but doesn't mean it couldn't happen!
Quick shorter term and temporary approach: boot into the custom recovery and see if their lights flash or they work at all in the custom recovery. I remember at one point during TWRP development we had the lights flashing on them. Not sure what kinda support ended up but you should be able to get some type of response to at least indicate the hardware is working.
Long but thorough approach:
Since you are running a custom ROM and kernel, I would suggest first reverting back to Stock and wipe /data and /cache.
If everything works on a Stock ROM and kernel, then you know it has something to do with either the custom ROM, custom kernel or a custom setting configuration. From a known working stock configuration, you can customize one piece at a time checking after each customization step to make sure the buttons work.
Ideally, the buttons will break after a specific customization step and you'll be able to narrow it down to that step and approach the appropriate developer with your results who will then be able to dig into their code and look at the issue.
Hope that helps!
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
I left my phone on the counter near the dish drainer and smoked the usb/mhl port. Another time, I filled the thing with crushed banana. I can charge the battery using an external charger (hasn't burned my house down yet), but can't use the usb port at all. So I set the phone aside for a while.
S-On, rooted, was running Scrosler's Cleanrom DE 1.4. I got tired of my wife's iPhone 4 and started using the ReZound again recently, but got myself into trouble flashing the clockworkmod recovery over my AmonRA and can't go back. I'm stuck on CarbonROM (used HTCDumlock) with no stability unless wifi and mobile data are disabled.
Is it possible to get AmonRA back (or at least restore the nandroid I made with AmonRA) without a usb? What about S-Off without any USB connection?
yimpierre said:
I left my phone on the counter near the dish drainer and smoked the usb/mhl port. Another time, I filled the thing with crushed banana. I can charge the battery using an external charger (hasn't burned my house down yet), but can't use the usb port at all. So I set the phone aside for a while.
S-On, rooted, was running Scrosler's Cleanrom DE 1.4. I got tired of my wife's iPhone 4 and started using the ReZound again recently, but got myself into trouble flashing the clockworkmod recovery over my AmonRA and can't go back. I'm stuck on CarbonROM (used HTCDumlock) with no stability unless wifi and mobile data are disabled.
Is it possible to get AmonRA back (or at least restore the nandroid I made with AmonRA) without a usb? What about S-Off without any USB connection?
Click to expand...
Click to collapse
Kind of a pickle without a working USB port...
You can not gain S-OFF without a working USB connection using any known (Juopunutbear, rumrunner, or firewater) S-OFF method, sorry. Although JTAG may be a possibility.
If Carbon is running and root is working, you could use Goo Manager to install TWRP, it has HTC Dumlock built in, and you could flash in Evervolv or something else more stable (later incarnations of Carbon caused me lots of issues as well). The backups are not compatible between Amon Ra, CWM, and TWRP though.
As far as getting Amon Ra installed without a working USB connection, it MIGHT be possible, but it is over my head... The real issue would be even if you did get it back on and restored your nandroid, being S-ON means you still need to flash your boot.img manually, even from a nandroid restore, which would be another issue altogether and probably highly difficult (if possible at all).
Although, if we are talking water damage and possible banana damage (did I really just type that?!?!) a different ROM may or may not help, this could all be a exercise in futility that one wrong move could brick you.
Hmmm. I did have the phone working well with CleanROM DE, so I know it's at least worth trying. I'm also not afraid of a brick seeing as what I have now is basically no better. Good point about the boot.img. I hadn't thought of that.
Carbon is working and moderately stable when wifi and mobile data are off. When I enable wifi, I tend to go into a boot cycle with 1-2s before reboot to disable it again. When enabling mobile data, I get frequent popups saying something like android.com.phone stopped working, and not data anyways. I do have a working recovery right now in CWM (up to date non-touch). But, I don't think that has HTCDumlock built in.
yimpierre said:
Hmmm. I did have the phone working well with CleanROM DE, so I know it's at least worth trying. I'm also not afraid of a brick seeing as what I have now is basically no better. Good point about the boot.img. I hadn't thought of that.
Carbon is working and moderately stable when wifi and mobile data are off. When I enable wifi, I tend to go into a boot cycle with 1-2s before reboot to disable it again. When enabling mobile data, I get frequent popups saying something like android.com.phone stopped working, and not data anyways. I do have a working recovery right now in CWM (up to date non-touch). But, I don't think that has HTCDumlock built in.
Click to expand...
Click to collapse
Have you tried just booting into CWM, wiping everything except external SD twice, and reflashing Carbon again, the same one so you don't have to try to flash the kernel?
Probably too late now but did you try drying it out via the bag of rice trick?
I found this nice app for getting files on and off via wifi, not doing you much good if your wifi makes you bootloop though.
https://play.google.com/store/apps/details?id=com.dmitril.droidoverwifi
At this point, an SDcard reader would be my investment and store your backups on the internal SDcard. This would allow you to use PH98IMG's. As far as your mobile data and wifi is concerned. It really sounds like you havent flashed the boot.img matched with the rom. If you still have the rom zip about place it on your external sdcard while in rom in a folder called lunar. Run sysrw in terminal emulator then invoke a script named "menu". Choose option 4, then choose the SAME zip you flashed. You might auto-reboot to recovery, just reboot back to system without any changes.
Thanks. I got wifii to run stable. Did a couple more wipes and re-flashed. ES file explorer disappeared, so maybe my previous wipes were insufficient. Also changed from "Launcher" to "Trebuchet", so a couple variables working together. Either way I flashed TWRP now, so I have HTCDumlock again.
Snuzzo, I'll try and follow your steps to see if that fixes mobile data. Not working right now with mobile roaming enabled, LTE or 3G. I can place calls now, though!
EDIT:: ran the Lunar Menu script and flashed the boot.img (seemed successful). wifi is stable, but no data.
At least you now know how to use LunarMenu and can flash a ROM using that instead also with using dumlock. Option 4 reboots you into recovery, let's you do your normal wipes which you then flash the matching ROM zip. Dumlock basically flashes recovery to your boot partition so to flash a rom , you would be flashing boot partition twice. My implementation flashes it only once.
Sent from my Nexus 7 using xda app-developers app
You guys have been a great help. Thanks a lot
It seems my data connectivity issue is unrelated to the ROM i'm using. I must have caused it while tinkering or trying to update firmware. Now I'm on Evervolv with the same issues. Both Carbon and Evervolv are mostly stable with cell signal for calls and wifi, but no mobile data.
TWRP 2.6.3.0
HBOOT 2.21.0000
Radio 1.22.10.0310r/1.22.10.0308r
Is there something I can flash via a PH98IMG.zip that might fix this issue? Or maybe it's an issue with Verizon that they could fix?
I've a feeling it isn't your own Rez. I have a rom cooked with updsated Telephony. If things go right, release is imminent and very soon. No eta promised tho.
Sent from my Nexus 7 using xda app-developers app
yimpierre said:
You guys have been a great help. Thanks a lot
It seems my data connectivity issue is unrelated to the ROM i'm using. I must have caused it while tinkering or trying to update firmware. Now I'm on Evervolv with the same issues. Both Carbon and Evervolv are mostly stable with cell signal for calls and wifi, but no mobile data.
TWRP 2.6.3.0
HBOOT 2.21.0000
Radio 1.22.10.0310r/1.22.10.0308r
Is there something I can flash via a PH98IMG.zip that might fix this issue? Or maybe it's an issue with Verizon that they could fix?
Click to expand...
Click to collapse
you are on a VERY old hboot and radios....that is what could be causing your mobile data issues
REV3NT3CH said:
you are on a VERY old hboot and radios....that is what could be causing your mobile data issues
Click to expand...
Click to collapse
Thanks for joining in! I tried to update these, but was having a hard time. When I was looking at firmware update PH98IMG.zip's, it looked like you need to relock to flash these up, then unlock again (both requiring usb). Is it possible to update hboot and radios without doing this?
yimpierre said:
Thanks for joining in! I tried to update these, but was having a hard time. When I was looking at firmware update PH98IMG.zip's, it looked like you need to relock to flash these up, then unlock again (both requiring usb). Is it possible to update hboot and radios without doing this?
Click to expand...
Click to collapse
also need to be s-off to do this....with broken usb though only possibility i would say is on pure stock youd have to do all the updates givin by them...including stock recovery as well...and relocked bootloader is required...im wondering if theres a way around this that can be possibly worked in somehow...this is a tight predicament with the phone having no usb function and s-on though
1I went back to an old ICS rom (CleanROM DE 1.4) and got the same issue. Everything works except no data. I thought I'd post an update, but it's not so pressing here: LG G2 is in the mail!
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Messed_sensation said:
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
es0tericcha0s said:
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
Click to expand...
Click to collapse
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Messed_sensation said:
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Click to expand...
Click to collapse
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Thank you for all your help and suggestion:good:. I am now running the Android Revolution HD.
This is a huge change from my iphone 4.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Messed_sensation said:
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Click to expand...
Click to collapse
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
es0tericcha0s said:
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
Click to expand...
Click to collapse
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Messed_sensation said:
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Click to expand...
Click to collapse
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
es0tericcha0s said:
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
Click to expand...
Click to collapse
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Messed_sensation said:
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Click to expand...
Click to collapse
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
es0tericcha0s said:
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
Click to expand...
Click to collapse
I think it is my battery. I picked up an Anker and the phone is now at 20% after 21hrs. Is there a way to get Emoji to work on my phone? When people SMS me, on the lock screen they show up as a question mark in a box but when i go to read the text message there is nothing there.
Using a different keyboard will let you send Emojis, but not really sure about enabling the view from other people's messages off the top of my head, sorry. I recommend SwiftKey for a great keyboard replacement with lots of built in Emojis.