Related
[Q&A] [Toolkit] Wug's Nexus Root Toolkit v1.9.3 [Updated 10/28/14]: Nexus 10 Thread
Q&A for [Toolkit] Wug's Nexus Root Toolkit v1.9.3 [Updated 10/28/14]: Nexus 10 Thread
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Toolkit] Wug's Nexus Root Toolkit v1.9.3 [Updated 10/28/14]: Nexus 10 Thread. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Armeniandave said:
I was asking if it did. I just updated to lollipop without root.
I haven't tried to install twrp or root it yet.
Click to expand...
Click to collapse
I've tried it twice and it won't root my device.
---------- Post added at 08:23 PM ---------- Previous post was at 08:15 PM ----------
Evidently I have to post here since I don't have enough posts (??).
Anyhow, I upgraded to 5.0.0 via the Toolkit, well attempted to since I guess it's a bad idea if you're on an encrypted FS since it reported corruption and then wipe/reset. So I attempted to do a restore and the Toolkit keeps telling me I'm set to "Any Build" despite being set to 5.0. I tell it the correct one, go through the process again and yet it still Restore mode says it's "Any Build". I don't know if this is a bug or I'm doing something wrong since if I set it to 4.4.4 it works fine.
I'm attempting to re-flash 4.4.4 now and will see if I can restore my backup. Total clusterf...
Root Nexus 10 v1.9.4 on Lollipop.
Running Root+custom recovery script. Live log is on, and everything seems to go as it should. When final boot is done SU notifies that binaries need updating, which I accept. Then Device boots into recovery and when it returns to system SU informs that there's no binary installed..!?
Prior to this I rooted my Nexus 5 on Lollipop without issues...
Thx for your support!
Martin
To reply to myself I ran a srock+unroot script, and then tried to root once again - this time it appeared to work
Installing 5.0 through NRT limited my storage to 13.0 GB
I have a 32 GB Nexus 10 and the storage shows up as 13 GB after installing Android 5.0 through the Nexus Root Toolkit. Can someone help me with fixing that?
After you've rooted using the tool kit, message appears that describes your problem pretty well - the solution suggested by wugfresh is to perform a factory reset, IIRC - have you tried this already?
Mas
Mine did the same thing. Factory reset fixed it
13 GB instead of 64 ?
cancelled
Hashcheck Mismatch
I'm trying to flash the stock firmware to my wife's Nexus 4 so she can receive the 5.0 OTA and install it correctly. The problem I'm encountering with the "flash stock+unroot" button is that the image files always fail the hash check, as do the twrp downloads and the superSU downloads and pretty much any file that this program tries to hash will fail.
I've downloaded the hashcheck shell extension and manually verified every file I've tried to load, they ALL have correct md5sum values when compared to the md5s on the google developer page or the download page at the android filehost website. Is there any way to get around the broken hash checking? My wife is very impatiently awaiting here lollipop upgrade.
Thanks,
Sergio
Hi, i used the tool kit to flash 5.0 on my nexus 10 and i have it running fine but my status bar and soft keys background are black. I noticed in video reviews of 5.0 that they should still be translucent. Any ideas whats up?
geek wana-b said:
I noticed in video reviews of 5.0 that they should still be translucent. Any ideas whats up?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-10/help/lollipop-translucent-decor-t2938952
Trouble flashing my Nexus 10
Hey guys. I am having trouble with flashing my Nexus 10 tablet back to KitKat (due to frustrating wifi issues) after upgrading to Lollipop using the "official" method.
I had read an article on pcadvisor.co.uk about how to downgrade using Minimal ADB and Fastboot, so I started there. Everything was going well up until the point where I was to install the KitKat image.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.030s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.035s
erasing 'recovery'...
OKAY [ 0.027s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.035s]
finished. total time: 0.035s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.193s]
finished. total time: 0.194s
sending 'bootloader' (1280 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
rebooting into bootloader...
^CTerminate batch job (Y/N)? y
After that, I posted a question to the AndroidCentral forums. There, user rhea turned me on to Wug's Nexus Root Toolkit, thinking that it would help solve my problems. Unfortunately, I got pretty much the same errors. I was using the option to install from a soft-brick or bootloop, which sounded like my problem.
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.030s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.035s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.027s
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.193s]
finished. total time: 0.194s
sending 'bootloader' (1280 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.006s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
sending 'boot' (4784 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.009s
rebooting into bootloader...
Any help you guys could give me would be very much appreciated. At this point my Nexus 10 is bricked, which is bumming me out. I am seriously missing reading Flipboard in the morning while I eat breakfast.
I'm not sure if it helps, but I have included a pic of what is on my tablet's screen.
Thanks in advance,
Mike
Nexus 9 disable force encryption not working woth Nexus Root Toolkit v1.9.9
Hi everyone,
I wanted to disable the forced encryption in my Nexus 9 using the Nexus Root Tolkit v1.9.9. I succesfully installed all the drivers and apparently was able to unlock + root my device. However, when I try to disable the forced encryption the tool somehow isn't successful in flashing the new flashboot, and when the device reboots it is still encrypted.
Did anyone come accross this issue?
Thanks very much for your help!!
Nexus 10 stuck at fastboot
In my attempt to flash the new 5.0.2 update to my Nexus 10 it seems to have correctly wiped the device, but then couldn't finish pushing the new update onto it. As of right now, the device will sit at the screen shown below, and boot to the screen shown below no matter if I move to "Recovery Mode" etc. What do you believe I should do to correctly finish flashing the new update?
imgur [dot] com/a/gZNpH
Edit: It seems my problem is similar in nature to that of mdhankins 2 posts above.
stuck at "flashing custom recovery to recovery partition"
title says it all, I've got a N7 2013 Flo, android 4.4.2 KOT49H
I used this toolkit with NO problems whatsoever with my grouper, so I'm not sure what to do here, should I force close the tooklit, reboot tablet and start over or will I brick the device?
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Hey, no problem bro! It's called vendor, not vender, and the command is: fastboot flash vendor etc. This should solve your problem (Sorry for my english)
NHagney said:
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Click to expand...
Click to collapse
I'm a Linux guy so you may wish to take this with a grain of salt. I have a vague memory of the same error and it was a case of a misspelled and/or miscapitalized command. I am assuming 2 things -
1) everything has worked up to this point
2)the code presented is exactly what you typed on your computer
Your error may simply be that your misspelled vendor after "fastboot flash"
Thats what i get for being hung over. I'm over here trying to run this as admin all kinds of nonsense. Wondering why this went so smooth last night now running into this. I still don't have a working device. After restarting the device I don't get the OS only the initial google screen. Edit: nevermind. It just posted. TY guys. On to Android 'N' maybe Nuttybar?
I did the b10 update yesterday, fully stock.
After the update it keeps getting stuck at the boot screen.
Luckily recovery still works.
I downloaded an official rom package, put the update.zip on 3 different sdcards.
all 3 cards get the same response from recovery. 'Sorry, you can't sdcard upgrade'.... great... fine sideload it is.
so tried to sideload, got this message:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Then tried to fastboot twrp
got this message:
C:\adb>fastboot flash recovery twrp-3.0.4-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.402s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.424s
I have had several galaxy phones in the past, but never encountered this troubles.
Does anybody have a idea what's going on? im kinda lost here.
FREEKR said:
I did the b10 update yesterday, fully stock.
After the update it keeps getting stuck at the boot screen.
Luckily recovery still works.
I downloaded an official rom package, put the update.zip on 3 different sdcards.
all 3 cards get the same response from recovery. 'Sorry, you can't sdcard upgrade'.... great... fine sideload it is.
so tried to sideload, got this message:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Then tried to fastboot twrp
got this message:
C:\adb>fastboot flash recovery twrp-3.0.4-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.402s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.424s
I have had several galaxy phones in the past, but never encountered this troubles.
Does anybody have a idea what's going on? im kinda lost here.
Click to expand...
Click to collapse
Your battery percentage is low. Make sure you charge it until at least 80%
EDIT: Enable OEM unlock in developper settings
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk
Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.
ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!
We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.
I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?
ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)
I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.
Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.
My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry
Hello,
I spent the last two evenings trying to install the Android 11 preview in my old "spare" Pixel 2 XL, however I run into some issues.
I unlocked the bootloader, and tried to install the preview via adb sideload, this didn't work, error was some Signature Verification error.
I noticed my Pixel 2 XL was still on the October 2019 patch level, but it would not find an update using system update in settings.
So I downloaded the February 2020 factory image, tried to install is via adb sideload as well, same issue, Signature Verification error.
I tried the November 2019 OTA file, and was able to sideload and install it, phone booted and it finally started finding updates, so I updated to the latest Security patch level February 2020 using system updates.
I hopped this will solve my issues but still, the same Signature Verification error, with both 11 dev preview as well as the current full factory image.
I then moved on to using the flash-all.bat file. It would start, installing the bootloader and radio, but it is not able to install the image-taimen-qq1a.200205.002.zip, I'll always get this "error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space"
And this issue I cannot solve, well, both the validation issue and the "not enough space" issue.
By now I installed twrp recovery, not luck either, running into the same issues when trying to install the image.zip after pushing it to the phone.
"not enough space" Error
=================================
\platform-tools\taimen-qq1a.200205.002>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36352 KB)...
OKAY [ 0.811s]
writing 'bootloader'...
OKAY [ 0.267s]
finished. total time: 1.080s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.352s]
writing 'radio'...
OKAY [ 0.800s]
finished. total time: 2.153s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space
Press any key to exit...
=================================
I also tried to follow some "manual" flashing guides, but those are all for Android 8, the file names and file system format has changed a lot, so that would not work either.
I believe I completely corrupted one of the two partitions doing that, luckily after a few failed boots the device booted from the other partition, for some reason that had thrown me back to December 2019 patch level, so I updated up to February 2020 using the standard system update feature, that fixed both partition slots A and B, so I am back to a normal functioning device with twrp installed. But I cannot solve this issue.
Would be glad if someone has a solution for this, or suggestions on how to tackle this.
[EDIT]: As I mentioned this is a spare test device, I am not worried about any data, the device was completely wiped anyway. Also it is the 128GB version.
Regards,
Alex
Just flash the 11 ota with twrp. Works fine.
When you go back to 10 you'll have to format your data
I've encountered the verification error before and what I did was redownload the file and it solved the problem. As for the not enough space I would check out the Google dev site as they have a flash tool you can use to flash as well. Just a suggestion to try. Hope you get figured out.
Edmontonchef said:
Just flash the 11 ota with twrp. Works fine.
When you go back to 10 you'll have to format your data
Click to expand...
Click to collapse
Thanks, that worked! I didn't even knew there are OTA files for the 11 preview.
The announcement stated image flashing only, so I assumed only full factory images are available.
I flashed the stock boot image back as well, so no twrp anymore, no reason, just like to run stock if possible.
Thanks a lot again, such a simple thing.
pantallica420 said:
I've encountered the verification error before and what I did was redownload the file and it solved the problem. As for the not enough space I would check out the Google dev site as they have a flash tool you can use to flash as well. Just a suggestion to try. Hope you get figured out.
Click to expand...
Click to collapse
Thanks, I have redownloaded all images multiple times, no luck, but the 11 previre OTA worked, so it is sorted, even though the underlying issue still persists.
MiLeX84 said:
Hello,
I spent the last two evenings trying to install the Android 11 preview in my old "spare" Pixel 2 XL, however I run into some issues.
I unlocked the bootloader, and tried to install the preview via adb sideload, this didn't work, error was some Signature Verification error.
I noticed my Pixel 2 XL was still on the October 2019 patch level, but it would not find an update using system update in settings.
So I downloaded the February 2020 factory image, tried to install is via adb sideload as well, same issue, Signature Verification error.
I tried the November 2019 OTA file, and was able to sideload and install it, phone booted and it finally started finding updates, so I updated to the latest Security patch level February 2020 using system updates.
I hopped this will solve my issues but still, the same Signature Verification error, with both 11 dev preview as well as the current full factory image.
I then moved on to using the flash-all.bat file. It would start, installing the bootloader and radio, but it is not able to install the image-taimen-qq1a.200205.002.zip, I'll always get this "error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space"
And this issue I cannot solve, well, both the validation issue and the "not enough space" issue.
By now I installed twrp recovery, not luck either, running into the same issues when trying to install the image.zip after pushing it to the phone.
"not enough space" Error
=================================
\platform-tools\taimen-qq1a.200205.002>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36352 KB)...
OKAY [ 0.811s]
writing 'bootloader'...
OKAY [ 0.267s]
finished. total time: 1.080s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.352s]
writing 'radio'...
OKAY [ 0.800s]
finished. total time: 2.153s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space
Press any key to exit...
=================================
I also tried to follow some "manual" flashing guides, but those are all for Android 8, the file names and file system format has changed a lot, so that would not work either.
I believe I completely corrupted one of the two partitions doing that, luckily after a few failed boots the device booted from the other partition, for some reason that had thrown me back to December 2019 patch level, so I updated up to February 2020 using the standard system update feature, that fixed both partition slots A and B, so I am back to a normal functioning device with twrp installed. But I cannot solve this issue.
Would be glad if someone has a solution for this, or suggestions on how to tackle this.
[EDIT]: As I mentioned this is a spare test device, I am not worried about any data, the device was completely wiped anyway. Also it is the 128GB version.
Regards,
Alex
Click to expand...
Click to collapse
You have a spare Pixel 2 XL? ? I am still using duct tape to keep mine together. Lmao.