Hello.
So I've decided to flash treble AOSP Phh's rom.
It works but since I haven't figured out *before flashing* that safetynet can't be passed, I really want to go back to stock.
I've tried a lot of things like the dload method with differents update.app, but each time it fails.
I haven't TWRP and AFAIK it's pretty useless.
I don't care if I loose all my data, or get my bootloader re-locked. I simply want my H9 to works on stock.
Before flashing, I was on C432B364. Then I flash Treble AOSP from Phh using "fastboot flash system".
Should I flash stock partitons like system, vendor ? ...
I've downloaded these files: update.zip (STF-L09C432B365 ), and update_full_STF-L09_hw_eu.zip.
So what should I do ? Thanks in advance.
(of course if Magisk Hide function worked on Treble Rom, I'd keep using this custom Rom)
Did you install custom aosp with twrp or stock recovery ?
If u used stock recovery you have to flash system with the os you had before so B364 in your case and no B365. Then do wipe data/factory. Extract the system.img from .app of the full package not the light one.
Aqwel said:
Did you install custom aosp with twrp or stock recovery ?
If u used stock recovery you have to flash system with the os you had before so B364 in your case and no B365. Then do wipe data/factory. Extract the system.img from .app of the full package not the light one.
Click to expand...
Click to collapse
Thank you for the quick reply.
So, I need to flash the b364 update, by using fastboot or the stock recovery?
Maybe answer my question first to be clear
Aqwel said:
Maybe answer my question first to be clear
Click to expand...
Click to collapse
I have never installed TWRP, so I still have the stock recovery.
I've flashed the rom with fastboot on my pc
Then its pretty simple. Just extract system.img from the .app of the full package of B364 and use fastboot to flash. Then do a wipe data/factory
Aqwel said:
Then its pretty simple. Just extract system.img from the .app of the full package of B364 and use fastboot to flash. Then do a wipe data/factory
Click to expand...
Click to collapse
Woooow it works!!
Thank you so muuuch !!
cynooosura said:
Woooow it works!!
Thank you so muuuch !!
Click to expand...
Click to collapse
You're Welcome
And what about the other zip with data? It fails to update every time. I was able to restore my device too, but this zip just wont flash.
Related
Hi, first of all, my English is bad and i'm a noob at installing custom roms
My HOX+ is rooted and i have the TWRP Recovery installed.
So, i downloaded the newest CM11 Nightly for my device (enrc2b) from the Cyanogenmod site.
When i try to flash it with TWRP it says:
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:Error executing updater binary in zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
I also downloaded a Snapshot version of CM11
It says:
Skipping MD5 check: no MD5 file found
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
So finally i downloaded the CM10.2.1 Version
I wiped all cache and data and did a factory reset.
After flashing the .zip and rebooting the phone, but i got stuck in a boot loop (i think) because i waited like 20 minutes but the boot animation didn't change (blue guy with the arrow). Did i do something wrong
I just restored my phone to the backup i made (stock rom)
If you need any information about my phone or something just say it.
I also heard about using CWM instead of TWRP but i don't know how to change it.
PLZ HELP :crying:
CWM recovery
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
[email protected] said:
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
Click to expand...
Click to collapse
Thx, I will try it
Sent from my HTC One X+ using XDA Free mobile app
I'm working with a Mac so it might take a while before i understand everything but i'll let you know if it worked.
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Anthony26 said:
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
did you flash the boot.img in fastboot before installing the rom?
reaper90 said:
did you flash the boot.img in fastboot before installing the rom?
Click to expand...
Click to collapse
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Anthony26 said:
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Click to expand...
Click to collapse
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Thx,
I forgot to unzip the file :silly:
I'll try it and let you know of it worked
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Stock boot image
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Anthony26 said:
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Click to expand...
Click to collapse
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
[email protected] said:
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Click to expand...
Click to collapse
reaper90 said:
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
Click to expand...
Click to collapse
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Anthony26 said:
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Click to expand...
Click to collapse
no, oxp_kk is just for 4.4 (kitkat) AOSP like roms. there's another non- kk version which works with 4.2.2/sense5 roms, but i don't know about stock roms. There's also a fallback kernel version which should work with all stock and custom 4.2.2/Sense 5 roms.
http://www.pocketables.com/2016/08/official-android-nougat-released.html
Pulled directly from my device and uploaded to my AFH site.
https://drive.google.com/open?id=0B0OpOqUNqeKkb19UbGxBV2NPc28
Stock, decrypted boot image, w. Verity disabled.
What version of android where you coming from?
spunks3 said:
What version of android where you coming from?
Click to expand...
Click to collapse
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
digitalhigh said:
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
Click to expand...
Click to collapse
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Deadlights said:
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Click to expand...
Click to collapse
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
What steps did you follow to get TWRP and root ?
So how is OTA different from full image?
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
MRL3GS said:
What steps did you follow to get TWRP and root ?
Click to expand...
Click to collapse
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Deadlights said:
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
Click to expand...
Click to collapse
Yep, /vendor is included, as well as updates to bootloader, etc.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It does not encrypt if you were not previously encrypted, this is the biggest difference
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
When i try to setup pay I get "android pay cant be used" :S
MRL3GS said:
When i try to setup pay I get "android pay cant be used" :S
Click to expand...
Click to collapse
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
digitalhigh said:
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
Click to expand...
Click to collapse
Thanks all working now
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
Working great for me! Thanks again man!
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Worked for me Thank you!!!! Still kept super su and twrp!!!
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
hutzdani said:
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Click to expand...
Click to collapse
Flash the TWRP image file from TWRP? And what is the modified boot image?
Sent from my Nexus 6P using Tapatalk
Batfink33 said:
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
Click to expand...
Click to collapse
Me everything works fine tho just i cant get root to wrk the app keeps freezing on me can't grant root?
Sent from my Nexus 6P using Tapatalk
Guys please help me.. I have a query.
I just unlocked bootloader and want to follow the following procedure, please tell me if I'm doing anything wrong
Flash twrp using fastboot command
Flash lazy flasher using twrp
Flash magisk(for root purpose) using twrp
Reflash stock recovery img using fastboot command
If i follow the above procedure will there be any problem and also will I be able to install system updates using updater app??
why do u even want to reflash ur stock recovery TWRP is much better stay onit.!!! and first flash magisk and then lazy flasher and everything will be fine
The only reason I want to flash stock recovery is OTA updates..
Don't worry about OTA u can always manually download the update and flash it using TWRP
leo_pard2331 said:
Don't worry about OTA u can always manually download the update and flash it using TWRP
Click to expand...
Click to collapse
You mean I can install the update package without the need to download entire 1.5gb package every time?
night_mare said:
You mean I can install the update package without the need to download entire 1.5gb package every time?
Click to expand...
Click to collapse
You need full package everytime.
sachin n said:
You need full package everytime.
Click to expand...
Click to collapse
So for every update I have to flash the entire rom + magisk + lazy flasher? And Is clean flash necessary every time?
night_mare said:
So for every update I have to flash the entire rom + magisk + lazy flasher? And Is clean flash necessary every time?
Click to expand...
Click to collapse
Most likely!
Ive no idea about MIUI Roms tho. But I believe the same ^
Clean install via twrp everytime, would be good to go.
night_mare said:
So for every update I have to flash the entire rom + magisk + lazy flasher? And Is clean flash necessary every time?
Click to expand...
Click to collapse
You can dirty flash new update
No need of clean flashing
And also you dont need to flash magisk and lazyflasher after flashing the update
Just the update zip thats all
leo_pard2331 said:
You can dirty flash new update
No need of clean flashing
And also you dont need to flash magisk and lazyflasher after flashing the update
Just the update zip thats all
Click to expand...
Click to collapse
But flashing update zip restores stock recovery right?
night_mare said:
But flashing update zip restores stock recovery right?
Click to expand...
Click to collapse
Yup
But after flashing the update zip file flash the twrp.img file
That should fix it
i have nearly the same problem i just wanna flash dolby thats all n dont wanna break ota updates. so i just wanna know
if i unlock bootloader n boot into twrp recovery("fastboot boot recovery.img" this command will not wipe stock recovery) and flash dolby then im able to receive n install ota updates(incremental and full package) or not? what u say guys?
arjitkumarsingh said:
i have nearly the same problem i just wanna flash dolby thats all n dont wanna break ota updates. so i just wanna know
if i unlock bootloader n boot into twrp recovery("fastboot boot recovery.img" this command will not wipe stock recovery) and flash dolby then im able to receive n install ota updates(incremental and full package) or not? what u say guys?
Click to expand...
Click to collapse
You cannot flash dolby using stock recovery bro.. first you have to flash TWRP recovery. The fastboot command loads whatever recovery your phone contains. It will not flash TWRP
night_mare said:
You cannot flash dolby using stock recovery bro.. first you have to flash TWRP recovery. The fastboot command loads whatever recovery your phone contains. It will not flash TWRP
Click to expand...
Click to collapse
no bro this command will boot temporarily into custom recovery. search on google. so what u say now is it possible ?
---------- Post added at 04:31 PM ---------- Previous post was at 04:24 PM ----------
arjitkumarsingh said:
no bro this command will boot temporarily into custom recovery. search on google. so what u say now is it possible ?
Click to expand...
Click to collapse
im assuming if it is possible then i may not b able to install incremental updates while full packege will wipe dolby atmos in the process of installation.
m i right?
Hello,
i was on EMUI 9 with my BKL-L09 and decided to give the custom roms a new try.
So i backed up my recovery_ramdisk (it was rooted with magisk before) and then flashed twrp (version 3.2.3-3).
Now i went for Wipe>format data and gave it a try. Result: it was hanging after makefs->(..) done. So i done the whole procedure again but it was still hanging.
Now i can't get back into twrp, because only the twrp bootscreen is showing up. Even after restoring my recovery_ramdisk backup with fastboot i can't get back into erecovery Is there anything i can do?
Thanks.
Ok, i solved this by myself through downloading the full ota update, extracting everything and flashing new kernel, system and recovery from ota update contents.
Can you put the CMD lines to do it?
Thank you anyway. I think i have the same problem.
jesusdoar said:
Can you put the CMD lines to do it?
Thank you anyway. I think i have the same problem.
Click to expand...
Click to collapse
I don't have this smartphone anymore but i remember the following:
1. Download the Full OTA Zip (e.g. here: https://www.getdroidtips.com/huawei...-update-for-honor-view-10-download-available/
2. Use the Huawei Update Extractor to extract the partitions from the content in the zip file. (https://forum.xda-developers.com/showthread.php?t=2433454)
3. Flash the partitions over the existing ones on your V10 using fastboot "fastboot flash recovery_ramdisk recovery_ramdisk.img , ...) - these contents are inside the full ota package
Greetings
Did it work out for you?
You can also try to flash the original erecovery using fastboot und use the download option inside the Recovery App. This will reset all partitions back to default. But also all data is lost.
Brodelpiet said:
Did it work out for you?
You can also try to flash the original erecovery using fastboot und use the download option inside the Recovery App. This will reset all partitions back to default. But also all data is lost.
Click to expand...
Click to collapse
it works thank you, now the problem is that the erecovery doesn´t download the package to flash.
jesusdoar said:
it works thank you, now the problem is that the erecovery doesn´t download the package to flash.
Click to expand...
Click to collapse
Did you just flash the erecovery or also the normal recovery partition und Kernel from the zip? What kind of error do you get?
Brodelpiet said:
Did you just flash the erecovery or also the normal recovery partition und Kernel from the zip? What kind of error do you get?
Click to expand...
Click to collapse
Yeah i flashed the kernel and the recovery ramdisk. And now it boots into erecovery, but inside the erecovery, the option to download and install the last version of emui doesn´t work, it just shows an error that it can´t get the package info.
thanks for your attention.
greets
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
felloguard123 said:
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
Click to expand...
Click to collapse
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
It seems your boot.img corrupted. If you format data and wipe dalvik cache data and flash stock rom you will succeed i think
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
https://c.mi.com/oc/miuidownload/detail?device=1900372
download official xiaomi mi a3 rom here. and flash it via pc and you will have brand new stock rom. Try it if you fail i will help you when i have free time
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
I was stupid and thought I did it without a boot image untill I checked all of my commands again.
I used fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img .
My phone was on V10.3.9.0 EUropean. But that image file is for twrp or is it also a boot.img? Not sure if this caused the problem? I'm very new to all of this so how can I find a stock boot.img of that version and how do I flash it again? I feel kinda lost right now.
Anyone can help me out with this?
felloguard123 said:
Anyone can help me out with this?
Click to expand...
Click to collapse
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
antoine62 said:
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
Click to expand...
Click to collapse
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
felloguard123 said:
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
Click to expand...
Click to collapse
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
antoine62 said:
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
Click to expand...
Click to collapse
So twrp has to be installed on both partitions?
I'm not sure if really twrp installed on only one partition could cause Wifi problems.
I would assume that my .img for twrp was faulty.
a
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
and how to do that:{?
i have same problem as yours and searched too many videos on youtube but then i have decided to remove the twrp from the device and no one yet has told me that how to flash twrp in another partition rather i dont know what is the another partition