Ok, guys. I tried every option on every forum and none of them worked so here I am.
I unlocked and rooted my nexus 4 using the Wugfresh toolkit v 1.9.3. Everything worked perfectly until I tried to flash Cyanhacker ROM and kernel at the same time. I factory reset my phone before doing that (wiped dalvik/cache etc.). In TWRP, it said everything was successful, however I got stuck in a bootloop and when I tried to factory reset again, I accidently wiped my OS as well (i know... i am a retard:cyclops. Now I can only go in fastboot and TWRP.Now, I tried to use Wugfresh toolkit to Flash Stock + Unroot while being in fastboot, but it states that "Fastboot device was not found". Suggestions?
Thanks in advance.
First of all check you have fastboot driver install for your Nexus 4.
After that, you can try to reboot again in bootloader and from fastboot command line write "fastboot devices".
If your device appear you can reimage your stock image.
If you could load TRWP recovery, from it you can use install from sideload to "reinstall" again the original or modify custom rom.
That's the problem, when I connect my phone to my PC, nothing happens. When i try to open device manager I dont see my phone or the Android ADB Interface.
it happened to me last week, use usbdeview (easily googled) to uninstall all your android related driver from it, don't forget to check the driver properties to delete the inf file also.
restart your pc and search then install universaladb driver (do some googley again) then try again. though last week my side here had to reinstall my xp from scratch to get mine working but i hope you aren't.
so i feel like Ive tried everything.
tried to flash a rom and gapps in twrp and phone booted to warning screen with the yellow triangle.
passes that and then goes to google splash screen with unlock icon. and then repeats to the cycle.
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
my phone is unlocked.
computer can see it as fastboot devices
computer CANNOT see it under abd devices
i am able to install and get into TWRP using skipsoft tookkit.
i feel like i am running out of things to flash onto the device haha
any help is appreciated.
barrackOBAMA said:
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
Click to expand...
Click to collapse
First, I'd recommend staying away from Toolkits, as you can't really see what's happening and diagnose issues. Since you've used fastboot/ADB commands, you know they are faster anyway. When you say your PC can't recognize your device in ADB, was your device in recovery? Make sure you're in recovery and you're ready to receive ADB commands. If you CAN see your phone with fastboot that means you're in the bootloader, whereas you have to boot into recovery to see your device via ADB.
Also, you didn't outline anything else you may have done. Did you restore from a nandroid with a buggy version of TWRP? Your issue sounds like the TWRP EFS restore bug (3.0.2-2). It effectively bricks your device, but there is a thread here that discusses it. Effectively you need to be recovery ADB mode and run a couple commands to delete your EFS partition and that will fix the issue.
More info here: http://forum.xda-developers.com/nexus-6p/help/im-stuck-google-logo-stop-reboots-twrp-t3452842
Make sure you've also installed the updated 3.0.2-3 TWRP as it will work with encrypted data and doesn't have the EFS bug.
I accidently formated everything in twrp and ended without OS and was stuck in custom twrp. I tried to flash stock recovery and that went ok. Now whatever i do i cant sideload stock zip file using adb. Fastboot is recognized but adb is not. When connected to pc shows error. I have tried to install, reinstall all sorts of drivers but all the same. Is there a way to get back to stock using fastboot commands manualy? Please help !!
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
himanshuladia said:
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
Click to expand...
Click to collapse
You mean stock twrp or custom because i have stock but when connected i cant copy files on device because it is not recognized by PC
Del.
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
himanshuladia said:
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
Click to expand...
Click to collapse
Ok will try !
Del.
Finaly i did it after a few hours of trying to find a solution and figuring out why my PC doesn't recognize phone in adb I tried on an old PC with win7 installed and sideload went smooth like butter on first attempt. I have tried on two computers with win10 installed, tried with all sorts of USB cables, usb on computer 3.0 , 2.0, tried all sorts of drivers and nothing helped. I hope that someone else will have a benefit of this post and sort of a solution if he will have the same issue. Thanks to everyone that tried to help out!
I have a file for a twrp recovery image 3.5.4 and firmware but I have not been able to upgrade any firmware using the computer spflashtools or flashtool. I rooted with kingroot 4.5 then used terminal to replace it with supersu. Rebooted to fastboot using terminal but would not show up left waiting for device. on minimal adb. Recovery was android guy nothing else you could do. Tried flashify, mobileuncletools changed the recovery to a funos screen but still no twrp. Is Magisk possible on android 4 at all or could I possibly use firmware from another mtk6572 with android 5 or 6? I thought I had all drivers installed computer recognizes it as storage just wont appear as adb. Thank you for any leads
I didn't understand clearly. Do you trying to flash a rom with sp flash tool with watch on fastboot mode? if yes sp flash tool won't recognise the watch. Watch needs to shutted down (turned off) for sp flash tool. (Forgive my English)
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.