Database Users

[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel

Simple way to root and unroot stock kernel without flashing insecure kernel.
Don't worry about custom counter and yellow triangle, with this method they never appear, because we only rooting, it's a rooting script not a custom kernel.
This rooting script included Busybox installer.
Rooting
Download this File first and put in your SDCARD
- MOD EDIT: Links removed as its the unsafe version...
or download zip from http://clockworkmod.com/rommanager
- SU-Busybox-Installer.zip
Reboot to recovery.
Choose apply update from external storage.
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard or external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your SDCARD
- MOD EDIT: Links removed as its the unsafe version...
or download zip from http://clockworkmod.com/rommanager
- SU-Uninstaller-Signed.zip
Reboot to recovery.
Choose apply update from external storage.
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Tested on latest stock Galaxy S II ICS rom.
Tested on latest Galaxy Note by some user (thanks for report)
Note: This method should work for other device with ICS rom, check CWM that compatible for your device here http://clockworkmod.com/rommanager
Mirror:
CWM.zip - MOD EDIT: Links removed as its the unsafe version...
SU-Busybox-Installer.zip - http://turbobit.net/gg8gyz535ouo.html
SU-Uninstaller-signed.zip - http://turbobit.net/7miov7grs1m1.html
Please
and don't forget to hit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you like my work.

Didn't work for me I am on stock LA4...went to stock recovery..tried flashing cwm.zip E: signature verification failed....any advice
Sent from my GT-I9100 using Tapatalk

Tested on stock XXLPB, everything working as expected
Thanks !

worked perfectly on LPH. I reset my counter with Jig, updated to LPH(the bootloader too) and used this to use CWM and root. I ended up restoring my CM9 backup and now I'm on the new bootloader(feels faster, may be just me) with no triangle. Thanks!

Do you loose the ability to install apps to sd card like when you use CF-Root kernels or is it a safe method?
Thanks
---------- Post added at 07:39 AM ---------- Previous post was at 07:38 AM ----------
freemini said:
worked perfectly on LPH. I reset my counter with Jig, updated to LPH(the bootloader too) and used this to use CWM and root. I ended up restoring my CM9 backup and now I'm on the new bootloader(feels faster, may be just me) with no triangle. Thanks!
Click to expand...
Click to collapse
About the bootloader that came with lph, when you select it, do you also check update bootloader in odin?
Thanks
---------- Post added at 08:29 AM ---------- Previous post was at 07:39 AM ----------
root is there but it is not working.
Tried with titanium Backup.. failed.

MasterTB said:
root is there but it is not working.
Tried with titanium Backup.. failed.
Click to expand...
Click to collapse
Try to redownload now, i already fix the SU permission
http://dl.dropbox.com/u/34053267/SU-Installer-signed.zip

Hi
CWM is possible?
Yeah Odin-PDA flashen:Touch_recowery
http://data.hu/get/4744534/STOCKPLUS-GT-I9100-XXLPH-KERNEL-TOUCH.tar

Thanks for sharing this method, will try it out.
But please increase the font size in OP, it's stressful for eyes.

bajusz66 said:
Hi
CWM is possible?
Yeah Odin-PDA flashen:Touch_recowery
http://data.hu/get/4744534/STOCKPLUS-GT-I9100-XXLPH-KERNEL-TOUCH.tar
Click to expand...
Click to collapse
As you have done you please do?

Still not working INDIAN GT-i9100 model on latest 4.0.3 LPH Stock Rom.
Rachmat3 said:
Try to redownload now, i already fix the SU permission
http://dl.dropbox.com/u/34053267/SU-Installer-signed.zip
Click to expand...
Click to collapse
the above link doesnt work not even the original one.. when i reboot i can see su and while installing tb patcher it does ask for root access but while activating patch it say root access denied

You may have the Holy Grail here - a rooting method that doesn't need USB/PC connection.
As far as I know, there is nothing else that can do this.
Market it as such, and you're on a winner.
Any reason why someone without said connection abilities couldn't root with this ROM and then change accordingly?
Still many who don't want ICS, but I'd be interested to hear if anyone's rooted via this method and then successfully changed to GB.

Sounds good thanks for sharing..

the cwm screen blink and reset, they is a problem.
I need to use internal sd or external sd ?

This will trigger the yellow triangle?

GRACO said:
This will trigger the yellow triangle?
Click to expand...
Click to collapse
Its not a kernel, so this will not give you yellow triangle.

Will work on 2.3.6 ?
I'm on official XWLA4.
If it does first i install the CWM.zip and then the SU-Installer-signed.zip ?

It still says "signature verification failed"
Any luck boys?
---------- Post added at 01:10 AM ---------- Previous post was at 01:03 AM ----------
My bad! Works fine...
For those who are still stuck, please flash the CWM first and then flash the SU Signed zip file...
This works on ICS as well...
Thanks mate, you ROCK!

Didnt work for me.
Tried to flash but both packages say signature verification failed...
Any solution to that?

angelossssss said:
Didnt work for me.
Tried to flash but both packages say signature verification failed...
Any solution to that?
Click to expand...
Click to collapse
It only work on ICS, i will try to make it work for GB.

This is perfect! Almost too good to be true! Thanks!

[Q] /system/etc/gps.conf

adb sideload the kitket update zip is fails with following error:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?

alexroz said:
adb sideload the kitket update zip is fails with following error:
View attachment 2408712
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/showthread.php?t=2525947
you MUST reflash a kind of stock/not gps moddified version :/

Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.

EvilAaron said:
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
Click to expand...
Click to collapse
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.

eksasol said:
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
Click to expand...
Click to collapse
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers

EvilAaron said:
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
Click to expand...
Click to collapse
The flashing will required an unlocked bootloader, so if its not unlocked you will lose all data when unlocking it. (Doing a factory reset in stock recovery also wipe everything.)
I don't really know what else you can do, if there were never any modifications, then the problem is due to Google having too much protections and issues for their OTA packages.

Unlocked so can do the method in your guide. But she says she wants to clean up her phone so a clean start will probably perform better and she gets the clean slate she wants, problem solved Though OTA checks annoy me now lol
thx for the feedback and guides

[OTA] Stock XNPH25R OTA

Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000

I'm getting binary update script error by flashing with TWRP

I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!

With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?

Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.

iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me

Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")

I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok

Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?

ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.

housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO

truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One

housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO

truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One

housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO

Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app

truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.

fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.

ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?

Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk

Full stock receiving an update today

I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.

Milkman00 said:
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Click to expand...
Click to collapse
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.

pre4speed said:
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
Click to expand...
Click to collapse
400 megs for Stagefright? That seems pretty big.

OC2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Milkman00 said:
400 megs for Stagefright? That seems pretty big.
Click to expand...
Click to collapse
Yeah it was 380 for the S5 too.

Thanks for the info. This was the only site that had ANY information about the update.

I'm on Lollipop, but Rooted. Will this update take away root by any chance?

My question exactly!

sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
Typically these updates do remove root. Best to wait until someone has a root method figured out for the new update.

sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
I just updated via the OTA method on AT&T. Rebooted twice. I still have root (verified by Root Checker). Here's my About page:
Here's the root checker pic:
I now have OC2. Update OTA with confidence!
I originally rooted OC1 (Lollipop) by following the Root/OC1 method.
EDIT: I just checked for stagefright vulnerability (via Stagefright detector). It reports that my device is NOT VULNERABLE. Nice.
I took the chance because this site has helped me in sooo many ways. It's the least I could do. Thanks everyone.

I'm rooted and my update failed at 26%
Sent from my SAMSUNG-SM-N900A using Tapatalk

Update failed for me at 25% too. I'm rooted OC1.

Does this update do more than just fix the stagefright exploit?
If not, then kmokhtar already posted a flashable update fix for stagefright which works great.

Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...

Why is this 'update' 5.0? I could have sworn it was just up to 5.1.1

KestrelX said:
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...stagefright-vulnerability-fix-note-3-t3175087

Can confirm that the update worked for me on rooted OC1, now shows OC2 and I retained full root on my phone.

ATT Ota file
https://mega.nz/#!TdE02KwJ!m4pkNivN9q2ZB7hGuXFiq872UoB8D-F-QpiPVX4sWI0

mine worked I am still rooted no problems no failure

peterson65 said:
mine worked I am still rooted no problems no failure
Click to expand...
Click to collapse
Those like me who have installed modded apps like S6 and have mixed in deodexed files, the OTA will fail. the OTA installer MD5 checks the system files and if any fail it will abort the Update. Any deodexed system files will also abort the Update
How to updated to OC2 if your OTA failed
1. Download and unzip and copy this Folder to OC1 stock root backup to your TWRP backup folder,
\TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Copy OC1 kernel recovery installer to your sdcard SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
*** You can also go ahead and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk and NC2 Flasher to your sdcard ***
3 Download the OC2 OTA 2400258.cfg
rename the 2400258.cfg OC2 to 2400258.zip and copy to your sdcard
4 Install the OC1 backup,
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip
5. Install OC1 Kernel
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
6. (I did a factory wipe , but Warning you will loose UserData settings and Apps you installed) You might try without but if you had a custom SystemUI and Touchwiz as I did it might FC because you have setting in Userdata pertaining to the Custom apps that you will over write with the OC1 backup.
7. Select Reboot and then select Recovery to boot to stock recovery and install as a update from external storage. mine installed with no issues.
8. To get safe strap back working Download and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk to sdcard (if you have not done yet)
9. Download and copy NC2 Flasher by benwaffle
10. Install Safestrap-HLTEATT-NC2-3.75-B03, run app and install recovery ( do not press reboot to recovery, it will only take you to stock recovery)
11. Install NC2 Flasher app and then use it to boot to recovery.
12. Do a backup of your new OC2
Now you can customized and do what you want

TWRP doesn't flash anything

I have flashed stock MM rom , now whenever i try to flash any kernel twrp freezes and phone restarts to recovery, I've used this armoa supported TWRP https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
latest official TWRP and also latest Orangefox, all had the same issue, what should I do?
UPDATE: Problem resolved after reflashing the stock and debloating it, not sure which one did the trick but anyways it worked!

A.Rahman96 said:
I have flashed stock MM rom , now whenever i try to flash any kernel twrp freezes and phone restarts to recovery, I've used this armoa supported TWRP https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
latest official TWRP and also latest Orangefox, all had the same issue, what should I do?
Click to expand...
Click to collapse
If you can flash rom, Gapps or any other things expect kernel, then your twrp works fine and you flash the wrong kernel for that one(you flashed the another model)
And maybe it's bc of your twrp that can't flash kernel and need the special one that the kernel dev should be mentioned
Would you please share the link or give me more details?

amirizad_7436 said:
If you can flash rom, Gapps or any other things expect kernel, then your twrp works fine and you flash the wrong kernel for that one(you flashed the another model)
And maybe it's bc of your twrp that can't flash kernel and need the special one that the kernel dev should be mentioned
Would you please share the link or give me more details?
Click to expand...
Click to collapse
yes, I can flash everything else except kernels.
the issue is all TW 6.0.1 kernels here have their links removed so I just have them from re-uploaders outside of xda forums, here is a kernel of a total of 3 kernels that don't even flash no matter what recovery I'm using
http://www.mediafire.com/file/040tj212gjqfzzp/J500H-Kraken-R4_Nyell.zip/file
and thanks for the reply
update: the recovery doesn't freeze in the middle of the procedure. it freezes at the very beginning like "checking digest files" and things like that

A.Rahman96 said:
yes, I can flash everything else except kernels.
the issue is all TW 6.0.1 kernels here have their links removed so I just have them from re-uploaders outside of xda forums, here is a kernel of a total of 3 kernels that don't even flash no matter what recovery I'm using
http://www.mediafire.com/file/040tj212gjqfzzp/J500H-Kraken-R4_Nyell.zip/file
and thanks for the reply
update: the recovery doesn't freeze in the middle of the procedure. it freezes at the very beginning like "checking digest files" and things like that
Click to expand...
Click to collapse
How do you install kernel?
Would you explain
It's img file or zip file

amirizad_7436 said:
How do you install kernel?
Would you explain
It's img file or zip file
Click to expand...
Click to collapse
it's a zip flashable file

A.Rahman96 said:
it's a zip flashable file
Click to expand...
Click to collapse
That's the problem. Unpack the zip and there should be a boot.img inside. No wonder it wasn't working.

garylawwd said:
That's the problem. Unpack the zip and there should be a boot.img inside. No wonder it wasn't working.
Click to expand...
Click to collapse
already tried that, but have you looked at the file? it has patches for wifi and things like that, when I extracted the zip file and flashed only the boot.img the rom worked but without wifi and with a lot of bugs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

A.Rahman96 said:
I have flashed stock MM rom , now whenever i try to flash any kernel twrp freezes and phone restarts to recovery, I've used this armoa supported TWRP https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
latest official TWRP and also latest Orangefox, all had the same issue, what should I do?
Click to expand...
Click to collapse
Try using an earlier TWRP, the 3.3 version has trouble flashing some zips

Problem resolved after reflashing the stock and debloating it, not sure which one did the trick but anyways it worked!