Lately i'm experiencing problems with flashing custom roms (i.e. UltimaROM , Xperianze, whatever)
What i did is:
1: flash the latest CWM , touch and non -touch with Odin
2: download ROM of choice , copy to internal SD-card
3: reboot recovery, fact-reset, wipe cache + dalvik
4: flash rom ( with aroma installer )
5: boot phone
with booting it keeps hanging on the Samsung i9300 logo txt. It doesnt matter which rom i flash. it always keeps hanging.
I've tried alternative methods like flashing TWRP and do the same as above but again, no success. I also tried factory-reset after flash, cache wipe etc. no success.
The weirdest thing is: when i try to flash CM or MIUI ( current running MIUI ) , it works like a charm, but normal "custom" roms are not approved it seems.
does anyone have a suggestion for me what to do? or explain what i am doing wrong , or even better, can explain why CM-based ROMS work?
Have you checked the MD5 of your downloaded ROMs when they are on your SD card? Format system, data and pre-load before flashing? Tried flashing an alternative kernel/radio before you boot the first time?
If only stock based ROMs are a problem then it maybe something that is unique to them, probably a direct hardware hit via the kernel.
Try returning completely to stock to test, flashing Samsung's vanilla EMB5 via Odin - including stock recovery and full wipe. If that doesn't work then you may have a hardware issue that CM or MIUI doesn't use.
yeah good idea to return to stock and try all over again.
to your other questions: no i didnt flash another kernel after i flashed the custom rom. i've tried with several kernels which options were given to me in aroma installer ( boeffla, syah, stock )
md5: did that
format system and data: nope. kinda relied on the fact-reset + cache/dalvik
what do u mean with pre-load?
if I were you I would format data & system again manually after the fac. reset thing, or even more clean use the mega wipe flashable zip to have a clean slate to start from (it will format anything but the ext. sd-card). Then flash the rom from your ext. sd-card and see how it goes.
additional possibly helpful hints
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
magnamentis said:
try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
Click to expand...
Click to collapse
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
thanks for the explanation which makes totally sense, so my feeling which i could not explain was right always better to learn exactly why than just guessing
no thanks button found in your post however, so i want to thank you this way.
regards
Hi,
I want to temporary boot my nexus 6 with ElementalX.
I'm familiar with the fastboot command fastboot boot boot.img
But what boot img I need to use after downloading the flashable zip file of the kernel?
Pics provided below, which file I need to use for the fastboot command?
I don't believe you can flash Elemental kernel in that regards as it is set up differently than many custom boot.imgs. Even if you did, you would be missing out on many functions of the kernel without the other settings being installed. You could either do a nandroid backup of your boot and system and restore that when you were done testing the kernel or dirty flash just the rom you are on (they have flashable stock roms in the forums) while just wiping the cache and dalvik cache.
es0tericcha0s said:
I don't believe you can flash Elemental kernel in that regards as it is set up differently than many custom boot.imgs. Even if you did, you would be missing out on many functions of the kernel without the other settings being installed. You could either do a nandroid backup of your boot and system and restore that when you were done testing the kernel or dirty flash just the rom you are on (they have flashable stock roms in the forums) while just wiping the cache and dalvik cache.
Click to expand...
Click to collapse
I only want to flash ElementalX in order to be able to use properly on Android M.
But I'll try to do a nandroidbackup . funny I never though to do that. Thanks.
Yea, for best results, use TWRP, make a backup, then flash what you need. No reason to keep a stock recovery setup if you are running a custom kernel and root as you will not want to take OTA updates anyway. Keep in mind that it is also recommended to update the radio and bootloader. I have seen reports of members being fine without them, but it's best practice to keep them all updated together. If you don't want to mess with any of that and don't care about being rooted or customized at all, then you will just want to unlock the bootloader and flash the factory img files from Google and then all partitions will be updated to official 6.0 and you'll be done with it. If you go that route, remember to backup your internal storage as unlocking the bootloader and the update will wipe everything.
Clarifying here, it's a simple question.
I saw several people in the blu_spark custom kernel thread saying that you don't need to do a full wipe and flash stock OOS to flash the kernel. If I'm coming from stock rooted with TWRP, am I able to just flash the kernel itself without wiping anything? New to flashing custom things in general.
Dont know for sure, but what I'd suggest is to Flash the Kernel & Wipe Dalvik before reboot, thats what i do, no problems so far, same for updates too.
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Im using despair kernel
Scherzengel said:
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Click to expand...
Click to collapse
How would I be able to check this?
Ask the Dev of the Kernel you want to install. But first read the description of the Kernel and the Devs advice for Installation.
Most kernels do not require a whole system wipe like that. As long as the kernel is compatible with the ROM you should have no problems in just plain flashing it. You can find out if it is compatible by looking on the Original Posting by the developer. Another thing to note: if a kernel developer does not specify a ROM compatibility and yet a kernel installs and the ROM even boots up that does not mean you are completely bug free. An example of this would be using blu_spark's OOS kernel on CM 13. It will flash, boot, but your phone will lag, randomly reboot, apps will force close, etc.
He actually has a beta kernel for CM 13 so that you can use his customization and without above issues.
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs. Orange Fox, along with other TWRP derivatives, allow complete access to virtually all of the phone, so it is very easy to accidentally hard brick the phone if you don't fully understand what your doing.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
It is recommended to have encryption removed when flashing, but this is easily done by temporarily removing lock screen security before flashing and adding it back after.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
Do I need to update my vendor and firmware when flashing a new ROM
-----------------------------------------------------------------------------------------------
Probably not.
If you currently have MIUI installed and it's up to date, then you will have the latest firmware and vendor and won't need to flash them.
If you're moving from one custom ROM to another, then it depends on how up to date your current ROM is. If the vendor and firmware requirements of the new ROM match the requirements of your current ROM, then will have the current vendor and firmware already installed and so do not need to flash them again.
Only when the new ROM needs a later version of vendor and firmware than you have currently installed will you need to flash them. This isn't such a common occurrence, so you'll not need to flash vendor and firmware often.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Thank you
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
AkashNP said:
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
Click to expand...
Click to collapse
Since, I think, Android Marshmallow, Google have added forced encryption. Before this you had the security menu option to encrypt your phone storage, which required a separate password to be entered on every reboot. Now encryption is done as standard and uses your lockscreen security PIN/password as the key.
Initially your phone will be unencrypted, but as soon as you first set-up lockscreen security the phone will be automatically encrypted.
Many people see this as a good thing. Should you lose the phone, you data is secure and cannot be accessed without the lockscreen PIN/password. Other people don't care about this and so prefer to disable encryption, as it makes life a little easier when flashing custom ROMs.
Some people, incorrectly, believe that disabling encryption is necessary when flashing custom ROMs, or that disabling encryption is the only solution to problems seen when flashing. This is not true and disabling encryption should only be about a users personal choice to be unencrypted.
Think of vendor and firmware as the equivalent to device drivers for PC components. They are a collection of compiled code files, provided by component manufacturers and the phone manufacturer, to allow Android to communicate with the hardware components in a standard way. Occasionally these files might get updated, as part of a MIUI update, to fix a bug or to add extra functionality. When these files are updated, custom ROM devs will include them so that they get the bug fixes or extra functionality. When this happens they will update the minimum vendor and firmware version requirements for their custom ROM - the version will be the actual MIUI version in which the vendor and firmware files were updated.
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
AkashNP said:
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
Click to expand...
Click to collapse
Follow this guide, assuming you've downloaded the recovery ROM.
https://c.mi.com/oc/miuidownload/detail?guide=1
If you view this on a mobile, it might be a blank page. In this case, you need to change the mobile browser to desktop mode when viewing this page.
The most simplest and right guide on the xda forum, well done! Thank You
Noob here
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
jaydeep0712 said:
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
Click to expand...
Click to collapse
As far as I'm aware, there shouldn't be any noticeable difference in speed. The whole data partition is encrypted as a block, so, in use, accessing files is done on an already unencrypted partition. The individual files are not encrypted/decrypted on demand on an individual basis.
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
I've never gone for the screen refresh rate mods, so can't comment on them.
Thanks for replying.
Robbo.5000 said:
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
Click to expand...
Click to collapse
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
jaydeep0712 said:
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
Click to expand...
Click to collapse
I'm currently using LOS. It's mostly bug free. There seems to be a current issue with wired headphones - on calls it is using the phone mic instead of the headphone mic. For my use, I don't see any other issues, but there could be other things around functionality I don't use.
Fingerprint recognition is about as good as it gets on custom ROMs. Not quite as good as MIUI, but good enough.
Thank you so much for busting so many myths, I was dying for someone to speak up but couldn't muster the courage myself. Hats off, and I support everything you said 100%.
Robbo.5000 said:
With the latest Flipkart sale, there have been a number of new owners asking a lot of old questions.
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Click to expand...
Click to collapse
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
XXXLR8 said:
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
Click to expand...
Click to collapse
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Robbo.5000 said:
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Click to expand...
Click to collapse
I did the TWRP format (which prompted me to type yes to continue) and wipe data partition,but didnt wipe the partition itself, rebooted, installed pixel experience, and still same, i even got into a boot loop, which i got out to, by forcing my way out by fastboot, and reinstalled MIUI,
Im currently at MIUI, currently stable.
So Im going to try again some other time about this, when i have another available device to use while i reinstall pixel experience in Mi9T Pro
But, your guide is helpful, it failed on me probably because of a mistake I made.
Thanks anyways!
Best Regards.
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
FuriousFrodo said:
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
Click to expand...
Click to collapse
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Robbo.5000 said:
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Click to expand...
Click to collapse
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
FuriousFrodo said:
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
Click to expand...
Click to collapse
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Robbo.5000 said:
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Click to expand...
Click to collapse
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Sent from my [device_name] using XDA-Developers Legacy app
FuriousFrodo said:
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Click to expand...
Click to collapse
Yes, both things are normal. You should be good to go with your new ROM. No need to reinstall it.