yashsingh1/xdaforums huggingface dataset:
[SuperSU] jcmm11:
I can state that on the Nexus 5X the new bootloader doesn't cause any problems. From what I'm reading so far it seems to be only the Pixels that are having an issue, so the comment about the extra patch for htc bootloader security issue being the culprit is very likely correct.
[SuperSU] mtw4991:
No problem on the pixels either, unless you change recovery, kernel or install SuperSu with the May update. Chainfire is working on it, as is Franco... Shouldn't be an issue shortly
[SuperSU] Chainfire:
For those interesting in the boot image signing for the Pixel (XL): https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[SuperSU] osm0sis:
Ah, I ran into this just recently as well!

The Xiaomi Mi Max also uses this signing scheme and a user reported and submitted a patch to me that having mkbootimg treat it as second (since the signature was at the second_offset) worked on their bootloader where without a signature it would otherwise fail to boot.

https://github.com/osm0sis/mkbootimg/commit/f8946a263eb6f53369359dafcc86dd780949a413

And some fixes to the idea:

https://github.com/osm0sis/mkbootimg/commits/master

No idea how the new Pixel bootloader enforcing the signature check differs from Xiaomi's - sounds like it's even less lenient from what you've tested.
[SuperSU] namfat:
Sorry if brother you! Do you have SuperSU update for S8/S8 plus.

Many thanks!
[SuperSU] Ch3vr0n:
Did you try the current one?

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] Angel_Perez:
How to delete or reset the PIN code in SuperSU by forgetting, help!!

Hi, I have a phone that after Routing it and fixing all the APK, I activate the PIN Security Code in to the SuperSU, then I forgot what digits I had entered.

Is there any way to reset it without Flashing back?

Note: Re-copying or Re-installing the SuperSU (in this case is a Huawei) is still locked. :(

I have been told that in the Chainfire Forum on SuperSU he mentions a method using the ADB, entering the phone in secondary mode (why we can not use the ROOT logically) and delete a file ... ??? Whats the file, I´dont not. :confused:

According to some, within the SuperSU files, Is the solution to remove the PIN and to re-establish the SuperSU.

How and what is the file please? :good:
[SuperSU] jcmm11:
The file is /su/etc/pin

Since it's in the su directory you need to mount su.img to get at it.

Easiest way, probably, is to go in with TWRP and flash SUmount from osmosis. That will mount /su and make it accessible. You can then go and delete the file.
[SuperSU] droidzer1:
Chainfire, Apologies if this is slightly OT but some of us have noticed a new CF auto root for the Verizon Galaxy Note 5 SM-N920V on your web site just a couple days ago. Being this phone has a very locked down bootloader SuperSU doesn't seem to get installed and the phone hasn't yet been rootable with this particular CF auto root by the couple people who have tried it. They had the exact version of Nougat specified, the exact model phone and so on and were not newbies to these types of operations. Is there some special way to use this CF auto root we need to know?
[SuperSU] shaggyskunk:
I'm going to guess that if there's a CF Auto Root for Verizon - It would apply to the Developer Edition.... You may find this Thread helpful?

https://xdaforums.com/showthread.php?p=66366819
[SuperSU] droidzer1:
Thanks although this is for a Note 5 Verizon model. After Googling around and checking directly with Samsung I can't seem to find any evidence they had a Developer Edition for the Galaxy Note 5. The link you mentioned seems about how to convert a Note 4 to a Developers Edition and under requirements states you need to have root either temp or permanent. The only root (of sorts) for the Note 5 is a command line root using the ENG kernal file and it seems that's only good in ADB and you can't even change any folders to RW. However it has been something I have considered that may possibly work by flashing the ENG file first (although intended for MM 6.0.1) and then trying the CF auto root for this SM-N920V which however is intended for Nougat 7.0. Probably a bad idea though as I think the ENG kernel was using something that was patched in the MM BQB1 update if not before.
[SuperSU] Angel_Perez:
Thk, jcmm11 ....

Where do I get the SU.img?

I only have the Binary "SuperSU-v2.79_SR3-SYSTEMMODE.zip" to install it with the TWRP after Flashing Android. Can not you get me a guide to understand better? How do I flash the "SUmount"?

The file "pin", is it a file or is it a folder?

Please help!
[SuperSU] jcmm11:
pin is a file. You flash SUmount like any other zip. All it does is mount su.img at /su so you can access it. su.img is created by the SuperSU installer and already exists on your phone in /data.

You can find SUmount here: https://xdaforums.com/showthread.php?t=2239421

Towards the bottom of the first post. Full name is UPDATE-SUmount-signed.zip.

Boot into TWRP. Flash ("install") SUmount. Go to TWRP's file manager, navigate to /su/etc. Delete the pin file. Reboot.

If you navigate to /su before flashing SUmount you'd find it empty with no files or directories.

EDIT: I just noticed that you're using the system mode zip rather than the standard systemless one. That changes matters somewhat and I'm not sure of the layout in that case. You can try looking for the pin file in /system/etc

If you can't find it post back, I may have a way for you to find it.
[SuperSU] Chainfire:
This is a different signature scheme. As I said, OEMs can (and will) use different schemes. Do you by any chance know if the SuperSU installer ZIP works properly for this device? It does contain similar code that does a best guess on how to work around such signatures, but that doesn't mean it ended up doing things right.

As is clearly stated at the top of the page:

You need an unlocked bootloader for this to work, period. As CF-Auto-Root is moving towards a fully automated system, devices that come bootloader locked from the factory will no longer be filtered out from the listing, as there is no way for the system to know.
[SuperSU] shaggyskunk:
Yeah sorry about that - I'd misread your post regarding the device model.
[SuperSU] osm0sis:
It's actually the same I believe; the Pixel devices also keep it at second_offset, and the Mi Max signature has the same magic as the Pixel devices. As far as I know sukernel makes a working image because it only rewrites the zImage and ramdisk and then updates the header.

Here's the example boot.img I was provided so you can check it out:

https://drive.google.com/file/d/0B4UO8XSpvKCfSWhDT19rMHlpQkk/view?usp=drivesdk

Does sukernel handle sha256 hashed boot images? That's the other one that came up recently, but is unrelated and on a different device (Mi 5s/5c) than the above signing issue.
[SuperSU] Chainfire:
Ok, if you say so :)

Hashed in what way? You mean the header checksum that is normally sha1 ?
[SuperSU] mtw4991:
In case you miss it guys and girls, he's done it again :good:

Well, that didn't take too long: https://goo.gl/l9eUih

Chainfire just made a flashable zip to sign the boot image. Just flash last and boot to system.

I'm now on the May bootloader, Franco Kernel, TWRP and SuperSU all working fine.
[SuperSU] osm0sis:
Yes, indeed! Some newer Xiaomi devices (Mi 5s and Mi 5c so far) use sha256 instead.

Back to the Mi Max though, can you (or anyone really) test a repacked boot image from my AIK v2.7 on the post-May bootloader update Pixel? I'm curious whether the reported second_offset workaround to re-append the original signature would work on Pixel as it did on the Mi Max.

I'm guessing no, since sukernel would in effect have the same thing and that didn't work, but I wanted to know for sure. :)
[SuperSU] chazall1:
I just wanted to upgrade just the May bootloader. Should I fastboot boot.img first and reboot recovery TWRP and flash VerifiedBootSigner.zip. Then reboot. It is not clear? Thanks
[SuperSU] mtw4991:
If you just want the May update, including the May bootloader, then install the full update which will also install the bootloader--

fastboot boot twrp-boot.img which will load a temp twrp, then install the twrp.zip on your sdcard and also install the verifiedbootsigner.zip. Then reboot system normally and you should be good.
[SuperSU] chazall1:
Thanks for the reply. I did not explain I want to stay on PN and not return to stock. I always update my radios and bootloader by fastboot. I just want to see how can I update just the May bootloader in my ROM current setup.
[SuperSU] mtw4991:
Ok, since you are rooted, custom rom/kernel, etc., just fastboot flash bootloader then install the verifiedbootsigner.zip in recovery and keep your fingers crossed lol. Idk how just flashing the May radio and changed bootloader will interact with PN ROM. Maybe ask the PN devs to include it in their next builds...I'm sure they are aware of it by now.
[SuperSU] Kisakuku:
You have to fastboot boot the TWRP image in order to flash the verified boot signer. After fastboot flashing the May bootloader you can't just boot into the flashed recovery since boot.img is yet to be signed.
[SuperSU] chazall1:
Thanks I am thinking about it. lol good information from you all.

Thanks
[SuperSU] user2k10:
Where can I find the SR4 flashable file?

Thanks
[SuperSU] mtw4991:
Here ya go: https://www.dropbox.com/s/9bnbg7v28h7w7ju/eu.chainfire.supersu_2.79-SR4-279_minAPI7%28nodpi%29_apkmirror.com.apk?dl=0

It is the apk you can just install to update SR3 to SR4
[SuperSU] Kisakuku:
Here.
[SuperSU] Ch3vr0n:
Unless you're running a N5x or N6p it is NOT recommended to use SR4 as specifically stated by Chainfire
[SuperSU] Alxoom33:
Do you have a link to [MENTION=631273]Chainfire[/MENTION]'s post? I've been using SR4 on the Nexus 6 and Pixel C without a hitch for some time now.

My impression was that SR4 can be used on any Nexus or Pixel device running 7.1.1+
[SuperSU] Johny Cipeli:
Guys I'm trying to flash it but evereytime it show the mensage:

- Creating image

- Mounting image

- Creating paths

- Removing old files

- Placing files

******************

Boot image patcher

******************

- Finding boot image

--- Boot image: /dev/block/sda5

- Extracting ramdisk

- Decompressing ramdisk

--- Failure, aborting

*************************

IMPORTANT NOTICES

*************************

If TWRP offers to install

SuperSU, do *NOT* let it!

*************************

First reboot may take a

few minutes. It can also

loop a few times. Do not

interrupt the process!

*************************

- Unmounting /system

- Done !

Install from sdcard complete.

I've tried it in different roms, but I got the same error. I'm currently taking it in a Moto G5 Plus (potter) running Android 7.1.2. Thanks for your help !!!
[SuperSU] ktmom:
Chainfire's post re: Preliminary root for ODP1 on 5X and 6P
[SuperSU] Alxoom33:
As I said, it works great on the Pixel C and Nexus 6. I personally have been using it on my devices since [MENTION=631273]Chainfire[/MENTION]'s post above.

---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------

Thank you. That's what I recalled.

I've been using it without any problems on the Nexus 6 running 7.1.1 and on the Pixel C running 7.1.2 (also worked on Android O Dp1).

Your milage may vary on other device.
[SuperSU] Kisakuku:
SuperSU v2.79 SR4 with delay also works on the Pixels with ODP1 in a dual slot setup with 7.1.2.
[SuperSU] Ch3vr0n:
I didn't say it didn't or wouldn't work. I specifically said 'not recommended'. There's a difference.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] Kisakuku:
It was not recommended by the OP because in his limited testing he did not get SR4 to work on the dual slot setup of the Pixels running ODP1 as he stated in the SR4 post. Since then specific conditions required for SR4 to work have been found. Not sure why you're insisting it is still not recommended.
[SuperSU] Angel_Perez:
OK, I downloaded this file from osmOsis: "UPDATE-SUmount-signed_zip"

I indicated, try to flash "UPDATE-SUmount-signed.zip" and exited this error message:

_________________________________________

Instaling Update

ERROR in: /sdcard/Update-SUmount-signed.zip

(Status 1)

Installation aborted.

Missing or not su.img file in directory

_________________________________________

I also wanted to inform you that the Recovery that is installed is the one that I was recommended here in XDA for the Huawei Y-330 "CWM v6.0.2.3 & Huawei Recovery 3ei for Y330.rar" which has the file "recovery.img" and "MT6572_Android_scatter.txt" to install from the SP Flash Tool. So I can not get the "File Manager" in the Advanced menu of the TWRP only these options appear: :confused:

Advanced Menu

- Reboot Recovery

- Wipe delvik cache

- Report error

- Key test

- Show log

- Fix permissions

- Partition sdcard

EDIT: Exactly, what name does the PIN file have? Onli PIN?
[SuperSU] jcmm11:
Yes, only pin (lowercase). As I mentioned in my edit because you're running system mode rather than systemless I'm not sure of the layout involved. Did you look in /system/etc?

Do you have a terminal emulator installed on the phone that's already gotten su permission?

Do you have a root file explorer with a search function?

Can you get an adb root shell?

At this point it's a matter of searching for the file.
[SuperSU] Angel_Perez:
Yes, I understand you very well, but as I enter from the TWRP if in advanced I do not see the option of "File Manager". Already with this inconvenience never be able to perform the search properly and know if it is in: [/System/etc]. Do you know if there is a more complete or better Recovery for the Huawei Y-330?

I already install the Terminal emulator, but when I start [/su] asks me the PIN code and but I denied the ROOT request for the PIN.

I installed ES Explorer Pro, but I denied the ROOT request for the PIN.

The only APK with ROOT within the SuperSU, and install it from the beginning, is Link2SD (thank God).

EDIT:

Teach me or explain how to use a Shell ROOT with ADB and have access to these files ?? Other people recommended me to use the ADB, but I do not know how to use it, nor which shell are the ones I should handle.

Why when I install the "UPDATE-SUmount-signed.zip" it tells me that it does not find the file "su.img", do you say that this file should already be inside the phone?

The file [su.img] is automatically installed when I flash "UPDATE-SUmount-signed.zip"?
[SuperSU] jcmm11:
It doesn't find su.img because you installed system mode SuperSU instead of systemless.

Hmm, there is another way to get rid of pin file. Reinstall ROM.

Adb - use Google. Lots of tutorials available on how to use adb. Once you figure that out come back and I'll give you a find command to run. Whether our not you can run adb root shell depends on your kernel. If you're running a custom kernel you can probably run a root shell. If you're running a stock kernel you probably can't

The simplest way at this point is probably just to reinstall the ROM. If you're running stock you just need to install the system partition (then reroot). How to do that - ask on your device thread. Custom ROM, ask on your ROM thread (but a dirty flash should do the trick).
[SuperSU] Angel_Perez:
I will try to do some tests as you indicate! :good:

I activating the PIN in the SuperSU of another similar phone Huawei G620 and doing a search with ES Explorer Root in: [/ Device]. A file called [.pin] could be located in [/system/.pin]. Will this be? :confused:

EDIT: Activate the PIN on the Huawei G620 and get in with the ES Eplorer Root at: /system/.pin; I moved the file on the MicroSD, closed and reopened the SuperSU. PERFECT! Get rid of the active PIN in the SuperSU, but in this case, you could get Root right to ES Explorer Root.

Now you only need to be able to enter the Shell Root ADB to the other Huawei Y-330 and delete the [.pin] file. If you can help me with the Shell ADB I appreciate it, give me a link of some tutorial that I consider good. Thank you...

IMPORTANT! : You must enable "View Hidden System Files" in the ES Explorer Root, otherwise the file will not be visible.

Screenshots:

http://prntscr.com/f577sw

http://prntscr.com/f5784t
[SuperSU] jcmm11:
That should be it. Do you have a way to delete that file?

Just saw your edit. Give me a few minutes.
[SuperSU] jcmm11:
[MENTION=8253128]Angel_Perez[/MENTION]

We going to make this very simple at this point. Just flash the attached file, it will delete /system/.pin

Do some research on how to use adb when you get a chance. If you're messing with your phone it's something that you really should have some clue about. I have no specific site. Pretty sure there's threads​ on here about it. I know there's lots of Google results.

Since you don't have a file manager in your recovery go back to osmosis' thread. He's got a zip for an Aroma file manager that you should be able to use. (Note: I've never tried it). Just another tool for the toolbox.
[SuperSU] GPSSlovakia:
After each reboot SuperSU 2.79 says that it needs to be updated, why ?
[SuperSU] Ibuprophen:
If you installed SuperSU via the apk file, from the Play Store, then your message reflects that the SuperSU Binaries needs to be installed by the SuperSU app. If the Binaries aren't installed then the SuperSU isn't able to properly manage your devices root access.

If you decide to flash the zip version of SuperSU, then the flash will install the Binaries as well.

I hope i explained this okay... LOL!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[SuperSU] GPSSlovakia:
I have flashed SU.zip via TWRP - that's why it is strange for me that it asks to update after each reboot...
[SuperSU] osm0sis:
TWRP's got that awesome Terminal feature now as well. :good:
[SuperSU] cdiaz92:
V2.79 works on sn-920t running latest ota update 7.0.

Took 2 hours to finish but it did work.
[SuperSU] jcmm11:
Except that he has CWM installed (CWM v6.0.2.3 & Huawei Recovery 3ei for Y330.rar). Terminal would have made things much simpler. Find command then rm.

People that are modding phones should really have at least a basic understanding of adb (which would translate to command line in terminal). Plus a non_blocking kernel.
[SuperSU] osm0sis:
Ah wow, people really need to stop porting CWM..
[SuperSU] bdwilk:
I agree with you but when my digitizer went nuts I was extremely happy that I found a working CWM till my replacement screen was delivered. (2 months) so there is an actual purpose for it still.
[SuperSU] ashyx:
TWRP has mouse support.
[SuperSU] AJ:
does boot image signing work with Android O ?
[SuperSU] Angel_Perez:
Thanks jcmm11, You prepared a direct and automatic scripts (remove_pin.zip) to remove the [.pin] directly when I Flashing, I think only if it is located in this direction [/System/.pin], if I am not mistaken. I try it and I will answer you again! :victory: :good:

The other additional tool that you recommend to install on this Android, is the AROMA Filemanager 2.0 (Beta7) Binary [File: aromafm-2.00b7.zip] from the osmOsis page? Good! :)

Hi, Osmosis.

I do not know from which version of TWRP comes with the Terminal feature inside, and with Mouse support. LOL. :confused:

The problem is that on Android Huawei Y-330 I could not find a Custom Recovery TWRP (BUG FREE) or with [.img] extension to Flashing with SP Flash Tools. If you prepare it I install it without thinking ... :laugh:;):good:

My Huawei G620, incorporated in to the list Philz Touch 6.59.0 (CWM 6.0.5.1) Recovery, the scripts Aroma File Manager, But I select indicates me: :(

_________________________________________________________

No File found

No clockworkmod/aromafm/aromafm.zip in storage paths.

________________________________________________________

logically and Flashing but you have to insert the Zip into the MicroSD logically

Install the Zip "aromafm-2.00b7.zip" and mistake comes up, I do not understand why?: :confused:

________________________________________________________

AROMA Filemanager version 2.00

(c) 2013-2015 by amarullz.com

E: Error in /storage/sdcard1/aromafm-2.00b7.zip

(Status 0)

E:Installation aborted.

press any key to continue.

No file found

________________________________________________________
[SuperSU] osm0sis:
Something seems very broken with your recovery.. :confused:
[SuperSU] Angel_Perez:
Do you really think I have a problem with my Recovery? :confused: I thought that only something extra was missing for the "Aroma File Manager" to work, I have installed it according to the best for this model Huawei G620S (PHILZ-TOUCH-6.59-G620S-buid-01-02-2015.zip) which is based on CWM but Touch, from this link: EloYGomeZTv on YouTube. And install the fabulous Custom ROM of MIUI8 By GLOKIN666. :cool:

Until the moments I had no problems with it and work well until I try only this additional function "Aroma File Manager" included in the Recovery, hemm, Crash... :confused:

Do you recommend me something better Recovery for this Android model? Your advice would be appreciated .. :) :good:
[SuperSU] osm0sis:
No idea.. PhilZ should be good, he used to have built-in menu support for AROMA Filemanager. It has also ceased development like CWM however.
[SuperSU] Angel_Perez:
I Flashing TWRP "3.0.3-0 Touch Recovery Cherry for Huawei G620S" all Good and File Manager Original! Thk... :good:
[SuperSU] Johny Cipeli:
Same problem here, everytime I open the app, it say that I should flash binaries, but it is already installed. :(
[SuperSU] ScRuFFy7:
Are you running stock or custom ROM? If a custom ROM, which one? Does it come pre-rooted?

I run Nitrogen OS and this is only an issue if you don't properly unroot.
[SuperSU] Johny Cipeli:
I have a potter, and it running Dirty Unicorns, but I tried on crDroid and the same issue. :(
[SuperSU] ScRuFFy7:
Based on my limited research my suspicions appear correct. crDroid is pre-rooted. Potter does not appear to be a currently supported DU device. Older DU ROMs were pre-rooted. You need to properly unroot your ROM before changing to a different root.
[SuperSU] Lord_Flaya:
Does --mount-master command work on systemless root?

Tried using it on my Nexus 5x 7.1.2 purenexus along with cigs manager, but it does not work.
[SuperSU] jcmm11:
Should work. I don't see a reference to a restriction as far as system vs systemless. Just a requirement that it be first parameter and su as daemon, but that, I think, is a given

-mm, --mount-master connect to a shell that can manipulate the
master mount namespace - requires su to be
running as daemon, must be first parameter
[SuperSU] peterlee928:
that was not a long post at all :)
[SuperSU] bdwilk:
Use hastebin or pastebin next time, and just posting a log without any details about device or issue is just frowned upon.
[SuperSU] Polv89:
How can I install systemless root on Nexus 6 with purenexus 7.1.2 to use magisk?

Thanks a lot

Inviato dal mio Nexus 6 utilizzando Tapatalk
[SuperSU] Didgeridoohan:
That question sounds like it should go here: https://xdaforums.com/apps/magisk/

If you're asking how to install SuperSU systemlessly the answer is simple: Just flash it in TWRP, for your device it'll be systemless by default.
[SuperSU] Angel_Perez:
Greetings jcmm11, :good:

Perfect run your file (remove_pin.zip) installed from the Recoery, and solved the problem, without needing to re-flash the ROM and Root. Congratulations, now this Automatic scripts will be able to Reset the SuperSU to its initial state without problems, I hope also you can serve another person that happens to you the same. You are a :angel: :good:

Thanks also to you osm0sis, Forget the moment Recovery CWM and PhilZ, but I told you to install the last TWRP to my phone to test and verify if with the "Internal Recovery Explorer" to try to remove the same file [.pin], and I can not see it since, this file is invisible and protected by the system. I do not understand how I could remove it from the Recovery with the TWRP Explorer? :confused:

But equally is a great work of yours and also reconosco that you are a :angel: :good:

Thanks to both! :D
[SuperSU] dexterek91:
after install suhide I have bootlop on Xiaomi Redmi Note 3
[SuperSU] dratsablive:
I suggest you should peruse the Suhide thread.