Database Users

[PSA] Information Regarding Firmware Version 5.1.1 A.K.A. ROOT

Root Method​Amazon has just released a new firmware update, blocking the fastboot commands necessary for root/custom ROMs (fastboot boot). We need more information about this update. If people could update their tablet to this latest version without getting it stuck in the botloop, we could see the information regarding the update and get root out for this ROM ASAP. Thanks to anyone who sacrifices root/ROMs for development.
List of things you can't do:
Downgrade to an earlier release
Boot a .img from Fastboot
List of things you can do:
Install and use the Google Play Framework and Services
Root
Install Custom ROMS via FlashFire
Remove Lockscreen Ads
Remove Amazon Bloatware
Feel free to comments things that worked/didn't work on your device.
ANYONE WHO IS ON 5.0.x AND WANTS TO GO TO 5.1.1 WITHOUT ANY COMPLICATIONS AND KEEPING TWRP, GO TO THIS LINK: http://forum.xda-developers.com/showthread.php?t=3265594

Can anyone test if the Google Framework Install tutorial works on this update?

It does.
However, DON'T TRY TO DOWNGRADE BACK TO THE 5.0.1 FIRMWARE. IT WILL BRICK YOUR DEVICE. I found that out the hard way. It's stuck in a preloader reboot-loop.

Added list of what you are able to do on the update.

Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.

blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
You have to go through the setup, but originally I just skipped that part, even though I was next to a Starbucks, and it didn't connect.

Doesn't Starbucks wifi require you to click to agree to their terms of use before you can freely browse or download? So Internet would not actually be available initially to the update script.
Pretty much, I trust amazon on this issue, as far as I can throw them. I don't want to presume that a OTA proccess won't silently connect, while the Fire otherwise appears to be waiting for the ok to connect to wifi.

Bloat removal
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01

craigs23 said:
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
Click to expand...
Click to collapse
Thanks, added.

This is bullsh!t. the ENTIRE reason about 5,000 people bought this tab last week is because of root, fastboot and CM. If I get my tab soon I can offer any assistance you need. I'm not sure if it will be possible to dump any part of the system, boot, etc. without fastboot or twrp, but I'm sure we could figure something out.

blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
When I setup mine it asked to turn on wifi I skipped it and said later.
Sent from my SM-N910T3 using Tapatalk

Has anyone tried kingroot on 5.1.1?

Experts please take a look at this

What was changed in OS 5.1.1?

If anyone can get the frimware update or capture it id like to test it out

running 5.1.1 & all I could manage to load was Google Account manager. The rest (Framework Services, etc) says something like "App not installed" & nothing else, every time I try.
scratch that..... found found a couple that did load for me.

Damn! I did this (tried to downgrade, got bricked) a day before you posted this. I should probably replace mine...

My unrooted Fire upgraded to 5.1.1 last night before I had any idea it was coming. I'm willing to try whatever is needed to assist with further research if I could be of any help.

unlikely it would work, but did anyone on 5.1.1 try
Code:
fastboot -i 0x1949 boot twrpfilename
Sent from my KFFOWI using Tapatalk

5.1.1 update file
Here is the 5.1.1 update file
snap42.com/update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip

Oneplus 5 stuck on setup?

EDIT: Solution was to sit with OP5 technician which flashed my ROM to Oxygen 4.5.1. After this didn't do it, I RMA-ed it and got a new OP5.
EDIT: TL;DR: After updating OP5 to 4.5.5, It doesn't recognizes sim nor wifi, and can't rollback to 4.5.3 that did and stuck on phone setup (needs wifi). ADB devices is empty, I have Google USB Driver from SDK, Windows 10
Hello,
I just got a new OP5 today.
Opened it in the store, came with Oxygen 4.5.3 outta the box.
I putted the sim in, and I connected to the store's wifi, all was good and even had a phone call to my mother to check if the mic and speaker are working well.
Then when I got home, I upgraded the OS to 4.5.5 through the settings, where Android suggested. I'm new to OP and android (moved from iphone 5) and so if there is a right way to do it, and that's not it, I wouldn't have known.
Then, OP5 didn't recognize the sim anymore and couldn't start the wifi (switching it on wouldn't work, it would do nothing), so I tried Factory reset. Unfortunately it didn't reset the OS as well and now I'm stuck outside can't use my sim card or connect to my home wifi to setup the device.
Tried installing OP5 usb drivers (show when connecting the OP5 to PC) and press the power button and lower speaker volume together, then flush the 4.5.3 OS through USB, but it doesn't recognize ZIP folder and when I tried to unzip and send boot image (cmd->"adb sideload boot.img) it started and then failed at 0%.
Please help, the phone right now is unusable.
Tried the Factory reset through settings, but it took so long I thought it was stuck, so I did it through recovery screen.

Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...

ultramag69 said:
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
Click to expand...
Click to collapse
Why should it be replaced in less than a week? Also, isn't there a fix for adb problem so I could flash 4.3.5? Maybe a remote takeover?

Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.

ultramag69 said:
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
Click to expand...
Click to collapse
I can't pass the "Connect to Wifi" in the initial setup of the android, as it finds no wifi networks (but of course there are, when I use the sim in my iphone it works properly and there are wifi networks). So I don't know how can I get the IMEI number.
Right now my PC recognizes the OP5 connected via USB, but "adb devices" bring back empty list.
I think that once I get that working, I could unlock the bootloader. But I can't seem to be able to enable dev mode in settings - I can't get there.
I can only get to the recovery screen beyond the initial steps of setting up android.
Right now there is no important data on the phone and I have my laptop which is virgin to ADBs and Drivers (didn't use it to try to resolve it).
What driver and where do I get the right ADB so I could load 4.5.3 from usb to the phone?

When you upgraded, did you wipe cache and dalvik?

Binary Assault said:
When you upgraded, did you wipe cache and dalvik?
Click to expand...
Click to collapse
Wiped after the upgrade whem problems started

Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.

ultramag69 said:
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
Click to expand...
Click to collapse
It doesn't seem like I can skip it. Can't pull down a menu or anything
I guess only Oneplus can help me now?
Do you have any suggestion on fixing adb so it would recognize the OP5?

No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...

ultramag69 said:
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
Click to expand...
Click to collapse
Welp it is a pickle.
Going to go live chat with OP "level 2" representative.
See if they wipe the phone out and restore an older ROM.
If that't not going to work, RMA it is :/
Shame. A new phone. Took only one picture with my dad when we opened it back at the store. nothing else.

Unfortunately bad things can happen... You just got to be the one who got the dud this time round.....
Here's hoping it's the last time....

you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.

OcazPrime said:
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
Click to expand...
Click to collapse
When I connect the OP5 to the PC there are no folders under it (Computer -> OP A500 -> no folders), but I'll try and give it a shot. see what happens. Will update this reply.

Update:
After Oneplus flashed Oxygen 4.5.1 on the phone and some other magic I was able to skip wifi step on setup, yet still when I try to activate it it won't budge. the slider won't move and it looks as the page is being refreshed. Also, when I try to get into sim section in settings it would just freeze and alert the program stopped and suggest to close or wait.
Oneplus says it is hardware issue, and the fact it happened when I upgraded to 4.5.5 from settings menus is coincidence. They say I need RMA it.
If anyone knows how to fix it then I'm more than welcome to hear it.
EDIT: it also won't shut off unless I long press the power button.

XT1644 No longer connects to any PC

I have been going nuts as of late trying to figure what happened with my Moto G4+. It was working fine, could connect to my pc no problem, then all of a sudden out of the blue, nothing. It only connects as a charger. I've checked it with different USB cables, different ports, even 3 different computers. Still will only connect as a charger. I've even tried it in recovery mode, still not recognized by any computer. I have not restored the phone as of yet due to a ton of pictures and whatsapp chats that I need to save. I have installed Xender to start to move some stuff off the phone, but I'm not too sure that a factory restore would help this. I have read that it could be a USB issue with the phone, either the port or the chip it uses itself. While I know I can replace the port, the chip is beyond what I have equipment for. I have turned on developer mode, and its set the USB mode to MTP by default, I've tried changing it to PTP as well, but the phone will only charge and is never recognized by the pc. All software and drivers have been updated, uninstalled thoroughly, reinstalled multiple times to no avail.
Is there any chance that this IS some form of software thing? Or am i just going to have to use the Zender app to move things between my phone and pc from now on. Until I can possibly send it off to Lenovo since it IS under warranty.
Any help is appreciated.

Just got off the phone with Lenovo/Motorola, and they are giving me the option that I wasn't wanting to hear, do a complete factory reset on the phone after removing the account information from the phone. Gee, that's what I was trying to avoid. Looks like I'll have to figure a way to completely back up the phone via wireless and hope I can save all my data needed to restore it later.
Will be trying the factory reset, but I'm not feeling very good about this at the moment. Will update later when I can get this done. But in the meantime, please suggestions.
Thank you again.

Provide some more info about what ROM you're running, etc... The more info you can provide about your situation, the more likely you're gonna be helped.
What ROM:
Stock? If so, what version and security patch?
Custom ROM? If so, which one and build date..?
I also have the xt1644 and don't have any issues whatsoever connecting to my Laptop, granted I run Linux on my personal PC. I also have zero trouble connecting to the PC's at my work which all run Windoze.
You mentioned you've tried connecting to your PC thru Recovery, so I would have to assume you have TWRP installed, no? If so, which version and by whom?

I'm running full stock room, no mods, build NJPS25.93-14-4, security patch of March 1, 2017. As for the recovery mode, that was the stock recover/bootloader. To where it should be raw adp mode. Even in that mode it is never seen by the computers I've tried. I can't install the newest security update because it won't mount internal nor external memory. I'm at work at the moment and if you need any more information, please let me know.
Thank you

rainfellow said:
I'm running full stock room, no mods, build NJPS25.93-14-4, security patch of March 1, 2017. As for the recovery mode, that was the stock recover/bootloader. To where it should be raw adp mode. Even in that mode it is never seen by the computers I've tried. I can't install the newest security update because it won't mount internal nor external memory. I'm at work at the moment and if you need any more information, please let me know.
Thank you
Click to expand...
Click to collapse
Did the factory reset work? As I'm suffering from a similar problem

Have not done the reset yet, still finding the best way to back up everything, plus finding the time. Will be doing it sometime this weekend though

I just did the compete factory reset, and as i feared, it made no difference. So all my data is gone (saved what I could) and will have to figure a way to get a backup phone working while I have to send off the phone for repair. At least it's under warranty.

I have the same problem. I didn't do the factory reset (yet), but you confirmed my fear, the factory reset won't fix it. Too bad my phone isn't under warranty anymore.
Did you send it for repair?
What was the problem after all?
My XT1640 seems to be falling apart. Bluetooth stoped working out of the blue. Can't read SD card anymore and now USB connection isn't working.

My apologies for not doing a follow up post. I was able to send it back to Lenovo and the replaced the phone so it's back up and running fine. If it's out of warranty, then I'm not sure what avenue you can take aside from maybe finding one that's got severe screen damage but a good non blacklisted board and change it out. Aside from that, I can't tell you what they found wrong with it. I would assume the usb chip may have gone out, but without knowing the fate of my original phone, I can't say.

How can I recover data from my Core Prime SM-G360G with a broken screen of death? :-o

Hello experts!
First off I do admit I have cross posted some information here. Perhaps I should have just asked here first. As a lot of research I have been doing lead me here. I am also aware of the XY problem. So I am giving what information I have on my problem and what I have done to resolve it. In a nutshell I need to recover app data from internal storage.
So here is yet another story of a dropped Samsung Galaxy BSOD. The broken screen of death! :-o
So I dropped my phone and the screen broke, fixed it then put on a screen protector that fractured the new screen in my pocket, of all things. Through that it spiraled out and it needed a new LCD as well as screen which failed to repair as LCD remains blank now. I suspect the display controller has somehow fried. Decided to give up and buy a new phone.
My broken phone is a Core Prime G360G. The digitizer doesn't respond. The LCD is blank. The side buttons, volume, power and home, work fine.
The good news. It turns on and technically still works. It has no screen lock. I can plug it in to computer via USB and it mounts over MTP. I can also install apps remotely (so to speak) from another computer from the Play site. I've installed Samsung Switch this way. Switch does work and I managed to back up files from the Windows program which is good but in my case it isn't smart enough as it doesn't back up app data which I need. I also have AirDroid installed and can reach it that way I but didn't enable mirroring before the incident. Trying to use that to download an app (~10MB in my case) just results in the browser stalling.
The bad news. It is not rooted. It has stock standard firmware. USB debugging is not enabled. Last time I tested OTG wasn't supported. At least not for OTG USB sticks.
So in effect it's rooted without being rooted! Yes, i know, I know, Android rule of thumb; before you accidentally drop your phone, even without planning it, and not being a seer, enable USB debugging for no apparent reason! It all makes sense now.
I've spent the last two weeks reading forums all over the place, blogs and watching videos about how to recover data with a broken screen. And in almost all cases they tell you to enable USB debugging. Well that's nice advice and about as useful as advising someone with a broken toilet to sit down, do their business and then flush it! And is met with equally crappy commentary pointing the conundrum out.
My computer has Windows (Vista) and Linux (Mint 64). I read all about ADB and installed this on both Windows and Linux. And tried to talk to it that way with adb and fastboot which failed. I then read of Samsung devices being different, with a download mode, and using this Odin or Heimdall program. So I could "see" the process I tested with my new phone (a J5 Prime as it happens) and learned I needed to use download mode and how to enter it on boot. Recovery mode didn't work as expected. Heimdall was the only program that would work. I managed to view the PIT on my J5. Odin did see my phone but I found the interface harder to work with at first.
I tried on my Core. Blindly got it into download mode. Heimdall could see it. But the transport was buggy as I kept getting USB errors. I ended up removing it then compiling Heimdall v1.4.2 from source. This worked better, even though it was giving empty bulk transfer warnings, but it managed to download the PIT file. So at this point I can blindly get my Core into download mode and am able to communicate with it using Heimdall.
This is where I am at. I would prefer it if a screen mirroring app could be installed that would load up and activate remotely when a client run on my computer is loaded up. I don't care if it is VNC or how it connects. But it would need to load itself up on the phone and work without needing intervention on the phone and without USB debugging. If there is an emergency mirroring app on the Play store or even an APK that can be installed remotely, using AirDroid or any other means, I would be happy to test it. I'd write one myself if knew how to write an app! LOL.
If USB debugging could be enabled by any remote means then I am welcome to hear how. It opens a window to possibility. But a window that is hard to open if it's locked.
So I would prefer to keep this at the app level if possible. Since apps can help. But if need be as long as it doesn't destroy data I am willing to install a custom recovery image. It looks like I will need to do this as I have exhausted all other possibilities. At least, when I read of the latest broken screen mirroring app, there is always a catch of it needing debugging or activating on the phone.
Although there is support for other Core Prime variants, support for my specific G360G model seems to be lacking. The information I read looks vague at best. I read about CWM and TWRP. But on the TWRP site, although there is Core Prime images, nothing is listed for exactly a G360G. There is no point to me flashing TWRP recover image only to find it doesn't work and I have bricked recovery mode. I'd look like a right twerp!
So guys, after all the info I have given you, what's the next step? Thanks.

Okay so just an update here. I have some good news and bad news on my part. I've been hacking around with customising recovery and modifying compatible recovery images in order to get debugging activated.
The good news is I got USB debugging enabled. The bad news is my computer is unauthorised.
I'm stuck at this point. I updated the adb_keys file with what was on my computer and it won't budge. I finally get somewhere and now I've once again hit a wall. This is just so annoying. :-x

The final countdown. After months of cracking and hacking I've broken in! I modded my hack to create the needed folder just to be sure and updated my RSA key. Applied the firmware patch and let it reboot. Even while booting I knew something was different. The digitizer started responding to my touch and making water noises. Which was strange as I never noticed it doing that before.
I issued an adb command and it was accepted. I could then browse around the system. I already had screen mirroring software installed and all it needed was USB debugging working and suddenly it worked. This was a blessing as I found that trying to do other things like going into a root shell or do an adb backup caused a requester to come up on screen. Had I not been able to satisfy that on a virtual screen I would have run into the same trap of circles I had just climbed out of. Having a rooted phone with no root access.
I was then able to install a backup app and extract the data out. Hooray! I had actually installed it from Google Play site remotely but found there was no space for it and it had failed. But the account said it was installed. With a view to a mobile I could then remove another app and install it from Play on the phone itself. Given how well this worked once I learned what was needed to be done I suppose I should make up a guide. An automated script to create an ADB patch wouldn't go far astray.

Killed P9 Lite instead of getting back to live, maybe there is a last chance?

Hello, short Story before. I got a full Hand of non working mobile phones because being full of a hell of viruses.
5pcs. younger ones.
2 Huaweis and 3 Samsungs.
Well so far 4 PCs. are saved.
Getting into the phone wasn´t possible anymore. Data not important so I resettet over the Buttons to original Status. -> Worked fine.
But one Piece which is a Huawei P9 Lite guess it is a single sim? was the button method not possible cause it wanted a Software update and Installation of WLAN failed (EMUI)
Getting into the phone for any informations was also not possible because of all the viruses and not working right ahead anymore.
Well ok -> will use High Suite for stock Firmware -> this mobile phone is not supported and also couldn´t activate MTP as I am not in the phone. So far.
Next Idea -> ok. will take the C900B300 and go back to Marshmallow. From original HUAWEI site.
Took the European Version in German. Did it over EMUI (hold 3 Buttons) and worked so far but when I turned on I was stucking on the WIFI+. Even pressing the button -> further nothing anymore. So I thought -> maybe another stockfirmware useful.
Again C900B300 and then I think I did the big mistake. Took out the sdcard during it was rebooting (HUAWEI was already visible) and now it is big crap. Stucks at HUAWEI. Turning off not possible. This EMUI is not possible anymore. Just with a trick I am able to get into fastboot. Yeah. But what then? Reading TRWP which I know from Samsungs but putting it on with ODIN. ODIN doesn´t work with Huawei. Do I Need TRWP to get it back to normal Firmware? Mobile phone was never customized or anyhting else. just normal stock was on it and is the wish to get a clean back. Resetting to factory was not possible anymore.
So my questions, even I know it is my fault. Any rescue possible?
What could be the best stock Firmware. I Guess it is a single sim from Austria unlocked and unbranded. Would also take Nougat again. Just wanted to get it back to normal working and now I guess I have a big letter holder. Model from the backside is VNS-L31. More I don´t have.
Thanks a lot for any help for my being an idiot. Samsungs are much more easier than HUAWEIs.

Blimey mate,
This really just boil down to what partitions were damaged in your case- Most likely your system and data,
however since you are still Technically running unmodified emui you could manage to sort of salvage it.
The logic is this:
Most custom roms for the p9 lite build on top of emui (patching the system image) rather than replacing it (like the way samsung smartphones do)- so you could flash the rom, it would wipe your phone clean of viruses in the process and then proceed to do a hard restore back to emui.
1.) get your phone into fastboot and flash this twrp http://www.meticulus.co.vu/p/forum.html#nabble-td27
2.) Then flash this rom : http://www.meticulus.co.vu/p/ressurection-remix-for-hi6250-devices.html MAKE SURE YOU FOLLOW THE INSTRUCTIONS ON THIS SITE VERY CAREFULLY
3.)Follow this guide to do a hard restore https://forum.xda-developers.com/huawei-p9lite/how-to/tips-revert-custom-rom-to-official-t3668413
good luck!!! if you have any questions hit me up!

Hi
Hi Exiatron00,
thanks a lot for your maybe solution way. Will do it this evening after work and come back.
Hopefully it works cause as mentioned in other threads -> don´t think that the original owner opened the Debugging so that I can work over a tool. FRP locked is in fastboot. This was already mentioned in other posts which I have read here in the forums.
Thanks for your step by step explanation. Will do it. Hopefully it works. I am really pissed of my own that i was unpatient with the sdcard. That´s a mistake which shouldn´t happen. Anyway it did. So i will try to do everything to get back working again. I am from IT so I am not such a DAU but newbie with HUAWEIs. Most are Samsungs.
Will give Feedback.
CU

If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.

Hi,
well adb for flashing not working as device not found. Hi Suite installed. Guess that the USB Debugging is not enabled. hrmpf.
There is a similar thread of somebody with no enabled USB Debugging.
https://forum.xda-developers.com/nexus-4/help/fastboot-recovery-remotely-enable-usb-t2177440
He writes an solution how to enable in fast boot mode with using N4 toolkit.
Search for a p9 lite toolkit and found this
https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
may could work?
Big **** -> as Long as USB Debugging is not enabled as Long I am not able to Flash TWRP over adb.
If I connect to PC Hi Suite opens automatically. So driver should be fine as pc recognize the phone.
hm?

Got it working somehow
Exiatron00 said:
If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.
Click to expand...
Click to collapse
Hi Exiatron00,
got it working somehow!!!!
Bought a 3 day licence for DC Phoenix where you are able to put Firmware even in fastboot with FRB lock and no USB Debugging on.
So I got the IMEI and Fitting Version which is a L11.
Downloaded it original from Huawei as I still want a original stock Rom not customized which was
HUAWEI P9 Lite Firmware (VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU) only wokring one.
BUT the big Problem is that the apk Android System Web View is missing in the ROM. A known Problem by HUAWEI. Yeah now I am stucking in the Setup wizard like this guy who mentioned also the solution whell the reason of this Problem.
https://forum.xda-developers.com/hu...stuck-initial-setup-upgrade-to-t3498097/page2
So my question now. How do I get the apk on the phone still no USB Debugging? Does anyone have this Version original incl. this apk? Maybe an img. from a running working System?
Only way I am able to put the Firmware on is DC-Phoenix. It is valid still two days. Maybe someone can help me? Please?
So an Image of VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU incl. Android System Web View, so that I can go ahead and use the phone again please?
Thanks a lot.
Kind Regards.