I'm hoping someone on here can help me. I've had a few lingering issues that I can't seem to resolve. I run AOKP, but at this point, I may go completely back to stock to see if the issues resolve.
- The main issue is the random freezes on boot. It is really random, but definitely has gotten worse over the past few months. Basically, the phone freezes at the first boot screen about 60-75% of the times I reboot. I've had to pull the battery sometimes once (if I'm lucky), and sometimes 3-4x, just to get it to boot past the Samsung screen. This is compounded by the second issue I'm having:
- Loss of data. Actually, more specifically, it is data not coming back when I leave a no-signal area. I live in a no-signal area and depend on a VZW home tower. I don't get a solid signal until about 2 miles out from my house, just after I leave the neighborhood. After I clear the area, I get a strong cell signal, but data never becomes available. Toggling mobile data or cycling airplane mode does not resolve it. I have to reboot, which can bring me to the stuck boot screen, where I'm pulling my battery to get back up and running (often when I'm driving... which really sucks).
This weekend, I wiped the phone as fully as I could. I don't believe I restored it completely to stock, as the phone still showed the unlocked icon when booting. I did, however, restore the phone to the stock MDK ROM, re-rooted, reinstalled TWRP (through GooManager), and reinstall the 11/14 AOKP ROM. It did not seem to help.
Shortly after wiping the phone, I was 99% sure I had figured out the boot issue. For some reason, I got the idea to pop out my sdcard while it was stuck at the boot screen. As soon as I popped the card out, it moved past the Samsung screen and changed to the Google "X". The card was a SanDisk Ultra 32GB, which some people have had dismounting issues with, so I thought I hit the jackpot. I tested it several times, and as soon as I popped the card out, it would start booting each time.
I was excited when I hit the road this morning. Unfortunately, the data bugged hit me as soon as I got out of the neighborhood. As before, I had to reboot to get it back. That is when it stuck on boot again. I did not have an sdcard in, though. It took for cycles of pulling the battery before I finally booted up.
I'm stuck. I really don't know what else to do. I've tried every ROM/radio/kernel combination out there, except for bone stock. I used a combination of different guides to get as close to stock as I could, but I still didn't get there. I'm sure I missed something, but I'm not sure what. The steps I took to restore are below.
Is there a PIT file I can use to repartition the phone? I know that is frowned upon unless the phone is completely bricked, but I don't know what else to try. Just from experience, I'd doubt it's a hardware issue... but who knows:
Steps I took to "restore" phone:
- Flashed SCH-I545_MDK_562219_Stock_Restore.tar.md5 in Odin
- Rebooted, then went back to Odin to install MD2 kernel
- Booted into stock ROM, enabled dev options, USB debugging, etc...
- Rooted, rebooted, installed GooManager
- Installed TWRP through GooManager
- Installed 11/14 AOKP, gapps, faux 0123m, and MJ7 radio
Related
So after initially getting the S4, I couldn't wait for a ROM to come out so I didn't have to run TouchWhiz. Needless to say when I seen some ROMs starting to appear, I flashed some with no hesitation.
I flashed the following before encountering any problems -
garwynn's - AOSPA Beta followed by CM 10.1 (POC)
Everything on those ROMs was pretty much perfect, no errors or glitches in anything I used the phone for, so after a day or two I was feeling pretty confident about the current releases thus far. I seen the thread for SlimBean this morning and flashed it with no problems
The ROM loaded up just fine, instantly obtained 4g signal with full bars and everything seemed pretty much good to go. About a half hour into it my signal indicator went to "Roaming". I figured it was just a glitch in the ROM not properly displaying the signal indicator as it should. My data was working fine, so I just assumed all was well. I switched the indicator to the text / dB style which showed a pretty constant "-72 / 80" It didn't come to me that I could not call or text for about two hours...
Needless to say, I tried to put the phone on "CMDA only" "EVDO only" and pretty much any combination besides "GSM only" in the Phone Information section after dialing *#*#4636#*#*. I tried turning the radio off an on. Still nothing would work....so I dirty flashed SlimBean over itself. Didn't work, flashed the following ROM-
Beans' Stock ROM (Odexed)
Loaded up fine, had 4g but still couldn't call. I tried flashing the CM 10.1 ROM as well with the same problem. When I got home I put the phone in download mode and flashed the stock image (link) hoping that it would solve my problem. It didn't.
I'm currently sitting here as stock as I'm aware I can be with no working voice / text on my radio. Data works fine, as does everything else. My IMEI matches what is on the label under the battery. Everything looks normal to me except the IMEISV which currently reads "00".
I'm not too worried about this as of this moment as I know the SIM card is good, it works in my SIII and my other phones. I'm just not sure if this is a fixable problem or not.
Thanks,
-clay
Odin back to stock and go get your phone exchanged.
Solution
I'm glad to report that I did in fact manage to fix this problem. Hopefully this can help others.
*DISCLAIMER* - I am not claiming this is 100% full proof, nor am I able to explain why this worked.
However it may be useful to others....
After doing a bit of research I came to the conclusion that my EFS wasn't completely corrupt because I still had my IMEI intact on the phone. The best I could come up with was that my files / data for SIM card provisioning weren't correct / corrupt. Thus I tried the following:
1) Odin stock image.
2) Odin MD2 kernel and root via Motochopper.
3) Install Root Explorer and Terminal.
4) Copied my EFS folder and placed it elsewhere. (Never used this copy but could be useful somehow?)
5) Renamed EFS to something random. *Probably very dumb to do* Deemed necessary after some reading.
6) Phone rebooted into Factory Mode.
7) Executed the following command
Code:
su
echo -n ON >/eds/FactoryApp/factory mode
8) Rebooted Phone.
9) Odin Stock Image.
10) Odin MD2 kernel and root via Motochopper.
11) Flashed TWRP.
12) Boot recovery and run Fix Permissions.
13) Rebooted, powered down phone, pulled battery and SIM for about 10 minutes and then reinstalled SIM, powered on.
14) Odin stock MDK kernel back to phone.
To my surprise in a minute or so I locked on to a signal and could make calls / text. 4g was working as it was previously. I'm not sure if all steps are necessary but after a few attempts at various things, this method proved to work.
I'm back on SlimBean and everything seems to be working smoothly.
Glad you got it back up and running! Nice to see a community member work around and solve the issue. Many times a device ends up back to the carrier when all thats needed is a little trial and error with various fixes. Sure the carrier will replace the device, but this is why some carriers lock them down e.g. verizon/att.
nice job :good:
Glad you figured it out, but as an FYI, my IMEISV reads 00 and I have no issues, so this seems normal.
So I've been running KitKat via CM11 nightlies for quite a while now and about every other week the I lose signal and have to reflash stock. I Use Razr Utility (http://www.droidrzr.com/index.php/t...-verizon-droid-razr-and-droid-razr-maxx-only/) to flash stock, get signal, reroot, and reinstall SafeStrap. Have done it I think like 80 times or so now.
Today when I did it, when I pressed start at the Setup Wizard it said "Preparing may take a few minutes ... blah blah" then it reboots. I rebooted and tried again, over and over it won't get past the language selection, and if I leave it alone for a few minutes w/o pressing anything it will reboot on its own still; it continually reboots over and over. Also I am no longer getting service back on a fresh stock flash. I have tried 1.8/1.82/newest of RAZR Utility, all received the same result. So I tried House of Moto with 2 different VZW firmwares (2 newest JB) and still same result.
I was able to get root w/o having to mess with Smart Actions and then use ADB w/ su and PM to disable all the setupwizard BS so I could install SS and get back to CM11. (Setup Wizard is locked and no way to bypass, even tried build.prop tweaks to turn it off and nothing) Now on CM11 it is liking to randomly reboot whenever it feels like it too; that is if it even boots back into CM11 after rebooting, sometimes it makes it all the way to CM11, sometimes it doesn't.
Does anyone know WTF is going on with my device and how to fix it. I'm going to try and get a new SIM tomorrow and see my SIM fried or something (though I never received the "No SIM" error). I'm honestly about to chuck this phone through the friggin wall....
Update: Was finally able to get CM11 to stop rebooting, upgraded to newest nightly and wiped Dalvik & Cache, and Fix Permissions. Signal has sort of come back, it goes in and out; very finicky.
Update 2: Service is completely gone and can't get it back now.
So, I managed to get safestrap and it works completely fine. However, when I install Hyperdrive no matter what I do the restart won't work from hyperdrive. I end up having to take the battery out of the phone and turning it on.
Initially I ignored this issue, but I feel like if I ignore it completely I may realize later that it was actually a much greater problem.
Are there logs or anything I can post that can provide more information to help solve this?
Also, I've noticed that hyperdrive seems to get very buggy after so much time.
First, hyperdrive rom slot stopped booting up. did everything I could think of. Luckily I kept a second one for emergency and switched to that for the time being.
Second time everything just crashed and kept on crashing.
Also, when I attempt to boot into stock I keep getting storage errors despite having 500mb storage available.
Edit:
I've also noticed almost everytime it boots up it shows "android is upgrading"
More or less things have been very bug filled. I'm curious what would be recommended to start out doing first? Is the reboot issue something that could be concerned about?
edit 2: I'd like to note that when I install Xposed framework and reboot. The reboot works. So, this reboot issue is specifically towards Hyperdrive.
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.
Last week on Thursday, I allowed Verizon to install their Software Update 21 (April 2020.) It made it as far as the going through the optimizing apps and then was stuck in a boot loop. The phone would be usable for about a minute, then would freeze, and then reboot. If I clicked on the System Update option in settings, it would say that a system update was in progress. I chatted with Verizon, and they ended up telling me that the only way to stop the update was to do a factory reset, which I am doing everything I can not to do that as I don't want to lose my data.
I changed it into maximum power mode and it did stop the update for that time being and I was able to use the phone, texting, etc. This allowed me to at least connect the phone to my computer to backup all of the directories. After many reboots, on Friday it finally stopped doing the update and gave me an error which I think was 410. It thought it was updated, though did show as failed. When checking for updates, it said it was the current version. Twice I was able to get the phone to stop by freezing when going to the app and stopping some programs (sadly, I was not able to remember the exact combination that worked) which allowed me to use the phone like normal. All this while, I was uninstalling a large amount of the apps that I had installed hoping that would minimize whatever may have been causing the problem.
Went to each of the google and samsung apps, stopped, disable, and reverted them all back to factory defaults. Guess that was a bad idea, from then on I received an error as soon as the phone started which caused it to go directly into recovery mode. I chatted with samsung and they thought it might be a hardware issue. I still think it is related to their software update, so not a hardware issue.
By using Odin, I loaded the firmware from March 2020, and when it rebooted, it did go as far as optimizing the apps, though anytime it booted up, it would never get past the white verizon loading screen. It took me hours before I discovered that Odin was failing to load the firmware on the phone as the Windows 10 laptop only had USB 3.0 ports which don't always work with Odin, and ended up being successful using my old Windows XP laptop as the USB 2.0 ports worked fine. After a bit hanging on the verizon loading screen, it would reboot and never went past. I have been able to load the March and April 2020, though none of them will ever get past that white verizon loading screen. I did see something say that in loading TWRP, I could possibly do a full backup of the phone which is what I would like to do.
One time I only loaded the AB file for a different version than I had loaded, and it was the first time it went beyond the white screen, only to tell me that the verification failed and it would need for me to do a factory reset. I was able to reboot the phone without actually doing the reset.
I have read many posts here and the forums on androidcentral, and with so many things, I really needed to post to get guidance from people here that can point me in the right direction for any other things that I can try. As you have read, doing everything that I can to get the phone working by keeping my data. Any help would really be appreciated.