Brick after trying to revert to stock - Honor 7X Questions & Answers

Okay so I was on Lineage OS and I tried to revert to stock with the Huru updater which went wrong because I forgot to rename the files. So now I'm stuck, my phone won't turn on, I can't flash TWRP >> writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.530s
Tried flashing back the stock system.img but it didn't work. Anyone know what to do? Cuz i'm clueless

Jetze243 said:
Okay so I was on Lineage OS and I tried to revert to stock with the Huru updater which went wrong because I forgot to rename the files. So now I'm stuck, my phone won't turn on, I can't flash TWRP >> writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.530s
Tried flashing back the stock system.img but it didn't work. Anyone know what to do? Cuz i'm clueless
Click to expand...
Click to collapse
BIG HOLES in the story. Not enough information to even begin to help.
Start with say what ota files did you feed into hurupdater?

mrmazak said:
BIG HOLES in the story. Not enough information to even begin to help.
Start with say what ota files did you feed into hurupdater?
Click to expand...
Click to collapse
You're right, i'll tell you everything I remember. I used the latest files I could find for bnd-l21, then when I tried flashing it it gave me an error because I forgot to rename the files. After that I tried a bunch of things like reflashing TWRP which gave me that error. Then i tried reflashing stock recovery to see if that'd error too and it did.

Jetze243 said:
You're right, i'll tell you everything I remember. I used the latest files I could find for bnd-l21, then when I tried flashing it it gave me an error because I forgot to rename the files. After that I tried a bunch of things like reflashing TWRP which gave me that error. Then i tried reflashing stock recovery to see if that'd error too and it did.
Click to expand...
Click to collapse
well let me look at some of my notes, and when i find them i give you some commands for fastboot to see the partition information

mrmazak said:
well let me look at some of my notes, and when i find them i give you some commands for fastboot to see the partition information
Click to expand...
Click to collapse
Alright, thank you

Jetze243 said:
Alright, thank you
Click to expand...
Click to collapse
i have one that will hopefully verify the version of partiton table, maybe.
fastboot oem get-build-number
and one to verify lock status
fastboot oem get-bootinfo

mrmazak said:
i have one that will hopefully verify the version of partiton table, maybe.
fastboot oem get-build-number
and one to verify lock status
fastboot oem get-bootinfo
Click to expand...
Click to collapse
Okay, here's the output:
C:\Users\Gebruiker>fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0BFR)
OKAY [ 0.000s]
finished. total time: 0.000s
&
C:\Users\Gebruiker>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Gebruiker>

Jetze243 said:
Okay, here's the output:
C:\Users\Gebruiker>fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0BFR)
OKAY [ 0.000s]
finished. total time: 0.000s
&
C:\Users\Gebruiker>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Gebruiker>
Click to expand...
Click to collapse
then this should work.
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
download the recovery from
https://forum.xda-developers.com/devdb/project/dl/?id=28883
if it works and boots, follow that with hurupdater again, or my HWOTA guide.

mrmazak said:
then this should work.
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
download the recovery from
https://forum.xda-developers.com/devdb/project/dl/?id=28883
if it works and boots, follow that with hurupdater again, or my HWOTA guide.
Click to expand...
Click to collapse
Same result as last time:
C:\Users\Gebruiker> fastboot flash recovery_ramdisk C:\Users\Gebruiker\Desktop\complete_twrp_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (14672 KB)...
OKAY [ 0.526s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.526s

Jetze243 said:
Same result as last time:
C:\Users\Gebruiker> fastboot flash recovery_ramdisk C:\Users\Gebruiker\Desktop\complete_twrp_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (14672 KB)...
OKAY [ 0.526s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.526s
Click to expand...
Click to collapse
I suspect something now, but need to confirm something.
You said you used "latest files for L21"
not very specific.
On pro-teammt.ru site the newest full firmware in the list for L21 is (BND-L21C432B131CUSTC432D002)
this is nougat firmware.
That explains what is happening.
your partions are half oreo and half nougat.
lets hope you can flash nougat twrp .
then do the full ota Of OREO this time.

mrmazak said:
I suspect something now, but need to confirm something.
You said you used "latest files for L21"
not very specific.
On pro-teammt.ru site the newest full firmware in the list for L21 is (BND-L21C432B131CUSTC432D002)
this is nougat firmware.
That explains what is happening.
your partions are half oreo and half nougat.
lets hope you can flash nougat twrp .
then do the full ota Of OREO this time.
Click to expand...
Click to collapse
For Nougat it was "fastboot flash recovery recovery.img" right?
edit: Do you have a link for a nougat twrp?

Jetze243 said:
For Nougat it was "fastboot flash recovery recovery.img" right?
edit: Do you have a link for a nougat twrp?
Click to expand...
Click to collapse
try this bro
https://androidfilehost.com/?fid=962021903579497006

Jetze243 said:
For Nougat it was "fastboot flash recovery recovery.img" right?
edit: Do you have a link for a nougat twrp?
Click to expand...
Click to collapse
I don't know how well these files work, I have never had the need to use them:
https://forum.xda-developers.com/devdb/project/?id=23956#downloads

mrmazak said:
I suspect something now, but need to confirm something.
You said you used "latest files for L21"
not very specific.
On pro-teammt.ru site the newest full firmware in the list for L21 is (BND-L21C432B131CUSTC432D002)
this is nougat firmware.
That explains what is happening.
your partions are half oreo and half nougat.
lets hope you can flash nougat twrp .
then do the full ota Of OREO this time.
Click to expand...
Click to collapse
Okay I flashed the Nougat TWRP succesfully! How do I know which firmwares are Oreo and which aren't tho? On Teampro there are no versions next to the files

Jetze243 said:
Okay I flashed the Nougat TWRP succesfully! How do I know which firmwares are Oreo and which aren't tho? On Teampro there are no versions next to the files
Click to expand...
Click to collapse
It's not real easy. Sometimes it is in the change log. Click the build number and read through it, see if it says.
I have found that generally build numbers for the 7x that are b300 and higher are Oreo
And ones that are below are nougat.
Almost none of the devices have nougat full available.

Related

can't unlock bootloader

Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.

Completely Bricked?

All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work.
Device state is unlocked.
Reinstalled Google Drivers.
I will use taimen-opm1.171019.013-factory-6d9954c3
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version eac51f2bb6a8-android
Unified Android Toolkit:
Booting TWRP recovery-twrp-3.2.1.0-taimen.img ..
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.007s
Click to expand...
Click to collapse
Cannot flash TWRP
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot flash recovery twrp.img
sending 'recovery' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.009s
Click to expand...
Click to collapse
ADB sideload
PS C:\adb> adb sideload C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip
loading: 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip'
* cannot read 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip' *
Click to expand...
Click to collapse
If I use flash-all.bat:
sending 'bootloader' (36344 KB)...
FAILED (unknown status code)
finished. total time: 343.328s.
Click to expand...
Click to collapse
If I use flash-all command in cmd:
PS C:\Users\tiger\Desktop\tamien> flash-all
error: cannot load 'bootloader-taimen-tmz10n.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
error: cannot load 'radio-taimen-g8998-00122-1708311414.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
W/ ( 9820): Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.025.zip': I/O Error
Click to expand...
Click to collapse
Do you have the latest adb downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
azntiger said:
All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work. Device state is unlocked.
Unified Android Toolkit:
Cannot flash TWRP
ADB sideload
If I use flash-all.bat:
If I use flash-all command in cmd:
Click to expand...
Click to collapse
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
ilal2ielli said:
Do you have the latest are downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
Click to expand...
Click to collapse
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
Click to expand...
Click to collapse
azntiger said:
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
Click to expand...
Click to collapse
Why are you trying to flash the November build?
Badger50 said:
Why are you trying to flash the November build?
Click to expand...
Click to collapse
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
azntiger said:
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
Click to expand...
Click to collapse
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Badger50 said:
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Click to expand...
Click to collapse
I'll take a look if I can get my phone working again lol.
Badger50 said:
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
Click to expand...
Click to collapse
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
PS C:\Users\tiger\Desktop\Pixel> fastboot devices
711KPVH0902199 fastboot
PS C:\Users\tiger\Desktop\Pixel> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
PS C:\Users\tiger\Desktop\Pixel> fastboot flashing unlock
...
Click to expand...
Click to collapse
azntiger said:
I'll take a look if I can get my phone working again lol.
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
Click to expand...
Click to collapse
You may have to use this to get back on track my friend.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I'm not entirely sure what the issue is (it could be a couple of things), but here are some issues that I see to help you troubleshoot:
1. Adb commands don't work in bootloader mode, only fastboot commands, which is why your device is visible to fastboot and not adb.
2. The file that you tried to adb sideload was a factory image, not an OTA. Adb sideload can only be used with OTA images. And even if you were using an OTA image, OTA images cannot be used to downgrade to a previous firmware version.
3. The latest version of adb is 1.0.39. You are using an older version. That fact itself doesn't really matter since adb will not help you in this situation, but fastboot will and if your adb is obsolete, I'd be willing to bet that your fastboot is too. Pixel 2 support was added in the October 2017 release of adb and fastboot. If yours is older than that, you're gonna have a bad time.
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
5. You do not have driver issues. The fact that fastboot devices worked means that your drivers/connection are/is working fine.
PS: Get the latest adb and fastboot here: https://developer.android.com/studio/releases/platform-tools.html
UPDATE: I did a Google search for adb/fastboot version eac51f2bb6a8-android. I found a reference to it in a forum post dated mid-2016. There's your problem. Or one of them, anyway. If you do adb --version or fastboot --version on the latest releases, they will tell you that they are version 0.0.1-4500957.
TheSt33v said:
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
Click to expand...
Click to collapse
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Click to expand...
Click to collapse
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Badger50 said:
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Click to expand...
Click to collapse
All the platform-tools and the stock rom are together in folder.
azntiger said:
All the platform-tools and the stock rom are together in folder.
Click to expand...
Click to collapse
Did you extract the factory image first, or just put the whole zip file in platform-tools?
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
Click to expand...
Click to collapse
Hmm. Fastboot is definitely having issues communicating with your phone. "Failed to identify current slot" is a bad sign. If I were you, I would try flashing the most recent factory image (not the November 8.0 image you're trying to flash) first just to see if you can get everything up to date again and clear out any mismatched files that may have been flashed during your attempts. Once you manage that, then try to downgrade. If you can, try a different computer too, preferably one with a type C input that you can use the stock USB cable with.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Badger50 said:
Did you extract the factory image first, or just put the whole zip file in platform-tools?
Click to expand...
Click to collapse
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.[/QUOTE]
Thanks man. I learned something new today :good:
Wonder if his transfer cable. I've seen that cause headaches as well ?
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
Oh nice! Glad you got it figured out. This stuff can be a bit tricky at times. I know I've lost some hair from pulling it out when things didn't go right! ?
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
I was on edge just reading this! I would also look into Deuce's script. It can save the 'device can't boot' issue once and for good.
Kudos on not having a faulty device~!

Clean Dump for Mate SE

Been asking around for this in multiple threads and have gotten nothing. So I decided to just make a new one. If ANYONE has a backup I can use in order to restore it via TWRP, then PLEASE share it with me. Whether it's a Mate SE backup or an Honor 7x US variant backup, I'll take either.
That makes 2 of us
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
chrisn812 said:
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
Click to expand...
Click to collapse
Can you not use the hardware keys to get into the recovery? Also, what is the status of the recovery partition? Alive and well?
XandeR180 said:
Been asking around for this in multiple threads and have gotten nothing. So I decided to just make a new one. If ANYONE has a backup I can use in order to restore it via TWRP, then PLEASE share it with me. Whether it's a Mate SE backup or an Honor 7x US variant backup, I'll take either.
Click to expand...
Click to collapse
I am wiping my wifes phone today and I will do a clean backup via twrp and upload it to drive later today for ya
Ultraman666 said:
I am wiping my wifes phone today and I will do a clean backup via twrp and upload it to drive later today for ya
Click to expand...
Click to collapse
Thank you so much
XandeR180 said:
Thank you so much
Click to expand...
Click to collapse
Ok man here you go, hope this helps!! Its the least I can do since you helped me with all my questions
https://drive.google.com/open?id=1X2oB98XYngybIZpPPc7B51VMW8ID6F1c
chrisn812 said:
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
Click to expand...
Click to collapse
1-first got to fastboot mode in phone(vol down+ power) then connect phone to pc doesn't matter if the hisuite pops up in pc or not.
2-after connecting open adb shell from the directory where you have installed it in your pc(go to the folder and press shift+ right click of mouse then select open command prompt option).
3- type - fastboot devices , if some number appears then it confirms that the device is connected, if it doesn't appear then close everything in pc and disconnected your phone then power off the phone and then connect it to pc then open adb and type adb reboot bootloader - this should restart your phone into fastboot mode.
chrisn812 said:
Any ideas why I can't seem to boot a recovery? Used to do this all the time in the Motorola world:
~/Downloads/Huawei$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.711s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.714s
Click to expand...
Click to collapse
It doesn't look like this is supported (at least not on MY L24 variant). I don't know if the mount points are identical from one variant to another but they are posted here: https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990 (Nougat) and https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-oreo-t3764506 (Oreo). (The TWRP versions in the Multitool are from the OP of these two threads.) And some other posts showed the adb shell commands (and batch file) to backup stock recovery to the external SD card. I think for Nougat, they are:
Code:
dd if=/dev/block/mmcblk0p29 of=/external_sd/recovery.img
dd if=/dev/block/mmcblk0p22 of=/external_sd/recovery2.img
Stock recovery for the L24(?) can also be found in one of the threads here. And finally, the 7X has dual recovery so I ended up flashing TWRP to eRecovery (fastboot flash recovery2 TWRP.img) leaving the stock recovery in recovery1 for OTA updates. Then I use "adb reboot recovery2" whenever I need TWRP.
XandeR180 said:
Thank you so much
Click to expand...
Click to collapse
So did that work for you?
Ultraman666 said:
So did that work for you?
Click to expand...
Click to collapse
For the most part, yeah. Booted up and everything but for some reason I couldn't install Magisk ?
XandeR180 said:
For the most part, yeah. Booted up and everything but for some reason I couldn't install Magisk ?
Click to expand...
Click to collapse
FYI, I installed supersu from https://forum.xda-developers.com/honor-7x/how-to/how-to-root-honor-7x-international-t3716056 using the TWRP from MultiTool on my L24 and it appears to be working okay.
iammudd said:
FYI, I installed supersu from https://forum.xda-developers.com/honor-7x/how-to/how-to-root-honor-7x-international-t3716056 using the TWRP from MultiTool on my L24 and it appears to be working okay.
Click to expand...
Click to collapse
Hmm. I'm more of a fan of Magisk, personally but I'll try SuperSU
XandeR180 said:
For the most part, yeah. Booted up and everything but for some reason I couldn't install Magisk ?
Click to expand...
Click to collapse
Sweet glad to help!!
Didnt work on my SE L34. Still boots into EMUI eRecovery. Oh well. I'll wait a bit longer.
I had to overwrite the recovery2 partition with TWRP to do it, but here's an almost complete backup of the stock firmware for my Mate SE: BND-L34C567B130.zip
Magendanz said:
I had to overwrite the recovery2 partition with TWRP to do it, but here's an almost complete backup of the stock firmware for my Mate SE: BND-L34C567B130.zip
Click to expand...
Click to collapse
By almost complete, what exactly is it missing?
XandeR180 said:
By almost complete, what exactly is it missing?
Click to expand...
Click to collapse
The original contents of the recovery2 partition, which had to be overwritten with TWRP to do the backup. I believe it was identical to the recovery partition, but I was never able to confirm.
Magendanz said:
The original contents of the recovery2 partition, which had to be overwritten with TWRP to do the backup. I believe it was identical to the recovery partition, but I was never able to confirm.
Click to expand...
Click to collapse
Pretty sure it is. I'd flashed the same honor 7x stock recovery image for both my partitions in the past. Regardless, both my partitions use TWRP at the moment, so this doesn't bother me. Thanks a ton!
Magendanz said:
The original contents of the recovery2 partition, which had to be overwritten with TWRP to do the backup. I believe it was identical to the recovery partition, but I was never able to confirm.
Click to expand...
Click to collapse
So restoring your backup was successful. However, for some reason the updater is completely missing. Therefore, I can't check for updates anymore. Also, in the "About Phone" section at the bottom it says, "Custom Version - CUSTC567D001" which I don't recall ever seeing before. Does this have to do with your recovery partitions being modified?

Can't flash TWRP - remote failure (SOLVED)

Hi guys!
I hope you can help me, since I've looked everywhere but can only find people with similar but not the exact same problem.
I tried flashing TWRP in order to migrate to a custom ROM. I am currently running official 7.1.1.
When I try to flash twrp (tried several versions) the command window shows me this:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.068s
I tried using Moto fastboot as well but with the same result. I'd really appreciate your help. Please note, that I am not a pro like most you guys so I might have follow-up questions
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Artim_96 said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Click to expand...
Click to collapse
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Okay, I managed to unlock the bootloader with the unlock key I got from Motorola.
Now when I try to flash it says:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.280s]
finished. total time: 0.330s
Come ooooon
ischariot_pasadelski said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
I figured it out.
I had to restore the file system by only checking the "System" box when wiping with TPWR - just in case anybody else has the same problems.
So a factory data reset solve the problem? Having your first issue with moto e5 cricket and you can't unlock three bootloader
Artim_96 said:
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Click to expand...
Click to collapse
well, i had it unlocked via the settingsbutton and after read this here , via the website where you can get the 20 bits code, but it is the same result with a code that is the same as the adb devices code, just as before! Only thing that is changed is a warning when you starts the phone up.
ischariot_pasadelski said:
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
Click to expand...
Click to collapse
Can you tell me how you got the phone twrped, pls?

Question Red Magic 8 Pro stuck fastboot

Red Magic 8 Pro stuck fastboot
It no longer has sideload mode in recovery
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
BoJaXz said:
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
Click to expand...
Click to collapse
I switched both slots, but I can't boot up
Mr.PvT said:
I switched both slots, but I can't boot up
Click to expand...
Click to collapse
What steps did you do before you got stuck in fastboot?
BoJaXz said:
What steps did you do before you got stuck in fastboot?
Click to expand...
Click to collapse
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Mr.PvT said:
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Click to expand...
Click to collapse
Did you oem unlock before you tried flashing? You may have to flash the whole image
BoJaXz said:
Did you oem unlock before you tried flashing? You may have to flash the whole image
Click to expand...
Click to collapse
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Mr.PvT said:
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Click to expand...
Click to collapse
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
BoJaXz said:
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
Click to expand...
Click to collapse
I flashed those 2 files and changed both slots but failed to start the phone
I faced with the problem by locking the bootloader with init_boot.img for magisk. Then I unlocked it again and switched aactive slot to b and then to a in "Fastboot Enhance" tool. After that my phone entered to the system.
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
DarkestSpawn said:
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
Click to expand...
Click to collapse
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
edzchen said:
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
In bootloader:
fastboot flash odm odm.img
target reported max download size of 805306368 bytes
sending 'odm' (1284 KB)...
OKAY [ 0.032s]
writing 'odm'...
FAILED (remote: (odm_a) No such partition)
finished. total time: 0.038s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_dlkm system_dlkm.img
target reported max download size of 805306368 bytes
sending 'system_dlkm' (428 KB)...
OKAY [ 0.011s]
writing 'system_dlkm'...
FAILED (remote: (system_dlkm_a) No such partition)
finished. total time: 0.018s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_ext system_ext.img
target reported max download size of 805306368 bytes
sending 'system_ext' (730792 KB)...
OKAY [ 17.204s]
writing 'system_ext'...
FAILED (remote: (system_ext_a) No such partition)
finished. total time: 17.211s
Nothing happens when I flash system & vendor.
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash vendor_dlkm vendor_dlkm.img
target reported max download size of 805306368 bytes
sending 'vendor_dlkm' (93564 KB)...
OKAY [ 2.181s]
writing 'vendor_dlkm'...
FAILED (remote: (vendor_dlkm_a) No such partition)
finished. total time: 2.187s
In Fastbootd:
Everything that failed in bootloader, flashed beside system. Could only flash _b slots. Nothing seems to exist for slot a. I did not fastboot format or erase anything to my knowledge unless Fastboot Enhance did so when I flashed the playload.bin thru it without having logs on to watch what it did. If it formated or erased any partitions can they be recreated?
And last when in Recovery:
F:\Files\Downloads\RM8P>adb sideload NX729J-update.zip
loading: 'NX729J-update.zip'
error: closed
DarkestSpawn said:
Everything that failed in bootloader, flashed beside system.
Click to expand...
Click to collapse
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
edzchen said:
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
Click to expand...
Click to collapse
I just retried in bootloader with a new outcome this time:
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/6 (786364 KB) OKAY [ 18.742s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I copied the fastboot.exe from fastboot enchanced to the directory of the extracted payload.bin. Was able to recreate partitions. Am attempting to recover from potential brick.
I tried LineageOS TD-based. Didnt attempt calls or messages. Was just checking out the feel of the rom and its capabilities.
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
DarkestSpawn said:
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
Click to expand...
Click to collapse
Here you go:
ugene1980 said:
Here you go:
Click to expand...
Click to collapse
So looking thru this, the only difference I have is:
(bootloader) partition-size:userdata: 0x718BCD3000 Mine
(bootloader) partition-size:userdata: 0x35F5CD3000 Yours
as well as:
(bootloader) slot-successful:a:yes Yours
(bootloader) slot-successful:a:no Mine
but thats because it hasnt successfully booted since last flash.
I also need the fastbootd's printout. The one provided was from bootloader. The one from fastbootd will give logical partitions and has slot info.
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
DarkestSpawn said:
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
Click to expand...
Click to collapse
Yeap I did all that but calls and texts only half worked. I could do calls but no audio and I could send texts but couldn't receive. Was the main reason why I switched back to stock

Categories

Resources