Related
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.
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
moinkazi said:
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
Click to expand...
Click to collapse
delete
allrockedout said:
This is stock recovery. Flash in twrp as image. Select recovery ramdisk as partition.
After flash. Reboot to recovery from twrp. That should take you to stock recovery. There you can do a factory reset.
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=sharing
If you also flashed magisk or root. You will need to flash kernel as well. I was able to flash in fastboot mode. https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=sharing
Click to expand...
Click to collapse
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
moinkazi said:
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
Click to expand...
Click to collapse
The recovery I posted before was for bl24 usa version ORRRREEEEEOOOOO ONNNNLLYYY. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
allrockedout said:
The recovery I posted before was for bl24 usa version. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
Click to expand...
Click to collapse
Thnks bro
Perfect time to find this post. I am getting the OTA update notification but it won't install on TWRP. My strategy is to return to stock (unrooted and stock recovery) to get the OTA. Once I am on that, get TWRP and Resurrection Remix.
allrockedout said:
The recovery I posted before was for bl24 usa version...
Click to expand...
Click to collapse
BND-L24 you mean?
duckredbeard said:
BND-L24 you mean?
Click to expand...
Click to collapse
Si
allrockedout said:
Si
Click to expand...
Click to collapse
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
duckredbeard said:
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
Click to expand...
Click to collapse
I tried flash recover ramdisk than kernel in twrp, rebooted to stock recovery and factory reset. But wouldn't boot, than booted to fastboot and flashed kernel, fastboot flash kernel kernel.img and it rebooted and was all good. Just my experience.
Just trying to avoid using adb.
duckredbeard said:
Just trying to avoid using adb.
Click to expand...
Click to collapse
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
allrockedout said:
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
Click to expand...
Click to collapse
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
duckredbeard said:
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk recovery_ramdis.img
allrockedout said:
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
duckredbeard said:
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
Click to expand...
Click to collapse
You can boot to fastboot from twrp than start flashing
allrockedout said:
You can boot to fastboot from twrp than start flashing
Click to expand...
Click to collapse
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
duckredbeard said:
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
Click to expand...
Click to collapse
Yeah bootloader is correct. Good luck.
allrockedout said:
Yeah bootloader is correct. Good luck.
Click to expand...
Click to collapse
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
duckredbeard said:
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
Click to expand...
Click to collapse
Is frp and bootloader unlocked when rebooting to fastboot both are red?
"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?
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.
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 !!!!