Related
NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others
sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App
If you look at Darkyy's rom he has a script that does this.
Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.
Tested and works with Rogers 2.2 Rom. Thanks
skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks
Works great on Rogers 2.2. Thanks
I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+
I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.
I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.
Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?
Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
While trying to do some mods and themeing I did something very stupid... instead of replacing the framework-res.apk file I first decided to rename it to framework-res.apk.bak
Since that moment I just can't start the phone... it's stuck on loading animation. I've tried to reboot, to wipe, even installed CyanogenMod (the phone is rooted and bootloader unlocked)... the CyanogenMod is installed right now, but after it loads (after the blue animation with the rotating arrow) it shows up the screen with the green droid with two buttons at the bottom - "Emergency call" and something else... and after 5 seconds it restarts back again.
I've tried to push the original file (I have a copy on my computer) but the adb.exe doesn't want to connect to the phone. I can enter in recovery, but there is no way to copy or rename file through there
PLEASE HELP
Use flashtool to flash the original rom you were using, just uncheck the box to wipe user data.
sinkster©
sinkster said:
Use flashtool to flash the original rom you were using, just uncheck the box to wipe user data.
sinkster©
Click to expand...
Click to collapse
Nope... nothing new It loads the Sony Erricson animation and than restarts back again...
I could do: adb push framework-res.apk /system/framework/framework-res.apk
But how run the adb?!?! It always shows me: error: device not found
sinkster said:
Use flashtool to flash the original rom you were using, just uncheck the box to wipe user data.
Click to expand...
Click to collapse
That was bad idea Because now the phone is with the original rom, ie. it's not rooted and it doesn't have recovery (bootloader is locked) and even the USB DEBUGGING and UNKNOWN SOURCES are OFF by default... So now there is absolutely no way to access anything...
Any other ideas?!?!
estilian said:
That was bad idea Because now the phone is with the original rom, ie. it's not rooted and it doesn't have recovery (bootloader is locked) and even the USB DEBUGGING and UNKNOWN SOURCES are OFF by default... So now there is absolutely no way to access anything...
Any other ideas?!?!
Click to expand...
Click to collapse
Find one of the theme packages that can Flash over recovery and flash them. Make sure it contains Famework-res.apk.
You should be able to use adb within recovery.
And how to enter recovery after I installed original rom from Flashtool?
I only can get in fastboot mode and flash mode... because the USB DEBUGGING and UNKNOWN SOURCES are OFF...
P.S> Or give just a tip - how to install a zip update (new theme with new framework-res.apk) at current stage?! Is there a way to do this through Flash mode in Flashtool or through fastboot?!
Flash a kernel with built-in recovery such as this, Advanced Stock (with recovery).
doomed151 said:
Flash a kernel with built-in recovery such as this, Advanced Stock (with recovery).
Click to expand...
Click to collapse
Good idea, but the link from mutliupload.com is closed by FBI Anti-Piracy program I get only a message and can't download the file
Nope... nothing helps. I managed to install the new kernel, after that I installed new theme... - no change, still restarting. Even tried with pushing the framework-res.apk with: adb push framework-res.apk /system/framework/framework-res.apk
Again - restarting
Any other ideas?
You'll need to flash a rom, not a theme. Use fastboot to flash doomkernel then fastboot to flash arconium or similar, wipe userdata in cwm, reboot then flash your theme.
sinkster©
You said you had CMW recovery, so....
Y U NO MAKE BACKUPS???
Always make nandroid backups before editing system files. It will save you A LOT of time and disappointment.
Since you are in this situation now, do as others adviced you above.
iR¡[email protected]!* via Tapatalk
Of course I had backup This is always the first step before doing anything... but it didn't help! I don't know why... it just didn't!
Here is what I had to do to make the little arc work again:
1. I installed new kernel which has included recovery in it;
2. Through the recovery I did Factory Reset / Wipe data / Wipe dalvik
3. Reboot
4. Through the recovery I started the ADB and did a copy of the original file with this function:
adb push framework-res.apk /system/framework/framework-res.apk
Click to expand...
Click to collapse
5. Through the recovery (without rebooting) I installed the original Generic version, BUT HERE IS THE IMPORTANT THING - moving from 4.0.2.A.0.42 to 4.0.2.A.0.62
After all... it started normally It's important to mention that after each step I was trying to start the phone, but it was still rebooting... so it's logical to say that the key step was the final one.
This is interesting...
When you say backup didn't work, what do you mean? Did you do an advanced restore (system only) or a full restore?
Were you not able to go into recovery at all?
I am asking because I am involved in a project regarding recovery integrated in /system (so for locked bootloaders) and any info would be very valuable! Thanks!
iR¡[email protected]!* via Tapatalk
Right basically if you've followed my last thread, http://forum.xda-developers.com/showthread.php?p=27975788#post27975788 it turns out I haven't got anywhere really. Today I managed to flash both froyo and GB but after trying to root both and install a custom ROM it would fail and I'd end up in a bootloop. Normally I'd just reinstall the dload files from the SD card and start again. Now however, when I go to boot the dload files, I get pink a screen (with usb plugged in I have the image folder with various files). When I try and boot recovery, nothing happens, I've tried replacing the recovery image, but no success. So now I'm left with a phone that does pretty much nothing other than bootloop or turn pink on command. Any suggestions on what I can do to install froyo or GB?
Sorry and thanks again.
Before root the rom(s) run ok?
And how you root the device? Also are you sure that the root have success? How you check it?
The root was fine, followed the instructions from the thread in dev section, ran the one click root everything was fine, swapped the recovery to get v5 used remount and astro explorer. went to CWM, made sure i had a rom that ran with the kernel, installed it everything said it was fine reboot into a loop. my options now are boot loop or pink screen, it wont even pick up the dload from the sd card.
So the bootloop happen with the custom rom you flashed from recovery mode?
Which rom you flashed? Did you wipe data/cache/dalvic_cache before the reboot?
Indeed I did. Something corrupted in the image folder. So I found a custom Image folder by the guy who's developed the v5.5 of CWM. In his signature theres a load of zip files one of them had a custom Image folder which Ive swapped in to which the phone has read the dload files now finally. Im hoping this will work.
If the device boots fine with the official roms, and bootloops with the custom, there is nothing wrong with the image file. The problem is with the rom that you try to flash and maybe with the recovery version.
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Dave759 said:
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Click to expand...
Click to collapse
The only cases I can think a custom ROM won't work are
- installing a .32 ROM over a ROM based on .35 and vice versa
- installing a custom ROM without wiping data and caches of the previous ROM, especially if they are not related, like not different builds of the same ROM
- installing a .32 ROM using cwm other than 5.0.2.6 and below
- installing a .35 or ics ROM using a cwm other than 5.5.0.4 or 5.0.2.7
Are you sure you did none of that?
Sent from my U8800
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Finding installed ROM
sjs_bebop said:
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Click to expand...
Click to collapse
Go into system settings / about tablet (at bottom of settings)
About 3/4 down list you'll see the ROM installed. Also kernel info plus other info.
For updates ;
I go to this link and download directly.
http://download.cyanogenmod.org/?type=nightly&device=encore
Also I copy and paste the md5 sum into MD5 checker (free in play store), run the check.
Reboot into recovery using power button menu and install in TWRP there. I had too many problems using cm downloader, goo manager, etc.
nook color cm10.2 update problems
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Sounds like a problem I had a while back
sjs_bebop said:
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Click to expand...
Click to collapse
You may be having partition problems. I have had either lost the ability to install new nightlies or the ability to backup. Read the instructions through completely first. Get the info together and then start.
If you have a backup App like titanium backup, backup all files and data before anything else. Also if you can, do a backup in recovery before doing the following.
Check this link: http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 by Leapinlar
I set up a 2Gb sd bootable card to run these from using the CWM recovery (If you need help check eyeballer's link below).
I put the partition repair files on it. Also the 1.4.3 Stock rom, the TWRP open recovery. zip 2.4.1.0 (http://forum.xda-developers.com/showpost.php?p=37554712&postcount=129), and the latest Rom you want to install and Gapps.
After following leapinlar's instructions including installing the 1.4.3 Stock rom (fixes other possible problems), then follow eyeballer's install for the Rom, Gapps and recovery here (http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color).
After booting and doing the initial CM setup return to recovery and VERY IMPORTANT ***restore only the data*** Not boot or system from your latest backup. This should get you back up and running. If you have a backup like Titanium restore "newer versions of apps" if you had to use an older recovery backup. Once you have everything set reboot into recovery and do another backup for safeties sake.
Including my wife's Nook I have four units and have needed to do this 4 or 5 times. Takes a little time but has always worked great. I keep the card available and update the Rom, Gapps or whatever else needs changing.
This link also contains a lot of helpful info. I have all these bookmarked on both my PC and Nook.
User Tips http://forum.xda-developers.com/showthread.php?p=25354258#post25354258