Develop Bugs

[Q] I download it a rom and it won't fully load

I finally decided to flash a new rom since my note 2 after year and a half started to seriously lag on me. I downloaded via goomanager the following rom Bam 2.0 rc3 20140304 kitkat l900. zip along with pa gapps stock 4.4.2 20131215 zip. I made a stupid mistake of not doing a backup since I thought that TWRP will save my last backup. When I flash the rom they seem to be working but when the rom is trying to activate my mobile data service, it just lags for a long while, and at the end says that activation can take a few minutes. After a long while it tells me that it failed to connect. I am stuck, i have tried reinstalling various stock files via odin but to no avail. Now I have also retry using the galaxy note toolkit v 4.1.0 but I can't get to the usb debugging mode since the rom won't load all the way. Does anybody now what I did wrong? Or how can I fix this problem? I have been reading all kinds of posts and try many solutions, please help. Thank you in advance.

[Q] Q & A BrokenPop [5.0.2][official] Dialer not working ?

Merry Christmas to all!
JLM, have posted similar on your other site.
Having a problem with the BrokenPop 5.0.2 on my L900 (Sprint Note2)
I can't seem to dial out with this rom. I get popup saying 'Unfortunately, Dialer has stop"
Are others seeing this problem? Is this an rom issue or a setup issue on my end?
I don't expect a daily driver from an early alpha of this rom and do expect issues but I would hope that I can at least make phone calls, after all, the Note 2's primary function is a phone
What I have done so far.
DL and installed rom twice. Both DL check via MD5 OK
Using Philz 6.07.9 recovery
1. Backup internal sdcard to pc
2. Factory reset / Install new rom option
3. Wipe/format internal sdcard
4. Reboot recovery (selected yes to restore root notification)
5. Install rom
6. Boot rom
7. Boot into recovery
8. Flash Gapps
9. Did minor setup of things like Wifi, Google Login, Play Store, DL ES File Manager.
10. Try to make phone call using dialer (phone icon) and get 'Unfortunately, Dialer has stop"
11. DL another free dialer from Play Store.. same error message.
I'm open to suggestions on how to get this to work.
I do like what I see from my little tour around this rom, but not being able to make calls is a major issue for me even for an alpha release. For now I have fallen back to my trusty Community Rom 4.4.2 which has been rock solid for me.
Thanks

bump.... a few people have viewed this posting .. anyone else having this problem? I have since try to install once again.. had some limited success with dialer, but then problem returns. even made a nandroid of when it was working.. still my favorite early lollypop rom for the l900

I installed Broken5.0.2, ran it for 24, and found it seemed to be one of the least reliable functioning loli roms for L900. I personally am preferring the LiquidSmooth 12-23 nightly. The LS rom has overcome the wifi/screen off hotboot bug, the keyboard bug, but still needs the manual GPS fix. Right now it offers hands down the most functioning options at this particular time and the phone is semi reliable??? Lol its doesnt FC but its buggy.
My two cents ... Cheers!

I've tried LiquidSmooth 12-23 nightly also.. one thing I had issues with was I have a OTG usb drive and did not find a way to unmount it. Did you find that function anywhere in LS?.. Other issue I have is no XPOSE support right now.. and I'm not a fan of the AOSP messaging pgms. Lots of things I don't like about TW .. but they make a nice messaging pgm
I did see a semi-workaround where you click on the carrier setting and it kinda resets the capability to make calls.. kinda hokey.. but it seems to work.. Lolllypop is still very early.. and I guess these are the growing pains for being alpha testers. Hopefully over time it will get more mature. Back on 4.4.2 for now.. everything works.. the thing is huge.. over 2gb nandroids using high compression.. but hey, everything works.. Thanks for responding.

[Q] Unlocked Galaxy Ace 2 + new ROM = lost unlock?

Hi everyone. I received my very first Android phone a couple of days ago, a Samsung Galaxy Ace 2. I did some research on the Android OS (my phone came with Gingerbread) and I found out about Cyanogenmod. So today, I installed C11 (found it right here http://forum.xda-developers.com/showthread.php?t=2568105) after a lot of sweat and blood... And I got it to run nicely, but I noticed I can't get my network to work. The phone was previously unlocked (I bought it used), and when I first tried my SIM on it, it worked.
When I first had to install CWM in order to be able to install the ROM, I succeeded in rooting it, and I noticed that the phone was still rooted after flashing it (though I don't know if that came along with C11). But anyway, I can't get my network to work; I removed the battery and the SIM a couple of times, but it didn't work. Now I don't know what to do. Could anyone please give me a hand on this? I know nothing about Android. Thanks in advance.

CM11 requires JB (4.1.2) - Sound like you flashed CM11 onto GB (2.3.6)
This can't work.

The thing is that I was trying to install an AOSP ROM (found in these forums as well) before trying with C11, and I wiped the data, formatted the system... So the phone was left without an OS. I didn't just "update" the OS, if you know what I mean. And C11 is working fine except for the mobile network.
EDIT: If I install a clean JB 4.1.2. and then restore to my current CM11, do you think that could solve the network issue?

Again: You need JB! With JB there are also other partitions which are needed to be new (on JB)
And Yes - Data restoring could work - But not recommended.... I would do an clean new install...
Please do not start an discussion... again: You needed JB.. (just to be sure)

Uhm, I never intended to start a discussion, I was trying to explain what I did. Thank you for replying anyway. I'll let you know if I get the network to work.

Sorry - I don't what to sound outrageous... But those questions were asked to many times... Here on XDA ACE 2 section...

[Q] Can't turn wifi on. Tried with 5.1 and 4.4.4

I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..

stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process

Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.

stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)

Camera frozen on black screen no matter what I do

I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!

Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.

You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck

Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.

Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.