Related
I was running a stock ROM, rooted, with the original radios. All was operating properly.
Flashed the leaked radio update. Everything still okay.
Flashed Das BAMF 1.6. It boots up fine (and looks gorgeous, btw), but my SIM card is not recognized at all. Symptoms:
When making a call, I see text in the upper-right corner saying: "SIM Card not found. Please \n the phone."
Settings > Call > Voicemail Service... tapping on this dropdown results in "Voicemail number change unsuccessful. Please contact your carrier if this..."
I tried turning the phone off, booting it once without the SIM card, then rebooting with it back in place. That didn't help.
Out of frustration, I restored my tbolt to the backup I made before attempting das BAMF. Magically, my SIM card is recognized and everything back to normal. ...I tried das bamf one more time, only to have the same crappy results... FYI, I was sure to wipe data/cache/dalvik before flashing the rom in recovery.
HELP!
EDIT: I've also just noticed that despite this being das bamf 1.6 remix, I don't see the 4-in-1 restart menu, nor a 6-bar signal indicator. I'm absolutely positive that I downloaded 1.6 remix... Am I in the twilight zone?
did you wipe data before installing the ROM?
nevermind i missed it. i dont know then sorry.
try redownloading and check md5
I verified the md5 before flashing.
i actually received the same errors but it did not impede functions of the phone. My data has been dropping, but that is not because of the ROM, it has been doing it since the 4G outage.
EDIT: Actuallly my voicemail says:
"We have a problem
Your voicemail settings could not be loaded. Please try again."
Never seen that before.
The more I look into it, I'm missing things that are pictured in the 1.6 Remix screenshots... all of this has me very confused. I'm going back to the stock ROM until someone else finds and resolves the SIM card issue.
I am experiencing the same issues here. I see 'no Sim Card Detected' at the top, I have none of the Reboot Options, no 6 bar signal, etc.
Seems to be kind of a big issue and yet noone has really offered solutions. I have done the full wipe aswell.
Thank you for everyone's time involved with making such a Great ROM....Plus this Community of Users is awesome...Take that IPhone!
Did you happen to download 1.6.1 or 1.6.2 and install just those first? Those two are just patches that required 1.6 as a base.
So, you would have to flash 1.6, then 1.6.1 or 1.6.2 over it as a patch - you can't just flash 1.6.1 or 1.6.2 by themselves. With 1.6.3, I think they went back to a full rom release.
Install via cwr, not Rom manager.
Sent from my ADR6400L using XDA App
I had the same problem with the SD card running Bamf Remix. What solved it for me was formatting the SD card. Obviously backup the SD card on your computer first.
Download 1.6.3 and do a flash. It's a complete download too, id give that a go. I didn't run into any of those problems. Are you flashing through rom manager or cwm?
Sent from my ADR6400L using XDA App
Dont manually mount data. For some reason when i did that the same exact this happened to me. No 6 bar signal and no 4 in 1 reboot menu.
Sent from my ADR6400L using XDA App
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
I ended up wiping everything and installing 1.6.3 and that fixed everything. Thank You all Gentlemen for helping!
You guys are genius!
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Kodiax said:
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Click to expand...
Click to collapse
For the Call Recorder, it sounds like you're running a custom kernel. Most kernels don't support the things that Call Recorder needs. For the reboots, well, can't help you there.
mcore09 said:
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
Click to expand...
Click to collapse
Other than wiping twice (???), what you said you did should be standard procedure. Flashing via ROM Manager and Kernel Manager are no-no's unless you get lucky. In an ideal world, they work. And in many cases, they do work. However, in many cases, they cause nasty issues. For example, if you flash some kernels via Kernel Manager, the device drivers don't get flashed properly and you have some pretty nasty problems. And when you flash via ROM Manager, well, you learned what happens. From now on, only flash via CWM and CWM only.
Thank you for your responses. I am only using the 4.4.7 kernel. Which come s with dad band 1.6.3. I think that it is this new kernel (4.4.7). I never had these issues with 1.6.2.
Sent from my ADR6400L using XDA Premium App
Try down grading your kernel to a slightly older version.
Sent from my ADR6400L using XDA App
I reflashed my kernel to the same 4.4.7 but downloaded the kernel from his standalone post regarding kernels. My call rcorder is working now. Hasn't restarted since then either. Crossing my fingers ...
Sent from my ADR6400L using XDA Premium App
Well it restarted randomly while I had it connected to my Laptop and set to charge. I was in the middle of a Call with someone.
Very interesting why its Randomly rebooting. Could be the new radio. May be that why verizon held out on releasing it yet.
Im unable to make voice calls through the Phone app. It will connect, then make no noise (ie no ringing). Same if i receive a call, i hit accept and i hear nothing, nor can the person calling me hear anything. I can use the voice search/navigation, and i can use other voice apps (ie voxer) just fine. SMS works, as does 3g, and im not getting any error messages.
Phone is GT-I9100, Kernel is Siyah 3.1rc6, running D4rom (ICS). I've tried 3 seperate roms (Omega v11, D4, and Slim (all ICS)) all having the same issues. Im assuming this is an issues with ICS (or more likely something i didnt update prior to switching) but ive spent about 6 hours now trying to find out what is causing it.
I realize downgrading would solve this, but i'd rather find out what my issue is and fix it. any ideas?
Flash again, but this time full wipe, it happened to me once on d4 rom, this should do it
Edit: have you tried wanamlite with siyahkernel? If you follow the below, you shouldn't have a problem.
A. Ensure FULL wipe;
1. System
2. Cache
3. Data
4. Dalvik cache
B. Immediately Flash ROM
C. Let boot and initial setup
D. Check if phone dialer and choice calls are ok?
E. If ok, Restore only user apps and data. NO System crap. Recheck
F. Reboot and setup accounts. Recheck
Sent from my GT-I9100 using xda premium
Still no luck. Flashed 3 times, once with D4 again, twice with wanalite. did factory reset, manually wiped /data, /system, /cache, and Dalvik cache. after doing initial run (i didn't set up my gmail account, since i need wifi for that (data cap is annoying)) i tried to make a call, and it still wont ring. At first it would end the call after 15's or so. after restarting it it would go longer, usually until i end it. SMS still works, as does 3g data.
I got an error this time setting up the clock, but it was only visible for about 2s. It was something to do with setting the time, if i can get it again ill try to write it down.
Also, when wiping the Dalvik cache i get this :
E:unknown voluem for path [/sd-ext]
Dalvik cache wiped
any other advice?
I finally downgraded to GB rom (unnamed). Phone worked fine, as well as everything else. Ty for your help though, It was greatly appreciated.
Also, i noticed prior to updating it that the search and back buttons didnt do anything. IDK if this is normal or not, i dont use those buttons much.
Very strange after fresh full wipe and flash, and test without setup of the different ROMs
Edit: Have you tried flashing some of the alternative ICS modems found in the modem thread? Maybe yours doesn't like the modem packaged with the ROM.
If that doesn't work, what if you flash one of Intratech official or Frankenstein firmware. You'll need to re-root after and flash cwm again.
That error with the Dalvik is ok. Forget why, answer will be found with some searching though. If you look carefully, it would have said "Dalvik cache wiped"
Sent from my GT-I9100 using xda premium
Hello. I've done a few searches, but there's no suggested fix or correction ton the problem. Sometimes when I install a custom ROM (it doesn't matter which one or what slot) using safe strap 3.11, after wiping cache, dalvik, factory reset, and system, then installing and rebooting, the ROM always has issues when it gets to the 'turning on WiFi' screen. It never turns on and all the buttons do not work except the skip button. If I skip the step, my WiFi will lock and never work correctly. Can anyone tell me what I'm doing wrong or what the problem could be?
Sometimes it will work after a few flashes on the ROM, but its kind of annoying to flash something over and over, with hit or miss software.
Fixed: I figured it out. If anyone else has this problem, go back to your stock ROM, uninstall and reinstall safe strap, then flash your ROM again (and gapps if needed). Don't wipe anything, just reboot immediately after you flash. It will start working correctly.
Sent from my DROID RAZR using Tapatalk 2
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.