Hey, i have some problems rooting my p9 lite VNS-L31. Now i use the Elite Kernel V9 for root it, but i have a huge problem. There is another way to root Nougat p9lite?
TZombi1234 said:
Hey, i have some problems rooting my p9 lite VNS-L31. Now i use the Elite Kernel V9 for root it, but i have a huge problem. There is another way to root Nougat p9lite?
Click to expand...
Click to collapse
You can root on stock ROM by flashing TWRP and SuperSu package (https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356). You can also flash lastest Magisk with TWRP and install Magisk Manager. here the guide https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I don't know if you have to get stock Kernel before proceed
TZombi1234 said:
Hey, i have some problems rooting my p9 lite VNS-L31. Now i use the Elite Kernel V9 for root it, but i have a huge problem. There is another way to root Nougat p9lite?
Click to expand...
Click to collapse
tell the issues in my Kernel thread,,, dont make another thread which no one sees or noticed,,, what issue you have in v9 ??
HassanMirza01 said:
tell the issues in my Kernel thread,,, dont make another thread which no one sees or noticed,,, what issue you have in v9 ??
Click to expand...
Click to collapse
Man, i already talked to you about this, every time (i tried all) i can't reboot or shutdown my phone, it goes in bootloop and goes in eRecovery saying that i have to factory data reset because i have a problem with boot. if i don't shutdown or reboot my phone, it work normal but this is a huge limit and every time a have to restore a system and boot backup for restart.
Ah and i have to say that the frist time that i installed Nougat and rooted my phone with your kernel (i don't know which version) it worked perfectly ( i could reboot). I tried to install Viperium, something went wrong and from here i always have this problem with your kernel
TZombi1234 said:
Man, i already talked to you about this, every time (i tried all) i can't reboot or shutdown my phone, it goes in bootloop and goes in eRecovery saying that i have to factory data reset because i have a problem with boot. if i don't shutdown or reboot my phone, it work normal but this is a huge limit and every time a have to restore a system and boot backup for restart.
Click to expand...
Click to collapse
tell me your whole phone detail... rom kernel recovery and ur method of flashing,,, also, recovery.log too
HassanMirza01 said:
tell me your whole phone detail... rom kernel recovery and ur method of flashing,,, also, recovery.log too
Click to expand...
Click to collapse
I flashed Twrp 3.1.0-2 with fastboot. "i uploaded screen of phone's info and recovery_log zipped." The kernel is elite kernel v9, the rom is Nougat from here ( https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 ).
TZombi1234 said:
I flashed Twrp 3.1.0-2 with fastboot. "i uploaded screen of phone's info and recovery_log zipped." The kernel is elite kernel v9, the rom is Nougat from here ( https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 ).
Click to expand...
Click to collapse
first of all i wrote in my thread that you should have a valid build number,,,
2nd, the log u uploaded is not required,,, recovery.log required,,,
flash correct rom and get a valid build number before flashing elite kernel
HassanMirza01 said:
tell me your whole phone detail... rom kernel recovery and ur method of flashing,,, also, recovery.log too
Click to expand...
Click to collapse
HassanMirza01 said:
first of all i wrote in my thread that you should have a valid build number,,,
2nd, the log u uploaded is not required,,, recovery.log required,,,
flash correct rom and get a valid build number before flashing elite kernel
Click to expand...
Click to collapse
Before i had b366 build, and i had the same problem. Now i have test-keys because i tried some "solution".
For the recovery.log, i don't know what do you mean, the file that i uploaded needs to be opened with notepad (i used notepad++).
If you mean another log file, can you explain me how i can take it?
I know how to open logs... After flashing my kernel, go to advance and copy log to sd...nd send me... Also get a valid rom...
HassanMirza01 said:
I know how to open logs... After flashing my kernel, go to advance and copy log to sd...nd send me... Also get a valid rom...
Click to expand...
Click to collapse
I tried to install B380, something went wrong i guess(because i still have test keys) but now i can reboot and shutdown with your kernel but i still have test keys, and i have root with busybox and it works 100%...... is strange.... by the way i uploaded recovery.log too....
TZombi1234 said:
I tried to install B380, something went wrong i guess(because i still have test keys) but now i can reboot and shutdown with your kernel but i still have test keys, and i have root with busybox and it works 100%...... is strange.... by the way i uploaded recovery.log too....
Click to expand...
Click to collapse
you should rollback to MM and then do a proper update to Nougat,,, also, you didnot flashed my kernel so there is no installation in that log... no benefit to me of that log...
HassanMirza01 said:
you should rollback to MM and then do a proper update to Nougat,,, also, you didnot flashed my kernel so there is no installation in that log... no benefit to me of that log...
Click to expand...
Click to collapse
Sincerely i'm ok now with my phone. If for some motivations i get another time the same problem i will use your advices and i have to say that you are so kind to help me.Thanks man.
HassanMirza01 said:
you should rollback to MM and then do a proper update to Nougat,,, also, you didnot flashed my kernel so there is no installation in that log... no benefit to me of that log...
Click to expand...
Click to collapse
I installed B371: From test-keys to MM(b123) to Nougat B371. Now i tried to install elite kernel v9....
(In the recovery.log..... yes i flashed two times the kernel....)
https://drive.google.com/file/d/0By44578ZYKVNaHA5cTVZWXB6SXM/view
TZombi1234 said:
I installed B371: From test-keys to MM(b123) to Nougat B371. Now i tried to install elite kernel v9....
(In the recovery.log..... yes i flashed two times the kernel....)
https://drive.google.com/file/d/0By44578ZYKVNaHA5cTVZWXB6SXM/view
Click to expand...
Click to collapse
now u should not have any issue,,,
HassanMirza01 said:
now u should not have any issue,,,
Click to expand...
Click to collapse
Yeah because is strange that Only me have this issue, i unlocked the access to the file on Google drive
HassanMirza01 said:
now u should not have any issue,,,
Click to expand...
Click to collapse
In the log file i saw that when i did the backup the auto folder name is NRD90M test-keys, but i have B371 build
TZombi1234 said:
In the log file i saw that when i did the backup the auto folder name is NRD90M test-keys, but i have B371 build
Click to expand...
Click to collapse
thats no issue,,, we also have same name,,, and all the zip flashed correctly,,, you should have no issue now,,,
HassanMirza01 said:
thats no issue,,, we also have same name,,, and all the zip flashed correctly,,, you should have no issue now,,,
Click to expand...
Click to collapse
aaaaaaaaaand nope, i still have the issue.....
and i can confirm that the cause is your kernel, because i restore the boot partion from a backup did before flash the zip and the phone restart without superuser.
I tried the modded supersu that Radish95 linked. After flashing the phone doesn't start. restored backup. Working as well as before without superuser...
TZombi1234 said:
aaaaaaaaaand nope, i still have the issue.....
and i can confirm that the cause is your kernel, because i restore the boot partion from a backup did before flash the zip and the phone restart without superuser.
I tried the modded supersu that Radish95 linked. After flashing the phone doesn't start. restored backup. Working as well as before without superuser...
Click to expand...
Click to collapse
haha,,, there is something weird with your device,,, supersu also working for us,,, last solution, wipe dalvic and cache and flash v9.1,,, may be encryption causing issue,,,
Related
DISCLAIMER
I'm not responsible for any damage, bootloop, bricked or broken handsets.
Notice
The recovery can't be flashed to the handset with locked bootloader! Unlock it first!
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom and stock (with some remarks) ROMs to your device, repair broken file systems, and root your device.
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Update 29.03.2016
It's alive! First experimental working build published at internal 4pda Russian board.
Download
TWRP 3.0 M86 fastboot flashable image
TWRP 3.0 M86 flashable zip
Stock Recovery flashable zip
Unlocked BL flashable zip
Install
With BL unlocked reboot into fastboot mode and flash:
Code:
fastboot flash recovery TWRP_3.0_m86.img
Cautions
Before flashing stock rom with TWRP replace bootloader file with unlocked one inside rom archive!!!!
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)
JUST IN CASE this is an April fools.... I'll wait ?
Great mate, u've stolen my idea in the end, right ?!
Gooooood work, thank u very much ! Testing wip :highfive:
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
Nein, first step doesn't work
Flashing unlocked BL through stock recovery, I get always the same result :
FIRMWARE CORRUPT
Click to expand...
Click to collapse
faust93 said:
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Click to expand...
Click to collapse
*Working fine
PYCON said:
Nein, first step doesn't work
Click to expand...
Click to collapse
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
toms157 said:
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
Click to expand...
Click to collapse
Ahahah yes yes but the purpose of BL_UNLOCKED.ZIP is to unlock bootloader. But in order to flash it correctly... we've to have the bootloader already unlocked
Damn it, it's really stupid, right ?
PYCON said:
Damn it, it's really stupid, right ?
Click to expand...
Click to collapse
Filename could lead to confusion, sure... It's needed for this :
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)"
Click to expand...
Click to collapse
Meanning flash 3 files from custom recovery without rebooting
Anyway this is not a catch-22, leaked beta from tutorial is the entry point
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
showofdeth said:
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
Click to expand...
Click to collapse
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
naboleo said:
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
Click to expand...
Click to collapse
Oh man that's great to hear! Thanks. Bought myself a laptop specifically to get my PRO 5 all TWRP'd up.
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
showofdeth said:
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
Click to expand...
Click to collapse
Never had troubles to downgrade to leaked beta
naboleo said:
Never had troubles to downgrade to leaked beta
Click to expand...
Click to collapse
Brilliant. Thanks a lot. Can't wait to hear people's experiences with this.
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
That TWRP works perfectly for me, backup nandroid, restore it, flash ZIP rom and ZIP other ( Xposed, etc ), no problem at all :highfive:
Good job !!! Great, thx !!!
Thank you so much for this!!! could i ask you how you managed to create a recovery for the pro5?
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
I assume youare still on 5.6.1.19: Thats an error with this version.... put the updatefile manually (in the PC) on the external sd and flash via TWRP... you should later update your modified Pro 5 to 5.1.3.0, the error ist gone then...
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
Copy UPDATE.ZIP from PC to phone BUT CONNECTING THE PHONE WHEN IT'S OPENED TWRP
MTP mode works great, even u'r on 5.6.1.19 :highfive:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
PYCON said:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
Click to expand...
Click to collapse
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
cedric3 said:
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
Click to expand...
Click to collapse
Uh I didn't know that a new version was released... Maybe, I could be. I download it again and try... Thx man ! :highfive:
The last version can't read the micro sd.
Hey guyzz,
Anyone here have rooted desire 820 with marshmallow rom. If yes plz reply
Yes, i have rooted my device after updating to marshmellow.
how did u do that.... I tried many times ... Could u tell me how ?
I tried all the tutorial in the internet and no help... Succeeded in unlocking boot loader and installing twrp. But SUbinary is not installing.
This is the error which i get
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/mmcblk0p43
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
Click to expand...
Click to collapse
rahulbmg said:
how did u do that.... I tried many times ... Could u tell me how ?
I tried all the tutorial in the internet and no help... Succeeded in unlocking boot loader and installing twrp. But SUbinary is not installing.
This is the error which i get
Click to expand...
Click to collapse
Try this supersu zip
http://xiaomitips.com/download/supersu-flashable-zip/
subhashdas said:
Try this supersu zip
http://xiaomitips.com/download/supersu-flashable-zip/
Click to expand...
Click to collapse
No. Not working ....same issue... I have tried all the versions... And are you using desire 820U... ?
rahulbmg said:
No. Not working ....same issue... I have tried all the versions... And are you using desire 820U... ?
Click to expand...
Click to collapse
I have HTC desire 820 dual sim (Qualcomm)
subhashdas said:
I have HTC desire 820 dual sim (Qualcomm)
Click to expand...
Click to collapse
How did you root ur phone... did u face any problem like this ... I am able to root the lollipop but not marshmallow .. Can you help me
rahulbmg said:
How did you root ur phone... did u face any problem like this ... I am able to root the lollipop but not marshmallow .. Can you help me
Click to expand...
Click to collapse
I faced problem when rooting with supersu 2.56, but got successful with supersu 2.76 (above link). No other problem for me.
subhashdas said:
I faced problem when rooting with supersu 2.56, but got successful with supersu 2.76 (above link). No other problem for me.
Click to expand...
Click to collapse
ANy way i tried with 2.76 and 2.77 and no luck....
By the way do you know what this means ?
- Finding boot image
--- Boot image: /dev/block/mmcblk0p43
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
Click to expand...
Click to collapse
Anyone ????
rahulbmg said:
ANy way i tried with 2.76 and 2.77 and no luck....
By the way do you know what this means ?
Anyone ????
Click to expand...
Click to collapse
I think ramdisk is related to kernel.
which TWRP are you using?
is it this one http://forum.xda-developers.com/des...-desire-820-recovery-twrp-recovery-3-t3373480
if not then try the twrp first if you still face the problem you could try to reflash the marshmellow ruu and then try again to relock bootloader, flashing TWRP and then flashing supersu process.
subhashdas said:
I think ramdisk is related to kernel.
which TWRP are you using?
is it this one http://forum.xda-developers.com/des...-desire-820-recovery-twrp-recovery-3-t3373480
if not then try the twrp first if you still face the problem you could try to reflash the marshmellow ruu and then try again to relock bootloader, flashing TWRP and then flashing supersu process.
Click to expand...
Click to collapse
Man you are a life saver.... It worked..... The problem was with the recovery ..... this recovery worked Thanks a lot man
rahulbmg said:
Man you are a life saver.... It worked..... The problem was with the recovery ..... this recovery worked Thanks a lot man
Click to expand...
Click to collapse
I have rooted and installed xposed framework, after that i have been facing a problem that "HTC Backup" has stopped working.
Now i have question for you, i assume that you have rooted your phone but not installed the xposed framework, do you face any problem with htc backup app?
subhashdas said:
I have rooted and installed xposed framework, after that i have been facing a problem that "HTC Backup" has stopped working.
Now i have question for you, i assume that you have rooted your phone but not installed the xposed framework, do you face any problem with htc backup app?
Click to expand...
Click to collapse
HTC backup app is working...I have not installed xposed till now. And it has option only to restore from previous backup.
rahulbmg said:
HTC backup app is working...I have not installed xposed till now. And it has option only to restore from previous backup.
Click to expand...
Click to collapse
OK, Thanks
So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash
sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).
sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument
Which TWRP did you use?
sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.
Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse
Have u tested change boot partition ?
yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse
ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse
ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse
ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse
ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!
I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.
I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.
hello, i have a P9 lite from 2016 + twrp. how do i install an update 'update.zip'?
toto6976 said:
hello, i have a P9 lite from 2016 + twrp. how do i install an update 'update.zip'?
Click to expand...
Click to collapse
Hello dude,
sorry but you should post more info about your device...
What is your complete firmware ? ( settings > device info... example VNS-L31C432B381 )
Which update would you like to do ? A simple update of your firmware ?
Which TWRP version do you have ?
Twrp Elite 3.2.1-0
The firmware is not original. I installed the C432B414 a while ago but I don't know how ...
The proposed update weighs 2 GB. it's the C432B418-Full.
EMUI 5.0.3. Android 7
I don't know the difference between a simple update or a firmware update. I would only like to install the proposed 'update.zip' file.
toto6976 said:
Twrp Elite 3.2.1-0
The firmware is not original. I installed the C432B414 a while ago but I don't know how ...
The proposed update weighs 2 GB. it's the C432B418-Full.
EMUI 5.0.3. Android 7
I don't know the difference between a simple update or a firmware update. I would only like to install the proposed 'update.zip' file.
Click to expand...
Click to collapse
Mmm, does not original firmware mean ?
You didn't said but i bet your device is L31, isn't it ?
Updates won't install via TWRP and "only" update.zip, you must use HuRUpdater...
Are your firmware 100% working ? If yes, i suggest to use
TWRP 3.1.1-1 by HassanMirza01 then to follow the procedure
in the HuRUpdater appropriate thread.
That's it. If you need some further info just tell.
Cheers
Yes, it's L31.
Hello,
I think I already have the TWRP version of HassanMirza installed. I will check this morning.
The firmware is not original indeed. This is an update that I had installed. In the meantime, I have lost the bootloader unlock code. Do you know if there is a way to retrieve it from the mobile since it is currently unlocked?
Hello,
How do I replace my current TWRP with that of HassanMirza? I put it on SD card and I flash it?
If it doesn't work, what will happen?
Brick?
I'm going to do a 'nandroid backup'. Via adb, is it possible? with the command 'adb backup --twrp'?
toto6976 said:
Yes, it's L31.
Hello,
I think I already have the TWRP version of HassanMirza installed. I will check this morning.
The firmware is not original indeed. This is an update that I had installed. In the meantime, I have lost the bootloader unlock code. Do you know if there is a way to retrieve it from the mobile since it is currently unlocked?
Click to expand...
Click to collapse
toto6976 said:
Hello,
How do I replace my current TWRP with that of HassanMirza? I put it on SD card and I flash it?
If it doesn't work, what will happen?
Brick?
Click to expand...
Click to collapse
toto6976 said:
I'm going to do a 'nandroid backup'. Via adb, is it possible? with the command 'adb backup --twrp'?
Click to expand...
Click to collapse
Heyho
3.2.1-0 TWRP have some issues and it's not guaranteed it will 100% work,
that's because i suggested you to install 3.1.1-1 version...
I don't know how to retrieve the code, maybe you'll need to pay 4€
and use DC unlocker to read it again...
If you will use HuRUpdater and ( suggested ) keep the TWRP,
your bootloader will not be re-locked.
Your current TWRP can be replaced flashing it into the recovery.
How to do it ? Place the TWRP into your SD card, reboot recovery,
tap install, then in the bottom right tap install image, select your 3.1.1-1 TWRP.
Next tap on recovery partition and swipe to flash.
When finished reboot recovery to verify if it's really changed.
There is no reason why it shouldn't work.
I don't know about adb, you can try... but i think you can do a
nandroid backup rebooting into recovery and
selecting every partition you see...
Beware using 3.2.1-0 TWRP, as i told you it could cause unexpected issues.. :cyclops:
P.S.: a good rule before making a nandroid backup or attempting an
update/downgrade/switch ROM are
to remove all the security of the device..
fingerprint and / or password and / or pattern.
Dadditz said:
Your current TWRP can be replaced flashing it into the recovery.
How to do it ? Place the TWRP into your SD card, reboot recovery,
tap install, then in the bottom right tap install image, select your 3.1.1-1 TWRP.
Next tap on recovery partition and swipe to flash.
When finished reboot recovery to verify if it's really changed.
There is no reason why it shouldn't work.
Click to expand...
Click to collapse
Good evening,
I went to see for the TWRP of HassanMirza. This is version 3.2.1. Why are you telling me to take 3.1.1.1 ??
I finally found version 3.1.1.1 on the xda page of HassanMirza. I install it tomorrow. We will see if it goes well because in fair I downgrade from 3.2.1 to 3.1.1 !?
I found the link I followed to install the LC432B414 version:
https://www.stechguide.com/huawei-p9-lite-b413-b414-nougat-update/
I keep it under the elbow if it goes wrong ...
I forgot to say that, if it is possible, I would like to keep the root and the OTA updates ... Is (this possible ??
toto6976 said:
Good evening,
I went to see for the TWRP of HassanMirza. This is version 3.2.1. Why are you telling me to take 3.1.1.1 ??
I finally found version 3.1.1.1 on the xda page of HassanMirza. I install it tomorrow. We will see if it goes well because in fair I downgrade from 3.2.1 to 3.1.1 !?
I found the link I followed to install the LC432B414 version:
https://www.stechguide.com/huawei-p9-lite-b413-b414-nougat-update/
I keep it under the elbow if it goes wrong ...
I forgot to say that, if it is possible, I would like to keep the root and the OTA updates ... Is (this possible ??
Click to expand...
Click to collapse
Hi,
sorry, you installed B414 firmware in your phone using that guide ?
If yes, which recovery did you used ?
Are your current ( B414 ) firmware 100% working ?
As i know firmwares cannot be flashed that way, that's because some
DEVs started create scripts capable to do that and because
i suggested you to use HuRUpdater method..
Anyway the device are in your hands and you can do anything you want...
Ahmmm, for your latest question, as i know, flashing a firmware will erase
the root ( not necessarily the recovery ), but you can easily reflash it...
Cheers
sorry, you installed B414 firmware in your phone using that guide ?
Click to expand...
Click to collapse
Yes. This is the reason why I needed the bootloader code because I believe it had deleted TWRP after the flash.
If yes, which recovery did you used ?
Click to expand...
Click to collapse
TWRP Elite 3.2.1, The one that is currently installed I believe.
Are your current ( B414 ) firmware 100% working ?
Click to expand...
Click to collapse
I don't know what it means and what I can measure it with?
i suggested you to use HuRUpdater method..
Click to expand...
Click to collapse
This is what I intend to do by putting in it the twrp of Hassan after having flashed it on my mobile
as i know, flashing a firmware will erase
the root ( not necessarily the recovery ), but you can easily reflash it...
Click to expand...
Click to collapse
Precisely, currently installed root is 'super su'. But I had to remove it because too many problems with some application. I was wondering if 'Magisk' works on this mobile? And if so which version?
I would like to recover my bootloader code before doing any manipulations in case it goes wrong. My mobile is unlocked but no longer root. I tried this command but it doesn't work:
adb devices
adb shell
su -c "grep -m1 -aoE 'WVLOCK. {14} [0-9] {16}' / dev / block / mmcblk0p7 | grep -aoE '[0-9] {16}'"
How can I recover this code which is on my mobile since it is unlocked?
toto6976 said:
Yes. This is the reason why I needed the bootloader code because I believe it had deleted TWRP after the flash.
Click to expand...
Click to collapse
That's strange (at least for me)
toto6976 said:
Elite 3.2.1, The one that is currently installed I believe.
Click to expand...
Click to collapse
Yep, really strange (at least for me)
toto6976 said:
I don't know what it means and what I can measure it with?
Click to expand...
Click to collapse
I meant if " everything " is working into the device...
toto6976 said:
This is what I intend to do by putting in it the twrp of Hassan after having flashed it on my mobile
Click to expand...
Click to collapse
Ok, i never used the method you wrote into the guide you posted above...
toto6976 said:
Precisely, currently installed root is 'super su'. But I had to remove it because too many problems with some application. I was wondering if 'Magisk' works on this mobile? And if so which version?
Click to expand...
Click to collapse
You have to check, i don't have that device anymore...
toto6976 said:
I would like to recover my bootloader code before doing any manipulations in case it goes wrong. My mobile is unlocked but no longer root. I tried this command but it doesn't work:
adb devices
adb shell
su -c "grep -m1 -aoE 'WVLOCK. {14} [0-9] {16}' / dev / block / mmcblk0p7 | grep -aoE '[0-9] {16}'"
How can I recover this code which is on my mobile since it is unlocked?
Click to expand...
Click to collapse
Sorry, i don't know how and i don't know if it's possible...
Hello, update successfully
Nos, i would like to know how to install magisk and, if IR is possible, wich version to take ?
Thank you
toto6976 said:
Hello, update successfully
Nos, i would like to know how to install magisk and, if IR is possible, wich version to take ?
Thank you
Click to expand...
Click to collapse
Hi, that's a good news for you...
For magisk you should go in his main thread, then hit on the
Magisk's GitHub Page link.
I don't know which version, you have to try by yourself.
Download the installer (multiple versions, ex. 20.4 & 20.3 & 19.4), the uninstaller and the apk.
Flash the uninstaller into the twrp if something goes wrong.
Follow the installation guides...
Good luck.