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.
Related
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.
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?
Hi I tried to OTA on my D802. It downloaded the latest update file, rebooted to TWRP, then I had to manually instlal the update and since I did it it bootloops to TWRP.
So I wiped all data, system .. everything and via USB-OTG flashed clean OS and gapps. Anyway Im not able to boot to OS even I press BOOT TO SYSTEM in TWRP.
I updated TWRP to the latest 3.0.3-a (originally I had 3.0.2-1.
I cant boot to OS and my D802 is useless. anay help ???
thank you
Petr
Manually like fastboot? Are you sure you did not flash TWRP to boot instead of recovery?
Sent from my Nexus 6 using Tapatalk
My D802 downloaded new nightly build and rebooted to TWRP and nothing happened. So I install the new nightly manually in TWRP.
Since I did it it reboots only to TWRP.
Tried to wipe all in my phone including internal storage etc. and installed new fresh Lienage (tried more nightly)
I even tried to install it from fastboot and it boots only to TWRP itself even I use BOOT TO SYSTEM in TWRP.
i had no chance to flash TWRP instead of updated OS since there is only lineage-14.1-20170306-nightly-d802-signed.zip and open_gapps-arm-7.1-stock-20170308.zip on my flash (OTG)
update: It does not matter what ROM do I install to my D802, I get TWRP bootloop only ..
Solution
I know the solution of this problem just read carefully
You have to do it from the fastboot.
Google your device and learn how to enter into fastboot mode after switching off the phone via pressing combination of hardware keys.
Then Google and download the exact same following files for your phone model not others (wrong files will brick your phone). Following are the files :-
1 boot.img
2 droidboot.img
3 recovery.img
4 rom.zip
(All the above mentioned files should be the official files provided by the manufacturer company of the phone)
Now download the basic Windows or mac or Linux driver of your phone for the computer you have and install it in your computer, then restart your computer and also install the "minimal fastboot" in your computer and then connect your phone while phone is in fastboot mode, then copy all the above mentioned files in the folder where the minimal fastboot driver is installed.
Now go to that folder where minimal fastboot is installed in your computer and press shift key and while keep pressing the shift key right click the mouse and select "open command" here.
Note Google and learn the command how to check whether your device is connected to your computer via fastboot.
Then install all the mentioned files using fastboot commands.
Hurry you have your phone with official ROM and then if you want use the same technique you may have used earlier to unlock bootloader and root your device and installing the latest twrp.recovery and then lineageos.
Now your phone is unbricked and you have latest lineageos.
Also remember the ota update of lineageos is broken so don't install updates via updater app.
The safest method is to download the whole update package and put it into your phones internal/external/usb otg drive and install via custom recovery.
Be happy
जय श्रीराम ?????
Hi, yesterday I was flashing a rom with flash tool. It finished, reboot but it didn't start anymore. No fastboot nor recovery. Seems to be dead.
Is there a way to start it?
Thanks,
Andrés
Does this help?
Please report back.
Hi! thanks, it worked. Now I'm having a different issue with TWRP.
I install TWRP via fastboot, but i can't access the data inside the phone nor do the wipes. It shows errors.
When I boot the TWRP i don't enter any password or something like that.
Any ideas? It is a TWRP issue?
Thanks
andres88_ said:
Hi! thanks, it worked. Now I'm having a different issue with TWRP.
I install TWRP via fastboot, but i can't access the data inside the phone nor do the wipes. It shows errors.
When I boot the TWRP i don't enter any password or something like that.
Any ideas? It is a TWRP issue?
Thanks
Click to expand...
Click to collapse
Glad to hear your device is back from the dead.
Are all TWRP functions available? And all info gibberish?
Before installing TWRP, you can also see if it works without installing it by just booting it.
Code:
fastboot [B]boot[/B] recovery TWRP.img
See if folders are readable now, then extract data. Try different TWRP's. There are a few for Mi Max 3. Keep trying, TWRP does have some rare and occasional hiccups with password and decrypting. Also for me. Just reboot and try again until it works. Try to boot Orange Fox in recovery if needed.
Second, if nothing works, you may try and download the ROM you used before updating. Extract boot.img, recovery.img and system.img from old ROM and flash with fastboot:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
This will restore the 3 .img's. Boot into recovery and see if you can pull data.
Let me kow if it helps because maybe otherwise you have to worry about flashing full ROM and lose data.
Addendum: if you run into trouble when flashing you can use Xiaomi ADB/ Fastboot Tools. Install Java first though. Also, please be aware of Xiaomi's ARB feature.
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.