Honestly, this is the 3rd time that there has been an issue with the AIOv2. Whether it was a Manufacturing error, Production delay, now there is this? We’re getting a product that doesn’t even work as it was advertised? There are a bunch of people who are forgiving about this because they are just willing to solder the part anyway. What about the customers who don’t have the ability or know how to do it on their own? What happens when they mess it up? I haven’t even received the upgrade kit yet and there is already a problem with it that I don’t feel comfortable fixing on my own. I don’t think a “how to pdf” or “stickers” is enough of a compensation as people are suggesting. I believe the error should be corrected by vileer and the part should be replaced. This error is something that should have been caught when you were doing the “quality checks” after receiving the new batch you ordered after the manufacturer error. This whole issue with the AIO v2 and the delays and problems stemming from it need to be corrected for the customers because so far nothing has been done just promises that the product will come and it would be operational. Which it is not.
Can you all stop giving terrible advice, you can’t just throw a pack of stickers or a pdf at this issue. Did he not do a “QC check” when he got the boards back (which he announced he was doing?!). Some people do not have the ability to do what you guys do and fix the problem themselves. He needs to mark them as sold out, fix the issue and send people the working product HE PROMOTED and that WE PAID FOR.
What was being tested here?! ^
make sure that you have updated the eeprom to go from SD card to NVME first.
the order “BOOT_ORDER=0xf461”
i can confirm that mine works fine.
if you have a working SD, you can use rpi-clone to get what you have on SD into the NVMe. i have found that to be trouble-free
@vileer
A compensation plan is appreciated. overlooking the electrical current limits happens. it is not as if the USB is failing…. it just cannot support the current required for high powered devices. Of course, it is good to have that fixed moving forward in a v2.1.
You might want to fix the information on the website too (at least for now).
I am for one appreciative that your team made the various expansion boards in the first place, and am still impressed by what your team has done to make the uConsole great.
Love the consolidated antenna system, love the NVMe, and love the fact that i have USB3 and Gigabit Ethernet on my uConsole. Thank you so much for making these happen.
AS for me, not everyone can solder and is comfortable with a hardware self-fix for something this small. But for those who are, and part of your compensation plan, perhaps you can send them a few of the right resistors and clear instructions on how to solder. 
just my 2 cents.
Are you saying I need to copy this script on both .cfg files in boot folder on the SD card and NVME?
How do we setup like this can you show a quick guide.
Please check out this post. Getting the eeprom to the right boot order is faily well discussed there.
Once you are sure that you have done that right, you need rpi-clone. The instructions to get rpi-clone installed is available in the link below.
make sure you use the right device. in uconsole it should be “nvme0n1”.
Once that is done, you should be able to remove the SDCard get boot from NVME.
I have CM4 does it make any difference?
They should buy Apple products instead. 
But seriously:
The upgrade kit is an extension for a hacker gadget. The entire uConsole project is aimed at DIY enthusiasts and a tech-savvy target group.
In my opinion, this is not a defect, but a weakness that does not constitute a complete malfunction.
One should not apply the same standards here as one would to an expensive product from a major brand manufacturer. And even there, it would not be a glaring flaw.
If that was what it was advertised as then I would agree with you, but it wasn’t. So that whole comment is null and void. No where was it stated that you would need to modify anything as far as soldering, as a matter of fact most people are purchasing this kit to avoid having to do just that or else they would be content sourcing the parts and doing the mods themselves. You are choosing to overlook a problem, which is your prerogative, but don’t down play like this isn’t an issue just because you are ok with it.
My comment wasn’t meant to be taken entirely seriously, even though there is a grain of truth in it.
There’s no need to get so worked up amongst hackers, as if a $1,000 product had completely failed.
I would like to see a little more understanding for one another.
I’m being realistic and it doesn’t matter how much something is. I’m confused as to where there is confusion. The product didn’t work as advertised we all paid for what was advertised, kinda the end of story. Again, whether you’re ok with it or not it’s your prerogative, but don’t try to talk other people into being ok with it and I was understanding after the first delay, was understanding after the second delay. But you want me to be understanding when after he gets the second batch he states he’s checking to make sure they were operational
As you can see here so again to follow that up with now there is something that isn’t working that could have and should have been caught then?
I’m not saying you’re not allowed to be upset. Go ahead!
I’m just pointing out that most hackers are capable of replacing a 1-cent component themselves, and this circumstance, which doesn’t even affect everyone, as the connection is used differently, in my opinion does not justify any reduction or other compensation. The change takes a few minutes and costs a few cents.
Happy hacking!
Um. No?
I’d guess most of us are not set up to solder this small smd components reliably. I’m certainly not, I lack both the setup, steady hands and eyesight needed.
I can give it a shot and probably get it to eork, sure. But not reliably.
However I do not intend to use the bluetooth on the module, so … i’ll be ok?
i’m not entirely sure as i have not tried it with the CM4. But the confidence level that it should work the same is high.
The Hackergadgets board should support the CM4 from what i read.
And you can run “rpi-eeprom-config” to check the boot order.
make sure that you have updated the eeprom to the latest on your CM4, and then check/edit the boot order to “BOOT_ORDER=0xf461”
The reference boot order property table is here
https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER
after that the rpi-clone etc steps should be the same
That’s what I was told too. The only difference is the speed that the NVMe connection can achieve.
However, since I haven’t received my uConsole yet, I can’t confirm this from my own experience.
I have never had a problem with @vileer’s products. I have the first AIO board, and it works perfectly. I have ordered the AIO v2, which I am aware may not be perfect, but I’m willing to work with it. We must understand that if it weren’t for people like him, we would still have a plain old boring uConsole running on an SD card and cellular, which most of us don’t use, gathering dust. Now we have something to keep us active and give new meaning to owning a uconsole. We need to show a bit of appreciation for that.
I totally agree to the above Vileer and Rex are legends without them UConsole would still be stuck on V1.
The SSD actually stopped mounting have no idea what happened it was a 2230 SSD. I have swapped out with a 2280 1tb SSD and it mounts just fine currently just using it as 1tb storage till I can figure out CM4 booting NVME.
Well, yeah. I won’t be expecting this to be considered warranty. Killing small vendors isn’t something I’m comfortable with.
I’m just saying that the soldering isn’t something anyone can do. We are talking worst case component, only two.terminals and the size of a grain of sand. 