Since I'm rooted and flashed Faux kernel, I have connection problems (wireless & 4G), is very slow. Today I had an infinite bootloop, I removed the battery to solve the problem. I also had problems with update SU ... I went on the market for the SU fixer. For that, it's ok...but is there anyone who can tell me what to do to return to the original version of Telus? no more for me.
fourire said:
Since I'm rooted and flashed Faux kernel, I have connection problems (wireless & 4G), is very slow. Today I had an infinite bootloop, I removed the battery to solve the problem. I also had problems with update SU ... I went on the market for the SU fixer. For that, it's ok...but is there anyone who can tell me what to do to return to the original version of Telus? no more for me.
Click to expand...
Click to collapse
first read this
http://forum.xda-developers.com/showthread.php?t=1426648
go here:
http://forum.xda-developers.com/showthread.php?t=1335703
fourire said:
Since I'm rooted and flashed Faux kernel, I have connection problems (wireless & 4G), is very slow. Today I had an infinite bootloop, I removed the battery to solve the problem. I also had problems with update SU ... I went on the market for the SU fixer. For that, it's ok...but is there anyone who can tell me what to do to return to the original version of Telus? no more for me.
Click to expand...
Click to collapse
Download the correct ROM and follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1335703?referrerid=922386
fourire said:
Since I'm rooted and flashed Faux kernel, I have connection problems (wireless & 4G), is very slow. Today I had an infinite bootloop, I removed the battery to solve the problem. I also had problems with update SU ... I went on the market for the SU fixer. For that, it's ok...but is there anyone who can tell me what to do to return to the original version of Telus? no more for me.
Click to expand...
Click to collapse
You will also need to flash stock kernel back, I'll let you find that in the dev section...i'll give you a hint its by xboarder and its called kernel flasher by xboarder.
Thank's for the answers ... I flashed the kernel again and now everything works normally. A question about the superuser, I have a message telling me that it's obsolete, yet I installed the fix from market, always the same message, you have an idea?
fourire said:
Thank's for the answers ... I flashed the kernel again and now everything works normally. A question about the superuser, I have a message telling me that it's obsolete, yet I installed the fix from market, always the same message, you have an idea?
Click to expand...
Click to collapse
Did you flash the stock rom back???? you should not have superuser if you flashed the stock rom back. you should always wipe dalvik cache, wipe cache, wipe factory settings from recovery before installing a rom.
seansk said:
Did you flash the stock rom back???? you should not have superuser if you flashed the stock rom back. you should always wipe dalvik cache, wipe cache, wipe factory settings from recovery before installing a rom.
Click to expand...
Click to collapse
absolutely not, just rooted (xboarder56 utility) & flash the kernel.
For SU, I currently have version 2.3.2.-efgh ... he told me There's a new version 3.0.3.2, it downloads but when installing, it says error
fourire said:
absolutely not, just rooted (xboarder56 utility) & flash the kernel.
Click to expand...
Click to collapse
then you should flash the stock rom back.
hasoon in post number 3 told you what to do. Why are you not flashing stock rom back????
Because now everything is working as I want and I have the stock rom, right? First, I wanted it to be root with a custom recovery while keeping the rom that was already in phone. Eventually, I download another rom.
Related
Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
I had Viper 1.0.1 working. It wasn't broke but I tried to put Viper 1.1.0 on the phone. I keep getting the message "Unfortunately system UI has stopped " I have no status bar and no pull down for notifications.
I have dirty flashed, clean flashed, tried different kernels, fixed permissions, different download.
Any ideas?????
I have restored the previous version for the time being.
TIA
Dave
I had the same problem, and couldn't fix it until I updated to the latest version of CWM recovery. Even if you think that you have the latest version, find the thread for it and re-flash it anyway. Then, do a FULL wipe, install Viper, then install the suggested kernel and see if it works, only after that, then try other kernels if you want to.
RLGL said:
I had Viper 1.0.1 working. It wasn't broke but I tried to put Viper 1.1.0 on the phone. I keep getting the message "Unfortunately system UI has stopped " I have no status bar and no pull down for notifications.
I have dirty flashed, clean flashed, tried different kernels, fixed permissions, different download.
Any ideas?????
I have restored the previous version for the time being.
TIA
Dave
Click to expand...
Click to collapse
you need to be sure to do a full wipe, because that is what happens when you dont
CastleBravo said:
I had the same problem, and couldn't fix it until I updated to the latest version of CWM recovery. Even if you think that you have the latest version, find the thread for it and re-flash it anyway. Then, do a FULL wipe, install Viper, then install the suggested kernel and see if it works, only after that, then try other kernels if you want to.
Click to expand...
Click to collapse
I will switch recovery to CWM, even though I don't like it, even from T'bolt days. I DO realize that the recovery will affect the Rom installs
Bigandrewgold said:
you need to be sure to do a full wipe, because that is what happens when you dont
Click to expand...
Click to collapse
Overnight I decided a complete wipe was in order. I also noticed something with the quick settings and notifications that is different. The quick settings scroll across the top of the notification menu and the page is skittish.
Time to back up all storage items.
Thanks for the responses.
RLGL said:
I will switch recovery to CWM, even though I don't like it, even from T'bolt days. I DO realize that the recovery will affect the Rom installs
Click to expand...
Click to collapse
If this solves the problem, please post back. I've seen two instances of it so far (one from twrp, one an early version of cwm) and I'm interested to see if these were isolated events or actual problems with the recoveries.
CastleBravo said:
If this solves the problem, please post back. I've seen two instances of it so far (one from twrp, one an early version of cwm) and I'm interested to see if these were isolated events or actual problems with the recoveries.
Click to expand...
Click to collapse
I installed the latest version of CWM and reflashed Viper. So far all looks good. Also one other issue has cleared up, unmounting the USB drive no longer causes apps to stop. The only other change I made was from ES File explorer to Root Explorer.
The recovery causing issues also surfaced with the Thunderbolts. CWM was the villan in those instances.:fingers-crossed:
I've been struggling with this for about a week and I am not able to figure this one out. I hope someone here can give me a hand.
I've unlocked my phone using HTCDEV and rooted using TWRP 2.4.3 gaining root and recovery access. All seemed to work well but every GOOGLE app crashes now on start up. I can't go to the market as it crashes "Unfortunately Google play store has stopped". It does this with all Gapps.
I've flashed the GAPPS through recovery since I can't access Play.Google. and it made no difference. I can't log in to Google accounts as soon as try it gives me "google account manager has stopped".
I've tried to RUU back to rom 3.16. but RUU fails to update the phone although the restoral screen shows the scrolling dots indicating it is updating, but it goes on forever. the bootloader shows "TAMPERED" "Unlocked" and this came after using FASTBOOT OEM LOCK command in an attempt to reflash the unit. I have tried to flash to other roms like CM10 but it only gets to the point of the spinning logo and just sits there and spins, etc. Other roms get stuck as well in the first boot up logo of the rom or give a black screen. I can use TWRP to restore the backup each time so the phone works seemingly ok except for anything with Gapps.
I assumed I can't not flash JB roms without S-off and I tried to use Dirty Racun to obtain S-off but I get errors with each step so gave up on that for now. I've resolved myself to sticking with the stock rooted rom but I can't do much without Google Voice which is my text and phone account.
Can anyone shed some light on this for me? I've searched the forums here and elsewhere for dozens of hours and have not been able to find a solution for this or any help that might help me "stumble" into a solution. I don't mind flashing another rom if I could get one to take hold just so I can get this unit working.
I think the TWRP recovery or a old verion of Superuser might have caused this glitch. I did the rooting and recovery using this guide here htcevohacks.com/htc-evo-4g-lte-root/how-to-root-htc-evo-4g-lte-unlock-bootloadertwrp-recovery and the provided TWRP would not accept any input so I replaced it with 2.4.3.0 and recovery then recovery seemed to work and backup/restore but still can't flash any roms successfully. I didn't notice Superuser v0.87 here as being old (my goof) and didn't get a more recent version until after the flashing was done. LIke I said, where I'm left at now is everything seems to work but anything having to do with Gapps just crashes on start.
Any help please?
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
thicklizard said:
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
dominicsdad said:
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
dominicsdad, I'm going to check out what was suggested about Mean Bean but I did try several JP type GB apps, etc. None of them would restore the function. THis has been so frustrating. I'm a guy that can folllow the posts and the guides I read, etc., but not having the core understanding or depth shows it's ugly face for a non-connected guy like me. WHy did you do an SD wipe? That's where I keep my backups which have been the only thing that has let me get back from a few botched rom attempts. I will try the goo manager if I can find a flashable version since I'm locked out otherwise with any kind of app install. I was surprised to see the EVO LTE didn't have a file manager as I was going to try and just install google voice which would at least allow me to use the phone.
THanks!
billaggie said:
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
Click to expand...
Click to collapse
Thicklizard,
Update, I installed Mean Bean and solved my problem. It gave me a scare thinking it would backfire with the 2 duplicate rom installs it requires but I had to put some faith in something working and it worked. Thank you for getting me on the right track!!!!!! Bill