Database Develop

[Q] Bricked razr i help - locked bootloader

Well, this is embarrassing...
Current Status:
After a factory wipe and reinstalling (phone was OK after that) and an OTA, i managed to nearly brick my razr.
Currently every time i start it lands in fastboot (according to RSD Lite mode S) with the message fastboot reason: flash failed
after 'fastboot reboot-bootloader' i can operate the menus but only changing the console type and power off work, everything else results in a freeze.
Reflashing CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip or 31 is not possible, since the OTA update apparently changed boot[1], gpt[2], and few other things to version "8.7.1I-110_IFW-DE-39" (the only thing i can flash from those are the recovery partitions and from the new one the gpt.bin)
Custom fastboot also does not work, since i'm not eligible according to Motorola ( tis was my first thought to check the custom boots & finally unlock the bl *g*)
I already ordered the factory adapter (hey, you never know, when you're gonna need one) & My Battery still has ~3.9v left, so i think a few tries should not hurt that much : >
TL;DR, Here's my question:
1) is it possible to patch the images provided in CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip with the binary patches from Blur_Version.81.5.32002.XT890.O2.en.DE (updates to: 8.7.1I-110_IFW-DE-39_O2DE) and then maybe re-flash them to get my razr back from the near death zone?
2) should i hope and pray that Motorola announces JB upgrade and provides us with the full system images within the next few days?
3) can anyone find a full system image / full update with the version: 8.7.1I-110_IFW-DE-39_O2DE ?
References:
[1]: from update-script:
assert(apply_patch("MTD:boot:11534336:affeb8868070f6e6f061143b662e03b5bf65b2f3:11534336:19bf404a393a50d08a809affd45df5692e36e1db",
"-", 19bf404a393a50d08a809affd45df5692e36e1db, 11534336,
affeb8868070f6e6f061143b662e03b5bf65b2f3, package_extract_file("patch/boot.img.p")));
[2]: There is a brand new gpt.bin file within the OTA package
Cheerio,
Andy

The Problem is, without unlocking your Bootloader, you can't downgrade the Boot. img.
I would suggest you to grap the 39002 O2 Homemade Fastboot from Mattlgroff and flash only the Boot. img out of it. If you're an lucky guy, you're able to boot after that.
An Guy from my Home Forum tried the downgrade from 40002 today with an locked boot loader. RSD stopped @ point 1 GPT. His solution to boot his phone again was to flash the gpt.bin out of the 40002 OTA .zip.
So your only chance to get your phone back is to find flashable Images from the 39002 or 40002 because of the secure Level.
The easiest way is to unlock the device, I can downgrade to any FW. Or you'll have to wait for an updated Fastboot File to flash with RSD.

Hokay, apparently i had a typo yesterday when i tried to unlock the bootloader
But, now after trying the custom fastboot, i still land in fastboot with reason: Sticky bit fastboot
and all other menus still cause a freeze : /

If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.

HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
Purrrrfect, i owe you a bottle of wine.
Problem solved : >

Yeah, I'm glad I could help you out... RazR I Nr. 8 > Strike

bricked
hi guys the same thing happen to me i cant use rsd or fastboot because it says stigki bit fastboot.and in rsd it fails tryin to flash boot. im in mexyco i was using the new ota for 30006 that would be 40002. i just try to erASE THE BOOT LINE AND IT DIDNT WORKIT SAID THE SAME. HELP

So you're on 40002 and tried to flash back with RSD and your Bootloader is locked?
RSD failed on step one, right?

brick
Yes sir. Iwas on 40002 and with the rsd i was trying to go back to stock 30006,but on step 3 it says fail. Then i try to fastboot 40002 but it tqkes me again to fastboot and its freezes when i try to open a command like normal boot or recovery. I tried to eras the lineinside of motoboot where it says motoboot like the guy you just helped. But in my case still gets stuck on step 3in the rsd. So could you send me images of how erase the line of motoboot on text editor?? Im boot unlocked.

You mean 31006...Here ya go (unpack it > i can't attach an .xml)

Thank u sir. So i flash this on rsd,right? Vause i think that this is the one i have.the last digits are 31 on mine an starts cfc . Something else. I cant really tell u cause im at work but tonight i'll try ur method. Hope it works.

http://www.mediafire.com/download.php?ud9kowzk1uw2bcb
Use RSD 6.1.4 and copy the xml into the fastbootfolder. That's all...BTW: Charge your battery if possible or hope you got enough juice!

unbricked
thank you sir. everything like new!!!!!!!!
i"ll buy u some beers.

my razr i is workin now but i cant update the ota for the 31006 thats going to take me to 40002??

You're trying to update regular over the Phone or the manual over the leaked Update.zip? If you're trying it over the leaked zip, than beware. There's one if you're coming from 31006 and one from 32002.
Sent from my XT890

I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.
---------- Post added at 03:04 PM ---------- Previous post was at 02:07 PM ----------
I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.

Thank you - you're the best
HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
My RAZR i works again thanks to HSD-Pilot. You saved my life.
THANK YOU
Roman

how found fastbootfolder me friend, sorry im newbie and me phone is death, please help

Razr i black screen after update phone not getting on
After i have unlock bootloader and root the phone....i have to do a fresh update to last Jelly Bean....phone have got turno of for starting insatll the update....and have rest like that...............When i press Power or Power and Vol Down is just doinf a short vibrate and the Notification led stay On for 10 sec after led OFF and a short vibrate.....>>Connecting to PC no getting any device on RSD or Fastboot and in Windows detect as a MEDFIELD device for wich no driver i found anywhere.........Phone was having 100% POWER before doing all this....adn i have try on several Pc with diferent Windows and diferent 32 or 64 bit with all RSD, drivers Sdk, etc installled and same results.....if anyone have a ideea how to repair will be a really expert on this modding devices....thank you and ...HELP

[Q] Emergency! NEED HELP IMEDIATELY!!

Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????

Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.

BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
Thanks a bunch! I'll check this out and see if it works

Rom Update Utility
It will get you back to 100% stock
If you need help PM me I'll be happy to help

roflcopter1212 said:
Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????
Click to expand...
Click to collapse
Try this tutorial from BD619 http://forum.xda-developers.com/showthread.php?t=2503646&highlight=tutorial

roflcopter1212 said:
Thanks a bunch! I'll check this out and see if it works
Click to expand...
Click to collapse
I tried it with your tut. but when I try to reboot into RUU it says fastboot isnt a valid win. 32bit application. What now?

BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
I put in the failed 90 hboot.... command and it says its an invalid command

roflcopter1212 said:
I put in the failed 90 hboot.... command and it says its an invalid command
Click to expand...
Click to collapse
You *have* to get your Android SDK setup properly. All the commands your run end up on "command not found" of "invalid exe" and that suggests a few things:
First -- make *sure* you install the correct SDK for your computer. If you can't find them, let us know what your computer is (32-bit, 64-bit, windows, etc.). Further, it seem possible:
1) You did not yet install the Android SDK (or ADT bundle if that's what you grab);
2) If just the SDK, you did not run the 'android' app and let it update all the platform-tools apps (that's adb, fastboot, etc);
3) You did not open a command shell in the <sdk>/platform-tools directory, or you did not add your <sdk>/tools and <sdk>/platform-tools to your path. Further:
Finally -- make sure you have your USB drivers loaded if you're using Windows.
Don't run 300 miles per hour trying to fix things -- it'll kill your phone. Relax, take a breath and get the SDK setup. That will solve most of your problems (if not all). At least that's what it looks like from afar.
Before you run any of the RUU, you should be able to type either of:
adb devices
or
fastboot devices
The latter works only when you are at the bootloader with your USB plugged in and you selected 'fastboot'; the former runs only when your phone is booted fully.

The Sprint 3.05.651.5 RUU is available here: http://www.htc.com/us/support/htc-one-sprint/news/ (Install at your own risk!)

I simply cannot flash recovery

I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help

carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that

thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names

update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?

carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.

Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go

I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!

I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?

It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).

First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.

I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.

Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0

xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.

YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.

Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.

Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice

Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen

xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.

Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You

Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.

Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.

Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks

Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.

Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.

Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.

Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.

So I tried to unlock via EDL...

...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)

So neither of the two USB ports in the phone seem to work for you in bootloader mode?

dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?

I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.

dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.

WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?

dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.

What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.

HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!

WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.

HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.