yashsingh1/xdaforums huggingface dataset:
[SuperSU] zeroprobe:
Does Nougat still have some SU issues?

I have an app that runs an SU instance to run some commands.

Using SR5 and Galaxy Tab S / S7.

My code has the following line.

p = Runtime.getRuntime().exec(new String[]{"su"});

After stepping over it I get the following error in Nougat only and my commands don't get run. Anyone have any idea on this?

12-11 20:54:38.277 3437-3840/system_process E/ActivityManager: Sending non-protected broadcast eu.chainfire.supersu.NativeAccess from system uid 0 pkg null
java.lang.Throwable
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:17726)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:18287)
at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:499)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2755)
at android.os.Binder.execTransact(Binder.java:565)
[SuperSU] DerpleNerple2000:
I had to flash the factory image for my Pixel XL after TWRP RC1 bootlooped my device (my fault), but I cannot get root to work anymore. I've flashed boot-to-root, but updating to SR5 caused a reboot to recovery. I've tried it without boot-to-root, but SuperSU just doesn't show up and installing from the play store says the binary isn't installed. Is there something I'm doing wrong? Is Android 7.1.1 (December Security Patch) on Pixel XL not supported yet?

EDIT: It appears that TWRP RC1 was having an issue with root not sticking, and Dees_Troy has acknowledged this problem. I'll have to revert back to Alpha2 to install root.
[SuperSU] DPyro:
This breaks sensors on Kate running CM14.1. Auto rotate won't work.
[SuperSU] jdegreef:
Well, here I had to reflash it. After a dirty flash of RR N build 3 root had disapeared and the app was saying that it needed update.

Envoyé de mon XT1039 en utilisant Tapatalk
[SuperSU] GuzuGuzu:
If it is of any help, the 2,78 SR5 version corrupts the IMEI on Android 7.0 on HTC M9. It also says that root is installed, but in reality it does not work. Tried to uninstall several system apps and received a "failed" error.

ROM 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4 .14.617.6.zip found here.
[SuperSU] storm119:
I guess supersu doesn't survive after dirty flashing....not sure tho.?.

Ps: im on Nitro roms right now with supersu built in...so much easier and nothing to worry [emoji1]

.....transmitting via TapaTalk
[SuperSU] bdwilk:
[MENTION=5504709]jdegreef[/MENTION]

Yeah SuperSU doesn't survive a dirty flash. The app is there but it has no effect till either reflashed or the binaries updated which never works. It's always part of my updating ritual. At least it doesn't lose its data. No need to grant all your root apps over again.
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], on the CM14.1 for the d2vzw I also had the same issue with SuperSU 2.78 SR5, SR4, and the SuperSU 2.78 Stable.

Is there something that I missed?

They all work fine on the CM13 for the d2vzw.

In addition, when i flash any of the 3 SuperSU (above) on the CM14.1 within TWRP v3.0.2-0, i select the CM ROM, GApps then SuperSU and that's it. I also don't see any errors when the SuperSU is being flashed either.

Could it be that i should begin with flashing the CM ROM and GApps first. Then, after rebooting and the initial setup, reboot again into the recovery and proceed with installing SuperSU?

Chainfire, the installation log files are also available upon request.

Thanks a bunch!

Sent from the Bridge of the U.S.S. Enterprise using XDA Labs
[SuperSU] Marek89:
After flast this SU, on application Busybox from meefik is this error.... remounting /system to rw . . . fail. What is a problem ? I have E6533, fw 32.2.a.5.11 and TWRP. Please, help.
[SuperSU] psychoela:
anyone have backup script supersu .sh? sory my bad eng:eek:
[SuperSU] John Dave:
Hello chain fire

i WANT TO ASK SOME LINK REGARDING ON HOW TO OR PROCEDURE AFTER ROOTING OF AN ANDROID MOBILE?
[SuperSU] jamiejames:
Don't have to yell. I think read the flashing instructions in the OP.
[SuperSU] mrcigi:
I have a OP3 and I need to type

echo SYSTEMLESS=true>>/data/.supersu

Into terminal every time I flash it, or it automatically flashes in system mode. I thought the default mode was now systemless. Not a big issue just curious as to why I need to type it in every time.
[SuperSU] bombadier:
What ROM are you using? because it sounds like whatever you have is already rooted
[SuperSU] mrcigi:
Its resurrectionremix which does come already rooted, so your probably right. I thought SuperSU would overwrite it to systemless. Thanks :)
[SuperSU] ruchern:
You might want to delete

/system/xbin/su and /system/bin/su in recovery before flashing.
[SuperSU] Terenu:
How can I do that? I'm not able to delete/rename these files.
[SuperSU] bombadier:
Use the file manager in recovery, remember and mount system first
[SuperSU] ruchern:
Boot to recovery then use the file manager inside there (TWRP) or any terminal.
[SuperSU] Terenu:
I tried to do it and it sais that is "busy", so I can't do it.

---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------

Could you writte to me the correct command to do that in TWRP? I can't find it on internet
[SuperSU] bombadier:
Well thats something you need to investigate as to why you are getting "busy"

You could also use Osm0sis's UNSU script zip which will remove all traces of "system" root, quicker as typing a terminal command or using the file manager
[SuperSU] Terenu:
Thank you . With this file works perfectly. :good:
[SuperSU] BlackMage879:
On my Asus [for details see my signature] (5.0 Stock ROM) crashes SuperSU 2.78 SR5 regularly (the device then restarts)

edit: sry, i forgot to update 'SuperSU Pro'. Now it runs smoothly.
[SuperSU] ruchern:
SuperSU just got updated and prompted me to update the binaries. Should I be doing that when I have SR?
[SuperSU] Einwod:
Yes.
[SuperSU] bdwilk:
It worked for me. One of the few times that updating binaries actually worked. SR5 to 2.79 now.
[SuperSU] HorstiG:
Thanks, works great

Galaxy S7 Edge M 6.01, LG G4 M 6.0
[SuperSU] counterfeit187:
To clear up some confusion for me... Does SR stand for series release or systemless root? Current stable build is 2.79 and is newer and I should update? Do I need to do anything special to switch from these betas to stable?
[SuperSU] Ja_som:
SR is not systemless root, I'm not sure what exactly it is :) , but "v2.78 SR1 (aka beta)" was the first version :)

2.79 is newer, you can update if you want, and you don't need to do nothing special, flash zip or instal v2.79 from the Play Store and update binaries via app
[SuperSU] Portgas D. Ace:
SR stands for Service Release, as explained in the official SuperSu stable thread here (see post #2):

http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
[SuperSU] Wolfcity:
With the latest v2.79 from PlayStore I went from system to systemless root the first time. Titan on turbo ROM.

Doesn't matter where this was sent from
[SuperSU] dahawthorne:
Service Release. I upgraded directly from 2.78 SR5 to 2.79. The installer is a pretty smart piece of coding.
[SuperSU] Ofthecats:
Anyone do the in app binary update on the pixel XL?
[SuperSU] dlsygaco:
how can i flash SR5 using fastboot? Just out of curiousity

EDIT: found a way myself thanks.
[SuperSU] JohnCorleone:
Did anyone try flashing the SuperSU 2.78 forceencrypt on the HTC Nougat once Captain Throwback conquered TWRP or is my SuperSU obsolete?!
[SuperSU] cwalker0906:
Yes, went fine
[SuperSU] ArKay74:
SIM card no longer works on my OnePlus 3 with the new Nougat beta since I have installed SuperSU. Upgrade to 2.79 didn't change that. SIM is recognized in the prefs, but system doesn't ask for the PIN hence it doesn't get unlocked
[SuperSU] GuzuGuzu:
Check IMEI

Check your IMEI. I am sure it is corrupted or shows blank in system info.

If so, restore it either using fastboot or other suitable to you method. After re-flash the ROM or better, restore it from a back-up.

Unfortunately on my M9 just restoring the IMEI did not help. ADB was showing it, but system would just not see it. I had to restore the ROM from a previously made back-up.

Cheers.
[SuperSU] ArKay74:
I had flashed an older SuperSU (2.78SR1) and then upgraded to 2.79 through Play Store. Guess the damage had already been done at that point because the phone was acting up in various places. The camera took 5 secs to show a picture, auto rotate didn't work and the SIM card wasn't activated.

So I just reflashed the system without su and everything worked again. Then I flashed 2.79 through TWRP directly and now everything is working fine. Weird, didn't expect all of the other problems to be SuperSU-related.
[SuperSU] GuzuGuzu:
You are perfectly right. All is related to SuperSu 2.78 SR5.

Would you be so kind and share the zip with 2.79 version? Can't seem to find it.
[SuperSU] osm0sis:
Stable thread:

http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Nothing's really changed between 2.78-SR5 and 2.79 though.
[SuperSU] ArKay74:
You can download it from the official page. 2.78SR1 was causing problems, I didn't try SR5.

https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip
[SuperSU] osm0sis:
Oh, slightly newer build date. I'll update to this. Nice that [MENTION=631273]Chainfire[/MENTION] is still doing and posting his own builds to cater to the semi-tinfoil-hatted, despite there being no code changes.
[SuperSU] Ibuprophen:
When Chainfire released the Stable 2.79, doesn't that make this thread, as well as earlier versions, a mute point to continue discussing?

OR is this just crazy thinking?

Sent from my D2VZW on the Bridge of the U.S.S. Enterprise.
[SuperSU] osm0sis:
... Until the next service release. ;)
[SuperSU] counterfeit187:
Moot
[SuperSU] egingell:
When a new SR is released, this thread well be renamed, the links changed, and discussion will continue. It has always been the way of things.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Chainfire:
Can I get a show of hands here from those on the latest S7 Nougat Beta (4 I think?) that are having issues with SuperSU willing to do some testing ?

If one of you can post the original file_contexts.bin file that would also be great.
[SuperSU] _alexndr:
Mine is in the attachment (original + patched) - from Nougat Beta 1
[SuperSU] Chainfire:
You were on beta1 ? I thought the reported issues only happened on beta4 ?
[SuperSU] _alexndr:
http://xdaforums.com/showpost.php?p=69870416&postcount=8225

http://xdaforums.com/showpost.php?p=69929464&postcount=8307

See above (ZPK4 in both my posts), but I noticed that reports are not related to beta release, same issues were reported also in case of beta 2/3/4 - seems like it does not matter
[SuperSU] Chainfire:
Sent PM.
[SuperSU] je2854:
Don't, it won't boot

---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------

Going from SR4 to 5 with inapp binary update prevented me from buying on sailfish.
[SuperSU] dratsablive:
I had same issue on 6P. Did in app update and soft bootloop. Reflashing SU from TWRP fixed it.
[SuperSU] gorilla p:
I don't know how similar they are but had a boot loop when flashing 2.79 on Mako. Went with 2.78 B4 and no probs.
[SuperSU] Ofthecats:
Worked for me
[SuperSU] WyldWolf:
Going inapp to SR5 put my Oneplus One into a bootloop. Luckily I had TWRP and the old SU zip and just backflashed the old version over the top and was able to boot back up, but of course now I have to live with the continual upgrade prompts. Any idea when SR6 is rolling in and I have admittedly not had the time to go back to read the last hundred pages to see, are many others getting bootloops from the in-app upgrade to SR5 too?
[SuperSU] bdwilk:
Funny my bacon worked just fine. Same as you running SR5 and got Playstore update to 2.79 and worked ever since. No issues. What ROM?
[SuperSU] WyldWolf:
Sorry should have stated......CM13.1-ZNH2KAS1KN
[SuperSU] bdwilk:
Oh. Well I don't know why that would be an issue then. I was running RR N at the time. Anyways just flash the 2.79.zip and be done with it.
[SuperSU] WyldWolf:
I'm confused then, today it prompted that the binary needed updating and I said yes and it bootlooped. I assumed apparently wrongfully that this SR5 was what it upgraded to, but are you saying there is a 2.79? Christ it would be nice when the GUI prompts that the binary needs updating to say what version LOL. I'll pull down the flashable 2.79 and try it I guess I can always backflash again if needed but would sure like to know what OTA version looped me today.

EDIT: Just took your advice downloaded and flashed the flashable 2.79 wiped Dalvik and booted right up fine and no more upgrade prompt from the GUI although I have not reinstalled it. When flashing a diff version is it best to reinstall the Playstore version of the Supersu gui, or just leave it alone?
[SuperSU] bdwilk:
Just leave it alone. Your settings will remain. If ever you update your ROM (any ROM) in the future. The app will remain in your app drawer but it will be ineffective. You'll have to flash the zip again but it'll just continue with your previous settings and permissions assuming you don't uninstall the app. No need to wipe anything after flashing. Just flash and boot.
[SuperSU] fenchai:
I tried installing SuperSu 2.78 SR5 on my Pixel XL and it flashes but no SuperSu app or root. Help?
[SuperSU] -Deco-:
Try downloading the app through the Playstore.
[SuperSU] fenchai:
It says "There is no SU binary installes, and SuperSU cannot Install it"
[SuperSU] drewski_1:
try reflashing the zip. I had the same error and that fixed it (with v2.79)
[SuperSU] shaggyskunk:
Yeah I don't think that simply installing SuperSU from the store as an app is going to do anything about Root - Either Flash the zip or Flash a Rom that has SuperSU or Root built-in.

Sent From My SM-N910W8 ??
[SuperSU] fenchai:
flashed 2.79, nothing, I give up, Im just going to flash stock again and deal with it. Or maybe I will flash a rom with root. T.T
[SuperSU] ridobe:
Just out of curiosity, what is your device?

edit: nevermind. Saw in an earlier post that you are on Marlin. Just prior to flashing supersu, go into the file explorer in twrp and delete the fstab.marlin file in the main ditectory. Then flash SuperSU.

http://xdaforums.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312/post69626086
[SuperSU] fenchai:
yeap, thanks, I did and it worked. All good now :) Im only missing xposed at the moment
[SuperSU] -Happy Feet-:
Hello,

Ich flashed an Stock Rom and an custom Kernel (78kernel) After that it reboots and it works. But after Switch root many System Apps force close and the Phone reboots.

I have made an logfile over ADB. Maybe someone have an idea what is wrong.

https://cloud.land-laeufer.de/index.php/s/DcRrkgRMSkazZiB
[SuperSU] Chainfire:
Ah, to beat a dead conversation:

#!/su/bin/sush
(
sleep 300
echo done
)&

Just do whatever you would normally do, inside the ()'s.
[SuperSU] osm0sis:
I found ()& didn't work (not sure why still), but I believe [MENTION=4878287]_that[/MENTION] suggested {}& and it works quite well. :)

https://github.com/osm0sis/gappsintegrator/commit/d1ea6d5f03c62f589671e9c95ca411b9afc7a3f3
[SuperSU] IMTLD:
Supersu doesn't work on mi5 android 7 IF the cache and/or data are formatted as f2fs. tried multiple roms only cm built in root works
[SuperSU] Ibuprophen:
I believe that [MENTION=4419114]rovo89[/MENTION] really could use more specific information regarding both the device in question and the issue at hand (to include, but not limited to logcat files).

He really can't go on individuals stating similar texts that they are having an issue with SuperSU on whatever device.

I'm really not doing a rant, lecturing or insulting anyone. I'm just expressing what I've seen Rovo89 state time and time again.

Thanks and Happy Holidays Everyone!

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] Pkt_Lnt:
Why does the Xposed dev (rovo89) need to be sent logs of SuperSU? :confused: You have you <mentions> tags confused? :confused:
[SuperSU] Ibuprophen:
That was just 1 example i had provided.

I truly apologize for any confusions or misunderstandings that may have caused.

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] Chainfire:
Interesting, it works well for me; Then again, accolades also work for me, so I'll put those in the docs.

Possible it has to do with the specific shell. () may not be a subprocess in the different flavors of shells present across all devices?
[SuperSU] :
Or try phh su
[SuperSU] osm0sis:
Found it:

http://xdaforums.com/showpost.php?p=68755324&postcount=7236 and http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post68736854#post68736854

Looks like I misremembered slightly; only tried () at the time, not ()&, since () alone works in most *nix shells, but not (m)ksh.

So I guess both ()& and {}& work. Any reason to favor one over the other?
[SuperSU] Chainfire:
I just looked it up. () should be used, not {}. () explicitly creates a subprocess, while {} does not. That {}& works at all is surprising reading the docs, I'd expect it not to.
[SuperSU] osm0sis:
My guess is since you're adding & to force the subshell, it doesn't really matter how you group the commands.
[SuperSU] _that:
http://pubs.opengroup.org/onlinepubs/007904875/utilities/xcu_chap02.html#tag_02_09 says:

"If a command is terminated by the control operator ampersand ( '&' ), the shell shall execute the command asynchronously in a subshell."

And the curly braces form a compound command, so the whole list is executed in a subshell.

I didn't find anything about which variant should be preferred.
[SuperSU] Chainfire:
SuperSU v2.79-SR1 released: https://plus.google.com/+Chainfire/posts/WrCvex7KAZR
[SuperSU] HorstiG:
[MENTION=631273]Chainfire[/MENTION] Thanks for your Update, works perfectly, Galaxy S7 Edge hero2lte Marshmallow 6.01 and LG G4/G5 Stock M

View attachment 3976809
[SuperSU] ridobe:
Booted up nicely. No fstab removal necessary.
[SuperSU] andreoide:
Thank you again Chainfire!

Updated with zip trough TWRP

Working Samsung kccat6 sm-g901f stockrom and xposed.

[emoji106] peace.
[SuperSU] liver20:
Works with f2fs partition in nougat?

2.79 lose root in my OnePlus 3t with 7.1.1

Enviado desde mi OnePlus3T mediante Tapatalk
[SuperSU] skyhirules:
It causes boot loop on my Xperia Z1 Compact, on stock Android 5.1.1. Didn't have that issue with 2.79.
[SuperSU] Ch3vr0n:
Thanks for fixing the lag issue on my 6P :) May it never return :p
[SuperSU] Stogie87:
This build stuck at boot on my Oneplus 3 with latest official Resurrection Remix Marshnallow build 5.7.4. With previous builds everything was fine...
[SuperSU] shaggyskunk:
How long did you wait? - Took about 3 - 4 minutes to finish boot on my Note 4 running CM Based 7.1.1 - No issues.

Sent From My SM-N910W8 ??
[SuperSU] vietnam100:
Play store is V2.79, here is V2.79 SR1?

Gesendet von meinem SM-G935F mit Tapatalk
[SuperSU] Ch3vr0n:
SR versions are the former beta versions. Different name, 'same' thing.
[SuperSU] KaMyKaSii:
I'm running CM 12.1. I upgraded SuperSU 2.79 to 2.79 SR1 and after starting, the SuperSU app was not in my drawer, but my apps got super user permissions, but without any notification or anything. I activated Liveboot and restarted. Same thing. /system/app/SuperSU/SuperSU.apk exists, so I clicked on it and installed it as update, now in /data/app/SuperSU/. Since then the GUI is working, but I believe that installing the app again was not necessary, right? Below is the link to Liveboot and twrp logs

https://drive.google.com/file/d/0B1uvONk-jlRiSG9CTnZvdnVpZE0/view?usp=drivesdk

https://drive.google.com/file/d/0B1uvONk-jlRiSU5LaGhpUVIyak0/view?usp=drivesdk
[SuperSU] counterfeit187:
After updating binary I've had to uninstall and reinstall the UI app too. Dunno why, but a simple uninstall reinstall fixes it.
[SuperSU] immi803:
Sr1 2.79 error

[MENTION=631273]Chainfire[/MENTION]

Couldn't flag sr1 as ended with error se policy, aborted

Please help

My device is op3t, rom mm

I am back to 2.79
[SuperSU] Ch3vr0n:
He can't help you unless you provide some kind of logs. Chainfire doesn't have every device or a crystal orb to see what the problem is. :)
[SuperSU] Chainfire:
Yes, it sometimes happens that the APK has to be manually installed, or un/reinstalled. It's not very common but it happens.
[SuperSU] andreoide:
Read post 1 from this thread.

[emoji111]
[SuperSU] eris23:
I'm running TugaPower N 11.0 on a OnePlus One. suhide 0.55, Root Switch 1.3.3.2, SafetyNet Helper.

UPDATE-SuperSU-v2.79-20161211114519.zip works fine.

When using SR1-SuperSU-v2.79-SR1-20161221223537.zip, if root is disabled in Root Switch, checking status in SafetyNet Helper freezes system.
[SuperSU] buttie:
HTC One m9 with Nougat stays on bootloop with v2.79 SR1 and suhide 0.55,

It's just a PSA, I know that suhide is an old unsupported song (it still works fine on many devices with Root Switch though).
[SuperSU] kishd:
Don't quite understand. If you use rootswitch why would you need suhide.
[SuperSU] buttie:
Sadly, with Root Switch alone device doesn't pass SefetyNet check, it does though with Root Switch + suhide combo.
[SuperSU] dratsablive:
[MENTION=631273]Chainfire[/MENTION] Just wanted to thank you for the SR1 update. I just noticed the speed improvement (other versions were slow to grant SU on 7.1.1 on my Nexus 6P) now it's instant!
[SuperSU] djsolidsnake86:
No root with latest beta on redmi note 3 pro qualcomm and miui 6.12.22

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[SuperSU] Ottobrerosso1977:
thank you Chainfire.

No issue with Galaxy Note 3, ROM CM 14.1 based 7.1.1, kernel PurifyK 1.3.3
[SuperSU] osm0sis:
The trick on my N5 was to make sure I had no bind mounts to /su. Once I let AdAway write directly to system and directly flashed the Adreno beta drivers (my only two bind mounted mods) SafetyNet passed with Root Switch alone. Doesn't even require stop all su daemons, but you do need to reflash SuperSU with the BINDSYSTEMXBIN=true keyword in /data/.supersu and the custom_ramdisk_patch.sh from the Chinese Asus forums Root Switch thread so that /su isn't part of the $PATH.

Also, CM's default kernel trips SafetyNet so a custom kernel is necessary. ;)

I'm still hopeful [MENTION=631273]Chainfire[/MENTION] will update suhide to get around the November security update zygote socket whitelist (the reason for the bootloop), because my tap banking app doesn't use SafetyNet but does detect root on CM14.1 even when root is disabled and SafetyNet passes. Maybe he could just remove SafetyNet support from suhide so there won't be any more major arms race and that way it can just be useful to get around the other, lesser root checks.
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], i wasn't sure if i should ask this 2 Part question using this thread or another so please excuse me if this was asked under the wrong one...

Part 1

----------

I was wondering if you could confirm the order in which to flash the SuperSU after performing a complete system wipe (starting from scratch, so to speak):

1) CM ROM

2) Open GApps

3) XPosed Framework (Only for flashing v6.x ROM & below)

4) SuperSU

I was always under the impression that the SuperSU was to be flashed last.

Am I wrong?

Or does it not matter as long as it's flashed after the ROM?

Part 2

----------

Am i wrong in believing that both the SuperSU and XPosed Framework has nothing to do with each other (and to clarify, I'm only referring to the XPosed Framework and not the Installer nor the Modules)?

I always felt that they didn't affect each other at all but, I just wanted to get a confirmation from the Dev.

Thank you for your time!

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] HammerHead0101:
Will this work on Nexus 5 running 7.1.1 Rom?