Hi all
I can't get a Mobil/cell connection when using roms like pa or catalysm. I also don't get a pin request. On stock everything works fine, carbon Rom was also fine.
Any ideas?
Sent from my Nexus 7 using xda app-developers app
same here, with a Samsung Galaxy Note 2.
It happened with several Android 4.3 & 4.2.2 ROM (my fav is PA).
Finally I gave up und went back to stock and then to a slimmed near-stock 4.1.2 ROM (Thunder Lite).
Suddenly and ever since there are no call in/out problems anymore.
Conclusion: for my Samsung device I suspect driver/or radio incompatibilities. I'll wait for Sammy to release a proper 4.3 stock ROM.
But that shouldn't be a problem for Nexus 4.
ok i finally made it.
The Problem was the Recovery!! The latest teamwin recovery was installed. Now i changed to clockworkmod and everything is fine.
Mayby the recovery was the problem or something went wrong on install.
but now its working:victory:
I always use CWM and PhilZ Touch (based on CWM), and had never problems with the Recovery.
Related
Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP
What twrp version?
xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM
How long has it been doing this/at what point did it start?
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.
Sorry, didn't read your whole post and missed the rc2.
jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.
It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.
cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers
Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!
emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.
Bought an unlocked Galaxy S4 from Tesco a couple of days ago and decided I'd try a couple of custom roms out pretty much as soon as I'd got it. I rooted it fine, installed cwm and thought I'd successfully backed up the rom it came with. When I tried to install the most updated stable version of CyanogenMod the phone wouldn't boot up at all. I believe I'd done it properly, as in wiping Dalvik cache and everything before and after installing (not sure if this is correct now), so I was a bit confused. Then I thought the best thing to do would be to restore the original rom but it said it couldn't find any files? In the end I managed to get a nightly version of cyanogen working but I really want the original Samsung version back on so I can properly try out the features. I've tried installing Samsung's official firmware for my device but it won't successfully install (it comes up with install aborted on cwm). Has anyone got any ideas on how I can get it working again? I'm considering taking it back to Tesco to get it replaced but now I have a working and rooted rom installed, it's unlikely that they'll take it.
Eaqq22hjwj .r, kyc C. U
Sent from my SGH-M919 using XDA Premium 4 mobile app
Just go to sammobile and fill in the boxes and that should show you which one you need.
Its probably xxuemk8 you need, then its "hello knox" ......lol
Sent from my GT-I9505 using xda premium
Hey guys. GOt my AT&T s4 here. first one i got couple weeks ago got the MK2 OTA and downloaded just fine, never got TWRP thru GooManager or CWM thru ROM Manager to work n install a recovery. SafeStrap is the only thing i had gotten working. Phone ended up getting wet, switched the board inside with that from a slightly older s4. this one came with the MDL firmware. However this time TWRP thru GooManager worked. So i installed couple other recoveries that wouldnt work before, one with Auto-Loki feature and the other was SafeStrap. With SafeStrap i installed two versions of CM11, none of which got beyond a black screen. Also i have little to no signal since dealing with MDL. Tried to update to MK2, but this time i get a reboot 2 my custom recovery followed by Status 7 error. I am interested in trying out a CM11 ROM, as well as maybe one or two TouchWiz ROMS. Mainly CM, really love the Torch app. What do i need 2 do in general to accomplish this? Ive got ODIN, pretty sufficient experience rooting and modding phones,so not a completely dummy here. Was wondering if i maybe needed to flash a kernel to get those CM ROMS working. any guidance is extremely appreciated.
You were trying to use SS. If you would read, you would know that only 4.2.2 TW and GPE ROMs work with SS unless you have the latest SS, but then again no AOSP, AOSP, CM or MIUI will work. Since the new board is able to have a custom recovery because it is pre MF3, use that to flash those types of ROMs .the error 7 is because you tried to OTA update with a custom recovery. Can't do it.
You say you are not a noob, but I disagree. Every concern you have mentioned is on the first page of both the QA section and general section. Read before you brick.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I'm using a Galaxy Note 3. I've flashed it with a ROM called X-Note which was really great! And it had 3 options for custom kernals to use. I can't remember which one I chose, all I remember is the other two seemed to prevent my phone from booting. (maybe the issue, I'm no expert).
And now I have recently flashed CM11 via temasek's build and it's working very well indeed. The thing is though, they seem to have their own kernal that I can use. I'm not though, I'm just wondering what it is and if I should try using it.
From my experience some kernals can stop the phone from booting. Is this true? Maybe it was just coincidence for me? Can anyone explain?
Reynbow said:
I'm using a Galaxy Note 3. I've flashed it with a ROM called X-Note which was really great! And it had 3 options for custom kernals to use. I can't remember which one I chose, all I remember is the other two seemed to prevent my phone from booting. (maybe the issue, I'm no expert).
And now I have recently flashed CM11 via temasek's build and it's working very well indeed. The thing is though, they seem to have their own kernal that I can use. I'm not though, I'm just wondering what it is and if I should try using it.
From my experience some kernals can stop the phone from booting. Is this true? Maybe it was just coincidence for me? Can anyone explain?
(as a side question, X-Note also came with a custom version of TWRP. I'm thinking of going back to Clockworkmod recovery as there's a few new ones on the GN3 XDA threads. What would be the easiest and cleanest way to do this?)
Click to expand...
Click to collapse
temasek's kernel is very good and yes flash it great for battery
use this cwm install with twrp or odin up to you i used odin
Hello,
I have a UK unlocked, GT-I9505 that had a broken screen, I bought a new black edition screen (dark black not black mist) and replaced it. Previously there was an AOSP 4.4.2 ROM on it that worked fine and everything was happy and good. I then upgraded to a AOSP 4.4.4 ROM which stopped the touch screen functioning (it displays, but no touch), and also tried a 4.4.3, same story.
The touch screen works in TeamWin but anytime it gets on the OS it just stops taking input.
Any help/advice would be massively appreciated
It almost sounds like you placed a different type of touchscreen in your phone and you got lucky it worked in the 4.4.2. It sounds to me like some drivers were changed after the 4.4.2. versions.
If your touch screen works in the recovery, then it's definitely software related.
Do a full wipe in the recovery and flash the rom again. If it still doesn't work, try a different rom (preferably TW based, because you are already on an aosp rom).
Lennyz1988 said:
It almost sounds like you placed a different type of touchscreen in your phone and you got lucky it worked in the 4.4.2. It sounds to me like some drivers were changed after the 4.4.2. versions.
If your touch screen works in the recovery, then it's definitely software related.
Do a full wipe in the recovery and flash the rom again. If it still doesn't work, try a different rom (preferably TW based, because you are already on an aosp rom).
Click to expand...
Click to collapse
Thanks, I've tried full wiping, I'll flash a TW (TouchWiz?) rom and see if that works
jamie_ap said:
Thanks, I've tried full wiping, I'll flash a TW (TouchWiz?) rom and see if that works
Click to expand...
Click to collapse
Hi,
Yes TW stands for TouchWiz, and I agree with the person above there. As it works on recovery, it should work on system. Just try flashing another ROM, and the best would be go back to the ROM you were IMHO. At least it worked right .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
XxLordxX said:
Hi,
Yes TW stands for TouchWiz, and I agree with the person above there. As it works on recovery, it should work on system. Just try flashing another ROM, and the best would be go back to the ROM you were IMHO. At least it worked right .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
Don't seem to be getting anything working , I'ved tried what I believe to be the 4.2.2 ROM I had working but as soon as I swip install on TeamWin it insta-power offs and then reboot into TeamWin :/