Hi All,
I just bought a new Hero two days ago. Since then I performed the following steps:
1.) downloaded the kernel source from HTC
2.) Compiled a kernel.
3.) As root:
a.) adb push newBoot.img /sdcard
b.) # cat /dev/zero > /dev/mtd/mtd2
c.) #flash_image boot /sdcard/newBoot.img
I did not install a recovery image unfortunately.
So.. after doing those steps the phone reboots, and displays
"HTC". It doesn't progress past there.
things i've tried.
1.) Installed a known .img that works. Renamed Recovery-RA-1.5.2.img to /sdcard/newBoot.img
2.) Copied other images that might work to /sdcard/newBoot.img
3.) renamed an image to HERC[DIAG|IMG].zip
Any other ideas I can try? I can boot to fastboot screen. Just not sure what else to do before I scrap it.
Any suggestions welcome.
how long did you wait at the HTC screen? it can take up to 10 minutes after the first boot.
hmm.. I didn't wait more than 5 minutes... I'll give that a try and see what happens. Hopefully that's all there is to it....
or you can just download a stock RUU and flash that.. Will atleast get you back to stock.
OK I tried that.. but since I can't boot into linux, I cannot get any adb commands to respond.
Between the "htc" screen that goes nowhere and the
the fastboot screen, I'm not sure how to install it.
I keep getting a USB 170 error.
still waiting at the HTC screen.
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
fred43 said:
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
Click to expand...
Click to collapse
The phone just needs to be on and connected to the pc when you run the RUU.
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
fred43 said:
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
Click to expand...
Click to collapse
If you can get in to fastboot then you should be able to run RUU while booted up in to fastboot. If not then you should be able to flash either a boot.img or RA's recovery img while in fast boot. At that point you should be able to boot the phone or boot in to a recovery image and flash a rom.
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Option 2) Download fresh rom (or any rom) and then extract the boot.img from the zip and copy it to your sdcard. And then fastboot boot /sdcard/boot.img
Option 3) You can TRY actually flashing an img through fastboot but I'm pretty sure it's disabled on our phones. fastboot flash recovery /sdcard/Recovery-RA-1.5.2.img
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
You can PM me if you have questions.
flipzmode said:
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Click to expand...
Click to collapse
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
I think this error is happening from the linux machine. I tried this command as a non-root user and got the same response.
flipzmode said:
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
Click to expand...
Click to collapse
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
Click to expand...
Click to collapse
Ok try running it off of your computer then. fastboot boot /home/user/boot.img (wherever you actually have it)
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Click to expand...
Click to collapse
Yup. That's our exact problem and why we are somewhat limited on what we can do for modifying stuff.
With HBOOT-1.41.0000, the boot option is disabled apparently...
sudo ~/android/android-sdk-linux_86/tools/fastboot boot ./boot.img
downloading 'boot.img'... FAILED (remote: not allow)
Yea I knew that with our hboot the option to flash via fastboot was disabled, but I have been able to successfully boot through it. That's how I test my boot imgs. Other than trying the RUU while you are in fastboot it seems like it's pretty dead.
What happens if you boot in to the recovery partition? The stock one. Does adb see the phone then?
Well I just tested the RUU, 1.29 version. I got this error:
ERROR[140]: BOOTLOADER VERSION ERROR
The recovery partition ( default one) apparently doesn't exist just shows an
X or something with a phone. ( The default image ?)
What version of fastboot are you using? That seems to be my only hope at this point.
Is this a "with google" branded phone?
The fastboot I have is the one that came with the sdk for windows. It doesn't provide me with any type of version number.
Ok, I got it to boot off of one of the later fresh.zip's boot.img.
The default version of hboot has most options of fastboot disabled.
However, there is a way of getting around it.
1.) boot into fastboot mode
2.) fastboot -s $DEVICEID oem rebootRUU
3.) fastboot whatever, upgrade, boot etc all seem to work.
Still waiting on the boot... still stuck at the "HTC" screen. hopefully it will boot up eventually.
fred43 said:
2.) fastboot -s $DEVICEID oem rebootRUU
Click to expand...
Click to collapse
I knew that command worked with adb (that's how you do a manual RUU) but I didn't think it worked in fastboot. Good to know.
See if you can adb now that it's running off a proper boot.img.
Well looks like I spoke to soon. The boot option apparently ignores the file argument while in oem mode.
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
fred43 said:
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
Click to expand...
Click to collapse
Not that has been made available, no. You didn't answer me earlier. Is your phone stamped "with google" on the back cover?
Related
How do you guys boot to fastboot if you have turned your phone off? I mean the actual fastboot ("black Huawei logo") not the recovery and not the pink bootloader. I can get to it if I reboot my phone if I press reboot and then bootloader, but is it possible without it?
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
-e-
Weird discovery I made. While trying to flashall it says the device is "swordfish"... If I flash system.img separately it says "no partition table exists". Anyone has used fastboot before?
Nice. With the new Android version, the product shows MSM7630_SURF. It now properly boots to fastboot without going to charging too, so thats an update.
Blefish said:
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
Click to expand...
Click to collapse
Thanks! I was trying to set up my UDEV (51-android.rules) and your post helped me boot into the bootloader mode to get the right idVendor & idProduct codes.
Blefish said:
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
-e-
Weird discovery I made. While trying to flashall it says the device is "swordfish"... If I flash system.img separately it says "no partition table exists". Anyone has used fastboot before?
Click to expand...
Click to collapse
I tried fastboot, but I just get a black screen with huawei logo. No any function, no adb connection, no menu entries or anything and no buttons work. And I can exit only by remove battery. Is this right?
dancer_69 said:
I tried fastboot, but I just get a black screen with huawei logo. No any function, no adb connection, no menu entries or anything and no buttons work. And I can exit only by remove battery. Is this right?
Click to expand...
Click to collapse
There's an external tool called fastboot which handles that. There you can reboot or even continue the boot.
Fastboot is broken as far as I know, no partition table exists.
Sent from my U8800
You mean the fastboot from adb tools which can used from command line? This cannot work because there isn' t adb connection on bootloader mode.
Or is another tool which can be flashed or something to device?
dancer_69 said:
You mean the fastboot from adb tools which can used from command line? This cannot work because there isn' t adb connection on bootloader mode.
Or is another tool which can be flashed or something to device?
Click to expand...
Click to collapse
I think you are confusing pink screen with fastboot/bootloader. The fastboot is the node where it stays in the Huawei logo.
Sent from my U8800
No, I know the difference. I get this screen, but nothing else. On my previous device, fastboot has some functions included flash rom, reboot and some else that I don't remember. I also could from adb to use fastboot command.
On X5 I just get this screen.
Maybe they disabled that in B522 too, I am not sure. It was bugged anyway. I only tested it on B138 and B518.
Yes, I have 522 and I thought this too. I've tried on B138 1-2 times and was the same huawei logo screen only too. I didn' t tested it more because I thought that just this mode is disabled and used pink mode only. In B138 sould appear something else on screen, or only commands from adb work?
Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?
ADB and fastboot drivers are different.
Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....
http://bit.ly/Zqk7pm
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....
Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.
oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck
bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...
In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes
SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).
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.
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Brettroth said:
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Click to expand...
Click to collapse
Tried your image and still same result. I am running following command
Code:
fastboot boot TWRP-3.6.1_11-OP6xT.img
The command window outputs the following
Code:
Sending 'boot.img' (34964 KB) OKAY [ 0.747s]
Booting OKAY [ 0.092s]
Finished. Total time: 0.860s
The phone then reboots into Fastboot Mode logo and stays stuck there. I even tried unplugging the USB after it reboots as well.
I even tried using the flash command instead of boot but no success.
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Brettroth said:
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Click to expand...
Click to collapse
I tried doing fastboot boot recovery but i get following error
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Brettroth said:
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Click to expand...
Click to collapse
When I am in fastboot mode, yes I can choose recovery but it takes me to the stock recovery. I do not have a option to flash any zip files there
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Brettroth said:
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Click to expand...
Click to collapse
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
smartinez832 said:
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
Click to expand...
Click to collapse
I don't know bud. I guess msm tool is the way to go then
Curious did you have the twrp file in same folder as adb and fastboot?
smartinez832 said:
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
Click to expand...
Click to collapse
I'm having same issue with fajita (OnePlus 6T) you found any solution if yes then please give some reply
Hey,
so yesterday I tried to install TWRP recovery.
While trying I assume that I hard bricked the phone and got the message that the current image has been destroyed and cant boot.
I've tried using MSM but the device wasnt recognized, I installed the qualcomm usb drivers and it worked for some time but still wasnt recognized in MSM.
Now I have the problem that when I plug it in, it only shows the above mentiond message. When I shut it off and press vol +/- it then goes into fastboot but cycles through it and is still only shown as android device in the device manager.
I'm using the usb 2.0 and original OP cable. Build number was IN2023...c.36, A12 and OOS12
ADB does not work, fastboot commands still work while it is in the fastboot cycle.
Does someone have any solutions for that?
Thanks
How did you "install" twrp?
via fastboot? or through booted twrp? Because from what i read, twrp or orangefox likes to patch boot image instead of flashing recovery partition.
So my suggestion is to flash via fastboot original boot.img and recovery.img
I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had
w4rdl0rd said:
I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had
Click to expand...
Click to collapse
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask
Thank you, it finally works
ShadoV90 said:
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask
Click to expand...
Click to collapse
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for
w4rdl0rd said:
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for
Click to expand...
Click to collapse
Wait... system can't boot up?
ShadoV90 said:
Wait... system can't boot up?
Click to expand...
Click to collapse
yeah, it goes always back to recovery
Hmm... Then i'm afraid that MSM is now your only option. Sincerely, i never used that, so i found thread with guide how to do it.
Look please here, read carefully, and i hope you will be able to recovery your device.
I guess it will rollback your system to OOS11.
PS. Give feedback if it was succesfull (or not).
Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work
w4rdl0rd said:
Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work
Click to expand...
Click to collapse
I hope it will work.
BTW, next time when you will try recovery like twrp or orangefox, don't flash it but boot it via fastboot.
fastboot boot <drag file of twrp/orangefox>
If it will work, and everything will work, then use fastboot flash recovery <drag file of twrp/orangefox>
Don't flash it via twrp/orangefox, because like i said, it will probably try to patch boot partition and in result boot will be unusable.
thanks for the advice, I'll try it next time or when I get it running again
w4rdl0rd said:
thanks for the advice, I'll try it next time or when I get it running again
Click to expand...
Click to collapse
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD
ShadoV90 said:
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD
Click to expand...
Click to collapse
I tried/am trying to get MSM working. It connected now in edl, in MSM it still freezes. No matter what I do it has the status "waiting for communication".
If I remember correctly then there was somethin with ..._b. But since I've closed the command prompt I can't look it up anymore.
I'll try to change slots and let you know if there will be a result.
With MSM there is one problem. After succesful operation your phone will be locked. I mean bootloader will be locked.
I did as you wrote...it works fine now. I think. There is still A12 and OOS12 installed but it is lagging a bit.
I attached a screenshot of the terminal with the slots. Does having switched them pose some problem? Do I have to switch them back?
Just check if you have an update. If you have, then install it via system update. For now, you have working system. Now you have much more possibilities to use. Like if you don't have update you can apply manually one which you downloaded. In system ofc.
There are no updates, there is the most recent version installed.
Thank you for the help in solving it
w4rdl0rd said:
There are no updates, there is the most recent version installed.
Thank you for the help in solving it
Click to expand...
Click to collapse
So, this is C36 installed?
yeah there is c36 installed