Related
WARNING
SONY has recently changed the method to unlock a bootloader. A rewrite will be done soon. Sorry for the inconvenience
Welcome to customising your phone! I made this guide specifically for new Xperia SP users (be it secondhand phones or you're just starting to do more with your XSP), and for future references until our Xperia SP forum cease from existence. There are many things to learn, if you search in the forums. This guide is to simply guide you into doing stuff in a more verbosely explained manner, at the same time will always be kept updated along with the progress of our Xperia SP.
This guide is universal — you can use any ROM versions that you like!**
"Universal Guide" Notice **
This guide mentioned "flashing custom ROMs". Though this guide is legitimate as it gets for flashing a ROM, I must warn you that methods provided here are exclusively a general outlook on how to flash a ROM. Always use the extraneous methods provided within a custom ROM's thread. If you fail to meet the exclusive requirements and steps of a ROM you will obviously encounter problems!
Disclaimer
Before you proceed, please understand that everything you do with your device, has many risks. If performed correctly, those terrible consequences may not happen. Any actions you will make are solely decided by yourself, and I have nothing to do with any damages that occur when you follow this very guide. Most importantly, following this guide will definitely void your warranty.
NOTE!
This post relies entirely on heavy formatting so you can understand better. Please open this post in a web browser, if you are viewing from a forum app. Tapatalk, for example. This also includes XDA Labs, which as of writing doesn't parse forum tags properly.
Things to consider before using Custom ROMs for your Xperia SP
Bootloaders
There are two different requirements for each custom ROMs here in the Xperia SP forum, in which there is one that require an unlocked bootloader and another is the one that can be used in a locked bootloader. What is a bootloader? A bootloader is a tiny program that enables you to get into an Operating System. Xperia phones have their bootloader locked by default. The one and only difference between a locked bootloader and an unlocked bootloader is the freedom to flash anything without so much concerns and risks of soft-bricking the device. In worse case scenario, even hard-brick too.
The choice to unlock your bootloader will be made by yourself. This guide will present on how to flash custom ROMs regardless of what bootloader you choose. NOTE however, some Xperia SPs are not allowed to unlock the bootloader. To check if you can unlock your bootloader, dial *#*#SERVICE#*#* (*#*#7378423#*#*) in Dialer. Tap on Service info > Configuration > Rooting Status and check if you can unlock your bootloader. The text "Bootloader unlock allowed: Yes" means that you can unlock the bootloader of your Xperia SP. If "No", I am sorry to say but you cannot do anything to unlock the bootloader. Don't worry yet! You can still use a special type of custom ROMs on a locked bootloader
Unlocking the bootloader will indeed have some drawbacks.
This will remove your DRM keys from your TA partition.
You will lose Bravia Engine on stock ROM forever. This due to the fact that the Bravia Engine requires the DRM keys that resides in your TA partition. This can be remedied, as you can actually back up your TA partition thus preserving your DRM keys as well!
Warranty will be lost for good. If you still have warranty, and quite paranoia if your device somehow magically broken, you also need to know that DRM keys also plays a huge role on confirming whether you have tempered with your Xperia SP's bootloader or not. SONY service centres will always check for the TA partition and also to see if your device is rooted or not. Root is reversible, but lost DRM keys is not. Again, backing up TA partition helps.
For those who can unlock their bootloader, since Xperia SP is no longer maintained officially by Sony and its last official ROM / firmware version is and will always be Jellybean 4.3, it is highly recommended to unlock your bootloader and set your Xperia SP for freedom. Unlocking the bootloader will also and always help you simplify things in the future.
Features
Custom ROMs are ROMs that are specifically made by different developers and teams based on their preferences and general idea. Depending on the custom ROM you want to use, you should understand that stock ROM features (e.g Camera, Walkman, Xperia Keyboard, Bravia Engine, etc) will no longer be available. This only applies on the custom ROMs that does not use the original stock ROM as a base.
Custom ROMs which are based on stock ROM on the other hand, usually contain a customised experience, while also providing the stock features to put into good use.
Stock ROM features aside, custom ROMs mostly are packed with other exciting features and customisations for you to tinker with, thus allowing you to make your ROM as unique to you as possible. You can inspect the screenshots posted on the ROM thread for a view of what features the ROM provides, or alternatively, (my favourite method) flash the ROM and test to see if it meets your preferences, and if the features really hook you up.
Explanation by another website (you will leave XDA)
Concluding
Now choose your device's future:
If you don't give a darn about TA partition, please refer to the guide 1(a). This can greatly reduce the hassle required while following this guide.
If you wish to both preserve your TA partition and unlock your bootloader, follow the respective guide which is guide 1(b).
If you don't want to or can't unlock your bootloader, there is also a guide for that, which is guide number 1(c).
Got questions? Refer to the second post for Q and As. If your question isn't there, feel free to ask!
Requirements!
Backup your apps. Use Helium backup tool. Do a backup of the apps that you want (only user-installed apps, or in other words, the apps that doesn't come with your Xperia SP when you bought it)
Un-metered and fast internet connection
A custom ROM's flashable zip of course. Copy the downloaded zip to your SD Card.
Download it by:
Going through the Xperia SP Lollipop Hub by @TheAvengingTITAN
Going through the Xperia SP Marshmallow Hub by @TheAvengingTITAN
Going to the custom ROM's thread of your choice in the Development subforum or the Original Development subforum
gapps package. Download the one supplied or suggested in the thread of the custom ROM of your choice. If there isn't any, maybe OpenGapps might be useful for you: http://opengapps.org (our device's architecture is ARM). Copy the downloaded zip to your SD Card.
Additional requirements if you want to unlock your bootloader:
Flashtool. Flashtool is a great software for you to flash your stock ROM back and also to do some other stuff. Download and install
Proper device drivers. After installing Flashtool, install the drivers by executing an installer from C:\Flashtool\drivers (assuming you didn't change the install location)
TWRP Recovery. We need the Beta downloads. Please download the twrp-3.0.X-rX-fota-huashan.zip. Copy the downloaded zip to your SD Card.
Unlocking the bootloader will wipe your /data partition. Please backup any files that you find important in the internal storage before performing these steps
Your IMEI written somewhere else. Dial *#06# to get your IMEI
Acceptable battery level (80% recommended)
Bootloader unlock code:
Go to: http://unlockbootloader.sonymobile.com/ and read everything!
At the bottom click 'Start Unlocking the Bootloader'
A number of prompts will be given. All you have to do is proceed (reading is optional and is recommended!)
Eventually you'll end up in the "Create Unlock request" page. From here enter your IMEI, name and email address. If your IMEI is unaccepted, try to enter your IMEI again, but excluding the last digit.
You should then receive the bootloader unlock key inside your email inbox.
1(a) I don't care about TA partition
WARNING: Once gone, you'll never able to retrieve your DRM keys, which will result in unable to use the Bravia engine, if someday, you wish to return to stock.
Just skip the guides below and jump to guide number 2.
1(b) I wish to both backup TA partition and unlock my bootloader
A working adb bridge is required before you proceed. Install it on your computer from here
Make sure USB Debugging is enabled in Settings > Developer Options
Root your 4.3 ROM with Towelroot!
Download and install the Towelroot apk
Open the newly installed app
Hit the make it rain button
After succession, go to Play Store and install SuperSU
Open SuperSU
It will prompt to update your binary. Continue to do so
It will prompt and ask you to choose which method to update the binary. Choose "Normal"
Reboot your device
Backup your TA Partition. NOTE! You can do a "dry-run" to determine the integrity of your backup. NOTICE! If you are a Windows 10 user, do note that you will need to apply this "patch" for BackupTA to work on your operating system
Follow guide number 2.
1(c) My bootloader is not unlockable / I don't want to unlock the bootloader
A working adb bridge is required before you proceed. Install it on your computer from here
Make sure USB Debugging is enabled in Settings > Developer Options
Root your 4.3 ROM with Towelroot!
Download and install the Towelroot apk
Open the newly installed app
Hit the make it rain button
After succession, go to Play Store and install SuperSU
Open SuperSU
It will prompt to update your binary. Continue to do so
It will prompt and ask you to choose which method to update the binary. Choose "Normal"
Reboot your device
Install CWM recovery
Reboot into CWM recovery by pressing the Camera button whilst on the BLUE light on the LED bar
You can navigate in CWM by using the volume and power keys or by swiping the screen up, right, down, left.
Wipe everything you can.
go to "Mounts and storage"
Format /system
Format /data
Format /cache
Go back to main menu
Get into "Advanced" > "Clear Dalvik Cache"
Go back to main menu
Attempt "Wipe data/factory reset"
Flash the custom ROM zip you've downloaded.
Go to "Install zip"
Choose "Choose zip from /storage/sdcard1" (I am assuming you've put the zip into your SD card)
Navigate to the zip you've copied, and select it
Choose "yes"
Flash gapps. The flashing process is similar to how you flashed the custom ROM zip based on the steps above.
Reboot the phone
You now have your preferred custom ROM installed! Congratulations! Set up your phone as usual now.
Restore your applications backup if you wish to have your apps back.
Your steps end here.
Now jump to the "Have fun" part to continue reading
2) Unlock the bootloader and flash TWRP recovery
Unlocking your bootloader:
Shut your phone down.
Open FlashTool as administrator.
Copy your unlock bootloader key that you received
Make sure drivers are installed. Install them by going to Flashtool install directory (default is C:\Flashtool) and then "drivers" folder. Install the .exe there in.
Click BLU on the toolbar
Connect your phone in flash mode (hold down vol down while device is powered off then connect to your computer. you can release vol button once phone is detected)
This will require you to enter IMEI and bootloader unlock key. You might need to check thrice for this to make sure the IMEI and bootloader unlock key is correctly copied.
Proceed. This will wipe your data completely. I've warned about this earlier on this post so I assume you've did a backup of important files.
Disconnect your phone upon completion. If it restarts, you need to shut it down after it booted.
Leave Flashtool open in order to proceed to the steps below.
Flashing the recovery:
Extract the TWRP recovery zip file you attained earlier. We will need to use the "twrp.img" file
Connect your phone in fastboot mode (hold down vol up while device is powered off then connect to your computer. you can release vol button once phone is detected)
Flash the kernel by selecting the Lightning icon in the toolbar, select Fastboot mode, then select "Select Kernel to Flash". Navigate to and choose the file "twrp.img" extracted earlier
Unplug your phone upon completion
Power up your phone. It will boot directly into TWRP Recovery
Once in recovery, you may now close Flashtool.
Please follow the guide below.
NOTE!
This will only grant you temporary access to recovery, as we are flashing the recovery into your /boot partition. When you flash the ROM zip later, this partition will be replaced with the ROM's kernel and the recovery will be lost!
3) Flashing the custom ROM
NOTE: Please understand methods are vary for different ROMs. Please prioritise steps provided in a custom ROM thread. This guide however, can be regarded as a "logic" for you to flash such custom ROM.
Wipe everything you can.
go to "Wipe"
Advanced Wipe
Tick Dalvik / ART Cache, System, Cache, Data
Slide the slider to wipe the ticked partitions
Go back to main menu
Flash the zips you've downloaded.
Go to "Install"
Tap on "Select Storage" button to select your storage that contains the flashable zip of your ROM and gapps. Assuming you put it in the sdcard, then it should be "Micro SDCard"
Navigate to the ROM zip, and select it
After that, hit the button "Add more Zips"
Navigate to the gapps zip, and select it
Make sure "Zip file signature verification" is disabled
Optional: You might want to flash the TWRP recovery zip downloaded earlier so that you would have a permanent TWRP recovery
Slide the slider to start flashing process
Choose "Reboot system"
You now have your preferred custom ROM installed! Congratulations! Set up your phone as usual now.
Restore your applications backup if you wish to have your apps back.
Your steps end here.
Have fun
You should now have completed the guide and have a custom ROM running on your device. Have fun with numerous new experiences in the time to come!
If you want to change ROMs in the future, after you have already flashed a custom ROM, you will just have to restart the same flashing procedure.
Don't forget to thank this post if my guide really helped you!
FAQ
FAQ
Q: What are custom ROMs actually?
A: I believe, Google will help you. This link might help you as explained by AndroidPolice: http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/
Q: I can't unlock my bootloader! What should I do?
A: I understand how sucks it is for this to happen. But don't worry, there are also methods for locked bootloader phones. If you read my first post correctly, there is a method geared towards a person who can't unlock their bootloaders.
Q: What is a TA Partition?
A: TA Partition is a unique partition that can be found in almost any Xperia phones. It contains mostly DRM keys and other boot parameters. Unlocking the bootloader does not wipe the TA partition, but somehow edit it. I don't know much about this part.
Q: Why will Bravia Engine not work if I use custom ROMs?
A: In order to use some custom ROMs you'll need to unlock your bootloader. Unlocking the bootloader will definitely remove the DRM keys, which is a requirement for the Bravia Engine. Backing up TA will backup your DRM keys as well, just in case if you want to get back to stock.
Q: If that's the case, what will happen if I relock my bootloader after flashing a custom ROM?
A: Relocking bootloader when using a custom ROM is not a safe practise, and will definitely soft brick your device. Basically, constant SONY logo.
Q: How about flashing custom ROM without unlocking the bootloader?
A: It depends on the ROM. If the ROM is solely for unlocked bootloaders, doing this will of course brick your phone. Please refer to guide number 1(c) on how to use custom ROMs without unlocking a bootloader (which only applies to ROM for locked bootloaders).
Q: Is it really necessary to back up TA Partition?
A: TA Partition backups will help you on getting your phone to its really fresh factory state. Moreover, it allows you to have Bravia Engine working on stock ROM, if you wish to get back to the stock ROM. If your phone has warranty, backing it up is recommended, as you'll need to restore it before handing it to the repair centre.
Q: I didn't backup my TA Partition. Can I ever get it back?
A: You'll never able to get it back. And please don't ever try to restore anyone's TA backup as that will ultimately cause your phone to be bricked very hard.
Q: What is this software called BackupTA?
A: Please read the explanations provided in the thread of such software. The software help you to backup and restore your TA Partition.
Q: Are these guides safe?
A: Sure! :fingers-crossed: But I can't give 100% guarantee. Fortunately, this guides are constructed based on my experience. My Xperia SP is still running and is still being used right now.
Q: I broke my phone while following your guide. What can I do now?
A: I hope its a soft brick. If so, please follow mrjraider's tutorial on how to use Flashtool and then flash a stock FTF to get back your phone to its stock ROM. If your bootloader is unlocked, reverting to its normal state is easy. Just go back to the main post of this thread, and follow the "Flashing the recovery" part of the guide number 2.
Q: What are bricks?
A: There are two types of bricks. First one being soft, and the second is hard. Therefore softbrick and hardbrick. Softbrick is a situation where you cannot use your phone, however it can still boot / start. This applies to events in which you keep having SONY logo shown many times, or the SONY logo stays on the phone after minutes of waiting. Softbrick is repairable. Hardbrick, is a situation where your phone is completely damaged. Usually, the phone will never able to start even after many methods used and will show signs of ultimate death. Repair is possible, though mostly it is not. If you prefer, you can have a look in Wikipedia for a solid and thorough explanation
Q: How can I prevent from bricking?
A: Always know what you are doing and follow the guidelines laid out
Q: How about battery usage, is it good?
A: Custom ROMs are mostly based on the original Android experience (AOSP). AOSP is the purest android you can ever think of. AOSP doesn't have these neat features that most company provides, rather, it is Android at its bare. This being said, Stamina mode will no longer be available on your phone. To counter this you may use Greenify, an app that hibernates apps. Moreover, since custom ROMs aren't developed by the manufacturer of the device itself (in this case SONY), it will not conserve battery as good as stock, but at the same time battery life is still acceptable and long-lasting. Also as of Lollipop, the introduction of Doze to the AOSP makes battery conserving on custom ROMs a lot better. To summarise, the experience is slightly different, but still is amazing. To give a rough comparison on a ratio-based rating, it would be 0.95:1 (custom ROM:stock ROM)
Q: The ROM I use has an update. How can I update?
A: You can just download the new updated zip, and flash it normally. This action is alternatively called "dirty flash". Then, reboot into your ROM. If your ROM is provided with an updater app, you can also use it to simplify the process.
Q: How about root in custom ROMs?
A: By norm, root comes with any custom ROMs that you wish to use. When you have successfully flashed a custom ROM, you don't need to do any additional steps in order to have root access. Exception goes for CM ROMs and some CM-based ones which does not ship SuperSU. You will need to enable root from within the Developer Options in Settings. To enable Developer Options, tap "Build Number" in "About Phone" 7 times.
Q: Can I somehow use stock ROM features on my current custom ROM?
A: No. The stock features on stock ROM is not portable, hence cannot be used freely on a custom ROM. You can however, find a specific port to an Xperia app / feature (e.g Xperia Keyboard) by searching for the port on XDA. Make sure that the port is compatible with the ROM you are currently running. The reliability of these ports are greatly dependant on the ROM version and type that you are running, so you may actually experience either problems or greatness when you are running these ports.
Q: I'd like to use another file system f2fs for my partitions (Advanced)
A: By default, all partitions on Android are formatted as ext4. This can be changed easily by using the TWRP recovery. Note that this is only for unlocked bootloaders only!
Please note that only data and cache could be formatted as f2fs. System partition cannot be formatted as such due to how ROM installations are block based. The steps are as follows:
Boot into TWRP recovery
Select Wipe
Select Advanced Wipe
Tick a single partition you wanted to change its filesystem
Select Partition Options button
Change file system
Select f2fs and proceed
Done
CAUTION! This will also cause data in internal storage to cease from existence as well
NOTE! A ROM may not support f2fs (rare occurrence). So it would always be best to prepare for the worst if you are not certain of a particular ROM supports f2fs or not
Suggestions?
If you have any suggestion that may improve these guides, do tell me about it. I would be happy to make it better
Uhm.. Nice but we don't need a lot of thread with the same instructions.
Doomlord has made a general thread in the Android Development and there was another thread with rooting and flashing and stuff..
mrjraider said:
Uhm.. Nice but we don't need a lot of thread with the same instructions.
Doomlord has made a general thread in the Android Development and there was another thread with rooting and flashing and stuff..
Click to expand...
Click to collapse
Well I tried my best to make it look like if its not a duplicate. It is really a shortcut through things, and yet the guide here in are actually my own way of doing stuff (inspiration from DoomLord's and other guys' tutorials) for example, DoomLord has a guide on unlocking bootloaders with adb command, while I use Flashtool itself to get it done. I see your point really, and I'm okay if this guide should be nominated for deletion (even if I woke up to deletion of this thread). The choice is in the mod's hand now. Thank you by the way
EDIT: Plus, searching is a pain. Links herein this thread are the ones I bookmarked when I was a really noob person back then. Thought of giving them newcomers a head start though. Later on, I am sure they will discover themselves new things, and started diverting from stuffs provided in this thread, to other things based on their choices.
I even wanted to put out links to other tutorials, but..... nevermind
A few questions
Hi sorry for hijacking the thread, I'm not sure if this is the right place to ask a few questions that has been bothering me for sometime. I have followed every step of the guide correctly and successfully installed CM 11 on my Xperia Sp, however there are certain things that I haven't quite understood ..sorry if they are noob questions
> What is the DoomLord kernal supposed to be? Is it same as installing CWM recovery? if yes ,then how can I flash a different recovery like TWRP?[/B]
> Is the kernal different for installing anything other than CM?
> If I am to go back to stock ROM for warranty purpose, should I remove the Kernal first? If yes then how?
Thanks in advance
murky94 said:
Hi sorry for hijacking the thread, I'm not sure if this is the right place to ask a few questions that has been bothering me for sometime. I have followed every step of the guide correctly and successfully installed CM 11 on my Xperia Sp, however there are certain things that I haven't quite understood ..sorry if they are noob questions
> What is the DoomLord kernal supposed to be? Is it same as installing CWM recovery? if yes ,then how can I flash a different recovery like TWRP?[/B]
> Is the kernal different for installing anything other than CM?
> If I am to go back to stock ROM for warranty purpose, should I remove the Kernal first? If yes then how?
Thanks in advance
Click to expand...
Click to collapse
No worries. Asking any questions are indeed welcomed in this thread
DoomLord kernel is a custom kernel. If based on my guide, the kernel mentioned contains CWM recovery with it therefore, making it easier to access recovery compared to traditional method.
Installing CM will wipe the kernel off. The (DoomLord's) kernel is created only for stock ROMs. Flashing such kernel on custom ROMs will usually cause soft brick.
Since DoomLord's kernel are gone during the flashing process of CM, no. But still, NO, flashing stock ROM will wipe the kernel as well and puts in the stock one.
If you requires elaboration, please say so. I would be glad to clarify :angel:
Thank you so much! I was quite worried thinking that I had made a wrong decision.
> so you are saying that custom ROMs use their own Kernels? If so then there are no prerequisites to installing custom kernels beforehand? I'm guessing that would brick the phone?
> If CM does wipe off the kernel then how is it that the recovery is still working? its meant to be the part of the DoomLords kernel right?
>Can I change my recovery now to a different one?
TechnoSparks said:
No worries. Asking any questions are indeed welcomed in this thread
DoomLord kernel is a custom kernel. If based on my guide, the kernel mentioned contains CWM recovery with it therefore, making it easier to access recovery compared to traditional method.
Installing CM will wipe the kernel off. The (DoomLord's) kernel is created only for stock ROMs. Flashing such kernel on custom ROMs will usually cause soft brick.
Since DoomLord's kernel are gone during the flashing process of CM, no. But still, NO, flashing stock ROM will wipe the kernel as well and puts in the stock one.
If you requires elaboration, please say so. I would be glad to clarify :angel:
Click to expand...
Click to collapse
Thank you so much! I was quite worried thinking that I had made a wrong decision.
> so you are saying that custom ROMs use their own Kernels? If so then there are no prerequisites to installing custom kernels beforehand? I'm guessing that would brick the phone?
> If CM does wipe off the kernel then how is it that the recovery is still working? its meant to be the part of the DoomLords kernel right?
>Can I change my recovery now to a different one?
murky94 said:
Thank you so much! I was quite worried thinking that I had made a wrong decision.
> so you are saying that custom ROMs use their own Kernels? If so then there are no prerequisites to installing custom kernels beforehand? I'm guessing that would brick the phone?
> If CM does wipe off the kernel then how is it that the recovery is still working? its meant to be the part of the DoomLords kernel right?
>Can I change my recovery now to a different one?
Click to expand...
Click to collapse
Usually yes. Yes. No, as by the time you flashes the custom ROM zip (in which there is a boot.img file within it), it overwrites the old kernel, so no bricks.
I am not sure as of correct answer, but in my point of view the recovery is loaded into your RAM. When you flash a custom ROM, the recovery files are indeed gone (with the kernel) but the recovery still working as it is residing in your RAM (I still could be wrong though). Once you restart, the recovery you used will be gone but you are still able to access recovery in which were included in the newer kernel.
Yes indeed.
Sorry for the late reply, I am quite busy these days, so my online frequency is not like before.
TechnoSparks said:
Usually yes. Yes. No, as by the time you flashes the custom ROM zip (in which there is a boot.img file within it), it overwrites the old kernel, so no bricks.
I am not sure as of correct answer, but in my point of view the recovery is loaded into your RAM. When you flash a custom ROM, the recovery files are indeed gone (with the kernel) but the recovery still working as it is residing in your RAM (I still could be wrong though). Once you restart, the recovery you used will be gone but you are still able to access recovery in which were included in the newer kernel.
Yes indeed.
Sorry for the late reply, I am quite busy these days, so my online frequency is not like before.
Click to expand...
Click to collapse
Hey sorry for bothering again, but I have noticed that after installing CM11 my RAM memory is only 839MB, can you explain why? Is it because of the recovery which you mentioned above? And if I flash another recovery, will the issue be solved?
murky94 said:
Hey sorry for bothering again, but I have noticed that after installing CM11 my RAM memory is only 839MB, can you explain why? Is it because of the recovery which you mentioned above? And if I flash another recovery, will the issue be solved?
Click to expand...
Click to collapse
I am guessing that you have many apps running in the background. May please share a screenshot?
technosparks said:
i am guessing that you have many apps running in the background. May please share a screenshot?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
murky94 said:
View attachment 3081260
View attachment 3081261
Click to expand...
Click to collapse
OOoooO! For your information, our available RAM for user is indeed 839MB+. I thought you were talking about RAM usage.
TechnoSparks said:
OOoooO! For your information, our available RAM for user is indeed 839MB+. I thought you were talking about RAM usage.
Click to expand...
Click to collapse
Ohh I see thanks again for your time
---------- Post added at 04:47 PM ---------- Previous post was at 04:43 PM ----------
murky94 said:
Ohh I see thanks again for your time
Click to expand...
Click to collapse
By the way, have you ever experienced lag with custom launchers? I have been trying to use a different launcher but there is always a certain seconds of lag when I press the home and background keys and this stays on until I uninstall the launcher itself!
murky94 said:
Ohh I see thanks again for your time
---------- Post added at 04:47 PM ---------- Previous post was at 04:43 PM ----------
By the way, have you ever experienced lag with custom launchers? I have been trying to use a different launcher but there is always a certain seconds of lag when I press the home and background keys and this stays on until I uninstall the launcher itself!
Click to expand...
Click to collapse
No problem mate!
Actually no (or maybe I am used to it). I am using only Nova launcher.
there may be two problems. If your launcher redraws, it seemed that you are using a lot of your RAM.
If your launcher loads okay, then based on community posts, if you have multiple launchers I suggest freezing all of them unused one. You can use Titanium Backup to freeze those other launchers. Alternatively you may use a custom kernel to banish this lag as people claims it came from the default CM kernel.
---
By the way, may I know which method do you used in my tutorial?
TechnoSparks said:
No problem mate!
Actually no (or maybe I am used to it). I am using only Nova launcher.
there may be two problems. If your launcher redraws, it seemed that you are using a lot of your RAM.
If your launcher loads okay, then based on community posts, if you have multiple launchers I suggest freezing all of them unused one. You can use Titanium Backup to freeze those other launchers. Alternatively you may use a custom kernel to banish this lag as people claims it came from the default CM kernel.
---
By the way, may I know which method do you used in my tutorial?
Click to expand...
Click to collapse
Thank you for all your help, I have followed your entire guide.
murky94 said:
Thank you for all your help, I have followed your entire guide.
Click to expand...
Click to collapse
Yes I may aware of that. But may I know which method did you used, 1a, 1b, or 1c?
TechnoSparks said:
Yes I may aware of that. But may I know which method did you used, 1a, 1b, or 1c?
Click to expand...
Click to collapse
I have used 1(b) followed by the rest
murky94 said:
I have used 1(b) followed by the rest
Click to expand...
Click to collapse
I think I may have solved my lag problem, I repeated the whole process, flashed the stock ROM first which restored my stock kernel/recovery and after that I flashed CM11, but without the DoomLord's kernel.
As a token of appreciation to this great device and it being slowly dying, I have again updated this guide to conform with latest changes. I had also verbosely explain some aspects of the things in the guide. Additionally, I also tried to provide better readability of the guide so that readers don't confused with numbers and alphabets eg, 1a is now 1(a).
This guide is pretty useful for new Xperia SP users in my honest (and maybe selfish ) opinion. I hope it benefits new users or old users as well.
Also, I am quite sad that my Xperia SP screen is damaged. This is due to a motorcycle accident that I confront with yesterday. The screen is not cracked, yay to Gorilla glass, but the screen isn't showing any colour. I don't know when will I have the money to fix it.
/monologue off
Ok, thanks.
I had unlocked the bootloader, rooted & installed the Cyanogenmod unofficial 12.1 build for ASUS Zenfone 2.
But, I realized I have a problem with the battery connector, and ASUS will be providing me with a replacement. But, the warranty will be void as I have unlocked, rooted & uninstalled the stock ROM.
Need help on going back to the factory settings.
flashing back asus rom is simple, unroot is simple, to dis-unlock your bootloader is.... :/
Yeah, easy to flash everything back to stock unrooted, but there is currently no way to lock the bootloader once unlocked. Best you can do is flash the original black splash screen so it is not immediately obvious it is unlocked and hope they don't check the bootloader.
send it back and pray it won't be detected as boot unlock. OR you wait till the official unlocking is out then send it back.
sooty84 said:
send it back and pray it won't be detected as boot unlock. OR you wait till the official unlocking is out then send it back.
Click to expand...
Click to collapse
official unlocking will likely report back to ASUS and will be on a warranty-voiding basis anyway.
Physical faults aren't voided by unlocking the bootloader anyway.
If it's a hardware connection issue, that's a factory defect, not a software-induced fault.
Just throw a stock ROM on it and don't worry about the bootloader.
Thanks sooty, kanagawaben, harfainx. Will do as suggested - flash the original black screen, unroot & install stock rom.
i read into the bootloader unlocking method and saw this line
getprop ro.isn > /factory/asuskey
i'm not a modder but this line trigger ro.isn to store in /factory/asuskey
so my question would be what was in asuskey previously. and if this was the file that open bootloader.
hence, it require a phone that was not unlock to go into terminal and do this
su
cd /
mkdir backupfile
find / -type f -name asuskey
find / -type f -name ro.isn
cat PATH/asuskey > /backupfile/asuskey
cat PATH/ro.isn > /backupfile/ro.isn
exit
go to your file manager and port the 2 files out from /backupfile
lets compare these with our unlock bootloader files.
i'm hoping it is this simple, because the command is only 1 liner and seem nothing much else it does except copying ro.isn to /factory/asuskey
When you want to flash back to stock from custom, are the steps the following?
1)Download stock rom from asus
2)Format phone
3)Flash stock ROM from custom recovery?
The reason I ask is because there is a guide that says you need to edit the stock rom when flashing from custom rom/recovery.. Link to his guide here: GUIDE FOR FULL ROM
Gave it a try and was able to flash to stock from twrp recovery without any issues. (though the TWRP recovery remained w/ the bootloader unlocked)
htc_softbank said:
Gave it a try and was able to flash to stock from twrp recovery without any issues. (though the TWRP recovery remained w/ the bootloader unlocked)
Click to expand...
Click to collapse
so which method did u try exactly ? did u flash it directly via twrp without changing anything in the zip file ? or did u use the method explained in the link that u have mentioned ?
I'm interested in this myself...I'll be selling my phone soon, and I want to get it back to stock
If your in europe, there is a law that its not ilegal to change your software as long dont damage any hardware
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
Its a european union law and they cant just ignore that
follow this bro
http://w*w.asus-zenfone.com/2015/12/how-to-re-lock-bootloader-asus-zenfone-2.html
I success with that method
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
I can root my p9 lite with Nougat? Thanks
Tommy28_ITA said:
I can root my p9 lite with Nougat? Thanks
Click to expand...
Click to collapse
Hello dude,
it's quite similar to...
"Can i eat spaghetti and pomodoro" at dinner?
Of course you can, just make sure after install TWRP
you do a full backup of stock ROM before preceed rooting.
Happy flash.
P.S.: the question is legitimate, but it would make sense if nougat had come out lately...
Regards
Dadditz said:
Hello dude,
it's quite similar to...
"Can i eat spaghetti and pomodoro" at dinner?
Of course you can, just make sure after install TWRP
you do a full backup of stock ROM before preceed rooting.
Happy flash.
P.S.: the question is legitimate, but it would make sense if nougat had come out lately...
Regards
Click to expand...
Click to collapse
Thanks, can you describe a software for a total backup? After backup, I need to unlock the bootloader and then I can flash the TWRP with fastboot?? Can you make a guide for all? Thanks for all
Hi, I just came home from work ..
What model of device do you have? Is it a VENUS (VNS) or a PRAGUE (PRA) one?
Write here complete firmware you have..
Later I reconnect, now I have to go ..
For apps, search the internet for the ones you need to backup, you can also use your huawei backup apps...
the rest as files or music, photos, videos, copy them on your computer ..
There are apps on the store to backup phone calls, text messages, etc., just search ..
When you feel relaxed about copying all your important things on your computer,
go to step 2, ie unlocking the bootloader, custom recovery flash, and so on ...
What is very important is to read more than one time GUIDES you need to follow...
Always one thing at a time
Dadditz said:
Hello dude,
it's quite similar to...
"Can i eat spaghetti and pomodoro" at dinner?
Of course you can, just make sure after install TWRP
you do a full backup of stock ROM before preceed rooting.
Happy flash.
P.S.: the question is legitimate, but it would make sense if nougat had come out lately...
Regards
Click to expand...
Click to collapse
My firmware is VNS-L31C432B407
Tommy28_ITA said:
My firmware is VNS-L31C432B407
Click to expand...
Click to collapse
Hey Tommy,
you have the same phone as mine... L31 single sim..
Well, do you already have your bootloader unlock number ? If yes you can proceed, if not.... well... we will talk anymore...
About "how to", yes you can use commands with fastboot or use k1ll3r8e's toolkit that makes all things you need, including:
another huawei backup via hisuite, unlock BT, download and flash custom recovery (TWRP), root ie HOW TO..
So download all files and copy SU to your SD card:
@k1ll3r8e toolkit and install on PC;
@OldDroid TWRP and put wherever you want (on your PC);
Official SuperSU 2.82;
A very IMPORTANT thing is before connect phone to PC enable/disable things as showed in THIS screenshot !!!
Then open toolkit, go in bootloader TAB and install hisuite drivers on PC.
When you ready dude, quote here, will replay ASAP ..
Peace :angel:
Dadditz said:
Hey Tommy,
you have the same phone as mine... L31 single sim..
Well, do you already have your bootloader unlock number ? If yes you can proceed, if not.... well... we will talk anymore...
About "how to", yes you can use commands with fastboot or use k1ll3r8e's toolkit that makes all things you need, including:
another huawei backup via hisuite, unlock BT, download and flash custom recovery (TWRP), root ie HOW TO..
So download all files and copy SU to your SD card:
@k1ll3r8etoolkit and install on PC;
@OldDroidTWRP and put wherever you want (on your PC);
Official SuperSU 2.82;
A very IMPORTANT thing is before connect phone to PC enable/disable things as showed in THIS screenshot !!!
Then open toolkit, go in bootloader TAB and install hisuite drivers on PC.
When you ready dude, quote here, will replay ASAP ..
Peace :angel:
Click to expand...
Click to collapse
I've already the bootloader code, I enable oem unlock and debug usb, but the setting lock screen is disable and I cant disable it. How can I make?
Now im going to school and I will download the files at home. Thanks
Tommy28_ITA said:
I've already the bootloader code, I enable oem unlock and debug usb, but the setting lock screen is disable and I cant disable it. How can I make?
Now im going to school and I will download the files at home. Thanks
Click to expand...
Click to collapse
Ok, i've already download all files, now what do i do?
@Tommy28_ITA
Hi, you can do what you want with your phone, you can choose what you planned to do my friend or do nothing....
In your previous post you wrote about lock screen you can't disable... investigate about this, could be very important. What you do with your phone is at your onw responsibility, you know.. just adviced....
In post number #3 you wrote:
"I need to unlock the bootloader and then I can flash the TWRP with fastboot??",
and in post #6 i wrote: "About "how to", yes you can use commands with fastboot or use k1ll3r8e's toolkit that makes all things you need, including:
another huawei backup via hisuite, unlock BT, download and flash custom recovery (TWRP), root ie HOW TO..".
So choose your method, fastboot or toolkit, or a guide HERE in @dariomrk's thread that use Magisk...
For fastboot search and download here on XDA, for toolkit i already posted you the link to the main thread, Search in each thread you will find the HOW TO section.
Just follow guides, use search, ask users/dev for helps...
If something goes wrong don't point your finger at me...
Where i'm wrong other members feels free to correct me whenever they want... thank you guys.
Good luck !!
P.S.: Some basic knowledge needed to root your phone, so if you think you don't have, just give up, sorry but necessary i write this.
Dadditz said:
@Tommy28_ITA
Hi, you can do what you want with your phone, you can choose what you planned to do my friend or do nothing....
In your previous post you wrote about lock screen you can't disable... investigate about this, could be very important. What you do with your phone is at your onw responsibility, you know.. just adviced....
In post number #3 you wrote:
"I need to unlock the bootloader and then I can flash the TWRP with fastboot??",
and in post #6 i wrote: "About "how to", yes you can use commands with fastboot or use k1ll3r8e's toolkit that makes all things you need, including:
another huawei backup via hisuite, unlock BT, download and flash custom recovery (TWRP), root ie HOW TO..".
So choose your method, fastboot or toolkit, or a guide HERE in @dariomrk's thread that use Magisk...
For fastboot search and download here on XDA, for toolkit i already posted you the link to the main thread, Search in each thread you will find the HOW TO section.
Just follow guides, use search, ask users/dev for helps...
If something goes wrong don't point your finger at me...
Where i'm wrong other members feels free to correct me whenever they want... thank you guys.
Good luck !!
P.S.: Some basic knowledge needed to root your phone, so if you think you don't have, just give up, sorry but necessary i write this.
Click to expand...
Click to collapse
Ok, I've unlock the bootloader with Minimal Adb and Fastboot, now I want install TWRP with the tools and next I'm going to flash SuperSu, this is my plan. And remember guys, MAKE A BACKUP, ITS VERY IMPORTANT
Dadditz said:
@Tommy28_ITA
Hi, you can do what you want with your phone, you can choose what you planned to do my friend or do nothing....
In your previous post you wrote about lock screen you can't disable... investigate about this, could be very important. What you do with your phone is at your onw responsibility, you know.. just adviced....
In post number #3 you wrote:
"I need to unlock the bootloader and then I can flash the TWRP with fastboot??",
and in post #6 i wrote: "About "how to", yes you can use commands with fastboot or use k1ll3r8e's toolkit that makes all things you need, including:
another huawei backup via hisuite, unlock BT, download and flash custom recovery (TWRP), root ie HOW TO..".
So choose your method, fastboot or toolkit, or a guide HERE in @dariomrk's thread that use Magisk...
For fastboot search and download here on XDA, for toolkit i already posted you the link to the main thread, Search in each thread you will find the HOW TO section.
Just follow guides, use search, ask users/dev for helps...
If something goes wrong don't point your finger at me...
Where i'm wrong other members feels free to correct me whenever they want... thank you guys.
Good luck !!
P.S.: Some basic knowledge needed to root your phone, so if you think you don't have, just give up, sorry but necessary i write this.
Click to expand...
Click to collapse
Do u know a tool for flash the custom recovery? Because I searched and I found this, always by @k1ll3r8e https://forum.xda-developers.com/devdb/project/?id=16538#downloads
I can use this?
Tommy28_ITA said:
Do u know a tool for flash the custom recovery? Because I searched and I found this, always by @k1ll3r8e https://forum.xda-developers.com/devdb/project/?id=16538#downloads
I can use this?
Click to expand...
Click to collapse
Hi, yes download latest version 14/08/2017
and install on pc...then
READ a couple of time...
1. ACCEPT terms of use,
2. Go in BOOTLOADER Preparation TAB and make sure you enableb USB-Debugging and OEM-Unlock,
3. Install HiSuite and follow what wrote here..
4.Go in Recovery TAB/Individual, tap on three point and choose OldDroid's recovery you downloaded on your PC.
5. FLASH recovery.
6. When finished tap on Reboot Recovery and disconnect phone from PC. If all gone well will reboot to recovery....
7. Once booted make a NANDROID backup, (use search if you don't know what talking about).
8. Go back to main menu, you're ready, now, to flash SuperSU.zip file you have on SD card...
9. At the end reboot system...done..
10. Enjoy.
Don't forget to thank the respective developers apps..
Best regards
Dadditz said:
Hi, yes download latest version 14/08/2017
and install on pc...then
READ a couple of time...
1. ACCEPT terms of use,
2. Go in BOOTLOADER Preparation TAB and make sure you enableb USB-Debugging and OEM-Unlock,
3. Install HiSuite and follow what wrote here..
4.Go in Recovery TAB/Individual, tap on three point and choose OldDroid's recovery you downloaded on your PC.
5. FLASH recovery.
6. When finished tap on Reboot Recovery and disconnect phone from PC. If all gone well will reboot to recovery....
7. Once booted make a NANDROID backup, (use search if you don't know what talking about).
8. Go back to main menu, you're ready, now, to flash SuperSU.zip file you have on SD card...
9. At the end reboot system...done..
10. Enjoy.
Don't forget to thank the respective developers apps..
Best regards
Click to expand...
Click to collapse
Thanks, now my phone is rooted
View attachment 4499485
Thanks, now my phone is rooted
Dear friends,
I'm a bit tired of custom roms and I have installed the last official b12 (the one from this week)
now, I would like also to remove twrp in order to remove the message that appears when restarting (the one that says is not official, wait 5 seconds...)
Can you please advise on which boot should I install?
Thanks a lot!!!!
Anyone?
julioforo said:
Dear friends,
I'm a bit tired of custom roms and I have installed the last official b12 (the one from this week)
now, I would like also to remove twrp in order to remove the message that appears when restarting (the one that says is not official, wait 5 seconds...)
Can you please advise on which boot should I install?
Thanks a lot!!!!
Click to expand...
Click to collapse
how did you install b12? if you do it in edl,twrp should be removed.And the warning is ther because your bootloader is unlocked.Lock your bootloader again and the screen/message is gone.I cant help with locking bootloader,i dont recommend it
Or keep TWRP and unlocked bootloader and install NFound patch (modified aboot) to remove warning.
julioforo said:
Dear friends,
I'm a bit tired of custom roms and I have installed the last official b12 (the one from this week)
now, I would like also to remove twrp in order to remove the message that appears when restarting (the one that says is not official, wait 5 seconds...)
Can you please advise on which boot should I install?
Thanks a lot!!!!
Click to expand...
Click to collapse
just leave twrp as-is and use one of the "remove inscription" zips. You should use Raystef66's zip.
unclear what "boot" has to do with this, but FYI the kernel doesn't really change this at all.
Don't relock the bootloader, it's just plain stupid. If you NEED OTA updates then you can extract the recovery.img from one of the stock ROMs (provided that you already are on stock ofc) and TWRP - Install - Install image - Recovery. The bootloader doesn't need to be locked for anything really, hell they don't even check it if you send it in for repairs lol
Choose an username... said:
just leave twrp as-is and use one of the "remove inscription" zips. You should use Raystef66's zip.
unclear what "boot" has to do with this, but FYI the kernel doesn't really change this at all.
Don't relock the bootloader, it's just plain stupid. If you NEED OTA updates then you can extract the recovery.img from one of the stock ROMs (provided that you already are on stock ofc) and TWRP - Install - Install image - Recovery. The bootloader doesn't need to be locked for anything really, hell they don't even check it if you send it in for repairs lol
Click to expand...
Click to collapse
Thanks a lot my friend.
i'm just reading the whole post and I'm not sure if I should use the zip.
I have the android bootloader, not TWRP and I'm on the B12 stock ROM from this week.
Shoud I?
I tried also the method with ADB but it says permission denied!...
Sorry for so many question.
Also I have to say that in my setting says that my phone is encrypted...
So I guess NFOUND option is not valid as per his warnings
julioforo said:
Also I have to say that in my setting says that my phone is encrypted...
So I guess NFOUND option is not valid as per his warnings
Click to expand...
Click to collapse
never use nfound's way. it's russian roulette all the way
---------- Post added at 04:30 PM ---------- Previous post was at 04:27 PM ----------
julioforo said:
Thanks a lot my friend.
i'm just reading the whole post and I'm not sure if I should use the zip.
I have the android bootloader, not TWRP and I'm on the B12 stock ROM from this week.
Shoud I?
I tried also the method with ADB but it says permission denied!...
Sorry for so many question.
Click to expand...
Click to collapse
you mean fastboot? Then what do you have as recovery? Stock MiFavor recovery?
Get TWRP and flash raystef's stuff, then also do what i said and flash the stock recovery (first flash the remove inscription zip, then test if it worked, THEN install stock mifavor recovery)