Database Develop

New to device and the whole firmware thing

OK, long story short. Came for the nexus 6 and nexus 6p to oneplus 3t. The 6p had to flash vendor.IMG after every new ROM flash. But what is this whole firmware thing in this device? I have tried to find answers before asking but, what should I DO and NOT DO to have a brick? Like, wanting to go from a nougat ROM to an Oreo ROM, but not sure how. And then if I wanted to go from a n/o ROM to a beta, not sure how...then if I wanted to downgrade from an o or beta ROM.......please help

Treat the OP3T pretty much the same as you would the Nexus 6. The only difference is, like you've discovered, that OnePlus provides firmware files rather than factory images.
The installation instructions for the different firmwares (stable and beta) are found in the first few posts of the respective threads:
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240

It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)

Mizart said:
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Click to expand...
Click to collapse
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?

jamescable said:
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
Click to expand...
Click to collapse
I'm not entirely sure but in most cases the ROM would simply refuse to flash. Like for RR, if you don't flash a correct firmware then the flashing returns an "Error 7" and the installation stops. But even if it does flash through, it would either not connect to a network or get stuck in a bootloop, but nothing too serious which you can't rectify.

[GUIDE] [F.A.Q.] [chef] [TREBLE] Common Hurdles and Solutions for First Timers!

This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.​
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI. ​
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.​
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update. ​
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!​

Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!

Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/

DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.

[Guide] [SM-T350] Root and Update Galaxy Tab A 8.0 to ANDROID PIE

I am not responsible for bricked devices, or any other hardware malfunctions that come as a result of flashing anything. Please do some research if you have any concerns about features included in this ROM before flashing it
Hey everyone,
I am writing this guide because I spend all day trying to figure out how to upgrade my grandma's tablet from android 7 TouchWiz to android 9 pie. I did not create any of the files that I am about to link just putting all the info in one place because I feel it's needed.
Before starting my grandam's tablet was running android 7.0 TouchWiz. So if you are in the same situation do the following.
Download the following
Odin3-v3-10-7
SM-T350 Marshmallow Firmware (check second post for faster mirror)
TWRP-3.2.1
PIE ROM of Choice
Open Gapps (Remember Platform: ARM | Android Version : 9.0| Variants: Your Choice)
Root (Optional): Magisk
Instructions
1. Put your tablet in download mode by turning it off then pressing and hold [Power] [Vol-Down] & [Home] at the same time till a cyan warning screen appear.
2. Press Volume Up to Continue.
3. Connect the Tablet to the computer via USB stick
4. Extract the Odin and Marshmallow Firmware zip files and place it on the desktop
5. Run Odin and make sure you can see your device
6. Click on [AP] button and find the marshmallow firmware. Let Odin verify the file (take a second) then click start to begin the flashing process
7. After flashing the firmware the tablet will reboot and just wait for the welcome screen.
8. In the welcome screen skip everything till you get to the home screen then turn the tablet off and put it back into download mode (see step 1)
9. Now your tablet should still be connected to the computer and Odin should still be open.
10. In Odin go to the second tab (OPTIONS) and uncheck Auto Reboot (VERY IMPORTANT)
11. Now click on the [AP] button and find the TWRP zip file then click start to flash it
12. After the flashing process has been successful press and hold [Power] [Vol-Down] & [Home] to reboot. AS SOON AS THE SCREEN GOES BLACK LET GO OFF THE BUTTONS AND PRESS AND HOLD [POWER] [VOL-UP] and [ HOME] AT THE SAME TIME.
13. If you did it right you should be in TWRP. If not you have to repeat step 11 and 12
14. Make a NANBACKUP in TWRP and copy it to your computer
15. After that copy the PIE ROM and GAPP of your choice. (MAGISK IF YOU WANT ROOT) to the internal memory card or sd card whichever you have. I don't have an SD card so I copied it to the internal memory
16. In TWRP Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)
17. Flash the ROM, GAPPS
18. Flash the root solution of your choice (optional).
19. Reboot your device.
Thanks to @lividhen99 for the post that I got all this info
Thanks to everyone who creates and ported recoveries and ROM to this device. My grandma appreciated it ( we both hate TouchWiz)
PS. I will eventually come back and make a mirror of the marshmallow firmware file because it is so long and slow. If anyone wants to beat me to it please do

https://drive.google.com/open?id=1WyafpwMlGbBmocWhwhHxcrtgS0mFpoes
Heres a google drive mirror.

Is there a 64 bit version of Android Pie for the SM-T350? After following these instructions I couldn't install the 64 bit version of GApps, said it was not compatible. Is that a holdover from the Marshmallow firmware? The SM-T350 supposedly has an ARM 64bit processor so you'd think it could take the 64 bit GApps install but after these updates it shows that it'e the 32 bit version of Pie. I know I'm kind of rambling here but I guess you can follow what I'm trying to do. Thanks!

is this compatible with the sm-p355?

Is it necessary to do this from Marshmallow 6? Will this procedure work for Nougat 7.1.1?

Wimmer4Archery said:
Is it necessary to do this from Marshmallow 6? Will this procedure work for Nougat 7.1.1?
Click to expand...
Click to collapse
It should technically work, but if you get a black screen, downgrade to marshmallow and try again. Not all devices need to be downgraded, and nobody knows why

Great, thanks for the info! This sounds like a, great summer project while we are all locked in quarantine.

2 different PIE roms, when I follow the path to add an account (google) the screen goes black with small top bar icons and does not allow the process to continue (setup). which specific ROMS have worked>

ygthb said:
2 different PIE roms, when I follow the path to add an account (google) the screen goes black with small top bar icons and does not allow the process to continue (setup). which specific ROMS have worked>
Click to expand...
Click to collapse
Same issue. Hopefully someone has an answer

sunnyd71 said:
Same issue. Hopefully someone has an answer
Click to expand...
Click to collapse
Could you and ygthb send me the links for the rom's forums? in fact, you might want to ask the question on the rom's respective forum.

lividhen99 said:
Could you and ygthb send me the links for the rom's forums?
Click to expand...
Click to collapse
if ur talking about a tab a then youre in it already

elliwigy said:
if ur talking about a tab a then youre in it already
Click to expand...
Click to collapse
This is a thread on how to install roms on this device, it provides no roms besides the marshmallow one to fix the black screen issue.

Trying to get this to work, everything is fine until I try to load the new ROM and GAps, it's giving me error 7, specifically this:
- Confirming target device...
mount: Failed to mount /dev/block/by-name/vendor at /vendor: No such
file or directory
ui_print(): Failed to parse the argument(s)
Updater process ended with ERROR: 7

browenb said:
Trying to get this to work, everything is fine until I try to load the new ROM and GAps, it's giving me error 7, specifically this:
- Confirming target device...
mount: Failed to mount /dev/block/by-name/vendor at /vendor: No such
file or directory
ui_print(): Failed to parse the argument(s)
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
What partitions did you wipe?

I might be a little late posting here but I am currently trying this with the SM-T350 that came with 7.1.1 and for some reason when I load the Marshmallow firmware to my tablet it never actually boots, it gets as far as flashing the Samsung logo on a black background then says Touchwiz.exe has encountered an error. Am I doing something wrong? I am following the instructions word for word as far as I can tell.

The marshmallow firmware never has to boot. If you want it to boot, factory reset (wipe data and dalvik cache). But you wipe system data and cache anyway when you install a rom.

lividhen99 said:
The marshmallow firmware never has to boot. If you want it to boot, factory reset (wipe data and dalvik cache). But you wipe system data and cache anyway when you install a rom.
Click to expand...
Click to collapse
Basically I just want to use TWRP to flash Magisk and use it to spoof for Pokemon Go. I did it previously on a Galaxy S5 but I never had a problem booting into the OS and just turning the phone off when I wanted to boot into recovery mode (TWRP) so I don't really know what I am doing but I am assuming I need it to boot normally for magisk to root the device. Unfortantely when I try to flash TWRP with the 7.1.1 firmware that comes stock on the device recovery just boots to a black screen so searching around has led me to the conclusion I need to downgrade to Marshmallow then try flashing TWRP but I never expected it to not boot normally xD Sorry this is a bit outside of my technical knowledge to say the least.
---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------
I believe I understand what I need to do now. I managed to load into TWRP so at that point I can just flash any rom and use magisk to root. Any particular one you might suggest? Thanks for all the help by the way!

Gemininja said:
Basically I just want to use TWRP to flash Magisk and use it to spoof for Pokemon Go. I did it previously on a Galaxy S5 but I never had a problem booting into the OS and just turning the phone off when I wanted to boot into recovery mode (TWRP) so I don't really know what I am doing but I am assuming I need it to boot normally for magisk to root the device. Unfortantely when I try to flash TWRP with the 7.1.1 firmware that comes stock on the device recovery just boots to a black screen so searching around has led me to the conclusion I need to downgrade to Marshmallow then try flashing TWRP but I never expected it to not boot normally xD Sorry this is a bit outside of my technical knowledge to say the least.
---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------
I believe I understand what I need to do now. I managed to load into TWRP so at that point I can just flash any rom and use magisk to root. Any particular one you might suggest? Thanks for all the help by the way!
Click to expand...
Click to collapse
OH! Well, now that you have that specific version of twrp booted, I would recomend either lineage os or crdroid for the SM-T350. If you just want stock Samsung, you can reflash the stock 7.1.1 firmware and grab the Nougat twrp for the sm-T355 from ashyx's galaxy tab a twrp page here: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560 . It will boot on Nougat (7.1.1) but it cannot flash android pie (9.0) or Q (10.0) roms. It can still flash magisk though.
Crdroid (I released a newer build on the second to last page ?): https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517/page32
Lineage: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t3903258/page31
If you do end up flashing a custom rom, just wipe system, data, cache, and dalvik cache. Then flash the ROM zip, the gapps zip, and the magisk tnstaller zip. Just remember to enable magisk hide to pass safetynet whether you go custom rom, or not.
If you want the marshmallow firmware to boot, I think just wipe cache and dalvik cache. If that doesn't work, wipe data.
Wiping data will delete all your apps and settings and passwords, etc. It is essentially a factoy reset.

64 bit
Bookworm214 said:
Is there a 64 bit version of Android Pie for the SM-T350? After following these instructions I couldn't install the 64 bit version of GApps, said it was not compatible. Is that a holdover from the Marshmallow firmware? The SM-T350 supposedly has an ARM 64bit processor so you'd think it could take the 64 bit GApps install but after these updates it shows that it'e the 32 bit version of Pie. I know I'm kind of rambling here but I guess you can follow what I'm trying to do. Thanks!
Click to expand...
Click to collapse
the device isnt capable of running ARM64 however you can find regular ARM variants of lineageOS (what i used instead of flashing the stock firmware) and of gapps. my galaxy tab a (sm-t350) now runs android 10 and gapps 10.0 full, through this guide. just ignore the first software package and continue with the guide.

help! flashed from stock firmware (i don't remember version)...after a lot of time, is in the wizard section with a lot of error (unfortunately the process xxx has stopped), and the tablet reboot...what should i do?

going to back to custom ROMS

hello, I used to be a custom ROM junkie in the past but after some time i got bored and never did it again.
now looking at my current device which i never installed a customer ROM before its quite old as its running Android 8 and i would like to jump to 10 or 11.
I am confident i understand the process but its been a few years and i have some questions:
-for example this is the 1st device i encrypt so i am not sure if this affects.
-the device has no custom recovery so i have to start there but not sure if i have to remove encryption or if its ok.
-Also i would like to see if you have any advice for me or somehting i should pay attention beside install TWRP, format all but storage and install zip file for custom ROM
Thanks

masterchop said:
hello, I used to be a custom ROM junkie in the past but after some time i got bored and never did it again.
now looking at my current device which i never installed a customer ROM before its quite old as its running Android 8 and i would like to jump to 10 or 11.
I am confident i understand the process but its been a few years and i have some questions:
-for example this is the 1st device i encrypt so i am not sure if this affects.
-the device has no custom recovery so i have to start there but not sure if i have to remove encryption or if its ok.
-Also i would like to see if you have any advice for me or somehting i should pay attention beside install TWRP, format all but storage and install zip file for custom ROM
Thanks
Click to expand...
Click to collapse
You've missed all the fun with the upgrade to OOS 9.
So, you'll need to upgrade your firmware to 9.0.6 because all the latest ROMs require it. Take your time and carefully read https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055.
You do not need to remove encryption (depending on how you upgrade your firmware).
If you've got a locked bootloader (which I'm expecting you do), them you need to unlock it so that you can flash TWRP. And unlocking will wipe all data from your phone. So backup everything you want to keep to your PC.
If you don't boot into recovery after flashing TWRP and install a patched boot image (see https://forum.xda-developers.com/on...ty-disable-oxygen-os-t3922324/post79357241)or flash Magisk, and reboot your phone, you'll lose TWRP because OOS automatically restores the stock recovery.
So the order is:
1. Backup
2. Unlock bootloader
3. Flash TWRP
3. In TWRP flash patched boot image (remember you're still on OOS 5.x so use the right one!) or Magisk.
4. Have fun moving to a custom rom.
Sent from my OnePlus 3T using XDA Labs

need help with nokia 7 plus custom rom

i want to install custom rom to my nokia 7 plus, but have no experience can someone guide me throughout the process?

Hello, I will try to do this!
First, you have to unlock the bootloader, follow step by step this guide. There is also this video that can help you if you have any trouble.
After that, download and run Repartition tool on your PC having the phone connected (always with usb debugging on) and press the 4.5G (3rd) button. Wait for the process and after that it will boot on TWRP.
Choose a custom ROM from XDA and follow this guide depending on your choice. For instance, for the LineageOS (I reccomend this) that doesn't come with GApps you have to follow the second guide.
All the ROM and TWRP images are stored here.
You can find Gapps here, if you flash Lineage 19 download the first image (MindTheGapps).
Good luck with the process!