Having an issue with the ViperXL 3.2.6 rom from Venom.
Quite frequently I receive a call, and before the call can connect and show ringing the phone reboots. The phone will light up and immediately go to the ViperXL logo.
I have flashed 3.2.6 twice, once via updates OTA and the second time a clean flash and wiping the phone. So this determines its a ROM specific problem and not my device as it worked fine with 3.2.5.
Anyone have any suggestions?
Mods please move to QA if needed. I tried to post there, but for some reason that didn't work. Thanks!
LOGCAT !!!!!! LOG CAT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jd101506 said:
Having an issue with the ViperXL 3.2.6 rom from Venom.
Quite frequently I receive a call, and before the call can connect and show ringing the phone reboots. The phone will light up and immediately go to the ViperXL logo.
I have flashed 3.2.6 twice, once via updates OTA and the second time a clean flash and wiping the phone. So this determines its a ROM specific problem and not my device as it worked fine with 3.2.5.
Anyone have any suggestions?
Mods please move to QA if needed. I tried to post there, but for some reason that didn't work. Thanks!
Click to expand...
Click to collapse
Do you use the AOSP lockscreen with the incoming call workaround? I had this problem. Just turn off the incoming call workaround and use Tasker to unlock the phone when a call comes in.
RollTribe said:
Do you use the AOSP lockscreen with the incoming call workaround? I had this problem. Just turn off the incoming call workaround and use Tasker to unlock the phone when a call comes in.
Click to expand...
Click to collapse
I'll give that a shot. Should this not work, is there a good guide on here to relock, unroot, and flash the original rom? Should I need to go back for a warranty reason I'd like to know I have the ability to do it. SuperCID, unlocked, and on 3.2.6 currently. I do not have a backup of my original ROM as when I was flashing that particular backup it erased the SD card. Which was awesome. haha.
I did use the AOSP unlock method with the autounlock feature enabled since last week. Its odd, sometimes it worked, sometimes it didn't. Prior to updating to 3.2.6 I never had any problems.
Thanks!
CheesyNutz said:
LOGCAT !!!!!! LOG CAT
Click to expand...
Click to collapse
I can paste the whole Log if you want but... I only have three "red" issues it seems.
"E/Trace (29702): error opening trace file: No such file or directory (2)" x 5
"E/hwcomposer( 237): void qhwc::QueuedBufferStore::unlockBuffer(private_handle_t*) Invalid Handle" x 1
"E/SQLiteLog(29830): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]" x1
Have you tried a dirty flash of the Rom? Agree that it is most likely aosp lockscreen issue. Could also be too little voltage. Do a nandroid backup, and then try a dirty flash(only wipe dalvik and cache).
Sent from the HOXL dimension of S-OFF
c5satellite2 said:
Have you tried a dirty flash of the Rom? Agree that it is most likely aosp lockscreen issue. Could also be too little voltage. Do a nandroid backup, and then try a dirty flash(only wipe dalvik and cache).
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
I did a dirty flash of the ROM prior to this current one. I have disabled the AOSP lockscreen and gone back to the stock one and it seems to be fine. I have received three calls on it so far with no random reboots, so far so good. Will report back if I have it again and i'll try a dirty flash if so.
Does anyone have a good step by step guide to bring the phone back to ATT spec? Supercid, relock, the stock rom etc? Assuming this guide will do me? http://www.youtube.com/watch?v=owjiYLQNbnI
At some point in the future I'll need to reformat in order to upgrade and I'd like to be ready for it.
Thanks everyone.
jd101506 said:
I did a dirty flash of the ROM prior to this current one. I have disabled the AOSP lockscreen and gone back to the stock one and it seems to be fine. I have received three calls on it so far with no random reboots, so far so good. Will report back if I have it again and i'll try a dirty flash if so.
Does anyone have a good step by step guide to bring the phone back to ATT spec? Supercid, relock, the stock rom etc? Assuming this guide will do me? http://www.youtube.com/watch?v=owjiYLQNbnI
At some point in the future I'll need to reformat in order to upgrade and I'd like to be ready for it.
Thanks everyone.
Click to expand...
Click to collapse
It depends what state your phone is in now. Is it SuperCID? If so, and you're S-ON the RUU will brick your phone. The safest way to RUU is with S-OFF. Are you planning on selling the phone? If so, I would just leave it S-OFF and bootloader unlocked and just run the RUU. This way, the phone is stock but if the next person wants to root it they can.
exad said:
It depends what state your phone is in now. Is it SuperCID? If so, and you're S-ON the RUU will brick your phone. The safest way to RUU is with S-OFF. Are you planning on selling the phone? If so, I would just leave it S-OFF and bootloader unlocked and just run the RUU. This way, the phone is stock but if the next person wants to root it they can.
Click to expand...
Click to collapse
Thanks for the information. Ironically a lot has happened since I last posted.
Unrooted and relocked the phone yesterday. After running the RUU, it booted up and I all was well. Phone was perfect coming out of the gate, and I installed all my apps and customization. Unfortunately, when I updated to the stock JB image using the OTA update from ATT it erased all my data. Puzzling. I tried updating again and it bricked the device. No power, no screen image, no charge LED, nothing.
Took it to ATT and my replacement is out for delivery today. I guess that's one way to do it...
Thanks to the community for all the help. Might end up rooting this new phone once I get sick of ATTs junkware.
Related
This is a download for the stock evo OTA update (1.32.651.6), rooted and in update.zip format. Please note that you will NOT be able to just flash this on your phone and have root. This is here for you to be able to have a totally stock rom (with root, superuser, and debugging turned on) once you root your Evo. You should be able to flash this without wiping, however if you have any problems then wipe.
Base: Supersonic_1.32.651.6
Download: http://geekfor.me/evo/21/ota1326516
Radio: http://geekfor.me/evo/radio/radio139000531/
Thanks, flipz!
Just saying that this also breaks 4G, I was running the debugging recovery PC36IMG.zip from toastcfh before this and 4G was working fine.
angeltk said:
Just saying that this also breaks 4G, I was running the debugging recovery PC36IMG.zip from toastcfh before this and 4G was working fine.
Click to expand...
Click to collapse
Did you upgrade your radio? This is a 100% copy of the rom with the minor tweaks required to make it root. I have had several testers confirm that 4g works perfectly fine with the radio update. I'll be making my way towards the city today and confirming it for myself. I can't test it from home.
4g works, confirmed.
efuse said:
4g works, confirmed.
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
has anyone successfully flashed this over their .1 "stock" rom? any FC/other issues?
flipzmode said:
Did you upgrade your radio? This is a 100% copy of the rom with the minor tweaks required to make it root. I have had several testers confirm that 4g works perfectly fine with the radio update. I'll be making my way towards the city today and confirming it for myself. I can't test it from home.
Click to expand...
Click to collapse
Yes, I flashed the radio that toast posted earlier. 4G connects and shows 2 bars, just no data gets passed through (ie, web pages don't load, speedtests don't run) tested after a reboot too.
flipzmode said:
You should be able to flash this without wiping
Click to expand...
Click to collapse
Please explain. I have the Toast root, Flipz original .1 rooted RUU & Toast radio update. I can flash this with the same procedure as the .1 rooted RUU? Are you saying that I do not need to clear data and davlic cache? Also, I assume I will have to reinstall all apps?
Thanks!
PS- If my SD card is working and I have the new radio, is there a reason for me to flash this rom?
Thanks flipz! You're the man!
Thank you Flipz.
Market is working shows all my apps and installs are running faster then ever.
Shows Handcent.
Flashed over stock rooted and got a boot loop. Oh well.
just want to clarify do we need to flash both this:
Base: Supersonic_1.32.651.6
AND the radio? or is the radio already included in Base: Supersonic_1.32.651.6????
Freelancerx said:
just want to clarify do we need to flash both this:
Base: Supersonic_1.32.651.6
AND the radio? or is the radio already included in Base: Supersonic_1.32.651.6????
Click to expand...
Click to collapse
Yes, you need to flash BOTH the ROM, and the newest radio seperately.
thx flipz for the rom
does 4g work without the radio update?
If I already flashed the radio subsequent to rooting using toast's method, I assume this ROM flash will not overwrite the radio, correct?
KyleMac said:
If I already flashed the radio subsequent to rooting using toast's method, I assume this ROM flash will not overwrite the radio, correct?
Click to expand...
Click to collapse
Nope it wont
Thanks flipz! Flashed this over your original RUU 1.32.651.1 w/o wiping and didn't have any issues. I was able to connect to Killeen/Fort Hood 4G network indoors with the following results 1655 kbps (down) 911 kbps (up). This portion of the post is being done using WiFi Tether (not the Sprint Hotspot) connected to 4G
Again great work!!!!!
KyleMac said:
If I already flashed the radio subsequent to rooting using toast's method, I assume this ROM flash will not overwrite the radio, correct?
Click to expand...
Click to collapse
I'd already flashed the radio and can confirm that this won't overwrite the radio.
MattyG Mods, Userjf Mods, AudioBoost Kernel,
Data Throttle Removal Mods, Camera Shutter Sounds,
CMW3-Flashable Boot Animations, BootLoader Splash Screens... And More!
All Files Can Now Be Found Here:
http://www.mediafire.com/?5ch2853xcxvi0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EVERYTHING YOU DO IS AT YOUR OWN RISK. I TAKE NO RESPONSIBILITY FOR WHAT YOU DO.
DATA THROTTLE REMOVAL:
This removes the throttle files from the rom. The files removed are actually named "throttle", by the way.
AUDIOBOOST KERNEL:
This is simply the stock kernel with all audio levels boosted. Other than that, it is the stock kernel. This will work with any nightly or rc build of cm7.
CAMERA SHUTTER SOUND:
A lower volume, more pleasant, camera shutter sound. Flash with recovery, works with any cm7 version.
CM3-FLASHABLE BOOT ANIMATIONS:
These are boot animations that I have ported to be CWM2 and CWM3 flashable.
SPLASH SCREENS:
Rename exactly to PB31IMG.zip and put on root directory of FAT32 sdcard, not in any folders. You might have to use a blank card with this being the only file... it works for some people better that way. It shouldn't hurt to try it either way though. It will either work or do nothing.
Once the file is on your card and the card is on your phone, with the phone OFF, hold down the vol.down and power button. Hold them down until the bootloader is up. After a few seconds, it should ask you if you want to apply the update. Choose yes.
Once it is loaded, it will be there permanently until you change it again. You don't have to reflash it ever.
BATTERY MODS:
I have continued the popular work "Mattyg battery and clock mods". Mattyg kept these current when he had a Droid Incredible, and he even kept them current for quite some time after he no longer had the phone. We are all thankful to him for putting these together.
These type of flash mods are specific to a particular build of cm7. If you flash one of these to the wrong nightly, it will work only if the cm7 framework has not changed. Otherwise, your phone will be unstable at best, and boot loop at worst. The files have the nightly number at the end, so there is never any confusion about which file goes with what nightly.
If your phone boot loops after flashing, you can easily fix this by reflashing cm7. This is also the method used to "uninstall" these mods if you want to go back to the stock original clock and battery icons.
These are built for CWM3, but they should also work with CWM2 and RA recoverys.
To flash, simply flash them with recovery. Rom Manager will probably work too, but I don't use it.
You can flash the battery mods over each other. The most recent flash will be on the phone, and will overwrite any previous battery mod. There is no need to flash back to stock between changing between these battery mods.
The RemoveClock mod is independent of the battery mods. You can flash clock and battery or either one. They do not interfere with each other in any way.
There is no need to wipe cache or dalvik when you flash these. You can if you want, and it won't hurt anything, but it is not required.
For safety, always have a known good working backup before you flash these, or before you flash anything for that matter.
Enjoy!
RC1 mods have been added, but they are not tested. I have moved past RC1, and you should too! There are CM7 fixes in Nightly #39, and there will continue to be more fixes in the following CM7 builds.
All Files Can Now Be Found Here:
http://www.mediafire.com/?5ch2853xcxvi0
userjf said:
Several people have said they would take over Mattyg's battery and clock mods... but so far no one has... until now!
These will work with cwm recovery 3 (and 2), and they are all tested on the nightly number at the end of the filename (currently #39)
As always, be safe and nandroid!
Enjoy
Click to expand...
Click to collapse
The GB circle bootloops with RC1.
cam30era said:
The GB circle bootloops with RC1.
Click to expand...
Click to collapse
RC1 is NOT 39!!! Flash 39 and you will be good... or wait until tonight and get the #40's.
userjf said:
RC1 is NOT 39!!!
Click to expand...
Click to collapse
Yes, I know. Thought I would give it a try anyway.
So which of those is the stock look with the percentage inside? "stock39"? Or is there one?
RyanTX said:
So which of those is the stock look with the percentage inside? "stock39"? Or is there one?
Click to expand...
Click to collapse
Stock = original
StockPercent = stock + percentage
userjf said:
Several people have said they would take over Mattyg's battery and clock mods... but so far no one has... until now!
These will work with cwm recovery 3 (and 2), and they are all tested on the nightly number at the end of the filename (currently #39)
As always, be safe and nandroid!
Enjoy
Click to expand...
Click to collapse
are you running into any issues with these? i put them all together, but was getting FC's after flashing. not MAJOR FC's, but enough that i didnt want to release them until i figured it out. Mostly CM settings when attempting to change anything and ROM manager.
lol ive been working on it all day.
AdhvanIt said:
are you running into any issues with these? i put them all together, but was getting FC's after flashing. not MAJOR FC's, but enough that i didnt want to release them until i figured it out. Mostly CM settings when attempting to change anything and ROM manager.
lol ive been working on it all day.
Click to expand...
Click to collapse
Let me check, I didn't modify any of Mattyg's actual coding other than compiling into the new framework.
Yup, you are right about that, I tried a few other things, but not that. Very interesting... I'll take a look..., and you take a look... and we will see who figures it out first
userjf said:
Let me check, I didn't modify any of Mattyg's actual coding other than compiling into the new framework.
Yup, you are right about that, I tried a few other things, but not that. Very interesting... I'll take a look..., and you take a look... and we will see who figures it out first
Click to expand...
Click to collapse
Problem found! I'll be putting up new files shortly.
userjf said:
Let me check, I didn't modify any of Mattyg's actual coding other than compiling into the new framework.
Yup, you are right about that, I tried a few other things, but not that. Very interesting... I'll take a look..., and you take a look... and we will see who figures it out first
Click to expand...
Click to collapse
boot loops on green circle-after clean install of #39. what did you find about the FC issues? i have a logcat of what i get with my files.. but no idea how to read it and fix it. lol
userjf said:
Stock = original
StockPercent = stock + percentage
Click to expand...
Click to collapse
That stockpercent was not there when I posted.
Thanks though.
Is there any possibility you could do a cyan colored circle battery?
Sent from my ADR6300 using Tapatalk
cmo220 said:
Is there any possibility you could do a cyan colored circle battery?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
FC issues should be resolved.
Download the GBCircle39-fixed.zip file and try it.
Post back here if it works well or not.
Only flash them to the build they are intended for (like 39 at this point)
Once these are proven to be good, I can make other colors.
userjf said:
FC issues should be resolved.
Download the GBCircle39-fixed.zip file and try it.
Post back here if it works well or not.
Only flash them to the build they are intended for (like 39 at this point)
Once these are proven to be good, I can make other colors.
Click to expand...
Click to collapse
Stuck in a boot loop...
These are all working fine for me now... I have flashed them over and over on my phone, I have had no boot loops, and no FC. I never had a boot loop during any of these.
Boot loop has always been a a symptom of flashing over the wrong nightly, even when Mattyg was releasing these. Make sure you have the right nightly (currently 39, not RC1.)
If anyone else has tried these, successfully or unsuccessfully since the fixes, please let me know.
userjf said:
These are all working fine for me now... I have flashed them over and over on my phone, I have had no boot loops, and no FC. I never had a boot loop during any of these.
Boot loop has always been a a symptom of flashing over the wrong nightly, even when Mattyg was releasing these. Make sure you have the right nightly (currently 39, not RC1.)
If anyone else has tried these, successfully or unsuccessfully since the fixes, please let me know.
Click to expand...
Click to collapse
Works now.
Reflashed #39, rebooted, cleared cache's and then flashed Mod. Everything seems to be working.
Great work bringing these back to life!! Much appreciated!!
I'm a stock percent kinda guy but I don't see the fixed file in the OP.
hokieputter said:
Great work bringing these back to life!! Much appreciated!!
I'm a stock percent kinda guy but I don't see the fixed file in the OP.
Click to expand...
Click to collapse
I downloaded the stock percent and flashed it and it works great. Im not sure what you mean by 'fixed file' though.
I'm not seeing StockPercent attached to the post either
I thought I had put that one on there. I can't load attachments from my phone but I'll put it on there shortly when I get back to my computer.
Sent from my telephone device thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SILVER ROM ICS
15 toggle mod and kernel thanks to RomRacer
download link
ROM
Http://www.theandroidcollective.org/i727/SilverRom/silver_cream_sammywich.zip
SuperSU
Http://www.theandroidcollective.org/i727/SilverRom/CWN-SuperSU-v0.87.zip
if you do not want transparent pop up menus flash this
http://www.theandroidcollective.org/i727/SilverRom/notrans.zip
Here are instructions.
Download bothzips
Put on sd card
Wipe/data/cache/dalvik cache
Flash rom
Flash supersu.zip
Boot system.
After boot is complete.
Shutdown. Wipe data/cache/dalvik and fix permissions.
Sign in google.
Sign in g+
Open the supersu ap. It will update binary.
You will not loose root.
Power options work.
For later.................
Screenshots.........nnnnnn
For later..............
Is TiBu working yet? And can I install this over another ICS Rom?
Love your rom. I tried the new ics but had tons of fc. Not only did tibu but also with waze and a few others. I went back to collective 3 for now. Patiently waiting for your next masterpiece
Skyrocket,
I was trying to follow your other thread ( no data loss gb rom ) and got lost...
Needless to say, I'm glad you've created a new one.
My question is: Is THIS rom your current 4.0.3 project? I'm still running 2.3.6 (NexusMod4) and would love to try out a stable (or at least somewhat stable) ICS rom.
Thanks in advance, and as always - thanks for the hours of time you and other devs put into these masterpieces!
yes this is my current ics android 4.0.3 rom
link has been removed from op
uploading updated version with changes ......tibu has been fixed so be patient i will update the op with new link asap
you can flash this from gb without wiping anything
yeah i accidentally added back the preloadinstaller
thats what causes the force closes and tibu not to work
silver03wrx said:
yes this is my current ics android 4.0.3 rom
you can flash this from gb without wiping anything
Click to expand...
Click to collapse
Well, I just attempted to flash it (without wiping first) and got stuck in a boot loop.
Any suggestions?
EDIT:
As I let it attempt to boot several times, it seems to get a little further into the boot animation. I've now seen just a little bit of blue swirls behind the earth.
TwiztedDotNet said:
Well, I just attempted to flash it (without wiping first) and got stuck in a boot loop.
Any suggestions?
EDIT:
As I let it attempt to boot several times, it seems to get a little further into the boot animation. I've now seen just a little bit of blue swirls behind the earth.
Click to expand...
Click to collapse
Yea same thing happen to me coming from NexusMod4 Im still trying to get it to not bootloop errgh
Sent from my SAMSUNG-SGH-I727 using xda premium
Yes restore yourbackup and wait for new upload
probs with the theme
I was running fine on the ICS rom (ics3.zip) and installed the theme. Now I'm getting lots of apps unable to run (handcent, lookout, juice defender, ROM manager). Ran fix perms in recovery (couldn't get into ROM mgr to try there) and didn't help... Just wanted to let you know.
I flashed mhx Superlite 4.5 over the previous version (ics3 I think) of Silver ICS and it fixed the freeze at shutdown issue for me. That rom has a wipe script too but that one wipes and formats data (also aligns disc partitions--not sure if yours does that).
I'm wondering if the freeze at shutdown issue has something to do with data not getting fully wiped.
I'm going to try flashing your latest rom over Superlite and see if I get the shutdown freeze again. I'll report back with results...
(I should mention that one person posted that they flashed mhx's rom and got the freeze at shutdown for the first time, so who the hell knows...)
I don't like being impatient, but I'm seriously sitting here biting my nails waiting for the download link to come back (with the latest version).
The suspense is killing me!!!
F5...F5...F5... ;-)
Sent from my SAMSUNG-SGH-I727 using xda premium
silver03wrx said:
download link
http://www.theandroidcollective.org/i727/silverrom/silverics.zip
Click to expand...
Click to collapse
Uhm.. OK I give... Where's the link exactly?
robinsonj said:
Uhm.. OK I give... Where's the link exactly?
Click to expand...
Click to collapse
It's not currently available.
We're all "patiently" waiting for his latest release to be linked...
...and I almost have no finger nails left!
So i'm having some trouble here.
Anything such as CM10.1 or any CM or related custom rom I install gets unstable after x amount of days.
And any CM based rom has the poorest battery life I could ever imagine. I've wiped everything multiple times. I've attempted to full restore and start over on a fully "reset" phone. It's killing me - as I'm an active college student who doesn't have time to sit around a wall outlet anymore [like I use to] to always have a good phone charge.
Anything else either turns out to be;
Unstable -or
Laggy -or
Fail to flash correctly -or
Camera and/or Gallery either isn't there, won't load, crashes, or fails to even hint about being usable.
I honestly am about to just dump this phone, as the screen is already cracked. And development slowed to a halt it seems.
I said screw it the other night, and went to install CleanRom 6.5, only to find that it starts installing [after clicking through my options in Aroma] andd loads for 1-4 seconds then says "DONE" with 0% completed and says everything installed perfectly. However when I go to reboot TWRP notified me I had no OS installed which made sense considering I've never had a rom install in <5 seconds.
Moving on though, anyone have any suggestions? And I do mean any? I've used the OneX tool for everything, AND done the usual [root/unlock/recovery/s-off -> custom rom] with that and manually to have no success between the two. Do I just have a busted device? Something faulty perhaps in the circuit board? I honestly haven't a clue. But all I know is, CM is and probably will forever be my favorite. However my phone died yesterday after 3 hours of sitting in my pocket and today I barely touched it compared to my normal use on sense based or other roms which I'll get 8+ hours out of. I just don't know what to do anymore. I use to consider myself a flash-a-holic where I'd be reinstalling ROM after ROM just to see what all the amazing and different features they have - then running new kernels. But now it isn't even usable.
My signal has also been in the toilet. A friend of mine has the same exact phone and we can put them right next to each other, he'll have full bars on AT&T and i'll have one or two [if i'm lucky]. I've flashed every radio up and down - back and forth. Flashed the radio and all else EXACTLY like his phone and I quickly found myself stuck in a hole with a better paperweight than phone. My last effort was to do wipe after wipe and battery calibration apps hoping that may be my problem and I'm stupid for over thinking it. But... if anything it made it worse.
Should I dump it? or is there hope. . .
I don't see how it could be my battery considering.. well... roms OTHER than those based on CM have been perfect on battery life just like they were when I first got the phone. But they don't have operable camera and/or gallery. I also uploaded a picture of my past 8~ hours with this phone. Note the past 2/3 hours. I know I've noticed some "slight" change..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What Hboot?
What recovery/version?
S-ON or S-OFF?
You said you'd tried wiping, have you tried RUU?
Edit: that said, don't just go flashing running RUUs, unless you're s-off.
As for battery drain, disable Google location services while you are on wi-fi. It really kills aosp roms For other issues see Exad's reply above. Easier to help with more information.
Sent from my HTC One X using xda premium
exad said:
What Hboot?
What recovery/version?
S-ON or S-OFF?
Click to expand...
Click to collapse
HBoot- 2.14.0000
TWRP- [tried the past couple versions, hoping maybe its just a bug with one but stuck with] 2.5.0.0
S-OFF
Venomtester said:
As for battery drain, disable Google location services while you are on wi-fi. It really kills aosp roms For other issues see Exad's reply above. Easier to help with more information.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Alright, I'll try that - even though I rarely use any GPS or related service.
RollTribe said:
You said you'd tried wiping, have you tried RUU?
Edit: that said, don't just go flashing running RUUs, unless you're s-off.
Click to expand...
Click to collapse
Yup.
TKTAB911 said:
HBoot- 2.14.0000
TWRP- [tried the past couple versions, hoping maybe its just a bug with one but stuck with] 2.5.0.0
S-OFF
Alright, I'll try that - even though I rarely use any GPS or related service.
Yup.
Click to expand...
Click to collapse
download twrp 2.6: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Check md5
fastboot flash recovery OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
fastboot reboot bootloader
fastboot erase cache
select bootloader on phone screen
select recovery on phone screen
Wipe
Advanced
Select everything, except sd card unless you want to wipe your sd card
check md5 of your rom on your pc.
copy and flash your rom.
Hi Guys.
Short info:
- before: HTC One M8 Verizon, Android 4.4.4 (RUU M8_VZW 4.4.4), rooted, S-OFF, Super CID, TWRP 2.8.3.0
- after: HTC One M8 Verizon, Android 4.4.4 (Viper OneM8 3.2.1), rooted, S-OFF, Super CID, TWRP 2.8.3.0.
Few hours ago I finished "converting" HTC One M8 Verizon from 4.4.4 to T-Mobile version, successfully installing Viper OneM8 3.2.1 over 4.4.4 RUU firmware, as described in this post:
http://forum.xda-developers.com/showthread.php?t=2710720
The main reason for the above was lack of LTE services under Verizon firmware (I live in Europe).
Finished installing Viper ROM, configuring phone, restored content (apps, contacts, settings etc) - part of it manually. LTE still not available, and continued to verify.
In the end I started to check Viper Tweaks section, and finally got to Misc - Phone info. While there, I checked also Radio bands, and I was stuck in the radio menu, with only 3 options (US Radios, 900-, 1900-). Had to select one to continue, and ... the winner was 900-. Instantly lost GSM signal and never came back.
Just to be nicer, after reboot (normal reboot), 900- option disappeared from Radio bands in Phone info advanced menu, and never came back. No matter what I did.
What I did try (all with full wipe / formatting etc):
- resetting Viper ROM
- reinstalled Viper ROM
- reverting to RUU M8_VZW 4.4.4 nandroid backup (saved before first installing Viper ROM).
- reverting to clean RUU M8_VZW 4.4.4 firmware
- flashed 4.4.4 radio from this topic: forum.xda-developers.com/verizon-htc-one-m8/development/radios-0-89-20-0222-t2824882
- reverting to Viper One ROM, this time installed with T-Mobile version. Same outcome, different message: "error er05 invalid sim".
Error messages stepped on:
Constant: "The SIM card is from an unknown source"
From time to time: "your SIM card does not allow a connection to this network."
If I tried to select GSM network and search for operators (manually / automatic): "No network found. Select "Yes" to switch to global mode, or Select "No" to stay in current mode." And "Error searching for networks" / "No networks found".
The only thing that did not have possibility to check (yet): SIM card health.
UPDATE: SIM card checked and OK, phone registered finally (T Mobile version of Viper One had also "Auto" option under Radio band, in Phone info hidden menu! ).
Still working on this, managed to solve it while compiling this post, but still have the question: what have I done so wrong, and how can I get back to the "good" setting? Is the radio band setting so resilient to full format, several ROM's and resets, even radio firmware change?!
I will revert with updates!
Thanks!
I've been into your position. It seems different ROMs have different options in phone menu. My guess is it depends on what source the rom is built from. There's a threads here on XDA showing how to unlock other bands of the phone. And t stays that way even after RUU. Here's mine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Vanshee, thanks for your inside.
What ROM are you on? How did you "unlock" all the band options in there? :cyclops:
As I said, I managed to solve the matter while was posting the topic. Seems that, after reflashing Viper OneM8 ROM, this time choosing T-Mobile US in Aroma, and not Default, I was able to select Auto in Radio band, and is working.
It still has no LTE in my region, and is also showing full signal all the time, even in places that I know having poor GSM signal. Everything else is working, at least until now.
Thanks again!
Ok i will give you 2 links for threads dealing with said unlocking of radio bands, but like most of the cool stuff here on xda you should be warned - any slight mistake could lead to hard brick. And a piece of advice - when start changing numbers in the needed moment following these guides - write down somewhere the original numbers you have. Or you will end like me - unlocking every possible band in order to bring back my signal to life. I'm serious dude - be very careful in following these guides.
You have been warned!!!
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
http://forum.xda-developers.com/verizon-htc-one-m8/general/lte-band-7-2600mhz-finally-guide-t2992523
Good luck!
Ok Vanshee, got it. Already been on the second link, I was studying it while making final try with Viper ROM, but abandoned it as the "soft" method payed up.
Thanks for links and warn-outs!
gaurika said:
Ok Vanshee, got it. Already been on the second link, I was studying it while making final try with Viper ROM, but abandoned it as the "soft" method payed up.
Thanks for links and warn-outs!
Click to expand...
Click to collapse
Hi im stuck on 2g on a verizon m8. I flashed the verizon version of the last kitkat based viper rom and chose tmobile as my carrier is GSM based (Orange Dominicana 900mhz 3g) i think thats what you meant, could yo please confirm?
but it did not solve my issue.
please help.
elander, that is correct. Initially I installed Viper ROM in default mode, after losing signal I tried RUU, nandroid restore etc. Finished with Viper in T-Mobile install, and that payed off.
I had not time since to try to unlock LTE as per vanshee's posts above, but will do it as soon as I will have some spare in my schedule.
gaurika said:
elander, that is correct. Initially I installed Viper ROM in default mode, after losing signal I tried RUU, nandroid restore etc. Finished with Viper in T-Mobile install, and that payed off.
I had not time since to try to unlock LTE as per vanshee's posts above, but will do it as soon as I will have some spare in my schedule.
Click to expand...
Click to collapse
Hi, I tried again and this time and it showed me the "automatic" band, and as of now I have connectivity which by the way seems to be a little faster than what it used to be (could be a placebo pill I took a few hours ago though ). Thanks for this.
I'm really confused and would like to know why this happened in the first place, I guess if I ever dare flash another rom it'd probably go back to being stuck on edge. I thought that Roms flashed thru recovery wouldn't touch anything regarding the radios, at least not the custom roms (which are normaly stripped from things that are meant to be on a firmware pack anyways), it had never happened to me before...
thanks again man.
Lost Signal while messing up with Phone Info settings
Hey I am facing the same issue here, ditto
I have flashed latest Viper ROM but don't see the Auto option in Phone Info settings.
How do I re-flash Viper in other than default mode as you described?
Doing it for the first time, please excuse.. Have already lost a couple of days sleep over this issue. Please help !!
Hey, does the T-Mobile version of Viper ROM for M8 work on Verizon? I did the same mistaje and now facing the same issue, I have updated my Firmware to latest 5.0.1 and now downloading Viper 4.3.0 T-Mobile version. Hope it works. I already tried Verizon version of Viper and it did not show automatic option in Phone Info Settings.
Fingers crossed
Update: Nope, didn't work. Viper ROM 4.3.0 T-Mobile variant did not work.
Resolved: So the issue was latest Viper ROM 4.3.0 doesn't give you an option to choose carrier(Verizon/Sprint/T-Mobile etc.) in Aroma, Viper has released a separate DL for Verizon M8. I learnt the hard way(downloading and flashing several ROMs) that any ROM that gives an option to choose carrier in Aroma during installation would enable the Automatic option in Phone Info Settings/Phone Testing App/ 4G Switcher App / Network app. So earlier version of Viper ROM probably 4.4.4 would have worked. A single Custom ROM download that supports Multiple Carriers is the solution missing Radio Band issue..
I downloaded GPE 5.0.1 on my 5.0.1 Stock Firmware to get my lost signal, relief !!
Careful, do not go for 5.1, GPE gives an option to upgrade your firmware and install Lollipop 5.1 , i tried and it didn't work but Firmware and ROM 5.0.1 work like a charm. Cheers!!
How did you choose T-Mobile US in Aroma?
gaurika said:
Vanshee, thanks for your inside.
What ROM are you on? How did you "unlock" all the band options in there? :cyclops:
As I said, I managed to solve the matter while was posting the topic. Seems that, after reflashing Viper OneM8 ROM, this time choosing T-Mobile US in Aroma, and not Default, I was able to select Auto in Radio band, and is working.
It still has no LTE in my region, and is also showing full signal all the time, even in places that I know having poor GSM signal. Everything else is working, at least until now.
Thanks again!
Click to expand...
Click to collapse
hey gaurika,
Could you please guide me how did you choose T-Mobile US in Aroma while installing ViperOne Rom on your Verizon M8. I am in a similar no signal situation from past few days and have tried almost everything that I cam across in XDA.
I tried figuring out myself but unable to do it so far, I'm pretty noob. Much appreciate your reply. A setp-by-step info will be helpful
Update: Installed latest GPE ROM from the below thread and was able to get my signal back..
http://forum.xda-developers.com/showthread.php?t=2716306
Celebration time Cheers!!!