Help Twrp Nougat - Mate 8 Q&A, Help & Troubleshooting

OP Junior Member13 posts Thanks: 1
Is it possible to install TWRP with your device running the Nougat beta ?

not for now.

misho_20063 said:
OP Junior Member13 posts Thanks: 1
Is it possible to install TWRP with your device running the Nougat beta ?
Click to expand...
Click to collapse
Yes possible 1-
Download TWRP Recovery 3.0.3
http://sillanwali.com/downloads/twrp-3.0.3.img
2-
adb devices
adb reboot bootloader
fastboot flash recovery (PATH-TO)\twrp-3.0.3.img
3-
Reboot your phone to TWRP then choose Wipe > format > type Yes
4-
Back again, then wipe (data, dalvik, cache, system)
Don't reboot
6-
Install supersu_v2.79_sr2.zip
http://www.sillanwali.com/downloads/supersu_v2.79_sr2.zip
7-
Rooted

Related

My P6800 kitkat 4.4.2 problem! can not boot.

I flashed omni-4.4.2-20140124-p6800-HOMEMADE.zip last night, but it can't work , when I boot system . it stay on OMNI logo screen. And I can not enter twrp 2.6.3.1 too. Is it brick? but I can enter odin mode . any one can help???? thanks
I wanna ask daniel_hk but I just a junior and I can't post at " Android Development" . help!!!!!!
Either flash full official firmware package with Odin or try re-flash recovery and (if successful) wipe, and then restore your Nandroid.
linvas said:
I flashed omni-4.4.2-20140124-p6800-HOMEMADE.zip last night, but it can't work , when I boot system . it stay on OMNI logo screen. And I can not enter twrp 2.6.3.1 too. Is it brick? but I can enter odin mode . any one can help???? thanks
Click to expand...
Click to collapse
Full wipe by CWM before upgrade to 4.4.
1) Reboot to cwm recovery
2) Do full wipe data, cache and davik cache
3) Reboot to cwm recovery again
4) Install KK442
5) Install Gapps
6) Install supersu (optional)
7) Reboot to system
69444091 said:
Full wipe by CWM before upgrade to 4.4.
Click to expand...
Click to collapse
HAPPYFATHER said:
1) Reboot to cwm recovery
2) Do full wipe data, cache and davik cache
3) Reboot to cwm recovery again
4) Install KK442
5) Install Gapps
6) Install supersu (optional)
7) Reboot to system
Click to expand...
Click to collapse
OP says cannot boot into recovery.......
That's why I suggested to flash firmware package or recovery with Odin.
Without a working recovery, it's the only option. From there, he can move on.
Sent from my GT-I9500 using XDA Premium 4 mobile app

[Q] Bootloader broken?

Hello guys,
after attempting to install a custom rom in my S5670B I got stuck in CWM every single time I try to reboot the phone. I doesn't matters what I try, it will always boot into recovery.
So, is there anyway to make it boot "correctly"?
Steps to install the custom rom:
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. format /system
5. install from zip
6. wipe dalvik
rmartignoni said:
Hello guys,
after attempting to install a custom rom in my S5670B I got stuck in CWM every single time I try to reboot the phone. I doesn't matters what I try, it will always boot into recovery.
So, is there anyway to make it boot "correctly"?
Steps to install the custom rom:
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. format /system
5. install from zip
6. wipe dalvik
Click to expand...
Click to collapse
just you need below steps test it reply here again.
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. install from zip
5 wipe data/cache
6. wipe dalvik
rmartignoni said:
Hello guys,
after attempting to install a custom rom in my S5670B I got stuck in CWM every single time I try to reboot the phone. I doesn't matters what I try, it will always boot into recovery.
So, is there anyway to make it boot "correctly"?
Steps to install the custom rom:
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. format /system
5. install from zip
6. wipe dalvik
Click to expand...
Click to collapse
If you are using CWM6 there is known bug that causes this. Just revert to CWM5.
If not just wipe everything (EXECPT SDCARD) and flash again
If that is no go then flash stock rom via odin, flash CWM5 and then flash custom rom.

HELP. Redmi Note 3 stuck in BOOTLOOP after installing Custom ROM

Hey guys, this is my first time here, sorry in advance if I say something wrong or anything.
I just unlock my Redmi Note 3 (SD 650 variant) bootloader via the unofficial way (the miflash tool way, without permissions from xiaomi).
It was done, I already checked the oem unlock status via command prompt, and then I was able to flash TWRP via fastboot.
Then I did a complete wipe of my device through TWRP, and flashed Resurrection Remix and GAPPS.
At first I was getting error 7 and error 6 everytime I flashed the rom, but I managed to fix that through some readings.
The problem is that, I always stuck in bootloop (the RR boot screen).
I tried with LineAge OS, because at first I thought it was a ROM issue, and the same thing happened: it stuck in bootloop (the LineAge OS boot screen in this case).
The step I did was :
TWRP 3.1.1-0 ---> Wipe ---> Swipe to Factory Reset ---> Install ROM and Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I also tried without the Wipe Dalvik step before rebooting, same result.
Another thing I tried was :
TWRP 3.1.1-0 ---> Wipe ---> Advanced Wipe ---> then I select "Dalvik/ART cache", "System", "Data", and "Cache" ---> Swipe to Wipe ---> Install ROM, Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I tried this one without the Wipe Dalvik aslo, same result.
This phone is my daily driver, so can anyone please educate me on what's happening?
(Yes I know it's not good for beginners to do this by himself on his daily driver, but in the past I have rooted and install custom ROM on my Galaxy S3 Mini...that's why I was a bit confident -.- )
Thanks in advance, I hope I get an answer here.
rioyoyo29 said:
Hey guys, this is my first time here, sorry in advance if I say something wrong or anything.
I just unlock my Redmi Note 3 (SD 650 variant) bootloader via the unofficial way (the miflash tool way, without permissions from xiaomi).
It was done, I already checked the oem unlock status via command prompt, and then I was able to flash TWRP via fastboot.
Then I did a complete wipe of my device through TWRP, and flashed Resurrection Remix and GAPPS.
At first I was getting error 7 and error 6 everytime I flashed the rom, but I managed to fix that through some readings.
The problem is that, I always stuck in bootloop (the RR boot screen).
I tried with LineAge OS, because at first I thought it was a ROM issue, and the same thing happened: it stuck in bootloop (the LineAge OS boot screen in this case).
The step I did was :
TWRP 3.1.1-0 ---> Wipe ---> Swipe to Factory Reset ---> Install ROM and Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I also tried without the Wipe Dalvik step before rebooting, same result.
Another thing I tried was :
TWRP 3.1.1-0 ---> Wipe ---> Advanced Wipe ---> then I select "Dalvik/ART cache", "System", "Data", and "Cache" ---> Swipe to Wipe ---> Install ROM, Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I tried this one without the Wipe Dalvik aslo, same result.
This phone is my daily driver, so can anyone please educate me on what's happening?
(Yes I know it's not good for beginners to do this by himself on his daily driver, but in the past I have rooted and install custom ROM on my Galaxy S3 Mini...that's why I was a bit confident -.- )
Thanks in advance, I hope I get an answer here.
Click to expand...
Click to collapse
i had the same issue, solution to this is : just flash MM bootloader from TWRP.
Here: https://drive.google.com/file/d/0B3tM1cVKiyp6Q3RvNUtLdEp1Q3M/view?usp=drivesdk

Instructions how to install custom rom

Hi write me detailed instructions how to install custom ROM without losing twrp?Thanks
Flash OOS stable (latest)
2flash twrp
3. Reboot to twrp
4. Flash oos stable
5. Flash twrp
6. Reboot to twrp
7. Wipe data, dalvik cache
8. Flash rom
9. Flash twrp
10. Reboot to twrp
11. Flash gapps
12. Boot system
The thread below yours have the same issue.. There is now 9 threads about this issue. Is the search function disabled?
Thanks
whizeguy said:
Flash OOS stable (latest)
2flash twrp
3. Reboot to twrp
4. Flash oos stable
5. Flash twrp
6. Reboot to twrp
7. Wipe data, dalvik cache
8. Flash rom
9. Flash twrp
10. Reboot to twrp
11. Flash gapps
12. Boot system
The thread below yours have the same issue.. There is now 9 threads about this issue. Is the search function disabled?
Click to expand...
Click to collapse

[Solved] Help to flash custom ROMs

Hello everybody,
I bought a Oneplus 7 Pro a few days ago and I'm preparing it for my daily usage. It's my fourth Android smartphone, and the third Oneplus. So far, I managed to flash everyone of them, with no major issues.
And then, the Oneplus 7 Pro suddenly appeared
I used this tutorial to unlock the bootloader and flash the custom recovery.
From my understanding, the custom recovery is flashed in the Recovery Ramdisk and available for both A & B slots.
For now, I have A and B slots with stock OSS, unlocked bootloader, custom recovery and Magisk. All of this is working.
There began my problems. I want to flash a custom ROM without Gapps and I fail to do it. All instructions around ROM threads seems different to me, I don't get the thing about A & B slots, when I flash one rom, it boots as usual on the stock ROM, if I flash both slots, It causes bootloops and if I manage to launch the recovery, my internal storage isn't detected and I can't restore any backup.
I already used MSMDownload to restore the phone completely once.
Can somebody explain to my dumb person how to do it proprely ? Thanks in advance ! :fingers-crossed:
TL;DR : I fail to flash a custom ROM and make it work.
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
djhulk2 said:
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
Click to expand...
Click to collapse
For now, my phone is working nicely. But that's the process of flashing a new ROM that fails. Recovery and Magisk are already and working.
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
WesTD said:
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
Click to expand...
Click to collapse
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
draentor said:
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
Click to expand...
Click to collapse
Nope, it doesnt tell you anything. Just reboot recovery from reboot menu. Don't touch the slot options
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
draentor said:
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
Click to expand...
Click to collapse
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Joker123## said:
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
Click to expand...
Click to collapse
Thanks for the explanation !
WesTD said:
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Click to expand...
Click to collapse
Well yes, I didn't understood the difference between Wipe and Format Data.
So let's resume :
Unlock Bootloader
Advanced -> Install Recovery Ramdisk : Install TWRP
Install -> Flash TWRP Installer
Install -> Flash Magisk
Reboot -> System : Reboot on stock OxygenOS Rooted
Then
Wipe -> Factory Reset : Wipe Data, Cache and Dalvik Cache, that means you just have to swipe on TWRP.
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
is wiping internal storage compulsory?
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
How would you do it ? This is an open discussion, I can't find one and only way of doing it
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
Not wiping.. formatting..that is compulsory if your current data is encrypted
After multiple tries to verify the process :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
It worked !

Categories

Resources