HI,
When press power on phone shows "HTC " logo than goes to black screen,
I can go to hboot menu but whenever I press recovery option, black screen comes again and no recovery menu. I also try to install recovery via adb but result is same.
Code:
C:\Android\android-sdk\platfo
sending 'recovery' (3182 KB).
OKAY [ 2.391s]
writing 'recovery'...
OKAY [ 2.844s]
finished. total time: 5.234s
This phone is unlock bootloader with htcdev and have hboot version 1.10.0000
Any tips or suggestion will be highly appreciated.
thanks
br
Seniors, need your help urgent ....
I would download adlx's recovery again and flash it via fastboot with this command:
fastboot flash recovery recovery.img
Maybe you used wrong recovery, size looks a bit small to me...
Related
Hi,
I am trying to install cwm recovery through fastboot but consistently this error arising.
<bootloader> Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' <8480 KB>...
OKAY [ 0.700s]
writing 'recovery'...
OKAY [ 2.219s]
finished. total time: 2.929s
after this when I go to recovery the screen remains black.
can anybody please help me regarding this issue that how could I flash custom recovery through fastboot.
Thanx.
This is normal (sort of) for KKBL recoveries -- it's a screen dimming issue; if you're using PhilZ the "fix" is to use the following:
- middle of screen; swipe left-to-right twice
- middle of screen; swipe right-to-left twice
- push a volume up or down button
Screen should come alive.
This affected TWRP too but I don't use it so not sure if there's a similar workaround.
I am not using Philz, using CWM Recovery 6.0.4.9.
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
hashims said:
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
Click to expand...
Click to collapse
I think when you flash a recovery and you boot into android, android overwrites the custom recovery with the stock one. Try to boot to recovery without booting in android.
I have an old HTC ONE S (z560e => S3 CPU as I now know).
1) I managed to unlock the boot loader (htcdev)
2) Probably managed to get root access (r3-ville-superboot was fast and error free)
3) However them "recovery install apps" (CWM, TWRP) still clamied they'd need root
access but "superuser or su are not to be found"; weird, considering success of 2)
4) hence I tried to flash twrp recovery manually via
Code:
fastboot.exe flash recovery twrp-3.0.0-0-ville.img
message was
Code:
sending 'recovery' (11896 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 3.845s]
finished. total time: 5.931s
And that's it. won't boot anymore. I apparently got the S4 version of twrp-3.0...
Holding in power button for ~10 secs has it very shortly flash the screen and turn on the oragne LED for ~4 secs, then it's black again.
Any idea what went wrong?
Any chance how to save that situation?
Hi. I was following the instruction<oneplusDOTgadgethacksDOTcom/how-to/update-your-oneplus-7-pro-without-losing-root-no-computer-needed-0208078> to upgrade the os on the pro. One step is to install TWRP. I followed the instruction<twrpDOTme/oneplus/oneplus7proDOThtml> and run "fastboot boot twrp-xxxx.img". It finished and my phone displayed "fastboot mode" and freezed there. I tried to hold the power button and hold power button & volume down button. Neither worked. Aappreciate any help.
I only have a macbook pro.
Log:
> fastboot boot twrp-xxxx.img
< waiting for any device >
Sending 'boot.img' (31704 KB) OKAY [ 0.682s]
Booting OKAY [ 0.121s]
Finished. Total time: 0.868s
screenshot: i.ibb.co/pRtwJ4L/IMG-1533.jpg
buy pc
other solution is maybe to use usb2.
superflb said:
Hi. I was following the instruction<oneplusDOTgadgethacksDOTcom/how-to/update-your-oneplus-7-pro-without-losing-root-no-computer-needed-0208078> to upgrade the os on the pro. One step is to install TWRP. I followed the instruction<twrpDOTme/oneplus/oneplus7proDOThtml> and run "fastboot boot twrp-xxxx.img". It finished and my phone displayed "fastboot mode" and freezed there. I tried to hold the power button and hold power button & volume down button. Neither worked. Aappreciate any help.
I only have a macbook pro.
Log:
> fastboot boot twrp-xxxx.img
< waiting for any device >
Sending 'boot.img' (31704 KB) OKAY [ 0.682s]
Booting OKAY [ 0.121s]
Finished. Total time: 0.868s
screenshot: i.ibb.co/pRtwJ4L/IMG-1533.jpg
Click to expand...
Click to collapse
You can upgrade the is without twrp,just go for local upgrade in updater app.
Also the terminal should show downloading boot.img message which is not shown in your case and it is evident that something is wrong.
Mess around a bit and you will figure it out
Hey guys.
I'm having trouble to come forward booting my device with TWRP on my Sony Xperia XZ1 Compact (G8441) using a MacOSX.
Additional info to the phone:
version-baseband:1307-7511_47.2.A.11.228
version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
Steps I did:
Unlocking the bootloader (worked)
Flashing with TWRP from Androidfilehost (here) with:
Code:
./fastboot flash recovery TWRP.img
I've used Android 9.0 twrp-3.3.1-0-lilac-pie-5.img as TWRP.img
It gives me:
Code:
./fastboot flash recovery TWRP.imgSending 'recovery' (34548 KB) OKAY [ 0.750s]
Writing 'recovery' OKAY [ 0.262s]
Finished. Total time: 1.016s
Booting with TWRP:
Code:
./fastboot boot TWRP.img
Sending 'boot.img' (34548 KB) OKAY [ 0.749s]
Booting OKAY [ 5.742s]
After step #3 the phone gets stuck on the Splash screen showing "SONY" (blue LED light on)
Rebooting into normal mode using Volume-Up + Power also gives me a similar outcome leaving the phone stuck on the "XPERIA" screen.
I've read somewhere in this forum that a possible solution could be to format the cache and user data which gives me:
Code:
./fastboot format cache
/Applications/Android/./mke2fs failed with status 1
fastboot: error: Cannot generate image for cache
And a similar one for user data.
Does anyone of you have a clue what I did wrong and what I need to do next to solve it? Every constructive comment is much appreciated.
Best
EDIT:
I could get it running and were able to install lineage-17.1-20201217-UNOFFICIAL-v1.7-lilac from here (androidfilehost.com - modpunk).
It was working to get into TWRP through unplugging the USB cable. Restarting the phone and directly after it restarts pressing volume up and plugging in the USB again.
Wondering why you try to boot into TWRP when it has already been successfully installed?
Code:
fastboot boot <TWRP.IMG>
is used if TWRP isn't already installed yet.
You should run
Code:
adb devices
adb reboot recovery
instead.