Currently running 1.5 The Dark Side Rom on my ATRIX. I thought installing a rom would help fix the problems, it didn't... there's about a 5cm thick line on the top half of the screen that doesn't respond, as well, the fingerprint scanner is laggy and unresponsive to the point of unusability, as a less prominent problem, proximity sensing apps and certain tasker scripts stop working after a while ... what's wrong?
Thanks!
Sent from my MB860 using XDA App
Do a full wipe (dalvik, cache, data) with latest recovery, install latest radio and the ROM again.
If you need to, update your bootloader pudding.
And try using the phone without restoring any data with titanium backup.
links:
Recovery - http://forum.xda-developers.com/showthread.php?t=1204500 (ROM MANAGER recovery is good too)
Radio - http://forum.xda-developers.com/showthread.php?t=1163009
ROM - http://forum.xda-developers.com/showthread.php?t=1222108
Pudding - http://forum.xda-developers.com/showthread.php?t=1136261
*Extra FULL WIPE if you want to use: http://forum.xda-developers.com/showpost.php?p=17656035&postcount=5
** After all that make sure you update to latest kernel - http://forum.xda-developers.com/showthread.php?t=1156040
would this help even if i had the problem when i was the bootloader was still locked and i was on stock?
I don't know ... maybe you need to give it back to store for fix.
But if you already unlocked your bootloader, give it a try ...
Related
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
First off this is the wrong section
Second yea u need to always wipe everything when switching to a new ROM. I use Synergy and the first boot will always be laggy. Synergy let's your Google account download all the apps that u previously had which really slows the phone down. What I'd do is wipe EVERYTHING. Then flash the ROM again. During setup, only setup your Google account and leave for Facebook or whatever other accounts u set up for later as it may speed up things for the first boot. And then I'd just put the phone down n let it do what it needs to do. Synergy is a fast and smooth ROM. The first boot is always laggy on any ROM that allows Google to auto download previous apps. Hope this helps
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
wetbo529 said:
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
Click to expand...
Click to collapse
Follow these procedures:
- Normally you'd perform a nandroid first after flashing into clockwork recovery, but I don't know that you'd want to do that since the ROM is running poorly; your call (I would anyway)
- Wipe Data I always do this, no matter what. That might sound extreme, but I've never had one issue with any of the three android phones I've owned.
- Wipe Cache
- Wipe Dalvik
- Flash Rom
- Flash Radio (if necessary)
- Reboot
Play with the ROM for a while before you flash a different kernel. You might find one of two things: 1) The kernel that came with the ROM is plenty fast and does everything you need, which leads to 2) The kernel you flashed originally could be the cause of the slowness.
Ir's possible the ROM is the issue, so following the above procedure will rule everything else out. Let us know how it goes.
Hi guys, so yesterday I decided to take the plunge and unlock my evo 3d with htc's tool. It seemed to work as expected (s-on with unlocked banner). I was then able to flash cwm 4.0.1.4 and root using the su zip floating around on here.
My issue seems to be that aside from the nandroid backup I made all the roms I have tried break wifi giving the wifi error instead of on or off. I tried synergy rom, viper rom and viper rom with silverneedle. I also noticed when I was flashing in recovery it would say unable to mount sd-ext and it looked like under the settings> about phone> software information that the kernel had not changed.
I'm at a loss as to why, but I think it may be related to htc's unlock method, although I am fairly noob and may be totally wrong. Any help is appreciated.
Sent from my PG86100 using XDA App
Since you used the HTC method then you have the newest OTA updates and bootloader. Your banner should say S-OFF though if you had a typo above about that.
You cannot flash a new kernel yet with the new hboot. You need to stick with the stock one for now.
When flashing other ROMs are you doing a complete wipe first? If not, that might be your problem.
Go to the Development section. Many useful instructions and guides are there.
That's what I was afraid of, but that wasn't a typo. My bootloader says ****UNLOCKED**** with S-On. I was reading that this was what was to be expected with the htc unlock though.
Sent from my Shooter using XDA App
If it's still letting you use Super User and says you're rooted then it should be OK I guess. The main thing is when switching to a completely new ROM you should always do a full wipe - everything except sdcard.
There's a superwipe zip you can flash in recovery that will do all the necessary wipes for you.
I was wiping data/cache and dalvik cache. I'll take a look at the superwipe zip. I'm ok with stock rooted for now but it would be nice to use roms at some point.
Sent from my Shooter using XDA App
Yeah just wiping cache and dalvik isn't going to work. New ROM means backing up apps (if you want), then full wipe. That will wipe the system and data too (and I think android.secure and sd-ext).
Ok. Finally got everything to work. I used superwipe but I also had to use one of the synergy nightlies based on 2.3.4 to get my radios to work properly. Currently running synergy build 331 and it runs great. Thanks for the help
Sent from my PG86100 using XDA App
sceadwe said:
Ok. Finally got everything to work. I used superwipe but I also had to use one of the synergy nightlies based on 2.3.4 to get my radios to work properly. Currently running synergy build 331 and it runs great. Thanks for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I have the same problem:
wifi error
Kernel doesn't change
Also my Android version now shows 2.3.3
Can you please tell me how you got it fixed?
Sorry I'm a noob... Details would help. Thank you
if you upgraded to HBoot 1.5 and used HTC's unlocker you have to install a 2.3.4 ROM or the WiFi and possibly 4G radio will break. If you are interested in Synergy ROM try their RLS1 build or any build version 319 or newer
i cant post a url here cuz i am still a new user on the forums but go check out the official nightly folder linked in the following thread:
http://forum.xda-developers.com/showthread.php?t=1193948
I bought device in Europe with German Vodafone 2.3.4/4.5.2A rom.
I get reboots with all roms i tried as well as all custom kernels i tried while these all stuff work on other peoples devices with no issues whatsoever..
Before flashing rom i wipe device with moto-fastboot and cwm like anyone else who is familiarized with the procedure.
I follow all instructions and all but somehow i end up with issues not many people have.
What the hell doing wrong if anything at all?
well this is the wrong section to post in, but have you tried factory resetting from the phone?
Wrong section. It might be that your CPU is getting very hot, so it keeps rebooting.
Tried factory reset off course but i don't have any single issue with stock software. Just with custom ROM's and kernels i want to play with.
Also, I haven't noticed it gets hot that much.
how come it doesn't get hot and reboot that much to other people?
What problems beside the reboots?
Sent from my MB860 using Tapatalk
@schwarzlichtkind, something like widgets missing after reboots, display staying turned on (when talking) when it needs to turn off.. annoying stuff like that..
Which CWM are you using?
Sent from my MB860 using XDA App
when you install a rom do u wipe data, cache, and dalvik cache before flashing the rom?
then do you fix permissions after flashing?
i recommend you do this when you flash a NEW rom, if you are installing an update just wipe cache and dalvik before flashing, then fix permissions after.
latest romracers..i always tend to run latest software, hence the topic
I'm having a similar issue since I got my phone back from repair, no matter what I do faux's kernel 0.2.2 and 0.2.3 cause random reboots and the phone not turning on and heating up. So far 0.2.1 hasn't caused me any problems, hopefully 0.2.1 fixes this and 0.2.4 (in the future) doesn't give problems.
First of all, please post question on the Q&A forum, not on the Android Development one.
Second, please organize your things before asking, and ask a serious question to get a useful answer. Based on your question, 90% of the answers will be guesses.
I reccomend you pick a ROM you like, try it without any custom kernels for a while and see if you get the same reboots. If so, then post a question on the appropriate ROM's discussion thread, don't create a new one just because.
Edit: Post reported btw
Sent from my MB860 using xda premium
Are you sure you fully wiped? data cache and dalvik? if you did you can try using rom manger and official CWM
everytime a flash a rom i use this tool without fail. option 10. then i do the appropriate wipe in recovery. have never had a bad flash. i am anal like that. : )
http://forum.xda-developers.com/showthread.php?t=1314607
I have problems with faux's latest kernels also. Just stick to the stock cm7/blur/MIUI kernels and you should be fine.
Sent from my MB860 using XDA App
try under volting using setcpu. i too had this random reboot issue. but did an undervolt of 100mV (for 1.45GHz). i use faux's 1.45ghz kernel v2.3
have fun!
a possible radio issue i think...
Which radio works better? I have N_01.100.00R
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
Hello guys,
From the title, you might wonder what it has to do with the Z2 Tablet but I know for a fact it's the tablet and not the apps.
A few months back, I tried custom Roms; it all went fine until I tried CyanogenMod. The Rom itself was quite good but it messed up with the Recovery Partition, forcing the installation of the crappy Cyanogen Recovery (although the option to install it with updates was deactivated in the settings; I still don't understand how it got there). I had a hard time installing permanently another Recovery, it always got back to Cyanogen Recovery after a reboot.
A few issues also started to appear on non-Cyanogen ROMS : Adway wouldn't work. Titanium Backup sometimes couldn't find the backups. Youtube playback wouldn't work with the latest version. Gifs would never load on Relay for Reddit. It took me a while to realize that it was related to the ROM, until I actually tried Cyanogen again...where everything worked, sometimes using the same Titanium Backup for the apps !
I got fed up about this, so I decided to revert to full stock (latest 5.1) using the proper FTF.
And you know what ? Youtube Playback is not working, Gifs won't load in Relay. Can't speak for TiBu and Adaway as I didn't root but I'm sure they wouldn't work either. I'm also sure that other apps that I don't use have issues.
Do you have any idea what could be the source of these troubles ? Because if flashing a stock FTF still didn't fixed them, I think Cyanogen damaged my tablet more deeply than I thought...
Thanks !
Did you wipe data?
Not wiping data when going from cyanogen to stock causes problems very similar to yours. (only wiping cache isn't enough)
Sent from my SGP521 using XDA Premium HD app
I always wipe the datas when changing roms. And I did wipe the datas when I flashed the FTF as well...
OGYoutube won't work as well. If only I could identify the issue...
Ok, here's the solution : I forgot to relock my bootloader...
so.. that's so strange. how relocking the bootloader fixes the youtube problem? I've got the same problem with youtube, BUT only with original sony 5.0.. 5.1 firmware. with 4.4.2 or cyanogenmod doesn't happen.