Database Info

6045i usa latest 5.0.2-01001

hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.

OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.

Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..

lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.

famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?

tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.

famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:

tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.

famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.

tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.

famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao

tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.

famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.

I need to edit build.prop file on my J3 without root. Is it possible?

Hello team. I need to edit build.prop file on my J3 but I cannot root.
My understanding is that this is possible using custom recovery, just mount the system partition and push and pull the file file with adb. The problem is my handset (SM-J330FN) is running Android 8, and I think only custom recovery exists for Android 7. I tried installing the TWRP I found for Android 7, but the phone just boot loops, get stuck at Samsung logo and reboot. Don't think I can use this Android 7 TWRP with Android 8.
So next plan, I tried to wipe and install Android 7 firmware instead, but Odin said no. I take UK BTU firmware from updato.com the same way I do with Android 8 but it gets to the first stage and Odin says FAIL!
Can anyone provide a suggestion for how I can edit build.prop without root? I don't care how - maybe I can find a custom recovery for Android 8, maybe someone can help with why I can't install the Android 7 firmware, maybe someone knows of a way I can do a 1 time boot to recovery image (have used "fastboot reboot recovery.img" in the past but am aware that Samsung bootloader does not support fastboot). Maybe I can do it with root and remove the root after? Root needs to be not detected so I can use certain tools.
Any advice hugely appreciated

marshedpotato said:
Hello team. I need to edit build.prop file on my J3 but I cannot root.
My understanding is that this is possible using custom recovery, just mount the system partition and push and pull the file file with adb. The problem is my handset (SM-J330FN) is running Android 8, and I think only custom recovery exists for Android 7. I tried installing the TWRP I found for Android 7, but the phone just boot loops, get stuck at Samsung logo and reboot. Don't think I can use this Android 7 TWRP with Android 8.
So next plan, I tried to wipe and install Android 7 firmware instead, but Odin said no. I take UK BTU firmware from updato.com the same way I do with Android 8 but it gets to the first stage and Odin says FAIL!
Can anyone provide a suggestion for how I can edit build.prop without root? I don't care how - maybe I can find a custom recovery for Android 8, maybe someone can help with why I can't install the Android 7 firmware, maybe someone knows of a way I can do a 1 time boot to recovery image (have used "fastboot reboot recovery.img" in the past but am aware that Samsung bootloader does not support fastboot). Maybe I can do it with root and remove the root after? Root needs to be not detected so I can use certain tools.
Any advice hugely appreciated
Click to expand...
Click to collapse
You obviously ignored my reply I gave you yesterday.
As I already stated TWRP fully supports your device on Oreo.
Your issue is not reading the thread properly.
All you need to do is explained in the TWRP OP.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056

ashyx said:
You obviously ignored my reply I gave you yesterday.
As I already stated TWRP fully supports your device on Oreo.
Your issue is not reading the thread properly.
All you need to do is explained in the TWRP OP.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056
Click to expand...
Click to collapse
Hello, if you look at the times you will see that i made this post before I commented on yours!
I did not ignore your message, I just had not seen it yet.
As it turns out, you were right - I just tried again, taking extra care to follow instructions exactly and this time it works.
Leaves me with mixed feelings, because I am really grateful for the great development work you have done to help people like me, but also the way you are speaking to me above was a bit rude and I do not deserve that just for a small mistake. I was polite.
Thank you regardless.

marshedpotato said:
Hello, if you look at the times you will see that i made this post before I commented on yours!
I did not ignore your message, I just had not seen it yet.
As it turns out, you were right - I just tried again, taking extra care to follow instructions exactly and this time it works.
Leaves me with mixed feelings, because I am really grateful for the great development work you have done to help people like me, but also the way you are speaking to me above was a bit rude and I do not deserve that just for a small mistake. I was polite.
Thank you regardless.
Click to expand...
Click to collapse
There's a difference between being rude and being direct.
I am the latter.
Nothing personal was included in my reply nor was it intended to be.
You're upset, but I also get upset when people cannot seem to take the time to read the descriptive instructions I've included in my posts.
Trust me, it takes far longer for me to create this stuff than for yourself or anyone else to read and apply the instructions.
Don't be offended it's just frustration from my end manifesting itself in my posts.

Qualcomm Crashdump

Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.

grego34 said:
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom

[email protected] said:
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
Click to expand...
Click to collapse
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.

grego34 said:
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
Click to expand...
Click to collapse
I have had luck with this downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!

TexnoViking said:
I have had luck with //oxygenos.oneplus.net/fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
Click to expand...
Click to collapse
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.

grego34 said:
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.

TexnoViking said:
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
Click to expand...
Click to collapse
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.

grego34 said:
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
Click to expand...
Click to collapse
Great! I am glad you managed to fix your phone! Enjoy

ROOT- HELP Needed

Hi guys,
I tried looking for this info on different forums online, couldn't really get to it.
TL;DR version- Need help unrooting/rooting back properly after update.
Anyway, I rooted my phone using Mac, OP7(phone) and some YouTube guide, and it worked like a charm. (Magisk, TRWP, the iso image, etc)- the only hiccup was I lost app data, but story for another day.
However, everything stopped working after an UPDATE!!
Thus, now I am caught between two worlds, where my phone is rooted- fastboot, but I am not getting any advantage- my adblock app(which had inspired this quest), or magiskhide(banking apps) are not working.
I tried doing the process again, but I think I am missing the right .zip files or versions, searching for them online is becoming a rabbit-holey adventure to no avail.
Attaching what I think are relevant files, for version details.
Thanks kindly.

saurabh_op7 said:
Hi guys,
I tried looking for this info on different forums online, couldn't really get to it.
TL;DR version- Need help unrooting/rooting back properly after update.
Anyway, I rooted my phone using Mac, OP7(phone) and some YouTube guide, and it worked like a charm. (Magisk, TRWP, the iso image, etc)- the only hiccup was I lost app data, but story for another day.
However, everything stopped working after an UPDATE!!
Thus, now I am caught between two worlds, where my phone is rooted- fastboot, but I am not getting any advantage- my adblock app(which had inspired this quest), or magiskhide(banking apps) are not working.
I tried doing the process again, but I think I am missing the right .zip files or versions, searching for them online is becoming a rabbit-holey adventure to no avail.
Attaching what I think are relevant files, for version details.
Thanks kindly.
Click to expand...
Click to collapse
Hello,
please check out this guide at first, It covers the majority of questions and files needed for rooting

strongst said:
Hello,
please check out this guide at first, It covers the majority of questions and files needed for rooting
Click to expand...
Click to collapse
Thanks for pointing that out.
Just to be clear, I am to perform the whole flashing-and-rebooting exercise with the zip, and image files(of TWRP, magisk) given in the links on the post you mentioned?
I am asking specifically w.r.t. version-updates, since the post is a bit old.

saurabh_op7 said:
Thanks for pointing that out.
Just to be clear, I am to perform the whole flashing-and-rebooting exercise with the zip, and image files(of TWRP, magisk) given in the links on the post you mentioned?
I am asking specifically w.r.t. version-updates, since the post is a bit old.
Click to expand...
Click to collapse
The thread is updated recently by myself and I'm still using the OP7, now with Android 11 hence it should also work. Noone wrote that it's not working anymore at a specific step.
Your bootloader should be still unlocked hence you can skip this step.
TWRP 3.4.0-10 and latest magisk stable(not canary) should work.

strongst said:
The thread is updated recently by myself and I'm still using the OP7, now with Android 11 hence it should also work. Noone wrote that it's not working anymore at a specific step.
Your bootloader should be still unlocked hence you can skip this step.
TWRP 3.4.0-10 and latest magisk stable(not canary) should work.
Click to expand...
Click to collapse
Hey,
Thanks a lot for the prompt replies.
My TWRP got flashed properly. But I am having issues with the "Magisk.zip" file, little digging around has led me to the discovery that Magisk manager and Magisk have been combined. In any case, I am unable to find the "Magisk.zip" file link in the GitHub directory.
Further digging proposes a method where some "customrom.img" file has to be patched via the application.
In any case, my Ramdisk on Magisk app is now a yes- this seems important.
And, I want to "I -want-to-say" flash Magisk but lacking the lead.
P.S- yeah, I didn't realise the update date was mentioned below, thanks again. I apologise in advance for other "noob" questions, I think I posted the question also in the wrong place- I'll try and keep up. Cheers.

You can use this attached one if you don't find a zip. For the first rooting: You can patch img files with the app and flash it, that's new since magisk 22 but not so convenient in my opinion.
The update process remains the same as described in my guide(using the magisk app).

strongst said:
You can use this one if you don't find a zip.
Click to expand...
Click to collapse
I figured it out man. Thanks again.
The step I was missing is "magiskvxx.apk" has to be renamed as "magiskvxx.zip".
Cheers.

saurabh_op7 said:
I figured it out man. Thanks again.
The step I was missing is "magiskvxx.apk" has to be renamed as "magiskvxx.zip".
Cheers.
Click to expand...
Click to collapse
exactly, it is mentioned here(as reference for others): https://topjohnwu.github.io/Magisk/install.html

Question Recovery and Rooting

I am coming from a OnePlus 5, I literally just got my hands on OnePlus 9 a couple of hours ago. It looks like a few things has changed and things are not as straight forward as flashing a zip file in TWRP. I have been reading through a few things and just want to ask some questions.
Is TWRP even needed anymore? Most instructions on flashing roms is done via sideloading and booting into recovery via fastboot (some requires OSS while others LOS recovery).
What is the easiest way to root (on OSS 12)? Seems to be a good mixture of different ways to root and reading comments does not make it any easier, if anything even more confusing.

Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.

posar said:
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
Click to expand...
Click to collapse
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.

Z-Blade said:
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Click to expand...
Click to collapse
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.

posar said:
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
Click to expand...
Click to collapse
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.

Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Yeah, it seems as if the simple TWRP days are over, at least for OnePlus. Maybe someone smarter than me will get it working flawlessly.

Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.

JustLeoSC said:
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
Click to expand...
Click to collapse
I downloaded the patched boot.img from the link below and I recommend you also down the normal stock boot.img as well.
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
In that thread there is a link to a 'Great root guide', I used that root guide and the patched boot.img to root Android 12.

Nice! After several tries, some softbricks and a lot of haste for the different methos I finally got it rooted. Thank you man, it worked like a charm!