PLEASE IGNORE THIS. I SOLVED IT.
I have 2 debs and both are running the AOSP Pie ROM, currently. Until 2 days ago both were able to detect my SIM card; now only one does. Here's what I've done to resolve what I first thought was a hardware problem.
* I swapped SIM cards and rebooted; no luck.
* I soft rebooted; no luck.
* I turned on Airplane mode and tuned it off; no luck.
* I swapped out the USB charging daughter board (I had a spare) to which the SIM adapter is soldered; no luck.
So, I thought it was a software issue. I ran Wugfresth, which I've had installed on my Windows PC forever, and went totally back to stock 6.0.1; no luck..
Then I booted into recovery, wiped Dalvik, System, Data and Cache, and formatted Data, and flashed AOSP, Gapps 9 Micro, and Magisk again; but still no luck.
What could it be?? I must confess that I'm somewhat of a
serial ROM flasher, and I'm not even sure how to frame this question, but could the firmware "radio" have become corrupted in one of my serial re-flashing episodes? I hope someone can help me.
Thanks
Related
Yesterday I flashed CM 7.2.0 FXP109 on my Xperia Arc S.
3G worked perfectly.
Later I installed AdFree, and set my phone on the table. I do not remember if I rebooted it first. About an hour later when I picked up the phone again, I had no 3G signal. Still nothing today. Tried re-flashing CM7.2 FXP109, whilst first wiping data/cache/dalvik. Still nothing.
Tried to put it into airplane mode, waiting 10 seconds and turning it back off, checked all the settings (and the APN settings are set the way they should).
Also, after having wiped the phone data and cache and re-flashing, somehow USB Debugging and Unknown Sources are still turned on. Shouldn't that reset?
Either way, something is wrong and I'm at a loss. I have no idea what to do, and I just bought the phone yesterday. Before that I had an X8 with GingerDX, so it's not my first time installing a bootloader, and I haven't had these problems on my old phone.
Any help would be greatly appreciated!
EDIT:
I found a (possible) solution, at least it seemed to have worked for me.
I flashed a different kernel (and thus got a different version of CWM), formatted, wiped cache/dalvik cache and flashed back to the kernel needed for FXP109. Then I installed FXP109 CM7.2 and GAPPS again. Problem solved.
My guess is that for some reason, I had to flash to a different kernel and back to solve it.
Cheers!
-Zareph
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.
Had something really weird happen to my S3 guys.
Running teamwin and the Liquid-Smooth ROM. Been that way for 5 months since I bought it with no problems until now.
Plugged the phone up to the charger last night before bed. Woke up and wondered why the charging light was still yellow so I kicked the screen on and it was charging at an extremely slow rate (Around 40mA). Unplugged the charger and the phone made a tone I had never heard before. Noticed two small "glitches" or "artifacts" in the display rendering around the clock area on the home screen. Attempted browsing around the phone. App drawer opened and closed fine but EVERY process or app I would try to launch would crash so I rebooted, and that brings me to where I am now.
The ROM will NOT boot. The phone just sits there at the Galaxy SIII splashscreen. I can boot to Odin/recovery just fine and the internal SD filesystem appears intact and browse-able. Tried totally nuking the data section. Wiped Dalvik/Cache, did factory reset and then wiped the ROM. Tried re-installing the ROM and even re-flashing the radio and it still doesn't boot past the splashscreen.
While I was in recovery it also told me, "Your phone doesn't appear to be rooted. Would you like to install SU?", which is strange because the phone WAS rooted.
Thinking this thing mysteriously turned itself into a paperweight. Any ideas?
Please install a different Non-Liquid Rom. But for best results, First ODIN back to stock and then go from there. Use Root 66 Stock image.
agree with odin flashing root66 firmware. factory reset FIRST though. you will likely be forced to if you dont, and once stock recovery is flashed back on it will wipe internal sd.
if you still have issues after that i would suspect a hardware failure.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Just FYI guys I got it back about an hour after posting this.
Even after wiping both caches, performing a factory reset, fixing permissions and finally nuking the ROM it still would not boot. I then put in a spare SD, used recovery to copy everything from internal to external to save all my valuable data and only after wiping the internal SD was I able to get the phone to boot again after re-installing the ROM.
I then transferred all valuable files back to internal SD, restored from a recovery backup and then was good to go. A bit strange but I got it working again.
Eventually I might upgrade from LiquidSmooth but I like it and have no reason to change for now.
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)
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!