Related
Hi
My HTC has a white screen when it starts and it says HTC in green on it and doesn't advance from there.
I was trying to root my phone and I messed up.
I installed the wrong PG58IMG file and it used to enter in a reboot loop (reboot, show screen, reboot, show screen..etc)
So I screwed up more by entering recovery mode(Volume down + Power) and I formated all the things that were in the list, including System and Data.
So I think it was because I formatted system. Now my issue is that I can only see a blank screen
My phone is not detected by the computer, either is the sd card using a memory card reader.
My phone enters in a white screen and stays there, so (volume down + power) doesn't work.
What should I do?
Any help will be appreciated.
PandaBoy7 said:
Hi
My HTC has a white screen when it starts and it says HTC in green on it and doesn't advance from there.
I was trying to root my phone and I messed up.
I installed the wrong PG58IMG file and it used to enter in a reboot loop (reboot, show screen, reboot, show screen..etc)
So I screwed up more by entering recovery mode(Volume down + Power) and I formated all the things that were in the list, including System and Data.
So I think it was because I formatted system. Now my issue is that I can only see a blank screen
My phone is not detected by the computer, either is the sd card using a memory card reader.
My phone enters in a white screen and stays there, so (volume down + power) doesn't work.
What should I do?
Any help will be appreciated.
Click to expand...
Click to collapse
It sounds as if you installed a boot.img or kernel, i believe that you should be able to get into recovery though, ensure the phone is entirely off by holding the power button until the bottom backlit keys flash and the phone shuts off, then try to get to recovery again, if you do manage to get this far, I would recommend immediately factory wiping/having an additional boot.img ready to flash to remove the current unstable one.\\
remember to hit thanks!
PandaBoy7 said:
Hi
My HTC has a white screen when it starts and it says HTC in green on it and doesn't advance from there.
I was trying to root my phone and I messed up.
I installed the wrong PG58IMG file and it used to enter in a reboot loop (reboot, show screen, reboot, show screen..etc)
So I screwed up more by entering recovery mode(Volume down + Power) and I formated all the things that were in the list, including System and Data.
So I think it was because I formatted system. Now my issue is that I can only see a blank screen
My phone is not detected by the computer, either is the sd card using a memory card reader.
My phone enters in a white screen and stays there, so (volume down + power) doesn't work.
What should I do?
Any help will be appreciated.
Click to expand...
Click to collapse
You now have an "empty" phone in your hands. If you still can go into recovery by holding the power + vol-down keys, download and flash latest CWM recovery (5.8.4.0) first with the following command from your PC's dos prompt where you have the needed fastboot files:
fastboot flash recovery <name of the recovery file>.img
Once you flash 5.8.4.0, go into recovery, go into mounts/storage and mount your sdcard partition from there. Now, you should be able to see your phone from your PC. Copy your choice of ROM's zip file to your phone using
adb push <name of your rom>.zip /sdcard
Once you have the zip on the sdcard, you are ready to flash the boot.img of the ROM. Extract the boot.img file from the ROM.zip to the directory where you have the fastboot files and issue this command from cmd prompt to reboot into bootloader
adb reboot-bootloader
When the phone goes into bootlader, go into fastboot (if not already in fastboot). You will see Fastboot USB shown on the phone and issue from PC
fastboot flash boot <name of boot image file>.img
fastboot erase cache
fastboot reboot-bootloader
Again in bootloader on the phone, select recovery. In recovery, select apply zip from SDcard, choose zip, and select your ROM.zip file. Flash it.
Now you should have your phone with boot image and rom and ready to boot. First boot may take some time. Good luck.
eyosen said:
You now have an "empty" phone in your hands. If you still can go into recovery by holding the power + vol-down keys, download and flash latest CWM recovery (5.8.4.0) first with the following command from your PC's dos prompt where you have the needed fastboot files:
fastboot flash recovery <name of the recovery file>.img
Once you flash 5.8.4.0, go into recovery, go into mounts/storage and mount your sdcard partition from there. Now, you should be able to see your phone from your PC. Copy your choice of ROM's zip file to your phone using
adb push <name of your rom>.zip /sdcard
Once you have the zip on the sdcard, you are ready to flash the boot.img of the ROM. Extract the boot.img file from the ROM.zip to the directory where you have the fastboot files and issue this command from cmd prompt to reboot into bootloader
adb reboot-bootloader
When the phone goes into bootlader, go into fastboot (if not already in fastboot). You will see Fastboot USB shown on the phone and issue from PC
fastboot flash boot <name of boot image file>.img
fastboot erase cache
fastboot reboot-bootloader
Again in bootloader on the phone, select recovery. In recovery, select apply zip from SDcard, choose zip, and select your ROM.zip file. Flash it.
Now you should have your phone with boot image and rom and ready to boot. First boot may take some time. Good luck.
Click to expand...
Click to collapse
Hi
I tried doing fastboot flash recovery <name of the recovery file>.img from the sdk/tools folder in my windows.
But I get this message:
sending 'recovery' <4618 KB>... OKAY [1.5808 s]
writing 'recovery' ... FAILED <remote: not allowed>
finished. total time: 1.827s
I've placed the .img file in the sdk/tool folder and I'm running the command from that folder.
What am I missing?
PandaBoy7 said:
Hi
I tried doing fastboot flash recovery <name of the recovery file>.img from the sdk/tools folder in my windows.
But I get this message:
sending 'recovery' <4618 KB>... OKAY [1.5808 s]
writing 'recovery' ... FAILED <remote: not allowed>
finished. total time: 1.827s
I've placed the .img file in the sdk/tool folder and I'm running the command from that folder.
What am I missing?
Click to expand...
Click to collapse
Please help, I will appreciate.
I somehow managed to install the recovery image file.
My phone was always searching this PG58IMG.zip file so I put the recovery file in that zip and put it on my sd card.
So the recovery got installed and when I go to recovery/mount/ then mount sdcard on my phone, in my computer something happens like its trying to search and install the drivers, but it ends up in a failed message: "MTP USB device failed"
I don't know what to try now, please I'm desperate.
PS: In the PG58IMG.zip I have many files like radio, boot_signed, tz ..etc all .img files and the hboot version and radio version are back to the correct one.
But it still doesnt work
Hi there,
I have a rooted HTC one M8 in Australia and I'm trying to flash stock recovery with fastboot in command centre. I'm having a problem because it keeps failing to flash the recovery as its more than 18mb and the command centre says "target reported max download size of 1830477824"
Is there a way to make the max file size bigger? so i can flash stock recovery, update the phone and then flash TWRP again?
Im a beginner so even just a little help would be amazing! THANKS SO MUCH!
What command are you typing?
I'm going to guess they're trying to flash it in RUU mode
BenPope said:
What command are you typing?
Click to expand...
Click to collapse
First they said to open the folder 'fast boot'
right click in folder whilst holding shift and click open command window here
then type 'adb reboot bootloader'
then after its in boot mode i typed in 'fastboot flash recovery "stock recovery.img"
after that it starts trying to send to my phone but then says that max file transfer is 18mb and this stock recovery is 24mb.
Rename stock recovery.img to recovery.img
then use command fastboot flash recovery recovery.img
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 an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
I did everything on https://wiki.lineageos.org/devices/ginkgo/install , I flashed the recovery, on the Prompt I get "okay" to both Sending and Writing, and on "Now reboot into recovery to verify the installation" my phone is still on fastboot, so I press for a long time the power button to (force?) shut down it, use volume_up+power and what I see is the "Redmi-Recovery 3.0" (stock recovery).
Is it possible to have 2 recovery and I simply don't know how to access the LOS one? Maybe I could have more luck installing TWRP and overwriting it with LOS recovery (how to?)?
From fastboot if I write "fastboot reboot recovery" right after "fastboot flash recovery ..." prompt says "Rebooting into recovery...okay" but then the normal OS is loaded.
If I use
Code:
adb reboot bootloader
I access to the stock fastboot, and from there
Code:
fastboot boot recoveryimagename.img
says
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
. If I use it from MIUI-OS:
Code:
< waiting for any device >
and Prompt is waiting there.
I have fastboot and recovery image in the same folder but with
Code:
fastboot flash recovery *recovery*
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
, infact I used full path (full of the img file, not the adb/fastboot which I properly installed) instead of relative, giving the "okay", and after that with
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
!
Only now I've seen I was writing from root Prompt and therefore from "C:\WINDOWS\system32>", I used "cd platform-tools_path" and (after
Code:
fastboot flash recovery lineage-17.1-20201228-recovery-ginkgo.img
)
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
worked, but now the phone is stuck here!! From prompt everything seems ok. The phone is stuck on the normal loading boot after that "fastboot boot..."! Before I even tried installing TWRP...maybe that was too much? Now?
I used again "fastboot boot lineage-17.1-20201228-recovery-ginkgo.img" and it seems to working...maybe in a couple of minutes(hours probably) I'll mark this as solved!
Ok, I think everything is good now, but I have a question: is it possible to have more than one recovery installed?
BEDBOI2 said:
is it possible to have more than one recovery installed?
Click to expand...
Click to collapse
it is possible on other devices, but until now not possible on ginkgo
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.