Related
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
dzap said:
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
Click to expand...
Click to collapse
i can't tell what kernel on here, its i flashed silver needle and then the rom and it nevered booted up.
I had the same problem using ROMs from XDA. Found that I used RUU to back to stock and it stopped. Haven't had a single reboot since I went back to stock where I would get reboots constantly, to the point the phone was useless.
Since I have S-Off, used the root patch to get root access, but only can be done with S-off...
djcro said:
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
Click to expand...
Click to collapse
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
cobraboy85 said:
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
Click to expand...
Click to collapse
yeah, most likely your issue is flashing a kernel NOT COMPATIBLE with the new base....
oh and your only compatible kernel at this time is stock
i tried to do the ruu step and none of the verisons workked, anybody have anymore ideas?? this is were i downloaded the ruu's from for sprint http://www.filefactory.com/f/4ef0ef536face67a/
I very thoroughly apologize if this has been asked and discussed before, but apparently my search skills aren't the best. Anywho, her's the issue.
I've used a number of different ROM's since I first got my DNA back in January. I've used older Tranquil releases. But anything after 2.1 I believe it was, I haven't had WiFi. I have it just fine with all other ROM's. But no matter what I do for Tranquil (even up to and including RLS 4.2), there's no WiFi connection. It says it's trying to find sources or something and eventually errors out. I have no idea what the problem is. If I go back to 2.1 or 2.0, WiFi works great. This kind of sucks as I really enjoyed the earlier Tranquil releases and would like to continue using them. I'm currently using NOS m7's latest release for 4.1.2 (couldn't get their 4.2.2 release to work for some reason, just sat at the HTC screen for over 30 minutes, even after wiping the entire phone and attempting to sideload).
Anyway, if someone can tell me how to get WiFi to work on Tranquil releases after 2.1, that would be awesome. And again, I apologize if this has been covered before. I tried posting in the official thread but my lack of post count keeps me from doing so.
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
thatotherguy.. said:
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Attempting to get the 2.06 update and then reunlock at the moment, but it's not recognizing the phone in Fastboot. Recognizes fine when it's on, but not Fastboot.
aweber1nj said:
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
Click to expand...
Click to collapse
It does it right from the beginning. Any other ROM and my WiFi network shows immediately. Any release past 2.1 and no WiFi at all.
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
thatotherguy.. said:
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've used this same cord to ADB push and sideload while in Recovery before. Plus it reads just fine when the phone is on as normal. Wouldn't that make it fine? (Note: Not being sarcastic or anything, genuine question. I know how things can be misinterpreted over the 'net so I kinda like to point out how I mean things.)
Edit: I got it to work so far. I'm reflashing back to complete stock now. Apparently a driver wasn't installed for it to be detected in Fastboot. I'll post back after I get back to stock, completely update to newest, and reflash Tranquil RLS4.2.
So I got everything installed, running again, latest updates, reunlocked, TWRP back on, flashed RLS 4.2... No WiFi still... What am I doing wrong here?
Edit: NOS M7 3.0.4 is doing the same thing it was before, also. It's not even getting passed the HTC screen, no matter how long I let it sit. This is quite frustrating. I put M7 2.0.3 back on and everything works as it should. Anyone have an possible solutions?
Do you upgrade your firmware?
Sent from my HTC6435LVW using Tapatalk 4 Beta
It was upgraded to 2.06 when everything was completely stock..
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
matthall9815 said:
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
Click to expand...
Click to collapse
Other than being rooted with the custom ROM, it's whatever the normal S is (can't remember off the top of my head). I rooted and tried the Moonshine thing but it never took (on stock 2.06) so I just went through and reunlocked with my original packet from the HTCDEV website and went about things that way.
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
matthall9815 said:
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
Click to expand...
Click to collapse
You're right. My battery life has been absolutely terrible. I can get maybe 6-8 hours until I'm at 30% or under, and that's not doing anything. Much less if I actually want to do anything with the phone. I'll give those two links a look. Thanks. :good:
Edit: So, I've noticed it's now S-On and the kernel isn't showing on the device. I copied the .zip over to the main directory where I always do, and it's not showing on the phone. But it shows just fine in Windows.
Edit again: Got it to flash using Sideload. Before I do anything else, is it okay to now flash RLS4.2 and see if WiFi works? Now that that's on there, it should be good, right? Or do I need to flash RLS4.2 and then reflash this kernal?
Yet another Edit: It took me a while, but I noticed a LOT of things were missing on the phone after flashing the 2.06 kernel. The one that made me notice was FaceBook. And Google Play Store wasn't there anymore, either. I've reflashed to Digital Dream 2.2 and everything is back to normal. This is really frustrating.
Pm me when you're working on this again I think there are a couple things that are confusing.
Sent from my HTC6435LVW using Tapatalk 4
I finally got it to connect.
I was running DigitalDream 2.2 while trying to figure this all out. I ended up getting S-Off and reflashing. For me to S-Off while already on DigitalDream 2.2, I used the first part of the Mooshine Method (downloading their 2.06firmware zip file, flashing that, rebooting) then used the FacePalm method. That successfully got me S-Off. I noticed that even on DG2.2 after that, I had no WiFi. So I decided to try flashing Tranquil 4.2 and now I have WiFi working. Hope this helps anyone that has the same issue I did.
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
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.
Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.