Database Users

May Factory Image now available MXC89F

For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions

Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine

redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.

Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?

Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP

redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!

Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate

Change log ? Or its just a security update

Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.

After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...

rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk

houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?

rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck

m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!

rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!

hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.

In dire need of help to root Huawei P8 Lite.

Hi all!
First of all, Im new here, sorry if this is in wrong section (please don't delete the thread, move it to other section if needed) and that this has been posted millions of times but Im in really really dire need of help, and people told me this is best place to come to!
So here it is, I've tried countless methods and read alot of threads all over internet and nothing seem to work for me. (All info is down below just read it )
I tried with ADB and Fastboot, but where I get stuck always is with that my phone, somehow rejects new recoveries (TWRP, CWM) (???). What I mean is that when I try to start phone in a custom recovery(either holding +-volume and power button , or volume + and power or volume - and power) I get nothing(I can get him into his own recovery, but only options are to reset, shutdown and update and recovery and that is from first holding -volume and power then from fastboot and rescue mode and then by holding +volume). I got him ONCE to recovery(or whatever/however that place is called) where I can wipe partition cache and dalvik , it just stays at Huawei logo.
I tried both with scripts and with manual way where I input commands in cmd. I've bricked my phone about 4-5 times , and I know how to unbrick it with ease. What I dont know is how to get phone to take a custom recovery. And yes, I have unlocked BootLoader and followed all and every step there was in each guide I found. I tried with the most hated method (KingRoot and other kinds) but nothing.
Info you might need:
-As stated, phone is p8 lite, with marshmallow 6.0. (ALE-L21C432B584)
-BootLoader unlocked.
-I have all necessary drivers installed and all permissions on my computer for drivers to work correctly.
-Kernel Version - 3.10.86-gd9a2b44
-Yes of course I have debugging enabled everytime.
Once again, methods I have tried:
-ADB and FlashBoot
-All kinds of programs through phone (Kingroot, Iroot, KingOroot etc.. (I read that you can't root phone through this method but gave it a shot.))
-I don't remember if there was any other method to do it tbh because Ive been doing it for last 2 days and Im kinda tired and super pissed hehe.
But if I forgot/missed something of information that you need please just ask.
Sorry if there is too much of detail, I just wanted to describe my problem as perfectly as possible and as in much detail as needed.
Thank you all who will read/read (Oh the typing world) my thread I really appreciate your time and effort. All and any help regarding my problem will be tried out and appreciated ^^!

What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.

keikari said:
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
Click to expand...
Click to collapse
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.

Ebilog said:
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Click to expand...
Click to collapse
Weird, though you must have done something wrong when installing TWRP, because it removes stock recovery. Make sure you have typed everything right. Because if you type like "flash recvery" insted of "flash recovery" it shows stuff that by quick glance might seem correct. Oh I forgot you need root to reboot with terminal emulator XD mb. Could you show what fastboot shows when you install TWRP.

Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?

Ebilog said:
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Click to expand...
Click to collapse
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.

keikari said:
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
Click to expand...
Click to collapse
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||

Ebilog said:
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Click to expand...
Click to collapse
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"

keikari said:
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP

Ebilog said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Click to expand...
Click to collapse
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.

keikari said:
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
Click to expand...
Click to collapse
So i managed somehow to get the to twrp menu and i flashed supersu and i flashed new version of twrp . but i think thats what made it crash. Would it be ok if my phone stayed with 3.0.2.0 ver instead of getting 3.1.0.0?
Bcoz when i flashed 3.1.0.0 phone got stuck on 2nd logo and didnt reset or anything.
Thank god i know how to unbrick a phone at least hahahah
Edit: If this thread stays and people with problem like mine need help , feel free to pm me ill gladly help

yeah older TWRP is good if it works.
Though problems you got are still weird.

I had this problem ..
If you have restored your system and can access twrp recovery , download supersu v2.62 and install it .. this version worked for me after trying many ..
Every time my phone bricks i was downloading new whole system , instead try flashing it with twrp its better ..
Good luck .

ADB drivers

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!

[Solved] Huawei P9 Lite Bricked

Hello, I was curious if anyone could help me with unbricking my phone, my phone has no custom recovery installed, the bootloader is apparently unlocked (OEM unlocking is disabled), FRP lock is enabled, I cannot flash anything (Command not allowed), relock bootloader (Root type is at risk), Unlock bootloader (Command not allowed), any help would be appreciated.
Edit: I also cannot boot a from a recovery img locally using fastboot (Command not allowed)
EDIT: Fixed it using DC Pheonix and flashing VNS-L22C636B140 OEMINFO and flashing B160

Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275

4uvak91 said:
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
Click to expand...
Click to collapse
I cannot flash anything, so any of these do not help, thanks for trying I guess

wheellzzz said:
I cannot flash anything, so any of these do not help, thanks for trying I guess
Click to expand...
Click to collapse
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.

4uvak91 said:
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
Click to expand...
Click to collapse
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader

wheellzzz said:
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
Click to expand...
Click to collapse
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.

4uvak91 said:
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
Click to expand...
Click to collapse
The problem is I cannot unlock bootloader again, flash anything or boot into any image in fastboot mode, I always get "ERROR: (Command not allowed)", attempting to relock the bootloader shows "ERROR: (Root type is at risk)"
EDIT: I have done some research for the dload method, If I want to dload to hopefully fix it, I'll need VNS-L22C636B381, but the official link from the hicloud is dead, if anyone could help me with that, that'd be great.
Last EDIT: Ended up scratching the above idea as it didn't work, gritted my teeth as I bought DC Phoenix and will update if it works out with the .APP from the latest package I found on firmware finder.

Fastboot help

I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....

BlackHawk580 said:
I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....
Click to expand...
Click to collapse
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone

_NikO_ said:
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone
Click to expand...
Click to collapse
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery

BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check

_NikO_ said:
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check
Click to expand...
Click to collapse
Yes, I've done that too, I've tried installing various different drivers as well, it also has Windows 10 as well

BlackHawk580 said:
Yes, I've done that too, I've tried installing various different drivers as well
Click to expand...
Click to collapse
So your phone is showing up in Adb devuces without any yellow warning or anything?

_NikO_ said:
So your phone is showing up in Adb devuces without any yellow warning or anything?
Click to expand...
Click to collapse
It doesn't show up at all on the list, yeah

BlackHawk580 said:
I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all.
Click to expand...
Click to collapse
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?

BlackHawk580 said:
It doesn't show up at all on the list, yeah
Click to expand...
Click to collapse
If there isnt your computer isnt actually seeing it as an adb device

osd_daedalus said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?
Click to expand...
Click to collapse
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume up and power doesn't enter the recovery either.

BlackHawk580 said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume down and power doesn't enter the recovery either.
Click to expand...
Click to collapse
I'm not sure you can reboot to recovery from fastboot.
Some people tell you can launch "fastboot reboot recovery" but it is not a standard command and does not work for me.
In fastboot you can boot the recovery image file with
Code:
fastboot boot recovery.img
Change recovery.img with your recovery file.
Keeping it simply, can you reboot normally and reboot to recovery via adb? With "adb reboot recovery"

Fastboot is the way to flash anything
Your phone don't have to get recognized by adb, it's more for sideload or apk installation. To flash recovery, you need fastboot.
Try fastboot flash recovery recovery.img (recovery.img should be in the same folder as fastboot.exe)

Is there any news? I have a similar problem:
I boot in fastboot mode and I run `fastboot oem device-info` to check status:
Code:
$ fastboot oem device-info [15:20:59]
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
And it seems ok.
Now I try
Code:
$ fastboot flash recovery recovery.img
and it stuck there and it don't do anything.
I tried different PCs and different cables, nothing make it works!
Normally it only lasts some seconds...
What should I try?
Thanks in advance