Let's see the official design and configuration first, then I will decide later.Are you going to upgrade to N10, Nam?
[ROM] [PIE 9.0] AMBASADII ROM FOR N9/S9/S9+ [STABLE] [ODEX] [S4CSJ1] [v8.0]
- Thread starter ambasadii
- Start date
- Status
Don't think we need to wait for official design and details, plenty of N10 details are "accidentally" public out there :laugh:. I'm going to upgrade anyway.Let's see the official design and configuration first, then I will decide later.
Update Mon, 15 Jul 2019 (Security Patch July.2019)
BL_N960FXXU3CSG3_DBT: https://mega.nz/#!85Yl1IxR!klip1A7nk0-Tt9gU1gqE4ECWyfFxE_FIX_ucT9I8Mxk
BB CP_N960FXXS3CSG2_DBT: https://mega.nz/#!ctYByIZS!Y272GmXyUlz3axOw50PI7aP88yG7BeRuFJ8JftlLL9A
BL_N960FXXU3CSG3_DBT: https://mega.nz/#!85Yl1IxR!klip1A7nk0-Tt9gU1gqE4ECWyfFxE_FIX_ucT9I8Mxk
BB CP_N960FXXS3CSG2_DBT: https://mega.nz/#!ctYByIZS!Y272GmXyUlz3axOw50PI7aP88yG7BeRuFJ8JftlLL9A
Hehe, yes. May be I will take this color.[emoji2][emoji2]
Sent from my SM-N975 using Tapatalk
Anyone seeing huge gap between underlines and words?
Edit, it's the font
Edit, it's the font
Last edited:
Could you describe what did you flash?When I flash now unknown emei
Sent from my SM-N975 using Tapatalk
and is this the first time you root and flash a rom in your note 9? or were you able to use an other custom rom before and all was good?
Last edited:
Same happened to me flashing latest ambasadii. I had to flash stock CSG8 to get IMEI back. None of my EFS backups would work when trying to restore them.When I flash now unknown emei
Still when I try to clean flash latest version I get bootloop. I know I'm doing everything correctly so I'm baffled.
Sent from my Galaxy S9+ using XDA Labs
this rom flashes CP (modem). i believe that if users never think of updating their bootloader then ( and modem as well) they have big differences 1 year later and when flashing latest roms it causes issues.
people dont realize that firmware is compromised of 3 essential components( 4 if you count CSC but its not important).
BL aka Bootlaoder
AP aka system,recovery
CP aka modem/ baseband.
custom roms update the system part.
bootloader and modem are out of sync if users dont update them. so 1 year later when users have issues and dont understand why its probably because they dont understand that firmware come in multiple components and just continually flashing the system part(custom roms) never updates the rest. its their duty to keep bootlaoder and modem up to date.
so they end up with miss matching parts that cause issues.
since including BL in roms is very dangerous, ambsadii only included the modem CP. but what this has as an impact is that users that dont keep their device updated properly encounter issues as reported recently in the last few pages.
lesson to be learned: read op check what gets updated when flashing rom. identify base revision. ensure that you keep your bootloader in sync as much as possible. Flashing BL.md5 from latest firmware corresponding to one's device is what should be done.( or else you have to flash full stock and waste time re rooting)
what people dont realise when they flash full stock to "fix" the issue is that it simply puts into sync the old components they should have been keeping up to date all along. and now they have to reroot/twrp when it would have been much simpler to just flash BL and CP
people dont realize that firmware is compromised of 3 essential components( 4 if you count CSC but its not important).
BL aka Bootlaoder
AP aka system,recovery
CP aka modem/ baseband.
custom roms update the system part.
bootloader and modem are out of sync if users dont update them. so 1 year later when users have issues and dont understand why its probably because they dont understand that firmware come in multiple components and just continually flashing the system part(custom roms) never updates the rest. its their duty to keep bootlaoder and modem up to date.
so they end up with miss matching parts that cause issues.
since including BL in roms is very dangerous, ambsadii only included the modem CP. but what this has as an impact is that users that dont keep their device updated properly encounter issues as reported recently in the last few pages.
lesson to be learned: read op check what gets updated when flashing rom. identify base revision. ensure that you keep your bootloader in sync as much as possible. Flashing BL.md5 from latest firmware corresponding to one's device is what should be done.( or else you have to flash full stock and waste time re rooting)
what people dont realise when they flash full stock to "fix" the issue is that it simply puts into sync the old components they should have been keeping up to date all along. and now they have to reroot/twrp when it would have been much simpler to just flash BL and CP
Yes, and while you're at it; It's rarely written aptly without mistakes, so here we go, for the Windows users:
- Download SAMSUNG_USB_Driver_for_Mobile_Phones.zip from https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
unpack, run the exe and install.
- Download Odin 3.13.1 (or newer) from https://techbeasts.com/download-odin-for-samsung-galaxy-all-versions/
and unpack it in a folder you can find later.
- Download Team Win Recovery Project for CrownLTE from https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note-9-exynos-t3833933
and put the TWRP*.tar.md5 file in the folder where Odin*.exe is
- Download the latest BootLoader file, watch out for the matching characters in the name.
- Download the latest Modem file, watch out for the matching characters in the name.
- Make sure you have back-ups of your valuable data and keys stored outside of your internal Samsung storage, on an external micro-sdcard or remote server, or cloud option. Back up your DCIM folder and other data you've stored on your device. Check the chat back-up options within WhatsApp (store it at Google if you trust them with it), and also do backup inside the Signal app if you use that. If you use Titanium Backup make sure you don't have your back-up directory on internal storage, make a copy elsewhere, store it on Google Drive, or use Google Backup to have your apps and settings up there before you switch roms.
- Enable Developer Options (Settings > About phone > Software information - Tap 7 times on Build number to activate the Developer options at the bottom of the Settings menu)
- Under Settings > Biometrics and security switch OFF [ Google Play Protect ] (apart from the open holes in their security setup, you'll see Google shows if an app is 'Verified in the Playstore' anyway whenever you install a new app..)
- Under the Settings > Developer options;
switch off [ Auto update system ]
switch on [ USB debugging ]
switch off [ Verify apps via USB ]
switch on [ OEM unlock ]
If you haven't rooted your Note before it will prompt you this will Factory Reset the device. Let it do this.
On your PC fire up the Odin*.exe you've downloaded earlier, then in Odin under "Options" untag "Auto reboot". Don't connect your USB cable to your phone just yet !
Put your Note in 'Download mode'. To achieve that state follow this carefully, you have to perform near acrobatic stuff, so be careful not to drop your phone:
- Power down your phone. Wait a second.
While keeping both [Volume down] + [Bixby] buttons pressed,
put in your USB cable with Odin running on your PC
(putting in the cable powers up the phone),
the phone boots with a light-blue screen. Release the buttons, and then
press [Volume up] to allow Downloading.
Odin will tell you it [Added!] your device.
In Odin click on [ AP ] and select the TWRP tar.md5 file, then click [ Start ]
Check if TWRP recovery was successfully flashed onto your Note, Odin will say "Passed!"
Patch the BL and Modem files using Odin (as mentioned in the post above), and do it *before* you update the ROM.
Then boot with TWRP recovery, in order to do so, again, some acrobatics are required:
- Disconnect the USB cable from the phone,
hold [Vol down] + [Power] buttons until it powers down,
but don't let go off the [Power] button! It has to remain pressed.
As soon as the screen goes black let go of the [Vol down] and immediately
press both [Vol Up] + [Bixby] buttons (while [Power] remains pressed)
this will make it boot into the great TWRP.
or, if you've already accidentally booted:
- Press [Power] button, press and confirm (Restart) on screen,
while it's showing the shutdown animation press the [Power] button,
keep it pressed! Immediately after the screen goes dark
press [Vol Up] + [Bixby] buttons. It should then boot into TWRP.
- In TWRP swipe right to allow modification. In the main TWRP screen, Select WIPE - Then FORMAT DATA - You need to type 'yes' to perform the wipe. This will erase all data including Internal Storage from your device. This part is required so the /data partition is no longer encrypted. After the format completes, go back to the main TWRP screen and click Reboot and then 'Recovery', This will reboot to TWRP again.
- Connect your USB cable if it is no longer connected. After your device booted into TWRP again on your PC you should see "omni-crownlte" and under that [Internal storage]. Upload your ROM zip into the root of your device's internal storage.
Now flash as described by the rom dev.
- Download SAMSUNG_USB_Driver_for_Mobile_Phones.zip from https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
unpack, run the exe and install.
- Download Odin 3.13.1 (or newer) from https://techbeasts.com/download-odin-for-samsung-galaxy-all-versions/
and unpack it in a folder you can find later.
- Download Team Win Recovery Project for CrownLTE from https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note-9-exynos-t3833933
and put the TWRP*.tar.md5 file in the folder where Odin*.exe is
- Download the latest BootLoader file, watch out for the matching characters in the name.
- Download the latest Modem file, watch out for the matching characters in the name.
- Make sure you have back-ups of your valuable data and keys stored outside of your internal Samsung storage, on an external micro-sdcard or remote server, or cloud option. Back up your DCIM folder and other data you've stored on your device. Check the chat back-up options within WhatsApp (store it at Google if you trust them with it), and also do backup inside the Signal app if you use that. If you use Titanium Backup make sure you don't have your back-up directory on internal storage, make a copy elsewhere, store it on Google Drive, or use Google Backup to have your apps and settings up there before you switch roms.
- Enable Developer Options (Settings > About phone > Software information - Tap 7 times on Build number to activate the Developer options at the bottom of the Settings menu)
- Under Settings > Biometrics and security switch OFF [ Google Play Protect ] (apart from the open holes in their security setup, you'll see Google shows if an app is 'Verified in the Playstore' anyway whenever you install a new app..)
- Under the Settings > Developer options;
switch off [ Auto update system ]
switch on [ USB debugging ]
switch off [ Verify apps via USB ]
switch on [ OEM unlock ]
If you haven't rooted your Note before it will prompt you this will Factory Reset the device. Let it do this.
On your PC fire up the Odin*.exe you've downloaded earlier, then in Odin under "Options" untag "Auto reboot". Don't connect your USB cable to your phone just yet !
Put your Note in 'Download mode'. To achieve that state follow this carefully, you have to perform near acrobatic stuff, so be careful not to drop your phone:
- Power down your phone. Wait a second.
While keeping both [Volume down] + [Bixby] buttons pressed,
put in your USB cable with Odin running on your PC
(putting in the cable powers up the phone),
the phone boots with a light-blue screen. Release the buttons, and then
press [Volume up] to allow Downloading.
Odin will tell you it [Added!] your device.
In Odin click on [ AP ] and select the TWRP tar.md5 file, then click [ Start ]
Check if TWRP recovery was successfully flashed onto your Note, Odin will say "Passed!"
Patch the BL and Modem files using Odin (as mentioned in the post above), and do it *before* you update the ROM.
Then boot with TWRP recovery, in order to do so, again, some acrobatics are required:
- Disconnect the USB cable from the phone,
hold [Vol down] + [Power] buttons until it powers down,
but don't let go off the [Power] button! It has to remain pressed.
As soon as the screen goes black let go of the [Vol down] and immediately
press both [Vol Up] + [Bixby] buttons (while [Power] remains pressed)
this will make it boot into the great TWRP.
or, if you've already accidentally booted:
- Press [Power] button, press and confirm (Restart) on screen,
while it's showing the shutdown animation press the [Power] button,
keep it pressed! Immediately after the screen goes dark
press [Vol Up] + [Bixby] buttons. It should then boot into TWRP.
- In TWRP swipe right to allow modification. In the main TWRP screen, Select WIPE - Then FORMAT DATA - You need to type 'yes' to perform the wipe. This will erase all data including Internal Storage from your device. This part is required so the /data partition is no longer encrypted. After the format completes, go back to the main TWRP screen and click Reboot and then 'Recovery', This will reboot to TWRP again.
- Connect your USB cable if it is no longer connected. After your device booted into TWRP again on your PC you should see "omni-crownlte" and under that [Internal storage]. Upload your ROM zip into the root of your device's internal storage.
Now flash as described by the rom dev.
You are correct. I had purposely stayed on Oreo bootloader as I am one of the lucky ones who has RMM issues and Oreo bootloader allowed me to bypass that. My only problem is that now that I'm fully updated with latest bootloader and modem I still can't get the latest Ambasadii for s9+ to boot. On a clean flash I don't debloat anything and I've tried several CSC's in the aroma just for testing. Other ROMs boot up fine.
Sent from my Galaxy S9+ using XDA Labs
check file integrity or redownload. also are you using this?
ROM.N960F.G96xF.XXU3CSF9-v4.1.by.ambasadii.zip
https://androidfilehost.com/?fid=6006931924117907357
verify that md5 checksum matches downloaded file.
u can flash ota v4.2 ontop right after.
also does it sit on samsung boot logo? if so just give it more time.
Last edited:
Actually no, to be honest this isn't the correct thread for this and this is why I haven't pushed it too much further because we, G96x users also have our own separate thread but I replied to the other guy as his issue seemed the same as mine. We have a newer build v1.9 than 4.2.
But I can confirm all MD5's did match on v1.9.
Sent from my Galaxy S9+ using XDA Labs
? there is no tweaks pro on this rom. i suspect you dirty flashed this rom ontop of ketans or something. tweaks pro is his payed RC i think. so...maybe clean flash next time? or not install tweaks pro maybe? all in all this is not an ambasadii rom issue and much more a user issue.
I took long press back to kill from Ambasadii's S9 1.9 rom and added it to my mods for the note 9 back when he released it. I was waiting to let Ambasadii add it to this rom when he updates it, but he said Samsung is being lazy so there won't be an update until we get a new base, which makes sense.
So here is my mod with Long Press Back2Kill, I have added some more fonts to my font pack too. If there are any fonts you want added let me know, I am always looking for some more good fonts.
(delete system\app\ChocoEUKor\ChocoEUKor.apk from .zip if you don't want the fonts)
Dual Statusbar
Single Statusbar
So here is my mod with Long Press Back2Kill, I have added some more fonts to my font pack too. If there are any fonts you want added let me know, I am always looking for some more good fonts.
(delete system\app\ChocoEUKor\ChocoEUKor.apk from .zip if you don't want the fonts)
Dual Statusbar
Single Statusbar
- Status
New posts
-
[ROM][OFFICIAL][fajita][10] LineageOS 17.1
- Latest: Mimax2upgrade
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone