Related
I've rooted and unlocked my MoPho as of now.
I've attempted to flash joker and romracer's recovery.
However, when I go to check to see how CWM is doing, I only get 4 options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Both of the videos I have watched show other options such as backup's and such. I'm not sure what I'm doing wrong, and any help would be appreciated!
Which clockwork are you using?
I have used this:
http://forum.xda-developers.com/showthread.php?t=1216143
and the
AIO root
The standard cwm (The one from market) gives me all the options.
However, when I try to flash jokers or romracers cwm recovery I just get the 4 basic options again.
Fastboot erase recovery and then use fasboot to install the new, one romracers or jokers your choice. If flashing CM9 id use Jokers.
That is the method I attempted to flash both of them with.
I still get the triangle with the arrow and the android by it that I have to press both the up and down volume buttons to show the recovery screen.
cardinalsfre said:
That is the method I attempted to flash both of them with.
I still get the triangle with the arrow and the android by it that I have to press both the up and down volume buttons to show the recovery screen.
Click to expand...
Click to collapse
Thats the stock recovery.. You ARE unlocked correct? and you flashed it by putting phone into fastboot and with CMD pushing the new recovery?
Yes, I do believe I am unlocked.
Root check shows that I am rooted
Upon boot the phone says, "unlocked"
Yes, I am using the CMD prompt to attempt to flash, following qbking's video instructions.
Edit: Also, the CMD prompt says it has completed the recovery flash.
So you did all this below?
"moto-fastboot erase recovery
moto-fastboot flash recovery recoveryfilename.img"
and it came back saying
"sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]"
If so id to redownload the recovery.img and try again..
That worked, at first.
Upon first boot up I was greeted with the right recovery module.
When I went restarted to flash my ROM I was brought back to the original Android Recovery.
Edit: Should I flash on first boot up or should I wait until I can get the recovery to stick?
You have to go into the files and rename the stock recovery to ".bak" to make the new one stick. If I can find the link again, I will post it , or you can Google it? I think that's how I found it to begin with.
Thanks, that worked!
I've tried everything I've found to get back to stock recover but I'm always greeted with red triangle. Only way to get to recovery back on line is to re-flash twrp. I've tried fastboot method, flasing new firmware, windroid toolkit... nothing works. I can't even flash CWM. So how do I get that damn leech out of my phone?
[edit]
Can't even flash twrp back on..so no recovery in this phone at the moment. Tried using goomanager, but it didn't do it either.
[/edit]
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
ethanon said:
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
Click to expand...
Click to collapse
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Wiper said:
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Click to expand...
Click to collapse
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
ethanon said:
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
Click to expand...
Click to collapse
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
I got the same problem with RUU battery stat
Flashing a kernel solved the problem
Flashing another kernel didn't solve that porblem.
Wiper said:
Flashing another kernel didn't solve that porblem.
Click to expand...
Click to collapse
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
[email protected] said:
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
Click to expand...
Click to collapse
Tried that as well..no go. Tried even fastboot boot recovery.img but the phone just turns itself off and doesn't load temporary recovery.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Lloir said:
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Click to expand...
Click to collapse
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
U tried every possible incorrect things.....and didn't even read Llior's post......
To flash a kernel the fastboot command is
Code:
fastboot flash boot boot.img
To flash a recovery the command is
Code:
fastboot flash recovery recovery.img
instead of this u had tried to write the recovery file in boot partition...
and the
Code:
fastboot boot recovery.img
is to enter into the recovery without even having to install it on phone....
and I haven't checked it in HOX+ so better flash the boot.img(Kernel) and recovery.img(Recovery) using the mentioned commands above. and erase the cache....(which you seem to do correctly)...
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Lloir said:
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Click to expand...
Click to collapse
I haven't actually renamed anything (just in here to keep it short). And that 1. & 2. was miswritten. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Ive tried it with All-in-one tool as well...The weird thing is that all fastboot flashes or with that allinone tool there are no errors ever, only successfull flashes.
Wiper said:
I haven't actually renamed anything (just in here to keep it short). And that 1. was typo. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Click to expand...
Click to collapse
are you sure your device is the enrc2b and not the evitareul?
Lloir said:
are you sure your device is the enrc2b and not the evitareul?
Click to expand...
Click to collapse
Yup... But anyway...decided to try that twrp one more time with all-in-one tool, flashed okay but this time the recovery worked and I was able to flash working rom and boot.img. Phone works now, but this was the last time I try to remove twrp.
I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp311 on android 5.1.1 and bootloader is unlocked.
1. I open cmd terminal from the folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" and it's successful (had an image but cant link it)
4. I use the command "fastboot reboot" and nothing my device stays blank, nothing appears on screen even after holding the power and volume up buttons to do a regular reset and hard reset. When I flash android 5.1.1 back on to my device all my data is still there.
I am also trying to use flashtool to revert too android kitkat but after flashing the firmware and booting up it just stays in a bootloop at the sony logo.
Anyone have any suggestions on what to do?
BrickedXperia said:
Anyone have any suggestions on what to do?
Click to expand...
Click to collapse
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Rootk1t said:
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Click to expand...
Click to collapse
Thank you, I flashed cyanogenmod recovery with adb commands and restarted it and it worked, I now have cyanogenmod on my tablet and it looks and feels way better than the stock rom.
As BrickedXperia, I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp321 on android 5.1.1 and bootloader is unlocked.
No root (must I?)
1. I open cmd terminal from the platform-tools folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" but here it fails and gives an error.
I see from Rootk1t's reply that you have to do something with kernel. Would someone care to elaborate a bit? I am new to this stuff and it's not straight forward despite all the guides around. I would appreciate any help a lot.
What does the error say?
Something like
writing 'recovery'... failed (remote command not allowed)
Svenni84 said:
Something like
writing 'recovery'... failed (remote command not allowed)
Click to expand...
Click to collapse
if it says not allowed, check that bootloader state is really unlocked.
Rootk1t said:
if it says not allowed, check that bootloader state is really unlocked.
Click to expand...
Click to collapse
When I open the hidden service menu it really does say that it is. Is it any other way to confirm this?
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.
Hey all,
I have a new z5c running 32.4.A.1.54 stock.
I flash TWRP (I have tried a few different versions) using Fastboot on Ubuntu20.04, it all runs fine no errors, and appears to flash as it should.
But the phone will not load TWRP, from the phone itself, I have tried a million different ways.
The only way it loads is by
fastboot boot twrp.img
But when I do this .. android will not then start .. hangs on Sony logo
I have to reflash the stock rom to get it to work again
If I run
fastboot reboot recovery
I get:
fastboot: usage: unknown reboot target recovery
even tho:
fastboot devices
correctly identifies the device
I would like to root and use custom rom, but have not yet been able to get past this TWRP hurdle
Has anyone experience of this, or any ideas?
You've flashed TWRP in a wrong way! Please search for help in my several ROM threads.
Well, thanks for your answer, really, I appreciate it
But I have flashed it again and again and followed your threads and other threads
I'm not a newbie, i have flashed TWRP and roms to a few phones, inc Z1C and a couple of Z3Cs
I have adb, and fastboot installed
Bootloader unlocked
USB debugging
Recommended stock
I have downloaded multiple .img files, including your 3.6.1 version
I run fastboot
and
fastboot flash recovery twrp.img
The phone will not reboot into TWRP, using buttons nor fastboot, only into android, unless I then run
fastboot boot twrp.img
Then TWRP runs, but when I then reboot, I just hit the SONY logo if I have not flashed a ROM or a bootloop if I have.
And from there will not return to TWRP at all.
What am I missing?
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Berni-0815 said:
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Click to expand...
Click to collapse
Yes, that makes 2 of us!
Ugh.
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Berni-0815 said:
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Click to expand...
Click to collapse
I did try that as recommended, thanks
I am flashtool-ing back to the stock again, after being again stuck on boot with TWRP inaccessible
I will give it one last go
Thanks, man
How do I buy you a coffee?
That's all really weird; since it works here since years.
From a fresh fully-functional stock install
Following this simple process exactly
Devices with only TWRP.IMG​
If your device only has the IMG file, then execute the below command: fastboot flash recovery twrp.img
Now execute the below command to boot your device to the TWRP recovery. fastboot boot twrp.img
Once it boots to TWRP, you could then boot it to the OS, via the Reboot > System option in TWRP.
From here;
https://www.getdroidtips.com/flash-twrp-recovery-android/
After 3. it gets to SONY logo and hangs
Same every time
Obviously not a problem with your or any other custom ROM
The only way out from here is to Flashtool the stock again
Geez
I'm giving up on TWRP and custom ROM
I'll go for the rooted, debloated, degoogled stock as best as I can get it
Thanks v much for the support!
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Berni-0815 said:
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Click to expand...
Click to collapse
That command is the only way that twrp has loaded for me
Right .. deep breath ... one last go at this using yr suggestion,
thanks
Nope
Same again
All goes as it should
Power and volume down simultaneously
Boots into Android
adb reboot recovery
Also boots into android
If I was now to run
fastboot boot twrp.img
It would run TWRP the one time, but just hang on SONY logo when rebooted
Ho hum.
kaivalyam said:
Power and volume down simultaneously
Boots into Android
Click to expand...
Click to collapse
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Berni-0815 said:
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Click to expand...
Click to collapse
Well, its not a particularly complicated process
I have described exactly what I have done
I have done it multiple times
And that is what happens
As I said: I've never seen that and that's not reported very often by other users.
And if, then it has been an error in flashing.
Highly unlikely that you're devices so called FOTA partition is damaged so that the command
Code:
fastboot flash recovery <name of the recovery image>
fails.
Code:
fastboot flash boot <name of the boot image>
flashes the boot partition and that's not the same as the FOTA partition.
I have to believe you but somehow I can't.
I understand
fastboot flash recovery <name of the recovery image>
Doesn't fail exactly ... it runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
target reported max download size of 536870912 bytes
sending 'recovery' (22668 KB)...
OKAY [ 0.570s]
writing 'recovery'...
OKAY [ 0.395s]
finished. total time: 0.965s
But then the phone will only boot android
~~~
Unless
I run;
fastboot flash boot <name of the boot image>
Again, runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.552s]
booting...
OKAY [ 0.561s]
finished. total time: 1.113s
This boots TWRP but then after that the phone hangs at boot and will neither start Android or TWRP
It is indeed very strange.
Look at your own code:
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
From where is boot.img downloaded? And where is it stored internally?
Have you flashed system.img too?
There goes something terribly wrong at your side.
Thanks for your patience
Yes I'm sure you're right, probably user error, although I am having trouble seeing what that is exactly ...
So, using Ubuntu, I am in the directory that contains the twrp.img file (most times I have renamed it this)
Is that correct so far?
From there I run
fastboot flash recovery twrp.img
All good, as above, but TWRP does not load, ever, using buttons or adb, unless I then run
fastboot boot twrp.img
TWRP then runs
But the phone will not boot into anything from there
Yes, I thought that was a little odd ...
"downloading" : I assumed it meant it was transferring the file across, or accessing it, from my pc to the device
"'boot.img" : I assumed fastboot had changed the filename to what it needed it to be ...
Is the problem around this?
You can name the recovery image file as you like it to be named.
Have you disconnected the USB cable after flashing?
Have you waited some time before trying to boot anything?
If you can boot TWRP, you can fetch a LOG file at the "Advanced" menu. Please send me this LOG file via PM (it may contain personell data!).