I have just bought a second-hand Oppo Find X6 Pro and it has a global ROM on it. I don't know how they did it because there's no global version of the phone. I think they might have tweaked the firmware because everything seems valid, except it hasn't got any updates and its security patch is of June which is pretty behind for this device. This is the version on it: PGEM10_13.1.1.144(EX01). The (EX01) OPPO Reno 10 Pro 5G has it and it stands for a European version, I think. That's why I say they might have tweaked something because even Google recognizes the device as OPPO Reno 10 Pro 5G. > **Check your Oppo Reno10 Pro 5G** > > Google sent a notification to your Oppo Reno10 Pro 5G. Tap **Yes** on the notification, then tap **17** on your phone to verify that it's you. So I wanted to roll back to stock firmware. I downloaded different stock ROMs, but there wasn't any way to flash them on the device. Can someone help me and go back to the stock ROM? - I tried https://oppostockrom.com/oppo-find-x6-pro-pgem10 but didn't figure it out. - I also used the QPST Flash Tool, but the firmware didn't contain anything to open it inside QPST like .hex or .mbn. It just had .elf for the programmer which when I chose it to flash the ROM, it said error FireHose. - The recovery mode also doesn't have a local update and online update. - When I reboot to EDL using adb, it just shows a black screen, but the computer does recognize Qualcomm 9008. I think the recovery is also not stock. I will attach the system information:

Summary: I am unable to revert my Samsung Galaxy Note 9 or **N9600** (Snapdragon variant) to stock firmware due to an issue where Download Mode doesn’t allow flashing, and I’m receiving error messages during the flashing attempts. When I try to enter Download Mode, I only see a blue screen with a downloading icon, and no information is displayed, unlike the usual mode where information such as "Do Not Turn Off Target" is shown. I disabled the OEM Unlock option, thinking it was the culprit and that doing so would fix the errors I encountered with Odin. Unfortunately, this only made things worse, as now I’m seeing the "Custom Binary (boot) blocked by OEM Lock" message, preventing my device from booting properly. --- What happened: 1. OEM Unlocking: OEM Unlock was enabled, but I disabled it, and after a reboot, the "Custom Binary (boot) blocked by OEM Lock" message appeared, making the phone unbootable and showing the error when starting. 2. Download Mode Issue: I’ve tried using Odin to flash the stock ROM multiple times, but it fails. When I attempt to use the SamFirm tool, I get an "**MTP Fail**" message. 3. Recovery Mode: In the past, I flashed TWRP (custom recovery) for the "crownqltechn" variant from this forum: https://xdaforums.com/t/official-twrp-sm-n9600-galaxy-note-9-crownqltechn.3845536/ and installed DotOS. To remove TWRP, I flashed the stock recovery image, believing it would help resolve issues with the bootloader. Now, I have the stock Android recovery instead of TWRP. 4. Download Mode Behavior: When choosing “Reboot to Bootloader” in recovery mode, it opens Download Mode, but it looks different from when I press Bixby + Volume Down. The usual information doesn’t show up (e.g., “Do not turn off target”). It only shows the blue screen with the downloading icon. --- What I tried: Used multiple stock ROMs from different sources (SamFirm, etc.), placed the correct files in Odin as usual, but received errors during flashing. The error messages I encountered include:

threads completed, succeeded 0 / failed 1.

Additionally, I tried changing various Odin options (like "Flash Lock" and "NAND Erase"), but they made no difference. Odin just can't deliver anything to Android while in this abnormal Download Mode. However, the phone is still recognized by Odin, and the blue box appears. Tried the ADB sideload option in the stock recovery options, but realized it’s only meant for applying software updates, and I couldn't use ADB commands either (e.g., adb getprop). The phone was in sideload mode when using the "Apply Update" option from Recovery. Downloaded and installed the latest Samsung drivers (version 1.7.61.0) to ensure proper communication between my phone and the PC, but the issue persists. --- Current Status: OEM Unlock is disabled, and I can’t access Developer Options or the OS because of the "OEM Lock" message upon boot. --- Additional Info from DM: >CURRENT BINARY: Custom > >FRP Lock : OFF > >OEM LOCK : ON > >KG STATUS : Checking > >RP SWREV : B9(1,1,1,9,1) K9 S9 Other details from Download Mode include RPMB and DID. I really don't plan to use closed-source and paid software; I just want to see what options I have.

Suppose I plan to flash my recovery with TWRP/CWM, but then later suppose I would like to move back to the stock recovery. Is it possible to take a backup of stock recovery just like we can take a backup of our ROM?

Following Google's guide for flashing/restoring the stock Android ROM, and initially using the default *flash-all.sh* shell script to flash the stock Android ROM to my device, I noticed that I am not able to do this successfully on the second consecutive attempt. When flashing the stock Android ROM the first time (usually when flashing the stock over a custom ROM or flashing the stock recovery over the existing TWRP recovery), the first attempt successfully flashes the stock Android ROM to the device and I am presented with the Android setup wizard. However, if I repeat the same flashing process once more, the device is stuck on the Android logo boot animation. I read that this is caused by the cache partition not being erased before flashing. Several tutorials have claimed that the cache needs to be wiped from within the recovery, and although I have tested this to be successful, I would prefer a method that can erase the cache during the flashing process (or an adb or fastboot alternative) without having to re-enter recovery. I have tried adding the fastboot commands to the *flash-all.sh* shell script to erase cache and erase userdata, either before or after flashing all of the partitions with those of the stock image, but it does not solve the issue. My device is the Huawei Nexus 6p and I am using the latest stock Android ROM for Angler (8.1.0 (OPM7.181205.001, Dec 2018)), which does not contain a *cache.img* file (removed since Android 8.0). I am aware that I could extract the *cache.img* file from an earlier stock image (e.g. Android 7.0) and flash that with fastboot, but I'd prefer not to have to rely on two different stock images, and one just for the archived *cache.img*. My customised *flash-all.sh* shell script, inspired by examples here and here , is as follows:

fastboot flash bootloader bootloader-angler-angler-03.84.img
fastboot reboot-bootloader
sleep 2
fastboot flash radio radio-angler-angler-03.88.img
fastboot reboot-bootloader
sleep 2
fastboot flash recovery recovery.img
fastboot reboot-bootloader
sleep 2

# no cache image (cache.img) in Android 8.0+, instead:
fastboot erase userdata
fastboot erase cache

# does not seem to flash images, even if extraced into the PWD
fastboot -w update image-angler-opm7.181205.001.zip

# ... which is the equivalent to (in the correct order) 
fastboot flash boot boot.img
sleep 2
fastboot flash system system.img
sleep 2
fastboot flash vendor vendor.img
sleep 2

fastboot erase userdata
fastboot erase cache
sleep 2
fastboot reboot

Q: What command(s) can I use during the flashing process (i.e within the bootloader) to successfully erase the cache partition so that I am not stuck on the boot animation logo upon startup?

I have a Sense TW102 and I'm trying to root my device with hours of research and trial and error trying to find a way to find stock firmware to trying to pull it off my device with no avail. Any leads or advice id greatly appreciate it.

The Realme 3 smartphone, developed by Oppo, comes in two variants: one with the Mediatek P60 chipset and another with the Mediatek P70 chipset. The global variant has the P60 chipset, while the Indian variant has the P70 chipset. The model numbers for these variants are RMX1821 for P60 and RMX1825 for P70. The question revolves around the compatibility of the ROM (Read-Only Memory) for two different chipsets. According to Realme's official website, the ROM version 'RMX1821EX_11.A.22' seems to be intended exclusively for the RMX1821 device with the P60 chipset. The concern is whether it is feasible to install this ROM on the RMX1825 device, which has the P70 chipset, and whether it will function correctly. Alternatively, it would be helpful to know if there is a separate ROM available specifically designed for the P70 chipset.

I'm trying to restore the stock firmware for a Samsung S10e. It's currently setup with the LineageOS recovery image, and the LineageOS firmware. I've rebooted in the (LineageOS) recovery, factory reset everything, and now I'm trying to sideloading the factory image (G970foo_bar_baz.zip), however, it's stuck at 0%. If I try to sideload LineageOS again, it sideloads without any problem. Should I keep waiting? Since the factory ROM is very large (5.9GiB vs 800 MiB), it's possible that it's normal that it takes a long time before the sideload starts, however, I don't know how long should I wait.

I factory reset my LG k7 phone to help with battery and storage issues, but upon reboot, I found that it was glitching up at the setup screen and says the 'Setup Wizard isn't responding. Would you like to close or wait?" on a black screen. Due to this, I had planned to go ahead and stock flash it, as I was recommended to do. Before proceeding with this, I decided to test out putting my phone in the required download mode. But when I tried disconnect it, which, for my phone model, means giving it a forced reset, it didn't respond no matter how long i held the buttons, which left me to assume it was frozen. I then pulled the battery. So my question is: should I take this reaction to being put in download mode as a bad sign and skip the stock flash? If the phone were to freeze up like this during the flashing, it would cause an interruption and a likely bricking. What should I do?

I unlocked bootloader on Huawei MediaPad T5 (AGS2-L09). Then I put TWRP on it and everything was fine until I installed UPDATE-SuperSU-v2.46.zip using TWRP. After that the tablet stuck at Huawei welcome screen. Then I found UPDATE-unSU.zip on xda-developers forum. Its author promised that it will revert changes of UPDATE-SuperSU. Now the tablet goes scrictly into TWRP and doesn't want to do anything else. How to recover it? P.S. Before to install SuperSU-v2.46.zip for the first time I noticed that many folder names in the tablet internal storage were encrypted.

I got a Samsung Galaxy C7 (SM-C7000) from China. I'm trying to install Hong Kong firmware on it and of course, got the partition size error in Odin. I searched around and found one pit file for my model Hong Kong. However, I'm concerned if it is the right file or not. The content of the PIT file: https://pastebin.com/FncY05pg . USERDATA view Can I flash the attached pit file? Otherwise, what is the correct file for my phone's Hong Kong PIT file? **My Phone** - Model - SM-C7000 - Variant - China - Storage - 32 GB

I have Karbonn A1+, android system of my phone totally hanged. i want format my phone and reinstall operating system. please suggest me method. (Android Operating System : Android 2.3 Gingerbread)

I have a Nexus 5 and root. I also use the MultiROM application. I want to create a secondary ROM from stock. However, I cannot flash factory images, hence need to make flashable zip out of it. How do I do it? What other method is recommended?

Lenovo Vibe K5 is up and running in CM 13. But, I need to flash stock ROM on it. Now, I have tried to flash with TWRP, but that didn't worked for stock firmwares. I have seen multiple tutorials, in that, they are using QPST and flashing it easily. While I am having problem, because my device shows as non Qualcomm device. It shows as RELINK HS-USB QDLoader instead of Qualcomm HS-USB QDLoader. I have installed the Qualcomm drivers correctly.

I have a Chinese HUAWEI Honor 4A and want to install a different OS without the bloatware and restrictions that come with it (eg no play store). Any recommendations on which path to choose? I just want a simple, stable, hassle free OS and the tips on the right way to do it.

sometime ago I installed Linage OS 17.1 on my MI Redmi 2 (1GB) and also resized my system partition to 2.00GB and after some time I faced some auto-restarting problems then I decided to install the stock rom and when I went to install it, In MI flash tool it gave me a error then I searched about it and found this article - https://forum.xda-developers.com/t/how-to-erase-partition-table-of-redmi-2-prime-2a.3520410/ Then I followed it but I used the rom I have downloaded from somewhere else and then I clicked flash, after 1-2hrs it was not completed then my friend suggested me to use the file given in this article and cancel the on going flashing process, so I canceled it and after that moment it is Stuck on Black screen, and not even booting into fastboot or Recovery mode and when I connect it to a power-source or my laptop it doesn't responds at all. So, if anyone from you have any solution please tell me... -Thanks

The P3113 model of the Galaxy Tab 2 hasn't yet received the Android 4.1 (Jelly Bean) update. Is it possible to install the stock ROM for the P3110 ROM (take from sammobile) on the P3113 device?

I was trying to root bluboo s8a with TWRP following this tutorial When I reached step 2 of installing the ROM with sp flash tools, the ROM installed up to the end but the phone stopped powering (doesn't show anything). I tried downloading other customs ROMs for bluboo s8 but they were customized to be flashed with TWRP because they had no scatter files. I landed on one custom ROM which I flashed into the phone with sp flash tools and the phone powered on and I could hear the sound when I press the buttons and when the phone is powering on but the screen shows a dark screen. I would like to go back to the stock ROM or a working custom ROM. I took some screenshots of the settings of the About Phone before trying the rooting process. " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> About Phone (click images for larger variants) **Update:** Now I have gotten some ROM from the seller's website. It's in a zip file with one .cpb file and a folder named dbs. The folder has two files. When I try flashing the .cpb file with QGDP, I get an error of CPB Package is not complete. How can I overcome this please?

I'm trying to flash stock firmware back to a Samsung Galaxy A51 (SM-A515F), when extracting the rom files and decrypting them from their lz4 formats, I noticed there were 2 vbmeta images (not to be confused with vbmeta_samsung, they're both named "vbmeta.img"), one was at the BL while the other was at the AP, when flashing from Odin3, I noticed that it flashed "vbmeta.img" 2 times, on Heimdall however there was only a single vbmeta partition option available instead of 2, printing the PIT also shows theres only 1 vbmeta partition, how do I flash both vbmeta image(s) to the device using Heimdall? I do not want to use a Windows vm just to get Odin working there. AGAIN, NOT to be confused with "VBMETA_SAMSUNG", I am talking about "VBMETA"

I'm rocking a OnePlus Nord 2 5G here that just recently came back from assistance because I had wiped the partitions with the IMEI stored in it... I had made a Nandroid backup, but it didn't backed up all the needed partitions to be able to restore it. So, I went searching for an alternative way to backup ALL the partitions of the phone. Mainly by the use of **adb shell** while booted in TWRP to gain root access without being rooted + **dd** for the backup. And I've made some good progress so far, but now I'm stuck. For comparison, I've donwloaded a **full stock firmware** from a third party, and these are all the files it contains: audio_dsp.img boot.img boot_para.img cache.img cam_vpu1.img cam_vpu2.img cam_vpu3.img cdt_engineering.img dpm_1.img dpm_2.img dtbo.img expdb.img flashinfo.img frp.img gz1.img gz2.img lk.img lk2.img logo.img mcupm_1.img mcupm_2.img md1img.img metadata.img misc.img my_carrier.img my_engineering.img my_heytap.img my_manifest.img my_product.img my_region.img my_stock.img ocdt.img odm.img oplus_custom.img oplusreserve1.img oplusreserve2.img oplusreserve3.img oplusreserve5.img oplusreserve6.img otp.img para.img param.img pi_img.img product.img recovery.img scp1.img scp2.img sec1.img seccfg.img spmfw.img sspm_1.img sspm_2.img super.img system.img tee1.img tee2.img vbmeta.img vbmeta2.img vbmeta_system.img vbmeta_vendor.img vendor.img vendor_boot.img Now, these are all the partitions I was able to find in /dev/block/platform/by-name and backup: audio_dsp.img boot.img boot_para.img cache.img cam_vpu1.img cam_vpu2.img cam_vpu3.img cdt_engineering.img dpm_1.img dpm_2.img dtbo.img expdb.img flashinfo.img frp.img gz1.img gz2.img lk.img lk2.img logo.img mcupm_1.img mcupm_2.img md1img.img metadata.img misc.img nvcfg.img nvdata.img nvram.img ocdt.img oplus_custom.img oplusreserve1.img oplusreserve2.img oplusreserve3.img oplusreserve5.img oplusreserve6.img otp.img para.img param.img persist.img pi_img.img proinfo.img protect1.img protect2.img recovery.img scp1.img scp2.img sec1.img seccfg.img spmfw.img sspm_1.img sspm_2.img super.img tee1.img tee2.img vbmeta.img vbmeta_system.img vbmeta_vendor.img vendor_boot.img ---------- As you can see, I'm missing a couple of partitions: my_carrier.img my_engineering.img my_heytap.img my_manifest.img my_product.img my_region.img my_stock.img odm.img product.img system.img vbmeta2.img vendor.img Including system, which is pretty strange since it's one of the main partitions. **I've no idea how to find the directory of these partitions, with their labels, and how to back them up.** ---------- These are all the solutions, tools, and similar questions I've already tried, without success: https://android.stackexchange.com/questions/92565/how-to-list-all-major-partitions-with-their-labels https://android.stackexchange.com/questions/24119/command-to-list-partitions?newreg=ae09db6d007f4614ac2b168a9eafe877 https://android.stackexchange.com/questions/5232/how-can-i-view-the-android-internal-partition-table https://github.com/for2ando/dump-android-partitions https://github.com/IzzySoft/Adebar https://github.com/dlenski/tetherback https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en_US&gl=US I just obtain the same list of partitions I'm finding, or straight not working / the directories do not exists. *Maybe because it's a MTK device?* The only app that made a difference is FX file explorer . By going in the "file systems" section I can see the my_* partitions and their directory, but no system, vendor, or others. And I'm searching for a command line solution ofc. I've contacted the user that posted the unofficial full stock firmware on XDA. I'm still waiting for the full response on what specific method he use to extract it, but for now I know he used some root solution, if that could help. Root solutions are completely fine by the way, just, no "Nandroid" as an answer please.

I'm looking to flash a stock ROM onto my phone but the SP Flash tool says it's invalid. My phone's chip is MT6771V/C. My phone is currently on Android 10. The internet (this link, for example ) has scatter files named MT6771T_Android_scatter, MT6771_Android_scatter 8.1 and MT6771_Android_scatter 9.0 and I'm not sure which one to use. I tried making a scatter file using the MTK droid tools but the only that showed up when I clicked on the "Block Map" button is [1, bmtpool, 0000000000, 0000000000, 0]