Develop Bugs

Soft/Hard brick when chainfire rooting

Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!

My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478

Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.

Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised

thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything

I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device

I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140

Thanks, Mike01680. trying now

When i go into sideload i can see the device listed on adb devices!

Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!

[8.0.0] Bootloop with locked bootloader. What can i do ?

Hi !
Before tonight, i was on a lineageOS 7.1 and i tried to flash the stock Oreo android that i downloaded on google websites. My bootloader was unlocked, so i just used fastboot and flashed all. I had TWRP installed.
It worked. Then i had the stock 8.0.0 with no TWRP anymore ( and i forgot to re-flash it ). Then, i dunno what passed in my head, after the first reboot, i decided to **lock my bootloader**.
And now i'm in a bootloop on the vendor image ("Google"), with a LOCKED bootloader ( so no fastboot anymore ) and i cant do anything. I forgot to go to paramters and allow the bootloader to be unlocked before rebooting...
The only access i got is via adb in the stock recovery mode, but i'm not enough aware of wath i could do with that. I tried abd sideload with the same .zip, but it didnt worked. I get stuck on the same Error when the phone tries to verify the conformity of the flash.
So :
1° Cant use fastboot to take me out of here because bootloader's locked.
2° No TWRP anymore, only the stock android recovery.
3° Bootloop so i cant launch the device.
4° My only in is adb fastboot.
5° My build number is OPR6.170623.013
What do you think i could / should do to take me out of here ? I'm taking anything that allows me to boot the phone.... For what i saw, i'm kinda thinking it's bricked, but i still got hope. I'm comming to you because i'm desperate
Thanks for your advices.

useful threads
that nobody ever bother checking out

Very usefull post. Thank you very much. I'm still stuck but i've posted there so i'll hope someone will come.
This post can be closed

Help to revive Honor 8 Pro

Hello, I really need your help. I was happy with my DUK-L09C432Bxxx, I rooted it, TWRP recovery, unlocked the Bootloader, unlocked the FRP ..... up to try an update with B182. It was not possible to install it with TWRP, the sytem failed and didn't want to restart. I reinstalled the original recovery and use the DLOAD process for updating with same result. With surfing I discovered I'm not alone in this situation and today, this is :
- cannot reinstall TWRP because the phone doesn't appears with ADB devices command, or unauthorized.
- cannot enter to the recovery for normal update with DLOAD.
- try to do it with DC-Phoenix with Honor 9 ROM (loose 1 IMEI number), with Honor V9 and there is error messages
- do the same wthi Huawei MultiTool, also some errors
I don't want to spend some money to buy another phone, so if someone can help me. I would be eternally gratefull.
Kind regards

misterwood said:
Hello, I really need your help. I was happy with my DUK-L09C432Bxxx, I rooted it, TWRP recovery, unlocked the Bootloader, unlocked the FRP ..... up to try an update with B182. It was not possible to install it with TWRP, the sytem failed and didn't want to restart. I reinstalled the original recovery and use the DLOAD process for updating with same result. With surfing I discovered I'm not alone in this situation and today, this is :
- cannot reinstall TWRP because the phone doesn't appears with ADB devices command, or unauthorized.
- cannot enter to the recovery for normal update with DLOAD.
- try to do it with DC-Phoenix with Honor 9 ROM (loose 1 IMEI number), with Honor V9 and there is error messages
- do the same wthi Huawei MultiTool, also some errors
I don't want to spend some money to buy another phone, so if someone can help me. I would be eternally gratefull.
Kind regards
Click to expand...
Click to collapse
Hi there
Probably a silly question, but did you try all the things some of us did on the rebranding thread? The only thing I can think of on top of my head was that we used older roms(B130 I think it was) and this worked like a charm
So...when you restart the phone, it loads on to the erecovery screen or something else?

Hi,
after reboot the phone restart in erecovery mode and of course it failed because there is nothing on the Huawei server. I made some test and that is new and really problematic, with ADB, the device is unauthorized, so I can't do anything. Windows or Linux, same behavior.

Rooting Xa1 Plus (G3412) - Recovery problem

Hello community!!
This is my first post here ^^
So I'm trying to root my g3412. After struggling to find drivers for S1 Fastboot, I successfully unlocked my bootloader (via Flashtool) . The only thing left is to flash the TWRP recovery and root it.
But I'm experiencing some weird problems.
When I'm trying to flash the recovery using ADB everything seems ok but when i try to turn on my phone it bootloops between the "your phone cannot be trusted" message and the Sony logo. After i freaked out for a couple of hours i found out that the only way to overcome this loop is to flash a fresh stock rom via FlashTool.
I'm back at step 1 and i can't really find a way to flash the recovery so i can continue my rooting process..
Also I think i found out while searching that g3412 doesn't have a stock recovery, so i guess that has to be considered as well.
Any ideas??
Thank you all in advance!!

You better change your handset...
Well i'm sorry to say but you can't root xperia xa1 plus,. the reason is there is no working TWRP for this mobile... I've tried almost every boot img on internet, none of them worked.... you better change your handset.. as there will be no TWRP img in future...

"Your device is corrupted and cannot be trusted" error. Nothing happens when connecting to PC

Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.

This is for Google Pixel 2 XL.

SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.

Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.

Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.