I just got my OnePlus 3 last week and I am having some issues trying to root it. Initially, I was using Win7 and could not get anything to work (phone was never recognized - yes drivers were installed). I went to my laptop with Ubuntu 16.04 and had some success. I was able to unlock the phone; however, when I tried to flash twrp.img (and recovery.img), I kept getting a fastboot permissions denied error. I was using sudo and fastboot devices worked. Also, if I try "sudo fastboot boot twrp.img" nothing happens on the phone (or pc for that matter). I am totally perplexed. The OS on the phone is Oxygen 3.2.4. Thanx for any assistance.
Bill
Install all driver (1+ Mobile Usb driver and Adb)
Than Follow Toolkit Method On Xda.. Its work Fine For me... ? and Follow their Video
I had a similar problem with mine. I could flash TWRP but it wouldn't stick. Reboot the phone and try again, the factory recovery would be back. I tried every version of TWRP, adb, fastboot and the toolkit -- same result.
Finally fixed it by using the toolkit to flash the previous version of TWRP, then using TWRP to flash the latest version without rebooting the phone. With that done, no problems after rebooting system.
Now I can flash new ROMs.
How old does twrp have to be before you get positive results?
Related
Ive been reviewing some of the threads on this forum for 2.3.3.0 and this doesn't look good. In my case I went ahead and downloaded Android 5.1.1 and transferred the zip file to the nexus (ADB Driver) as well as usb otg. I attempted to install the zip file but keep getting the message: "error flashing zip" (log is attached). After the first failed attempt I went ahead and removed then re-downloaded 5.1.1 again but still failed, Ive tried Android 4.1.2 but had the same result. Ive went to TWRPs site and attempted to perform a recovery using TWRP 2.8.7.0 but the recovery in TWRP 2.3.3.0 wont recognize any images. One last resort was to load from ADB SIDELOAD within TWRP 2.3.3.0 but still fails. Are there any other troubleshooting steps that could be performed?
Hi!
Try to flash any stock rom via NRT.
Heres what im getting when trying to communicate with the device: "ADB Device not found". Attached are the images of communication with the device while in TWRP 2.3.3.0 recovery mode, Is there a way to get NRT to recognize the device during the bootloader?
EDIT: I Found the FAQ, I will need to do some more research.
pepper55 said:
Is there a way to get NRT to recognize the device during the bootloader?
Click to expand...
Click to collapse
Hi!
Of course it is, just boot your tablet to fastboot mode, and choose in NRT Current status: Soft-Bricket/Bootloop.
If you really have a Nexus 7 (2012), you're using the wrong factory image (and you're in the wrong forum).
pavel2084 said:
Hi!
Of course it is, just boot your tablet to fastboot mode, and choose in NRT Current status: Soft-Bricket/Bootloop.
Click to expand...
Click to collapse
Kept trying with fastboot mode but ADB still wont recognize the device. When i boot in TWRP it does recognize the device just fine. Any other suggestions?
pepper55 said:
Kept trying with fastboot mode but ADB still wont recognize the device. When i boot in TWRP it does recognize the device just fine. Any other suggestions?
Click to expand...
Click to collapse
Hi, pepper55.
In recovery you can use ADB sideload
Simple ADB (not sideload) doesn't work without OS.
Use fastboot for the soft-bricked device.
Try to restore your tablet using stock google image, and "Flashing Instructions".
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
Hello, I have a huuuuge problem.
Every time I try to flash TWRP through cmd, nothing happenes. I have all needed files, my phone is being recognized in adb devices, reboots on command, is on fastboot devices list, reboots on fastboot reboot command, but it totally do nothing when I use fastboot flash recovery twrp.img command. Maybe it's my drivers fault, because last time i uninstalled my device through Device Manager, somehow it worked and I flashed TWRP. But then I switched to MIUI and as expected TWRP was removed. And I cannot flash it, please help
Did you update to latest MIUI?
Yes, right now I'm on Global Stable.
Turn your pc into a new one then you will.
Why turn your PC into a new one? resetting?
Isn´t there another solution?
Removes old data such as adb,platformtool, twrp.then can do it.I've come across and solved this way Do not know why
xx
Posted another tread:
I struggled a lot installing TWRP. I did not succeed flashing TWRP from my PC. My solution was:
Starting up TWRP: fastboot boot twrp.img / boot command only boot and does not flash.
Thereafter installed Magisk 17.1 from TWRP for rooting
Thereafter flashed TWRP / I tested flashing both by using Flashify and TWTP Manager and both worked.
Maybe by using Flashify I had to use an older version of TWRP. Think TWRP Manager let me install 3.2.3-0 direct without problems.
Hello all,
I have rooted my phone with TWRP and Magisk (10.3.5 global rom on China hardware). I used fastboot boot only - did not flash TWRP permanently.
All seemed fine.
Today I wanted to make a TWRP backup - and to my greatest surprise TWRP.img (which worked before) does not work any more.
Fastboot devices shows the phone but when I try fastboot boot TWRP - I get an error message and the phone reboots.
I have checked usb debugging and it is enabled.
How can I boot in TWRP and why doesnt it work when it worked before?
Thank you for any suggestions!
Update: trying a different computer worked. So this seems to be a PC issue: a laptop which first worked now does not work. My desktop works...
You can try
Code:
fastboot boot name_file_recovery.img
Fonte on OP post below:
https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
Good luck.
Hello. I decided today to clean install the Pixel Experience 10 rom. I previously had a Pixel Experience 9.0 Pie. I did the following:
1. Booted into TWRP and selected Format Data
2. Everything is deleted, so it's time to flash a new rom. The guide says to go Advanced/ADB sideload and enter a command.
3. Command is not working. My phone is connected to the computer but it's not recognized. I can't even manually transfer it to the phone so i can install it via TWRP.
So i enter fastboot. Phone is recognized. When i type fastboot devices i get this:
Code:
C:\adb>fastboot devices
42abad9b fastboot
If i try to flash again a TWRP, my phone disconnects and it asks to reboot the phone by pressing a volume button. And i am stuck here. Nothing i can do. Any suggestions? I haven't done anything unusual. I am truly desperate. Any help will be appreciated.
naruto14 said:
Hello. I decided today to clean install the Pixel Experience 10 rom. I previously had a Pixel Experience 9.0 Pie. I did the following:
1. Booted into TWRP and selected Format Data
2. Everything is deleted, so it's time to flash a new rom. The guide says to go Advanced/ADB sideload and enter a command.
3. Command is not working. My phone is connected to the computer but it's not recognized. I can't even manually transfer it to the phone so i can install it via TWRP.
So i enter fastboot. Phone is recognized. When i type fastboot devices i get this:
If i try to flash again a TWRP, my phone disconnects and it asks to reboot the phone by pressing a volume button. And i am stuck here. Nothing i can do. Any suggestions? I haven't done anything unusual. I am truly desperate. Any help will be appreciated.
Click to expand...
Click to collapse
Hi !
Did you bypass ARB with dummy.img before you flashed TWRP?
Do you use win 10, if you are change usb or use usb hub. If that doesn't help use win 7.
follow the link for details
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Good luck and stay safe.
drnightshadow said:
Hi !
Did you bypass ARB with dummy.img before you flashed TWRP?
Click to expand...
Click to collapse
I already had TWRP from long ago. And i didn't even try to flash a new ROM. I just formatted Data. I have the TWRP version 3.3.1-0. But as i said, PC does not recognize phone in TWRP and i can't adb sideload any ROM because of it.
naruto14 said:
I already had TWRP from long ago. And i didn't even try to flash a new ROM. I just formatted Data. I have the TWRP version 3.3.1-0. But as i said, PC does not recognize phone in TWRP and i can't adb sideload any ROM because of it.
Click to expand...
Click to collapse
Go back to previous version of TWRP(latest is buggy) or use OrangeFox recovery.
But still if you lose custom recovery you need again start over and bypass ARB.
And check if your bootloader is still unlock.
drnightshadow said:
Go back to previous version of TWRP(latest is buggy) or use OrangeFox recovery.
But still if you lose custom recovery you need again start over and bypass ARB.
And check if your bootloader is still unlock.
Click to expand...
Click to collapse
I can't go to a previous version of TWRP. I can't flash any recovery via fastboot because of the problem i said at the first post. I somehow managed to boot into some previous versions of TWRP via a tool called TOOL_ALL_IN_ONE, but nothing changed. I had the same exact problems.
How will i check in my current status if bootloader is still unlocked?
naruto14 said:
I can't go to a previous version of TWRP. I can't flash any recovery via fastboot because of the problem i said at the first post. I somehow managed to boot into some previous versions of TWRP via a tool called TOOL_ALL_IN_ONE, but nothing changed. I had the same exact problems.
How will i check in my current status if bootloader is still unlocked?
Click to expand...
Click to collapse
Use this and post the result...
Code:
fastboot oem device-info
So you managed to get TWRP via TOOL_ALL_IN_ONE, ... when you are in TWRP flash TWRP again via TWRP or better flash OrangeFox Recovery(use SD CARD or adb push - for more info google it for adb commands), than reboot it directly into recovery again by TWRP option reboot to recovery... and now you can flash your ROM.
So make it simple
1st time you'll boot in TWRP by TOOL_ALL_IN_ONE,
than you'll flash recovery via TWRP and make it permanent,
Than you'll directly reboot to recovery via TWRP,
now you can wipe and flash your ROM.
Happy ending :highfive:
The problem was that i couldn't use ADB sideload because the phone wasn't recognized by the computer. And i fixed it in a very weird way, by connecting the phone to the PC monitor's USB hub and that way the phone was discovered by the computer. So i fastbootted the latest TWRP and then easily transferred the ROM i wanted to flash via TWRP. It's crazy that i spent all day just to connect the phone to a USB hub so it could work...
naruto14 said:
The problem was that i couldn't use ADB sideload because the phone wasn't recognized by the computer. And i fixed it in a very weird way, by connecting the phone to the PC monitor's USB hub and that way the phone was discovered by the computer. So i fastbootted the latest TWRP and then easily transferred the ROM i wanted to flash via TWRP. It's crazy that i spent all day just to connect the phone to a USB hub so it could work...
Click to expand...
Click to collapse
I'm glad that you fixed your phone :highfive:
I told you usb hub is the solution :laugh: yeah win10 sh*t mess with usb and all other stuff :crying: its a total [email protected]'ll never gonna use it.
nicee your phone is alive now ....
Good luck and stay safe.