Database Develop

Help needed! Cannot boot into either Flash mode or Fastboot mode

Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.

Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing

Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you

Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?

crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders

Nexus 6 Marshmallow stuck in fastboot loop

I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!

turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
how about this, adb NEVER EVER works in fastboot mode. that is reserved exclusively for fastboot. you have to use fastboot to flash a recovery, then the recovery to flash supersu.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
now it also seems as you have to fastboot flash a factory image as well.

turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: link removed to satisfy forum policy...
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
I asked for help before searching thoroughly enough! I figured out that I needed to download another ROM, transfer it into the phone's storage, and install using TWRP. I really didn't understand the capabilities of this fabulous application and had simply flashed it because the thread instructed me to.

Can someone PLEASE help me boot my phone into FASTBOOT mode? ( T mobile h811) on CM13

When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?

did you ever unlock the phone....?

Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.

Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)

Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.

aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed

You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.

I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit

Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know

TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.

I reasked the question in Q and A. Please help some one.

You start over. LG bridge.

Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?

The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?

Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing

thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks

* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h

the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.

Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.

travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.

Teamwin boot loop after factory reset

An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it

did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot

KindleFireHD7" said:
did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot
Click to expand...
Click to collapse
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/

meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
its failing to install the first set of drivers any suggestions?? thanks

KindleFireHD7" said:
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
its failing to install the first set of drivers any suggestions?? thanks
Click to expand...
Click to collapse
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you

Fix...
meowmix2 said:
An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it
Click to expand...
Click to collapse
Hello,
Fortunately, i was in the same position as you and that too, for a whole year and 3 months. But I was a noob at that time. With your fastboot cable to be usable(no drivers needed but just a simple program), you need to get (Minimal ADB and Fastboot. The link is provided for download. Now you need to do some research. For me I found out that the main problem was that it was a TWRP problem and nothing else. So I am guessing you ahve the exact same. You need to go to CyanogenMod Wiki(discountinued so you'll have to wait until Lineage OS gets their Wiki up and then figure it out) and from there find your device and then the installation instructions whihc include the downlaod link for TWRP. From there download the recovery(it will link you to android file host or something like that). Now you can install Minimal Adb and Fastboot(MAF) and install it wherever convenient to you. Now you can place the zip file of recovery in the folder where MAF is installed and rename it to recovery.zip for your convenience. In that folder, open the exe that says "MAFAF" or something to that extent(dont' have it memorized lol). Now connect your fastboot cable to your Kindle and it should turn on with a screen on the kindle that says Fastboot and then Kindle. Now on your MAF, you cna check it's working by typing
Code:
fastboot devices
or
Code:
adb devices
. In theory, you should get something like " recovery (device number[random letters and numbers])". From this you can now type in
Code:
fastboot flash recovery recovery.zip
as done to flash our TWRP recovery. When this finishes(shouldn't take to long), you can detach the fastboot form the computer and device. Next, hodl down power to turn it off. Wait like 5 seconds after shut down and then turn the Kindle back on. This should momentarily boot into TWRP and then it will take off into your ROM or whatever OS you have installed. Now you should have not jsut fixed your problem but got TWRP to work too and from there it is easy to do stuff without the need of a PC. Hope this helps and feel free to quote me with a post if something didn't work or messed up. Sorry for bad grammer and spelling. Thanks!

meowmix2 said:
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you
Click to expand...
Click to collapse
Sorted thank you!

Huawei P10 Half root, Bootloader unlocked FRP lock, OEM greyed out, Erecovery loop

My Huawei P10,
My phone the Huawei p10 VTR-L09 the rooting proces has gone wrong.
I now have a half root on my phone. 50%-root
I have stock recovery on my phone but this does not work properly anymore becuase failed every time.
Factory reset does not work because loop.
My Bootloader is unlocked and FRP lock.
In fastboot mode all commands are blocked because i have no remote option.
This is becuase FRP-Lock.
OEM option is greyed out.
Dload method I have tried but that does not work.
And got my bootloader code true Huawei so you would say that I can also Relock my bootloader again, but this does not work either.
I have been looking and trying at it for about 5 months now and try to find new facts or technology so that I can repair my phone and use it again optimally.
My phone works but it is not 100%.
So I have no super user rights on my phone.
I would like to hear from people who know those errors how to repair them.
Or is there only one option left for me and that is the DC- unlocker
sorry for my lack of English, Peter.

Is there no solution for my problem huawei p10?
My Huawei P10,
My phone the Huawei p10 VTR-L09 the rooting proces has gone wrong.
I now have a half root on my phone. 50%-root
I have stock recovery on my phone but this does not work properly anymore becuase failed every time.
Factory reset does not work because loop.
My Bootloader is unlocked and FRP lock.
In fastboot mode all commands are blocked because i have no remote option.
This is becuase FRP-Lock.
OEM option is greyed out.
Dload method I have tried but that does not work.
And got my bootloader code true Huawei so you would say that I can also Relock my bootloader again, but this does not work either.
I have been looking and trying at it for about 5 months now and try to find new facts or technology so that I can repair my phone and use it again optimally.
My phone works but it is not 100%.
So I have no super user rights on my phone.
I would like to hear from people who know those errors how to repair them.
Or is there only one option left for me and that is the DC- unlocker
sorry for my lack of English, Peter.
I need help Xda is there no new solution for my own fold ****top problem that annoy me everyday

I don't understand text properly .
Can you boot your phone or not?

Did you try to boot into eRecovery (not normal recovery) by connecting the phone to USB and boot as you would do it for recovery?
Does this work and are you able to do a factory reset there?
Did you try to download the latest firmware via OTA and install it?
Which version is installed?

P10 problems
Jannomag said:
Did you try to boot into eRecovery (not normal recovery) by connecting the phone to USB and boot as you would do it for recovery?
Does this work and are you able to do a factory reset there?
Did you try to download the latest firmware via OTA and install it?
Which version is installed?
Click to expand...
Click to collapse
VTR-L09C4321b185
in e-recovery I come in without problems but he lingers there every time then I get a red exclamation mark. factory reset that does not work because I have frp lock and this is why I can not install new software.(I think..) OEM lock Greyed-out I run android 7.0 and emui 5.1 thank you

The factory reset should work even the OEM Lock is greyed out.
Did you try to relock your bootloader with both commands:
fastboot oem lock UNLOCKCODE
fastboot oem relock UNLOCKCODE
If this doesn't work, you can use Firmware-Finder to upgrade to Oreo, B185 is old.
Within the app you can check firmware access, if it's accessible, update through DNS or Proxy. There are many tutorials for this.

-don´t even think to relock your bootloader it will brick your phone when you are in this state
-try to use HWOTA to reflash the whole B185 firmware
-i don´t know how you rooted your phone so i cannot help more

Did you try this from part "force upgrade"? It use dload method
https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/

Huawei p10
Hi. I want to thank everyone for responding to my problem with my phone. And Jannomag thanks for your response yes I have tried all these commands in fastboot. I also have an original bootloader code. This way does not work for me in fastboot because it indicates all the time that no remote commands can be given. Furthermore, the half root (rooting gone bad) of my phone. Apk files when installed says that I have no Root and other APK files say that I have full root on my phone. I also can not use supersu and busybox because I have no full root to my phone. I've already done the dload method a couple of times, but I doubt that everything went very well. Nocia, I am going to try your method again and then I will let you know if this has succeeded or not. I have stock recovery and this wont work. I have no custom recovery installed. But it is a nice idea that I have some assistance from you nice people that keeps me motivated so that my phone will work once again ...keep you posted..peter (sorry for my bad Englisch)

make full unroot if you rooted with supersu (with nobody with sense will do in 2018 since we have magisk)

P10 problems
Hi,
I have tried the dload method. But I do not manage because SD card does not accept large files. SD card is in fat32 and formatting to NTSF will not work. exfat format has succeeded but I do not get large files. I have tried downloading it via phone directly to SD card and that has succeeded but then unpacking gives problems because the file is too large for SD card. New SD card purchased 16GB but same problems. A week and a half after work I started working on this and even DISKPART and other related softwares, but none of them gives good news. And Dallas-CZ I have done root with TWRP and custom GAPPS or it is called something like this but the latter is package of assembled apks. But this root has never gone well. I'm curious about your reactions and ideas thanks, Peter

just leave it.
1-you don't even know how you rooted yout phone.
2-you don't know how to put 4.6 GB file to your SD card. ( NTFS will of course work).
Sell the phone for spare parts it will save you a lot of pain.

P10 problems
i have tryed to root root with twrp and flash SuperSU-.zip file on the phone. Here went wrong because I do not have full root. Still not. I have tried so much I have tried everything i know. If you can tell me what the problem is why I can not get a 5GB file on my SD Card. If I know what I'm doing wrong then I continue with the dload method. If you say that it should be easy to put 4GB on fat32 SD card please tell me? Is it the SD card that is too small, should I just get a new one and 1 of 64 GB with ntfs? I would rather have my 16GB card work, but I can not format fat32 to NTSF on my SD-card. I am here also because I do not know what to do and need information about the correct way. Please help;;;;

You didn´t write what supersu have you flashed.
1 -have you tried to uninstall supersu in the supersu app?
2-have you tried to uninstal supersu in twrp with this method?
3-just format your 16gb sd card to ntfs. Put the right files on the sd card and follow the tutorial.

i dont think that the dload method still works.

Try the HurUpdater method...
Hi, try this method here:
HurUpdater: https://forum.xda-developers.com/hon...overy-t3769279
I had more or less the same problems and different boot, OS, a.s.o. problems.
Soemtimes I was in a loop, didnt had a working OS, other times I could get any ADB-connect.
The above way solved my problems and I could install different ROMs after I followed the method.
Hope this helps
SB

P10 problems
DallasCZ said:
You didn´t write what supersu have you flashed.
1 -have you tried to uninstall supersu in the supersu app?
2-have you tried to uninstal supersu in twrp with this method?
3-just format your 16gb sd card to ntfs. Put the right files on the sd card and follow the tutorial.
Click to expand...
Click to collapse
DallasCZ,
thank you for your reaction. I've made a mess of it and I have to confess that I do not know which Supersu version I used to flash my phone. Unroot by apk supersu I have tried but this indicates that SU binary needs to be updated so I can not. What do you mean by putting the right files on my SD card? I can not get the SD card to NTFS. I have tried all kinds of methods to format my sd card from 16 GB to NTFS but I can not. Have even bought a new card of 16 GB but this one so that it fails to format to NTFS. I can not get custom recovery installed and I now run stock recovery. twrp installed by root access does not work because I do not have root full access. And twrp at fastboot does not work because I have FRP lock and bootloader is unlocked. thank you in advance

Superblond said:
Hi, try this method here:
HurUpdater: https://forum.xda-developers.com/hon...overy-t3769279
I had more or less the same problems and different boot, OS, a.s.o. problems.
Soemtimes I was in a loop, didnt had a working OS, other times I could get any ADB-connect.
The above way solved my problems and I could install different ROMs after I followed the method.
Hope this helps
SB
Click to expand...
Click to collapse
superblond your link doesnt work for me will you please post it aigain ..thank you

P10 problems
TbiTw said:
i dont think that the dload method still works.
Click to expand...
Click to collapse
Hi .. as long as I do not get my SD card formatted to NTFS, I will not succeed .. What is the problem why that card does not want NTFS?

Link to HURUpdater Post
tamino161 said:
superblond your link doesnt work for me will you please post it aigain ..thank you
Click to expand...
Click to collapse
Sorry M8,
here is a proper link and the title is ' [Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery '. (I think you need to be loged in...)
I still have the files on my hd for my Huawei P10 VTR-09, that gave me a unbricked & fully functional phone with EMUI 8.0, OS 8.0 ver. 8.0.0.382(C432) again... if you need them I could upload them for you.