If i try to uninstall magisk from my Honor 8 i will end up with a bootloop until i reinstall magisk.
I tried to uninstall from the app and with the uninstaller zip same result.
Does someone know how to fix this
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Didgeridoohan said:
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Click to expand...
Click to collapse
OK so did as you said but i still get bootloops . No idea how something like that can happen but something seems not right guess i am stuck with magisk installed until i wipe and reinstall it completly.
resov said:
OK so did as you said but i still get bootloops . No idea how something like that can happen but something seems not right guess i am stuck with magisk installed until i wipe and reinstall it completly.
Click to expand...
Click to collapse
Did you try a complete dirty flash of your ROM/firmware package/factory image?
Didgeridoohan said:
Did you try a complete dirty flash of your ROM/firmware package/factory image?
Click to expand...
Click to collapse
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
resov said:
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
Click to expand...
Click to collapse
Dirty flashing means you don't wipe your data.
It's possible there's some kind of verified boot thing that you're going to have to restore, or something like that. Ask in your device's forum.
resov said:
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
Click to expand...
Click to collapse
Not magisk, it seems to be something with your device, some samsungs too.
Seems lke this happens to phone's that has auto-encrypted /data partition. This happens to me on a Samsung S7 (Android 8/oreo) and my "stock os" has auto-encrypt of /data if /system is touched. When uninstalling via Magisk, usually Magisk will restore your original boot.img (it did so during my uninstall, but still i get bootloop). Tried two nandroid's done of just boot-partition, but only one of them worked, and it only worked if I reinstalled Magisk. Without magisk I had bootloop's with all my stock.img availible (ps: i've not yet tried the "dirty flash replacement of the boot.img", I guess using ODIN? But hey, dunno if it is the AP,BL,CP,or CSC part that needs to be dirty-flashed then, so since im tired of setting up the /data patition (going through first phone install, installing apps and settings again, then I'll wait for further/better info.
But hey
Didgeridoohan said:
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Click to expand...
Click to collapse
I don't know how to thank you, you saved my life!
Related
First, Happy Thanksgiving to any/all US users!
Happy Thursday to everyone else.
I have read the other threads related to bootloop issue, however, none seem to address my particular issue.
I will try to give as much info as I can......
I am rooted, unlocked bootloader, TWRP installed.
I used fastboot method, not a tool
I have Xposed, and have using several modules and have not experienced any issues until today.
I downloaded fonts from the playstore.
Made a nandroid backup.
I noticed when nandroid was running, it said something to the effect of no backup of boot and no backup of recovery.
I googled this and only found a few posts on the internet that mentioned it, and from what I could tell, I shouldn't worry about it ( :facepalm: )
Went into Xposed, placed a check next to ifonts, and rebooted phone.
I've been in a bootloop ever since.
I can boot into recovery, and attempted to restore the nandroid backup. When it completed, I restarted the system, only to find myself stuck in bootloop.
Went back into recovery, and did another restore from a backyup I did in TWRP a week ago.
When it completed and I restarted system....bootloop.......
OK!
So I thought perhaps I lost my boot image somehow.
Restarted to bootloader, and opened command prompt and ran
fastboot flash boot boot.img
Powered off the phone, then attempted to restart system.....bootloop.
Anyone have any suggestions/advice/directions?
I would be ever so grateful, and THANKFUL, for any assistance offered.
totallybeachin said:
First, Happy Thanksgiving to any/all US users!
Happy Thursday to everyone else.
I have read the other threads related to bootloop issue, however, none seem to address my particular issue.
I will try to give as much info as I can......
I am rooted, unlocked bootloader, TWRP installed.
I used fastboot method, not a tool
I have Xposed, and have using several modules and have not experienced any issues until today.
I downloaded fonts from the playstore.
Made a nandroid backup.
I noticed when nandroid was running, it said something to the effect of no backup of boot and no backup of recovery.
I googled this and only found a few posts on the internet that mentioned it, and from what I could tell, I shouldn't worry about it ( :facepalm: )
Went into Xposed, placed a check next to ifonts, and rebooted phone.
I've been in a bootloop ever since.
I can boot into recovery, and attempted to restore the nandroid backup. When it completed, I restarted the system, only to find myself stuck in bootloop.
Went back into recovery, and did another restore from a backyup I did in TWRP a week ago.
When it completed and I restarted system....bootloop.......
OK!
So I thought perhaps I lost my boot image somehow.
Restarted to bootloader, and opened command prompt and ran
fastboot flash boot boot.img
Powered off the phone, then attempted to restart system.....bootloop.
Anyone have any suggestions/advice/directions?
I would be ever so grateful, and THANKFUL, for any assistance offered.
Click to expand...
Click to collapse
your phone cant run without a boot.img, thats the kernel and it controls the whole phone. it would never ever boot up without. anyways, what you need to do is wipe data in twrp, then reflash your rom and supersu.
I don't want to sound ignorant, but I'm going to anyway...
Could you please tell me which file is my rom?
I followed the guide(s) for rooting, and downloaded the files as were instructed, and as far as I know, I didn't download a ROM.
Only a custom recovery (TWRP), a modified boot image, then flashed SuperSU through TWRP.
Is the ROM on my phone somewhere? I can boot into recovery and look through file manager.
I also have TitaniumBackup. Would it be in a backup from that app somewhere?
Oh I didn't see the above question. So no, while the rom is on your phone, it's not in any flashable form, so you should download the latest factory image for shamu and flash that, a modified boot image for that version, and then root it. Do a factory reset, clear cache and dalvik, and you shoulbe up and running.
factory reset/wipe data might fix it, if not, then you need to flash a factory image(since you dont have a flashable cystom rom).
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
totallybeachin said:
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
Click to expand...
Click to collapse
system.img is your rom. recovery.img is your stock recovery
---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------
totallybeachin said:
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
Click to expand...
Click to collapse
factory reset and you wont lose root. factory.img and you will lose root. a custom rom requires twrp recovery, a custom kernel(for root), and the latest supersu.
Are you sure that it's not the xposed module is causing the bootloop??
use TWRP filemanager to delete /data/data/de.robv.android.xposed.installer/conf/modules.list
and try to boot again
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
eta:
Factory reset did nothing....
totallybeachin said:
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
Click to expand...
Click to collapse
Sure, otherwise it wouldn't boot
totallybeachin said:
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
eta:
Factory reset did nothing....
Click to expand...
Click to collapse
a rom always has a kernel included, as thats what ties the software rom to your hardware phone. it ties your cpu to it, your buttons, etc.. all to your rom. its also like the btain center to your phone.
Alright!
I seem to be back up and running.
Now I just have to spend the day getting my device back the way I had it before I crashed.
If I try and use my restore from Titanium Backup, will that mess anything up since it was made on a different ROM? Or, is that just a backup of my apps and stuff?
I want all my modules from Xposed, my wallpapers and stuff......
Thanks for all your help!
eta:
Also, SU says 'installed" in the play store, bu it's not showing up in my app drawer??? (And there is no option to 'uninstall' like any other app would have--weird)
totallybeachin said:
Alright!
I seem to be back up and running.
Now I just have to spend the day getting my device back the way I had it before I crashed.
If I try and use my restore from Titanium Backup, will that mess anything up since it was made on a different ROM? Or, is that just a backup of my apps and stuff?
I want all my modules from Xposed, my wallpapers and stuff......
Thanks for all your help!
eta:
Also, SU says 'installed" in the play store, bu it's not showing up in my app drawer??? (And there is no option to 'uninstall' like any other app would have--weird)
Click to expand...
Click to collapse
Maybe the dev has put an icon in settings for supersu.
And for future: don't forget the trick i posted above to disable modules
Droidphilev said:
Maybe the dev has put an icon in settings for supersu.
And for future: don't forget the trick i posted above to disable modules
Click to expand...
Click to collapse
Yeah...I found it there instead of app drawer.
And the 'trick'.....I didn't have this after data
de.robv.android.xposed.installer/conf/modules.list
I'm doing the installing, it's like half a hour and it still says "patching system image unconditionally..."
Am i stucked? should i wait or reboot and try to install again?
nanbo3 said:
I'm doing the installing, it's like half a hour and it still says "patching system image unconditionally..."
Am i stucked? should i wait or reboot and try to install again?
Click to expand...
Click to collapse
Surely it's a little bit abnormal. Mine usually uses less than ten minutes to get installed via TWRP.
You might need to wipe your system/ data/ cache partition completely and redownload the ROM.
maao666 said:
Surely it's a little bit abnormal. Mine usually uses less than ten minutes to get installed via TWRP.
You might need to wipe your system/ data/ cache partition completely and redownload the ROM.
Click to expand...
Click to collapse
Either way should be safe with TWRP installed.
nanbo3 said:
I'm doing the installing, it's like half a hour and it still says "patching system image unconditionally..."
Am i stucked? should i wait or reboot and try to install again?
Click to expand...
Click to collapse
I got same issue as you, tried different versions of TWRP but always stuck at "patching system image unconditionally...".
Didn't find any solution for now...
Manwex said:
I got same issue as you, tried different versions of TWRP but always stuck at "patching system image unconditionally...".
Didn't find any solution for now...
Click to expand...
Click to collapse
Smarty TWRP?
jazz452 said:
Smarty TWRP?
Click to expand...
Click to collapse
I tried even that one, but the problem still persists unfortunately.
It simply gets stuck at "Patching system image unconditionally..."
Manwex said:
I tried even that one, but the problem still persists unfortunately.
It simply gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
Did you tick read write under mount in TWRP?
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
aliensk said:
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
Click to expand...
Click to collapse
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
lept_2014 said:
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
Click to expand...
Click to collapse
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Hey guys,
I managed to resolve the bootloop issue. If anyone has the same issue use the following untouched boot.img
https://xiaomifirmware.com/download/11657/
As I was suspecting, the ones I was using the from the links provided in the forum were too small and this one is 64 mb. After flashing it boots perfectly.
However, unfortunately again I get errors during the update. At least no bootloop
aliensk said:
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Click to expand...
Click to collapse
That Stock BOOT works fine for me. Remember flash it into the right slot for you.
I did flash to to slot B as the getvar current-slot was B but it was still bootlooping until i tried the last one from the link I provided. However, since I am still unable to update, is there a link to download the system.img for 10.0.3.0 just in case i have somehow modified my system? I dont remember to have done anything but just in case.
Thank you.
How will you solve it
Plz...tell me with boot file how fill solve your problem
Varshithpoudala said:
Plz...tell me with boot file how fill solve your problem
Click to expand...
Click to collapse
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
aliensk said:
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
Click to expand...
Click to collapse
Did you find any way to fix it?
Hello. I restored the stock images in magisk, I thought. I tried to do a complete uninstall but it failed. So I fastbooted the April update and it's stuck in a bootloop. I fear I might not have uninstalled magisk. Is there help for me? I tried flashing stock boot image, factory reset, flash all stock. I'm in a pickle. Somebody help me. Thanks
madmuthertrucker said:
Hello. I restored the stock images in magisk, I thought. I tried to do a complete uninstall but it failed. So I fastbooted the April update and it's stuck in a bootloop. I fear I might not have uninstalled magisk. Is there help for me? I tried flashing stock boot image, factory reset, flash all stock. I'm in a pickle. Somebody help me. Thanks
Click to expand...
Click to collapse
If you don't care about the data on the phone, just do a full flash with wipe.
madmuthertrucker said:
Hello. I restored the stock images in magisk, I thought. I tried to do a complete uninstall but it failed. So I fastbooted the April update and it's stuck in a bootloop. I fear I might not have uninstalled magisk. Is there help for me? I tried flashing stock boot image, factory reset, flash all stock. I'm in a pickle. Somebody help me. Thanks
Click to expand...
Click to collapse
Do #4 'keep data' to install April factory image. Do #9 to reroot. Use this guide.
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Edit: I got it! It boots into this weird Fastbootd mode it looks like recovery. I thought it wasn't taking the install. I was doing something else and it kept installing even though it was in a recovery looking mode. Shoot I erased all my data and probably didn't need to. Thanks for the help!
madmuthertrucker said:
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Click to expand...
Click to collapse
Did you try flashing the OTA with the recovery?
Are you using SDK Platform-tools r29.0.6?
---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------
madmuthertrucker said:
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Edit: I got it! It boots into this weird Fastbootd mode it looks like recovery. I thought it wasn't taking the install. I was doing something else and it kept installing even though it was in a recovery looking mode. Shoot I erased all my data and probably didn't need to. Thanks for the help!
Click to expand...
Click to collapse
You're welcome, keep the guide it explains the fastbootd
Here it is. This threw me off. I just needed to be more patient.
Homeboy76 said:
You're welcome, keep the guide it explains the fastbootd
Click to expand...
Click to collapse
Thanks. I like the guide! I've been reading it. I wish I would have started there. Well now I have it to preview and fall back on.
madmuthertrucker said:
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Edit: I got it! It boots into this weird Fastbootd mode it looks like recovery. I thought it wasn't taking the install. I was doing something else and it kept installing even though it was in a recovery looking mode. Shoot I erased all my data and probably didn't need to. Thanks for the help!
Click to expand...
Click to collapse
A few months back the EXACT same thing happened to me.
bigmatt503 said:
A few months back the EXACT same thing happened to me.
Click to expand...
Click to collapse
Thanks that makes me feel better. It looked like recovery. I thought I messed up. It's nice to know I'm not alone.
guys help please i'm stuck and fastbootstd is not working for me i'm stuck with only fastboot and its using slot b to boot i can't even flash the stock firmware
medo411 said:
guys help please i'm stuck and fastbootstd is not working for me i'm stuck with only fastboot and its using slot b to boot i can't even flash the stock firmware
Click to expand...
Click to collapse
Did you uninstall modules? Restore stock boot.img? Fastboot devices gives you a proper response? Try everything they suggested that I do in previous posts. Change the cable you use. The guide from the previous post has a lot of good information. Tell us more.
bigmatt503 said:
A few months back the EXACT same thing happened to me.
Click to expand...
Click to collapse
Happened to me recently when I tried to flash dtbo.img back to stock
For some reason the fastbootd menu wouldn't let me use other fastboot commands, saying it wasn't unlocked, but going fastboot reboot bootloader then using fastboot commands worked successfully.
Very odd
madmuthertrucker said:
Did you uninstall modules? Restore stock boot.img? Fastboot devices gives you a proper response? Try everything they suggested that I do in previous posts. Change the cable you use. The guide from the previous post has a lot of good information. Tell us more.
Click to expand...
Click to collapse
Thanks a lot i 've tried restarting and changing the cables weird thing it worked previously it was saying remote partition not found bc boot slot is B
medo411 said:
Thanks a lot i 've tried restarting and changing the cables weird thing it worked previously it was saying remote partition not found bc boot slot is B
Click to expand...
Click to collapse
So did you get it?
Yes
I still refer to the guide every time there is an update.
medo411 said:
Yes
Click to expand...
Click to collapse
how'd ya fix the bootloop?
Rootmaster906 said:
how'd ya fix the bootloop?
Click to expand...
Click to collapse
If it is from a bad magisk module:
adb wait-for-device shell magisk --remove-modules
Tulsadiver said:
If it is from a bad magisk module:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
Nope...mine is deeper than that
My galaxy s10 is restarting as soon as it enters the OS, i can briefly see the adb device and enter the adb shell, but then the phone restarts, i got the last_kmsg file, anyone might have an idea of what's causing this?
This happened after i installed LSPosed and the xdowngrader module, strange thing that i manage to get both working, but after another restart this started to happen.
Already tried to remove the lsposed from /data/adb/modules and i removed the /data/adb/lspd
GamingSoldier said:
My galaxy s10 is restarting as soon as it enters the OS, i can briefly see the adb device and enter the adb shell, but then the phone restarts, i got the last_kmsg file, anyone might have an idea of what's causing this?
This happened after i installed LSPosed and the xdowngrader module, strange thing that i manage to get both working, but after another restart this started to happen.
Already tried to remove the lsposed from /data/adb/modules and i removed the /data/adb/lspd
Click to expand...
Click to collapse
It sounds like modules are causing the bootloop.
You can disable Magisk modules during boot by using this ADB command:
adb wait-for-device shell magisk --remove-modules
V0latyle said:
It sounds like modules are causing the bootloop.
You can disable Magisk modules during boot by using this ADB command:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
Already tried, and I realised that the folder /data/adb/modules was empty after the command, but I will try again
V0latyle said:
It sounds like modules are causing the bootloop.
You can disable Magisk modules during boot by using this ADB command:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
I tried again, didn't work, it's not the first time this has happened, strange thing is that the phone had booted fine once after installed a new magisk module, it's just the second boot that it enters this "bootloop", I never tested uninstalling magisk, from what I've seen is easy, just rename to uninstaller.zip and flash using twrp, but I wonder if that could make things worse
GamingSoldier said:
I tried again, didn't work, it's not the first time this has happened, strange thing is that the phone had booted fine once after installed a new magisk module, it's just the second boot that it enters this "bootloop", I never tested uninstalling magisk, from what I've seen is easy, just rename to uninstaller.zip and flash using twrp, but I wonder if that could make things worse
Click to expand...
Click to collapse
Well, I don't think it would make things better, since the modules are already removed.
What modules did you install?
V0latyle said:
Well, I don't think it would make things better, since the modules are already removed.
What modules did you install?
Click to expand...
Click to collapse
I only installed LSPosed and the xdowngrader module, after installed it asked for rebooting, so I did, and the phone booted fine, the module was working, but the second time it wasn't booting anymore, maybe it's the LSPosed?
GamingSoldier said:
I only installed LSPosed and the xdowngrader module, after installed it asked for rebooting, so I did, and the phone booted fine, the module was working, but the second time it wasn't booting anymore, maybe it's the LSPosed?
Click to expand...
Click to collapse
Did you change anything before you rebooted the second time?
The only thing I can really suggest at this point is to reflash with Odin and start over.
V0latyle said:
Did you change anything before you rebooted the second time?
The only thing I can really suggest at this point is to reflash with Odin and start over.
Click to expand...
Click to collapse
I only downgraded 1 app (and the app worked fine), and that's it, i'm really not surprised by this, it has happened before, but it will be an relief if I managed to get it working again without reinstalling the rom, it's really such a pain in the a**... I already "played" with rooting with 2 other phones, and none of them bothered me so much as this s10 hahahahaha
I think I have a twrp backup of the rom somewhere, I will try to locate and restore using that, last time I tried flashing with odin I had to update the phone and patch the magisk all over again :/
GamingSoldier said:
I only downgraded 1 app (and the app worked fine), and that's it, i'm really not surprised by this, it has happened before, but it will be an relief if I managed to get it working again without reinstalling the rom, it's really such a pain in the a**... I already "played" with rooting with 2 other phones, and none of them bothered me so much as this s10 hahahahaha
I think I have a twrp backup of the rom somewhere, I will try to locate and restore using that, last time I tried flashing with odin I had to update the phone and patch the magisk all over again :/
Click to expand...
Click to collapse
Yeah, if you reflash using Odin it will overwrite everything except user data as long as you use the HOME_CSC
If this is a custom ROM you can try wiping /system in TWRP and reinstalling the ROM. Shouldn't wipe data.
V0latyle said:
Yeah, if you reflash using Odin it will overwrite everything except user data as long as you use the HOME_CSC
If this is a custom ROM you can try wiping /system in TWRP and reinstalling the ROM. Shouldn't wipe data.
Click to expand...
Click to collapse
I found the twrp backup, and restored the partitions cache, data, system and boot, now the phone is working again, it isn't the latest backup, but it's better than using odin
GamingSoldier said:
I found the twrp backup, and restored the partitions cache, data, system and boot, now the phone is working again, it isn't the latest backup, but it's better than using odin
Click to expand...
Click to collapse
You probably just needed to restore system alone, but glad you got it working.