Wondering what im doing wrong? I've flashed 3 different ROMs so far and none of them would use my sim card.. The one i wanted to use was DN3 or DN4. I flashed the add on but im still unable to use my sim. In my stock ROM ,which im using now doesnt allow me to change the voicemail number...so theres no way to write it down, this was the same in DN4
Sent from my SGH-T889 using XDA Free mobile app
for anyone else having this issue, i replaced TWRP with the latest CWM and flashed the rom i wanted to use. Sim and mobile network works the way it should...so it could just be your recovery.
I ran into this last night too. To try and remedy it, I flashed the latest nightly, wiping the davlick, and cache before hand and it worked at first. for a few minutes and then went back to not recognizing the sim. After looking at NovaxxBite's post, I reflashed CWMR even though I was on the latest version and I am going to attempt to reflash the next update now. I'll update my post if it works for me..
Related
Basically everything is in the title. My wifi just doesn't work, I can't connect anywhere! using a lot of data on things that I could really be using wifi for. I've tried different rom's including the latest nightly cm7, the problem started on nightly 48 latest being 50. I'm now using miui and the problem still occurs. Anyone got any idea?
Sent from my MB525 using xda premium
Look like every roms not work with WIFI for you and is this only issues from custom rom? Have you wipe the data/cache in your quest of finding the root cause? How about retail untouch stock rom.
Before sending it back to the store for repair. Could you try flashing retail stock rom to your Defy original state and wipe it in stock recovery. See if it work again and report back.
I assumed you know all the steps of downgrading, flashing and recovery things yourself.
Has anyone tried this? I got it tonight and am having a hell of a time. I installed Gummy on slot 1 and 2 and everytime I boot to it I loop at the Google screen and have to while and restore through recovery. It worked once but I ****ed it up with a mod now nothing works. I've factory reset and deleted both slots.
Any ideas?
Sent from my Transformer Prime TF201 using xda premium
Hi,
I have no problems with it. My PhoneRom is CM9 and Slot1 is MIUI. Have you tried it with another Rom?
Gesendet von meinem Galaxy Nexus mit Tapatalk
I too have not had any problems. I have MIUI on ROM 1, Codname ANdroid on slot 2, and CM9 on ROM 3 with Wookie as my stock ROM. No problems, can easily switch between them. GO to your SD card, find the bootmanager folder, and delete the folders for the ROM's - maybe something was bad in the slots.
I checked the bootmanager folder after i whiped the slots out and all was left was a empty android.secure folder.
I'm going to try some other ROMs today, it just doesnt make sense that Gummy does this now after it worked fine the first time =\
What version of recovery are you guys using? I downloaded another ROM And tried using Boot Manager but got the same issue. I decided it must be my actual phone rom, so i tried to whipe and install Gummy, but it threw an error related to my version of CWM. I upgraded and am trying now with Gummy as my primary ROM
Upgrading my CWM seemed to work.
Anyone know how to sync texts between slots?
I selected the slots but the messages didnt take
Can't get the syncing messages or call log to work either. It's also not allowing me to flash kernals on slotted roms.
DroidHam said:
What version of recovery are you guys using? I downloaded another ROM And tried using Boot Manager but got the same issue. I decided it must be my actual phone rom, so i tried to whipe and install Gummy, but it threw an error related to my version of CWM. I upgraded and am trying now with Gummy as my primary ROM
Click to expand...
Click to collapse
I too ran int osome issues, then i realized that i am running AOKP milestone 6 and was trying o put a JB rom on slot 1.. Both ROMs have to run off the same kernel. So if you have ICS as your main ROM then you must use an ICS rom for your slots. I dont know if this helps any1, but now I am runing smooth
I am new with nexus.is boot manager work with this phone?
Sent from my GT-I9300 using Tapatalk 2
Hell I just noticed something that never happened to me before.. I just wanted to switch to a new ROM I was using paranandroid and I downloaded cm10 and went into recovery and it showed a bad download(I had a nandroid already so just restored it but then downloaded an older version and went into recovery and it told me the same thing so I downloaded a kernel kuz the ROM was eating the battery and sometimes its the kernel so I downloaded one and flashed it and it told me the same thing so its a really big coincidence that three different files gave me the same error and I just started using paranandroid this morning before I flashed parandroid everything was good everything flashed right but after flash in that ROM it started doing that luckily I had a very old version of cm10 so I flashed it and it flashed it properly so right now I'm using a month old cm10 version and I don't want to update it with cmdelta updater because I don't wanna have to waste more time recovering stuff I'm frustrated so yea anyone have a solution for what's going on with the files?? Or anyone have any idea why the phone started misbehaving??
Sent from my SGH-T999 using xda premium
Paragraphs....
Yes please, and punctuation.
Verrry difficult to read.
Try a different recovery.
Odin back to stock if that doesn't work.
Sent from my SGH-T999 using xda app-developers app
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
tpag02 said:
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
Click to expand...
Click to collapse
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Almite said:
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Click to expand...
Click to collapse
yes, i have. I also got back to stock, used an older recover, flashed with an older version of CM and nothing. I first was using CWM 6.0.3.7., after that I used 6.0.4.3, then an older version of TWRP but nothing. I also tried booting to system without flashing gapps.
With stock ROM everything works just fine.
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
iamdofus said:
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, thank you, but it didn´t work.
it happened to me the same thing months ago. never had solution. still in waiting. attempt internal and external SD format. and followed the same. I hope someday they can come up with the solution! : (
i have the same problem too
I try to install multiple ROM 4.2.2 and I could only install one version AOKP Milstone JB1. I also worked the other. however all 4.1.2 rom if I worked. I could not install any 4.3 and 4.4 now does not know what is the problem but I've tried everything! anyone found the solution yet but I see I'm not the only one! (excuse my bad English, not my language )
Well you all are right, I am also using shadow mastery (stock rooted rom). Just because I had the same problem sometimes stucking and rebooting and sometimes after going in gallery. Even I can't use 4.3 and 4.4 roms. Anyone have to contact with room developer or someone who know about this problem.
Sent from my SGH-T989 using xda premium
You might want to find an Official T-Mobile or Telus 4.1.2 or 4.0.3/4.0.4 rom that is Odin flashable, not one that has been custom made/flashable from recovery - then just start over after getting back to true stock, change to TWRP or CWM recovery that is 4.3+ compatiable, root and then flash rom/gapps etc.
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
abdullaha said:
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
Click to expand...
Click to collapse
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
dicksteele said:
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
Click to expand...
Click to collapse
I thank you for your suggesion but other than what you have said, do you have any other ideas on what I'm doing wrong?
abdullaha said:
I thank you for your suggesion but other than what you have said, do you have any other ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Not a clue.... Sounds like everything is good. I don't think you're doing anything wrong operational. Your phone just ain't happy.
I think it wants what it wants. And it's appearing it's not a 4.4 ROM at the moment.
That's what it's looking and sounding like to me.
abdullaha said:
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
Click to expand...
Click to collapse
Are you sure that you have a kernel that support cm ROM? Just curious.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Format system with your other wipes.
What he ^^^^ said. You probably have so many fragments, wipe system three times.
And internal storage wipe may be needed as well...
But MAKE SURE you have a full backup of a complete and working rom BEFORE wiping....just in case...g
Sent from my SGH-I317 using XDA Premium 4 mobile app
dicksteele said:
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
Click to expand...
Click to collapse
Thank you! You were right! I switched back to stock and rerooted and redid the flashing and it worked like a charm! I have no idea why it didn't work the first time. Thank you for your help.
Sent from my T0LTE using XDA Premium 4 mobile app
abdullaha said:
Thank you! You were right! I switched back to stock and rerooted and redid the flashing and it worked like a charm! I have no idea why it didn't work the first time. Thank you for your help.
Sent from my T0LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Glad it worked. These phones are tanks, hard to crush them. But they will let you know when they are not happy with what you did.