So.... I was stuck at the M logo after trying to update to a newer version of MIUI. I successfully SBF'd back to stock froyo and my phone won't activate. When the activation call tells me to press "1", it simply goes silent.
Now I somehow bypassed the activation screen, I don't think that was a good idea because it forced me to connect via wifi. I just said "screw it anyway" and went ahain to reroot. Then I installed CM7 (since I current don't have the MIUI zip I was previously running on my phone). Now I am stuck at the CM7 logo. Not sure if I should SBF again or what I should do. I'm kinda freaked.
Also, I have never had a problem SBFing before. This seems more serious than before.
Update: Wiping data allowed me to boot up in CM7. Still cannot activate my phone. Whenever it prompts me to press "1", all I get is complete silence.
I'm currently at UT Dallas, so I don't think location is a problem is it? Actually it shouldn't be because I bricked my phone here before. Had to reactivate it and it worked great.
Man, this is the first time my phone won't activate.
Yes I know I am posting a lot, but since no one is here to help currently I'm trying things out on my own.
I tried restoring a nandroid I had of CM7 previously. Man I thought this was always a failsafe....
Just thinking of things I did since the last time I activated my phone. I updated something (radio version, I don't really know much about it), it was supposed to make my 3G faster or whatever. But I mean I've SBF'd, factory reset and everything, so that shouldn't be an issue?
Gosh dang, I just want my phone back the way it was 2 hours ago.
One of the reasons nandroid might not be working is that I might have a different version of clockwork on my phone. I remember before having a version where the test was blue, but I forgot the version number. Now the one I get with rom manager is green (like the one I had before I got the blue one).
Man I am sooo confused here. I am completely at a loss. I am out of ideas. I need help.
So I realized I did not have the second init version of clockwork. I just flashed that, and I'm waiting to see if I will get any errors. If I get this to work I am going to flash the version of MIUI I had and try to restore my more recent nandroid (since Ive gotten MIUI).
Yup problem solved. Not sure what was causing the problem, but at least its solved. I'm gonna be extra careful next time I flash something.
Related
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
blackied said:
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
Click to expand...
Click to collapse
I had similar issue when flashing another kernel on my stock ROM. Maybe your kernel isn't compatible with the radio or the kernel modules haven't been applied correctly. Hardware error should be presumed after flashing original RUU.
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
blackied said:
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
Click to expand...
Click to collapse
As far as I know, factory wipe deletes just the user data. I might be wrong though, because this is my first android, so I'm still learning the basics on rooting, kernels, etc. But from your first post it seemed that you updated your radio in that period, so this might be the clue to what happened. I don't know if the nandroid backup would restore everything to stock, but I'm pretty sure that the original RUU would. Still, you should follow a procedure that would allow you to keep your root (I think if you have radio S-OFF, you'd be able to flash 1.32 RUU and just root it). Anyway, you can't return the phone for warranty services with a custom ROM, so you still need to flash a stock RUU.
Sorry, I should clarify: I did the radio update yesterday to see if it could fix it. It wasn't the cause.
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
tangler27 said:
Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
Click to expand...
Click to collapse
Utility is gonna take care of it for you...I'm certain. I cant think of anything that caused it though. That's kinda weird. But if I were you I would just stick with the stock ROM with that issue and just troubleshoot it and if it happens again...hit it with the utility again
Also if you don't mind losing camcorder the 4.2.2 ROMs are great and don't require safe strap as Kong as you unlock boot loader through the utility. But will void your warranty.
Good luck! And follow those instructions on Matt's utility perfectly!
Sent from my XT907 using xda app-developers app
Hi, just wondering if anyone has seen an issue like mine. I looked but did not find a thread or problem like what I am having right now. I have an original VS980, I was using TWRP 2.6.3.3 (the newest one) and tried to flash the new CM11 nightly and GAPPS, and it boot looped. I went back into TWRP using the vol down and power buttons, and installed a stock rom. Still boot looped. I restored a backup that I had actually restored and used before, of an earlier CM11 build, and that bootlooped too!!! So I have tried a couple of methods of restoring to stock firmware, and each time I am reaching the same point. The phone boots and the setup wizard starts. I click next, and the little activation window pops up, and just spins until the phone reboots. There is no signal showing during this.
I can get into download mode, and I can do factory resets. But I still can't get my phone activated, so I can't get into the stock ROM, to root or install TWRP again. Any ideas? Hopefully someone can help me by tomorrow, I am without a phone (I'll be fine lol).
Try doing this: http://forum.xda-developers.com/showthread.php?t=2448960
And if/when you get it working, don't use TWRP 3.3, it's all kinds of FUBAR'd at the moment. If you use 3.2 you'll be just fine.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Vepaot said:
Try doing this: http://forum.xda-developers.com/showthread.php?t=2448960
And if/when you get it working, don't use TWRP 3.3, it's all kinds of FUBAR'd at the moment. If you use 3.2 you'll be just fine.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Click to expand...
Click to collapse
Yes, I tried this. When it boots, it just gets stuck at activation.
BUMP NEED HELP!!!
EDIT: More info, so maybe someone can see where I went wrong. I tried the WACOMalt method, and flashed VS98010B_13.tot to my phone. Someone in that thread mentioned that if you are on VS98011A then flashing VS98010B might not work. Then I tried a few times with a different restore method to flash a VS98011A stock image, and came to the same result, boots fine but does not activate and I cannot do anything with the phone.
gotta say twrp 2.6.3.3 is working fine here on d802 uk and has been for the last week or so ive flashed roms,restored from backups and all was fine -providng you've got the latest twrp or cwm youll have no problems
Sounds like you are zeroed. Check status for IMEI, ect. If good, you may need to "reactivate" online. If not, hope you backed up EFS, would be time to restore it. If both the latter fail, flash stock and go to Verizon.
Steamer86 said:
Did you back up your EFS?
Click to expand...
Click to collapse
Unfortunately no.
Edited ^ Our EFS isn't in a separate partition. A bad wipe can and will destroy it. EVERYONE should back this up after root, no matter what you're doing with the phone. And store it in a few places.
Steamer86 said:
Sounds like you are zeroed. Check status for IMEI, ect. If good, you may need to "reactivate" online. If not, hope you backed up EFS, would be time to restore it. If both the latter fail, flash stock and go to Verizon.
Click to expand...
Click to collapse
What do you mean "check status"? If you mean from system settings -> about phone, I cannot even get to that since I am stuck in setup wizard. I am planning on going to Verizon tomorrow, first thing in the morning. I have already flashed stock, so they will not see anything out of the ordinary. I am also bringing my HTC Rezound, in case I need to go back to that. Hopefully they can help me reactivate the G2 though...
There's a key combo to pass that. Go online on your account, switch theline over to the rezound, activate, back to the g2, try and let it go through activation. If it doesn't work, return. Sounds like your EFS is gone though.
Okay, I tried that. I can bypass the setup wizard by pressing vol up, then vol down, then back. I took my sim card out to do this. Under about phone, it shows unknown for emei and all the other settings. But I keep getting an issue, whenever I turn the screen off, it cannot turn back on and I have to reboot it. So, I think my EFS is messed up, but I have restored stock. I can get into the rom and look at about phone settings. But I am having issues with the screen turning off and not turning back on. And when that happens the phone reboots itself after a while.
I don't have my Rezound sim card on me right now to try activating it. I will just find it tonight and take everything to Verizon tomorrow. I'm sure they will help me out of this jam. Thanks for your help dude!
You are zeroed regardless, as you suspected, nothing to do but return. Back up that EFS next time! If you are stock, you'll be fine and get a "new" refurb. Someone will get your nice refurb when it's repaired. You're good.
I have been running CM (currently CM11) on my SGS4 since I bought it from Sprint in summer 2013. However, Sprint changed their international partners pretty seriously in the past 2 years, so I *really* need a PRL update for international travel. Normally the easiest way to do this is to reboot to stock or TriForce, run the "update PRL" and "update Profile" options from in TriForce, and go on with my life.
But I encrypt my phone. So I had to boot into TWRP, wipe and format *everything* and make sure the phone came up unencrypted in CM. All is OK.
So I reboot, flash TriForce 5.4 custom with stock (not KK) kernel. Flash works fine, I reboot... and am prompted to decrypt the device before I can do anything. None of the decryption passwords I've used in the past (I checked my password safe) are working. When I flash back to CM, it boots fine, and the settings says that the device is not encrypted.
I downloaded and tried TriForce 5.2 and 4.0, both are giving the same problem. I have used TriForce in the past on this phone, so it SHOULD be fine....?
Someone in #twrp said that the location of the encryption key changed from Android 4.4 to 5.0. So my only remaining thought now is that there was also a change from 4.3 to 4.4, and the encryption key for 4.3 didn't get removed in the wipe, and since the partition is NOT encrypted, the decryption, even if I have the right key, fails, so I can't get into the phone. Hope that makes sense.
Anyone have any guess better, or, if I'm right, know what I need to move/edit to fix this?
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
docsmooth said:
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
Click to expand...
Click to collapse
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
docsmooth said:
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
Click to expand...
Click to collapse
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
http://money.cnn.com/2015/05/21/technology/resell-android-phone/
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
mikeprius said:
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
Click to expand...
Click to collapse
I was never able to get the stock odin download. The whole problem came up because I was going overseas... I got around it by just buying a local SIM rather than using the Sprint roaming (again, I was doing all this just to update the PRL. new GSM SIM = no PRL update needed). On the way home less than a week later, I cracked the screen so bad the LCD and backlight wouldn't even go on.
I replaced it with a Nexus 6. A bit big, but it doesn't suffer Samsung software awfulness, so I didn't have to flash it with CM to make it usable.