Related
***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
webelan said:
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
Click to expand...
Click to collapse
Hi Anne,
We all have the same trouble with storage on our J5.
If you chose to root your phone then yes you will be able to uninstall alot of the bloat ware that is on your phone.
You will also have the option of using adaptable storage.
There are lots of threads on here that will guide you through the process. Just make sure that you read the guides properly and download and install the CORRECT zips.
I don't know if the one click root is safe to use.
I would advice installing TWRP and then flashing super su. Again all of the guides are on here.
If you do install TWRP via Odin then you will have the option of flashing custom ROMs..
Have a good look at the guides. Ask all the questions that you need to. People in here will be happy to help.
It's really nice to see you on here
Have fun
John
Don't need root for adoptable storage.
Hi
Did u get the info that you need ?
Rooting
johnhux7 said:
Hi
Did u get the info that you need ?
Click to expand...
Click to collapse
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
webelan said:
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
Click to expand...
Click to collapse
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
johnhux7 said:
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
Click to expand...
Click to collapse
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
webelan said:
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
Click to expand...
Click to collapse
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
webelan said:
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
Click to expand...
Click to collapse
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
more woe
johnhux7 said:
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
Click to expand...
Click to collapse
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
webelan said:
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
Click to expand...
Click to collapse
It sounds like the app has been corrupted, don't really know how to best advice you.
It sounds like you have to do s factory reset.
I would install a custom ROM.
The only trouble with this is that all the roms have just been shut down so you will have trouble downloading any.
Why model do you have ?
If you want to use a custom ROM pm me and I will send you a link.
The custom roms are much better (in my opinion )
John
Sent from my j5nltexx using XDA Labs
#Henkate said:
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
Click to expand...
Click to collapse
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
webelan said:
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
Click to expand...
Click to collapse
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Having a similar issue, i have got my phone so it boots to TWRP 3.1.1-0 but cannot find a ROM file that will install, they all seem to be for j5nlte, even if the file name states j5nltexx. I have tried to ammend/remove the assert lines in the install package to no avail...
any advice would be good
Thanks in advance
PB
ashyx said:
Don't need root for adoptable storage.
Click to expand...
Click to collapse
Then what to do
#Henkate said:
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Click to expand...
Click to collapse
Please work on camera that is the only thing cm 12.1 lackss thank youu
" " Can't be installed. Try again, and if the problem continues, get help troubleshooting.
(error code: -504) is all I see whenever I attempt to download a new app or (more recent) try to update apps (I was only able to update until last night).
Can't sideload any apks either. "app appears to be corrupt" is all I get.
TB is the only way I'm able to install apps after setting up from a fresh Rom flash.
I really need help with this and would be extremely grateful if someone could tell me what to do. I've been having this problem for about a week now and I can't seem to figure out how to solve it.
I have an lgV20 rooted running the latest WETA 5.0 Rom (I've just switched from the latest Megarom ) I don't have these issues among the first hours after flashing so I've been careful with my setup but it keeps happening.
I have an a 128gb sd card with 29+gb left and there's 27+gb of storage on the internal memory.
(I'm constantly deleting things in hopes that this is the issue.)
With either Rom I keep root and use various apps such as tb, lucky patcher, & various other root reliant apps.
I've been flashing and rooting android devices since 2010 and I've never had this problem until now. I also have an LG V10 rooted with xposed (no problems whatsoever).
I've done so much to try and fix it that I'm running out of ideas. The last I have is to rollback to a previous build (h91810i)and stay there. I really don't want to because everything's perfect aside from this issue.
I don't know if this is a nougat issue, or a V20 security issue, but I'm stuck.
Please, if someone knows of a solution share it with me.
Also, I've tried every fix I could find online with no luck but any ideas would be accepted at this point.
Its probably Lucky Patcher causing issues. Try to do it with Lucky patcher not installed.
me2151 said:
Its probably Lucky Patcher causing issues. Try to do it with Lucky patcher not installed.
Click to expand...
Click to collapse
Thanks I think that lucky patcher was the problem. Too bad though, it's a great app.
KJOM said:
Thanks I think that lucky patcher was the problem. Too bad though, it's a great app.
Click to expand...
Click to collapse
It is lucky patcher, happens to me when I do the PATCH TO ANDROID
Still_living714 said:
It is lucky patcher, happens to me when I do the PATCH TO ANDROID
Click to expand...
Click to collapse
Aw wow... So I can still use lucky patcher as long as I don't use the modd3d play store and patch to Android?
KJOM said:
Aw wow... So I can still use lucky patcher as long as I don't use the modd3d play store and patch to Android?
Click to expand...
Click to collapse
Yeah you can but let's not talk about it anymore since LP can't be talked about on XDA.
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there
Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards
[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...
g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.
11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).
mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).
mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup
xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).
It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.
Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM