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?
Related
i rooted my tf300 when on stock ics. i used the method that doesnt require bootloader unlocking.
couple of days later the jb ota came along, so installed that, and restored root with voodoo
i want to install a custom rom, but i can't get the recovery working. the tablet boots fine, and the behaviour is the same now im on jb, as it was when on ics
basically, i power on + vol down, then select the rck icon, and it loads to an android with a blue loading animation, then changes to a 'dead' android with a red exclamation just above.
the tablet still boots fine otherwise.
question is, do i have to unlock the bootloader before i can install/run the recovery, or is there a way i can do it without unlocking?
edit: i tried also flashing via fastboot (tried first with terminal, when trying twrp for ics) and this is what it comes back with, same thing for cwm and twrp:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery CWM-Touch.blob
sending 'recovery' (6370 KB)...
OKAY [ 2.646s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 5.901s
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)...
OKAY [ 3.538s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 6.779s
You have to unlock to install a custom rom. Think it over and do some more reading. You could build a house since there is no shortage of bricks. :banghead:
Still Charged Up
do you think there's any chance of being able to do this without unlocking in the future?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Nope. One requires the other. Simply put - ASUS does not want to deal with true user-created bricks. That's why they make it optional.
Still Charged Up
So I wanted to root my One S and install CWM.
What I did was use http://forum.xda-developers.com/showthread.php?t=1604677 this tool, everything went fine. I used the TWRP recovery, it booted fine.
Tried to install CWM, found out my Hboot was too low (think it was 1.14.0.02).
Extracted the hboot.img from the CWM zip, installed it:
C:\Users\aSCO\Desktop\blabla\fastboot flash boot boot.img
sending 'boot' (5688 KB)...
OKAY [ 0.890s]
writing 'boot'...
OKAY [ 1.390s]
finished. total time: 2.280s
then fastboot reboot.
Now the ühone won't turn one, LED doesn't shine when connected to charger. From time to time it turns on, show the HTC screen (with text 'this is a developer version etc'), then turns back off.
Any hope there for me? What did I do wrong?
EDIT: I managed to get into fastboot, what's the best way to go on from here? The Hboot version number is still the same, is there another recommended boot.img that I could flash?
EDIT2: Managed to fix this, cannot find an option to delete the thread ...
CAN BE CLOSED.
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.
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.