Develop Bugs

Revert back to 3.2.4 from 3.5.2 community build

Hello. I'm currently running on 3.5.2 community build.
I have stock recovery and wanted to go back to 3.2.4.
I had hoped this would be a simple affair but there a few posts which state that having tried to sideload the stock rom using stock recovery the process halts at 47℅?
I had assumed this would be a straight forward process to revert back to stock?
Can anyone advise the process please?
I'm running a one+ 3 and I'm totally unrooted.

http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
use this recovery.

This won't work.
You've to flash completely stock from Naman thread
Then only u can flash any oos based rom or cm 13 rom.
Coz in latest beta built od oos firmware is changed.
So until you flash old firmware you won't be able to flash.
Sent From My One Plus 3

you can`t but they have know the issue and working on a solution: https://forums.oneplus.net/threads/oxygenos-3-2-6-mm-ota-for-oneplus-3.465753

freakzapster said:
This won't work.
You've to flash completely stock from Naman thread
Then only u can flash any oos based rom or cm 13 rom.
Coz in latest beta built od oos firmware is changed.
So until you flash old firmware you won't be able to flash.
Sent From My One Plus 3
Click to expand...
Click to collapse
Can you please help me with this i have the exact situation i would really appreciate it if you helped me step by step

so why dont you just side load twrp and flash a stock rom or you dont want to oem unlock

saadq101 said:
Can you please help me with this i have the exact situation i would really appreciate it if you helped me step by step
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3405700
If you've already flashed beta built you'll require method 2.
Sent From My One Plus 3

You must download alla in one tool kit forma oneplus 3

Samsung Galaxy A5 2017 Custom ROM and Issues with Fixes

So, I own a Samsung Galaxy A5 2017 and I became interested in Custom ROMs. So without any knowledge about flashing custom ROMs I tried it on my other Samsung Galaxy S5 and it worked flawlessly.
Thinking it would be same for my own A5 2017, I went ahead and installed TWRP Recovery and flashed a custom ROM. Little did I know that doing so will trip my KNOX and I won't be able to use secure folder and most of the Samsung apps. Thinking it would be best to switch to a custom ROM, I went ahead and flashed Lineage OS 14.1.
The flashing process completed without any error, but the device did not detect my sim cards even though I had 2 sim cards installed in it. Turns out my baseband version was displayed as 'unknown' and my IMEI was also 'unknown'. This issue took me 2 whole days to resolve and I found a fix for you guys.
To fix the baseband issue, I realized that my official stock ROM was android 8.0 and I flashed a custom ROM of android version 7.1.2 since a custom ROM with 8.0 is not yet available for this device ATM(none that IK of). So, after 2 whole days it hit me that I had to flash the stock ROM of 7.0 on my device to fix the baseband of the device.
After flashing the stock ROM 7.0 on the device, I installed TWRP again and flashed the custom ROM once again and it fixed the baseband 'unknown' issue and my IMEI was back to normal again.
Now for the Samsung apps issue, after installing the custom ROM the S Health app, Gear app did not work. So to fix this issue I had to root my phone using Magisk and then change my build.prop file to bypass the issue.
This fixed my issue and made my apps works properly and now my Gear S3 also connects properly and functions very well.
For Resurrection Remix OS Custom ROM A5 2017 (a5y17lte): https:// androidfilehost.com/?fid= 818070582850504876 (remove the spaces)
For GApps (choose arm64) (7.1): google OpenGapps ( I can't post outside links yet )
Root through Magisk or SuperSU (both work)
For changing the build.prop file:
To fix this, open build.prop in /system and change ro.product.name=samsung and ro.product.manufacturer=samsung to another brand like lg or htc (in lowercase).
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-31
For anymore issue feel free leave them in the comments and I will try and help you guys out.

I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks

Sorry for the Late Reply
drajithkv said:
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Click to expand...
Click to collapse
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.

MZainKh said:
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
Click to expand...
Click to collapse
That doesn't work on the latest updates as downgrading is blocked.

Unable to flash roms which need pie firmware

Flashing latest builds of most ROMs (ones which need pie firmware) give error 7: with message 'you need to have firmware V10.3.1.PIEMIXM or above as prerequisite to flash this rom'
Since I am on anti-rollback-3, i downloaded and flashed the non-arb version of V10.3.1.PIEMIXM firmware from the stable firmware list, but flashing the rom still gives the same error.
I tried using TWRP 3.3.1 Official, i am using redmi note 5 pro (indian version). Can anyone tell me what am i doing wrong?

avguser23 said:
Just install the normal fully arb firmware and try again
Click to expand...
Click to collapse
Is there no way to get pie firmware without getting to anti 4?

You need recovery compatible with Pie FW. Here is unofficial TWRP 3.3.1-1 working fine with Pie FW.

How to install Q roms on a device with P fw and TWRP installed? (SM-G960F)

Hello friends
I'm trying to flash custom Q roms in TWRP on my S9 (SM-G960F), but have received the same error message for any Q rom:
ERROR:
Vendor image on the device
is NOT compatible
Expected Android 10 vendor
Click to expand...
Click to collapse
I've only been able to successfully flash P roms, namely the Pie-based LightRom.
Based on the error message, it seems I need to update the firmware to Q before installing custom Q roms?
I've also seen some roms note installation requirements like "ROM Firmware Required: OneUI 2.x", which is new to me (have not seen a TW/OneUI ver requirement for roms I've used on S4, S7, N8).
May I ask someone to explain the steps required to install Q roms (eg, Havoc-OS) coming from P firmware? There seems to be some assumptions in most install instructions I'm not aware of, maybe since I am on older FW. (I am asking here, since I did not find instructions in any of the Q roms I tried)
So far, all I have done to the phone since unboxing it was to install TWRP 3.4.0, following the official guide for Exynos S9.
I am guessing I need to download latest official firmware image from sammobile or something for my device, and flash it in Odin. Is this correct?
If so, can someone explain the steps so that I can have latest FW for my device while maintaining TWRP and not bricking the device?
Thank you for your help
Extra info
(Snapshot from LightRom rom)
One UI version: 1.0
Android version: 9
Baseband version: G960FXXU6CSG4
Kernel version: 4.9.59
Android security patch level: 1 October 2019
Click to expand...
Click to collapse

UPDATE:
I installed latest firmware from Sammobile, flashed it through Odin following their instructions, reinstalled TWRP, and am now able to flash Q roms.
For those who have stock rom < Q, I would suggest updating firmware through OTA before flashing TWRP. If you cannot OTA, download the latest firmware from Sammobile and flash it through Odin following their instructions, then flash TWRP, then you can flash Q roms.
So:
Update firmware through OTA or via Odin with latest firmware from Sammobile.
Flash TWRP
Flash whatever rom you want.

Question What is firmwire

So i have this mi 11 lite device (lisa) and when i was flashing awoken os rom after flashing i was sidedload the firmware i downloaded from Xiaomi website..but after flashing it only went to bootloop but when i flashed pixel os rom and downloaded their firmware that was included with the rom it worked !! So my question is can i use that firmware for every rom or do i have to download separate firmware for every other custom rom..or is it the Android version that requires the same version firmware... e.g Android 12 has one firmware that works for every Android 12 rom and Android 13 has a firmware that works with every Android 13 rom..

Every rom requires different firmware . U can download the proper one from the rom's topics

Szuppermen28 said:
Every rom requires different firmware . U can download the proper one from the rom's topics
Click to expand...
Click to collapse
Thank you