[Q] Stuck unable to get into recovery from hboot - Desire General

Everyone here is awesome.
first off.. I have
hboot0.83.0001
radio-5.09.00.20
I'm stuck at hboot can't get into recovery. I've searched all the possibilities and tried all of them so far. I'm either stuck at black screen or white HTC screen, sometimes with black bar across top sometimes not. I've tried the blind button pusshing and I don't have a gold card made.. so those didn't work. Even had help from a senior member, who was amazing help, just lacked experience with this phone.
We were thinking that we could push recovery from ADB but couldn't get the command lines to work.
Tried these lines so far..
" fastboot flash recovery recovery-clockwork-2.5.0.1-bravo-slcd.img "
resulted in this error
sending 'recovery' (4230 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.000s
so we tried this line
fastboot boot recovery recovery-clockwork-2.5.0.1-bravo-slcd.img
and then
fastboot boot recovery-clockwork-2.5.0.1-bravo-slcd.img
which resulted in
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
could someone give me command lines to push recovery to the phone?
Or if needed an alternate out.. probably using ADB me thinks

as a side note, yes I've searched and yes I've tried other things. But none of the answers work. For some reason ADB doesn't recognize my device as being there, but when I search through fastboot it does... just get those error messages. Hoping a genius sees this and knows the issue

Related

Botched my old recovery, and can't flash a new one...help?

I've been playing around with some of the JB ROMs, and was using Goo Manager and TWRP to do it. Then, because I'm an idiot, I decided I wanted to upgrade TWRP to 2.3.3.0 (I think I was running 2.3.1.0).
That's when I ran into the "TWRP doesn't always install properly" problem. I've now tried updating TWRP from within Goo Manager more than 5 times, but it's not working.
So I decided I'd install the new recovery via the FASTBOOT method.
I have HBOOT 0.92. I have ADB and FASTBOOT loaded on my laptop. (I'm pretty sure this is the way I originally installed CWM 5.0.2.0 when I first rooted my phone ages ago.)
When I boot the phone into the bootloader and choose FASTBOOT, then plug it into my laptop, I get the "FASTBOOT USB" indication that it's connected, so that's good.
However, when I open a terminal window on my laptop, navigate to my miniadb folder (where the fastboot.exe and recovery images are located), and try to flash the recovery image, I see the green bar in the upper right corner of the phone, but on the laptop I get this:
c:\miniadb>fastboot flash recovery openrecovery-twrp-2.3.3.0-inc.img
sending 'recovery' (3642 KB)... OKAY [ 11.235s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 11.268s
So then I decided to give up on TWRP and go back to CWM, but there's no joy there, either:
c:\miniadb>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 12.370s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 12.402s
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Does anyone have a suggestion for a foolproof way to get a recovery (either CWM or TWRP--at this point, I'm not picky!) back on my phone?
Thanks!
MC
Check the last two pages of the tarp thread for a twrp hboot PB31IMG.ZIP or see my direct link below.
http://goo.im/devs/tiny4579/mods/PB31IMG-TWRP-2.3.3.0.zip
This method works without fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Many thanks, tiny! I'll give that a shot.
MysticCobra said:
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Click to expand...
Click to collapse
For what it's worth, I think you need to upgrade HBOOT to 1.02 or 1.07 and unlock it through htcdev to be able to use the fastboot flash commands. But the flashable zip for TWRP should fix it for you too and that way is easier and just as reliable.

I get 1/2 of the command line

Pixel C that was running 8.xx
I thought everything was going good.
I pushed twrp-3.0.0-0-dragon-ryu-02112016-1.img and it said completed. I had SR3-SuperSU-v2.82-SR3-20170813133244.zip on the tablet and thought I was going to boot into recovery and flash the zip and be done.
For about 4 hours I have been trying to get back to any screen. I can still flash in fastboot. I have read a ton of threads that show me why I get this black screen that says Command on it.
I downloaded
ryu-n2g48c-factory-0bc0ee15.zip
ryu-opr1.170623.026-factory-e27ff2c8
ryu-opr6.170623.010-factory-81a1479d.zip
ryu-ota-opr1.170623.026-0f2fd8de.zip
and in fastboot where it sees the phone I get this:
error: cannot open 'bootloader-dragon-google_smaug.7900.67.0.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-ryu-opr1.170623.026.zip': No such file or directory
Press any key to exit...
I am at a loss now. I only get 1/2 of the command word and 1/2 of the picture and then it shuts off. Any Ideas?
--------------------- **update
II relocked my boot.
I have a new menu
android recovery.-- google/ryu/dragon/8.0.0/opr1.176023.026/4286349
i tried to mount system and it says......... e:failed to mount/system invalid agument.

Question I bricked my phone, any advice?

So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b

Question Help! Redmi note 8 (2021) bricked (bootloop)

Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.
you only need to flash the original boot.img from firmware lol it's so easy

Coming back to an old problem

Hello,
Many many many moons ago i decided to try install LineageOS on my old pixel c, then the world when weird and the tablet has lived in a drawer, today it came out and i can't remember where i got up to so looking for guidance before i kill it.
This is what i do know:-
1. Doesn't have an OS as it won't boot properly
2. Get to a recovery menu but trying to boot to "Android recovery" doesn't work (just reboots)
3. Message in the recovery menu states "OS on your tablet is damaged. Needs Recovery" this is along side the Product name, Hardware Version, Bootloader Version and Lock State.
And advice on where to start very much appreciated.
I took another punt at this, tablet is "waiting for fastboot command...." from my mac when attempting to write the recovery image using the following: ./fastboot flash recovery twrp-3.7.0_9-1-dragon.img from my Mac i hit the following error:-
Sending 'recovery' OKAY
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: command failed
./fastboot oem unlock says it is unlocked already

Categories

Resources