Develop Bugs

[Q] Fastboot isn't working, neither is recovery...

I want to return my at&t m8 back to stock (currently on stock rooted with one bad mod installed) so I can give the phone to my father. I dont have S-OFF and dont care about resetting the tamper flag. I have tried many methods to do so, the first being fastboot flashing the stock recovery, then fastboot oem lock, rebooting bootloader, then running the AT&T RUU. After i tried this several times, i noticed that the stock recovery never gets flashed even though it reports 'okay':
Code:
fastboot flash recovery recovery.img
target reported max download size of 1830723584 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.789s]
writing 'recovery'...
OKAY [ 0.896s]
Fastboot reboot-bootloader (both the cli command and if you go select reboot fastboot on the phone) also doesn't work, it reboots the phone normally.
Seems weird that the flash doesn't happen and that reboot-bootloader doesnt work, but nonetheless i try another method restoring a stock nandroid from http://forum.xda-developers.com/showthread.php?t=2701376 . I followed the steps, fastboot erase cache --> fastboot flash boot boot.emmc.win --> fastboot erase cache --> reboot to recovery and restore nandroid --> reboot phone. ANNDDD.... somehow I'm still on the same System/ROM as I was before all this. Also worth noting, any files I push with adb are gone after a reboot. Not sure what is going on but any help would be appreciated.

So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]

jball said:
So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]
Click to expand...
Click to collapse
Yes I have root.
Unfortunately anything that has to be done from the phone that isn't in the boot loader or recovery, is not an option at this point because it's in a boot loop (makes it to lock screen and then reboots). Sometimes it stops the loops and works for awhile, so if it does I'll give this a shot. However, is there any other method via adb/Fastboot over USB or TWRP?

Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.

redpoint73 said:
Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.
Click to expand...
Click to collapse
Device id shows when i run fastboot devices . I am Positive the fastboot connectivity is not the issue here. So i am attempting to use the bootalble RUU. Since I am S-On though, I have to relock the bootloader first. When I run fastboot oem lock I get this:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.126s
And then it reboots the phone normally, it goes into its loop, I go back to bootloader, and it still shows unlocked.
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?

cojomojo said:
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?
Click to expand...
Click to collapse
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.

redpoint73 said:
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.
Click to expand...
Click to collapse
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
Click to expand...
Click to collapse
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494

jball said:
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.

cojomojo said:
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.
Click to expand...
Click to collapse
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.

jball said:
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.
Click to expand...
Click to collapse
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.

cojomojo said:
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.
Click to expand...
Click to collapse
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome

jball said:
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome
Click to expand...
Click to collapse
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.

cojomojo said:
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.
Click to expand...
Click to collapse
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
---------- Post added at 10:19 AM ---------- Previous post was at 09:54 AM ----------
@cojomojo
If nothing else works maybe try what I have over in here
http://forum.xda-developers.com/showthread.php?t=2586472

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.
Click to expand...
Click to collapse
Strange, fastboot problems are most often a driver issue. But I agree, if you've tried it natively on Mac and PC, it would seem that drivers is not the cause.
Out of curiosity, what ROM is running on the phone currently?

jball said:
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
Click to expand...
Click to collapse
I am trying to check to see if maybe fast boot is on. I suppose it is a possibility, now I just need the phone to stay on long enough to check.
redpoint73 said:
Out of curiosity, what ROM is running on the phone currently?
Click to expand...
Click to collapse
Running stock rooted, with one mod installed (wifi tethering). It is the 50% of the problem because it is causing the reboot loop i mentioned earlier.
******* Update **********
"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick. Thanks to all sticking with helping me out here, even as we approach 3 pages

@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be

jball said:
@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be
Click to expand...
Click to collapse
Will do for sure. Thanks for your help! I'm thinking I might try and get the phone on long enough to try flashify or something. Maybe try and get s-off???

Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it, does it state so in the bootloader screen?
If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.

ashyx said:
Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it? If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.
Click to expand...
Click to collapse
Bootloader says unlocked... so I assume it is unlocked. I suppose I could go through the unlock process again, but it definitely says "unlocked". Also TWRP flashing/restoring/anything does absolutely nothing. And I have tried 3 cables and 2 computers.
*** CLARIFICATION ****
I can get into TWRP fine, and I can restore, flash ROMS, whatever... BUT even though they report okay with 0 errors, everything stays the same, i.e. nothing in TWRP actually works. Same with Fastboot.

Soft Bricked: No recovery, only fastboot

I did a CM nightly Update, which relocked my phone. I tried to unlock it but something went wrong. I can flash partitions but somehow can't boot into anything besides fastboot. When I try to boot into any recovery (even Stock) the phone just restarts after showing the Oppo logo for a moment. (Just as if I was trying to boot a custom rom from a locked device)
OEM-Info:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
Booting a recovery.img (Same reaction for every recovery):
Code:
fastboot boot twrp-2.8.7.2-find7.img
downloading 'boot.img'...
OKAY [ 0.355s]
booting...
OKAY [ 0.013s]
finished. total time: 0.368s
Phone Just reboots into a boot loop.
Flashing anything works fine but I'm getting boot loops again.
A strange thing that happens is that if i try
Code:
fastboot oem lock
the process just get's stuck showing three dots. (Same on Windows and Linux) That probably means that the bootloader is in some buggy way half way locked. (That sadly doesn't explains why the stock recovery won't work)
No idea how to fix it. Thank you in advance!
Jakob

Amazing tool here: forum.xda-developers.com/find-7/development/recovery-recovery-installer-7-t2819794

Hey !! I solved the pblm!!! what I did was just hit and trial but it worked. Now I will give the method:
Follow these steps and see if u are lucky enough!
step1: go to fastboot mod in your oppo f1
step2: flash stock recovery using adb. Type in "fastboot flash recovery stock.img"
step3: do not reboot your device and type in "fastboot flashing lock_critical".
step4: type in "fastboot reboot"
After these 4 steps I was able to boot back in Project spectrum. I haven't checked until that if I m able to go to recovery mode but I will update once I check. Check if you can boot.
Note: keep the stock.img file in the same folder in which you have your adb installed.
And I am not sure if this will work for you also.. but it is safe so go give a try!!!
THIS WORKED FOR OPPO F1f YOU CAN TRY YOUR LUCK BY USING THIS METHOD
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

A5FCN19 to A5FMB19

C:\IntelAndroid\resources\platform-tools_alt1>Fastboot reboot-bootloader
C:\IntelAndroid\resources\platform-tools_alt1>fastboot oem lock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) Userdata erase required, this can take a while...
OKAY [ 2.294s]
finished. total time: 2.298s
C:\IntelAndroid\resources\platform-tools_alt1>fastboot reboot
rebooting...
finished. total time: 0.151s
C:\IntelAndroid\resources\platform-tools_alt1>fastboot oem unlock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) Userdata erase required, this can take a while...
OKAY [ 2.217s]
finished. total time: 2.221s
C:\IntelAndroid\resources\platform-tools_alt1>fastboot flash boot recovery.img
sending 'boot' (12269 KB)
fname=recovery.img...
12269 KB / 12269 KB
OKAY [ 0.748s]
writing 'boot'...
OKAY [ 0.629s]
finished. total time: 1.382s
C:\IntelAndroid\resources\platform-tools_alt1>fastboot reboot
rebooting...
finished. total time: 0.140s
C:\IntelAndroid\resources\platform-tools_alt1>adb sideload A5FMB19_update.zip
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
C:\IntelAndroid\resources\platform-tools_alt1>cd..
C:\IntelAndroid\resources>cd platform-tools_aosp
C:\IntelAndroid\resources\platform-tools_aosp>adb sideload A5FMB19_update.zip
Total xfer: 2.00x
Complet
hi~
i have a fool english~
you need a File? write a reply your e-mail
i will send you

My device stuck at usb logo, can you help me

badao said:
My device stuck at usb logo, can you help me
Click to expand...
Click to collapse
that's bricked? or power charge?

I had A5CHB19 out of box, if you have fastboot, try my way to flash A5FMB19 http://forum.xda-developers.com/showpost.php?p=69191740&postcount=51

Can you send me the tools?
Is there include boot loader unlock tool?

Have you been here?

It's success

latheliao said:
It's success
Click to expand...
Click to collapse
Did you succeed to flash?

half way through the sidloading, it aborts the process and says, this devices for A5FCN19, not FM - what can I do? tx

ArtDo said:
Did you succeed to flash?
Click to expand...
Click to collapse
Yes
It's success
Thanks
---------- Post added at 11:11 PM ---------- Previous post was at 11:05 PM ----------
kvalvik said:
half way through the sidloading, it aborts the process and says, this devices for A5FCN19, not FM - what can I do? tx
Click to expand...
Click to collapse
You must to unlock bootloader
Than flash stock FM Recovery.img
lock bootloader
Enter to recovery mode (check A5FMB19 )
Side load A5FMB19.zip
Reboot enjoy it

latheliao said:
Yes
It's success
Thanks
---------- Post added at 11:11 PM ---------- Previous post was at 11:05 PM ----------
You must to unlock bootloader
Than flash stock FM Recovery.img
lock bootloader
Enter to recovery mode (check A5FMB19 )
Side load A5FMB19.zip
Reboot enjoy it
Click to expand...
Click to collapse
Thank you, I am going to try. Maybe I had the wrong recovery.img -- would you please give me the link to the FM recovery.img -- oh, and how can I recognise what recovery.img it is?
Thanks a lot

kvalvik said:
Thank you, I am going to try. Maybe I had the wrong recovery.img -- would you please give me the link to the FM recovery.img -- oh, and how can I recognise what recovery.img it is?
Thanks a lot
Click to expand...
Click to collapse
Please refer the link
http://forum.xda-developers.com/nokia-n1/development/iovyroot-nokia-n1a5cnb19-a5fmb19-t3466897
Link have FM recovery.img

latheliao said:
Please refer the link
http://forum.xda-developers.com/nokia-n1/development/iovyroot-nokia-n1a5cnb19-a5fmb19-t3466897
Link have FM recovery.img
Click to expand...
Click to collapse
Thanks a lot again, it's running like a charm now!

Android Marshmallow 6.0, Nougat 7.0, or Oreo 8.0 on Nokia N1 anybody?
Hi everybody,
my N1, converted from A5FCN19 to A5FMB19 along the guidelines here (thanks again!) has been working like a charm ever since. However, I wonder, has anybody tried to upgrade the N1 from Android 5.1.1 to a newer Android version, is that possible at all? I would like to use the split-screen / multitasking

If anyone still has the A5FMB19_update.zip file, I'd like to have it since the download links are offline

I has not the A5FMB19_update.zip file, please help me!

See my thread here for the ROM files.

Pixel XL bricked, bootloader n/a baseband n/a

I waked up this morning and checked time on my Pixel XL, about 30 mins after I checked my phone which has been powered off. I tried to power on, it screens off right after the google logo showed on, and loop.
Then I entered bootloader, it shows:
Code:
BL: N/A
Baseband: N/A
Product/Variant: marlin-ROW-PVT
Serial Number: HT69Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
My Pixel XL is now on Dec 2016 7.1.1 (NMF26O). I tried to flash bootloader from NMF26O and NMF26U, it failed, showing:
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 0.735s]
writing 'bootloader'...
FAILED (remote: Verify bootloader image failed on production device.)
finished. total time: 1.338s
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
Code:
>fastboot boot twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
creating boot image...
creating boot image - 9072640 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.653s
Does anyone here know how to fix this without wipe my data? I have super super important data on my phone.
-------edit--------
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?

ghovik said:
I waked up this morning and checked time on my Pixel XL, about 30 mins after I checked my phone which has been powered off. I tried to power on, it screens off right after the google logo showed on, and loop.
Then I entered bootloader, it shows:
My Pixel XL is now on Dec 2016 7.1.1 (NMF26O). I tried to flash bootloader from NMF26O and NMF26U, it failed, showing:
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
Does anyone here know how to fix this without wipe my data? I have super super important data on my phone.
Click to expand...
Click to collapse
So you can at least get into bootloader right? Does "fastboot devices" show your serial?

aholeinthewor1d said:
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
Click to expand...
Click to collapse
Yes I can boot into bootloader, 'fastboot devices' shows my device correctly. But any 'fastboot flash' or 'fastboot root' returns failure. for example, I tried to flash boot.img, returns:
Code:
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (26229 KB)...
OKAY [ 0.611s]
writing 'boot'...
(bootloader) Flashing active slot "_b"
FAILED (remote: flash write failure)
finished. total time: 0.866s

@ghovik,
Try putting it on the charger for a while. I'm not saying your battery is dead, but it sure can't hurt.

Thanks. I have charged it for about 30mins. You remind me of another strange thing, when it is powered off and connected to the charger, the charging battery logo shows up for 1 sec and screens off. It loops for few times and the phone starts booting itself. So I put it into bootloader mode now while charging.

ghovik said:
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
>fastboot boot twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
creating boot image...
creating boot image - 9072640 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.653s
Click to expand...
Click to collapse
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.

^^^ What he said.
Too many links usually means a bad filename or bad path to the file.

muzzy996 said:
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
Click to expand...
Click to collapse
Oh this is my fault. Now I tried 'fastboot flash twrp-3.0.2-0-RC1-fastboot-marlin.img', it worked but, first the google logo shows up and immediately screens off, then root loop as the same as I boot my device.

I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?

TonikJDK said:
^^^ What he said.
Too many links usually means a bad filename or bad path to the file.
Click to expand...
Click to collapse
muzzy996 said:
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
Click to expand...
Click to collapse
cam30era said:
@ghovik,
Try putting it on the charger for a while. I'm not saying your battery is dead, but it sure can't hurt.
Click to expand...
Click to collapse
aholeinthewor1d said:
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
Click to expand...
Click to collapse
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?

ghovik said:
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
Click to expand...
Click to collapse
Fastboot set_active _a

TonikJDK said:
Fastboot set_active _a
Click to expand...
Click to collapse
It seems this is not a correct command because I tried this commend and it returns the usage help.

ghovik said:
It seems this is not a correct command because I tried this commend and it returns the usage help.
Click to expand...
Click to collapse
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>

TonikJDK said:
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
Click to expand...
Click to collapse
I think you are right. I googled this command, all the websites said the same command as you told. It might be my fastboot version problem. May I ask what version are you using?

ghovik said:
It seems this is not a correct command because I tried this commend and it returns the usage help.
Click to expand...
Click to collapse
Try updating your ADB and fastboot. From here > https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv

ghovik said:
I think you are right. I googled this command, all the websites said the same command as you told. It might be my fastboot version problem. May I ask what version are you using?
Click to expand...
Click to collapse
https://developer.android.com/studio/releases/platform-tools.html

@TonikJDK,
FWIW: the link that I posted above allows one to download just ADB and fastboot directly from Google. Tiny little package.

TonikJDK said:
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
Click to expand...
Click to collapse
I've installed Minimal Adb and Fastboot just now. I tried the command it returns:
Code:
>fastboot set_active _a
error: Could not get suffixes.

cam30era said:
@TonikJDK,
FWIW: the link that I posted above allows one to download just ADB and fastboot directly from Google. Tiny little package.
Click to expand...
Click to collapse
My link is the link on the page he directs you to. Saves a click.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
ghovik said:
I've installed Minimal Adb and Fastboot just now. I tried the command it returns:
Code:
>fastboot set_active _a
error: Could not get suffixes.
Click to expand...
Click to collapse
Dang it, stop using Minimal. It is old...from like March of last year. Our Pixels are different...they have dual partitions, they need the newer fastboot and adb.

TonikJDK said:
My link is the link on the page he directs you to. Saves a click.
Click to expand...
Click to collapse
Cool. Thanks.
---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------
TonikJDK said:
My link is the link on the page he directs you to. Saves a click.
Click to expand...
Click to collapse
Well, all I see is the SDK package (which is a lot smaller than the full Studio). Unless I'm missing something, I don't see any link to just the ADB and fastboot....

Help unbrick honor 7x frp locked, bootloader loked. rescue mode only save me or..?

Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....

JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
this needs to come here n the open, not in my PM.
PS C:\adb> fastboot flash rescue_recovery_ramdisk C:\adb\twrp_openkirin_sudeep.img
target reported max download size of 471859200 bytes
sending 'rescue_recovery_ramdisk' (25164 KB)...
OKAY [ 0.854s]
writing 'rescue_recovery_ramdisk'...
OKAY [ 0.031s]
finished. total time: 0.885s
PS C:\adb> fastboot reboot
rebooting...
Click to expand...
Click to collapse
recovery flashed while frp and bootloader locked.
!!!!!!!!!!!!!
---------- Post added at 06:55 PM ---------- Previous post was at 06:16 PM ----------
What happens after reboot, try to boot to recovery with volume button, when you use
Code:
fastboot flash rescue_recovery_ramdisk RECOVERY_RAMDIS.img
recovery_ramdisk
does phone still have your broken twrp or the stock recovery?

JKmamba$ said:
https://ibb.co/nKOuRT
https://ibb.co/ccECD8
https://ibb.co/m1qxfo
for new users prevented post external link sorry .... you can for me?
Click to expand...
Click to collapse
so the fastboot command shows ok flashed, but its not changing the loaded recovery image.
don't know what to suggest next.

JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen

Thetpcguy said:
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen
Click to expand...
Click to collapse
let me chek man take a pictures of all single screen you'll see... RECOVERY, AFTER RECOVERY (bootloop logo, black screen ecc), and FAST BOOT MODE.. maybe i help you ... i won't to roll back my device because oreo is very perfomance but so buggy for exemple bluethoot don't worck multy shut on photograf bugged or many root application work and after 5 min close with (root with magisk -_-")... in nougat don't have ever this problem root with only super su and all unlocked....