[Q] Restoring NookColor After Botched 1.2 Update - Nook Color Q&A, Help & Troubleshooting

I sort of did myself in with a perfect storm of derp, but I'm hoping I can still recover...
My NookColor is -- or rather, was -- a rooted v1.1.0 system (AutoNooter'd). I last picked up my NookColor a couple of days ago. During that interval, it downloaded and applied the 1.2 system update.
As it happens, I had an SD card installed that I was using for other things, but which also contained the old AutoNooter tools for rooting a 1.0.1 system. So the 1.2 update was applied, the system rebooted, and the AutoNooter started applying patches for a 1.0.1 system. The result was a machine that wouldn't get past the 'n' logo.
Since there was nothing important on the machine, I decided to wipe it and restore it to default using the 8-reboot trick. But... Surprise! I had installed ClockworkMod 3.0.0.5 earlier (as part of applying the rooted 1.1 update), and it was now taking control of the restore process. I used it to format both /system and /data, in the hope that the regular boot process would notice they were blank and do a restore from /rom (or wherever). But no, that didn't work. And CWM has no option to mount /rom and attempt restores from there.
I tried downloading the 1.2 update ZIP file from B&N's site, copying it to an SD card, and using CWM to install it, but CWM refused, claiming it couldn't open the file (the error message was simply, "(bad)"). I tried using 'zip -F' to repair the ZIP file, but it still wouldn't work.
So, I'm now officially stuck. Can anyone point me to resources on how to get my NookColor back into working order?

Hmm. This thread appears to describe how to do a full restore to 1.0.1, complete with links to SD card images. This falls under the "good enough" category, so I'll be trying that shortly (just as soon as I can find a usable uSD card).
But feel free to chime in with additional suggestions.

Create a new CWR 3.0.0.5+ sd card. Get hold of the 1.01 restore and 1.2 update. Copy 1.01 to the CWR sd and boot it up. Do a wipe on the nook using CWR. I think it's system and data under the mount and restore menu. Then run the 1.01 restore and reboot. Do all the registering and such. Then attach to usb and drop the 1.2 update into the "nook color" drive that pops up. It will update shortly and you should be up and running again with 1.2 again.

Sorry if that is kind of thrown together. I don't give very good directions. lol

Related

[solved] need help recovering epic 4g after trying to install a ROM

Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.
Cincinnatux said:
Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.
Click to expand...
Click to collapse
Odin back to this http://forum.xda-developers.com/showthread.php?t=794138 then root using this http://forum.xda-developers.com/showthread.php?t=770388 then install this if you want cw3 and ext4 if not skip it http://forum.xda-developers.com/showthread.php?t=897612 but check on the rom ur flashing because most rom are now using ext4 and cw3. Also if you want and ur rom has the option for no journaling flash this before flashing a rom http://code.google.com/p/bonsai/downloads/detail?name=ext4-format_nojournal-1.1.3.zip&can=2&q= . I know Bonsai and Midnight roms have the option for it. Well best of luck to you and if you have any question or concerns please post them here and ill or one the many helpfull people here at xda will assist you.
Thanks, asj2583, for the quick response. For whatever reason, it did not occur to me to try putting the phone in download mode!
So to get the phone back on-track, I:
1. Started Odin3 v1.61
2. Removed the SD card from the phone
3. Plugged the Samsung USB cable from the phone to the computer (which is running 32-bit Windows Vista)
4. Clicked on 'PDA' in Odin3, then selected the Froyo TAR that had worked before, then I clicked on 'START.'
5. Let Odin3 do its thing, and now my phone is back up and running unrooted Froyo.
Moving forward, I:
1. went here and downloaded One Click Root 2.5.5.
2. On the phone, went into Menu/Settings/Applications and enabled 'Unknown sources,' then unplugged the USB cable and clicked on /Development to enable USB debugging and Stay Awake.
3. I plugged the USB cable back into the phone and ran the 'run.bat' file I extracted from the One Click Root 2.5.5 download. In short order my phone rebooted into rooted Froyo. (confirmed by going into Applications and seeing that 'Superuser' is installed)
Now it's time to set up CW3 and ext4:
1. I went here and downloaded a different One Click Root (anyone know if I could have used this instead of 2.5.5?).
2. Again, with USB debugging enabled and the USB cable plugged in, I clicked on 'run.bat' extracted from the One Click Root CWM3 download. After a brief wait, the phone rebooted. Theoretically, at this point I have Clockwork Mod 3.0.0.5 and my phone can handle ext4 filing. (Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
And to try a new ROM:
1. I went here and downloaded CyanogenMod 6.2 prebeta 14 and saved it to the root directory of my phone's SD card.
2. Powered down the phone, and reinserted the SD card.
3. Powered up into ClockworkMod Recovery. The screen showed that it was running v3.0.0.5. ClockworkMod automatically checked for ext4 but failed to mount. ClockworkMod suspected my files are still in rfs (admittedly, I never reformatted my SD card to ext4). ClockworkMod created a backup named 'before-ext4-convert-1296478915' in case I need to restore. At this point, I found myself in ClockworkMod's menu.
4. In ClockworkMod, I ,ped data/factory reset 3 times, cache partition 3 times and, under /Advanced, wiped Dalvik cache 3 times. I then went back to install zip from SD card and chose the CyanoGen Mod I wanted to try, but it failed. ClockworkMod noted that Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages. So I went back to my SD card and told ClockworkMod to install gapps-hdpi-20101218-EPICv1.0.3.zip, which completed without error. Then I told ClockworkMod to install NebulaMod. The phone rebooted and all seems well.
Thanks! I sure was stuck last night, and just needed a nudge in the right direction.
Whoah. Whatever you do, don't follow my advice. This just bricked the phone. It will not even power up any more. Damn.
Correction. Not bricked. Just really, really scary. Thanks to Koadic I'm back at unrooted Froyo. I think maybe I'll stay here for a while.
Cincinnatux said:
(Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
Click to expand...
Click to collapse
Ext4 wasn't intended solely for handling large files. It made some changed to ext3 that allows handling of larger files and also increases the subdirectory limit, which makes it suitable large files or large disks. Ext4 also added journaling. These are not the reasons we use ext4 on our phones. I think all of our ext4 roms mount the disks with the noatime flag, and many people are running the no-journal mod. This makes ext4 act more like ext2 with the ability to allocate extents instead of individual block.
"Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages."
My phone also says this when I try to install the Truly-Epic rom. I'm on DK28 like the rom says to be on, and on CWM3 and EXT4...yet...it doesn't want to install. Anyone know what for or what might be any problems?
how long did it take for your phone to power up after rooting with ext4 and cwm3? mine has been at it for a while now. i flashed back to stock dk28 using odin and did the process over and it gets stuck backing up my information and just keeps creating before ext4 back ups til my memory is gone

How to avoid the nook boot loop problem before or after Adobe auto-updates

Update 20111117: Updated .zip file to Adobe Flash 11.1 and AIR 3.1.
Update 20111020: Updated .zip file to reinstall Flash and AIR, previous version didn't properly fix AIR.
Steps I used to update Adobe Flash (to version 11.0) and AIR (version 3.0) so it doesn't update automatically and thus get me back into the boot loop cycle (again):
Go to Titanium Backup ( Pro )
You need to uninstall with this since these are system apps
Buy a Pro key and keep it on your SD card root, since this app will save your bacon
Uninstall Adobe AIR and Adobe Flash Player from Titanium Backup
It will warn you that you are uninstalling a system app, that's OK
I think that is why the update through Market isn't working
Open Market, Install Adobe Air (3.1.0.488 as of this post) and Adobe Flash Player (version 11.1 11.1.102.59 as of this post)
Nook seems to be working after several reboots. Also, note that Adobe updated their apps. After following the procedure above, I was able to update via Market without any problems with bootlooping.
Obviously, the above steps only work BEFORE Adobe gets auto-updated and you get in the boot loop cycle. If you are already in the boot loop cycle, download this file (Updated link, should work better this time):
FlashPlayer11.1_AIR3.1_Update_Fix_20111117
and install it using a ClockworkMod Recovery SD card.
Get a ClockworkMod Recovery SD card
http://forum.xda-developers.com/showthread.php?p=11987469
Put the zip from the above post on the SD card
Reboot your Nook with the SD card inserted
Install from Zip, Select zip from SD card, select the flash update
This basically will uninstall flash and air as system apps and install as a user apps. This is based on the zip from GMPOWER which updated flash to 10.3, which worked for some but not others, perhaps because it didn't touch Air:
http://forum.xda-developers.com/showpost.php?p=16526691&postcount=7
Also note, I have been through several cycles of restoring backups, restoring to factory, re-rooting, etc. this last week, so I was getting very annoyed and cautious. I think I was able narrow it down to just the Adobe updates causing my problems. I have been able to update ROM Manager, Superuser, and just about everything else with updates; and besides the Adobe updates, everthing worked, and I don't currently have a boot loop problem.
Note, I didn't update Superuser or ROM Manager until after I applied the above updates to Flash and AIR. After several reboots, my Nook is still working fine.
For those of you who are still having trouble getting your Nook back, and the attached zip doesn't work for you, you can do the following. Using the instructions on this site, I got my Nook back up and running to factory new condition:
http://mrm3.net/nook-color-recover-any-bricked-device/
(Quick method at top, not older methods below; instructions slimmed down from several posts here at XDA, updated for stock 1.2) also here on XDA:
http://forum.xda-developers.com/showthread.php?t=914690 (original restore to stock post)
http://forum.xda-developers.com/showthread.php?t=1050520 (update for stock rom 1.2)
Then, I registered my Nook (again).
At this point, I could have tried to update to 1.3, but my patience was a bit low, so I didn't go for it. If you do, be sure to follow the appropriate ManualNooter instructions here:
http://forum.xda-developers.com/showthread.php?t=1054027
Since I was still on Stock 1.2, I rooted using ManualNooter 4.6.16
(while in CMR, after running ManualNooter, I also applied update-Froyo1.2-dalingrin-OC-emmc-090111.zip, and that seemed to work without a hitch)
Then I reinstalled all the other apps I wanted on my Nook,
=== BUT DID NOT YET UPDATE ADOBE FLASH OR AIR ===
Flashed ClockworkMod Recovery, updated a lot of my apps using Market and Amazon Appstore, restored data and other apps from Titanium Backup,
Then I made a full backup of my Nook using CMR. (still booting normal, running fast and clean)
After confirming my Nook was as I wanted it, and that I had a good backup, I did the steps at the top of this post to update Adobe Flash and AIR.
After confirming that was working, and getting another backup on my SD. I then did the updates to ROM Manager and Superuser. It seemed like those updates happened at the same time as the boot loop, so I was cautious. My Nook is still working well without boot loops as of yet.
Results:
Kernel: Stock 1.2
Rooted with: ManualNooter 4.6.16
Additional Mods:
update-Froyo1.2-dalingrin-OC-emmc-090111.zip,
ClockworkMod Recovery 3.2.0.1,
ROM Manager 4.5.0.1, Titanium Backup 4.5.2,
Adobe Flash 11.1, Adobe AIR 3.1 (uninstalled system app, reinstalled via Market, updated via Market)
[Update Zip] CMR zip to update Flash Player and Air
I updated the original post with a link to the zip to fix the FlashPlayer and Air apps. I had intended to post it here, but since I'm new, I can't link externally in a reply.
Please let me know if there are any problems with the zip and I will get it updated. It worked on my Nook.
I updated the zip file 20111020 to fix a problem with the AIR reinstall.
Wow, thank you so much for this! I wish I had known this on the weekend when I was gong crazy trying to figure out why I was getting bootloops over and over. I can't seem to give you thanks though (probably because I never post, just lurk).
So far I haven't done the uninstall/re-install with TB. I am just making sure my Adobe air and Flash don't update, and when Air did I went into Nook Color Tools and uninstalled the update to set it back to what it was originally. That worked but it is a pain if it keeps happening. I will try the TB to uninsall the programs.
I too did a update on ROM Manager and Superuser (and a binary update), and all is still well. No bootloops. I hold my breath though every time my NC gets to the "color" part until the N appears and it all disolves.
thanks for this!!! this was really getting very frustrating.
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Thanks for this information. My nc is currently in a bootloop and won't load CWR. It shuts off before getting to that point (my bootloop is adobe air related). None of the restore to stock via SD card have worked for me. I'm now looking at ADB options, the post you referenced with the fix has some instructions for that. Did you use the ADB or the SD card instructions? I was actually rooted with CM7 before the bootloop.
Thanks,
shy guy1 said:
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Click to expand...
Click to collapse
I realized that my zip was not working to uninstall and reinstall Air properly. Try the updated zip file in the post.
shelly29 said:
Did you use the ADB or the SD card instructions?
Click to expand...
Click to collapse
I used the SD card instructions. Unless you have done something strange to your nook (not sure what), it should always boot from the SD card first, so you should never have problems booting into CMR from an SD card.
If the link in the original post doesn't work for you to get a CMR SD card, try the instructions here:
http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
If you have a newer Nook, you may need to repartition your Nook's internal memory and use CMR version 3.2.0.1. See details here (this guy just condenses the instructions you can find on various posts on XDA, and tries to keep it up-to-date)
http://mrm3.net/nook-color-how-to-blue-dot-nook-color/
Also note that I updated the zip file in the post to correctly uninstall and reinstall Flash. I re=bootlooped my nook, and after applying the new zip, my nook was working.
Just an update....
I wanted to let U guys know that I had updated Adobe Flash, Air and Super Users and this has worked for me. I also went to double check the versions of both Flash an Air and they are the newest versions!? I still went to uncheck the "Update Automatically" setting in the market for them both just in case for future updates for the time being. Back up and Running! Thanks Again to ALL involved who put contributions to this
This may have worked for me
I tried the updated fix posted here, and the Nook booted properly. Thank you for this fix; I hope it continues to work for me.
I will have to locate the automated back up mentioned here (Titanium), and I will see how this works. I had been leaving my Nook on at all times to avoid the reboot until I turned it off yesterday, forgetting that I did not want to do that.
Awesome post.
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Thanks!!!! You are my new best friend. XD I ended up reflashing several times before I found this post. Followed the instructions and my Nook is happily running Android again without reinstalling (again!). I thank you. My Nook thanks you. And the Angry Birds who would have had to start from scratch thank you.
Thank you! It appears to work now. I've restarted a few times with success!
Took me about an hour to find this thead. I knew there would be an easier fix than starting from scratch. The zip worked on my rooted 1.2
Thanks! Keep up the good work
Thanks! That worked for me.
Stagnation1 said:
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Click to expand...
Click to collapse
From my previous searches, it seems the boot loop is usually caused by either an incompatible installation of Adobe flash, or an incompatible kernel (central part of the ROM). Hopefully the OP zip will fix the first, but I'm not sure of another way to fix the second, other than reflashing and rerooting. How far in the reflash/reroot process do you get before it boot loops again?
mastigia said:
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
Click to expand...
Click to collapse
Hmm, haven't seen that error. I'm not sure whether its related to the same problem. It sounds like you might need to re-register your nook with B&N. I'm not sure if you can do this without restoring to stock. Not much help, sorry.
I can't post a reply to this ([NC][1.2][1.3] ManualNooter 4.6.16) thread yet - Still new to these forums... I was one of the many in that thread who had installed ManualNooter 4.6.16 on Nook Stock 1.3 only to end up with a boot loop.
Wish I had found this thread last week - would have saved me a lot of headaches!
It's okay though - every boot loop is another opportunity to learn something new.
Thanks much for the easy walkthrough and I hope others find their way here too.
Just saw another new update for Flash & Air .. released yesterday I believe. Has anyone try them yet ? Just don't want to was my time getting into a boot loop again by updating it.
--

[Q] I'm a mess, CM7 back to stock

Hi. Ok so I rooted my NC to CM7 sometime last year, and now with all the blah about markets not working and having to do more about it, not to mention the PIA it is to get books on, I decided to put it back to stock. Which apparently was a big mistake.
First I mounted an older version of clockwork to the SD card, then when I figured that out (having format data error) I did the newer 3.2.x.x one. So that went good, I went through the steps and reformated data and system, and then went to upload the zip from the choose zip part, but it says there are no files. So I backed out, took out the SD and put it in my computer(Macbook pro) to try to put it in again but it wont show up at all? I tried looking in Disk Utility too and its not there. Any ideas where my card is? What do I do next?? I have nook complete restore 1.0.1, 1.0.0 and nook color update 1.4.1 on my desktop, I thought I had 1.0.1 on the SD card.
I've been reading and googling all over, I can't find what could've made my SD card disappear?
Thanks, I know you must get these all the time and I really appreciate your help-
Ok I didn't do anything, but it just started up to the little silver N and is now sitting there? Is that a good thing?
Don't panic. The NC is very hard to permanently brick. From what you've described, it sounds like your SD card may have gone bad or been corrupted. I'd just try again.
The 'n' logo is a good thing, but if it hangs there, be sure you've followed all the steps carefully. That's typically a sign that /data wasn't formatted, though from your description, you got that step.
Sorry I can't offer up anything more specific. Do be aware that you can restore back to 1.3 if you don't want to go back to 1.01
It happened to me and what I did is plugged my sdcard into my android phone and format it and start over again.
I did that couple time during first attempt to install CM7 on my nook
Hope this helps ! Good luck!
Try plug it into different computer(s) along with using usb-adapter.
The Eausus Partition program works well to wipe/format cards too...

[Q] Stuck at "read forever" - ManualNooter 5.02.12

Hello!
I have some problems rooting my nc with manualnooter 5.02.12. Before this I unrooted my device (by doing that: http://www.youtube.com/watch?v=szlGSBtWbKY) and then updated to 1.4.1 (working fine). Then I copied the manualnotter-zip-file on my "8gb_clockwork-3.0.2.8.img"-sd-card and installed the zip-file.
But at next start, my nook gets stuck at the "read forever"-screen forever. I tried this three times, always with the same negative result.
What am I doing wrong?
it seems your new image that you were installing may have had an error. I would try to download a new image, possible from a different site. It sounds like after wiping the boot not much else was installed
try wipe all, wipe cache and wipe dalvik cache, it's work for me
I had the same issue. I found that if I updated my sd card to CWM 3.2.0.1 and reloaded both the MN 5.02.12 and Dal's OC kernel zips I corrected the problem and didn't have to wipe or rebuild anything else.
edit the file in manualnooter-5.02.12.zip\tmp\scripts\uramdisk.sh
change the line below
mv /boot/uImage /boot/uImage.cwbak
to
#mv /boot/uImage /boot/uImage.cwbak
save and flash again,it work for me
sorry for my late feedback, had not much of time.
I will try your proposals later that day, thanks!
Ive been having the same problem as well. So I updated CWM , redownloaded mn, read some of the tips and finally got it working. I ended up having to wipe cache and i used the app2sd w/ the dalingrin kernel. Rebooted and then it was good. I assumed app2sd needs a sd card, but apps from the market saves to internal memory. I'm confused, but at least its working.
Sent from my BNTV250 using Tapatalk
blackpiranha said:
Hello!
I have some problems rooting my nc with manualnooter 5.02.12. Before this I unrooted my device (by doing that: http://www.youtube.com/watch?v=szlGSBtWbKY) and then updated to 1.4.1 (working fine). Then I copied the manualnotter-zip-file on my "8gb_clockwork-3.0.2.8.img"-sd-card and installed the zip-file.
But at next start, my nook gets stuck at the "read forever"-screen forever. I tried this three times, always with the same negative result.
What am I doing wrong?
Click to expand...
Click to collapse
I fixed the script problem in the 5.02.19 release. You can flash one of the kernel images to fix the problem. I am sorry about the problem.

Bricked NST Glowlight. Impossible to boot from SDcard (for Noogie)

Hey all!
I've been admiring e-ink even before it came out. This is why I finally purchased an old NST with Glowlight for damn cheap.
Now, I rooted it using:
noogie.img to mount the internal memory on the pc
a rooted uRamDisk image with USB adb
The device still wasn't rooted, so I downloaded an exploit. Which worked fine.
It has firmware version 1.2.1.
Now, eagerly, I've removed a very few system apps which seemed useless to me.
Yep, I've been stupid.
The Nook is now stuck in a boot loop. I see the "Nook" screen with the five "loading dots".
When I long-press the power button, it just reboots.
When I do "reboot -p" through ADB, it reboots.
When I remove the battery and put it back, it reboots.
It doesn't even turn off!
I wanted to:
mount the internal memory with noogie
mount my recovery img on the laptop
copy all system apps from the image to the nook
Or just reflash it with the recovery.
Yet, the system gets into this reboot loop, which would mean it doesn't even have the time to mount the SDcard, does it?
As attachment, the logcat. Full of errors.
If someone could help a dumb person, that would be nice
Thank you
Ps: It's my first post! This forum helped me a lot!
Something is screwed up with Relaunch.
Delete it and install something else.
There are many ways to unbrick touch, search the four subforums.
Then root with glownooter or similar
Update to firmware 1.2.1
Install kernel #166 by guevor
You might want to install nook touch hard buttoNs modmanager to reassign them
To back up:
Install CWM (bumped the thread yesterday), backup (has 2 internal & bigger external to sd), copy system backups to PC
I also use Titanium (see my thread: listing of my apps, version no.) To Backup my system data & apps, backup to PC
Super Manager also backups, but only apps apks.
Thank you !
I've already uninstalled Relaunch through adb. Problem remains.
I'm going to follow your instructions
unbrick:
http://forum.xda-developers.com/showpost.php?p=50025879&postcount=5
zeam launcher, screenshot:
http://forum.xda-developers.com/showthread.php?p=49470538
download:
http://forum.xda-developers.com/showpost.php?p=48813400&postcount=56
good luck
Hey!
Actually, the key combination for factory reset worked. I tried it before, though.
Thank you for your help

Categories

Resources