Develop Bugs

cant go bootloader. bricked desire?

all i got now is desire which i cant put in bootloader mode
prehistory is unknown
when i press power, power + vol down or power + back i got black screen with htc in center and 4 exclamation signs at corners
what could i do now?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you get into fastboot? You get there by pressing and holding first back and then power button.

as i said before, it shows only the image above on every key combo

turn it off, plug it in via usb, hold back and power
if you know where your fastboot.exe is then cd into the path in cmd.
if you don't then unzip my attachment and put it in your c:\ and type these commands
Code:
cd\
fastboot devices
if it gives back a serial then it is not bricked and you can flash a RUU

It will likely not give a signal back on fastboot devices, as it isn't in fastboot, but it wouldn't do that in hboot mode either so you can't use that info for anything.
I've seen a couble of these, and you should still be able to flash a ruu. If it's a gsm desire(you should have a sim-card), download and run the following ruu while it's connected: http://www.htcdev.com/process/legal_download/152(the ruu is the .exe file inside the .rar)

mortenmhp said:
It will likely not give a signal back on fastboot devices, as it isn't in fastboot, but it wouldn't do that in hboot mode either so you can't use that info for anything.
I've seen a couble of these, and you should still be able to flash a ruu. If it's a gsm desire(you should have a sim-card), download and run the following ruu while it's connected: http://www.htcdev.com/process/legal_download/152(the ruu is the .exe file inside the .rar)
Click to expand...
Click to collapse
FYI, when it's in that state it is booted in RUU mode, which is pretty much the same as fastboot.
if you don't believe me, plug your phone in while booted into a rom and type
Code:
adb reboot oem-78
fastboot devices
fastboot getvar boot-mode
***OP LOOK AT MY PREVIOUS POST - AND DON'T BE AFRAID TO ASK FOR HELP***

i tried the official gb ruus, no connection
it detects as HTC Bootloader in my xpsp3

aZzz.bZzz said:
i tried the official gb ruus, no connection
it detects as HTC Bootloader in my xpsp3
Click to expand...
Click to collapse
Did you try what I said in the first post?

ive finally been able to flash it with official gingerbread ruu from the link given by mortenmhp
it ran without errors
but after reboot its stuck on infinite loop: white htc screen, then vibra and reboot
it now enters fastboot, shows all info, but doesnt enter recovery
any ideas?

aZzz.bZzz said:
ive finally been able to flash it with official gingerbread ruu from the link given by mortenmhp
it ran without errors
but after reboot its stuck on infinite loop: white htc screen, then vibra and reboot
it now enters fastboot, shows all info, but doesnt enter recovery
any ideas?
Click to expand...
Click to collapse
well, congratulations on following bad advice which has got you in an even worse situation... Nothing much you can do. You're S-ON, and you have an un-overwritable RUU (unless a newer one comes out). Can try to flash it again but whether that works is anyone's guess.

Why it doesn't boot now? What's wrong
Sent from my MB860 using Tapatalk

Good question.. that could be anyone's guess!

fastboot flash problem

My phone is arc and I installed like this.
1. Xperia Arc S
2. Super Jelly Bean 2.0
But I tried to install fxp209 for easy updating, but I could not flash boot.img.
ths adb driver installed as this picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I tried to install kernel as this.
but the message is only "flashing...", and not end it.
Please let me know what's problem.
Thanks in advance.

Default fastboot flash problem
First question is your bootloader unlocked!!
If yes try flashing like below
How to fastboot a kernel
(1) Download kernel .boot img place in folder Windows/Flashtool/Firmware
View attachment 1787067
(2) Press lightening bolt
(3) Select Fastboot mode
(4) Connect phone in Fastboot mode (Hold Menu Button ) then connect your phone to pc
(5) Choose select kernel to flash in Fastboot on pc
(6) Wait -until finished 10 seconds tops
(7) Done! switch phone on boot to cwm wait for vibrate/blue light press down/up/or back button depending on kernel or age of phone
Also try booting into fasboot manually as above (step 4)
Also if the fxp kernel not working try another compatible kernel there is plenty in the forum

First question is your bootloader unlocked!!
Click to expand...
Click to collapse
He is using CM10 based ROM so I think his bootloader must be unlocked.
To OP: You can try to flash a kernel with a fastboot and CMD like a real man ; D. Google how to use fastboot.

pypcier said:
He is using CM10 based ROM so I think his bootloader must be unlocked.
To OP: You can try to flash a kernel with a fastboot and CMD like a real man ; D. Google how to use fastboot.
Click to expand...
Click to collapse
Lol I knew that But believe me I have seen people try to flash cm based rom's/kernels with locked bootloaders that's why I never presume it is unlocked unless they have stated it in the post that it is unlocked :good:

My phone is "bootloader unlocked".
And I tried to flash at command line, but it didn't finished.

The correct command is fastboot flash boot kernelname.img See the link in my sig for more help.

XperienceD said:
The correct command is fastboot flash boot kernelname.img See the link in my sig for more help.
Click to expand...
Click to collapse
Yes, I did "fastboot.exe flash boot boot.img".

Try again without an .exe extension. Just type fastboot flash boot kernel.img

After command "fastboot flash boot kernelname.img", command line shows;
sending 'boot' <6430 KB>....
Click to expand...
Click to collapse

That's how it's supposed to be. Show us the rest of CMD content after typing that command.

d816w dual-sim wiped , cannot acces recovery

Hy guys,
my 16 years boy make a full wiped on devices.
the device is stuck in fastboot but cannot acces recovery and is not synchronized with my pc.
when i push hboot and select recovery is suddenly go back into fastboot
i try many different methods to flash recovery with adb devices but list attached is empty and the adb drivers are installed on device manager android usb devices ( My htc )
can somebody give my some advice with this ?
tnx in advance.
Regards

ADB fastboot folder (just extract it to C:\ and you're good to go)
- Connect your device and PC using usb data cable
Step 1
Flashing recovery (before relocking your bootloader)
- Download recovery.img
- Save it to C:\ADB folder
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window' here
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
adb reboot fastboot
to reboot your device. It should start in fastboot mode. If it's not, shut down your phone and restart using power + volume down buttons, pressed at the same time. Once Hboot starts just navigate (using volume up or volume down buttons on your device) to Fastboot and press the power button. Make sure FASTBOOT USB is displayed under your specs.
- Enter
Code:
fastboot flash recovery recovery.img
into the cmd window and press enter to flash your recovery.
- If it's successful go to step 2, if it's not try again.
Step 2
Relock Bootloader using Fastboot:
Now you need to relock the bootloader, otherwise the Stock RUU can't be installed.
- Copy command to the cmd window
Code:
fastboot oem lock
- Press enter
Your device should now be relocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then just place your stock RUU on an sd card, start in bootloader and select Fastboot. Your device should pick the file up as an update and flash on its own.

How do I sideload?

I have ADB installed, Android SDK.
I've tried to sideload and I get the error message "can't read".
Should I be changing the directory in terminal?
This is frustrating.
Thanks.

Anyone? Lol

koooba said:
Anyone? Lol
Click to expand...
Click to collapse
Is your phone coming up after using the command ADB devices?
What are you trying to sideload

No for whatever reason it's not.
I have the drivers installed, debugging on phone set.
Didn't list when I type advice devices.
What directory should terminal be in?
Wondering if I'm in the wrong directory perhaps?
Thanks

ADB could be anywhere and it'll work, double check the drivers and make sure the ADB drivers are installed and not just the MTP drivers.
What are you sideloading btw?

ADB can be anywhere, okay good to know. Thanks.
I'm trying to sideload Oxygen 3.2.1 since I'm having microphone issues - people can't hear me sometimes or my voice gets all messed up.
Apparently sideloading this update fixes this issue, at least for a few people it did.
When I connect the phone to the computer in regular mode, the device is listed.
When I go into RECOVERY mode with the phone, the computer doesn't find the device at all.
I'm going by the OnePlus instructions to turn it off and go into this mode.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.1/

unlock bootloader
install twrp
make Nandroid Backup
download FreedomOS 3.2.1
move to phone
Wipe Caches and system, no need to wipe data (in TWRP)
Install FreedomOS ( u may need to redownload SU and flash manually if not working in FreedomOS Aroma)
Done... If still issues do a clean flash, go to twrp and Advance Wipe (Caches, Data, System) DO NOT DO STORAGE!!!!
No this will not Void your warranty with OnePlus
Click here for better instructions

Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????

koooba said:
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
Click to expand...
Click to collapse
what drivers did u install, so when u type "adb devices" nothing at all comes up?

I installed the drivers that are on the phone when you plug it in.
When the phone is on and plugged into the computer, it recognizes it.
This is what I get -> http://imgur.com/B3a8AMg
When I turn it off and plug it in, it recognizes the device.
When I'm in recovery mode, it doesn't recognize it at all.

i am not sure how stock recovery works, but if u are in fastboot mode, does it recognize?
with it unathurized that means u did not check the box on the phone when plugged in to ur computer.... u should get this on your phone when booted into the OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i would try to boot into fastboot mode and push the file to ur phone and install via zip in stock recovery
and try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118

I checked that box off, yes.
I'm about to give up, now it's not even showing a "storage" folder at all when plugged in.
Cannot even copy files into the phone, no storage showing.
OP, so many problems and it's only 4 days old.

anyone, please

Question Can i install android 12 gsi on my Samsung a52s 5g?

Hello good morning
I have been trying to install android 12 gsi on my a52s 5g via ADB for some time. I know that my phone already has the android 12 update but I would still like to try android 12 gsi.
I have already unlocked the bootloader and installed all the necessary drivers.
I have USB debugging and OEM mode enabled.
When I enter ADB and want to enter the command "fastboot reboot fastboot" I get the following message below the command: C:\ADB>fastboot reboot fastboot
< waiting for any device >
And when I try to enter fastboot through recovery, it restarts the phone. I have also tried with the "reboot recovery" command but still not successful.
Since then I have not been able to continue with the steps. I have already granted the usb debugging permissions and everything necessary so right now I don't know what to do.
Any solution to the problem????
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mrjacobosuper said:
Hello good morning
I have been trying to install android 12 gsi on my a52s 5g via ADB for some time. I know that my phone already has the android 12 update but I would still like to try android 12 gsi.
I have already unlocked the bootloader and installed all the necessary drivers.
I have USB debugging and OEM mode enabled.
When I enter ADB and want to enter the command "fastboot reboot fastboot" I get the following message below the command: C:\ADB>fastboot reboot fastboot
< waiting for any device >
And when I try to enter fastboot through recovery, it restarts the phone. I have also tried with the "reboot recovery" command but still not successful.
Since then I have not been able to continue with the steps. I have already granted the usb debugging permissions and everything necessary so right now I don't know what to do.
Any solution to the problem????
View attachment 5661025
Click to expand...
Click to collapse
Do you have a recovery with fastboot installed on your phone? I got into fastboot with: adb reboot fastboot (enter)

bobfrantic said:
Do you have a recovery with fastboot installed on your phone? I got into fastboot with: adb reboot fastboot (enter)
Click to expand...
Click to collapse
No, but already tried the "Adb Reboot Fastboot" command and yet the only thing it does is restart the phone

mrjacobosuper said:
No, but already tried the "Adb Reboot Fastboot" command and yet the only thing it does is restart the phone
Click to expand...
Click to collapse
for it to work you need to have the recovery with fastboot in it. try pushing this to your phone with adb... but doso at your own risk, i accept no responsibilty if it causes a soft brick or anything else on your phone. it is the recovery that is on my phone though so should be alright. Make sure it is for the A52s 5G.