yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] AfterForever666:
Ok, here's how I managed to flash renovate after it failed a few times (i used to end up in bootloop after 70% into the flashing process).

1. Install stock ARD4 via odin

2. Restart phone and double check if oem unlock is still on

3. Install twrp according to instructions given in twrp post.

4. Restart the phone again and check oem-unlock is still on

5. Reboot into twrp and do a dirty flash (only cache and dalvik wipe) of renovate. I did not flash vendor partition at all as i thought ARD4 base is recent enough. I needed to choose magisk as root method. First attempt I tried supersu, but that didn't work. Supersu gave black screen on startup after i successfully booted the phone. Then, after reinstalling supersu from playstore and updating binary phone didn't boot anymore.

After this renovate boots successfully altough i sense a significant performance decrease. I'll see if that gets better after it settles a bit.
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
If it is laggy, please check whether you have an files in data/dalvik-cache/arm64
[Samsung Galaxy S9 & S9+ Cross Device Development] AfterForever666:
543 files in that folder.

It seems to be picking up speed however as i continu working with it. I think i'm going to be happy soon!

Any clue why the supersu is not working properly? I prefer that over magisk as i also like to use xposed for some very useful modules.
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Yeah give it time to settle.

I really don't know mate, I don't own an s9 myself. I'm sure it'll get fixed in time though!
[Samsung Galaxy S9 & S9+ Cross Device Development] PG101:
Strange.. when I flashed stock, I ticked unlock OEM and went thru the factory reset. I checked now and it's untucked though it says that the bootloader is unlocked already. I tried ticking again and did a factory reset and it says same.. any thoughts?
[Samsung Galaxy S9 & S9+ Cross Device Development] illuzi0n:
Flash stock ARD4 rom via odin and start again. Only way to proceed. Been where you are and there is no fix except reflashing stock rom. This will also make you not have to flash the vendor partition the next time you flash renovate ice
[Samsung Galaxy S9 & S9+ Cross Device Development] PG101:
Oh FFS Sammy!!!

Anyway.. i will do it later..

But why does it say "Bootloader is already unlocked"

And what if it happens again? I guess I will do it only once I plan to flash custom again.. takes forever for the setup without Titanium there at your service.
[Samsung Galaxy S9 & S9+ Cross Device Development] lupin57:
Hi ;)

Its a "secure" way to avoid misuse by users :D
[Samsung Galaxy S9 & S9+ Cross Device Development] PG101:
Yeah I know.. I just don't want to risk it if I have to keep doing it again.. so might as well do it when I'll flash custom.

Strange Sammy.
[Samsung Galaxy S9 & S9+ Cross Device Development] lupin57:
Hi mwilky ;)

In OP, u mention "Firmware (Vendor partition) We don't include the vendor partition in the ROM zip. Please flash this before you flash the ROM!"

Noob question however ... :rolleyes:

Whats the folder called "vendor" present in the zip ? :rolleyes:

...

Due to too much "lag" (dunno why) with the yesterday "dirty" flash, this morning I decided to reflash with full wipe !

I tried the 2 methods, without & with "vendor" flash !

Same very bad result : At starting, after long boot, the phone start again & again •► not a bootloop ... but startloop !

Never seen that before on any device !

I tried to restore my precedent ROM & disaster ... so I finished to reflash the precedent ROM !

How to proceed to get ur ROM working well (without outrageous lag) cause I like all the tweaks stuff :D

Thanx in advance ;)
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Have you flashed a seperate kernel from anywhere? When booted, if dalvik cache hasn't successfully been created, the phone will reboot. So this may be the "startloop" you mentioned. I really need some logcats guys. I've got 10 internal testers with not one issue. There is obviously some contributing factor out there causing issues, but without logs I won't know what it is
[Samsung Galaxy S9 & S9+ Cross Device Development] PG101:
Did the logs I sent help?
[Samsung Galaxy S9 & S9+ Cross Device Development] lupin57:
No separate kernel flashed here on my S9+ ... not yet at the moment :cool:

Since the beginning, always using base kernel or the one included by default in ROM !

When I wanted reflash this morning & before full wipe, I had urs •► 4.9.98-RENOVATE-Star-1.0 :)

...

If I reflash it ... I'll send u a logcat in case of trouble :D

Just for information : The startloop came after Sammy "flickering" & the message "Android start is in progress" !

U didnt answer to my first noob question (vendor folder) ... ;)
[Samsung Galaxy S9 & S9+ Cross Device Development] donoboy97:
I had the same problem with the samsung pulse logo / blue notification light only. I fixed it by flashing my stock Home_CSC in odin, everything is working 100% now.

Somehow I got through it one random time after 20 flashes but com.phone app kept crashing and my data kept crashing to from no service to 4G.

I tried reflashing it with exact same options and boom bootloop / blue notification light only problem. > Flashed stock Home_CSC and it worked!
[Samsung Galaxy S9 & S9+ Cross Device Development] Geekser:
I know what you mean. I have been flashing a while and lately you really have to jump thru hoops to flash - root - etc. I think it is a combination of things -

Advanced Nature of the S9 plus - and OREO - those things have complicated things I beleive - but hell, I am not a developer so I don't really know.

I do love this phone and I am very grateful we have roms like Renovate ICE we can flash. It really makes this very special phone - even more special.
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Flash stock or another rom you can boot, authorize adb and then flash renovate, then start it logging as soon as you can. Leave It going as long as you can.

Vendor is where most of the hardware/device specific files go, since project treble this has all moved to the vendor partition
[Samsung Galaxy S9 & S9+ Cross Device Development] PG101:
Got Soldier's ROM up and running.. rebooted and flashed Renovate without wipe.. but it gets stuck..

Also, the OEM lock again shows in checked.. LOL

But I am rooted and with Soldier's ROM..
[Samsung Galaxy S9 & S9+ Cross Device Development] Aleksandr-1:
mwilky,

Can you please add the SER region?
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Can you log it mate when stuck? Make sure your authorize adb on soldiers rom, then dirty flash renovate
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Guys with issues: there's a new nightly up on the nightly server that flashes vendor with the rom. Could you please try this please? If not I'm gonna really need some logs when you are stuck not booting...
[Samsung Galaxy S9 & S9+ Cross Device Development] mcn1970:
no other changes?
[Samsung Galaxy S9 & S9+ Cross Device Development] jack allen:
Im glad you get what i mean lol it is a mission to do but like you said it is an exceptional phone the camera is beyond amazing i love it i take pictures of random s*** because i juat like looking at the quality of the photo lol and i too am grateful for roms such as renovate/soldiersrom/lightrom/alexandrs rom little choice like back when i had my s5 or s6edge i think that the work to put into rooting tge phone puts most people off rooting and profiting from the potential the phone can be.
[Samsung Galaxy S9 & S9+ Cross Device Development] starbucks2010:
Hi guys,

I've been there also: I was on Soldier stock rom and after flashing Reno 1.0 I got bootloop right after the building cache apps. My /data/dalvik-cache was still empty. The only solution to go out of the bootloop and have built my dalvik-cache was to flash Luca's kernel (Flash kernel) and then the SuperSu. All great and never lost the root since then. Hope it helps.

Good luck.
[Samsung Galaxy S9 & S9+ Cross Device Development] lupin57:
Hi ;)

Same problem here n always present ... but not resolved by Home_CSC flashing :(

Sorry, but I'll maybe come back for a future release (...)

Thanx for all in anyway

---------- Post added at 08:06 AM ---------- Previous post was at 08:00 AM ----------

Thanx mwilky for this nightly r57 ... but how to send u a log when the device startloop :confused: :confused: :confused:

Impossible for me to start properly :(

Remind me please : Where are located logs if any n what is the best way to collect them :confused:
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
If you have authorised adb and you haven't full wiped, plug your phone to your pc, and when it is stuck type adb logcat > logcat.txt into a cmd prompt (you need adb drivers). Leave It going for 30 seconds or so, then send me the text file it created
[Samsung Galaxy S9 & S9+ Cross Device Development] Geekser:
I have a question about one of the last options you are given when flashing the rom - I am using G965F in US and am on ATT - when it gets to the end of the Aroma Installer, you have to choose your region, When you select the US it offers three or four different ones to choose from - which is the one I should choose if I am on ATT in the US (I live in the Midwest) Does it matter which I select?
[Samsung Galaxy S9 & S9+ Cross Device Development] SoLdieR9312:
Just take the first one
[Samsung Galaxy S9 & S9+ Cross Device Development] Pho3nX:
Hi all, each time i try to install Renovate (latest nightly) after starting the Aroma installation TWRP reboots. The device is not encrypted and i'm using TWRP 3.2.1.2. I previously was using Alexand3r's ROM without experiencing any problem at all.

Cheers
[Samsung Galaxy S9 & S9+ Cross Device Development] martgenius:
Uh?

I don't understand all the Problems.

I was on Alexander's Dev 5.4.

1.i make a full backup

2.i flashed the newest TWRP

3. Then I flashed the firmware zip ard4

4.wiped everything

5.cause I Reeded some have problems I flashed the vendor thing ( thought then it's savier)

6.then install renovate

7.it takes a bit

8.then Android updating thing - runs twice and then I get a black screen I pushed the power button for few seconds and tada im in the Android first installation menu

Conclusion: some times (also at the S7/s8) after flashing the device is black, at this time test to activate the screen with holding only power for few secs.

The other thing is, if you stick in a bootloop by upgrading apps touch the screen multiple times at the end, sometimes it don't restart and you get the first Configuration screen.

Hope it helps other users.

Big thx for the ROM, it's really really fast and customable, like it.
[Samsung Galaxy S9 & S9+ Cross Device Development] exocetdj:
I followed these exact steps coming from alexandr rom abd renovate works great. Could it be that theres something left behind from that rom after a wipe that helps this one boot etc like vendor stuff?
[Samsung Galaxy S9 & S9+ Cross Device Development] Leiden70:
I switched from soldiers rom to renovate and i have a question

Fingerprint in my banking App does not Work anymore

With soldiers everything was ok

Did i something wrong?

Thx for an answer
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Nope, you've enabled fingerprint after unlock option. Banking apps require you to unlock your phone at least once with your pin/pattern before you can use your fingerprint
[Samsung Galaxy S9 & S9+ Cross Device Development] t0rz:
Is SafetyNet "cts Profile" false for anyone else? I didn't install anything else but the ROM. NO xposed, NO modules.

Magisk Manager ver: 16.4(1642) by jenslody (version installed by ROM).
[Samsung Galaxy S9 & S9+ Cross Device Development] alizandru:
Good morning. I've had an issue since the first install of the ROM. I've moved from Soldier to your ROM and had the flash kernel installed before the ROM install. I've deleted the SYSTEM partition and chossed fresh install from Aroma choices. After the reboot it did not go from the Logo screen. I rebooted and installed flash kernel. It booted and it works. I want to install other kernels. Am i doing something wrong?
[Samsung Galaxy S9 & S9+ Cross Device Development] Leiden70:
You are right! After deleting fingerprint and new detecting and setting as unlock Option in system i added the fingerprint in my banking App and it works now :svetius:

Thank you for your comment
[Samsung Galaxy S9 & S9+ Cross Device Development] Carach_CZ:
[MENTION=3699616]mwilky[/MENTION]

hi friend, i tried r62 and encountered the same issue i mentioned in testing group on telegram. Used SVN (Updated main foler, exported it to another folder, then zipped its contents with 7zip), dirty flashed in TWRP (using previous AROMA choices), rebooted the damn thing, a got stuck on Samsung, secured by knox screen. Not even flashing back the old zip helps, any help here; kinda annoying to clean wipe everything every time (anyway i could make a TWRP backup, right? Silly me). Thanks.

Edit: Clean flashing 62 is okay and phone boots up perfectly, same as all your builds. Issue is ONLY when dirty flashing from one version to another.
[Samsung Galaxy S9 & S9+ Cross Device Development] ounerkouks:
Hi all

To flash a new nightlies after renovate ice 1.0, we must flash vendor partition ?

it's possible without wipe?

Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
Wait till tonight nightly or use svn. I've added the option to not flash vendor if your current build is working fine.
[Samsung Galaxy S9 & S9+ Cross Device Development] ounerkouks:
thank you.

yes at home everything works perfectly
[Samsung Galaxy S9 & S9+ Cross Device Development] mcn1970:
on the nightlies section on the web page latest version is r57. where are the others?

---------- Post added at 03:45 PM ---------- Previous post was at 03:21 PM ----------

where you find 62?
[Samsung Galaxy S9 & S9+ Cross Device Development] mwilky:
RENOVATE ICE G96X 1.1 - Server: GERMANY - 11th May

MD5: -

RENOVATE ICE G96X 1.1 - Server: GERMANY - 11th May

MD5: -

RENOVATE ICE G96X 1.1 - Server: USA - 11th May

MD5: -​

RENOVATE ICE G96X 1.1​

-Choose whether to install vendor partition with the ROM

-Added code for carrier text color

-Updated Kernel to 4.9.99

-Updated Adaway to 4.0.2

-Added option to remap bixby to change volume mode

-Added code to color notification carrier

-Added code to hide notification carrier

-Removed dalvik wipe option (it will wipe automatically if needed)

I only recommend flashing vendor if you are having problems booting. If you are already on RENOVATE ICE with no issues then there is no need to reflash vendor. If you have trouble

booting, install the ROM first with no root selected, let it boot up and get to the OS, then reboot to recovery and dirty flash, selecting the root of your choice.

If using magisk, for some reason the dalvik cache doesn't build on first boot. I have added a script that will reboot you soon as a boot is completed if your dalvik-cache isn't built.
[Samsung Galaxy S9 & S9+ Cross Device Development] Largewoodenspoon:
Brilliant!

Many thanks SoLdieR!!

---------- Post added at 07:08 PM ---------- Previous post was at 07:07 PM ----------

And mwilky of course!!!!!!
[Samsung Galaxy S9 & S9+ Cross Device Development] mcn1970:
extremely smooth flash over 1.0
[Samsung Galaxy S9 & S9+ Cross Device Development] kgr:
Yes, CTS is false for me too until I toggle Magisk Hide off/on then its all green
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
I installed 1.1 on my G965F/DS this evening, the first time I've ever installed Renovate on any device. Unfortunately, I experienced the same symptoms as others here. After the Optimising Apps... message, the device rebooted and then got stuck at the flashing Samsung logo.

I connected adb and observed the following:

05-12 00:45:11.121 4255 4255 I Magisk : ** Initializing Magisk
05-12 00:45:11.129 4255 4255 I Magisk : * Creating /sbin overlay
05-12 00:45:11.131 4255 4255 I Magisk : * Mounting mirrors
05-12 00:45:11.131 4255 4255 I Magisk : mount: /sbin/.core/mirror/system <- /dev/block/platform/11120000.ufs/by-name/SYSTEM
05-12 00:45:11.131 4255 4255 I Magisk : mount: /sbin/.core/mirror/vendor <- /dev/block/platform/11120000.ufs/by-name/VENDOR
05-12 00:45:11.131 4255 4255 I Magisk : bind_mount: /sbin/.core/mirror/bin <- /data/adb/magisk
05-12 00:45:11.131 4255 4255 I Magisk : * Setting up internal busybox
05-12 00:45:11.165 4259 4259 D Magisk : client: connect fail, try launching new daemon process
05-12 00:45:11.177 4259 4259 I Magisk : Magisk v16.4(1642)-jenslody(1642) daemon started
05-12 00:45:11.177 4259 4265 D Magisk : log_monitor: logger start
05-12 00:45:11.177 4259 4264 D Magisk : log_monitor: magisk log dumper start
05-12 00:45:11.178 4259 4266 I Magisk : ** post-fs-data mode running
05-12 00:45:11.179 4259 4266 I Magisk : * Mounting /data/adb/magisk.img
05-12 00:45:11.186 4259 4266 D Magisk : magisk_img: e2fsck 1.43.3 (04-Sep-2016)
05-12 00:45:11.188 4259 4266 D Magisk : magisk_img: skipping journal recovery because INCOMPAT_RECOVER was clear.
05-12 00:45:11.188 4259 4266 D Magisk : magisk_img: check whether gdt & bitmap free count is vaild
05-12 00:45:11.189 4259 4266 D Magisk : magisk_img: Pass 1: Checking inodes, blocks, and sizes
05-12 00:45:11.189 4259 4266 D Magisk : magisk_img: Pass 2: Checking directory structure
05-12 00:45:11.192 4259 4266 D Magisk : magisk_img: Pass 3: Checking directory connectivity
05-12 00:45:11.192 4259 4266 D Magisk : magisk_img: Pass 4: Checking reference counts
05-12 00:45:11.192 4259 4266 D Magisk : magisk_img: Pass 5: Checking group summary information

And that's where it sits... forever.

In an effort to fix this, I rebooted to recovery and reflashed Renovate, this time without root. Then, without rebooting, I separately flashed magisk.zip (the 16.4 jenslody version from inside the ROM zip) and then rebooted.

Bingo! The device booted properly this time.

I hope this goes some way towards helping you troubleshoot the hangs that some users are seeing. I should add that I was coming from version 2.4 of Soldier's ROM and his ELS kernel.

In fact, Renovate reports that I'm still using kernel 4.9.99-SoLdieR9312-start2lte-2.4. I'm not sure whether Renovate shares that kernel, or whether the proper Renovate kernel has failed to be applied.

Anyway, now to go exploring this new ROM! Thanks for all of your hard work on on it.
[Samsung Galaxy S9 & S9+ Cross Device Development] hadinz:
Can you please tell me where in the rom did you flash the Magisk from? Can't find it. Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
$ unzip -l RENOVATE_ICE_G96X-1.1.zip | grep magisk
0 05-11-2018 19:26 root/magisk/
9860927 05-03-2018 18:25 root/magisk/magisk.zip

Just extract that file before you flash the ROM, then flash it after flashing the ROM.
[Samsung Galaxy S9 & S9+ Cross Device Development] illuzi0n:
is the latest version magisk thats working 16.4?
[Samsung Galaxy S9 & S9+ Cross Device Development] Kalemawesome:
Dodgy servers!!!

Really annoying.
[X Style (Pure) Q&A, Help & Troubleshooting] jonpagecr:
hi,

what are the recommended modules to be installed on this device?

Thank you.
[OnePlus 5 Questions & Answers] segevngr:
Hey guys!

im in a serious condition right now and i really need your help,

I've wiped everything on my device, and wanted to copy my new rom and install it from scracth (not my first time doing so).

So after the wipe i've used TWRP mount with MTP as usual, and pc indeed recongized my empty internal storage.

but than i discovered i cannot copy anything to it! the copying proccess just stuck as if its not really recongizes my device!

I basically don't have a phone right now, and have no idea whats my next step.

please help ! :crying:
[OnePlus 5 Questions & Answers] segevngr:
Update: I've tried copying no limit's rom via sideload but it says "cannot read zip file" :(
[OnePlus 5 Questions & Answers] vanzant83:
I had a similar problem yesterday i guess i made some mess inside the "mount" option. I solved that way: switched the mtp enabled and then i reboot the twrp, right at the the reboot swipe to allow modification and that's It. Pc now can see and transfer file in the phone
[OnePlus 5T  Questions & Answers] anas sami:
Whenever I'm on-call and talking to someone else , most of the times the speaker just makes a noise (sounds like something vibrating) and i can't listen to whom I'm talking. After that I've to put my 5T on laud speaker and again turn off laud speaker to listen up. Is this a bug or I've to go to service centre. I'm using 8.1.0 stable. I've done resetting but can't work.
[LeEco Le 1S Questions & Answers] A.E.:
I bought a new Letv 1s screen to replace the one that was cracked.

The mobile phone was working fine with the cracked screen, before the replacement.

After applying the new screen appear vertical lines only (I can't see anything beyond the lines) any idea what is going on? How I fix it?
[LineageOS Questions & Answers] najeb3:
Hello everyone,

I've flashed LOS 14.1 on my S4 mini. When I went to add an account (my Samsung account), I discovered there are only few options like: Office, Exchange and IMAP ..etc. But I want to set up my Samsung account to get the backup. How to do this ?

Thanks
[LineageOS Questions & Answers] ericch2:
Have you found a solution?
[LineageOS Questions & Answers] nezlek:
Not very likely

Like most Samsung apps, the backup is probably going to be restricted to stock ROM configurations. HOWEVER, if you want to install select Samsung apps, you can (PROBABLY) find the .apk files for them at www.sammobile.com. SOME of them WILL want to use your Samsung account to connect and in those cases they will recognize your credentials if you have already defined them before you flashed a non-stock ROM. You also will likely have to add / edit a statement in your build.prop file concerning ro.config.tima if you have tripped Knox along the way. Not all of the Samsung apps will work completely, since some features apparently just don't and won't work with AOSP based ROMs. Hey, you can't have everything !! Good Luck.
[LineageOS Questions & Answers] najeb3:
I am really happy for your reply. Yeah, I can not have everything as I am running a custom ROM because I wanted to stick to my s4 mini 3g.

Anyways, I am visiting sammobile,com ,but I am pretty sure that I can not edit or add any statements for the apk as I am an electrical engineer with no experience in android development, but I will try and get back if I got results.
[LineageOS Questions & Answers] XTCrefugee:
Just FYI I tried this myself a while ago without much success. If you download a stock-based TWRP-flashable rom for your device and extract the contents you should be able to find the APKs for Samsung account, the store, push service etc. (some are also on apkmirror, if you want to try newer versions). The Galaxy store does actually work, but crashes when you try and go to the account page (as there's no Samsung account on the device) so you can only install free apps. The same goes for the Samsung customized versions of apps such as Kindle, it works until you try and log into a Samsung account. The actual Samsung account service itself wouldn't work for me, it appeared in the list of possible accounts to set up but would just crash if selected. Fortunately, the best Samsung app (the internet browser) can be installed on any device directly from the Play store, so you don't need any Samsung account services for it.
[LineageOS Questions & Answers] najeb3:
I understand now that Samsung account service would not work on customised ROMs. I have tried to download the application from Sammobile and it did not even show to add a samsung account. And in your case even if it shows, it will crash once you proceed.

Thanks for your reply.
[Moto G5 Questions & Answers] SARFACE:
Hello my friends, I'm new here and I have some problems with my device moto G5 xt1670, actually I unlocked the bootloader and intalled the TWRP 64 bit for install some rom 8.1.0 but when I installed that TWRP my device's brick, actually I solve that problem and I want to install a Rom for my device plis help me with some rom and twrp for my device plisssss