Develop Bugs

[Q] ROM/Theme/Mod Flashing Issues

I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.

Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.

I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:

techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.

All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?

Any idea why no rom will work? (CDMA)

I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.

Did you do a full wipe ???

ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...

donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.

You mean the Rom booted normally right ?? If yes then the problem is with the Rom

donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).

Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.

[Req] Best mod with much less bugs for I927R

Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you

ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.

On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again

David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....

Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.

yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.

davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod

davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.

yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me

Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.

Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.

I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.

davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB

[Q] Phone isn't bricked, but nothing will revive it!

Hi everybody, I was hoping to get some help here. Be warned, this is a long story.
I was running CM10.1 fine. My phone was lagging for some reason. A quick search told me to clear my cache. I did. I flashed the Darkside cache wipe. Now my phone wouldn't boot. There would be a Samsung Splash screen, then nothing and my phone would (try to) reboot. Again and again.
My (external) SD card had been acting up a lot. It wouldn't be recognized, copies would be slow, and all sorts of problems. So I formatted it. It worked fine. I assumed my phone was back to normal.
I restored my phone to stock via ODIN. It would reboot at first, but I That worked fine. I was happy until I needed my Wifi hotspot back. I rooted via Odin. The Deleting of tethering provision no longer worked. I flashed the Darkside ICS Rom. That worked fine. I missed Jelly bean/stock android. I flashed CM10.1 along with a fresh download of the Darkside cache and data wipes.
The phone didn't boot. Same problem as before. I assumed same solution. I got a PASS! and unplugged the phone. At this point, It showed the stock splash screen (Galaxy SII, Android 4G etc.) and then an animation of the Android with some blue 3D figure spinning in his belly. The %age status bar at the bottom reached 30ish% then stopped. The animation continued and the bar remained at 30% for a very long time. I tried to reboot normally, which would result the Splash screen with a %age bar at 99%, frozen, and to enter recovery which gave me a splash screen then this:
-- Verifying internal MMC block...
Not need checksum confirmation
already executed!!...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC
This is character to character what I read, and there seems to be a dead android with a red triangle in his belly in the back ground.
I can consistently reproduce these two situations, both of which are disturbing. I could try to restore via Odin for the third time, but I risk making things worse.
Thanks for reading the essay. Until I can somehow fix this, I'm stuck with Hercules in a coma.
Any help is appreciated.

step one, flash twrp (2.5.0.0) via odin
step two, wipe everything except external sd
step three, flash whatever rom
the end

What are you restoring your phone to...ics or jb?
Sent from my Infamous Hercules.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
ClaireH said:
step two, wipe everything except external sd
Click to expand...
Click to collapse
Are you trying to make him wipe his internal storage as well? :sly: lol
Sent from my Infamous Hercules.

ClaireH said:
step one, flash twrp (2.5.0.0) via odin
step two, wipe everything except external sd
step three, flash whatever rom
the end
Click to expand...
Click to collapse
I did the same thing day before, actually. Only I flashed CWM via Odin. I could now access recovery, but flashing CM gave me the same no boot problem. Funnily, resetting to stock actually worked after I did this!
Obviously I'm not happy with stock. However I am hesitant to mess with my now fully functional phone.
And without starting a flame war, would using TWRP give me different results?
Oh yeah, iburnhearts, I resetted to the (I think) latest stock JB, 4.1.2. Should it matter? I heard there was a difference in where the SD card was located or something.
I will make a backup before trying TWRP this weekend.
Thanks for all your help.

sauprankul said:
I did the same thing day before, actually. Only I flashed CWM via Odin. I could now access recovery, but flashing CM gave me the same no boot problem. Funnily, resetting to stock actually worked after I did this!
Obviously I'm not happy with stock. However I am hesitant to mess with my now fully functional phone.
And without starting a flame war, would using TWRP give me different results?
Oh yeah, iburnhearts, I resetted to the (I think) latest stock JB, 4.1.2. Should it matter? I heard there was a difference in where the SD card was located or something.
I will make a backup before trying TWRP this weekend.
Thanks for all your help.
Click to expand...
Click to collapse
Glad to hear you're phone is fully functional...stock jb touchwiz isn't too bad in my experience especially now since a lot of the newer cm10.1, pacman and carbon nightlies are having SODs and RRs.
As far as twrp vs cwm...in my experience twrp has a much simpler user interface which makes it easy to wipe amd theres no need for the darkside scripts. Although if you want to flash a custom touchwiz jellybean ROM then you would need the infamous wipe scripts which are similar to dark side but they've been updated by Jamison.
Sent from my Infamous Hercules.

Hi everybody,
I flashed CWM via ODIN, then I flashed the TWRP .zip. It was easy enough. Then I flashed CM 10.1, gapps and a custom boot animation by nozerogravity (keywords CMX boot animation). All went surprisingly well, and the welcome screen alleviated my concerns.
There still remains the problem that originally worried me something was wrong with my phone: it would lag during the simplest of games. Until I tried other ROMs I didn't know that this was a known issue with CM 10.1. I simply had to lock and unlock to temp fix this problem.
TWRP is much simpler and cooler than the classic CWM. Also, why did CWM conk out on me so? That is the real question. The evidence seems to point to CWM, however, I am reluctant to blame such an established piece of software, esp. considering the fact that it's free.
Thanks everybody, for the help!
*Nota bene: No wiping scripts were needed with TWRP, neither Darkside nor Infamous (I'm not familiar with the latter)

Issue with booting on 4.3

Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!

your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.

Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!

bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?

thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away