I used 2.3.5 JVT (+root) for some weeks perfectly fine on my Galaxy S I9000, though a bit laggy due to too many apps.
Today I rebooted the phone and got stuck in a boot loop. Never had that before.
I went into CWM recovery, wiped cache and did factory reset. Did not resolve a thing.
Then I flashed the whole phone again with the 2.3.5 JVT and it did not help either.
What can I do? The phone goes into download and recovery mode perfectly fine, so guess it's OK. I see Odin has an Option "EFS Clear". Would that help?
I would not tick that option. What happened when you flashed stock JVT with Odin? Bootloop?
Yes I use the stock firmware, that is firmware from sammobile.com (samfirmware.com). No fancy mods.
Tried with and without root. Both give me boot loops.
If you properly used Odin with the 3 files, pit, and repartition ticked, and you get bootloops after that then it goes beyond my experience. Maybe corrupted stock rom download? Download again stock JVS or JVT (change the one that you used before).
ok tried too other firmwares. still bootloops.
then i tried stock 2.3.3 and it went past boot screen. but it said UIDs inconsistent, need to wipe data partition. so i wiped data partition. but still same error.
seems like something strange is going on here. i'm always using 512 pit file and flashing with repartition checked!
that happened to me ,i just plugged in my charger and voodoo lagfix spoke then phone turned on apps were transparent set launcher default went into bootloop tried nandroid restore didnt work .eventually flashed 10.2 resurrection xxjvq worked a treat
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
thers a video on tube by totallydubbedhd or puggerdug shows u how but u probably already know ,hope it helps u
try flashing 2.3.4 XXJVP. this ROM worked for me while I went into a similar bootloop like yours once...while in 2.3.5 XXJVS. Then I reflashed JVS and it worked just fine.
I had similar and had to flash a stock rom to get it to boot. Then just root again...Took a while to figure this out. Very frustrating at the time!
.
OK tried a couple of other roms with no success. I read in another thread that someone had exactly the same problem and had Samsung fix it.
Now I am having a problem wiping my SDcard. The CWM backups are on the SDcard, right? So why can I still select them if I wipe the SDcard in Recovery?
OK, Samsung replaced the motherboard of the phone (warranty).
It's working again now.
So to everybody that is having the same problem, it is a hardware problem, most likely. But you will need to have tried everything else that could fix it beforehand, of course.
cdbee said:
OK, Samsung replaced the motherboard of the phone (warranty).
It's working again now.
So to everybody that is having the same problem, it is a hardware problem, most likely. But you will need to have tried everything else that could fix it beforehand, of course.
Click to expand...
Click to collapse
but warranty doesn't cover rooted/hacked phones lol?
HelloThere1 said:
but warranty doesn't cover rooted/hacked phones lol?
Click to expand...
Click to collapse
Yes, I resetted everything to stock.
Related
I have found that with some phones using ODIN to flash Froyo and then back to the stock 2.1 it will not repartition the internal. We need to find out how to repartition the internal memory back to stock. I believe whats going on is that because ODIN will not repartition the internal some of the data from Froyo is causing problems with 2.1. Thus causing bootloops, market place errors and not registering the modem or baseband says unavailable.Also not reading sim cards.
Reserved for a fix.
my phone was acting up so flash it with Eugene's Froyo that never brick then flash it back to stock 2.1, took me long time to find out a way using adb to reboot my system.. i tried doing the re=partition but it took a long time.. and there's no indicator that it is being partition.. so i just flash with stock 2.1 without re-partitioning the SD and it works like a charm.. after stock was installed.. i flash it again with bionix1.3..
Tried that didnt work. Also when you repartition it deletes all data on internal, I can check it to repartition and it will flash whatever rom im installing but doesnt repartition.
I also was able to re partition by flashing the Froyo that does not brick, then a ODIN flash of the stock 2.1 with the re partition box checked in ODIN. This worked great for me! Please view my post below for the fix info and the credits to who came up with it.
http://forum.xda-developers.com/showthread.php?t=788238&highlight=voodoo+brick
Did that too didnt work. As the OP states ODIN will not repartition my internal at all, I have tried everything in the forums. Lets put it like this I have been reading and trying everything that I have found for the last 2 weeks, nothing has worked. I will try every method posted in here and see which one fixes my phone.
Hmmm that's odd. Well hopefully you get it working.
jordanjf86 said:
Hmmm that's odd. Well hopefully you get it working.
Click to expand...
Click to collapse
Just tried the method you posted, still goes into a bootloop and wont read my sim. Also did not wipe my data or repartition my internal. Anymore Ideas are very welcome will try them all.
KellyLewis3985 said:
Just tried the method you posted, still goes into a bootloop and wont read my sim. Also did not wipe my data or repartition my internal. Anymore Ideas are very welcome will try them all.
Click to expand...
Click to collapse
Are you still able to get to clockwork recovery? You could just format sdcard in that. Then use odin without repartition.
T-Mobile Vibrant T959
ROM: Eugene373's Vibrant9
Kernel: Jac's ExtremeMod UV/OC
Lagfix: Voodoo beta4
Yes I have tried that and formatting all partitions in the partitions menu, didnt work either.
Please don't think I am assuming you did something wrong but you did use the Froyo that Eugene put out a while back right? the "Froyo that does not brick"? I just want to make sure you had tried that one. Im sure you have but just want to make sure because I flashed another Froyo out there and it messed up my internal memory and my phone was not recognized when I tried to mount it. Thank God it was still recognized in Odin.
I will explain what happened. I used the other froyo first, of course like an idiot. Well I didnt like it and just got the phone didnt read up like I should have and used a nandroid of Vibrant9, thats where it started it bricked right there. So I used odin to flash the froyo that doesnt brick, repartitioned and then did the flash back to stock and got nothing but a boot loop. Well I found a way to get around the boot loop and use the phone but market place and my signal suffer severly. Every since then the phone hasnt been the same its been depressed bc I havnt found a way to fix it yet.
I was on MidTeam 1.3. i decided to change my lcd density via an app and this messed up everything. i went to CWM and do a wipe/factory reset. After this the system failed. I flashed a GB rom via Heimdall, everything went well, the phone booted as usually, i've seen the "click android to start" screen but when i clicked on it phone freezed. I tried to flash different ROMs both customs and stocks, they are all being flashed via heimdall succesfully but stacked at the same place. I finally flashed CM9 (again via heimdall). It booted normally, i saw the lock screen, i unlocked it by touching the screen then the phone freezed again. I made a search on the forum but did not find a similar case. Can anybody help? CWM is working fine, i can do wipe/factory reset or mount any partition.
jayaka said:
I was on MidTeam 1.3. i decided to change my lcd density via an app and this messed up everything. i went to CWM and do a wipe/factory reset. After this the system failed. I flashed a GB rom via Heimdall, everything went well, the phone booted as usually, i've seen the "click android to start" screen but when i clicked on it phone freezed. I tried to flash different ROMs both customs and stocks, they are all being flashed via heimdall succesfully but stacked at the same place. I finally flashed CM9 (again via heimdall). It booted normally, i saw the lock screen, i unlocked it by touching the screen then the phone freezed again. I made a search on the forum but did not find a similar case. Can anybody help? CWM is working fine, i can do wipe/factory reset or mount any partition.
Click to expand...
Click to collapse
see if anything in my signature can help you... good luck!!!
Thank you for the answer. I've succesfully flashed LPY rom from the list you provided the phone restarted, boot animation is ok, then the phone stacked at samsung logo. I've waited like 45 min but nothing has changed. I gave a try with a gingerbread rom but the odin process was freezed during datafs. I'll try another GB and if same thing happens, will try LPY of LPF once again.
jayaka said:
Thank you for the answer. I've succesfully flashed LPY rom from the list you provided the phone restarted, boot animation is ok, then the phone stacked at samsung logo. I've waited like 45 min but nothing has changed. I gave a try with a gingerbread rom but the odin process was freezed during datafs. I'll try another GB and if same thing happens, will try LPY of LPF once again.
Click to expand...
Click to collapse
It looks like you have got a Superbrick on your hands, mate.
It looks so, but as the phone opens both in download and recovery mode and stock lpy rom can be flashed, i still keep the hope for a possible miracle :/
Happy End
After trying hundreds way, my galaxy note is working now.
every rom i try to flash via Odin had some issues. LPY was flashed with succes but stack at boot.
LPF was not able to write DataFS
but i was able to enter CWM. So i flashed abbys kernel. Then i realised that wipe/data factory reset was working.
I formated /data and /system
then i mounted /data
reboot in recovery
again i mounted/data and then flash darky's rom. Everything looks running properly now.
Never ever i'll try a lpy rom
dont try LPF and LPY roms for now..
dont know why they kept making roms for it despite the constant warning... i guess a lot of people love the thrill of bricking expensive things.. lol..
Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?
right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.
Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself
right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?
Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.
If you have tried also with the correct original pit, then it's time for the scanners to do its job
nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?
Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.
SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.
Ok. Try booting into recovery and performing a full wipe.
nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?
Yeah
nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.
right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
spiderman07 said:
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
Click to expand...
Click to collapse
Yeah I have done that. I have tried it about 10 times. Im going to give it another bash today as I am stuck using my wife's old Iphone and its horrendous.
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
spiderman07 said:
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
Click to expand...
Click to collapse
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Filipiak said:
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Click to expand...
Click to collapse
Found the pit file and read up on it. Tried to use it but it fails as soon as it starts.
Best of luck
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Knox was tripped when the firmware install crashed. So knox tripping is no issue. Thanks for the information. I will have a go tommorrow.
I did manage to restore a cm9 backup but my IMEI is now gone and I cant get to the menu to restore my back up. Seems like Samsung has done a number on my phone. In all the years ive been fingering phones with custom firmware and modding I have never had anything stuff up this bad. Its rather amusing that it has happened flashing a stock rom that belongs to my phone.
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Filipiak said:
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Click to expand...
Click to collapse
Cheers
Filipiak said:
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
Click to expand...
Click to collapse
It happened to me once, i found that 4.3 won't boot if baseband and imei are unknown. when you were trying to flash with odin and your phone got stuck it probably has damaged or ( erased ) your imei partition. try flashing 4.1.1 ( the package file without bootloader files ) it will definitely work for you. the reason is simple , Samsung's stock 4.3 never boots if the imei is corrupt or unknown (baseband is then usually too ) so, flash 4.1.1 , root your phone and install Persus kernel +any modem / baseband file, this is the only solution as i dont know how but does repair your imei , but you will be stuck at 4.1.1.
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Cummins4 said:
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Click to expand...
Click to collapse
If it's still happening after two Odin flashes something is seriously wrong with your phone. It started force closing out of the blue? Your sure you weren't poking around in partitions other than system and data?
No, everything was working fine on looper. I flashed Alliance in the 925t thread. Let it boot, went back twrp then flashed latest kt kernel. That's when I started to get the fc. Figured I did something wrong, so Odin stock tar. Still getting the fc. Sorry for the miss post. Just frantic..
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Cummins4 said:
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Click to expand...
Click to collapse
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
ThePagel said:
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
Click to expand...
Click to collapse
Thanks, lesson learned.. Been flash dozens of ROMS since my s2, first-time ever I couldn't save a device. Just so weird. Tried stock tar right from Sammy with everything wiped. Wish someone had an idea what would've caused it. Right Odin, right tar, Samsung cable, different computers... Just think I'll leave it alone from now on. Too expensive to mess around with this device, especially without a reliable fall back.
Just wondering if anyone had any idea on how to fix a force close loop after stock Odin flash? I bought a new device. Obviously my warranty is void. I didn't have insurance. I'm left with a really shiny paperweight. I'm willing to try anything, thanks in advance.