Getting dialer problems - AT&T, Rogers HTC One X, Telstra One XL

I've been trying to fix this problem for 2 days now, I tried installing back to stock, reroot and unlocked. I slapped Cleanrom on and it hasn't fixed the issue. I was hoping if the problem could possibly be fixed, or if its a hardware issue i want to know what steps i can take to deal with it. As of right now i cant make any calls without it foreclosing on me.
Thanks

Weird. Tried clearing cache? Did you have this problem when u first got the phone? When did all start?

It was 2 days ago. I tried almost everything, but still a no go. I have pmed some people who have experienced it in the past, but their on 2.20 now, so i might consider it if its going to fix the issue. I rather not though

I'm getting that same problem too, also i can't properly add phone numbers to my phone or sim. This is getting frustrating, hopefully someone can elaborate on this..

Do you have any accounts syncing? Maybe if you delete all the accounts that sync contacts? Maybe try it without a SIM card in?

If you are using CWM and flashed CleanROM (and maybe other ROMs), then that is why you are having this issue. Its a known issue, and it clearly says in the CleanROM top post to not use CWM, and to use TWRP.
Also, this is a double post. Somebody posted a fix in your other thread. Go look at it. Now see why double posts are confusing and annoying?

solution
It happened to me too and now I have a solution.it happened to me when I installed a rom(don't want to mention the name).ok do this
Root ur phone unlock bootloader and install cwm not twrp.now clear cache,data,system everything and install any rom(even stock)using TARP(dont forget to clear everything in twrp also).
It worked seriously for me and believe me.if I helped u please hit thanks button

saketh91 said:
It happened to me too and now I have a solution.it happened to me when I installed a rom(don't want to mention the name).ok do this
Root ur phone unlock bootloader and install cwm not twrp.now clear cache,data,system everything and install any rom(even stock)using TARP(dont forget to clear everything in twrp also).
It worked seriously for me and believe me.if I helped u please hit thanks button
Click to expand...
Click to collapse
I tried this method, installed CWR over TWRP and installed cleanrom 4.5, then my phone would reboot continuously. Did you experience this?

Are u guys doing FULL wipes as stated above?? Do a full wipe, cache, dalvik, system, factory reset/data. Flash a rom and dont restore anything. Just boot it up and see. Im fairly certain it wont mess up after that.

Did you flash KingCobra then started having this issue? I have the same problem as well right now, there is a FC.zip fix he's made that you can flash but I'm getting an error right now. Its a awesome rom tho!

as i mentioned you need to clear data,cache,system.. in cwm then switch to twrp and install a rom.installing cr4.5 or any latest roms in cwm will cause bootloop

Related

Continuous Crashes

Evening everyone-
Having some issues I am hoping someone can help me with.
I have a rooted ATT HOX on 1.85 that is having some major problems. I started this morning by trying to flash the Magnolia ROM after being on one of the Cleanroms.
I guess the download was corrupt and I received an error while flashing in CWM and was then stuck in a boot loop. I did the whole RUU deal going back and was able to get back on 1.85, root with super user, etc. but once I got back into the phone to setup I noticed that none of my contacts were syncing after signing in. After playing around a few more minutes I noticed the Messaging would crash after being open for a few seconds with no Force Close warning. Occasionally I could go into a text but after trying to respond or type anything it would revert back to the previous page.
Contacts is a complete no go. As soon as the app is opened it crashes. Same with phone. Absolutely can't use any of the three core apps.
I then tried flashing a variety of the roms and even using the different recoveries and have had absolutley no luck getting the Phone, Messaging or Contacts to work on anything. Even stock RUU 1.85! The only thing I have had luck with is the AOKP port which is working ok minus the phone audio being botched.
Any hope here? Any idea what the deal is?
Any help would be greatly appreciated. Thanks in advance!!!
Do a full wipe and install the ROM.. this should take care of it
I am also having this problem. I tried doing factory restore from TWRP 2.1.8 multiple times. Re-locked the phone and reinstall RUU 1.85 and still have issues.
Can you explain further what you mean by full wipe?
fishscale28 said:
Evening everyone-
Having some issues I am hoping someone can help me with.
I have a rooted ATT HOX on 1.85 that is having some major problems. I started this morning by trying to flash the Magnolia ROM after being on one of the Cleanroms.
I guess the download was corrupt and I received an error while flashing in CWM and was then stuck in a boot loop. I did the whole RUU deal going back and was able to get back on 1.85, root with super user, etc. but once I got back into the phone to setup I noticed that none of my contacts were syncing after signing in. After playing around a few more minutes I noticed the Messaging would crash after being open for a few seconds with no Force Close warning. Occasionally I could go into a text but after trying to respond or type anything it would revert back to the previous page.
Contacts is a complete no go. As soon as the app is opened it crashes. Same with phone. Absolutely can't use any of the three core apps.
I then tried flashing a variety of the roms and even using the different recoveries and have had absolutley no luck getting the Phone, Messaging or Contacts to work on anything. Even stock RUU 1.85! The only thing I have had luck with is the AOKP port which is working ok minus the phone audio being botched.
Any hope here? Any idea what the deal is?
Any help would be greatly appreciated. Thanks in advance!!!
Click to expand...
Click to collapse
I think I figure out how to fix our problem. I was on re-lock status and stock RUU 1.85. I proceed to unlock the bootloader, flash cwm, go into advance, and select fix permissions. I also wipe everything while I am here. After reboot, I am able to set up e-mails and sync contacts and make calls again.
Hopefully, the same will work for you too.
leo14888 said:
Can you explain further what you mean by full wipe?
Click to expand...
Click to collapse
In recovery, wipe data, cache and Dalvik.
Thanks for the responses. To be honest I did factory resets and wipes about 15 times in total...between all the various available roms, the factory 1.85 and a combination of anything I could imagine. Nothing-and I mean nothing-would work. Finally I put it as close to stock as possible and brought it back for a swap. I couldn't find anything at all to help rectify the situation or any info on what in the world may have caused it.
To those of you stuck-good luck! Sounds like it was only a handful that experienced it...hope you get it sorted. Would love to find out why it happened though!
Best of luck!!!
did anyone ever figure out the problem and how to fix this? ive been screwing around for an hour just clearing the data from anything related to contacts or google sync, and even people and still can't get my contacts to sync.. everything else syncs fine my calendar, drive, etc. just not contacts!! grr... any help would be much appreciated. if i figure it out and know how i did it i'll post so others don't waste as much time as i have.
edit: it all started when i tried to flash clean rom using CWM (it said not to but i missed that part lol).. so i ended up having to relock my bootloader, unlocked it again, flashed 1.85 RUU and then finally i was able to boot my phone past the HTC screen.. after that i booted into TWRP and flashed cleanrom. that is when i noticed contacts won't sync, phone book, sms etc. just close when i open them..
tried everything suggested in this thread and still no luck
current status: I decided to flash CWM again, and restored a nandroid backup i had from a while back.. which is a stock rogers rom. contacts r syncing fine.. question is. when i flash to cleanrom 4.0 again will it break the contacts sync again? i sure hope not.. we'll find out tomorrow lol sleep time!
ok so installed cleanrom 4.1 again today and all is working well..
i guess the solution is:
* somehow obtain a stock rogers or att rom (1.85 ruu should work for most)
* once thats installed use fastboot to flash CWM or TWRP
* boot into recovery
* clear cache, dalvik cache, factory reset / clear data
* install custom rom (in my case cleanrom 4.1)
* Reboot phone and check if ur contacts r syncing properly
such a messed up problem hopefully this helps anyone else who runs into it..

[DONE] Fix for "Preparing Sim Card..." Error for CleanROM

Hey,
Starting this thread up as a place to figure out the "Preparing Sim Card" problem.
Essentially, if you flash CleanROM 4.1 with CWM, you'll probably get this error. There were plethora of fixes out there, such as:
1. Clearing all cache (fastboot/recovery)
2. Clearing all data/force stopping problem apps (people/dialer/messaging)
3. RUUing back to stock
4. Flashing a new radio
5. Removing/Changing SIM cards
6. Trying dialer trick:
.....a. Go to Dialer (if you can't access it, clear the data in it first)
.....b. dial *#*#4636#*#*
.....c. Turn off the radio
.....d. Turn on the radio, and right as the toast appears, choose something from the drop down menu.
.....e. Run a ping test to make sure everything's alright.
7. Used TWRP to clear system/flash new ROM
8. Tried another ROM with GSM Patch
CURRENT STATUS: WORKING!!!! =D
The answer to all your problems issss........
Well, it's multi-step
1. Make sure to flash back via RUU (preferably 1.82 since 1.85 was a b**** for me to re-root T_T)
2. Make sure to unlock your bootloader again
3. Install back CWM (I know...wtf?!) <<THIS STEP IS IMPORTANT (believe it or not)
4. Go back and flash CleanMOD 3.1 or something (just anything below 4.1 should do the trick) [if just installing CleanMOD doesn't work, install the GSM Patch too!]
5. NOW install TWRP
6. Install CleanMOD 4.1
7. SUCCESS!!!
Also, thanks to tehdef, who also tried this method:
Here is what I did to break my phone.
I had the following MODS.
-AOKP 6.1
-CWM
Decided I wanted to test something on CleanROM 4.1
- Flashed CR4.1 in CWM
Got stuck in Boot Cycle and CWM would not load
1. Locked Bootloader
2. Installed 1.85 Evita RUU
3. Unlocked Bootloader
4. Installed TWRP
5. Flashed AOKP 6.1
At this point, I still had an issue. Instead of receiving the "Preparing SIM" Message, I had absolutely zero signal, and I could not "SAVE" an APN.
6. Rebooted to Bootloader
7. Reset to Factory while in AOKP
8. TWRP Loads
9. Reboot to System
My phone now has signal and full contacts and I can make calls and send Texts and MMS with no additional modifications. Please note that with AOKP Superuser comes installed and works just fine, so for whatever reason I did not have to root my device.
NOTE: YOU DO NOT NEED TO USE CLEANROM 3.1 IN ORDER TO GET BACK TO A WORKING STATE!!! Just any rom supporting the unofficial CWM should do. =] (at least I think so, but I'll confirm when someone get's back to me =D)
Thanks goes out to...
Scott for his awesome ROMs and his life lessons
kleeman7 for toughing it out and helping me through the entire thing
tehdef for helping me test out several of my theories
shackman716 for suggesting the idea that worked (it was so crazy it actually worked! XD)
and thanks goes out to anyone I forgot to mention. XD
Now, back to more ROM flashing
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
redpoint73 said:
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
Click to expand...
Click to collapse
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Error 170 is a usb communication error and is fixable. Turn off HTC sync. Check for it in running processes. If you still get the error reboot to the bootloader make sure the phone says fastboot usb in red then start the ruu.
tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
thats a driver error do u have htc drivers installed? good usb cable? tried a diff slot?
if not install htc sync let the first portion install. when it comes time for htc sync inself to install cancel. and just the drivers will be installed
tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
elsupermang said:
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
Click to expand...
Click to collapse
Well, I tried emailing and stuff, and it seems anything regarding data seems to be alright. It just seems to be the issue with phone/sms data now. I believe it's something software related as it still reads my sim just fine, and it recognizes when it gets a call. Just when I get a call, it repeatedly FCs. I might give it a try though, so thanks!
redpoint73 said:
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
Click to expand...
Click to collapse
Sorry, I had to go out for lunch, so I didn't really go into much detail. I have tried using TWRP and is still using that atm, and also tried flashing a rom with GSM Patch, which I'll edit the OP to match. Both of these did not work and I'm going to try and pull a logcat or something. Will update when I get it
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
tehdef said:
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
Click to expand...
Click to collapse
i feel like the dialer and the contacts are linked together. if we can solve one, we can probably solve both. I looked in my catlog and they stated that they couldnt find a particular file/db in the /data/data folder. ill look into this and see what happens
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Well, hopefully that's it.
---------- Post added at 01:12 PM ---------- Previous post was at 01:06 PM ----------
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
I haven't unlocked my BL again because I'm at home, and frankly, I'm not sure how the process is changed once I already ahve the Auth Key, and if I can do it quickly here from work.
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
jojojohnson7410 said:
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
Click to expand...
Click to collapse
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
tehdef said:
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
Click to expand...
Click to collapse
That's a good idea, maybe once Scott reads his thread he will have some input for everyone.
Sent from my HTC One X
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
...actually, tehdef, did you ever unlock your bootloader with the one-click without HTCDEV unlock at any point in time? This might help me out cause this might also be the problem. Thanks!
jojojohnson7410 said:
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
Click to expand...
Click to collapse
Clearing contacts seems to work. My list is now populating.
Attempted to send text. Prepairing SIM Card returns.
---------- Post added at 02:23 PM ---------- Previous post was at 02:12 PM ----------
Unfortunately the Android.acore process has stopped when I tried to sync my Gmail contacts after clearing everything.
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Something is corrupt.
I want to put AOKP back on the phone, because I honestly think it's Sense related.
natediddydude said:
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Click to expand...
Click to collapse
lol at the shaking your phone really hard XD
Anyways, I have a theory:
there are two ways we COULD possibly fix this:
1. obtain a rom that has root. Get root explorer or somehow get into /data/data/com.android.providers.contacts/databases/ and delete .db-journal if its in there. Do this in conjunction with clearing out the data of all the affected apps and their sister apps (i.e. Contacts, Contacts Storage, Contacts Sync) and force stopping all of them. Can't test this cause bootloader refuses to unlock atm)
2.lock the bootloader, RUU to 1.82 (NOTE: NOT 1.85!) and try to unlock using this: http://forum.xda-developers.com/showthread.php?t=1734558. REMEMBER take out your SIM card! but maybe this might help not 100% sure if this is what caused it for me, so it's best to consider it too. Can't test this right now because I am stuck without a BL unlock and i can't get root on this firmware
*EDIT* ahahhahahah i lied. no sim card needed, so why would it rely on mobile data? ahh im such a silly person alright here goes!
i'll let you know when i get out of my pickle, but it might be a while. That, or i might just get pissed off enough to just go to the store and look like an idiot cause i really do feel like one right now and I need to get the phone working T_T
Keep checking back!

Jelly Bean ROMs caught on boot animation

Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
kailehu said:
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
Click to expand...
Click to collapse
o-l-a-v said:
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.*An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine*(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
I'm sorry to hear that but I'm also glad it's not just me, and wouldn't be a huge stretch to call me a newb.
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
Click to expand...
Click to collapse
Unfortunately, I've tried both recoveries already. I've gone through each step every time and I've never done it that specific order consciously, but I feel like I must have just by chance in all the times I've tried this. I'll try again though exactly like you listed and see what happens. Thanks.
No dice. I'd like to give more info than that but I don't know what else to try.

TWRP fails after update

So guys, yesterday I updated twrp (cwm) on my i9505 and everything worked fine.
this afternoon i suddenly couldnt use my phone anymore because i got systemui fc's messages every 3 seconds.
i reflashed the rom, cleaned cache +dalvik but it still wouldnt work.
so i thought: hey, you did a complete backup yesterday, why not use that.
well, seems that this didnt work out so well.
its always telling me failed when trying to restore either /system or /data (boot and efs works fine).
i dont exactly know whether i made the backup before or after the update, but either way i do think that it SHOULD NOT be a problem (im looking at you, devs)
do you guys have any idea on how i can possibly use my old backups? i downgraded again but it still says failed everytime
any help will be greatly appreciated.
oh and yes, i did use the search, but all suggestions that help didnt with me
hi.
i'm not a pro/dev, but by flashing rom or restoring backup i think you are missing a point.
i think, you need stock recovery too to have phone fully reset. in case you flash Stock rom i think it also flashes stock recovery too. but incase not, the old recovery and changes you made to custom recovery are still there. so you maybe is facing that problem.
as i mentioned above that i'm not pro/dev, so again just trying to find the exact problem/point maybe you are missing or i could be wrong too. all i mean is that updated recovery is still there. see in case you can flash stock recovery and stock/custom rom again. i hope you get the point/idea what i mean to say. try it and i think you'll not get the error.
but do not do anything in case you are not sure/aware about what you are doing.
i hope it help.
no, i dont need the stock recovery to fully reset it. trwp can do that too.
actually my point was that it denies to restore that backup and i have no goddman clue why.
(so nothing about roms or so, all that works perfectly fine)
ok i fixed it, it seems like the last backup i made was faulty so i just took an older backup. never had an issue like this before
Thread closed - OP request!

screwed up phone bad,think its some kinda bricked HELP PLZ NOOB

So I had cm12 installed and something happened to where my.phone was lagging so I said screw it and reflashed, while something happened and now I tried to while everything. Well I think I did something wrong because I lost all my apps in the app drawer,but when I go into file manager all my stuff is still there,but now the last couple times I tried to reboot the charging light was flashing red to yellow, but when I take the battery out and put it back in it reboots fine back to the screwed up home screen. Still with all my apps and pictures. Viewable in file manager.someone please help I'm freaking out thinking my phone is screwed up for good ....
Very hard to understand you. What ROM did you flash to now? Does TWRP work, can you get into TWRP?
Yes I can get into twrp,basically it threw me back into my cm12 ROM with none of my apps,and I tried to reflash Google apps and it didn't work,so if I can get into twrp is there a way to fix this by doing like a general full factory reset? And if so exactly how do I do that? I dunno this sucks....I dont wanna try anything else until I kinda have an idea what to do, don't wanna screw it up anymore
kjhrezjr said:
Yes I can get into twrp,basically it threw me back into my cm12 ROM with none of my apps,and I tried to reflash Google apps and it didn't work,so if I can get into twrp is there a way to fix this by doing like a general full factory reset? And if so exactly how do I do that? I dunno this sucks....I dont wanna try anything else until I kinda have an idea what to do, don't wanna screw it up anymore
Click to expand...
Click to collapse
If you don't know how to factory reset you probably shouldn't be flashing in the first place. I highly suggest just doing a clean flash and flash Gapps right after you flash CM 12. In order to wipe data, you just click wipe in TWRP.
No I know how to factory reset lol.it's just I did that and when it would go to restart I got little error code up in left hand side of screen. But it doesn't matter because thanks to androidrootz I downloaded New firmware connected it to pc and completely reinstalled operating system. So I'm not rooted or anything and I'm back to square one, .but much better than where I was at.
If your custom Rom was bugging out it could have been a corrupted download. Sometimes all you can do is start from scratch. If you want to flash custom, you need to expect these things. Remember that this is a development site. I have seen where the same Rom acts differently on the exact same phone model. This could be due to a variety of things such as microscopic differences in hardware (this is one of the reasons phones of the same model handles being overclocked more our less than others), settings, tweaks, or apps installed.

Categories

Resources