IVP4S | Frozen device/screen problem???

[Jimmy Vape]

Hello Guys,

I have a brand new IVP4S and I have managed to get it stuck.

The screen display is showing 'YH SX330 V4S T 12.8'

I can not get this to change, I have removed batteries, looked through the manual and scowled the internet and not having much luck.

It has been working fine, I have had it open for one day so far. It is as though the memory has been wiped and it does not know how to function.

Has anyone got any ideas or had the sam experience

 

[Hans Wermhat]

I have the first run ipv4, but have never seen that on my screen. That's the model info for the chipset in the mod. Looks like it isn't booting up maybe?

 

[Jordan Alexander]

My suggestion would be download the firmware installer on your PC, and download the newest firmware and reinstall it.

See if that works.

 

[Matty316]

Oh dear, I have the IPV4s on order. I hope this doesn't become a common problem with them.

 

[G-rad]

I was having the exact same problem. What fixed it for me was taking out the batteries, letting it sit for about 15 min, putting one battery in and then holding down the fire button as I put the second battery in. The white noise and firmware screen still showed up but when I let go of the fire button the device restarted and has been working like normal. I did this about 15 hrs ago and its still working great, I've taken the batteries out and put them back in, turned the device on and off via the fire button several times and no issues.

 

[JBR3AK]

I've just run into this same problem myself with my ipv4s. Im lead to believe the board is goosed. I've had mine for 5 months. I would smack it, and it'd restart and run normal for 30 seconds. Then, it would restart with the white noise screen and just display the firmware version and stay like that. No fix for me. If there is a fix, I'd like to know myself instead of junking it.

 

[JBR3AK]

Update**:I took it apart and fiddled. Board and soldering is intact. However, the battery connection and post separated from the battery box upon removal of the cover. Reassembled, and still no avail. Still the same situation. I will be investing in a better box mod. Sry Pioneer4You, I'm no longer a fan. Quality is important. Lesson learned from a hyped up china box.

Sent from my XT1080 using Tapatalk

 

[JBR3AK]

It is now 2days since using it. Put a fresh pair of fully charged xstar bats in, now it works flawlessly... My mind is blown. I'm assuming it was that time of the month for it..

Sent from my XT1080 using Tapatalk

 

[nyiddle]

Very odd, but my 2 cents.. I've never been a fan of P4U products. They're a bit wonky (the IPV3 had that weird non-functioning touch-button thing..) and usually they do a less-than-stellar job of acknowledging their product's shortcomings. It's one thing to release a "meh" product, it's another thing to not own up to it and offer solutions to the new owners of their devices. Anyway, with that rant over..

I really like pretty much everything from Sigelei. They make some cheap yet durable mods, and a lot of them offer many of the same features that are offered on P4U products. I haven't had a problem with any Sigelei product I've owned, and I rarely hear of stories of people having issues. Just a recommendation for a future purchase.

 

[Bunnykiller]

I have the IPV4 and it works flawlessly.... still dont like the mirrored screen cover tho...

 

[JBR3AK]

I have it in black. I was originally going to get the silver one,but I read that "chrome cover" makes the display hard to see in daylight. As far as the white noise/firmware frozen screen issue, its gone. It trys to act up and keep firing now and then, but stops when I quickly push the fire button hard. I have a habbit of leaking juice down the sides of the mod when I store it in my tool box at work. So I'm assuming it's in the firing button, and/or the board its connected to. Also, I've noticed what appeared to be a capacitor on that circuit board with the firing button. So, its a possibility after sitting for the 3 days without batteries, the device had time to fully deplete the capacitor. Again, all assumptions. But, hey. It still works. At least, for now anyway.

Sent from my XT1080 using Tapatalk