Help Rooting N4 4.3 - Nexus 4 Q&A, Help & Troubleshooting

Hello community
I am able to get as far as unlocking the bootloader but I'm not sure as what to do next. I am on a fresh clean 4.3 stock upgrade Can some one suggest the best rooting method and possibly a very good ROM and kernel for this device please...

jgentry151 said:
Hello community
I am able to get as far as unlocking the bootloader but I'm not sure as what to do next. I am on a fresh clean 4.3 stock upgrade Can some one suggest the best rooting method and possibly a very good ROM and kernel for this device please...
Click to expand...
Click to collapse
I recommend backing up your data before making any changes then follow the Nexus 4 Root Guide at http://forum.xda-developers.com/showthread.php?t=2266654 to install your preferred recovery utility, either Clockworkmod or TWRP.
If you plan to install a custom ROM and kernel anyway, there really isn't much point in gaining root on the stock 4.3 ROM. If you must gain root on the stock 4.3 ROM, you will need to download Chainfire's experimental SuperSU v1.41 (available at http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip) and transfer the file to the root folder of the Nexus internal storage. Start your phone's bootloader by powering down the Nexus and simultaneously holding the volume down and power buttons approximately 5 seconds until the bootloader screen appears. Next use the volume up/volume down buttons to highlight Recovery and press the power button to start the custom recovery. In recovery press Install, then highlight the file SuperSU-JWR66N-S005-130625-1.41.zip and move the button slider to the right to install root. Reboot the phone and update SuperSU from the Play Store.
There is a wide selection of custom ROMs and kernels available in Nexus 4 Android Development and Nexus 4 Original Android Development. Every custom ROM already includes a kernel, so you only need to download and flash a kernel if you need specific features inlcuded in the custom kernel. I recommend taking some time to review the ROMs listed in these two forums, look at the screen shots, and read some of the user comments regarding the ROMs that look appealing to you. Once you identify the ROM(s) you would like to try, download the ROM(s) and tranfer the zip file to the root folder of the Nexus internal storage.
Before flashing any ROM make sure your battery is charged at least 50%, then boot into recovery and make a nandroid backup of your existing setup. Next wipe data, cache, and Dalvik cache and install the custom ROM from the associated zip file. Bear in mind that the first boot after flashing a new ROM will take a few (5 to 10) minutes. After booting the phone configure your Google account, update your Play Store apps, and configure the phone settings to suit your preference then reboot your phone. Be patient: Try out the new ROM for a couple of days before making a decision to move to a different ROM.

Related

[HOWTO] Update to 4.0.3 OTA ICS from any version with Root access (For I9020T/I9020A)

Okay First of all download the following files
a)http://android.clients.google.com/packages/ota/google_crespo/VQ8PQk_V.zip (4.0.3 OTA)
b)http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip (2.3.6 Official I9020T Build)
c)http://bit.ly/su2361ef (SU flashable)
d)http://forum.xda-developers.com/showthread.php?t=988686 (Grab recovery form this thread)
e)http://developer.android.com/sdk/index.html (Grab the android SDK installer)
f)http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429 (Radio file only required for I9020A)
Okay so when done with all that proceed as follows
1) Backup your current apps using Titanium Backup (Optional/Recommended)
2) Backup(Nandroid) your rom using backup option in CWM (Optional/Recommended)
3) Do a full wipe, wipe sdcard, system, data, cache Transfer a,b,c,f to your phone.
4) Flash the 2.3.6 Official I9020T Build you had downloaded using the install zip option in CWM (IMP-DO NOT REBOOT RIGHT NOW)
5) Flash the flashable SU file you had downloaded and then reboot.
6) Once your phone is on, continue to set up your account or skip it as you wish. (Optional)
7) Open up market, download the latest SU app, Voodoo OTARootKeeper, Titanium Backup and any other app you use that requires root.
8) Open the updated SU app, hit menu button and click preferences, go all the way down, click on su binary(tap to check for updates) , and make sure it updates to v3.0.3
9) After that is done, open and allow root permissions to all your root apps. (This is important)
9.5) Run Voodoo OTARootKeeper and click on protect root, make sure all options get checked.
10) Turn off phone, keep volume up and power pressed to boot into fastboot.
11) Select recovery with volume buttons and use power to launch.
12) Once you see a android bot image and an arrow image, keep volume up pressed and press power once, then you'll see some options appear.
13) Select apply update option and find the official 4.0.3 OTA file you had downloaded and flash. Reboot.
14) Once you have booted into ICS, go to Voodoo OTARootKeeper and select resture Root, all options should now be ticked, if not something went wrong.
15) Voila, you have root. Now to get back CWM recovery you can follow this -
i) Place the recovery img file in the android sdk platform-tools folder
ii) Switch to the directory where you unzipped the Android SDK & go to "tools"
iii) Then type "fastboot flash recovery yourfilename.img" & hit enter
iv) That should do it.
v) Optionally you may do it form Rom Manager too, if it works.
16) (ONLY FOR I9020A) Reboot phone, turn it off, boot into fastboot, select recovery, CWM should launch, flash the radio file you had downloaded to get radio working on I9020A (ONLY FOR I9020A)
Root only works for the apps that were installed while on 2.3.6
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip , use this root file, flash it in cwm, everything works, permissions etc.
This might work for other variants, tested on I9020A and I9020T, I take no responsibility for anything that might go wrong with your device. I take no credit for any links or procedures provided in this guide, I just tested and compiled.
Thanks and best of luck.
..........
Good guide but first two links are broken.
bajansurfer said:
Good guide but first two links are broken.
Click to expand...
Click to collapse
Thanks, fixed.
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
poging22 said:
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
Click to expand...
Click to collapse
Might not work, though you can try, if it fails, do it my way, also its impossible to get any kind of root that way.
Link for the ATT Radio doesnt seem to be working
Great work!
wipe SD card?
Is this necessary?
I don't think it's necessary to wipe the SD card, I followed the procedure in http://forum.xda-developers.com/showthread.php?t=1396913 and although it said my SD card would be wiped, everything was still there after I was done!
Anyone on a i9023 tried this?
Hmm...does "any version" includes M200(Korean Nexus S)?
Sent from my Nexus S using Tapatalk
http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429
I think he meant that for the 9020A radio
Link fixed, sorry for that, SD wiping might not be necessary, but I suggest as it makes it cleaner. Might work for I9023 and M200, I have no clue, maybe some experienced developer can answer that better.
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
little hiccup at step 12. im getting the android bot with exclamation mark but i press volume up with power and nothing happens. menu doesnt show up....
Edit: NVM... i pressed it 3 or 4 times and it finally worked
Michie23 said:
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
Click to expand...
Click to collapse
You should post it in questions, I cannot answer this.
fromthestars said:
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Click to expand...
Click to collapse
Many ways of doing it, I just am suggesting one, the flashable zip for ics isn't available as yet, what did you flash?
i9020 keeps getting status 7 aborted and my padlock is still unlocked on t-mobile 2.3.6
Has any tried this on an i9023? Thank u
Sent from my Nexus S using xda premium

[GUIDE] Flash Custom ROMs for the Xperia SP

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.

[guide] developer edition note 4 wikipedia/how to/everything to know

Here is my Note 4 Guide. I did one for the note 3 so figured i will throw one up for note 4 so it might look familiar to it! Sorry this one is a little late but here it is!
I TAKE NO CREDIT I AM NO DEVELOPER! THIS IS MERELY A GUIDE!!
UNDERSTAND ROOT/RECOVERY WILL VOID YOUR WARRANTY
Part 1: Flashing TWRP onto Developer Note 3
Step 1- Download and install Odin onto Windows PC http://uploaded.net/file/o2xcp01n
Step 2- Download Verzion TWRP Tar File (openrecovery-twrp-2.8.1.1-trltevzw.img.tar) http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.1.1-trltevzw.img.tar
Step 3- Flash your Verizon TWRP Tar File your just downloaded in Odin under the AP Slot ONLY!
BE CAREFUL IF YOU PLACE IN WRONG SLOT DEVICE WILL BE A BRICK!
Side note phone will now say Set Warranty Bit: Recovery when booting into recovery. Don't worry this is normal. This is showing you what tripped warranty. More about this below later in guide.
Step 4- Flash Superuser if TWRP doesn't ask you to root http://download.chainfire.eu/589/Sup...erSU-v2.16.zip
Step 5- Make a complete backup of EVERYTHING in TWRP. Boot, Recovery, System, Data, Cache ALL OF THEM I have backed up to internal sdcard & external sdcard & even throw a backup on your pc just in case something catastrophic happens since we have no Odin stock files still!
Step 6- (optional) Flash a rom/kernel.
Rom Section: Only one stock rooted, deodexed, Knox-Free rom so far
Thanks @EMSpilot!!
http://forum.xda-developers.com/not...rom-stock-root-odex-deodex-knox-free-t2949569
Kernel Section: While there is no verizon specific kernels there are ones that will work. I have flashed ktoonsez's kernel over in the T-Mobile side of things and it does work. Haven't been on long but it will flash. I am testing now how much better it is then stock. Always have your boot.img ready to go and/or your stock backup in TWRP ready to restore the boot if required. Some other carrier kernels will not play nice with it but from what i have expereienced with Note 4 so far and the Note 3 T-Mobile kernels will work without any hassle. So continue to check back here for updates!
Thanks @ktoonsez!
http://forum.xda-developers.com/not...lopment/kernel-kt-note4-nih-ktweaker-t2936809
Step 7- Enjoy!
Part 2: Restoring Boot.img if phone will not boot after rom or kernel install
If you get a kernel that won't run properly or boot loop or a rom that will not boot on the developer edition without proper boot.img here is how you fix.
Step 1- Boot into TWRP. From phone being off use three finger method of vol up, power and home button to boot into TWRP.
Step 2- Restore boot.img from the very important backup in step 5 from part one! This is why you have to have a backup of everything! Restore the boot.img only and reboot!
Step 3- Back to enjoy!!
I do not take any credit for roms/kernel/recovery just sharing links and what I have done. Hope this guide helps!! Please continue to check back here for updates on roms/kernels or other helpful Developer Edition info!
Thanks for the instructions!
After your suggestion I also flashed KToonez kernel and it makes the phone a WHOLE lot snapier. The only issue is that sometime it'll randomly go into a boot-loop. I was wondering if you also had encountered this.
There's other kernels from t-mobile development which work on the DE, such as the N4 Kernel from Echo Rom. I'm running that and it's the smoothest my device has ever been.
keithce said:
Thanks for the instructions!
After your suggestion I also flashed KToonez kernel and it makes the phone a WHOLE lot snapier. The only issue is that sometime it'll randomly go into a boot-loop. I was wondering if you also had encountered this.
Click to expand...
Click to collapse
yes it does and oh i havent experienced that. i actually flashed stock kernel again to get a good baseline for battery life and such for a week or so before i start going off the deep end with kernels! haha what settings did you change?
bobbarker2 said:
There's other kernels from t-mobile development which work on the DE, such as the N4 Kernel from Echo Rom. I'm running that and it's the smoothest my device has ever been.
Click to expand...
Click to collapse
there wasnt when i looked but i will have to check them out! any special settings you are using!?

Starting the root, recovery and custom ROM procedure from KitKat (D80220d-HKG-XX)

I've read pretty much every source I can find on getting a custom ROM up on my LG G2, which I haven't even rooted in the past 2 and a half years. My warranty ran out a while back and I'm getting a bit bored with stock now, and I want to start flashing, but the last time I did this was with my old HTC Desire HD.
As you can see I'm on 20d on my LG G2. It's a Hong Kong version for some reason, lol. What I considered doing was the following: update to the latest Lollipop official ROM using the LG Flash Tool (it gives me an available update to 30d); root using the rooting app, install a recovery with AutoRec Lollipop, flash a thermal recovery from the installed recovery (very scared of my phone overheating, I'm even considering putting it on a large, fast-running fan while doing anything, read too much about the phone overheating and making the screen yellow); back up my phone's IMEI data; use the recovery to install a brand new (I'm hoping a Marshmallow) ROM. I also understood that I need to flash a bootstack to change my bootloader to a KitKat, because it can be "fooled" using the BUMP thing. Is that correct? Do I even have to update my phone to Lollipop in this case? Also, how likely is it to overheat while doing all of these procedures?
Thanks in advance!
Sorry for the necroing my old thread, but I have yet to do anything with my phone. I am also still on KK. I saw that I can start rooting and install TWRP from it straight away. After that I need to flash a bootstack, right? How likely is it that I can brick myself? By that I mean what could get mixed up to get a brick while flashing. Also, has anyone had overheating issues while doing root, recovery installation and flashing things (newer TWRP, bootstacks, new ROM)?
Hi, i can understand your situation as i was in same till today, g2 with stock kitkat.
i finally installed cm13 after rooting it and the phone feels fresh.
you have understood most things right and ready now.
you dont need to upgrade to lollipop if youdont want to, you can start from kitkat itself.
few things i can tell you to begin here,
Root your G2,
for kitkat i found few good methods. Either do it via ioRoot using pc. or you can use towelroot or kingoroot apps to do it from phone itself. I used kingoroot since i didnt have a system with me. You can find these apps by searching at google, jst tyoe kingoroot. At first i was skeptical but it worked nice.
after root, you download autorec app, this is to install a custom recovery(twrp) for kitkat. you just have to install the app and run it and press install recovery/twrp and it'll do the rest.
after you have twrp installed, you need to upgrade it to latest version. For that download blastgator's twrp for your model and flash it through your recovery.
oh and dont forget to learn, how to enter into recovery yourself, since each G2 model has different method.
once you have these things you can start flahing roms. Most of the instructions on how to flash certain rom with what bootloader and bootstack etc. is written in its own thread, so you can learn that from that rom's thread that you will flash.
but basically, you need kk bootloader and lp bootstack for cm13 and above. usually both these things come in one zip. (if not you check for hybrid bootstacks)
Just make sure you are downloading things For your Model, if you try to flash different models stuff into yours, itll brick.
The autorec app, blastgator's twrp and ioroot can be found in a sticky thread in G2 general section, along with many other files and guides in that thread, theres complete index in that thread of all thing for all g2 models .
here : http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
also usually the phone doesnt heat up while flashing, just make sure your battery is more than 80% before you start and itll be ok. Even if it does a little, after a custom rom itll be fixed. I suggest you try cm13 for starters as your first custom rom.
hope this helps you :good:
Good Luck ::highfive:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
hitmancho said:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
Click to expand...
Click to collapse
to upgrade from kitkat you need lp or hybrid bootstacks. they have images (. img files) that are needed for your phone to function properly., like aboot, modem, radios etc. Hybrid bootstack contains aboot from kk and everyhing else from Lp. So when youll flash a bootstack, youll need to wipe everything, except internal storage(or external if you have one) , before you can flash it. that wipe will include, cache, dalvik cache, system, data. so basically all the old system stuff will be gone before you can flash this bootstack. i hope after reading that youll know that you cant access your old kk installation since itll be wiped, therell be nothing to boot to. if youll try, it will give you errors on lg logo.
understand it like this, to install new 21 inches tyres to your car, you need to upgrade the rims to hold a 21 inch tyre right? what will happen if you just put the 21' tyres on old 15' rim or old 15' tyres on new 21' rims?
the cm 13 devs dont recommend you to flash bootstacks because most of the models took the official lollipop update, which put everything in their phone to lolipop level. since there is no official marshmallow(MM) bootstack for our phone (because no official update), everyone developed ways to utilize lollipop bootstack to function on a custom MM Rom. Since most models are already on lollipop, theres no need to flash lollipop bootstack while flashing custom rom. That step is mostly for those who are still on stock or custom kitkat based rom. So they say to get official lollipop through kdz method, instead of flashing Lp bootstack before gettig their rom. But remember if a rom developer asks to install a bootstack for their rom, you should consider it if you dont have much knowledge about it, cause if you dont follow instructions, you can soft brick, in that case youll need hybrid bootstack.
see if you are using everyhing proper for your phone then your phone wont brick. only thing that can go wrong with that condition is your execution, your steps. As long as you dont make a mistake in these steps everything will go fine.
ill explain it what you should do.
1. first root your phone.
2. when done rooting, install "root checker" from google play. itll confirm if you have root or not.
3.Then you come back here and find autorec app from the link i gave you in my previous reply. download that, install the autorec app. and follow on screen instructions and itll install twrp recovery for you.
4. then come back here again, and find blastgator's twrp, from the same link in previous post. itll be the one whih says "twrp with f2fs". download it and remember where you put it.
5. turn off phone, boot into recovery (i hope you've learned by now how to get into recovery of your g2 model). Now youll be in recovery, hit install button there and find where you put that file, flash it, then reboot recovery, youll have new recovery after that. then you reboot into system.
now upto this point, you can play along in your kk, have fun with features, say last goodbyes and all lol. Because everything stock kk related will be gone, past this point, including all the apps you have installed.
[IMPORTANT] : after rooting and installing recovery, get bootstack zip, rom zip and gapps zip files downloaded and placed together in a folder on your phone, before you start with flashing bootstack. Because you wont be able to boot back into system after flashing just bootstack.
now you prepare for MM, boot into recovery, now since you are in kk, you need to install LP bootstack, and for that you need to wipe everything using your recovery's wipe feature.
6. in recovery, hit wipe, hit advanced, select cache, dalvik cache, system, data. [ Dont select internal storage otherwise all flashing files will be gone and youll be left with a brick.] and wipe.
7. Now hit the back button to go back to main recovery screen once wiping is finished. hit install, flash the bootstack zip.
8. now your phone has new bootloader but its still empty, like you got a body but no soul . so hit back button, hit install and flash the rom zip you downloaded.
9. now flash gApps same way.
10. once its done, just hit reboot system. no other steps needed.
11. be patient, first boot takes longer than normal boot.
12.enjoy MM :highfive:
you probably know these steps from all the reading but its for your reference, so you dont screw up at all and be safe from bricking.
you can get google apps from opengapps website. you need to get ARM-> 6.0 -> (your prefered ones) pico/nano/micro/etc.. pico has the least amount of gapps, all important ones are there in pico, then extra will increase as you go up from pico to stock. stock has all the gapps. size will also increase as you go up. so choose as you prefer.
now once you have a cm13 /MM based rom, you wont need to flash bootstacks for other roms from next time unless the developer instructs to do so.
good luck
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
andrew2432 said:
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
Click to expand...
Click to collapse
cwm is clockworkmod, its a custom recovery. i think you meant CM 13, mm rom.
yes, the Cyanogenmod team have placed root access into the rom, so once youll be finished wih installing cm 13 rom, you can just go to settings, Tap build number repeatedly until a message will show "congrats you are a developer now". that'll open developer options in main setting screen Go into that and youll see root access. turn it on. youll have root.
you can check in root checker app to confirm root access for confirmation. you wont need super su app in any of these roms anymore.
your steps :
stock
1. root
2.autorec (for installing twrp on your phone) for kitkat its on forums, for lollipop its in google play. just get the one for your model, search for autorec in google play.
- blastgator's twrp requires you to have any version of twrp beforehand in order to install his version.
3. download and save blastgator's latest twrp, when youll go to download his twrp, itll be written there which one's is the latest version, just download that one and flash it through recovery.
4. Yes place all files in your phone, you can get gapps from opengapps.org/
select arm- 6.0- whatever size you like(, pico is lightest contains all essential gapps, stock contains every gapps)
5. wipe yes.
6. flash bootstack
7. flash rom
8. flash gapps
9. once gapps done, just hit reboot system.
10. enjoy
yes go for it when you have more than 80% battery, this is to ensure that all flashing steps go through without any issue, you dont want your phone to run out of juice while flashing rom do you that could cause soft bricks. so always keep battery more before flashing.
[IMPORTANT] : remember to read instructions of the rom you're installing and adjust the steps as instructed in there.
Goodluck :highfive:
Awesome, I forgot to.flash gapps prior to something I just did, not sure if it will cause increased global warming or thermonuclear war...update soon
@MarshisnotMellow
Gapps installed!! No Internet connection on the d800 and something sinister has happened to my unlocked WiFi Hotspot so I'll have to check for play store capabilities later!! Thanks for the help!!
I decided to go with the latest 29.10.2016 nightly of CM13 for my first run on this phone. Everything went through, no one died, lol. I'm going to start installing and restoring stuff now, get Xposed on, like I have on my TF701T tablet and trick out my phone's appearance. Just a note - after you install new bootstacks your phone's MAC address will change, so if you have a WiFi network with a MAC filter you might want to add your new address.

How do I go from 5.1.1 on nexus 10 to Nougat?

I am not a programmer and have little knowledge about flashing the ROM so to make sure I understand what I need to do and the order it needs to be done.
My Nexus 10 works great still, I have not had a security update for 2 some years and am concerned about this. Last October I tried to upgrade to 6.0 but it would not recognize the new rom and I ended up going back to the original 5.1 rom.
What I need to know is how to do it in a way I can understand. I have seen a utube video of someone that has been able to do it. So I know it can be done. Just need to know how.
Thanks,
Mike B.
Assuming you have a PC use this tool to unlock then root and install a custom recovery
Next download a Nougat rom like Lineage
Also download gapps and SuperSU
Copy the rom, gapps, and supersu into a folder on your tablet
Now reboot the tablet into recovery and do a full wipe then from recovery
Flash the rom
Flash gapps
Flash SuperSu
Reboot to system and give it a few minutes on the first boot

Categories

Resources