[Q] Help Desire Z stuck on HTC screeen and ADB not recognize - G2 and Desire Z Q&A, Help & Troubleshooting

I lose my rooting access after installed custom ROM Honeycomb
then i tried to root my device with this tuttorial
[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)
but after that my device stuck on HTC logo
entering fastboot mode I got this
Code:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Aug 20 2010,16:51:01
SD Checking...
Loading.. [PC10DIAG.zip]
No image!
Loading.. [PC10DIAG.nbh]
No image or wrong image
Loading.. [PC10IMG.zip]
Lack of heap!
Loading.. [PC10IMG.nbh]
No image or wrong image
this is the result on cmd
{
"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"
}
the first offline result when i'm on recovery mode
and the next is on fastboot mode
why is adb won't recognize my device? and what i have to do to fix my device?
please help

diothero said:
I lose my rooting access after installed custom ROM Honeycomb
then i tried to root my device with this tuttorial
[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)
but after that my device stuck on HTC logo
entering fastboot mode I got this
Code:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Aug 20 2010,16:51:01
SD Checking...
Loading.. [PC10DIAG.zip]
No image!
Loading.. [PC10DIAG.nbh]
No image or wrong image
Loading.. [PC10IMG.zip]
Lack of heap!
Loading.. [PC10IMG.nbh]
No image or wrong image
this is the result on cmd
the first offline result when i'm on recovery mode
and the next is on fastboot mode
why is adb won't recognize my device? and what i have to do to fix my device?
please help
Click to expand...
Click to collapse
Beli hp baru aja oi

Flashing a custom rom should not lose you root access.
Have you tried rebooting the phone and seeing if that works in adb?
Also, when its in fastboot mode, adb won't recognize it. You have to use fastboot.exe (which might be in your tools/platform-tools folder).
Try 'fastboot devices' when your connected in fastboot mode to see if it reads.
Seeing as you have the eng hboot, you should be able to recover the phone from whatever state its in.
-Nipqer

Related

[Q] Flashing firmware error

A friend of mine has a CID 044 and still got ICS since his Bootloader is already unlocked and he doesn't get OTAs
So, he tried to install the Jelly bean firmware from here: http://forum.xda-developers.com/showthread.php?t=1957376
and while writing the commands he ran into a problem, thats what he said happened:
After he wrote the first command [fastboot oem rebootRUU] the phone rebooted into the HTC logo and got stuck there, so he rebooted it again and it rebooted as usual
Then he got it back to fastboot USB, wrote the second command and this is what he got:
{
"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"
}
Anyone knows whats wrong?
You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).
hopscotchjunkie said:
You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).
Click to expand...
Click to collapse
Hey, im his friend with the firmware problem.
I did as you said (did it more then twice) and got the next problem:
I cant post photoes here so i'll just copy it
c:\fastboot>fastboot flash zip firmware.zip
sending 'zip' <12875 KB>...
OKAY [ 1.672s]
writing 'zip'...
<bootloader> adopting the signature contained in this image...
FAILED <remote: 99 unknown fail>
finished. total time: 2.281s
Click to expand...
Click to collapse
Any chance you know whats the problem is?
Thanks alot
1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.
hopscotchjunkie said:
1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.
Click to expand...
Click to collapse
1. copyed from where i downloaded
x.xx.707.x - Asia WWE (World Wide English)
cidnum: HTC__044
Download:
firmware.zip with hboot 1.36
2. I didnt relock my bootloader before starting,
Now it finnaly worked, but it stuck on the black screen with the htc logo, and it added like a green loading bar that showed that it had finished loading but still stuck on this screen.
Should I wait for something to happend or reboot manually?
Reboot manually (use 'fastboot reboot-bootloader' to get back into the bootloader and unlock it again)

back to stock sense

i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
{
"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"
}
nassimxmax said:
i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
Click to expand...
Click to collapse
umm that doesnt really help, whats your fastboot getvar all, whats rom did you try to flash, your flash commands are all wrong but require the other info in order to see what your doing.
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
nassimxmax said:
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
Click to expand...
Click to collapse
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Seanie280672 said:
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Click to expand...
Click to collapse
thank you so much i trying to find that htc fastboot but i didin't find it
i understand now i will try
now it work fine
just waiting ^^

need help! accidentally flashed twrp.img as boot, now phone shows that it's destroyed

Hi guys, i really need help here.
i wanted to flash and install TWRP.img on my redmi note 8 today, but i accidentally used the cmd command fastboot flash boot TWRP.img .
my phone then only boots to TWRP instead of my usual MIUI. so i tried flashing the whole note 8 rom using MiFlashTool. However, there is a error (error:Mismatching image and device), and now my phone only shows me that "the system has been destroyed".
when i tried to flash another boot.img to the phone, it shows "FAILED (command write failed (unknown error))"
{
"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"
}
anyone know what i should do to fix this phone? will really appreciate any help... :crying:
I don't know if you can enter to fastboot mode (power + vol down button). If you can, you can try fastboot flash recovery TWRP.img and search for boot.img at Google I think....
---------- Post added at 23:41 ---------- Previous post was at 23:36 ----------
I think this may helps: https://c.mi.com/thread-2542493-1-0.html
I think that the key is to get boot.img (miui or custom rom) from installation zip and flash it again to the phone via fastboot
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
I got the same message even when trying to boot into recovery, even flashing the recovery again didn't work, so I downloaded The stock rom uncompressed and flashed each img manually with fastboot
Leeban Joseph said:
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
Click to expand...
Click to collapse
This is the right solution
Dont worry you phone isnot destroyed ,just fellow these instructions
Hello Community!
I unlocked my 7 days old REDMI NOTE 8 with MI UNLOCK. All fine.
Then I Boot into Fastboot-mode and flashed TWRP.IMG (twrp-3.3.1-0-ginkgo.img) and started into TWRP (Recovery). On internal drive i copied new XIAOMI.EU, deleted all data. Take a reboot into Recovery, too.
But now I get "Message THE SYSTEM hat been destroyed".
MI UNLOCK SAYs UNLOCK no Nessesary. Is unlocked.
I COULD NOT BOOT INTO TWRP after Flashing TWRP.IMG
Devicecheck:
d:\platform-toolsfastboot devices
130fd5f2 fastboot
Writing TWRP is possible:
d:\platform-toolsfastboot flash recovery twrp.imgSending 'recovery' (65536 KB) OKAY [ 1.673s]
Writing 'recovery' OKAY [ 0.287s]
Finished. Total time: 1.980s
Command CONTINUE:
d:\platform-toolsfastboot continue
resuming boot FAILED (status read failed (Too many links))
Finished. Total time: 30.073s
Can Someone help me, please?
Many Thanks!
I tried to flash with MI Flash (Fastboot.rom)
ginkgo_global_images_V11.0.3.0.PCOMIXM_20191119.0000.00_9.0_global_a8923e1765.tgz
Now I am back to Stock!
Thank you!

Vivo V7+ bootloader unlock FAILED (remote: unlock fail.)

Lately, after using this separate phone(Vivo V7+) for 2 years, I've been trying to root it.
The basic drill I found to root this phone is,
- Unlock bootloader
- Install TWRP
- Root it using Magisk/SuperSU
I've tried most of the methods mentioned online to unlock the bootloader,
While trying to unlock it using vivo fastboot, An error occurs.
Command: fastboot bbk unlock_vivo
Result: FAILED (remote: unlock fail.)
Another command: fastboot oem unlock
Result: FAILED (remote: unknown command or device is lock)
When rebooting device into fastboot using: adb reboot-bootloader the developer option, oem unlock & usb debugging all was turned all.
{
"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"
}
Much help appreciated, Thank You.
Re
vedantspeed7 said:
Lately, after using this separate phone(Vivo V7+) for 2 years, I've been trying to root it.
The basic drill I found to root this phone is,
- Unlock bootloader
- Install TWRP
- Root it using Magisk/SuperSU
I've tried most of the methods mentioned online to unlock the bootloader,
While trying to unlock it using vivo fastboot, An error occurs.
Command: fastboot bbk unlock_vivo
Result: FAILED (remote: unlock fail.)
Another command: fastboot oem unlock
Result: FAILED (remote: unknown command or device is lock)
When rebooting device into fastboot using: adb reboot-bootloader the developer option, oem unlock & usb debugging all was turned all.
Much help appreciated, Thank You.
Click to expand...
Click to collapse
I am facing the same issue.
V7+ bootloader unlock failed adb fastboot
Please help me to unlock bootloader
I have same issue to unlock the bootloader for vivo
I typed the methods, and it's not working
People said for new phones use this command: fastboot bbk vivo_bsp unlock_vivo
But I tried that to my new vivo phone and it's not working also
I'm thinking that people who failed need unlocking bootloader tools or download firmware of the vivo and remove bootloader (Make sure the stock firmware must have higher version, and your phone not updated)
Note: people have to downgrade to low version of vivo if they want the cmd method(if still not working)
If you are facing the bootloader issue in you device thenclick here to take guide about it because some months ago I also faced this issue and this platform helped me on that time.

Plz help - trying to flash Stock image from Google

Hi all,
Just wondering if anyone might be able to lend a hand... Im trying to flash back my Pixel C back to stock (currently running TWRP and build from [ROM][UNOFFICIAL][LineageOS]18.
For some reason, when running the flash-all script or manually flashing the Booloader img, it comes back with "writing 'bootloader' failed (remote 'unsupported command')".
The tablet still boots into the Lineage OS (at least its not a brick... yet..) but really like to try and get it back to stock if I can..
if it helps..
{
"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"
}
When running the flash-all bat file:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
See also:
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command" Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock I used TWRP and SuperSU to root and modify the buildprops to enable and get...
forum.xda-developers.com
bernardomarx said:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Thanks bernardomarx! That seemed to have done the trick!!
Yeah - Luckily TWRP recovery was still accessable, typed in the command within TWRP Terminal. And followed the post you linked to
Essentially after doing the fwtool command in a cmd window:
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
Flashed the bootloader:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
I then had to extract the img zip file and manually flash each img file:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
>fastboot flash vendor vendor.img
Many thanks for entering the details of how you recovered your Pixel C. I had the same problem when un-installing TWRP. I did performed the same steps as you, and the tablet is back up and running!
Many thanks for documenting it here!

Categories

Resources