Related
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!!!
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Czechball said:
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Click to expand...
Click to collapse
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
dirlan2001 said:
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
Click to expand...
Click to collapse
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Czechball said:
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Click to expand...
Click to collapse
If you can get into download, you could connect to a PC and start the LG-tools.Use that to restore to the original ROM and start allover again with latedt software (TWRP, ROM, SU)
Cheers
So I've had a read through other threads on different sites and youtube videos etc.
Basically I was trying to root my phone using magisk following the video where TK roots a oneplus 5, but was switching out the software for the oneplus 3 version of twrp.
All was going well, connected phone to pc, unlocked it, copied the files across, flashed and installed twrp then when it rebooted after installing twrp it came up with an error saying that "dm-verirty" is not started in enforcing mode, and the phone wouldn't boot past that.
I relocked the OEM, as I couldn't get it to recovery mode (stock) so tried that and now I can get it into recovery mode.
It will happily go into fastboot mode, have tried reflashing stock recovery and trying to update the os via adb.
Have been looking at the Mega Unbrick Guide - but can't get my phone to show up on my pc to even begin there.
Would appreciate any and all help, plus tips for what to do after I get it back to stock as I'm still keen to root my phone but don't want to screw it up again and have to go through all of this again.
The Mega Unbrick guide is your best hope. Did you install all the drivers on your PC? Specially the Qualcomm ones? Also, make sure to press the volume up button like it says in the instructions for 40 seconds. Otherwise it doesn't show up. If all fails, try using a different PC.