Develop Bugs

Xperia S LT26I- nAOSProm_b26 Cannot Flash Gapps in TWRP

Gapps not Installing
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!

haris05 said:
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!
Click to expand...
Click to collapse
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.

Mirhawk said:
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.
Click to expand...
Click to collapse
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?

You have to say clearly step by step what you have did to flash the ROM or gapps.then only some1 can help you

same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..

haris05 said:
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?
Click to expand...
Click to collapse
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
Try the gapps I linked above.

Mirhawk is always a life saver for all new Comer's.

Mirhawk said:
Try the gapps I linked above.
Click to expand...
Click to collapse
thanks but still got no luck

nageswarswain said:
Mirhawk is always a life saver for all new Comer's.
Click to expand...
Click to collapse
Just helping out in whatever I can.
bojz said:
thanks but still got no luck
Click to expand...
Click to collapse
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.

Mirhawk said:
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.
Click to expand...
Click to collapse
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.

bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
Have u followed the procedure I sent you by message

Mirhawk said:
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
Try the gapps I linked above.
Click to expand...
Click to collapse
I guess am skipping one step of recovery.... gonna try that.

I did flash by using recovery and now I am successful in installing gapps using TWRP 2.8.5.
Now the other issue am facing and that is of unknown IMEI
after flashing 4-5 times the issue resolved but now am facing issue "Unfortunately Setup Wizard has stopped" and it is not letting me do anything with my phone
Any Suggestion what should I do now

bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
exactly the same problem I am facing

bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
The same thing exactly
Got Any solution to that?

haris05 said:
The same thing exactly
Got Any solution to that?
Click to expand...
Click to collapse
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.

only in this nAOSP b26 rom im facing this problem "system wizard has stopped" after installing gapps. but i tried other rom then i dont have any problem.

Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Let me try this now

Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Cannot flash using this ROM. Its giving error on installing

These Steps am Following:
1) Connected Phone on flashboot mode (By Pressing VolUp+Power Key and connecting the cable and it shows blue LED)
2) Flashed with recovery.img file in nAOSProm_b26 using flashtool (Fastboot mode)
3) Flashed with boot.img file in nAOSProm_b26 using flashtool (Fastboot mode)
4) flashed with TWRP 2.8.5 using flashtool (Fastboot mode)
5) disconnected cable and open bootloader then flashed using nAOSProm.zip file
6) wipe cache and dalvik (also treid by wiping cache/dalvik/data and other option I forgot (total 4))
7) flashed using pa_Gapps (as only this Gapps are flashed on my phone, others are giving errors)
same I followed for b25b but its giving error on 5th step mentioned above.
So what wrong am doing

TWRP bootloops

I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk

Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu

You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !

Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk

I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks

badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.

followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks

badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.

followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!

That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.

badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..

``

tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices

Can't reinstall twrp after accidently updating CM13 to CM14.

I've been running cm13 nightlies on my OP3. I haven't updated in a couple weeks and last night i got a notification that there was some new updates. Since it's been a while i decided to do the update so i let the cmupdater do it's thing and went to bed. This morning i wake up and was greeted with a very cranky phone. I noticed i was having trouble with any google related app, and also popups of google apps crashing. So i go to settings and I see that my phone has been updated to CM14!
well that would explain the Google apps pproblem. I was going to flash gapps for 7.0 but i couldn't get into recovery. I had twrp installed but now i couldn't get into it. the phone reboots, shows the oneplus logo then shuts off. Then i decide to reflash twrp. i put the phone into fastboot mode and from my pc command prompt, tried the fastboot flash recovery. img. it says it was successful but i still can not boot into recovery. I made sure debugging was on and I also accepted my pc key when asked on the phone before booting into fastboot mode. I realise this is a dirty flash but is there anyway of recovering from this ? i usually flash the nightlies myself from the recovery,i don't know why last night i used the cmupdater.

You probably got it going by now but in case. Which version of twrp are you trying? I would try the latest twrp-3.0.2-23-oneplus3.img. Make sure OEM unlock is checked in device manager, root is allowed as well, try an app like flashify or something that can flash an image from within the OS and see if you have better luck.

Ducter said:
You probably got it going by now but in case. Which version of twrp are you trying? I would try the latest twrp-3.0.2-23-oneplus3.img. Make sure OEM unlock is checked in device manager, root is allowed as well, try an app like flashify or something that can flash an image from within the OS and see if you have better luck.
Click to expand...
Click to collapse
Thank you for your help. I couldn't try the flashify route as it would not install. Something about parsing the package failed. I did manage to fix it by downloading the latest twrp you suggested and flashing that. After that I was able to boot into recovery and flash pico gapps 7.1. Unfortunately that wiped out all of my apps but at least i didn't lose any of my files. Thanks again.

pdrift said:
Thank you for your help. I couldn't try the flashify route as it would not install. Something about parsing the package failed. I did manage to fix it by downloading the latest twrp you suggested and flashing that. After that I was able to boot into recovery and flash pico gapps 7.1. Unfortunately that wiped out all of my apps but at least i didn't lose any of my files. Thanks again.
Click to expand...
Click to collapse
Glad you got it going, I see now that I mentioned device manager... No clue where that came from lol, was suppose to be developer options. Regardless, you got it and that was the goal.

Help. Stuck in TWRP boot loop after downloading latest update OTA

Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc

Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads

Puddi_Puddin said:
Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?

Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
After you've flashed the full zip, flash also the latest stable version of SuperSu (2.79) and latest TWRP from @eng.stk (the v11, it solves the dm-verity error). Then reboot to recovery, it should appear TWRP and the error should't appear.

Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
There are quite a few versions of TWRP from eng.stk (bluspark). Which one did you install? Try version 11 which is supposedly for N or 3.0.2-19 or 23.

Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:

Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
Try the other two given by me.

Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.

tnsmani said:
Try the other two given by me.
Click to expand...
Click to collapse
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
let92 said:
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.
Click to expand...
Click to collapse
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.

Zingapuro said:
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.
Click to expand...
Click to collapse
Unfortunately I haven't tried to update the phone yet, so I don't know what else you can do. But you can also follow the guide posted by @Viper The Ripper here:
https://forum.xda-developers.com/showpost.php?p=70499899&postcount=5
I think that it's simpler and I'll follow that one this weekend when trying to updating my phone

Zingapuro said:
Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc
Click to expand...
Click to collapse
In my opinion, the only thing you can try is to make a data backup from recovery to any external storage (like a pendrive) by Otg, but it takes some risks. In case this partition has been damaged, you can get issues when you install the rom.
The safest you can do is clean installation in spite of you lose data so, full wipes and a new full rom.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Good luck :good:
P.D.: I have formated system partition, so I lost the android configuration

satisastur said:
You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
P.D.: I have formated system partition, so I lost the android configuration
Click to expand...
Click to collapse
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?

Zingapuro said:
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?
Click to expand...
Click to collapse
Yes, I was on f2fs before this happens, so I only have to install all without formating data. You should do a manual backup to do that, once on recovery, you be able to enter phone data partition from windows. Copy all folders you want to save before formating to f2fs in recovery. Other setup and configuration like ringtones and stuff, all cache and configuration of apps, wallpaper, led, colors and themes... you will lost it. I don't know how to backup that, but its the worst part of formating data... google backup doesn't save all the config
You will start with the android phone start menu, like new, with new dactilar and patron security, etc...

@Zingapuro
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.

tnsmani said:
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.
Click to expand...
Click to collapse
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
satisastur said:
Copy all folders you want to save before formating to f2fs in recovery.
Click to expand...
Click to collapse
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.

Zingapuro said:
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.
Click to expand...
Click to collapse
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
It will fix most of your issues.
For going back to full stock use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
I hope everything will go back to normal.

Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?

Zingapuro said:
Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?
Click to expand...
Click to collapse
Great!
I think you can edit the thread title

Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:

MASSIVE brick: error messages

Hey guys. I'm going crazy for days. I tried to root my T805 and something went wrong. After rooting and after the reboot there appeared many many error massages like "Google service stopped" or "android..... stopped". You can't really skip them because they are coming over and over and over. After some time it rebootes by itself and voila same issue... makes it unuseable. So right here nothing special I thought. Just flash the stock rom over it with odin and you will be fine. But whatever kind of rom or firmware I tried to flash I'm getting the same issues. Plus after every flash I got stuck at the Samsung logo incl. some vibrations in intervals. So when I get stucked (over 20 min) I have to force shutdown it and yeah it starts and hello error messages.
I rooted and flashed so many smartphones and tabs and I've never seen a problem like that. Please oh please try to help me. Probably I'll donate you some dollars for the perfect hint or solution, I'm really desperate.

Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM

mihailrusia said:
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
Click to expand...
Click to collapse
Yes. Every time I'm flashing I wipe befor and after it. And after I tried LineageOS the same happend with the error messages . But now after flashed stock ROM again it seems now that I'm totaly stuck at the Samsung logo. Even when I try to reboot and reflash I get stucked at the logo with these vibrations.
Thanks for your reply.

Ok now I'm not stucked at the logo but get the error messages again...

Are you flashing the last firmware and system and data are on ext4?

mihailrusia said:
Are you flashing the last firmware and system and data are on ext4?
Click to expand...
Click to collapse
Yes I'm flashing the latest. About the filesystem... I'm not sure. Where can I look at the filesystem? In Recovery? What I reached in the last houres: I flashed LineageOS again WITHOUT Opengapps. And boom ist startet pretty well but yea now I have no google playstore and such stuff. Now I'll try to flash the opengapps stock over the ROM using the TWPR.
Edit: I looked at the filesystem, it's ext4

You can view the partitions with DiskInfo
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=es
Install the pico gapps

So now I flashed opengapps stock again and I'm now stucked again in at the Samsung logo. I have to hard reboot now and yeah I think there will be the error messages. But I'll try the Pico version of opengapps like you said.
Edit: I didn't have to hard reboot it. It booted by itself after some minutes but yea with the errors. After some errors it shutsdown and reboot... and so on.

If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work

mihailrusia said:
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
Click to expand...
Click to collapse
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2

Metero said:
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Click to expand...
Click to collapse
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205

mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
Thanks for searching. I'll try this next. (Give me some minutes )

mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.

Metero said:
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Click to expand...
Click to collapse
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.

thejase said:
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
Click to expand...
Click to collapse
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany

Metero said:
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Click to expand...
Click to collapse
Try using https://forum.xda-developers.com/ga...olkit-unified-android-toolkit-galaxy-t2998205
This should take you back to stock as if the tab was new. It has many many features, including rooting the tablet for you. It runs in windows ( hopefully you have). Habben Sie einen guten Tag! (is this right? I love German but I am just learning)