Started with stock, then S-off'd, rooted, and flashed a custom AOSP (can't remember the name). Everything went swimmingly for months.
Out of nowhere, I started getting "internal storage" issues. Internal storage was listed at 1GB, and started filling up regardless of if I deleted things. It seemed to cause slight problems, but nothing serious. Shortly after, I stopped receiving texts altogether. Tried flashing a new ROM, went with MIUI V5, it worked, but still no texts. Decided to start from scratch. RUU, re-root, re-flash recovery, etc etc. Ended up flashing MIUI V5 again, but got stuck in a bootloop. Tried 4-5 different hboots/recoveries/every setting imaginable, nothing. Started over again (RUU >>>), flashed MIUI V5 again, and this time it worked. Load it up, ask a friend to text me, BOOM, text received!
Open up the browser... "403 Forbidden". Wat. Nothing to do about it, it seems. I've tried fiddling with all of the relevant settings, I've downgraded/upgraded radio, nothing. I've flashed to a different ROM and back again, nothing. Just crip-crapity-crap.
As of right now, the rest of my night is going to be spent backing up/flashing to sense to do system upgrades/restoring backup and hoping it works. Anyone know what would cause "forbidden" errors, data wise? Calling/texting works both wase (not MMS, obv).
I think you should try a new kernel
Sent from my HTC EVO 3D X515m using xda app-developers app
Problem was solved by backing up my current MIUI build (working minus data), full wipe, then flashing Harmonia 3.17, doing all available System Updates, full wipe, then restoring my MIUI backup. I now have data, send/receive MMS, and calling, + MIUI V5 totally working.
Finally!
Case closed. Thanks!
Related
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
So I got an Evo 3D GSM a few days ago and upon installing a custom ROM on it, the phone worked perfectly up until the first reboot. At which point it began to reboot frequently so I reverted back to stock and it was fine. I then tried another ROM though from the same developer and once again it was fine up until the first reboot and then again it became unstable.
At this point I know it could just be that I used 2 different Sense 3.5 ROMs from Shooter that's been causing the problem but unless that's a known issue which I couldn't seem to find, I'd rather not install another ROM just to test this out.
Basically I'm wondering if I could be doing something wrong, I installed it through ClockworkMod Recovery which never gave me problems on my Nexus One. Also if I'm going to test if it's just an issue with the ROMs, can anyone suggest a stable and relatively customizible ROM?
Are you doing a clean install, full wipe?
Also, are you loading apps and settings back into the phone from Titanium or the like?
Ya when I attempted to do it non-clean it was unstable off the bat. The last time I basically wiped everything. I have been using Titanium Backup to restore apps but I also used it on stock(I backed up from my Nexus originally) and it hasn't given me any problems there.
Try flashing the rom first again and this time don't use tb to restore data to apps. I've seen and read quite a few times that tb can cause all kind of weird problems when restoring data+apps. Try just restoring just the apps and see if the issue still remains.
#Root-Hack\Mod*Always_
""Shooter on Deck""
I went through the apps I don't need first and removed the backups, I never did restore data, just apps. MikRunny seems to be running stable so problem solved though I still don't know if it was ROM related or just an app screwing with it.
if you flashed a new ROM, it was probably the ROM since it is working now, seeing as how you didn't restore any of your data. logically, that sounds right to me.
cobraboy85 said:
if you flashed a new ROM, it was probably the ROM since it is working now, seeing as how you didn't restore any of your data. logically, that sounds right to me.
Click to expand...
Click to collapse
Well I had tried two different ROMs before and never restored Data, kinda strange but it appears to be fine now so I'm not complaining.
Background:
Unlocked, Rooted, S-Off, ICS Leak RUU 605.22
Was running Ivysaur Rom with no issues at all. On Sunday afternoon, the phone started acting up, wouldn't light up when pressing power button, huge lage problems and all the sudden, incoming calls lock the phone requiring a battery pull and outgoing calls lock during call resulting in battery pull. Well Sunday night Venosaur was released so I tried to update to that, update went good, but no fix. So desperate, last night I flashed the new leaked RUU. Everything went great, thought everything was working, but now, no incoming calls at all and outgoing locks the phone. Please help me, i'm at my wits end.
Upon further investigation, it seems as if I'm getting tons of Android Process has stopped, where you either select ok to close or wait. These are happening in the background for some reason. I've ran fix permissions, just tried clean wipe 5x and then flashing scroslers new debloated of the leak. Still having issues though. I think these process stoppages are causing my messaging issues too, as in no landscape texting which now comes and goes.
What should I do?
Wipe data/cache/system/boot in recovery and re-install rom. Be very careful of what data you are restoring as it sounds like a data issue to me.
dottat said:
Wipe data/cache/system/boot in recovery and re-install rom. Be very careful of what data you are restoring as it sounds like a data issue to me.
Click to expand...
Click to collapse
+1
I've once had similar issues flashing one ROM over another without wiping data properly. Could be due to different UIDs, folder layouts, etc. compared to the ROM pre-Ivysaur. And then Titanium Backup restores wreak havoc due to the differences. Remembering to do nandroid backups helps for just such occasions.
If sure about being fully clean before flashing, check MD5 of your downloads for corruption, check network settings in the ROM, reflashing the RUU twice in a row before using, and reverting back to PKMN ROM or downgrading to try and fix the call issues.
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance