Could anyone have experimented with this model of phone about other rom's !!??
no information found conserning the custom rom such as lineage, aospextented, resurection remix, miui and others ... ????
No news ?!!
itmasen1 said:
No news ?!!
Click to expand...
Click to collapse
Maybe it has something to do with the low number of people using Sony's mobile phones.
On the getdroidtips site there is a new update for xa2 plus (OMNIROM) created based on android 9 pie. Someone installed this custom rom?
Sure. It works (well for me it does). For now only H4413 variant.
But you better download from http://dl.omnirom.org/voyager/
scanno said:
Sure. It works (well for me it does). For now only H4413 variant.
But you better download from http://dl.omnirom.org/voyager/
Click to expand...
Click to collapse
Hi Scanno thank you !
How did you root your phone?
I found a problem of flash recovery it does not pass, I tried twrp-3.2.3-0-voyager.img and twrp-3.3.0-0-voyager.img by command adb it did not succeed , maybe with twrp zip but I do not find twrp voyager in format zip .can you help me ?? thank's
itmasen1 said:
Hi Scanno thank you !
How did you root your phone?
I found a problem of flash recovery it does not pass, I tried twrp-3.2.3-0-voyager.img and twrp-3.3.0-0-voyager.img by command adb it did not succeed , maybe with twrp zip but I do not find twrp voyager in format zip .can you help me ?? thank's
Click to expand...
Click to collapse
What problems did you get?
I presume you unlocked the bootloader?
What exactly did you do?
What firmware are you on?
What device do you have... H4413?
scanno said:
What problems did you get?
I presume you unlocked the bootloader?
What exactly did you do?
What firmware are you on?
Click to expand...
Click to collapse
Device xa2 plus dual (H4413)
yes bootloder unlocked
i am in pie 9.0
when i lunch commad adb :
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (27916 KB)...
OKAY [ 0.783s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.798s
itmasen1 said:
yes bootloder unlocked
i am in pie 9.0
when i lunch commad adb :
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (27916 KB)...
OKAY [ 0.783s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.798s
Click to expand...
Click to collapse
Dont do that.....
do fastboot boot twrp-3.2.3-0-voyager.img
XA2 devices are so called A/B devices and do not have a recovery partition.
That is why you should use fastboot boot [recovery image] to boot into twrp/recovery
Then you can do a adb sideload of the rom zip.
But you are better off by using 50.1.A.13.123 (Oreo) since there are problems with TWRP on 50.2.A.352
scanno said:
Dont do that.....
do fastboot boot twrp-3.2.3-0-voyager.img
XA2 devices are so called A/B devices and do not have a recovery partition.
That is why you should use fastboot boot [recovery image] to boot into twrp/recovery
Then you can do a adb sideload of the rom zip.
But you are better off by using 50.1.A.13.123 (Oreo) since there are problems with TWRP on 50.2.A.352
Click to expand...
Click to collapse
yes it work with this method :
C:\ADB>fastboot boot twrp-3.2.3-0-voyager.img
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
OKAY [ 5.304s]
finished. total time: 6.115s
and now , when i reboot in recovery mode twrp disappears. is this normal?
can I flash the omnirom on the first shot ?? .
itmasen1 said:
yes it work with this method :
C:\ADB>fastboot boot twrp-3.2.3-0-voyager.img
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
OKAY [ 5.304s]
finished. total time: 6.115s
and now , when i reboot in recovery mode twrp disappears. is this normal?
can I flash the omnirom on the first shot ?? .
Click to expand...
Click to collapse
Yes that is normal TWRP is not flashed, it is just booted.
You can flash omnirom like you normally would, but you will need to format the data partition.
I usually use adb sideload, but flashing the zip from sdcard is also possible.
If you want to use gapps, use open gapps nano.
But after flashing omni, reboot to bootloader from TWRP and run fastboot boot twrp-3.2.3-0-voyager.img again
then flash gapps.
scanno said:
Yes that is normal TWRP is not flashed, it is just booted.
You can flash omnirom like you normally would, but you will need to format the data partition.
I usually use adb sideload, but flashing the zip from sdcard is also possible.
If you want to use gapps, use open gapps nano.
But after flashing omni, reboot to bootloader from TWRP and run fastboot boot twrp-3.2.3-0-voyager.img again
then flash gapps.
Click to expand...
Click to collapse
YES:good: but wifi not worked
Can you give a logcat. Working fine here.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
The flash of this rom is successful, just some bugs and also the wifi does not work anymore, it turns round does not capture any network, Probably the cause comes from the pie9 version. I will go back to the version oreo8 and reflash the omnirom and I'll keep you informed.
Thank you for all the infos scanno
itmasen1 said:
The flash of this rom is successful, just some bugs and also the wifi does not work anymore, it turns round does not capture any network, Probably the cause comes from the pie9 version. I will go back to the version oreo8 and reflash the omnirom and I'll keep you informed.
Thank you for all the infos scanno
Click to expand...
Click to collapse
That WiFi is not working is strange. I flashed pie and then Omni, but WiFi was still working.
Like I said please provide a logcat / dmesg. There is an app included in the rom for that
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Can anyone confirm if it can used on H4493 also. Thanks!
https://drive.google.com/file/d/1bgUrUcEUrdkRtIIcoe_7ehCmPlYP5sQ4/view?usp=sharing
scanno said:
That WiFi is not working is strange. I flashed pie and then Omni, but WiFi was still working.
Like I said please provide a logcat / dmesg. There is an app included in the rom for that
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse
finaly backed to oreo and booting with twrp-3.3.0-0-voyager.img,flashing omni rom with sideloader
and rebooting in mode recovery with cmd fastboot boot twrp, install gapps and all done fine !!!!!
:good:
hamirali said:
Can anyone confirm if it can used on H4493 also. Thanks!
Click to expand...
Click to collapse
It can be used. Guess the only difference is memory/storage..
But i would need some info because I might need to add something in init.
I need to value of:
/proc/cei_project_id
Just to be sure.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Thanks scanno for confirming so promptly.
I am quite a. novice at this... I am minimally experienced with twrp and have used it to flash custom rom on another device.
Thanks for trying to assist, but I have no clue how to get you the info you asked. Apologies.
scanno said:
It can be used. Guess the only difference is memory/storage..
But i would need some info because I might need to add something in init.
I need to value of:
/proc/cei_project_id
Just to be sure.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse
provide a logcat / dmesg.
Not anderstand !!!!
Related
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
i.snehal.kiran said:
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
Click to expand...
Click to collapse
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Your oneplus bricked itself?
are you sure there wasn't a human involved in the process?
As other people says, you're the first one with a " bricked" device, so please tell everyone what your device status is, and how it got bricked.
did you unlock bootloader, did you have root? as much info as possible..
anupritaisno1 said:
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
Click to expand...
Click to collapse
I already have the link for that file. Someone shared. But, what next ?
Sent from my OnePlus2 using XDA Labs
anupritaisno1 said:
Fastboot on op2 is already a mess...
Click to expand...
Click to collapse
Why a mess?
Fastboot itself is very simple.
fastboot flash <<partition you need to flash>> <<file patch>>.
Is it different from the "common" fastboot we can find on a Nexus?
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
CyberCROC said:
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
Click to expand...
Click to collapse
You did 'fastboot oem unlock' first, correct?
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
CyberCROC said:
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Click to expand...
Click to collapse
And have you enabled OEM Unlocking in Developer Options ?
BTW Please reply to my PM ASAP if possible.
Thanks.
Best Regards,
Naman.
I can't OEM unlock in developer options as I no longer have access to my device
PM answered
Experiencing the same problem here.
I had the same in other thread. OEM unock was disabled. Do You have working stock recovery or TWRP? If stock works You can flash stock rom by ADB sideload.
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
cepheid46e2 said:
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
Click to expand...
Click to collapse
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
I have the same problem too
sino84 said:
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
Click to expand...
Click to collapse
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
try this:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
you need the OnePlus3_Unbrick_Tool_Full.rar to unbrick your phone, i was also in your situation,
you need also the Qualcomm_Diag_QD_Loader_2016_driver.exe with this two tools you can flash to restore the OP3
me helped al lot this thread http://forum.xda-developers.com/onep...icked-t3405700
a had a success with this part How to Make the device show as Qualcomm 9008
it is important that you have the correct driver installed on your pc that the phone will be recognized as Qualcomm 9008
I did the exact same stupid thing... locked bootloader before flashing stock recovery.
This post saved me:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I used method 2 in the post which wiped everything but at least i got the phone back.
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Since im a new member I cannot post links so ill have to give you directions.
Search google for Hard Bricked OnePlus 3 and it will be the first one called Mega Unbrick guide.
Use method 2. Ive used it multiple times when flashing goes wrong on my oneplus 3.
Another step, download the latest stock recovery from OnePlus and name it recovery.img and replace the one in the folder. You should understand more when you have all of the files.
You can download the latest recovery from OP at the bottom of the page linked here:
Google OnePlus 3 beta download and it should be the first one saying community build.
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.
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?
"fastboot flash recovery twrp.img" doesn't work. Gives me an "FAILED (remote: partition length get error)" error while I tried to flash TWRP that I downloaded from "unlock bootloader" XDA page. I have unlocked my bootloader, but couldn't install TWRP and proceed further. Noob here. Any help is appreciated. Thanks in advance.
This is what I got:
F:\Phone\Honor 7x\adb>fastboot flash recovery twrp_Honor_7x.img
target reported max download size of 471859200 bytes
sending 'recovery' (25158 KB)...
OKAY [ 0.634s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.649s
The New Partition Name in Oreo is recovery_ramdisk for Recovery.
Gesendet von meinem BND-L21 mit Tapatalk
johination said:
The New Partition Name in Oreo is recovery_ramdisk for Recovery.
Gesendet von meinem BND-L21 mit Tapatalk
Click to expand...
Click to collapse
Thanks mate !:good:
This twrp does not want to boot up.
error still not resolved
johination said:
The New Partition Name in Oreo is recovery_ramdisk for Recovery.
Gesendet von meinem BND-L21 mit Tapatalk
Click to expand...
Click to collapse
i am still getting following error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s
passengerUS$ said:
i am still getting following error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s
Click to expand...
Click to collapse
what file and command did you use?
mrmazak said:
what file and command did you use?
Click to expand...
Click to collapse
I have used all these commands and n all of them give errors
1) fastboot flash recovery twrp.img
2) fastboot flash recovery_ramdisk twrp.img
3) fastboot flash ramdisk twrp.img
passengerUS$ said:
I have used all these commands and n all of them give errors
1) fastboot flash recovery twrp.img
2) fastboot flash recovery_ramdisk twrp.img
3) fastboot flash ramdisk twrp.img
Click to expand...
Click to collapse
number 2 is correct, as long as your twrp.img is correct oreo recovery.
number 3 has put twrp into your (boot) , this is possibly a bad move.
mrmazak said:
number 2 is correct, as long as your twrp.img is correct oreo recovery.
number 3 has put twrp into your (boot) , this is possibly a bad move.
Click to expand...
Click to collapse
Number 2 is also not working I think I have to wait for official twrp oreo recovery image
passengerUS$ said:
Number 2 is also not working I think I have to wait for official twrp oreo recovery image
Click to expand...
Click to collapse
Im on oreo and am using this twrp on my L24 https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447. I used the 0.3.img. I've used it to backup and then flashed magisk 16 with no problems.
Joebloeh said:
Im on oreo and am using this twrp on my L24 https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447. I used the 0.3.img. I've used it to backup and then flashed magisk 16 with no problems.
Click to expand...
Click to collapse
Did you make the backup through TWRP or ADB? I'm using the same one and every time I go to make a back up it fails at system.img. Also do you know how to use decryption with it?
stuck on logo screen
Joebloeh said:
Im on oreo and am using this twrp on my L24 https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447. I used the 0.3.img. I've used it to backup and then flashed magisk 16 with no problems.
Click to expand...
Click to collapse
i flashed it it wroked perfectly thanks man you saved my day
Hold upppppppp.
Don't use Huawei p10 recovery. I tried it and it just got me stuck on the TWRP splash screen.
Just do "fastboot flash recovery_ramdisk complete_twrp_ramdisk.img"
I use this and it works flawlessly.
https://forum.xda-developers.com/devdb/project/dl/?id=28883
It worked do you have any super su version that works with it because when u install super su it shows ramdisk aborting installation error
passengerUS$ said:
It worked do you have any super su version that works with it because when u install super su it shows ramdisk aborting installation error
Click to expand...
Click to collapse
I would advise not to flash SuperSU. Magisk is the way to go. And you don't give enough details so I (and other people) can't really help you.
You're flashing it through TWRP?
crayonicle said:
I would advise not to flash SuperSU. Magisk is the way to go. And you don't give enough details so I (and other people) can't really help you.
You're flashing it through TWRP?
Click to expand...
Click to collapse
Yes I have flashed it through twrp
Now I want to root my device but when I install supersu in through twrp zip installation it shows
Checking patch status, attempting to find stock backup
Stock restore failed, attempting ramdisk restore
Ramdisk restore failed aborting
Do you need any extra information then pls comment
passengerUS$ said:
Yes I have flashed it through twrp
Now I want to root my device but when I install supersu in through twrp zip installation it shows
Checking patch status, attempting to find stock backup
Stock restore failed, attempting ramdisk restore
Ramdisk restore failed aborting
Do you need any extra information then pls comment
Click to expand...
Click to collapse
Do you get the same error with Magisk? Try Magisk please then report back.
crayonicle said:
Hold upppppppp.
Don't use Huawei p10 recovery. I tried it and it just got me stuck on the TWRP splash screen.
Just do "fastboot flash recovery_ramdisk complete_twrp_ramdisk.img"
I use this and it works flawlessly.
https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
When I first installed the p10 recovery it did hang up on the splash screen for at least a minute. But, now when I enter recovery it hangs more like ten or fifteen seconds.
crayonicle said:
Do you get the same error with Magisk? Try Magisk please then report back.
Click to expand...
Click to collapse
I tried magisk and it worked I was able to successfully root my phone thanks man
---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------
Joebloeh said:
When I first installed the p10 recovery it did hang up on the splash screen for at least a minute. But, now when I enter recovery it hangs more like ten or fifteen seconds.
Click to expand...
Click to collapse
Use the 0.3 IMG the other updated images hang up on Honor 7x when I used the latest one my twrp got stuck on twrp logo then I flashed it with 0.3 IMG as mentioned in the comment and It worked flawlessly
this is the recovery to use for 7x oreo right?
Hello i am writing here the very first time.
This is what happened :
I unlocked the bootloader.
Downloaded Twrp for Honor 7x from xda
Tried to flash it using ADB but it showed this :
C:\android-sdk-windows platform-tools>fastboot flash recovery twrp_Honor_7x.img
target reported max download size of 471859200 bytes
sending 'recovery' (25158 KB)...
OKAY [ 0.9695)
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.000s
Please someone help, and if possible provide me a link to the working twrp img
Thanks
If you're on oreo, the partition names have changed.
Use this command instead:
fastboot flash recovery_ramdisk twrpname.img
TWRP for oreo: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
If you're on oreo, the partition names have changed.
Use this command instead:
fastboot flash recovery_ramdisk twrpname.img
Click to expand...
Click to collapse
Okk let me check using this command and thanks for replying I will let you know in a bit
MeChiku said:
Okk let me check using this command and thanks for replying I will let you know in a bit
Click to expand...
Click to collapse
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
crayonicle said:
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
Click to expand...
Click to collapse
Thank you so much dear?
crayonicle said:
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
Click to expand...
Click to collapse
Thanks a ton bro Twrp Installed Successfully, Please can you suggest the best treble rom for honor 7x i am looking for DOT OS or Lineage