Related
I install twrp and accidentally wipe all system data there is no backup
when i install new firmware it says unknown file system osip.
when i go to recovery it says there is no os
my phone is not start?
plz help me
Just flash the rom you want. The osip thing is dosen't matter. Just flash the rom and you are golden
How to flash rom?
Magan Mittal said:
How to flash rom?
Click to expand...
Click to collapse
What kind of recovery are you using? If you are using stock recovery. Just use add sideload. If you are using TWRP. Then go to fastboot and flash the stock recovery. You can find the stock recovery in the rom downloaded from Asus : https://www.asus.com/Phone/ZenFone_5_A500CG/HelpDesk_Download/. Version 2.22.40.540 is recommended
i use twrp and adb sideload and recovery mode not working
Magan Mittal said:
i use twrp and adb sideload and recovery mode not working
Click to expand...
Click to collapse
Step 1: Flash recovery I'm via fastboot with "Fastboot flash recovery recovery.img"
Step 2: boot to recovery.
Step 3: Chose Adb sideload option in recovery.
Step 4: use command 'adb sideload (rom). zip
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Flash999 said:
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Click to expand...
Click to collapse
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Wormboymx said:
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Click to expand...
Click to collapse
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Flash999 said:
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Click to expand...
Click to collapse
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Wormboymx said:
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Click to expand...
Click to collapse
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
P.D. the encryption is when finishi whole process in the installed custom rom the hard drive doesn't work e.g... Open the camera and system say "Don't have sd card to save the files"
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
asad0181 said:
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
Click to expand...
Click to collapse
On this Youtube channel https://www.youtube.com/channel/UCuEtuySiR1DDYCRerutqvnA/videos
You can get some files...
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
chrisdlc119 said:
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
Click to expand...
Click to collapse
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Flash999 said:
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Click to expand...
Click to collapse
I think my display is tianman (ss atached). Is that right? Do you know if any display is affected with burning effect? It's just that I had a RN5 and I changed from MIUI to a custom ROM and one day the display just got the burning effect
Thanks for your reply.
Wormboymx said:
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
Click to expand...
Click to collapse
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Thanks! Now I could install Havoc and have access to my files!
Op you should include ,,fastboot -w" in your guide.
Finally i can boot PitchBlack recovery without Blackscreen in JDI panels::
Boot this recovery file: https://sourceforge.net/projects/pitchblack-twrp/files/jasmine_sprout/
Only one difference between the guide of this Thread....
I can´t change the partitions in PitchBlack recovery... i used the command in the op to change the partitions.... NOW i can flashed the Resurection remix rom in my phone
hlg1 said:
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
Click to expand...
Click to collapse
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
hlg1 said:
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I made it work by doing the first 2 steps from the OP and then after booting into system the first time I booted into bootloader and then used fastboot -w. I did this with Havoc OS though so it might not work for everyone.
When I wanted root and didn't know how to get a patched boot image for my ROM, I just followed the steps to access TWRP through ADB again and then wiped cache and dalvik, afterwards I used the sideload command to flash Magisk on my phone.
hlg1 said:
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I eventually figured out that all my problems occurred because I was using old versions of ADB and fastboot. After updating to latest platform-tools (currently r28.0.2) I was able to run fastboot -w without problems. And once that worked I was able to set up a fully working system following the steps of this guide.
Thanks for a very useful guide, it saved my day!
i got failed command write failed. any suggestion?
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Sarath_sh said:
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Click to expand...
Click to collapse
I'm not entirely sure I understand your question, but please note that by following the OP instructions you never flash TWRP, you just boot right into it from RAM. So should be no problem to do that while keeping stock ROM.
With the huawei support down, could anyone please help me to unlock huawei nova 2i RNE-L22 bootloader and to root it?
DC. UNLOCKER?
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
bootloader unlock codes forbidden
Chisetdel31260 said:
DC. UNLOCKER?
It says
> If your phone runs Android 8 or later with latest security patch - then this service won't work!
I have the latest security patch(March 1, 2019), I've been searching for the past 3 days for a working method to root my mate 10 lite, found nothing.
Huawei stopped providing oem unlock codes, All the services that provided unlock codes for money are now obsolete too.
I'm trying to find a way to root this phone on my own, but I'm not sure where to go from here.
I've read this book today "XDA Developers' Android Hacker's Toolkit", but it teaches how to use rooting methods that are already out there and not how to create your own way to root a device.
Can you provide guidance on where to go from here to learn how to find vulnerabilities in android?
Click to expand...
Click to collapse
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite .
it works
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
(4€/4$).
Service ROMs you can find here :
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
m10_lite said:
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
Click to expand...
Click to collapse
Best Custom ROM is Stock ROM & root .
bozka1 said:
Best Custom ROM is Stock ROM & root .
Click to expand...
Click to collapse
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
He did already
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
(4€/4$).
Service ROMs you can find here :
https://androidhost.ru/search.html
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
ante0 said:
He did already
Click to expand...
Click to collapse
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
davideakc said:
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
Click to expand...
Click to collapse
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
ante0 said:
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
Click to expand...
Click to collapse
Don't worry, thanks for the fast reply!
davideakc said:
Don't worry, thanks for the fast reply!
Click to expand...
Click to collapse
I can't find any TWRP with decryption. This one might work, it's from the MorfuZ thread: https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
So it may or may not have working decryption. But if you have an external SD it doesn't really matter as you'd only transfer magisk to that.
Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download latest stable.
Flash twrp using fastboot.
Reboot to recovery.
Transfer magisk zip to external SD.
Flash Magisk zip using the Install button
You will probably have to browse to /external_sd manually as it will default to /sdcard in the install browser.
If it fails to install using TWRP:
Open terminal in TWRP from the Advanced button then enter this command:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
This will dump your stock ramdisk to external sd, which you then can patch in Magisk Manager and flash the output file to 'ramdisk' using fastboot. You will have to install Magisk Manager apk first though, it can be found in the Magisk thread.
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
bozka1 said:
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!ot8TGIIa!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
Click to expand...
Click to collapse
If I do this, I lost all apps and data or not?
davideakc said:
If I do this, I lost all apps and data or not?
Click to expand...
Click to collapse
No you won't, but you should always backup your data.
AztekSoul said:
No you won't, but you should always backup your data.
Click to expand...
Click to collapse
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Yes you can, although you have to download updates through firmware finder and update with HuRUpdater in twrp.
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
bozka1 said:
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
Click to expand...
Click to collapse
After that, how can I restore factory eRecovery?
davideakc said:
After that, how can I restore factory eRecovery?
Click to expand...
Click to collapse
Okay, one can install Magisk without TWRP. There are plenty of guides on how to do these things in the Mate 10 forums. Of course, TWRP makes things easier ....
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
You made sure you have latest OOS11 on BOTH slots?
xtcislove said:
You made sure you have latest OOS11 on BOTH slots?
Click to expand...
Click to collapse
Thanks for the response! How do i check that? Both slots of what?
Infraviored said:
Thanks for the response! How do i check that? Both slots of what?
Click to expand...
Click to collapse
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Infraviored said:
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
Click to expand...
Click to collapse
U don't need the command fastboot reboot recovery. U can just use the volume buttons to select recovery and press power button to boot to recovery
Nimueh said:
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Click to expand...
Click to collapse
Another way to set your phone up for a custom rom can be found here. https://wiki.lineageos.org/devices/instantnoodlep/install
Just make sure your booting from a good 00S11 install when you do this.
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
king_xerxes said:
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
Click to expand...
Click to collapse
Sorted it out by this. Thank you!