Wow it has been a long 24 hours. I want to go ahead and appoligize,...I have a really bad memory. Sunday I went from Task650 AOKP (Android 4.3) to Validus 4.1 (Android 4.4.2) . I cleaned everything before flashing and then installed the supersu and gapps as stated in the op. Yesterday I found out I had a wifi problem, not sure if I was able to connect before or not. from this point until I try back to stock i get a popup stating that media has stopped or media storage has stopped and it happens progressively more often as time goes on. I tried dirty flash and it didnt work so i thought i would try a new kernel. I had never tried flashing kernels before but i read up on it and seemed very simple. so I flashed Ktoonsez KT747 kernel, i also flashed EMJB modem to see if there was a difference. afterward when i looked in settings - about phone under kernel version it said (not exactly but best i can remember) 3.4.77-cyanogenmod .... dirty KT747. i couldnt find anything about this but i didnt think this was good. i dont remember if i tried reflashing or doing anything to fix it right then or not. but at some point late yesterday after a reboot my lockscreen was transparent (might have been before), background was black, status bar was gone, when i recieved a call there was no popup it would just ring but i could go in to phone and it said return to current call but i couldnt do anything to answer. I could call backthough. i did still have notification on the lockscreen. xposed fimware was also disabled so i figured that ruled out any issued from it. I was getting aggrivated. i read up a little more. read suggestions to flash back to stock periodically. I figured i should try that. BIG MISTAKE!!! I still dont know why it didnt work but i tried plenty! before flashing the EMJB modem I had DLK3. so i thought that meant i would be ok to return to stock because i never upgraded my bootloader. when i flashed it with odin it went all the way through and restarted the phone but got stuck on samsung logo after at&t splash screen. so i odin flashed cwm booted into recovery and restored a nandroid backup (life saver!!). this worked and i was back on AOKP with DLK3 modem but not satisfied and feeling a little safe to explore knowing that i had a safe return plan unless something went detrimentally wrong. so with my modem saying DLK3 and my rom on 4.3 instead of 4.4 i decided to try back to stock again and use the true stock instead of rooted stock. (WORSE MISTAKE!!) ODIN failed. my heart dropped i was terrified. I decided to download and try KIES but it wouldnt connect to the phone after downloading the firmware. I tried odin flashing root stock again and if finished and stuck on samsung again. so i flashed cwm and sideloaded Validus to get back to 4.4.2. seems to be working good but now to get to the issue. ater i got it back working i got a notification that sdcard was removed unexpectedly. before anyone directs me to one of the hundred threads with this title my issue is with internal storage not the external sd card. i have seached it quite a bit but i cant find anything like my situation. it seems that if i go to /storage/sdcard0 it is empty but i can access it from any of the following locations and its not empty.
/storage/emulated/0
/storage/emulated/legacy
/sdcard
/mnt/sdcard
I do not understand this.
Anyone that has any helpful information thank you in advance.
update : it happened again today. my phone died during the night and when I turned it on just now it popped up the notification SD card removed unexpectedly except it popped up and went away really fast like 10 times. still the only thing missing is storage/sdcard0
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Related
Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though
Here is my problem on 4.3 roms, i have no trouble installing them and the load up perfectly but after i do a restart i cant get past the boot screen. It does it on all 4.3 roms, i have the latest twrp recovery latest modem and stuff everything is up to date only have this problem on 4.3 ive formatted the internal storage numerous times and always followed op instructions. i cant find anyone else with this problem any help is appreciated tia
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
joeyhdownsouth said:
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
Click to expand...
Click to collapse
im using twrp first i tried to factory reset, caches that didnt work i formated internal storage same problem everything works great untill i restart the phone then wont go past boot screen. like its not reading the internal drive even did fix permisions and wiped caches after install. Also i used the updated su to flash after still problems, beyond me no problems with older ones or tw just the 4.3 roms
I, also, am having this very same issue. I'm honestly surprised that noone else seems to have run across this issue.
Installing is never an issue, running is never a problem, but if I ever reboot, if a ROM reboots itself, I'm left stuck at the GalaxyS4 splash screen, and the only way out it to Wipe everything and reinstall.
I see youre posting from an S3, I am using an AT&T S4.
Clearly, the issue is related to 4.3...
I had that problem with an unofficial build. But that was a bad download. Do you have new phones? The mount points are different on the newer sg3's. There's a thread with a fix for that
i had that problem. for some reason it locks your recovery and internal storage. you have to wipe it and install a rom via odin to work again. thats why im staying away from 4.3
i got my phone last december so its not real new, guess Ill just stay away from 4.3 roms. my recovery never got locked it just wont boot back up after restart. thanks for all the ideas
First of all, my English is not that good, so I hope everybody understand me
I'm a flashoholic (i think this is the right expression); i flash a new ROM almost every two weeks. And, from some days ago to now i'm experiencing some problems. Here's my problem:
Problem: my phone "stucks" when I let it locked for more than some 5, 10 seconds. I lock it now, and... dead. I have to press the power button until it restarts. My phone is having trouble to find operator's network and it's EXTREMELY lagged too. It almost stucks when i try to write something on the keyboard, or draw/write my passwords on my lockscreen.
Here's my "ROM timeline", too:
ROM Timeline: MIUIBrazil v4 [4.1.2] >> P.A.C MILESTONE [4.2.2] >> TigraROM/Hurricane [4.3 leaked] >> MIUIAndroid v4 [4.1.2] >> MIUIBrazil v4 [4.1.2]
Underline = i think that this is the point
Bold = problem started
So, let me explain my history: flashing ROM's as always, I decided to change things a bit and go AOSP for a while. So I flashed P.A.C. Milestone. Actually, I've flashed first the Nightly version, but it was a bit unstable. I went to P.A.C and everything went fine. But, hey, where are the Samsung functionality? I missed it. So, after some trouble finding the right ROM to me, the 4.3 from Samsung leaked. I tried it, then. First the Hurricane, afterwards the TigraROM (Note 3 functions ). And it was ok, but was lagging a lot. Too much launchscreen redraws to handle, so I went back to MIUI (not the first MIUI on the timeline, because I've decided to go right from scratch), and then, i've noticed a lot of problems.
It was not booting up.
I've flashed A LOT of ROM's trying to solve this problem. What it was? EFS folder. I went to the TWRP file manager on Recovery and noticed that the EFS folder was empty. And no backup. I went crazy until i found an old backup stored on my PC. Restored it right away, and everything was fine for a while... until it started doing some strange things like extreme lag and dead when locked.
And, when I went to recovery to look again to the EFS folder, it was always empty... i restored it again, again and after locked... BAM, disappeared. But some strange things are happening, like:
My bluetooth doesn't turn on.
My IMEI was fine, even with this EFS showing and hiding like that.
I'm almost finishing. Let me put here some basic questions that I know everyone will ask:
Q: have you tried to wipe everything and go from zero?
A: yep. It didn't worked.
Q: is your IMEI ok?
A: yep. But some things that are on the EFS folder doesn't wok, like Bluetooth. The MAC address of the bluetooth is there, but it doesn't show up when I write *#*#232337#*# on my Phone app (this code shows up Bluetooth address and try to turn it on... to me it tries to turn on forever).
Q: do you know that thing about the new modems? Click here to go to the post
A: yes, but only read it when i've had the problem. But i've restore that backup, and it was from the original ROM. So it doesn't seem to be this, because the backup was before this leak. Very very very before, actually.
I hope you guys can help me, and that I don't need to go to the Samsung support with the phone wiped. Thanks,
~imatheussm
When you say you've tried from zero, do you mean you've flashed a stock rom?
Sent from my GT-N7105 using xda app-developers app
3vo3d said:
When you say you've tried from zero, do you mean you've flashed a stock rom?
Click to expand...
Click to collapse
When I had this problem, the second/third thing I did was flashing the stock ROM. But it was with these problems too, and with some other weird things: the S Note and the Samsung Keyboard giving FC almost every second.
~imatheussm
Well I guess if you're getting these issues when completely on stock I reckon you need the service centre?
Sent from my GT-N7105 using xda app-developers app
Have you try formatting your internal sd? I got similar problem too when flashing 4.3 mj5 leak.
Also got a uid mismatch when the phone start. I format my internal sd then flashing 4.1.2 firmware back.
Not a problem after that.
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
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)