Hello, I was on Android Marshmellow 6.0.1 + SU and I made with TWRP a full backup (+TA.img). I wiped:
+Dalwik
+Cache
+Data
+System
+Internal Storage
-Micro SDcard
Then booting into the TRWP 3.1.0.1 revovery did not work anymore (only Sony logo) and I thought I have to flash TWRP again. I used cmd administrator with this commands:
C:\adb>fastboot.exe -i 0x0fce oem unlock 0xxxx640DA639C0xxx
...
OKAY [ 3.281s]
finished. total time: 3.281s
C:\adb>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (13092 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.875s]
finished. total time: 1.422s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.000s
I hold the volume down button and i was able to come into TWRP menu. Problem: I forgot to save my Lineage files on Micro SDcard, so flashing was not possible for me and I made it off (Volup + Power) After copieng with the pc the needed flash files to micro sdcard I tried again booting to TWRP recovery but does still not work. Then I tried some more commands:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.063s]
finished. total time: 0.484s
C:\adb>fastboot reboot
< waiting for any device >
rebooting...
finished. total time: -0.000s
C:\adb>adb ls -h
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
C:\adb>adb shell
error: no devices/emulators found
C:\adb>adb devices
List of devices attached
C:\adb>fastboot devices
YT9119CPJT fastboot
C:\adb>
I´m still in a bootloop and i can not see that my smartphone is charging the battery. At last it saw only 50% in TRWP
and I don´t realy know what I have to do now. Need HELP :crying:
P.S.: I am on Windows 10 home (64 bit) and flashtool-0.9.25.0 told me all drivers was succefuly installed (with Win10 Disable Driver Signature Enforcement) and I used twrp-3.0.2-1-z3c.img
Edit: After some research, I read the battery can not charging, because it's in bootloader mode and i have to flash the stock rom back. I did it succesfully with flashtool
Related
ok I have 2 htc one, I s-off'ed one 6 months ago and its been working fine since then.
but today I tried to s-off the other one may built having hboot 1.44
I got it s-off successfully and unlocked but there are no red warning that your htc one is a development blah blah on the welcome screen
I flashed the twrp recovery 3 times but when I enter the recovery mode first a blue screen appears and then the red triangle with exclamation mark!
note: the custome recovery flashes successfully
also I have used fastboot erase cache also
Just to clear things up: S-off was achieved back in June/early July for Hboot 1.44
Hboot 1.54 S-off was achieved two weeks ago with a different method to the first one.
Hboot 1.44 modified Hboots are available where the red warning flag has been removed, and I guess you put that one on your second One.
gunswordx said:
ok I have 2 htc one, I s-off'ed one 6 months ago and its been working fine since then.
but today I tried to s-off the other one may built having hboot 1.44
I got it s-off successfully and unlocked but there are no red warning that your htc one is a development blah blah on the welcome screen
I flashed the twrp recovery 3 times but when I enter the recovery mode first a blue screen appears and then the red triangle with exclamation mark!
note: the custome recovery flashes successfully
also I have used fastboot erase cache also
Click to expand...
Click to collapse
Bad download? Try to download Twrp again or try CWM rercovery
hardstuffmuc said:
Just to clear things up: S-off was achieved back in June/early July for Hboot 1.44
Hboot 1.54 S-off was achieved two weeks ago with a different method to the first one.
Hboot 1.44 modified Hboots are available where the red warning flag has been removed, and I guess you put that one on your second One.
Click to expand...
Click to collapse
I tried the old revone method(same file I used for the previous one)
also I checked the md5 and have download almost all the versions of twrp. to be sure I even flashed it on my previous one and was working there
I would also try the CWM recovery with
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
and make sure you use a USB 2.0 on your computer. Apparently USB 3.0 may cause problems
hardstuffmuc said:
I would also try the CWM recovery with
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
and make sure you use a USB 2.0 on your computer. Apparently USB 3.0 may cause problems
Click to expand...
Click to collapse
yes tried all the recoveries
the thing is even though fastboot says flashed successfully, the stock recovery is still there !
also i have only usb 2.0
gunswordx said:
yes tried all the recoveries
the thing is even though fastboot says flashed successfully, the stock recovery is still there !
also i have only usb 2.0
Click to expand...
Click to collapse
can you copy/paste the command prompt, including a DIR of the folder, so we can take a look?
251|[email protected]:/data/local/tmp $
c:\ADB>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $ exit
exit
c:\ADB>adb reboot-bootloader
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.825s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.810s
c:\ADB>fastboot flash recovery recovery.img
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.810s
c:\ADB>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
c:\ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.856s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.206s]
writing 'recovery'...
OKAY [ 0.663s]
finished. total time: 1.871s
c:\ADB>fastboot flash recovery recovery-TWRP-newbl.img
sending 'recovery' (7238 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.794s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
c:\ADB>adb reboot-bootloader
c:\ADB>
gunswordx said:
251|[email protected]:/data/local/tmp $
c:\ADB>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $ exit
exit
c:\ADB>adb reboot-bootloader
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.825s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.810s
c:\ADB>fastboot flash recovery recovery.img
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.810s
c:\ADB>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
c:\ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.856s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.206s]
writing 'recovery'...
OKAY [ 0.663s]
finished. total time: 1.871s
c:\ADB>fastboot flash recovery recovery-TWRP-newbl.img
sending 'recovery' (7238 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.794s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
c:\ADB>adb reboot-bootloader
c:\ADB>
Click to expand...
Click to collapse
why use revone again, and why so many flashes?
Just:
adb reboot bootloader (no - needed in adb)
fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader (- is needed in fastboot)
Then just select RECOVERY using VOL Up or Down, press POWER to enter into recovery.
the first time revone didn't work so I had to do it again.
got s-off and super cid
after each recovery flash I rebooted bootloader and went to recovery but same red triangle
that's why so many recovery flashes
gunswordx said:
the first time revone didn't work so I had to do it again.
got s-off and super cid
after each recovery flash I rebooted bootloader and went to recovery but same red triangle
that's why so many recovery flashes
Click to expand...
Click to collapse
OK, just reboot your phone and try the steps, I posted above.
tried but same result. I can't seem to flash the recovery even though the cmd window says successful
gunswordx said:
tried but same result. I can't seem to flash the recovery even though the cmd window says successful
Click to expand...
Click to collapse
very weird, you feel like trying one more time?
Download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Check MD5: 1c6afb14db3f305b0ad7d85d5af80bef
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot
adb reboot recovery
and post back command prompt.
nkk71 said:
very weird, you feel like trying one more time?
Download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Check MD5: 1c6afb14db3f305b0ad7d85d5af80bef
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot
adb reboot recovery
and post back command prompt.
Click to expand...
Click to collapse
ok will try
Hi guys hoping you can help.
I had phone connected in fastboot and wrongly issued the following command while trying to load CWM:
c:\fastboot boot recovery-clockwork-touch-6.0.4.8-m7.img
downloading 'boot.img'...
OKAY [ 1.143s]
booting...
OKAY [ 0.005s]
finished. total time: 1.160s
I overwrote something here in the wrong place..
Phone is currently connected to PC in fastboot.
I then tried:
C:\fastboot reboot
rebooting...
finished. total time: 5.003s
But phone did not reboot and just stuck on fastboot.
side toggle buttons also don't work now..
Can you help please ?
EDIT: All sorted now, just followed thread here http://forum.xda-developers.com/showthread.php?t=2617016 and all is good in the world again..
Hi
After de-brand, and upgraded to Nougat, bootloader isn't restored to locked
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
But when i flash pre-rooted boot image,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot rooted_b378_boot.img
target reported max download size of 471859200 bytes
sending 'boot' (16204 KB)...
OKAY [ 0.350s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.365s
Help me please
I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.
That's normal. Just enable modifications and that's it.
kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?
I don't think so.
You're good to proceed.
I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.
No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Flash fastboot ROM
Setting current slot to 'a' OKAY [ 12.421s]
Finished. Total time: 12.517s
Rebooting OKAY [ 0.098s]
Finished. Total time: 3.115s
Rebooting, then back to FASTBOOT
Solved!!
I got help from Xiaomi support
Helen17 said:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Click to expand...
Click to collapse
i had the exact same problem, but someone on the site has solved the problem and repaired my phone on distance but against fee, if you want i can send you the link for him.
Helen17 said:
Solved!!
I got help from Xiaomi support
Click to expand...
Click to collapse
how to solved?