i want to go back stock recovery and relock the bootloader - Honor 7X Questions & Answers

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?

Related

Can't install custom recovery (TWRP)

Hello,
I have a big problem with my H815.
My H815 bootloader is been unlocked.
II try to install TWRP, but without success:
Code:
C:\Users\~\Downloads\G4\platform-tools>adb reboot bootloader
C:\Users\~\Downloads\G4\platform-tools>fastboot flash recovery twrp-2.8.7.0-h
815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32064 KB)...
OKAY [ 1.197s]
writing 'recovery'...
OKAY [ 0.317s]
finished. total time: 1.520s
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
For me, it's ok, but after that, my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Any idea please?
Kind regrards,
~~
Sylar
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
nfsolutions said:
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
Click to expand...
Click to collapse
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
This does not work for me. :'(
After this command : fastboot boot twrp-2.8.7.0-h815.img
My G4 boot imediatly to the System... :s
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
thanks, now it works. My mistake was that I installed directly a supersu (not this from twrp) and this messed up the boot.
After installing twrp permanently, I used this method to get root:
http://forum.xda-developers.com/g4/general/guide-root-lg-marshmallow-rom-repacked-t3265497
now I have root and twrp
Can someone help me please ?
I tried to flash the KDZ 2 times but still nothing I parobleme always the same.
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
Thank you Sir!
Got the same problem, installed TWRP but got bugdroid dead once booting recovery. Idk why TWRP isn't written.
Nothing to do I'm trying every way I could imagine. The result is always the same.
I can't find solution on any forum. Please, I need help. :'(
Kind Regards
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
rjboy11223 said:
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
Click to expand...
Click to collapse
No i'm not rooted atm. That why i wanna install a custom recovery ^.^
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
bender_007 said:
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
Click to expand...
Click to collapse
Thank you, but after that... :
Code:
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
...my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
bel57 said:
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
Click to expand...
Click to collapse
Thank you, but same problème i can't boot to TWRP after the comand "fastboot boot twrp-2.8.7.0-h815.img" my G4 reboot directly to the system.
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
bel57 said:
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
Click to expand...
Click to collapse
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Ur phone is weird lol
Sylar37 said:
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Click to expand...
Click to collapse
try first fastboot erase recovery, then fastboot flash recovery twrp....img
then fastboot reboot recovery
I downloaded the v20b kdz and flashed via LGUP.. I don't know what's wrong mate, sorry. :silly:

Recovering Possibly Bricked OnePlus 3

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.

oxygen OS 4.0 no twrp possible

Installed oxygen OS 4.0 everything seems to become OK
but after flashing twrp 3.0.2 to the phone it is just hanging in a black screen.
I tried several twrp alternatives from XDA: always same result.
After some seconds up to some minutes it is possible to reboot but no twrp has been flashed.
The twrp 3.0.2 works fine in the old version of OS oxygen
RoFrie said:
Installed oxygen OS 4.0 everything seems to become OK
but after flashing twrp 3.0.2 to the phone it is just hanging in a black screen.
I tried several twrp alternatives from XDA: always same result.
After some seconds up to some minutes it is possible to reboot but no twrp has been flashed.
The twrp 3.0.2 works fine in the old version of OS oxygen
Click to expand...
Click to collapse
Hi, you can fix it. Flash OnePlus3_OpenBeta7-FIRMWARE+MODEM-flashable.zip
https://www.androidfilehost.com/?fid=457095661767116249
I use this twrp and works!
You need PC to see youre phone in FASTBOOT. ADB + drivers instaled.
Reboot youre phone in Fastboot (Boot loader), then flash recovery. After flashing reboot to recovery.
sakarya1980 said:
Hi, you can fix it. Flash OnePlus3_OpenBeta7-FIRMWARE+MODEM-flashable.zip
https://www.androidfilehost.com/?fid=457095661767116249
I use this twrp and works!
Click to expand...
Click to collapse
I'd like to know some details before installing:
FIRMWARE+MODEM what is this? Is firmware the whole oxygen OS? Modem is for mobile connection like LTE?
What are the advantages in comparison of using the originals?
Can you give me the origin of the twrp you attached?
null0seven said:
You need PC to see youre phone in FASTBOOT. ADB + drivers instaled.
Reboot youre phone in Fastboot (Boot loader), then flash recovery. After flashing reboot to recovery.
Click to expand...
Click to collapse
I think I did exactly what you described. But nothing in the newly flashed TWRP resulted must in a black screen.
Install the modified TWRP v 3.0.2.1-28. Search in XDA you should find it. Flash it and boot into recovery. I installed it and flashed OOS 4.0 OTA through this recovery. Everything is working fine.
Black screen means you did not flash it.
Open Command Promt. Type:
fastboot flash recovery "recovery".img. (name of the recovery between commas)
reboot bootloader.
reboot to recovery.
Because we don't have any twrp updated to support Nougat oos roms. The ones we have can only read decrypted storage. I'm too waiting for someone to pick up the development and build an updated twrp.
Flashing this one works
null0seven said:
Black screen means you did not flash it.
Open Command Promt. Type:
fastboot flash recovery "recovery".img. (name of the recovery between commas)
reboot bootloader.
reboot to recovery.
Click to expand...
Click to collapse
But the log said the flash was ok:
fastboot flash recovery twrp-3.0.2-1-oneplus3.img
target reported max download size of 440401920 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.594s
---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------
mavidser said:
Flashing this one works
Click to expand...
Click to collapse
YES
This one works.
But my phone is encrypted and as written by abhibnl decrypting is not possible right now.
RolfFrie said:
But the log said the flash was ok:
fastboot flash recovery twrp-3.0.2-1-oneplus3.img
target reported max download size of 440401920 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.594s
---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------
YES
This one works.
But my phone is encrypted and as written by abhibnl decrypting is not possible right now.
Click to expand...
Click to collapse
Yeah, I noticed that too, after writing the comment.
For me though, I only needed to create the Nandroid backup and flash SuperSU, so I flashed the recovery, cancelled the decryption, formatted the data (removing the encryption), adb push'd the zip and installed it.
Any idea how I can turn the encryption back on now?
@RoFrie I originally had the same problem as you but with the difference that my phone was on OOS 3.2.8 and it upgrade to N. after that I tried TWRP but the phone would replace it every time I rebooted. Once I got the right TWRP I can boot to it but the internal drive was encrypted so TWRP was useless. I said forget this crap I'm going back to CM14.1. And as always I felt that I had to get this done. So once on CM14.1 I used TWRP to switch the file system to s2fs flash OOS3.2.8 than I let it do the upgrade yet again. This time when I flashed the TWRP .28 the phones was no longer encrypted,I rooted than its all good now.
Sent from my ONEPLUS A3000 using Tapatalk
What was the file?
RolfFrie said:
But the log said the flash was ok:
fastboot flash recovery twrp-3.0.2-1-oneplus3.img
target reported max download size of 440401920 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.594s
---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------
YES
This one works.
But my phone is encrypted and as written by abhibnl decrypting is not possible right now.
Click to expand...
Click to collapse
You need the unreleased beta twrp. Encrypted and rooted OOS 4.0.3 here
Sent from my ONEPLUS A3000 using Tapatalk

Any working TWRP for EMUI Oreo 8.0?

"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?

Can't flash TWRP after 11.0.12.0

Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
-
Hacker?pcs said:
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
Click to expand...
Click to collapse
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
J. Harry Potter said:
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
Click to expand...
Click to collapse
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
By the way this is a different method. this should have worked. what did you do ?
J. Harry Potter said:
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Click to expand...
Click to collapse
My bootloader is unlocked, I'm with Magisk since I bought the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
J. Harry Potter said:
By the way this is a different method. this should have worked. what did you do ?
Click to expand...
Click to collapse
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Hacker?pcs said:
My bootloader is unlocked, I'm with Magisk since I bough the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Click to expand...
Click to collapse
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
J. Harry Potter said:
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
Click to expand...
Click to collapse
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
fastboot continue
says "system has been destroyed"
I really don't want to wipe data and start fresh with Mi Flash tool ffs
Hacker?pcs said:
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
J. Harry Potter said:
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash the contained 4MB misc.img, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Hacker?pcs said:
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash it, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Click to expand...
Click to collapse
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
J. Harry Potter said:
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
Click to expand...
Click to collapse
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Hacker?pcs said:
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Click to expand...
Click to collapse
don't forget to flash VBMETA after so the custom recovery (twrp or orangefox) persist

Categories

Resources