Database Develop

No sim card after twrp restore

I have a oneplus 3t and am on OOS 4.0.3 and decided to upgrade to OOS 5.0. I downloaded the ROM, took a backup and then clean wiped my phone. Then I tried installing the ROM but it failed. So I decided to restore my backup from USB OTG. While restore failed and it showed error 255 while restoring data, so I wiped again and then restored everything except data. The phone rebooted and everything is fine except the phone is not detecting my sim card. I have tried restoring again and rebooting but it didn't work. I am using twrp 3.1.1
Please give a solution or tell me which ROM version to flash to solve this problem.

Just follow this guide to get back to factory default. And then try OTA update with the default recovery instead of TWRP.
https://www.google.se/amp/s/forum.x...ck-unbrick-tutorial-oneplus-3t-t3515306/page1

You need a special TWRP in order to upgrade to Android Oreo. Just google for Oneplus3 Oreo TWRP and theres a OnePlus-Forum Thread where you can download the TWRP that is needed for the Oreo Upgrade. Your Backup should work without Problems after you installed Oreo

just install bluSpark TWRP v8.61 from
https://forum.xda-developers.com/devdb/project/dl/?id=27655
and download official 5.0.1 ROM zip file from oneplus official site.
then you can proceed. You can use Magisk 15.3 after ROM installation for root access.
Make sure to reboot TWRP once after wiping everything from TWRP otherwise you may lose TWRP where stock recovery may take place.

Back to EMUI

I can't find the way to get my Huawei P10 to Stock. Huawei eRecovery is not working for me: Getting package info failed.
I'm currently on LineageOS 15.1

I have same problem. Anything I try to flash via TWRP gives me error messages. Tried download several files with same results. Also trying to flash Google apps package comes up with version error. Even thou system images for treble project are version 8.1 it asks me to flash gapps version 7.1.2.
I also am stuck with this system image. Can not use e-recovery to restore stock system.
On top of that I was silly enough to not make backup of my previous installation.
There are plenty tutorials on how to flash project treble images but not so many of how to revert back to stock. Especially huawei devices are nowhere to be seen.

Tried to flash twrp. Can't boot into recovery anymore.

Hi i tried to root my P9. I unlocked the bootloader successfully and i can flash the recovery but i can't boot into recovery anymore. I get stuck on "Your device is booting now...". Also i tried to flash twrp onto recovery2 which is often suggested and that didn't help either. What i find weird it that adb doesn't allow me to erase a partition "FAILED: (remote: Command not allowed). Also the phone still works normal and i can use android. I also tried to flash a stock recovery but that still doesn't boot into the recovery. I couldn't find any advice online that would help me further. Hope someone can help me out.

FlxF said:
Hi i tried to root my P9. I unlocked the bootloader successfully and i can flash the recovery but i can't boot into recovery anymore. I get stuck on "Your device is booting now...". Also i tried to flash twrp onto recovery2 which is often suggested and that didn't help either. What i find weird it that adb doesn't allow me to erase a partition "FAILED: (remote: Command not allowed). Also the phone still works normal and i can use android. I also tried to flash a stock recovery but that still doesn't boot into the recovery. I couldn't find any advice online that would help me further. Hope someone can help me out.
Click to expand...
Click to collapse
You probably flashed incorrect TWRP -
you didn't even mention are you on MM (EMUI 4) or N (EMUI 5)
Different TWRP images must be used, but from the corresponding XDA Huawei P9 (MM or N) threads - not something maybe from elswhere on Internet
Also, if it didn't work from Recovery then no chance that it would work from eRecovery (if wrong TWRP, not ported to Huawei P9 and your EMUI version, it will not ecognize partitions and encryption, no matter if flashed to Recovery or eRecovery)
For example, if you didn't spoil also eRecovery, you would be simply able now to (re)Install latest firmware and recovery from eRecovery, and it would fix your stock Recovery
Otherwise, you should flash Recovery and eRecovery (extracted by Huawei Extractor from update.app, unzipped from FullOTA update.zip corresponding to your exact stock firmware and build you have).
Or, reinstall your stock firmware by DLOAD method (FullOTA-MF-PV package must be used for DLOAD)
You can also just flash the correct TWRP (but I strongly recommend to recover the stock eRecovery anyway), find the correct ports for MM, N and O here:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
https://forum.xda-developers.com/showpost.php?p=75787111
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2
If you are on Nougat, you can also find on XDA (actually, zipped in HWOTA/HWOTA7 packages from links 2 and 3 above) the so-called no-check Recovery, it can replace Recovery (but not eRecovery) img for any EMUI 5 stock firmware)
---
Btw, for Magisk (root), you don't need TWRP. Just install Magisk Manager app and patch your extracted Boot.img (MM and N, on Oreo Ramdisk.img), then flash the patched img from Fastboot

zgfg said:
You probably flashed incorrect TWRP -
you didn't even mention are you on MM (EMUI 4) or N (EMUI 5)
Different TWRP images must be used, but from the corresponding XDA Huawei P9 (MM or N) threads - not something maybe from elswhere on Internet
Click to expand...
Click to collapse
Thanks alot! I was using TWRP img from twrp.me thought it was a offical site. Now i used an image from the forum here and everything works. Thanks alot would have gotten a headache without your help

FlxF said:
Thanks alot! I was using TWRP img from twrp.me thought it was a offical site. Now i used an image from the forum here and everything works. Thanks alot would have gotten a headache without your help
Click to expand...
Click to collapse
TWRP.me (apparently) is the official TWRP site but you can see that they only have one TWRP img file (for each new TWRP release) for Huawei P9 (EVA) - hence they don't care, they are not aware of different organization of partitions (sizes, names and encryption) coming with different EMUI versions.
And from their P9 Changelog (screenshot attached) you can see that last adaptation for P9 was made in May 2016, when P9 had its original Marshmallow (EMUI 4).
Below is XDA thread from 2017 when Nougat (EMUI 5) was released and a guy who ported to (with description of changes he made). TWRP for EMUI 5 I gave you the link in previous answer is based on his port, but made after he stopped maintaining it (he moved off from P9), hence it is still TWRP 3.2.1.0 but with slight change (somebody else fixed/improved I think which partitions are mounted by default and/or what will be erased by Factory reset option - I don't recall details anymore)
https://forum.xda-developers.com/p9/development/twrp-t3565703
Btw, you are not the first who soft-bricked P9 (with Nougat) by installing the 'official' TWRP (you could search here on XDA P9 sub-forum, I recall I similarly helped to two or three of them last year and this year) and who had to move to the proper port from XDA to unbrick - the 'official' TWRP seems to be good only for those who are stuck with Marshmallow / EMUI 4 from 2016 (most likely those who got stuck with the cust c900, 'international' cust at that time, that was never updated by Huawei to Nougat while they introduced new custs for different world regions, countries and operators when they started to sell and support the phone out of China)
It would be fair if TWRP.me at least makes a note on which stock firmware version they test their 'official' P9 releases...

Error 7 issue after android Q

hello
It's been a while since I wrote anything on XDA, so please be gentle
Let's get the ball rolling.
I have been using MI9 since launch. I bought mine directly at the store in Shanghai, and brought it with me to Europe. After 2 weeks i unlocked the bootloader, and was able to flash TWRP + xiaomi.eu ROM (current beta at that time).
For a couple of months I received OTA updates (all firty flashes), up until introduction of beta android Q (miui 11).
I downloaded the ROM, and flashed, everything worked fine. after some time I had an issue with google pay, so thought of reverting to android Q. I checked, and dirty flash was not recommended option, so I prepared Android P ROM (not sure if exact version is relevant), booted to TWRP (3.3.1.42), wiped the data and tried to flash the ROM (from USB OTG).
Sadly - received error 7, some info about system partition.
I tried reflashing android Q - only to receive the same error.
Stuck at TWRP or fastboot, I used miflash and returned to a global stable.
then I reflashed twrp hoping to remove the error, but had the same error while flashing. Tried to flash from both internal memory, and usb OTG.
returned with miflash to stable, to use the phone..
bootloader is still unlocked, I can flash twrp again, but it will be wiped once I restart the system (as global roms "reflash" recoveries when they boot up).
I looked on some guides how to deal with error 7, but most of them aren't applicable (removing asses lines from config files, as there is no assess line in the ROMs).
Perhaps I am missing some files that I should flash, such as "vendor" files, or something ?
I thought that miflash restores fully to factory state, so TWRP shouldn'[t give any more errors.

There might be something wrong about either the rom, or the twrp.
> Since error 7 is the updater script checking for the phone model, it's either a bad script, or you missed an asserts file when flashing with MiFlash, as even the "factory" roms might not contain all partitions.
> Some partitions can't be seen by Mauronofrio's TWRP, but that shouldn't be a problem tho...
- Try using TWRP 3.3.1-1001 by a chinese team
- Try using the latest 10.10.2019 MIUI11 Rom from xiaomi.eu, I'm using in on an EEA phone and quite satisfied with it

[GUIDE] OTA on TWRP

i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)

in my personal experience, if you get rebood to twrp, flash Disable Dm Verity ForceEncrypt to boot into rom

title
Was Magisk installed before the update? Since you are saying it rebooted to TWRP without you knowing, were you able to restore stock images before updating? Could you also provide information concerning the update? For example, miui version (updating from vXXX to vXXX)
jjsan said:
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
Click to expand...
Click to collapse

Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0

jjsan said:
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
Click to expand...
Click to collapse
What I meant was whether you uninstalled Magisk/restored original boot img prior to the update because sometimes not doing so tends to result in bootloop (happened to me before). I needed some information before I attempt the update myself. Thank you for replying.
P.S. One more question: All data was preserved, right?