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.
Related
Hey
So this old i9000 phone came with some Horrible bloatware I wanted to get rid of.
I flashed a stock Rom with Odin, (I've done it many times before on a different i9000)and Wiped Data and Cache afterwards, And 3 different Roms give me this problem:
When the phone finally initializes, Everything keeps Stopping unexpectedly. I've tried to get to enabling ADB to maybe view the logcat but I can't even get to the settings.
I did notice in the recovery mod an error that said something about System/CSC/CEL/system not being accesible (And i'm surprised it's still there after 3 flashes, CEL being the CSC for the bloatware company)
What do I do?
Currently on Stock rom with stock recovery.
Edit:
Okay, I have managed to race through the crashes, Launch the Home app, and enable ADB... so we have that now... "ADB devices" Shows its connected.
Edit2:
They all crash with "java.lang.ClassNotFoundException:" Right now Home screen is working but anything i try to run crashes
Edit3: It's like the old Gmail account is HARD CODED to it, What the hell? 3 rom flashes and countless factory reset, The account is still there, I cannot get rid of it.
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
Last night I tried putting Cyanogenmod on my i9300, its a european model that is not locked.
I first tried with the nightly build of CM 11. Flashing went well, but after boot the Phone seemed to crash/freeze after a few minutes. It stopped responding and only gave sound when using the system buttons. after a few presses that freezes too. I was thinking this might be a problem in the nightly build, so I went back in the recovery, cleared things up againa and this time I tried the latest image from the unofficial CM 12 that can be found here: http://forum.xda-developers.com/gal...-temasek-s-unofficial-cyanogenmod-12-t3086689
It seemed that most people have little problem with this version so I gave that one a try. It booted and gave me an error just before the launcher had to startup. but after a reset by taking out the battery, the Phone booted fine and it all went so smooth... but as soon as i got to the point of entering my google account, the Phone frose again. I retried, and again... at that time it was late at night, and the Phone needed to be used today. So I desided to go back in recovery, clean everything out, and put back my backup. Things looked fine... but sadly, at random times th Phone freezes again. its not my Phone but my wife's, she says it hangs using Facebook or chrome. I did not get the chance to look for a pattern yet, but I hope you guys might have an idea whats wrong.
For now I asked her not to use the internet, I'm not sure if wifi or mobile date will influence it, but it doesn't hurt to try.
I have to go to work untill 9pm tonight, and by the time I get home it will probably be 10 or later, so I have little time to work on it.
If anyone can give me a direction to go in or a possible sollution then I would appriciate it. i might have missed something when putting the backup back.
Any idea's?
I got my hands on a Galaxy Grand 2 sm-g7105. Performed a factory reset from device and the system worked nicely enough. A particular third party app I wanted to use wouldn't load so I kept tweaking.
I rooted and set up a CWM recovery with Odin, then considered going with Resurrection Remix. I made a backup with CWM, wiped the device and set it up. It looked great but 'audioFX.apk' or something along those lines kept crashing every 30 seconds or so. It didn't cause me any problem besides the annoying crash notification, so i figured I could just remove the apk and be done with it. To my dismay, then the notification then piled up non-stop and the system become unusable.
I went and restored the backup on CWM. Then I'd get error notifications for this and that stopping working (basically the apps present on the backup that weren't on the stock rom), so I figured the backup was useless. Another mistake, I guess.
Performed another wipe, deleted the backup for space. Tried removing every piece of bloatware I could find before unrooting (I wanted to do that). Finally everything seemed to roll... except I deleted some important apk, SecDownloadManager I've come to believe, and at that point the Play Store couldn't update a thing, it got stuck on 'Downloading'.
So I did another wipe, just to find out that didn't restore the missing apks. Got my hands on a stock rom for my model (a different build than my origibal one, but to hell with it... right?). I got that working work Odin, but to my surprise that didn't seem to completely restore the apk mess, and I got a ton of crash apl notifications and even after logging on Google the play store didn't let me in to try and see if apps could update.
Finally, I found what is supposed to be the device's original rom. Odin'd it all the way. Everything seems to be where it belongs, but I cannot really check 'cause... NOW THE ****ING WI-FI WON'T TURN ON. It's not like it doesn't connect to my network, it just won't activate. I press the switch, or goes back off.
I tried rebooting, taking out the battery for some seconds, performing a factory reset from within the system, wiping from CWM, dialing *#0011# to access service mode and deactivating power-saving mode. Nothing works.
HELP, please.
I'd be happy if the WiFi just worked, but knowing why the hell a stock rom should give any headache or what I'm doing wrong for it to go so wrong might be a step towards the solution.
PS: I'm writing this as I recall, so the details might not be completely spot-on, but the broader problems were those.
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.