Database Info

[GUIDE] T-MOBILE PRISM II aka HUAWEI U8686 ROOT AND BOOTLOADER UNLOCKING

ROOT GUIDE FOR T-MOBILE PRISM II AKA HUAWEI U8686 (ASSUMING YOU HAVE ADB INSTALLED).​1)BOOTLOADER UNLOCK CODE PROCEDURE
First this you need to unlock your bootloader, and Huawei requires unlock code to do so. (HINT BACKUP YOUR DATA, THIS WILL WIPE YOUR PHONE).
a.You will need to obtain this by sending an email to Huawei. It usually takes less than two hours and they generate the code and give it you.
b.I know you will say why not get it via their automated website. Model U8686 doesn’t exist, so stop being lazy and send an email to [email protected]
Use the below format.
Dear Sir/Madam
Please may I request the bootloader unlock code for my Huawei Prism II? Here are some Details:
Serial Number:
IMEI:
MAC:
Model: U8686
Please could you send me the code directly, as I cannot access the product ID on my device.
Thank You
Click to expand...
Click to collapse
c.Once you got unlock code, move to Step 2.
2)BOOTLOADER STATUS CHECK
a.First thing is to enable USB debug mode in developer settings.
b.Now connect the phone using USB to your computer.
c.Install drivers, this should be located in CD Rom that comes up when you connect your phone.
d.Open command prompt and type the following command
adb devices
Click to expand...
Click to collapse
e.You will get result like
023A02323223 devices
Click to expand...
Click to collapse
f.Turn off the phone and hold volume down and power button, keep holding and wait 30 secs. It will be standing still at T-Mobile Logo.
g.Now run a command
fastboot devices
Click to expand...
Click to collapse
h.You should see something like this
023A0232323 fastboot
Click to expand...
Click to collapse
i.If it says offline, you will need to install drivers, and make sure your adb updated.
j.Next type in following command
fastboot oem get-bootinfo
Click to expand...
Click to collapse
k.It will output something like this
C:\adb>fastboot oem get-bootinfo
...
(bootloader)
*******************************************
(bootloader) Bootloader Lock State: LOCKED
(bootloader) System State: OK
(bootloader) Bootloader Version: 001.001.000
(bootloader)
*******************************************
OKAY [ 0.006s]
finished. total time: 0.008s
C:\adb>
Click to expand...
Click to collapse
l.If you are locked go to Step 3
3)UNLOCKING BOOTLOADER (THIS WILL WIPE YOUR PHONE TO FACTORY)
a.I assume you are still in fastboot, so you will type the following command.
fastboot oem unlock 12354343534
Click to expand...
Click to collapse
– replace 12345343434 with your unlock code.
b.It will do it’s magic.
c.To confirm your bootloader is unlocked, go in Bootloader, type
fastboot oem get-bootinfo
Click to expand...
Click to collapse
d.You will see something like this.
C:\adb>fastboot oem get-bootinfo
...
(bootloader)
*******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: OK
(bootloader) Bootloader Version: 001.001.000
(bootloader)
*******************************************
OKAY [ 0.006s]
finished. total time: 0.008s
C:/adb>
Click to expand...
Click to collapse
e.Congrats, now you are unlocked. Move to Step 4
4)ROOTING YOUR PHONE
a.Make sure your phone is on and connect to PC with Wire, and Debug mode is on.
b.Download & Open Kingo Android Root (Google the name)
c.Follow Kingo’s Instructions, and you will be rooted in less than 2 minutes.
d.Enjoy the Root!
For those who find difficult to follow instruction check out this video by TomSGT. Video can be located in this thread or Click here Prism II Unlocking Bootloader

RESERVED!

Command Promt
I get everything upto the command promt. When I Type it it goes "abd" is not recognized as an internal or external command, operable program or batch file.

Type adb instead of abd.. It will work. If you still get not recognized then you need to install android dev kit.
Sent from my Nexus 4

Command Promt
Thats what I typed, the post had a typo. So when i type Adb it comes up the same thing.
How about some pictures?

That means you do not have android development kit installed. Search forums how to install adb and fastboot
Sent from my Nexus 4

Completed
Okay, I downloaded everything and tried for hours. Didn't work. Couldn't "Unlock Boot Loader".
So being the person I am I try random things a hope for the best. I gave up with Command prompt and just went to the Android Rooting Program.
Rooted Successfully, went threw and checked.
What was the point of boot loader and will I suffer any effects from not unlocking it?

Unlocking bootloader allow you to flash custom roms and kernels
Sent from my Nexus 4

Oh well...
nycelitemaster said:
Unlocking bootloader allow you to flash custom roms and kernels
Sent from my Nexus 4
Click to expand...
Click to collapse
Well to my knowledge their are no custom roms or kernels compatible with The Prism 2, believe me, I've looked. So if you know any it would be helpful.

Well the reason being is the to limitation to unlocking of bootloader. Now that we are able to unlock, i am positive we can do something. I have kernel sources, i might sync git next week
Sent from my Nexus 4

Awesome
nycelitemaster said:
Well the reason being is the to limitation to unlocking of bootloader. Now that we are able to unlock, i am positive we can do something. I have kernel sources, i might sync git next week
Sent from my Nexus 4
Click to expand...
Click to collapse
Awesome, because I have the Nook Color Root with Cyrogen Mod and its an awesome experience using a custom rom, and with the lower end specs of the Prism 2 a custom rom might be able to speed the thing up.

True
Sent from my Nexus 4

flash to stock
Thanks for the info on unlocking the boot loader, thanks button was hit.I'm in a bit of a pickle here, I deleted quite a few system apps and ran a few scripts one of them I think messed up my wifi so I decided to do a factory reset and i should have known better. Does anybody have info on flashing this phone back to stock? I've searched and wasn't able to come up with any info. Is there any way to push the missing apps through with adb, one of them being the "2D Home" app? Any help would greatly be appreciated, thank you.

You can with adb
Sent from my Nexus 4

If you have the time, could you maybe enlighten me on how to push the apps through with adb? Would they install automatically, I have no access to any File Managers. Thank you.

You need root to push app to system.. If you have root you can also do using android os. Push es file exp from google website. When phone turns on press menu it will take you to settinga. Go in lockscreen setting and assign es explorer as one of them. Use it from there
Sent from my Nexus 4

nycelitemaster said:
You need root to push app to system.. If you have root you can also do using android os. Push es file exp from google website. When phone turns on press menu it will take you to settinga. Go in lockscreen setting and assign es explorer as one of them. Use it from there
Sent from my Nexus 4
Click to expand...
Click to collapse
Thank you for your reply. I'm at a lost here as to how to push the apps through with adb. I have Minimal adb and fast boot installed. Do I need to download and install Android SDK? Could you maybe share the commands I need to use please? Sorry for all the questions, I'm a super noob and I really want to fix this. Thank you.

Ok so to answer how to push a file using adb is as follow
Adb push filename.apk /system/app/
Adb shell
Chmod 0644 /system/app/filename.apk
Exit
Adb reboot
Sent from my Nexus 4

wifi
Thank you for your time and reply I really appreciate it. I have my phone working now, except for broken WiFi. Do you Know if I can flash the kernel through stock recovery having the Boot loader unlocked? I think i messed it up running the v6 supercharger script. I am researching and looking for a fix myself, i was just wondering about the kernel flash. I'm not familiar with this phone and you have a lot more knowledge about it than I. Thank you for your time and replies, I was sweating bullets there for a moment.

Download the stock rom package and extract the boot.img from it. Once you do that turn off the phone and put in bootloader (hold power + vol down) for 30 sec. It will be on white screen with tmo sign. Type fastboot devices.. You should get 24gdh23 fastboot.. Once you are sure that you are in bootloader type fastboot flash boot boot.img. make sure boot.img contains full path. So if it is in c drive it will be "C:/boot.img"
Sent from my Nexus 4

Nexus 5 won't prompt for decrypt on boot / TWRP fails to decrypt

So I think I am screwed here but was wondering if anyone has run into similar issue. I was running SlimKat and had the data encrypted and I used BootUnlocker to relock the bootloader after I flashed TWRP a few months back. Been working fine for a couple weeks then yesterday I pull my phone out my pocket and it looks like it factory reset prompting to input all my info. So I reboot the phone thinking could be fluke and it doesnt prompt me for decyption password and again boots to setup screen. If you do login you cannot access the internal storage and there is no data connection. So I rebooted into TWRP and it prompts for decryption password only its not working. If I put in wrong password it comes back immediately that it failed. If I try correct password it tries for 30 - 45 seconds then comes back with failed. So tried downloading factory image and flash with fasboot but was complaining about bootloader locked. So I issued fastboot oem unlock and choose yes the screen switches to unlocked but doesnt wipe anything try to flash again and I get FAILED flash write failure. When I reboot to the bootloader it shows as locked again. I think my flash took a crap. Anyone have any ideas?

I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....

since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.

kj2112 said:
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.

simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.

what do you mean doesnt unlock it?

prestonr83 said:
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
Click to expand...
Click to collapse
very odd!
youre device is seen by fastboot(not adb)?

prestonr83 said:
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
Click to expand...
Click to collapse
That's a good point.
I'm afraid that if you cant flash the stock image, and you can't unlock the bootloader to try other methods....you may be at an impass.
You need to either get the stock image back on. Or unlock the bootloader, Then try my link. Not sure what else can be done here.
Sent from my cell phone telephone....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Oh....and again.....you may have driver issues on the pc, and that's why fastboot isn't seeing the phone. That is the first thing that needs to be corrected.
Sent from my cell phone telephone....

Zepius said:
what do you mean doesnt unlock it?
Click to expand...
Click to collapse
I mean i put it in fastboot issue fastboot oem unlock it prompts me on the phone to choose yes or no. I choose yes it then immediately goes back to fastboot screen and shows unlocked. However when trying to flash anything it fails and upon rebooting back into fastboot it again shows as locked.

Your emmc is dead. RMA it
Sent from my Nexus 5 using Tapatalk

simms22 said:
very odd!
youre device is seen by fastboot(not adb)?
Click to expand...
Click to collapse
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.

prestonr83 said:
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
Click to expand...
Click to collapse
have you tried flashing clockworkmod recovery and factory resetting it there?

simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Advice I would really have to disagree with as it is a built in security measure; telling people to avoid using proven security methods is sketchy in itself. I had my Nexus 4 encrypted for the last 4 months and had never had any issues. What issues are you talking about?

Encryption slows the device down... We all know that. Also, if by chance someone forgets their pw (yes... Seen it happen plenty) you lose al your stuff to get back in.
Anyway, to each their own... But I'm not important enough to worry about what's on my phone getting into the wrong hands. ?

Is there hope?

So the usual things has happened.. I have looked many different places, forums, and posts and the closest thing I have found was this thread.
http://forum.xda-developers.com/showthread.php?t=2423716
However it didnt help me at all so now I am posting this to see if there is an angel out there that can help me.
He is the problem.
1. It will show this if I plug it in to my PC but I cant turn on the device by its self.
"AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure"
2. It doesnt charge.. I dont think
3. When I hold the Vol- and PWR for 10 ten then add the Vol+ it sometimes will go to the bootloader and then it will boot.
Can I fix this to not show this message every time?
Thanks for your time
-Avethepizzaman

You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
K I have it charged..

Avethepizzaman said:
K I have it charged..
Click to expand...
Click to collapse
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.

bweN diorD said:
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
Click to expand...
Click to collapse
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping

Avethepizzaman said:
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Click to expand...
Click to collapse
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.

bweN diorD said:
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
Click to expand...
Click to collapse
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!

Avethepizzaman said:
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Click to expand...
Click to collapse
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.

bweN diorD said:
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
Click to expand...
Click to collapse
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman

Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
That's a lower version. Unless you unlocked your bootloader, which it appears you haven't, you cannot downgrade from 182.46.15. If you didn't unlock your bootloader (which I'm assuming because in your first post, you showed that the status said "locked" in fastboot mode), then you have no way to root, unlock the bootloader nor downgrade. You can only reflash the latest which is 182.46.15.

Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
ok, i was tired and forgot about the "tz".
to avoid any further confusion, download the firmware from here and replace the xml file with this one. i already edited it. then flash again.
now that we have all the facts straight, and files in line, it should go fine this time.

Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!

Avethepizzaman said:
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Click to expand...
Click to collapse
wow, your phone is being a pita lol
follow the instructions here to fix that.

Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!

Avethepizzaman said:
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Click to expand...
Click to collapse
np! happy to help

Pixel bricked with locked bootloader

Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).

You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.

post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'

This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905

junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.

Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs

junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?

aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.

Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?

post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.

Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks

HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.

Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks

Question Is unbricking possible?

Good morning all, I tried relocking my bootloader using the command "fastboot oem asus-csc lk" and at first, it seemed to be a success. However I restarted my device and was met with this error message. "Your device is corrupt. It can't be trusted and will not boot." I've tried searching high and low and it seems that I'm royally screwed, just wanted to confirm that I was though. Thanks for reading my post and any input is appreciated.

If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware

This is becoming a pretty common issue. I think it's time we make a WARNING thread.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com

jhosharath said:
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
Click to expand...
Click to collapse
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all

Jdotswift said:
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Click to expand...
Click to collapse
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com

twistedumbrella said:
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment

Jdotswift said:
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Click to expand...
Click to collapse
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.

twistedumbrella said:
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
Click to expand...
Click to collapse
Well thanks for your help. I admit defeat but learned a very valuable lesson

Jdotswift said:
Well thanks for your help. I admit defeat but learned a very valuable lesson
Click to expand...
Click to collapse
You may still want to contact Asus and tell them you don't know what happened. They may be able to restore it. I wouldn't tell them you unlocked the bootloader, since it's locked if they ask.

As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here

JazonX said:
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
Click to expand...
Click to collapse
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.

twistedumbrella said:
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
Click to expand...
Click to collapse
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas

Jdotswift said:
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Click to expand...
Click to collapse
Glad to hear it. Apparently, the issue was people not following instructions...