Related
Hi guys, sorry for my english
I have a nexus rooted, stock room and cwm installed but i didint recive the ota update to 4.2.2
Its normal?
Enviado desde mi Nexus 7 usando Tapatalk 2
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
AW: I cant recive ota update
It depends on which country you're in. I live in Germany and I still haven't got the update
Sent from my Nexus 7 using xda app-developers app
I live in chile, but the nexus was buy in EEUU
Enviado desde mi Nexus 7 usando Tapatalk 2
UK. Sat next to my sister who had received the update...
Could rooting be causing as problem because that's threw only difference between our devices, besides storage sizes, mine being a 16gb, hers being a 32gb.
I'm sure that won't matter, would it?
Sent from my Nexus 7 using XDA Premium HD app
Force stop and clear data in google play services a couple times. ( I think that's what it is) worked for me.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Numerous threads popping up all over asking the same questions, Mods are going to shut & lock many of these out soon - suggest that one read and use the SEARCH button. My OTA was downloaded already and ready to install but choose to wait 48 hours first.
4.2.2 rollout is for USA / North America now - gradually - and OTA if you are essentially running stock rom & kernel - simple update without losing Apps or data (CWM backup, always, as best practices) - took me 15 minutes from downloading, prep & backup to actual flashing and reboot, etc.
I opted to take a shortcut and went from 4.1.2 directly to 4.2.2 using the zipped, deodexed rooted version w busy box - bootloader stayed on 3.41 running JDQ39 now, smooth. I uninstalled the DSP/Beats Audio/Noozxoide EIZO-rewire audio Apps, just in case - and reinstalled EIZO from Play Store afterward, freeze Chrome browser & switched back on Boat Browser w. Flash Player, OTG mount is working for external USB, etc.
Using N7 from other regions of the world, download using the links here on XDA, check MD5's and then go thru the steps - profit & enjoy.
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Sent from my Nexus 7 using XDA Premium HD app
licaxda said:
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I had same problem, I downloaded stock image of 4.1.2, flashed and found my n7 going in to the bootloop. Downloaded stock image of 4.2.2, flashed and everything is ok. Restored with carbon backup. That is all.
Sent from my Nexus 7 using Tapatalk HD
licaxda said:
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Click to expand...
Click to collapse
Yes, my N7 was on rooted 4.1.2 factory rom & stock kernel, with minor tweaks for audio, Chrome browser frozen but no major mods otherwise, and the OTA file was downloaded already on the device when I checked yesterday, ready to install. From various threads posted in the last 48 hours, it's a mixed bags - some install easily while others ran into problems, reasons varied & solutions simple to unknown. I opted for a safer approach - reverse some of my tweaks/uninstalled the audio tweaks, unfreeze Chrome, rebooted & then wipe, before using CWM to flash. It was easy, rebooted and up & running in less than 10 minutes, ALL of the apps & data intact and no FC'd.
For (folks in Europe or Asia, etc.) not willing to wait or access to OTA and prepared to do it on your own (thus, taking the risks, however - small, do your backup first and save your data/settings/etc. with CWM or TWRP and Titanium Backup - to a HDD or USB drive (suggested: 8GB & up) or PC - just in case, for restoration in the "unlikely event" that something go wrong.
Here's the XDA-linked Factory IMG 4.2.2 Nakasi file links, either odexed or deodexed (rooted, insecure boot, etc.) that I used - also, download the bootloader zip in post #2 (not required or needed, but in case you needed it or wanted to use it as the latest bootloader) - http://forum.xda-developers.com/showthread.php?t=2148337
Download, check MD5's and transfer to the N7. Next - launch into bootloader (make sure USB debugging is enabled & unknown source is allowed too) and WIPE dalvik cache and cache (2 times or 3 times each) - then selected the zip to flash. Once done, exit & reboot and wait for it to boot up for the 1st. time and allow it to settle for a few minutes. Click Settings & confirmed that I'm on 4.2.2 and check a few Apps for functionality. Let it sit & shutdown, reboot & proceed to restore most of my tweaks, played videos & music, surf the web to reconfirm that it's running smooth - next, do a new baseline CWM Backup.
Of course, YMMV - if it doesn't work for you, re-trace your steps and take your time, do not RUSH. If all else failed, go back to stock first 4.1 or 4.2 - then, update to 4.2.1 in its rooted state - your saved Apps & data, settings, etc. saved to your PC or USB/portable drive will eventually help you "rebuild" - just a matter of time. (If my other 2 HTC's are that easy to update from GB to JB, I would be very, very happy)
Please give credit for "thanks" to "teshxx" for preparing the Roms and refer to that thread for future questions ...
Good Luck to all.
Great information, thanks for the hefty reply, may be worth stickying for a few weeks I'm sure others will have the same questions.
I believe installing Beats audio can screw things up too? Can some one confirm?
Sent from my Nexus 7 using XDA Premium HD app
Q&A for XperiaSP Locked Bootloader (LBL) Slim-4.4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for XperiaSP Locked Bootloader (LBL) Slim-4.4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello and thanks for the Rom and for your work.
Is neccessary flash the Kernel 207 with the build 8.8?
radio fm
Not for me !
Hey thanks for the latest release.
I currently have Slim-4.4.2.build.5.4_LBL-UNOFFICIAL-20140527 installed on my sp.
Do I need to wipe data/factory reset before update to the newest version or can I directly install it from the zip thru CWM?
Am getting google play services error after updating google play music app.
Can someone tell what is the meaning of the error and the fix?
nkat said:
Am getting google play services error after updating google play music app.
Can someone tell what is the meaning of the error and the fix?
Click to expand...
Click to collapse
Which gapps do you use?
I met a play service issue, due to bad download of the gapps...
To answer to kwstas, in slimroms, root must be enabled in dev options, root access: apps & adb
---------- Post added at 04:16 PM ---------- Previous post was at 04:14 PM ----------
In my case, i'm meeting 2 issues. I want to ask before flashing again: does anyone have the network mode tile? I have the LTE one, but can't find the 2g/3g one...
Also, am i the only one facing problem to access the external sd? It is shown in storage menu, but can't find it in root browser..
Babyrasta said:
Which gapps do you use?
I met a play service issue, due to bad download of the gapps...
Click to expand...
Click to collapse
I had installed the slim normal gapps provided with the v5.4 ROM.
Didn't have any problem till today when I updated the play music app.
One more question...
Am currently on the v5,4 slim ROM. Do I need to clear data/factory reset or can I directly update to the new version?
nkat said:
I had installed the slim normal gapps provided with the v5.4 ROM.
Didn't have any problem till today when I updated the play music app.
One more question...
Am currently on the v5,4 slim ROM. Do I need to clear data/factory reset or can I directly update to the new version?
Click to expand...
Click to collapse
Slim team always recommend to wipe at least system partition, cache & dalvik!
And don't forget to download the new gapps package
Help please
How did you solve the art problem (optimizing at every boot) ?
If you will tell me, can i implement it to any kitkat rom on Xperia SP ? (Most ROMS have that problem)
Babyrasta said:
Slim team always recommend to wipe at least system partition, cache & dalvik!
And don't forget to download the new gapps package
Click to expand...
Click to collapse
Thanks will install the new gapps after updating..
Sorry for so many questions.. Am new to this... Wiping system partition would wipe all the apps that I have currently installed right?
nkat said:
Thanks will install the new gapps after updating..
Sorry for so many questions.. Am new to this... Wiping system partition would wipe all the apps that I have currently installed right?
Click to expand...
Click to collapse
Nope, apps are deleted when you wipe data partition.
No worries for the questions, as you're in the right place
Just a warning, as you'll gap between 5.4 and 8.8, it's possible to meet some issues. If you have some problems, i recommend you to full wipe and flash again before reporting anything.
Babyrasta said:
Nope, apps are deleted when you wipe data partition.
No worries for the questions, as you're in the right place
Just a warning, as you'll gap between 5.4 and 8.8, it's possible to meet some issues. If you have some problems, i recommend you to full wipe and flash again before reporting anything.
Click to expand...
Click to collapse
Thanks @Babyrasta. Better to do a full wipe. Dont want any problems.
Babyrasta said:
In my case, i'm meeting 2 issues. I want to ask before flashing again: does anyone have the network mode tile? I have the LTE one, but can't find the 2g/3g one...
Also, am i the only one facing problem to access the external sd? It is shown in storage menu, but can't find it in root browser..
Click to expand...
Click to collapse
I installed the ROM after doing a full wipe. The ROM is very nice
I too didn't have the network mode after flashing. But I was able to add in the options. When we long press on the settings icon it gives the options to add the new tiles.
About the storage am not able to see the internal SD in the file explorers. Only the external SD card. Although in settings->storage both are visible. I guess this ROM only uses the external SD card as internal to install the apps and everything. OP has mentioned this post. Is there any way to use the internal memory also?
Ok. So i'm the only one to access to my internal instead of my external sd... Weird!
I fladhed back 8.2 yesterday because all my music is on my external one...
I'll try to flash last build later in the day...
I can't access internal storga? How can i fix that? is that rom only uses extenal storage like internal?
[noob question] And how to deodexed and super mod this rom? i used xperia z3 launcher but it couldn't change the icon and can i install z3 app like calendar, message?
CWM freezes at data wipe
Hi!
I've just downloaded this SlimKat ROM, but at the very beginning of the installation, in CWM, the screen freezed when it was wiping data.
The last lines were:
-- Wiping data...
Formatting /data...
Formatting /cache...
And now I can't do anything, it's like this for 45-50 minutes now, my phone doesn't react to any buttons or swiping on the screen.
Could anyone help, please?
EDIT:
Problem solved. It seems, I had to wait for a nice 65 mins for CWM to complete. Now everything works just fine, ROM installed correctly.
SP upgrade
Kedves Bagyusz,
1 hónapja próbálom összelapátolni a C5303-as Xperia SP-mhez (T-Mobile) a cuccokat, hogy 4.4.4-et tudjak telepíteni, de valami mindíg túl új vagy túl régi, így soha nem sikerül.
Kérlek küldj nekem telepítőket/linkeket, hogy össz tudjam rakni a csomagot a telepítéshez.
Köszönettel Ákos!
ftomi89 said:
Hi!
I've just downloaded this SlimKat ROM, but at the very beginning of the installation, in CWM, the screen freezed when it was wiping data.
The last lines were:
-- Wiping data...
Formatting /data...
Formatting /cache...
And now I can't do anything, it's like this for 45-50 minutes now, my phone doesn't react to any buttons or swiping on the screen.
Could anyone help, please?
EDIT:
Problem solved. It seems, I had to wait for a nice 65 mins for CWM to complete. Now everything works just fine, ROM installed correctly.
Click to expand...
Click to collapse
I advise you to use TWRP, it is much faster!
Hello. I'm new to this rom. I actually just flashed the latest release a few moments ago and I feel like I'm satisfied already. Anyway, do we have the screen recorder on the rom already? I can't seem to find it. I'll be back in a few days for a full detailed feedback. I'm almost certain performance won't fail me. What I'm worried about is battery life. I always find custom roms' battery life needs improvements.
millikp said:
Hello. I'm new to this rom. I actually just flashed the latest release a few moments ago and I feel like I'm satisfied already. Anyway, do we have the screen recorder on the rom already? I can't seem to find it. I'll be back in a few days for a full detailed feedback. I'm almost certain performance won't fail me. What I'm worried about is battery life. I always find custom roms' battery life needs improvements.
Click to expand...
Click to collapse
If you would want to know if there is a non-native workaround, I recommend going here:
https://play.google.com/store/apps/details?id=com.iwobanas.screenrecorder.free
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Make a backup in TWRP, wipe your system partition, Flash the ROM zip and the GAPPS zip, reboot, profit. If anything fails you can roll back to your backup and try again.
Real simple. Download the latest built as well as the latest google apps (gapps)
Reboot to TWRP
Do a backup, so you have a restore point if something happens
Go to wipe->advanced wipe and choose both caches, system and data. DO NOT wipe internal storage
Go to install, choose the ROM and gapps and install them
Reboot
You will now be on the latest. You will have to set your phone up again, and all your text messages, home screen, act will be gone but all your stuff on your sdcard (internal storage) will be untouched.
You can also get real ambitious and make backups with something like titanium backup of all your apps and data and restore it after booting PN, but try to not back up system apps or system data (it should be an option... I dont know, I never use tibu). The main thing you lose without backing up is texts, I usually just deal with it/redownload apps/set up home screen again.
On future updates, unless there are major changes and its indicated by a majority of people in the PN thread, just dirty flash.
That is, backup, wipe caches, install new ROM version( I wouldn't reflash gapps ) this will leave all your apps, settings, ect... But should only be done when flashing the same or a very similar ROM. If you dirty flash and experience problems, go back and clean flash as I first instructed.
So I should not worry about flashing the new 32r radio?
shouldnt this have been one of the first things to learn BEFORE you ever rooted your phone? yea, nice job jumping in before learning your way around. i bet you even used a toolkit to root your device..
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
roy.garlington said:
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
Click to expand...
Click to collapse
no tool kit? ok, your -1 on not learning before rooting has a +1 right by it, for rooting the proper way. you just might earn some respect
Hey there simbo, what do you say about flashing the radio?
Sure. Or don't.
Whatever.
The radio is pretty separate from android. Its basically drivers to tell you phone how to use hardware.
FI has certain requirements for activation that may check what radio you have, but outside of that run what ever works good for you., its not going to for sure be any specific one. Newer may often be better but its not uncommon that an older one may work a little better.
Different apps can help you monitor (I dunno which ones... But I know its a thing ), you can also go into about phone -> status -> sim status and check signal strength where lower dBm is better(well a lower numeric value... Its technically a negative number, so higher is better i.e. -113 is worse then -104). This will vary slightly minute to minute and place to place so just taking a glance once won't really settle it for you
I just use it for a day or two, pay attention to how my signal is (just kinda how often did I have decent # of bars, nothing scientific), and check battery stats clicking on cell standby and looking at % of time with out signal.
roy.garlington said:
Hey there simbo, what do you say about flashing the radio?
Click to expand...
Click to collapse
youre choice. you can try any of the radios, from previous android versions, on any android version. they arent specific. im using the 27R radio. whichever one works best for you, thats whats important
roy.garlington said:
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Click to expand...
Click to collapse
Well, it's all very easy if you read a little. Still i will give you one extra tip in case you start flashing all kinds of roms: You unlocked your bootloader. Before doing that you enabled "OEM unlocking" in 'Developer options'. Leave that enabled (this setting is 'sticky'. even when you wipe the device)!!!!. Leaving OEM unlocking enabled will disable "Device Protection" that causes sometimes a 72 hours lock-out from your Google account.
Ok so I've seen a lot of confusion on how to correctly flash OxygenOS on your brand new OnePlus 5, and also how to correctly and easily root your phone.. This guide aims to clear up any confusion regarding this. Ready? Let's move on.
Q: What's the difference between International and Chinese versions of the OnePlus 5?
A: Hardware-wise there is absolutely no difference between the 2 versions. In terms of software, the international version runs OxygenOS (OOS) while the Chinese version runs HydrogenOS(H2OS). H2OS has no Google services pre-installed and is generally not recommended for use outside China. Both OxygenOS and HydrogenOS are official updates by OnePlus.
Q: I bought a Chinese phone. How do I install OxygenOS then?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update.
2. Place it in the root of your internal memory. Basically don't put the file in any folder.
3. Go to Settings > System updates, press the gear icon and select Local upgrade.
4. Choose the file, the phone will boot into recovery and everything is done.
Q: OK I want to root my phone but I don't want to lose Android Pay, Netflix, Pokemon GO etc. Is it possible?
Simple answer: Yes. Long answer: Maybe not in the long run.
Why is that so? You see, back in the old days there were little downsides to rooting. Alas, Android Pay and Pokemon GO came along, and in an effort to tighten up security, Google implemented this thing called
SafetyNet. Basically it's a measure to test your system integrity, meaning that any modification to system will trigger SafetyNet and many apps will be "locked down". Android Pay and Pokemon GO will not work,
and Netflix won't show up on Google Play anymore. Some devices even check for unlocked bootloader, but apparently not the OnePlus 5, so you don't have to switch to a custom kernel to root.
To overcome this problem, the brilliant minds at XDA came up with system-less root. Chainfire was the first to implement it in SuperSU, but right now nobody uses SuperSU anymore. Magisk is the new kid in town,
and quite frankly much better IMO.
Q: Alright enough talk, how do I root the phone?
A: Patience my young Padawan. I will get to that in a moment. But here are some things you have to know.
1. Rooting involves unlocking your bootloader, and ALL YOUR DATA WILL BE WIPED. Keep a backup and move everything in your internal memory somewhere else.
2. Magisk may beat SafetyNet now, but there is no guarantee this will always be the case. So your SafetyNet enabled apps may not work all the time.
3. OTA updates from OnePlus will work differently when you are rooted. But hey that's what this guide is for. :good:
Easy rooting guide
1. Install ADB drivers.
2. Go into settings > about phone. Press the build no. a few times to activate developer options.
3. Turn on developer options, OEM unlocking and USB debugging.
4. Connect phone to PC and allow ADB access on phone. Wait for drivers to finish installing.
5. Download and install this simple tool on your PC.
6. Download one of the 2 TWRP recoveries below.
TWRP Official
xdvs23's TWRP
7. Open the All-in-One tool and make sure your device is recognised as OnePlus 5. Click on Unlock bootloader. Your bootloader is now unlocked and all your DATA WILL BE WIPED!
8. Select the "and boot it" arrow and click flash TWRP, click manual mode and choose the TWRP.img file you downloaded earlier.
9. After everything is done, your phone should now boot into TWRP successfully. Do not reboot yet.
10. On your PC, download the latest version of Magisk. Place the zip file onto your phone using USB and flash it with TWRP. Clear cache and reboot into system.
11. You should now see a new app called Magisk Manager. Check for updates!
12. However, do keep in mind not to mess around the system. If you need something, check to see if there any Magisk Modules available. There is also a small repo in the downloads section in Magisk Manager. Also Adaway works great with Magisk. Just make sure to turn on systemless host file in Magisk manager.
14. Congrats you are now rooted!:highfive:
Q: Alright now that I'm rooted, how do I get official updates?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update. Place it on your phone. Make sure you also have your Magisk zip.
2. Boot into TWRP. Press the volume button when the bootloader unlocked screen comes up. Use volume buttons and power button to select recovery.
3. Flash the OxygenOS zip file. DO NOT reboot yet!
4. Tap the home button and flash Magisk. Clear cache.
5. Reboot into system and you are done!
Hope this guide is simple enough for you guys to understand. It might seem daunting at first, but practice makes perfect.
Also it is not a requirement to root, most people get by fine without ever rooting. But we are not like normal people, are we? Why else would we be on XDA then?
Further questions
Q1: Why Magisk and not SuperSU?
A: Besides the fact that Magisk is being constantly updated to bypass SafetyNet, it is also open-source. Wish I could say the same for SuperSU, the app is not what it used to be. Chainfire is no longer aware of the changes made in his app and I for one am not willing to take my chances with a shady developer. I had countless bad experiences with Chinese apps, many of them created by large companies. Check out this thread for more info.
Q2: Why exactly is HydrogenOS not recommended for use outside China?
A: Besides the aforementioned lack of Google apps, HydrogenOS is also tweaked differently from OxygenOS. It is significantly more aggressive in killing apps and not letting them run in the background, as you would expect with the number of rogue apps in China, made worse by the fact that there is no Play Store in China. OxygenOS on the other hand has a limit of 32 apps in memory, which I guess is a nice compromise between performance and battery life.
Reserved just in case. Probably will never need it though.
to be fair, there are still lots of people using SuperSU..
What should I do if I still want to use SuperSU?
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
ipredatorv said:
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
Click to expand...
Click to collapse
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
iamelton said:
to be fair, there are still lots of people using SuperSU..
Click to expand...
Click to collapse
Ningyou Higeki said:
What should I do if I still want to use SuperSU?
Click to expand...
Click to collapse
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
jasonwsc said:
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
Click to expand...
Click to collapse
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
ipredatorv said:
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It might help with your battery drain issue, but chances are some apps are running in the background draining your battery.
Google services not working
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Nishatian1 said:
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Click to expand...
Click to collapse
Just a wild guess, but are you still in China? Check your VPN before trying to access the Google Playstore. Otherwise, remove the Playstore and download the most recent Playstore apk from a website like apkmirror. If they offer multiple versions, go for ARM 64.
Sent from my ONEPLUS A5000 using Tapatalk
jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I got my Chinese OP5 two days ago and went through the whole procedure of unlocking, rooting, and flashing OxygenOS. Now I see that somebody took the time to write a nice guide on how to do it. Thanks @jasonwsc! I really wish I had this available to me already. I am sure it's gonna be a great help to others though!
I wasn't aware that SuperSU had been sold to a Chinese company through and that it is no longer open source. Knowing what I know now I regret flashing SuperSU yesterday and would love to switch to Magisk.
My question would be: what's the "proper way" to switch from SuperSU to Magisk? Just unroot via SuperSU and flash Magisk, or is there a better, cleaner way?
Edit:
Nevermind, just searched it and there's a super nice guide here.
Ningyou Higeki said:
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
Click to expand...
Click to collapse
Magisk works fine, have no issues so far.
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Moazamali said:
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Click to expand...
Click to collapse
Yes it's the same. Just flash the firmware file for OP5T instead of the OP5.
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
nayemohd said:
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
strongst said:
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
Click to expand...
Click to collapse
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
kimon60 said:
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
Click to expand...
Click to collapse
Which h2os version and which recovery version did you use(file names please)? What do you mean with formatting the system? What did you wipe or format exactly?