HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
stubbadub said:
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
Click to expand...
Click to collapse
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
bjorn96 said:
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
Click to expand...
Click to collapse
I have just run the Easyroot Tool again and this seems to have solved it. :good:
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
My bootloader came unlocked on the phone. I bought the phone when it was released. I rooted and when 4.4.4 firmware was released it initially failed to update OTA. I had to remove the dual recovery. The OTA then worked fine and i still had root. However i could not mount the /system folder as R/W/. I just ran easyroot again and this solved it.
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
NC not working happened to me too. But only in niaboc79's version (and by this I mean the Russian OTA). I also tried the OTA and all was good. But after that I lost my root and tried to restore it (I ran the restore-mount script). This script messed things up. Instead of looking into that, I tried different approaches (niaboc79's / .314+root+script) except check if it was because of the the script .
If you have root now, install the dualrecovery and dirty flash for example shockss pre-rooted .267 and run the script. Stock .267, everything working but pre-rooted. Ow and 4G icon = LTE icon.
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
pec0ra said:
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
Click to expand...
Click to collapse
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
stonegroover said:
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
Click to expand...
Click to collapse
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
pec0ra said:
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
Click to expand...
Click to collapse
I still have 'some root', my Adaway still works but it won't load new/updated hosts, BusyBoxPro won't install, etc. I tried what you did, just ran the two lines of code but it said I didn't have permission when I tried to run the second line. Did you get that error? If you did, how did you get past that?
Related
I finally gave in to the update nagging screen and tried to update.
My phone was rooted with preinstall method, nothing else.
I was on 2.3.4 (4.5.91).
I installed RootKeeper and unrooted before the update (kept root backup).
The phone downloaded the update, restarted, and I saw the Android Icon and an "unpacking" progress bar. The bar stopped about half way and the icon turned into an exclamation point. I thought I was toast....
The phone rebooted fine, everything still there. I got a message box "Update failed" once I got on my home screen. The phone is still 2.3.4. The update nagging is gone.
I have pretty rare reboots, maybe 2 a month. I am quite happy with it.
Anyone had the same issue? Should I even bother going to 2.3.6?
The only thing I am really missing on the Atrix is HDMI mirroring option with 720p or 1080p up-conversion.
How can I get the cause for the "fail"? Should I use the Moto USB method?
I wouldnt mind going to CM9 but I want the Finger Sensor, Camera etc all to work. I dont want to loose any current functionality going to CM9 and its not there yet, correct?
Thanks!
I would just stay where you are at. Unless you really want the mirroring. You seem to not mind stock so I would wait for Moto to release ICS for the Atrix. They put it on the list.
if you only rooted, did nothing else that requires root (freeze apps, put files in /system, etc) and did not unlock the bootloader, just unroot and then apply the 2.3.6. update.
Code:
1. Open Android Terminal Emulator (ADB)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
spacev said:
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
Click to expand...
Click to collapse
There have been posts in various 2.3.6 threads where rootkeeper did not work if you used the fastboot preinstall method.
It should work if you manually unroot as long as everything else is stock.
for seeing why the update failed, hold the Volume up and power button when the error appears and you should see some sort of error msg...never tried it myself though.
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
otter9309 said:
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
Click to expand...
Click to collapse
Did you undo everything that requires root access prior to applying the OTA? I usually do the following prior to an OTA (and redo once the OTA is applied):
uninstall Swype beta, restore stock Swype files (the so and apk files)
move ringtones out of /system/media
Help Needed
Hi All,
I am a newbie here and I am not sure if my question makes any sense. Couple weeks back, I bought an Atrix 4g (US version), an unlocked version (the seller told me that this phone is unlocked using AT&T code) and I am using it with Vodafone (India) sim. It works perfectly and so far I didnt face any problems with this phone. But last week, I got an alert in phone saying that software update (2.3.4.5.141) is available for AT&T users and enable wifi to download. However, I didnt download and install the update as I was not sure why is it saying the update is available only for AT&T users. Also wherever I read about this software udpate, the name 'AT&T users' come along with that.
So my doubt here is, what will happen if I, who is not an AT&T user, download and install the software update in my phone ? will it cause any issues in the phone (like getting locked again or bricking the phone)
I have not done any modification like rooting or installing custom ROM and things like that and I am using the phone as I recieved it.
Thanks in advance for your help.
-Qaddaffi
So I used the guide on Condi's AiO tool to get ICS rooted and everything said it was going fine and root was successful and everything but then I installed it and it was a custom file and everything, it even said "Installing root" and then "Successful" but I am not rooted so what is up with that?
The system update button even still shows up...
ChristianTW said:
So I used the guide on Condi's AiO tool to get ICS rooted and everything said it was going fine and root was successful and everything but then I installed it and it was a custom file and everything, it even said "Installing root" and then "Successful" but I am not rooted so what is up with that?
The system update button even still shows up...
Click to expand...
Click to collapse
Maby you've forgotten to put in your sd card xD. i had the same stupidity re do the steps again, maby that works you could give it a try and if it wont work and you dont want root access anymore just apply the update and wait for the ics update and also wait if devs can root ics, remember you could have a chance that you get a kernel 9 or above with "3.2.1 release 2" and will not be able to gain root anymore.
Mahaco said:
Maby you've forgotten to put in your sd card xD. i had the same stupidity re do the steps again, maby that works you could give it a try and if it wont work and you dont want root access anymore just apply the update and wait for the ics update and also wait if devs can root ics, remember you could have a chance that you get a kernel 9 or above with "3.2.1 release 2" and will not be able to gain root anymore.
Click to expand...
Click to collapse
No, it was definitely on the SD card. It even went through the update and everything. I tried redoing the steps but I no longer have root so they failed. I definitely do want root, but either way I don't have it.
On my 3.2.1 I have kernel revision #1...
ChristianTW said:
No, it was definitely on the SD card. It even went through the update and everything. I tried redoing the steps but I no longer have root so they failed. I definitely do want root, but either way I don't have it.
On my 3.2.1 I have kernel revision #1...
Click to expand...
Click to collapse
I had the same, but there is an easy way to fix it.
It's because you had SuperSU... Didn't you?
sebarkh said:
I had the same, but there is an easy way to fix it.
It's because you had SuperSU... Didn't you?
Click to expand...
Click to collapse
Nope, I did not... I used SuperUser...
So if i get it right your on 3.2.1.r2 now without root?
If you havn't fixed this already there might be a solution for you try this:
1. Connect your tab.
2. Enable usb debugging.
3. Open device manager
4. Disable SONY TABLET S
5. Start Condi's 2.7 AiO Tool
6. Choose option 1 for root.
7. Press enter so your device will reboot.
8. look in device manager list and wait until SONY TABLET S re-appears
9. If it appears then you must enable it again and wait for the AiO tool to finish.
This might work just give it a try!
YF,
Mahaco.
Mahaco said:
So if i get it right your on 3.2.1.r2 now without root?
If you havn't fixed this already there might be a solution for you try this:
1. Connect your tab.
2. Enable usb debugging.
3. Open device manager
4. Disable SONY TABLET S
5. Start Condi's 2.7 AiO Tool
6. Choose option 1 for root.
7. Press enter so your device will reboot.
8. look in device manager list and wait until SONY TABLET S re-appears
9. If it appears then you must enable it again and wait for the AiO tool to finish.
This might work just give it a try!
YF,
Mahaco.
Click to expand...
Click to collapse
Hello,
Thank you for your reply, unfortunately I am actually on ICS without root. It is quite annoying because all of the root files are there but it still says I am not rooted. I can even use the hacked recovery file, unfortunately signature check is not disabled so I can't reinstall the rooted ICS file...
~Christian W.
ChristianTW said:
Hello,
Thank you for your reply, unfortunately I am actually on ICS without root. It is quite annoying because all of the root files are there but it still says I am not rooted. I can even use the hacked recovery file, unfortunately signature check is not disabled so I can't reinstall the rooted ICS file...
~Christian W.
Click to expand...
Click to collapse
Auch, Thats a bummer then its not possible to obtain root acces which you already knew, but that means that the rooting process whas half finished, that it has installed the Super User app but not changed any permissions or values,
too bad you cant see where it went wrong, but i think the devs will find out how to deal with the "Unrootable kernels"
Too bad i didn't helped you at all,
YF
Mahaco.
ChristianTW said:
Hello,
Thank you for your reply, unfortunately I am actually on ICS without root. It is quite annoying because all of the root files are there but it still says I am not rooted. I can even use the hacked recovery file, unfortunately signature check is not disabled so I can't reinstall the rooted ICS file...
~Christian W.
Click to expand...
Click to collapse
There are two scenarios - one - please check /system/bin/ directory - if there is 'tempsu', and /system/xbin/ if there is 'busybox' - if yes, then just let me know.
Second scenario - you've created custom update, then accidentally flashed 'decrypted_update.zip' - without root etc.
br
condi
condi said:
There are two scenarios - one - please check /system/bin/ directory - if there is 'tempsu', and /system/xbin/ if there is 'busybox' - if yes, then just let me know.
Second scenario - you've created custom update, then accidentally flashed 'decrypted_update.zip' - without root etc.
br
condi
Click to expand...
Click to collapse
Unfortunately it is not there, but when I was installing the update it said "Installing Root" and it showed the condi tool logo and everything...
https://doc-0k-1o-docs.googleuserco...009/*/0BzrP5DWIlpplYjFOY1MwOXFNLWc?e=download
here is the ota zip
if we flash this can we flash 4.5.141 with rsd?
any answers?
I wouldn't count on it. The ZIP seems to contain what looks like the bootloader, or at least a piece of it (ap20bl.img). Who knows what might happen after that. Motorola said a downgrade is not possible.
I would just wait for the .145 fruitcake. Then switching back and forth should be safe and painless.
ok thanks for answer
Installed 4.5.145 for fun
blttalas said:
ok thanks for answer
Click to expand...
Click to collapse
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
sn0wba11 said:
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
Click to expand...
Click to collapse
Did you do this via the standard update or by flashing that zip yourself?
vikingarcher said:
Did you do this via the standard update or by flashing that zip yourself?
Click to expand...
Click to collapse
Standard
Su ota survival
Has anyone tried to install the update after activating the superuser ota survival option
Root after sys 4.5.145 update?
fdaconta said:
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
Click to expand...
Click to collapse
This response is from the developer thread. I would respond there but the policy for members with less than 10 posts is silly.
None of the existing preinstall methods (e.g. atrix-4g-moto-fastboot or superoneclick 2.3.3) work with 4.5.145.
sn0wba11 said:
Standard
Click to expand...
Click to collapse
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
vikingarcher said:
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
Click to expand...
Click to collapse
Came across a link at Android Central that used Voodoo OTA RootKeeper to restore --> Forgot I installed this awhile back; reinstalling app restored my superuser access
Re-rooted 4.5.145 after OTA
I successfully re-rooted mine last night using the pre-install method.
Read my topic here:
http://forum.xda-developers.com/showthread.php?t=2153422
From 141, to 145, back to 141.... and finally ended up with a working (and rooted) 145.
Hello
This my very first post on XDA so be gentle.
Question is I created a pre rooted SGP611_23.1.A.0.690 with PRFCreator flashed it and everything went fine but I am unable to get any write access to root even though its stating its rooted I cant seem to install apps like busybox etc.
My first through was RicDefeat so I tried it all again and this time tried flashing RicDefeat but when I try to flash I get errors, had no problem flashing under Kitkat.
Is there anything i am doing wrong?
My bootloaders locked atm, I can unlock if necessary I have backed up my DRM keys.
Any help would be greatly appreciated.
Im on the same boat as you. So any help would be apreciated.
Use my RICDefeat from here and run it from terminal. Works only if you are rooted. Afterwards you should have r/w access.
lowtraxx said:
Use my RICDefeat from here and run it from terminal. Works only if you are rooted. Afterwards you should have r/w access.
Click to expand...
Click to collapse
It Worked I love you xxxxxx no homo!
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin