Develop Bugs

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?

grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium

All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk

Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....

borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?

grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html

zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted

~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'

anybody have any other suggestions to this? or a follow up?

It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium

Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.

grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)

ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?

grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app

not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img

Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"

grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm

ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

[Q] Recovering Verizon Galaxy Nexus

Hey all, I got a new Galaxy Nexus today and went about rooting it. Apparently something didn't happen correctly and now I'm caught in the kernel boot screen ("Google" with unlocked lock) loop. I'm surprised by this because I've rooted another and haven't had a problem. I've tried running `fastboot flash system ~/Downloads/aokp_toro_jb-build-1.zip` and that hasn't helped the boot loop.

Did you get a custom recovery (cwm.. twrp) loaded ... what steps did you perform to root and what was the last step before the looping?

pepp67 said:
Did you get a custom recovery (cwm.. twrp) loaded ... what steps did you perform to root and what was the last step before the looping?
Click to expand...
Click to collapse
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?

read this, before you mess up for real.
Sent from my i9250

bk201doesntexist said:
read this, before you mess up for real.
Sent from my i9250
Click to expand...
Click to collapse
I followed all of those instructions and I'm still caught in the boot loop. I did notice though that the `userdata.img` and `boot.img` weren't included in the .tgz that I downloaded for my toro.

JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
yeah its most likely the fact you didnt have usb debuggin on

JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
in parts:
JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock`
Click to expand...
Click to collapse
first you unlock, then you flash a custom recovery...
JustLikeThat said:
and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
Click to expand...
Click to collapse
do you see your device's SN under 'adb devices' output?
JustLikeThat said:
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Click to expand...
Click to collapse
what cwm version are you using?
JustLikeThat said:
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
unrelated, in recovery at least. a custom recovery would be meaningless without adb support. inside android itself, yes, of course, if usb debugging is not on, you can't use adb.
JustLikeThat said:
I've tried running `fastboot flash system ~/Downloads/aokp_toro_jb-build-1.zip` and that hasn't helped the boot loop.
Click to expand...
Click to collapse
of course it didn't work, that zip is probably packed for CWM/TWRP! you don't know what you're doing man, just read, read it again, read it one more time, and again re-read the thread that I posted, that will lead you unlock bootloader and get your device back to JB STOCK (!) through fastboot, since google-provided stock fastboot images are available for toro (you're SURE you have a toro, right? as in, Verizon Galaxy Nexus, right? just checking).
THEN you can flash a custom recovery, and a custom rom.

Well I found the correct stock image and just decided to start from square 1.
Sorry for the vague question and ignorance. I was honestly incredibly stoned when I wrote it and was doing this, attributing to the facts that I rushed everything, assumed I knew more about what I was doing than I did and didn't verify the md5's of the downloaded files. Thanks for being so thorough @bk201doesntexist, I'll be more careful round 2.

JustLikeThat said:
Well I found the correct stock image and just decided to start from square 1.
Sorry for the vague question and ignorance. I was honestly incredibly stoned when I wrote it and was doing this, attributing to the facts that I rushed everything, assumed I knew more about what I was doing than I did and didn't verify the md5's of the downloaded files. Thanks for being so thorough @bk201doesntexist, I'll be more careful round 2.
Click to expand...
Click to collapse
thanks. you got it, hash check is one of the best ways to check a file is good to go. although i'm not by any means a cryptography expert, i suggest you use sha256sum instead, safer than md5sum (i don't think we have found how to fully mitm or fully collision a sha-1 hash, let alone a sha-2 family hash). just something for everyone to think about, md5sum will suffice if you not all that worried.
also, remember that if some image is broken (corrupted), you'll never be able to flash it through fastboot.

Honor 7x with Lineage and TWRP, stuck in limbo

Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?

Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32

It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?

Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen

I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.

Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk

Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works

smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use

dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot

Please can you tell me the process to install twrp I have the L24

I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.

I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?

Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.

I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.

Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.

I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).

Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?

Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.

Fire Stick Gen 2 in bootloop after failed update

Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto

Phaisto said:
Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto
Click to expand...
Click to collapse
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.

Sus_i said:
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.
Click to expand...
Click to collapse
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....

Phaisto said:
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....
Click to expand...
Click to collapse
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please

Sus_i said:
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please
Click to expand...
Click to collapse
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...

Phaisto said:
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...
Click to expand...
Click to collapse
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??

Sus_i said:
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??
Click to expand...
Click to collapse
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.

Phaisto said:
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.
Click to expand...
Click to collapse
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
Code:
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin
or twrp file manager, if you have an otg cable and a mouse.

Sus_i said:
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
or twrp file manager, if you have an otg cable and a mouse.
Click to expand...
Click to collapse
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?

Phaisto said:
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?
Click to expand...
Click to collapse
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.

Sus_i said:
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.
Click to expand...
Click to collapse
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....

Phaisto said:
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....
Click to expand...
Click to collapse
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...

Sus_i said:
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...
Click to expand...
Click to collapse
I have downloaded the zip- files with Ubuntu and extracted as well. I used bash, as I saw it in the posts as a possible fix to problems, but my Linux knowledge is limited so I just used it without thinking about it....
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
https://photos.app.goo.gl/BAL9V2sQhjowTq498
https://photos.app.goo.gl/iL5D3meE6LgNjdDW8
Any ideas?
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?

Phaisto said:
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
Click to expand...
Click to collapse
probably it goes into fastboot, but maybe not the unlocked hacked one
Phaisto said:
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
Any ideas?
Click to expand...
Click to collapse
have you tried to run: fastboot devices
behind the boot-fastboot script?
Phaisto said:
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?
Click to expand...
Click to collapse
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.

Sus_i said:
probably it goes into fastboot, but maybe not the unlocked hacked one
have you tried to run: fastboot devices
behind the boot-fastboot script?
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.
Click to expand...
Click to collapse
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?

Phaisto said:
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?
Click to expand...
Click to collapse
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.

Sus_i said:
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.
Click to expand...
Click to collapse
Debian did not work either, same result....
Changing cable, same result....
I suspect, the bootrom-step script can't write the hacked fastboot...
Does anyone have an other idea how to fix this stick?
Amazon took the lazy way out and just offered 15% discount.... On a device their update broke....

Pixel 3xl Encryption issue.

So for starters. I was on the latest Android 11 rooted with magisk and LSposed along with GB.
I decided to sideload the Android 12 DP. So i floashed the stock boot image to both slots and then sideloaded 12DP. Everything went fine and i was testing A12. Tried to root A12 with magisk by the standard patch boot.img and fastboot flash to both slots. The phone hung on the bootscreen for like 10 minutes so i figured it best to flash back to A11. Back to BL mode and flashed theboot.img to both slots and then flash-all A11. Hit start when finished and it just flashed the white google screen for a few seconds then back to bootloader. Strange. Tried again, while changing active slots to ensure its flashing the system to both slots. Will not boot. Straight back to bootloader.
I can flash individual partions and i have no errors other than when wiping data it says it cant. Cant remeber exactly the error. But this is where it gets even more weird. I can flash android 9 and have no issues, I can take OTA updates with not issue. I can and am rooted and my phone is back to A11 via OTA. It will not boot if i flash or sideload any other version of Android other than A9. I believe this has something to do with encrytion. My phone was encrypted when i started this whole proccess and i believe thats why i get the error when trying to wipe data. In A9 recovery, when i factory data reset. it wipes with no errors. If i try to factory data reset in A10 or A11 Recovery i get the error E: can't send spi message: Try again .
So in closing, my phone is working and running fine but i can not flash-all any Android version other than A9 and have the phone boot.
So if anyone knows the proper steps to get this phone right, I would greatly appreciate it.
If not, i guess i will only be taking OTA's until i can figure it out.
Happy flashing!
Quick edit
Yes i pass safetynet and all banking apps work.
so is doing anything at all really necessary. I will leave that for the community to decide.
My opinion is, There is something wrong that needs fixing here. But its not crucial.

On A10-11 did you try "fastboot erase userdata" ?

wangdaning said:
On A10-11 did you try "fastboot erase userdata" ?
Click to expand...
Click to collapse
I did and it gives an error. Wish I wrote down the error like I did the other one. It's the same error at the end of flash-all when I don't remove -w

Try fastboot format userdata.

Just to add.... I can flash PixelDust (custom rom) and it boots and works great but can not flash-all or sideload android 10 or 11. Can only flash Android 9 and take OTA's up to Android 11.

Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.

wangdaning said:
Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.
Click to expand...
Click to collapse
I wish it were that simple. Unfortunately i actually updated it and also added the Android S Preview SDK and restarted my PC before even attempting this whole thing. And to make sure, just now checked for updates and its up to date.

What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.

wangdaning said:
What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.
Click to expand...
Click to collapse
You may be onto something here.....thoughtts?

And i think i have fixed that part on my PC. This is now what i get. I had that all-in-one tool installed so it made my system wide fastboot/adb look at its program folder instead of my default installation folder. Thats uninstalled and all folders and registry keys associated with it and my system is looking at my android sdk installation folder as it should.
This may very well have been the issue. I haven't tried to flash anything yet as i'm a bit gun shy after this fiasco lol
Maybe i will try flash-all with -w removed to see what happens.

Fastboot erase data?

jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
That may likely work now as one of my issues was my fastboot was the wrong version because of the all-in-one tool i had installed. Haven't tried it yet and may not need to loose data if the flash-all command will work past android 9 which it should now thats its using the proper fastboot/adb version.

wangdaning said:
Try fastboot format userdata.
Click to expand...
Click to collapse

jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
that finishes wothout any error....good start

is this how -w should work......sidenote, i can now flash-all android 11 and boot to system

Thank you @wangdaning for suggesting checking my fastboot version! That lead me to see i had 2 version and was defaulting to the wrong version. Removing that version and fixing my system path in windows variables fixed my issues. It was fastboot version the whole time. Again thank you @wangdaning!!
Edit to thank all who replied to this thread. I used everyones ideas

Glad you got it working.