Related
I have done most of the initial steps required to install CM11 but still I want to conform if I am going in the right path...
Model : Xperia SP C5302
Built number : 12.1.A.1.207 (Stock)
Kernel version : 3.4.0 (July 8 2014)
I have done the following things:
- Rooted using Towelroot (Verified root using a few root checking apps)
- Installed SuperSU (Chainfire) and BusyBox
- Installed CWM 4.4.1
And have not done the following:
- Yet to Unlock Bootloader
- Did not flash any Kernel
So I have a few Questions
Question 1:
Unlocking the Bootloader will lead to permanent loss of DRM keys... So will I be able to access Bravia Engine by any means after installing CM11???
Question 2:
Is it necessary to flash a kernel before installing CM11???
Question 3:
Is it safe to install CM11 by booting in Recovery mode or Flashboot mode (or whatever they call that, in which we do not need the help of PC) or using flashtool in PC is much safer and better???
Question 4:
Is there anything else for Me to do other than what I have already done (all those I have mentioned)???
Question 5:
There are a lot of Bootloop complaints about the recently released CM11 M10 Snapshot... So is it safe to install it or is it better to go with Nighties??? Is Nighties Stable (around)???
Question 6:
Is there any method to bring back the use of the Illumination bar in the mobile as a visualizer in Music n Photos app after Installing CM11???
Question 7:
In case I mess up, is what is the method to return to stock firmware (and what should I do now, i.e. before Unlocking Bootloader)???
If not all, please help Me clear at least some of My doubts
And if possible, It will be great if You give a complete tutorial (video or post) form a stock, unrooted, locked mobile to a mobile running a custom ROM...
Thank You all a Lot :victory:
bharathulaganathan said:
I have done most of the initial steps required to install CM11 but still I want to conform if I am going in the right path...
Model : Xperia SP C5302
Built number : 12.1.A.1.207 (Stock)
Kernel version : 3.4.0 (July 8 2014)
I have done the following things:
- Rooted using Towelroot (Verified root using a few root checking apps)
- Installed SuperSU (Chainfire) and BusyBox
- Installed CWM 4.4.1
And have not done the following:
- Yet to Unlock Bootloader
- Did not flash any Kernel
So I have a few Questions
Question 1:
Unlocking the Bootloader will lead to permanent loss of DRM keys... So will I be able to access Bravia Engine by any means after installing CM11???
Question 2:
Is it necessary to flash a kernel before installing CM11???
Question 3:
Is it safe to install CM11 by booting in Recovery mode or Flashboot mode (or whatever they call that, in which we do not need the help of PC) or using flashtool in PC is much safer and better???
Question 4:
Is there anything else for Me to do other than what I have already done (all those I have mentioned)???
Question 5:
There are a lot of Bootloop complaints about the recently released CM11 M10 Snapshot... So is it safe to install it or is it better to go with Nighties??? Is Nighties Stable (around)???
Question 6:
Is there any method to bring back the use of the Illumination bar in the mobile as a visualizer in Music n Photos app after Installing CM11???
Question 7:
In case I mess up, is what is the method to return to stock firmware (and what should I do now, i.e. before Unlocking Bootloader)???
If not all, please help Me clear at least some of My doubts
And if possible, It will be great if You give a complete tutorial (video or post) form a stock, unrooted, locked mobile to a mobile running a custom ROM...
Thank You all a Lot :victory:
Click to expand...
Click to collapse
First I will suggest you to leave your Bootloader locked and just install Paranoid or PAC ROMs.
1. Yes, you will lose your DRM Keys. No you wont be able to.
2. It's good to flash latest .207 kernel before/after you install the ROM (if your bl is locked).
3. Just install it from CWM/TWRP
4. Root→install recovery→wipe data/cache etc.→install ROM→install GAPS→flash kernel→reboot→you Gucci
5. Your phone can always explode if you're dumb enough or you just don't like to read. (as I said PAC or Paranoid are better options than CM11)
6. Not really sure.
7. If you have your bl locked then just put your phone in flashmode and flash stock .ftf with flashtool. If not relock your bootloader then do the same.
So, if you ask me go for PAC ROM and locked bootloader. I think it's the best ROM so far for our device. I'm with Paranoid and it's quite Gucci as well, everything works like a charm, the ROM is fast and stable. I'm only suggesting you to install Greenify and DS Battery Saver Xposed Modules cause the battery isn't as good as the stock one.
As for tutorial, just read the guide in the thread. It's pretty simple and straight forward. You have to be really dumb to mess up five simple steps.
Good luck!
For Q6, it is possible to use the illumination lights via U-Disco, here.
You can unlock your bootloader and use custom kernels, but I personally recommend staying away from that and using locked bootloader roms, there are many good ones. The risk (hardbrick :crying: ) is not worth it-if you mess it up.
eSu.Matix said:
First I will suggest you to leave your Bootloader locked and just install Paranoid or PAC ROMs.
1. Yes, you will lose your DRM Keys. No you wont be able to.
2. It's good to flash latest .207 kernel before/after you install the ROM (if your bl is locked).
3. Just install it from CWM/TWRP
4. Root→install recovery→wipe data/cache etc.→install ROM→install GAPS→flash kernel→reboot→you Gucci
5. Your phone can always explode if you're dumb enough or you just don't like to read. (as I said PAC or Paranoid are better options than CM11)
6. Not really sure.
7. If you have your bl locked then just put your phone in flashmode and flash stock .ftf with flashtool. If not relock your bootloader then do the same.
So, if you ask me go for PAC ROM and locked bootloader. I think it's the best ROM so far for our device. I'm with Paranoid and it's quite Gucci as well, everything works like a charm, the ROM is fast and stable. I'm only suggesting you to install Greenify and DS Battery Saver Xposed Modules cause the battery isn't as good as the stock one.
As for tutorial, just read the guide in the thread. It's pretty simple and straight forward. You have to be really dumb to mess up five simple steps.
Good luck!
Click to expand...
Click to collapse
Thanx a lot... I flashed PACman ROM... Its really Osm :laugh:
103
ShinOrochiX said:
For Q6, it is possible to use the illumination lights via U-Disco, here.
You can unlock your bootloader and use custom kernels, but I personally recommend staying away from that and using locked bootloader roms, there are many good ones. The risk (hardbrick :crying: ) is not worth it-if you mess it up.
Click to expand...
Click to collapse
Will try U-Disco... Thanx 4 d suggestion...
ShinOrochiX said:
For Q6, it is possible to use the illumination lights via U-Disco, here.
You can unlock your bootloader and use custom kernels, but I personally recommend staying away from that and using locked bootloader roms, there are many good ones. The risk (hardbrick :crying: ) is not worth it-if you mess it up.
Click to expand...
Click to collapse
U-Disco is OSM but U need 2 buy it 4 it 2 run in the background...
Can someone tell me if I can flash this on my locked sp? http://forum.xda-developers.com/showthread.php?t=2868398
I have been a hardcore custom rom user (nexus 4), but sony's implementation of things confuses me a lot, that is why I have been refraining to install CM
tj_droid said:
Can someone tell me if I can flash this on my locked sp? http://forum.xda-developers.com/showthread.php?t=2868398
I have been a hardcore custom rom user (nexus 4), but sony's implementation of things confuses me a lot, that is why I have been refraining to install CM
Click to expand...
Click to collapse
Yes you can ! The LBL tag means locked bootloader (opposed to UB or UBL for unlocked). You can flash any ROM that has it but just check the instructions in op for any ROM specific recommendation.
pec0ra said:
Yes you can ! The LBL tag means locked bootloader (opposed to UB or UBL for unlocked). You can flash any ROM that has it but just check the instructions in op for any ROM specific recommendation.
Click to expand...
Click to collapse
Is there any basic disadvantage of flashing ROMs on a locked bootloader(like some features not working?) or is the similar to unlocked bootloader roms?
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not iirc <71.08 shouldn't be flashed onto 71.08 existing BL right or was it 71.10 ?? (idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all. Heard a few CM roms had BL packed into ROMs and the updte to 5.1.x + lower BL caused hardbrick, a.k.a bootloop + noTWRP with Fastboot lockedout ).
So here's my to-do list sorry to post this long but seems like this is start for me....Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & Nexus 6 information....
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - MultiROM working guide on 5.1.1 plus M latest release anyone, will try the official thread tho, any info on whre to start would be awesome !!
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful posts/threads that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Ashtrix said:
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not(idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all). So here's my to-do list sorry to post this here but seems like this is start for me.Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & a few Nexus 6 information, any useful links would do the job.
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - Does MultiROM work on 5.1.1 plus M latest release ?
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful links that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Click to expand...
Click to collapse
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
AlkaliV2 said:
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
Click to expand...
Click to collapse
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Ashtrix said:
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Click to expand...
Click to collapse
I'm pretty sure mFastboot is made directly for a Verizon variant, but since the Nexus 6 is unlocked and your Verizon SIM card dictates the network you are on, I would say stick with normal Fastboot for your flashing endeavors. Good luck and read twice, flash once :good:
Edit: Quick side note, love the avatar. Good choice.
Thankyou :highfive:
Just did an OEM unlock and wierdly after that, the bugdroid loading doesn't end at all. Did an factory img flash of 5.1.1 Shamu-LMY48Y and booted in less than a min Lol.
And yes the fastboot is working, wow things are definitely wierd with Shamu (volume normalization, mFastboot previous xperience, bootloader bricks...seems like Qcom fixed that after CM brickbug and no one can help the manual bricking) but I'm ok with all these , just love this device, massive, powerful and sexy looking piece
EDIT :
Well everything's going fine but this bugdroid loading doesn't seem to be fixed at all, after bootup 23Gb was there so I did a format and again stuck, this time around I tried using TWRP to flash (CM12.1)after doing fastboot commands - fastboot format userdata, cache. Now it says unable to flash on so&so data partition, So formatted from the OS and now MTP says generical heirarchial. I don't remember any device with that format...
EDIT 2 : Device won't boot with that bugdroid formatting the Data partition. Needs to be fastboot flashed else stuck there forever again same 23Gb bootissue if I do that & Using fastboot format userdata command it formats into the 64GB - 54Gb available space but with TWRP It fails to flash - the same error, can't flash on data parition. So repeat fastboot and it's a damn cycle. Will try to flash MM if it won't then. I may have to return again...OMG
EDIT 3 : http://forums.androidcentral.com/go...ys-formatting-data-yellow-text-any-ideas.html
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-formatting-data-t2737793
EDIT : Tried MM and after 10 mins formatted succesfully now gotta try a ROM or any, hope its fine !!
Again the GH FS is back with MTP and doesn't flash at all with TWRP. If I go for a re-lock and it it fails to boot with formatting properly...then bam nothing but a bricked Nexus !!
TWRP did the format but the device is messed up, sliptscreen issue..
I'm going to return this, enough of the hassle had me messed up totally :crying:
Seems like 6P seems better than having all these issues. Or wait for the 2016 device...
EDIT : Sorry for the GH format seems like it's normal, but the flashing issue is too wierd..
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
scryan said:
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
Click to expand...
Click to collapse
I know this issue, just a factory reset fixed this thing on my old N6 that I had for 2 days, but this takes too much of time to format....Just had TWRP do the job and flashed the Temasek but ALAS !! Splitscreen issue.
I've been reading forums in XDA and reddit almost the whole day and was not able to find any definite guide about my inquiries so i started this new thread..
Here's my Story, i bought a brand new nexus 6 6.0.1 with build MMB29Q, i wanted to adjust the saturation because its too high, and of course i have to root to do that. i have already unlock boot loader. PS I'm very new in roooting, as in Zero experience, i'm reading about it right now but i need some help from you guys for me to not brick my new phone. 'Im planning on doing Systemless Root BTW.
My questions are:
1. What SuperSu version and TWRP version is compatible with MMB29Q? (i know the newest version is 2.67 for SuperSU and 2.8.5.0 for TWRP) I'm having second thought in using them because MMB29Q came to my device just February. Can someone tell me which version si compatible?
2. [/B] If i would be successful in rooting my device, i plan on flashing custom kernel (I'm Planning on Using Franco Kernel because it is the one the i have read which is compatible in color saturation control and temperature. Any suggestion for other kernel will be very helpful.) My question is after i root my device can i just directly flash it (franco kernel zip file) using TWRP in my device? or are there any requisites before flashing the franco kernel?
Please anyone can give a definitive guide on this, or atleast give me forum threads that i can read about this. Will really appreciate for your help guys, i really love my nexus 6, saturation and warm temp is my only concern. Thank you Guys!!!
2.67 for SuperSU is compatible. 2.8.5.0 TWRP is also compatible.
(Kernel - I don't know)
1. SuperSU 2.65 or 2.67, TWRP 3.0.0. Keep in mind that SuperSU 2.67 is the beta version so you might want to use 2.65 instead. There are alternative superuser binaries available but those require a bit more work to use.
2. No suggestion for an alternate kernel, as I don't use one. As long as a flashable zip file is available for the chosen kernel, you can flash it via TWRP.
I used SuperSU v2.67, TWRP 3.0.0-0 and the ElementalX (3.09) kernel.
Rooted right now on stock MMB29Q.
I'm using SuperSU 2.66 on 29Q without issue. TWRP has been updated to 3.0.0-1 link: https://dl.twrp.me/shamu/
Read the OP for the kernel that you want. In there it will state if any special requirements are needed to flash before and/or after.
You'd want to flash the kernel first then flash SuperSU.
No issues with SuperSU 2.67 and TWRP 3.0.0 ElementalX is a great custom kernel. It supports screen color control (manually or pick in Aroma installer) and has a bunch of other features.
You should check out the N6 all in one beginners guide.
http://forum.xda-developers.com/showthread.php?t=2948481
Sent from my Nexus 6 using Tapatalk
Question has been answered already, but I would say newest SuperSU, version 2.67, and kernel suggestion? I love elite kernel because it supports all ROMs! AOSP and stock! PM me if you have questions, I'll help ya!
Hi I have been reading hi and low also to root MMB29q but only access to a MAC....any advice/ point me in the right direction is much appreciated, thank you
d88naimi said:
Hi I have been reading hi and low also to root MMB29q but only access to a MAC....any advice/ point me in the right direction is much appreciated, thank you
Click to expand...
Click to collapse
On the phone make sure you have USB debugging enabled, and also allow the bootloader to be unlocked.
Get the Android SDK and ADB setup on your MAC. I don't have a MAC and this guide may or may not be correct, I can't confirm. Boot your phone into bootloader mode (hold volume up + volume down + power when the phone is turned off). Connect the phone to your MAC and run the command "fastboot oem unlock" to unlock your bootloader. Then "fastboot flash recovery twrp-3.0.0-1-shamu.img" this will put on TWRP recovery.
Now using your volume rockers to boot into recovery. Now flash the version of SuperSu you want to use- 2.67 for Systemless or 2.65 for System. If you use systemless, TWRP will probably warn you you are not rooted and to swipe to install SuperSu. Don't do this!
Today i want to explain how to update your phone in all cases you can be. The Thread is divided into situations and methods.
CASES
1. I have a stock rom with an unlocked bootloader and without modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
MSM Tool Restore Method
2. I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
3. I have a stock rom with an unlocked bootloader and I'm unable to boot the stock rom:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
4. I have a stock rom with an unlocked bootloader and I've not the stock rom or a rom stock based:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
5. My Phone is bricked, i can't boot the rom, i can't enter in TWRP:
In this can you can try with:
Fastboot Update Method (Recommended)
MSM Tool Restore Method
METHODS
Local Update Method
With this method you can flash a newer version or the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage in the main folder;
- Go in settings/system/system updates/advanced settings/Local Update and choose your new rom ( Here you can find a video guide for this passage);
- Click on Install and at the end of the process you need to reboot the phone;
- If this is a big update it's better if you wipe your data.
Fastboot Update Method
With this method It's better flash the same version you already have:
The full method is explained in the relative thread:
OnePlus 6T Fastboot ROMS
OnePlus 6 Fastboot ROMS
TWRP Update Method
With this method It's better flash the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage;
- Click on Install;
- Choose the stock rom and flash it.
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
DONATE LINK
If you want to support the project please consider making a donation, thanks.
[/CENTER]
mauronofrio said:
Today i want to explain how to update your phone in all cases you can be. The Thread is divided into situations and methods.
CASES
I have a stock rom with an unlocked bootloader and without modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
MSM Tool Restore Method
I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
I have a stock rom with an unlocked bootloader and I'm unable to boot the stock rom:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
I have a stock rom with an unlocked bootloader and I've not the stock rom or a rom stock based:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
My Phone is bricked, i can't boot the rom, i can't enter in TWRP:
In this can you can try with:
Fastboot Update Method (Recommended)
MSM Tool Restore Method
METHODS
Local Update Method
With this method you can flash a newer version or the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage in the main folder;
- Go in settings/system/system updates/advanced settings/Local Update and choose your new rom ( Here you can find a video guide for this passage);
- Click on Install and at the end of the process you need to reboot the phone;
- If this is a big update it's better if you wipe your data.
Fastboot Update Method
With this method It's better flash the same version you already have:
The full method is explained in the relative thread:
OnePlus 6T Fastboot ROMS
OnePlus 6 Fastboot ROMS
TWRP Update Method
With this method It's better flash the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage;
- Click on Install;
- Choose the stock rom and flash it.
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
Click to expand...
Click to collapse
Great Mauronofrio
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:18 PM ---------- Previous post was at 02:01 PM ----------
The second case?..Im rooted with twrp and stock rom on 6t..
so I have to flash the eventually full rom via twrp? !? which twrp?
Sent from my [device_name] using XDA-Developers Legacy app
isoladisegnata said:
Great Mauronofrio
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:18 PM ---------- Previous post was at 02:01 PM ----------
The second case?..Im rooted with twrp and stock rom on 6t..
so I have to flash the eventually full rom via twrp? !? which twrp?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, the recommended is the local update
Nice work
Thanks for this. This is my first OnePlus device. I'm coming from a 5-year-old HTC One so updating pretty much meant wiping phone completely and reinstalling the ROM. I watched that video on the local update method. Good to know that even the full ROM installation doesn't wipe my data.
I do need some clarification on some things, though. I'm case 2 - stock ROM, unlocked BL & rooted. I have YouTube Vanced installed via Magisk as well as AdAway. I assume those would be considered modifications. In this guide, https://forum.xda-developers.com/showpost.php?p=78026660&postcount=3, it says that rooted users need to first uninstall Magisk & restore images before installing the update. Then reinstall Magisk after updating. But here it doesn't mention the need to do this. What's the difference between these two processes? I've read lots of posts lately where people get into a soft brick situation after making some modifications. But I'm not seeing any explinations as to why this happens & I'd like to avoid that.
If I use the local update method from this thread, will Magisk survive the update and will I still be rooted? Or will I need to reinstall it & re-root?
sharksfan7 said:
Thanks for this. This is my first OnePlus device. I'm coming from a 5-year-old HTC One so updating pretty much meant wiping phone completely and reinstalling the ROM. I watched that video on the local update method. Good to know that even the full ROM installation doesn't wipe my data.
I do need some clarification on some things, though. I'm case 2 - stock ROM, unlocked BL & rooted. I have YouTube Vanced installed via Magisk as well as AdAway. I assume those would be considered modifications. In this guide, https://forum.xda-developers.com/showpost.php?p=78026660&postcount=3, it says that rooted users need to first uninstall Magisk & restore images before installing the update. Then reinstall Magisk after updating. But here it doesn't mention the need to do this. What's the difference between these two processes? I've read lots of posts lately where people get into a soft brick situation after making some modifications. But I'm not seeing any explinations as to why this happens & I'd like to avoid that.
If I use the local update method from this thread, will Magisk survive the update and will I still be rooted? Or will I need to reinstall it & re-root?
Click to expand...
Click to collapse
If you flash a stock rom you will lose all the mods you already do, root and twrp included. If you want you can keep the root, i will attach a image guide.
mauronofrio said:
If you flash a stock rom you will lose all the mods you already do, root and twrp included. If you want you can keep the root, i will attach a image guide.
Click to expand...
Click to collapse
Those are the instructions that I was referring to that had me a bit confused. Is there any benefit to doing the update that way compared to using the local update method and re-flashing Magisk, the way I did when I rooted the first time? Does one method have less potential for messing something up?
sharksfan7 said:
Those are the instructions that I was referring to that had me a bit confused. Is there any benefit to doing the update that way compared to using the local update method and re-flashing Magisk, the way I did when I rooted the first time? Does one method have less potential for messing something up?
Click to expand...
Click to collapse
It's the same thing...
mauronofrio said:
It's the same thing...
Click to expand...
Click to collapse
Great. Thank you.
I have bricked my new phone. With your flash-all.bat I have restored it in like 2 minutes.
Thanks A LOT mauronofrio! Grazie, Grazie molto!
SOS: please help to restore my oneplus6t to factory condition
mauronofrio said:
Today i want to explain how to update your phone in all cases you can be. The Thread is divided into situations and methods.
CASES
1. I have a stock rom with an unlocked bootloader and without modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
MSM Tool Restore Method
2. I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
3. I have a stock rom with an unlocked bootloader and I'm unable to boot the stock rom:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
4. I have a stock rom with an unlocked bootloader and I've not the stock rom or a rom stock based:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
5. My Phone is bricked, i can't boot the rom, i can't enter in TWRP:
In this can you can try with:
Fastboot Update Method (Recommended)
MSM Tool Restore Method
METHODS
Local Update Method
With this method you can flash a newer version or the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage in the main folder;
- Go in settings/system/system updates/advanced settings/Local Update and choose your new rom ( Here you can find a video guide for this passage);
- Click on Install and at the end of the process you need to reboot the phone;
- If this is a big update it's better if you wipe your data.
Fastboot Update Method
With this method It's better flash the same version you already have:
The full method is explained in the relative thread:
OnePlus 6T Fastboot ROMS
OnePlus 6 Fastboot ROMS
TWRP Update Method
With this method It's better flash the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage;
- Click on Install;
- Choose the stock rom and flash it.
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
DONATE LINK
If you want to support the project please consider making a donation, thanks.
[/CENTER]
Click to expand...
Click to collapse
Hey guys,
Re: OnePlus6T, Oxygen OS 9.0.7
SOS: Can anyone give me a Guide for Dummies (lol) kinda tutorial on how to unroot, remove twrp, remove magisk, remove adb+fastboot and everything else that had been done in the process of rooting+modding. (root as per https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6t-with-magisk-0190586/ ) (stereo mod as per https://forum.xda-developers.com/oneplus-6t/themes/magisk-stereo-speaker-mod-oneplus-6t-t3860041)
Actually, i am a total newbie/non-techie. But right after updating to os 9.0.7, i took fancy to having a stereo output through the earpiece, too. But in the end, there was no sound from the earpiece. Also, i found some other complications in other sections of the phone, although i don't know whether they were related/due to the stereo mod or the rooting process. And being a non-techie, I did not want to tinker with my phone any further. So, i decided to roll back and intuitively (1)first uninstalled stereo mod from magisk, (2)then uninstalled magisk from within the magisk itself, (3)then used the case #2 method, illustrated at https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795 to go back to the stock rom.
But i find that i have still not gone fully back to the factory state. When booting, i find the screen which informs me about the unlocked fastboot status, etc., which shows that twrp etc are still on my system. I would certainly want to go back to the factory condition. Will someone of you guide me step by step (as i am a non-techie) into removing this fastboot, twrp, etc. and bring me back to the factory condition and also (ii)in removing any fastboot/adb related things, if any, from my windows 10 PC? I shall be very grateful, as I am scared as well as left with no further technical skill to delve further into technical misadventure. It was my big mistake to undertake this exercise, without possessing any technical knowhow, i admit.
Anyway, someone please help.
mnbvcxzaq1 said:
Hey guys,
Re: OnePlus6T, Oxygen OS 9.0.7
SOS: Can anyone give me a Guide for Dummies (lol) kinda tutorial on how to unroot, remove twrp, remove magisk, remove adb+fastboot and everything else that had been done in the process of rooting+modding. (root as per https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6t-with-magisk-0190586/ ) (stereo mod as per https://forum.xda-developers.com/oneplus-6t/themes/magisk-stereo-speaker-mod-oneplus-6t-t3860041)
Actually, i am a total newbie/non-techie. But right after updating to os 9.0.7, i took fancy to having a stereo output through the earpiece, too. But in the end, there was no sound from the earpiece. Also, i found some other complications in other sections of the phone, although i don't know whether they were related/due to the stereo mod or the rooting process. And being a non-techie, I did not want to tinker with my phone any further. So, i decided to roll back and intuitively (1)first uninstalled stereo mod from magisk, (2)then uninstalled magisk from within the magisk itself, (3)then used the case #2 method, illustrated at https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795 to go back to the stock rom.
But i find that i have still not gone fully back to the factory state. When booting, i find the screen which informs me about the unlocked fastboot status, etc., which shows that twrp etc are still on my system. I would certainly want to go back to the factory condition. Will someone of you guide me step by step (as i am a non-techie) into removing this fastboot, twrp, etc. and bring me back to the factory condition and also (ii)in removing any fastboot/adb related things, if any, from my windows 10 PC? I shall be very grateful, as I am scared as well as left with no further technical skill to delve further into technical misadventure. It was my big mistake to undertake this exercise, without possessing any technical knowhow, i admit.
Anyway, someone please help.
Click to expand...
Click to collapse
You can try to use msmtool, it should be fix all these problems
mauronofrio said:
You can try to use msmtool, it should be fix all these problems
Click to expand...
Click to collapse
Can you give more details about "msmtool", what it is, where to find it and how to use it? Thanks.
mnbvcxzaq1 said:
Can you give more details about "msmtool", what it is, where to find it and how to use it? Thanks.
Click to expand...
Click to collapse
As is written in the first post:
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
mauronofrio said:
As is written in the first post:
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
Click to expand...
Click to collapse
Ok. Thanks a lot. I am gonna try it.
I have a query tough. That msmtool post relates to 9.0.5. I already am on 9.0.7. Shall i still use it?
mnbvcxzaq1 said:
Ok. Thanks a lot. I am gonna try it.
I have a query tough. That msmtool post relates to 9.0.5. I already am on 9.0.7. Shall i still use it?
Click to expand...
Click to collapse
Yes it's not a problem
mauronofrio said:
Yes it's not a problem
Click to expand...
Click to collapse
Thanks to you and this XDA community, for correctly guiding/directing me to the msmtool. Msmtool saved my life. i can't thank you guys enough.
Cheers.
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
I have stock rom with TWRP, Can I relock the bootloader?
MSMTool remove TWRP?
sorry for my english..
ross92 said:
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
I have stock rom with TWRP, Can I relock the bootloader?
MSMTool remove TWRP?
sorry for my english..
Click to expand...
Click to collapse
First post is pretty clear. If you don't know what to do go with the fastboot method, the local update method (if that's what you did with full OTA) must have overwritten your recovery anyway. Boot in recovery to see which recovery you have.
Hello,
I used your fastboot guide yesterday to recover my phone but I accidently flashed a newer version (9.0.10) then I had (9.0.7).
Do I need to reflash my device? If so with what method?
Steps I did:
1. Boot TWRP and wiped all except Internal Storage
2. Reboot in to the bootl;oader
3. Unpacked 9.0.10-OnePlus6TOxygen_34_OTA_017_all_1812111237_f52c4612-FASTBOOT.zip
4. Used flash-all.bat
5. Phone rebooted and working
I did not used TWRP because it did not show the correct internal storage??? If antone knows how to fix that please let me know using latest blu_spark TWRP
Hi,
about 2 years ago I rooted my S2 Galaxy Tab (T719) and now I would like to upgrade from Android 6.0.1 to Android version to 7 or 8. I have googled for instructions on how to upgrade a rooted S2 Tab but did not find anything useful (most info is on OTA upgrades which no longer works on rooted devices). Could someone please post step-by-step instructions (please bear in mind that I only ever deal with this kind of thing once every 2-3 years so I do not have much experience). I have TWRP v 3.0.2 installed (do I need to update this as well?) and the tablet is not encrypted (so hopefully I won't have to wipe the system partition and re-install all the app?!?). Thanks.
I also noticed that there is now a huge variety of ROMs out there. How can one know which ones are trustworthy? The main reason I rooted the tablet was to be able to increase privacy (control app permissions with XPrivacy). So I do not want to install some custom ROM that maybe contains spyware or other compromising features. Any advice on this would be greatly appreciated. Given my motivation (privacy) for rooting, would it maybe be better to go back to Stock ROMs (i.e. non rooted) and simply control web access via netguard (by preventing net access for some apps, they may still spy on my contacts, location, or email but cannot phone home to transmit the information)? At least I would still get OTA updates because being excluded from the OTA channel also poses a security risk in itself I suppose. Ok so any advice would be appreciated.
Thank you in advance!
There is no official Android 8 for our device. If you want 8 or 9 you have to install a custom ROM like LuK1337's LineageOS port. It is as safe as LineageOS is by itself on any device. Only problem you might have then is that calling is not possible anymore for now, but LTE works. If you want to use LOS, you HAVE to format data because it's not compatible at all. If you wanna stay on official Android you might keep it. Installing is done by flashing the official firmware with the correct country code over Odin. This will remove TWRP at first so you have to reflash it by Odin afterwards. For firmware download I always use: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 and Odin is found by google. If you wanna got the way to LOS you have to do all the steps I mentioned before too anyways to have a recent Modem firmware and bootloader. In that case you just have to flash LOS and OpenGAPPS by TWRP and delete /data aka Factory reset.
Regardless what you do, after ODIN is done, you HAVE TO boot into TWRP immediately to keep it from being removed by official firmware. While you are in there anyways you can install magisk to keep it from encrypting /data
Many thanks emuandco. So I guess I will stick with the Android 7 as I do not want to reformat the tablet and reinstall all the apps. I have started to download the Android 7 stock ROM, but it is taking quite long so in the meantime just to confirm, the steps to follow are:
1- use odin to flash the stock ROM (no steps required prior to this? I simply overwrite the existing ROM? I suppose that I will loose root then and need to re-root the device using the standard procedure as explained here: http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html ?)
2- use odin to flash TWRP (I will need the newest version I guess and cannot use the same as for Android 6?)
3- boot into recovery mode to ensure that TWRP does not get overwritten
4- done
Is this correct? Do I then need to reinstall Xposed, SuperSU and Xprivacy or will they be preserved?
Thanks again!
P.S.: BTW, I also found these instructions: https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 which are slightly different from http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html and require a wipe of the data partition. Does this mean that for an update to Android 7 I definitely do need to wipe the data partition? If this is the case then this would be a major disadvantage of rooting in the first place and maybe I simply flash the stock ROM and do not root at all but go the "netguard" route as mentioned in my original message?
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
emuandco said:
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
Click to expand...
Click to collapse
Deleted