Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...
Related
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.
I've seen this mentioned in other places before, other threads and in the r/motox subreddit, about how the open GAPPS package apparently flashes the Google Dialer over the stock one, and it doesn't work with the Pure? Which is what causes the reboots whenever I try to make a call or, presumably, get a call, which until now I chalked up to random reboots in CM13.
So I've seen a bunch of posts about it, but none that explain how to actually fix it? Am I doing something wrong from the start?
Bonus question, I've been having radio problems on almost every AOSP rom I flash, either Wifi doesn't work upon booting and it persists in other ROMS or cell service is out (even though LTE data works fine). Is the radio (which I assume is the same as the "modem") included in each ROM package and is replaced every time you flash a new one, or does it persist in some system directory cross-firmware?
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
lafester said:
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
Click to expand...
Click to collapse
Set what as default? Or uninstall what? When I look in the apps list all I see is "phone". Nothing under the name google dialer or anything. It's just confusing, I didn't have this problem on other phones.
Sorry for the double post but I figured instead of making another thread I'll continue asking here, I'm STILL having cell issues, no matter what ROM I flash, stock or AOSP, or any of the radios I can find around the forums, whether it be with the February security update or not, I'm still not getting a connection. In fact once I flashed a new modem, I went from not being able to send texts etc. but able to get LTE data, to getting no connection at all. I'm totally lost, this is the second time it's happened I have no idea what to do. Happens in every single rom.
Last time it was fixed once I flashed from stock (which I had in turn flashed to try to get rid of the problem) to CM13 I think. But it was totally random, I have a feeling it didn't even have anything to do with the ROM itself...
Google searching: "Google Dialer reboots when making a call" >
http://android.stackexchange.com/qu...s-when-making-or-receiving-a-call-nexus-6cm13
https://www.reddit.com/r/cyanogenmo...cm_13_nexus_5_soft_reboots_when_a_phone_call/
Even from Open GApps own FAQ page:
https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Thanks, I honestly dunno why I couldn't find that before. At first I wasn't even aware it was actually called the "google dialer" so I was just googling "phone app reboots after flash/root/etc" and obviously it wasn't turning up many results. But the stock rom rooted debloated thread had the instructions at the bottom, now I know. Whoops. Like I said, just really confusing coming from other phones where everything mostly just worked....
The baseband is still perplexing me though, in the bootloader under baseband it says <not found>. I'm keeping on trying to flash different stock roms to see if I get lucky.
EDIT: so I think flashing the modem at the SAME TIME as a new ROM might be the key? I think I saw something about that on some random obscure post and tried it out and bam, it worked like a charm. Anyway hopefully that works again when I flash to something new
So i just got a new moto g4 plus XT1642 (UK amazon version) and so of course the first thing i had to do was install a custom rom, so i followed a guide here to unlock it and install TWRP which went fine until i flashed a new firmware, I dont know if i somehow installed the wrong one but now it wont go past the "checking connection" screen on setup without crashing (sometimes it doesnt even get past the welcome language screen) I have tried flashing the stock firmware but it just does the same thing no matter which one i try (XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip is the right one i think?)
If anyone could help me get back to marshmellow it started with then i promise i wont mess around with it again :3
Thanks for any help you can give.
Edit: Okay so I finally just went to do the thing i started out to do which was to install the Resurrection Remix rom (http://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275) so I just thought that maybe if i got it installed it might fix what problems i was having and yeah sure enough i followed what i was supposed to flash first which was (Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63_Stock_Img) btw and then flashed Resurrection Remix and it just started working again, everything seems fine but I'm worried I might have broken something with all my puttering around with its inside ya know?
But the main thing is phone calls work, texts work, it rooted itself magically, can install unsigned apks and such, wifi works and so does the fingerprint sensor which i heard people were having issues with. So should i just not look for problems and enjoy it maybe? I'm glad i got it sorted im some fashion at least
So I HAVE now noticed that some apps seem to hang/crash sometimes, epecially games, not sure if it has to do with my puttering around though Is there anything I can do to check that everything is working ok? any programs that scan for errors or something?
Happy its working don't get me wrong but no issues would be best ^^
I've got your same model and I use this to get back to stock: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml
If you're running rr and everything works you don't need to do anything just stick with it.
gabriwinter said:
I've got your same model and I use this to get back to stock: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml
If you're running rr and everything works you don't need to do anything just stick with it.
Click to expand...
Click to collapse
Hey, thanks for the input, I did use that when i was having issues but it still caused that crashing at the connection screen issue sso i dont know why it would work for you and not me, perhaps i needed to get it to a working state before i could downgrade again? I dont really want to try it out now and see, the crashing issue seems to be infrequent so its possible its a different issue (software conflicts or ram overusage maybe?). I'll keep using it and see what issues develop