Develop Bugs

[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)

Galaxy Note 10.1 SM-P600 Reboot Loop

Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.

Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?

Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.

ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!

Transfer *EVERYTHING* To A New LG?

I just got a new G3 because my old G3 was having sim card reading issues. I'm trying to transfer everything from the old to the new*– and I mean everything: ROM, apps, contents of the internal SD card, etc. etc.
What is the best, most painless way to do this? The old phone, fwiw, is rooted with Cloudy installed as well as G3 Tweaksbox and some Kernel tweaks; the new one I haven't touched yet and is fully stock.
Thanks!
- Andi

Come on, anyone?

phnord said:
Come on, anyone?
Click to expand...
Click to collapse
Do a full backup in recovery, move it to the SD card and restore it in the new phone's recovery. Are you sure that the sim card issue isn't a Rom issue? I had this problem on Fulmics, flashed DU and had no problem since.

alaskenikeni said:
Do a full backup in recovery, move it to the SD card and restore it in the new phone's recovery. Are you sure that the sim card issue isn't a Rom issue? I had this problem on Fulmics, flashed DU and had no problem since.
Click to expand...
Click to collapse
I'm fairly certain it's not a ROM issue, as my phone was working fine on Cloudy for months, but after a tumble started having issues recognizing the SIM, even after replacing it with a new SIM.
The issue comes up upon reboot; it seems that if I squeeze the phone tightly during the reboot around where the SIM card is, it will recognize it and then everything works fine, but if it was booted without being squeezed it won't recognize the SIM until a squeezed-reboot.
That seems like a pretty definitive hardware issue to me?

phnord said:
I'm fairly certain it's not a ROM issue, as my phone was working fine on Cloudy for months, but after a tumble started having issues recognizing the SIM, even after replacing it with a new SIM.
The issue comes up upon reboot; it seems that if I squeeze the phone tightly during the reboot around where the SIM card is, it will recognize it and then everything works fine, but if it was booted without being squeezed it won't recognize the SIM until a squeezed-reboot.
That seems like a pretty definitive hardware issue to me?
Click to expand...
Click to collapse
Yep, really seems like a hardware issue. But after you do your full backup and put it on the new phone you could try to install a AOSP Rom just to try out, but thats up to you.

LG G3 D855: Problems after rooting (SD card, FM radio, Joyn service)

Hi all
I just got a new LG G3 from T-Mobile which came with Marshmallow (30b). I have inserted my 64GB external SD card from my previous G3 (its' display stopped working all of a sudden) and started to set up the new phone. All went quite well until I have rooted the phone following the steps in Root + TWRP Marshmallow D855 (30b).
Now I have a rooted phone with TWRP, which is good, of course. But I think during this process the original kernel has been replaced by another one, is this right?
1st problem now is the 64GB external SD card which is not usable any more, even after formatting it through the phone itself. I have inserted another 12GB card and this is working as expected. The 64GB card is working normally in a card reader.
2nd problem is that the FM radio app stopped working. It is only giving strange messages like "Mock: RADIO_ON", "Mock: UNMUTE", "Mock: TUNE" and so on without playing anything at all. I have uninstalled and reinstalled the radio, no success.
3rd problem is the annoying Joyn (RCS) service. I can disable it in the settings. But after a reboot it is turned on again.
I am not sure about the 3rd problem but the first two may be very well related to a kernel lacking support for the big SD card and the radio HW, right?
Any suggestions how to solve these?
Can I flash another kernel without losing TWRP and root again? If so, which one?
(Is there a Marshmallow custom ROM with the original camera and FM radio support? This I can find out by myself of course)
Thanks and regards,
xrig

Had the exact same problem. I have the international model G3 32 GB variant which I purchased 2 weeks ago. It worked good till I rooted it. FM radio kept coming up with mock & couldn't get any functionality of the radio, tried rebooting, taking out the battery & didn't work. What solved this problem was downloading the 30b global Marshmallow rom & flashing it. FM worked perfectly, even after rooting & had no issues. I'd recommend flashing the 30b rom with a complete wipe.

Stevo001457 said:
What solved this problem was downloading the 30b global Marshmallow rom & flashing it. FM worked perfectly, even after rooting & had no issues. I'd recommend flashing the 30b rom with a complete wipe.
Click to expand...
Click to collapse
Thank you very much for the suggestion. Did you use the above rooting method again after flashing the global stock rom? And can you use exFAT on your external SD card? It seems that Hacer Permisivo is breaking the exFAT support.
What global 30b did you actually use, the kdz corresponding to your IMEI from devtester.ro?

Maybe a custom kernel or ROM will fix your problems, and also formating your sdcard on fat32 will fix it.

T800: Can't complete boot when using 7.x.x roms

I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.

mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.

Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.

mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.

The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.