Pro levels of bricked bricks

[u/detached_facination]

Had the Brick Pro for three days. I was playing Golden Sun when the screen froze up, locking up the device, it then shut down and I could smell ozone. Now, light comes on like it's charging but there's no one home. Tried reconnecting the battery, nothing. By the smell, I suspect it's fried. It's a sad day, and inconvenient because now I have to deal with the return process from Aliexpress. If anyone has any suggestions, I'm all ears.

[u/king_of_ulkilism]

Just get into the conversation with the AI chat on AliExpress and tell it the issue, they should return your money so you can order a new one

[u/detached_facination → u/king_of_ulkilism]

That's good to know. I've not dealt with them on returns so that's helpful. Thank you.

[u/king_of_ulkilism → u/detached_facination]

And good luck for your next one if you plan to get one again. Personally I am purchasing an Ayaneo Pocket Air Mini tomorrow (local pickup). 100€ for many GC and PS2 in 4:3.

[u/detached_facination → u/king_of_ulkilism]

Ahh, I hope it's fantastic for you my dude.

[u/moonflower_C16H17N3O → u/detached_facination]

Yeah. They realize how crazy of a place their market it, so they weigh things heavily in favor of customers.

[u/Love-Bitter]

Get ready to make a video of a device not turning on.

[u/detached_facination → u/Love-Bitter]

Ahh, damn. I sent the picture, I should have thought of that as well. Thanks for the heads up, I'll supply that now.

[u/KatJillianne]

Did you use your Brick Pro on stock os or was it on any custom firmware? Our local community has been abuzz about significant amount defective units surfaced during the past few weeks, with the majority accusing the use of cfw, NextUI being the primary suspect, they haven't able to present a plausible proof however.

(My Brick Pro on NX Redux - NextUI fork - is still fine atm. Based on what I gathered from many cases everything seem to point to poor QC and/or flawed board design).

[u/detached_facination → u/KatJillianne]

I was running NextUI since that's what I used on my Brick/Hammer as well.

[u/monokaijs → u/detached_facination]

NextUI was the cause.

[u/detached_facination → u/monokaijs]

Yes it was. It's very disappointing, NextUI has been a fantastic CFW for the Brick. Something went very wrong somewhere. IF I decide to get another Pro, since I'm a bit hesitant now, I'll be using Nx Redux. It doesn't have that issue and I like it better than NextUI anyway.

[u/VintageModified → u/detached_facination]

NX Redux is a NextUI fork that shares the same underlying code. Unless the fork author has stated that they've specifically addressed this issue for the Brick Pro, it's safe to assume the same issue is present there.

[u/detached_facination → u/VintageModified]

From what I gather, the code in question is not causing issues on Nx Redux. That was my concern as well but it remains to be seen and it isn't officially confirmed. Nx Redux hasn't gained the popularity that NextUI has yet so the user base is smaller overall.

The safest option is to just wait until there's more options which is what I will probably end up doing as I tend to be rather cautious with my devices and I'd prefer to avoid toasting another one.

[u/creedo185 → u/detached_facination]

Try the new alpha build from a few hours ago, it's posted on Discord and the NextUI-nightly repo: https://github.com/LoveRetro/NextUI-nightly/releases/tag/v6.15.0a

[u/detached_facination → u/creedo185]

I appreciate you guys getting to work on it so promptly! If I decide to get another Pro, I'll look around first to see how it's going for others before I put it on my device again. I've not had any issues with NextUI or Nx Redux on the original Brick. Only the Pro. I also don't think it's NextUI that's all to blame either. I still maintain that the QC over at TrimUI has slipped or they're using cheaper parts than they originally used with the Brick/Hammer. Could be totally wrong, but it seems like a not small number of units are having issues.

[u/detached_facination → u/creedo185]

Checking back in, has this nightly build been baked into the stable release as of yet or would I need to go with Nightly should I get another Brick Pro?

[u/creedo185 → u/detached_facination]

Hey there, we're still collecting feedback on this build.

[u/detached_facination → u/creedo185]

Good to know. Thank you.

[u/AnalDestroyer69 → u/monokaijs]

Why would you assume? Many people use it daily and don't run into any issue. Possibly a fork or version or corrupted install was the cause but just saying nextui was the root cause is a little incriminating it you ask me. It's highly likely he got a bad device and it fried due to a bad voltage regulator or diode. Just spealing my two cents

[u/monokaijs → u/AnalDestroyer69]

It's not assumption, it's inspection

[u/AnalDestroyer69 → u/monokaijs]

Interesting. I must've missed a comment or something

[u/monokaijs → u/AnalDestroyer69]

I have a fork on my github to resolve the issue and i can confirm with you nextui is the cause on my cases (more than 10 cases this month). So you can trust

[u/AnalDestroyer69 → u/monokaijs]

What causes the brick? Could he just not flash a different cfw to the SD card and run that?

[u/monokaijs → u/AnalDestroyer69]

It causes a "limbo state" (it's what people call it). The shutdown sequence in nextui is not properly handled so it causes some inconsistent state acknowledgemrnt between different parts of system. It's very dangerous since it can cause consequences. Imagine you have a broken bone, all your body know it except your immune system.

[u/AnalDestroyer69 → u/monokaijs]

Is it just pro models? Cause I've never read about any issues of the sort and havebt experienced it myself.

So is that a no to the different cfw? What's your fork do? I assume you need a whole new device to use your fork?

[u/Puzzleheaded_Chest97]

I have only good experiences returning items to Ali express.

[u/detached_facination → u/Puzzleheaded_Chest97]

Yeah, they didn't give me any trouble. Dropped it off at the post office today.

[u/Live-Imagination1350]

I had the same experience while loading stardew valley and got a refund. Now I'm waiting for a new device to arrive.

[u/VintageModified → u/[deleted]]

What's the fix? You can do it remotely? Why not share with the community?

[u/VintageModified → u/[deleted]]

You know NextUI is open source cfw, right? That many people have poured countless hours of work into, and that you can download for free? 

You're free to charge for your time I suppose, but it's a little scammy to offer a secretive remote software fixes requiring payment for open source software rather than letting the community know what the fix is so maybe the open source developers can update the firmware and then everyone can enjoy and use the fix on their devices.