Related
Ok so
Rooted
S-off
hboot 1.12.2222
was running Mean-rom 4.4
Then tried to install the new apk fix for ringtones
http://forum.xda-developers.com/showthread.php?t=1900629
Phone rebooted then then continues to be stuck in boot loop.
What I have tried:
Factory reset in bootloader
clear storage in bootloader
reinstall TWRP to get in recovery as if I choose recover in bootloader it just boot loops.
Tried to install the RUU but it can not connect during boot loops and errors out.
Any ideas?
Thanks in advance
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
om4 said:
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
Click to expand...
Click to collapse
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Those are fastboot commands, you use the terminal
fastboot wipe recovery
fastboot flash recovery recovery.img
You should be able to boot into recovery afterwards
What terminal? I'm a bit lost here
Do you have adb tools or Android SDK?
C:\android-sdk-windows
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
om4 said:
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
Click to expand...
Click to collapse
Get an error see attached
Now that I am in fasboot usb on the bootloader the RUU can connect to phone via USB.
If I just flashed that and started all over would that work and do I need to unroot and relock before doing the RUU?
Still not having any luck on terminal so far.
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
om4 said:
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
Click to expand...
Click to collapse
got fastboot working but get this with your first command
That's because I haven't used wipe in fastboot in quite a while, I'm sure I'm just confused on wipe and erase but you shouldn't need it, the first command should be fastboot erase recovery but like I said you shouldn't really have to, it's just like formatting before flashing the recovery, just fastboot flash recovery openrecovery.img or what ever the name is for the twrp file
Ran
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 1.796s]
finished. total time: 2.912s
Hit recovery and we we still are in boot loop
Relock bootloader and run ruu fastboot oem lock
copc said:
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Click to expand...
Click to collapse
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
luisrod03 said:
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
Click to expand...
Click to collapse
Thanks recovery just loops, could never get in.
Ok this is where I am at (see OP)
We tried flashing TWRP and original recovery via ADB
We tried running RUU
I'm still stuck in a boot loop....
I am having a similar problem stuck in bootloader. I relocked to go to the new firmware and now am stuck in the bootloader. I can access adb but can't access recovery. I am now relocked. Can I unlock again with a fastboot command?
If you unlocked manually, HTC sends the unlock code code just use fastboot to flash, if you used regawmod, just run it again. I don't know if regawmod will recognize the phone in boot loader though
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
More info would be helpfully, firstly what is your hboot? Are you s-on or s-off? What Rom did you flash? You are have issues with bootloops after you flash a rom?
(My evil evo is snake bitten by venom sense 4.1 rom and also infected with THE kernel,don't ask me for help, as I couldn't care less if you phone explodes)
Jaklo said:
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
Click to expand...
Click to collapse
re-read the steps on flashing a ROM...youll find out you need more than just the boot.img file to do it... only time you should have to flash the boot.img is when a new rom is installed but wont boot up...if your phone still boots then youre not installing the ROM properly
You need to supply the information that flashallthetime requested, but you should also be aware that flashing boot.img from fastboot does not flash the ROM and doesn't even flash all the files associated with the kernel. The attached screenshot of the warning that comes up in 4EXT when selecting the "flash boot.img" option expains it better than I can.
If you are S-ON, the proper way to flash a ROM is to "fastboot boot recovery.img" then flash the entire ROM .zip file from recovery, or use 4EXT with the S-ON (SmartFlash) option enabled. You can tell that SmartFlash is working by watching to see if your phone boots twice after your exit recovery. The first boot is used to flash the boot partition and the second boot loads the new kernel and ROM.
Don't confuse the complete kernel with boot.img, which is only one of the files required.
ramjet73
thank you for your replies!!
flashallthetime my hboot version is 1.53.0007 and i am s-on.
I tried to flash the Cool-ICS and the cerom.
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Jaklo said:
thank you for your replies!!
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Click to expand...
Click to collapse
I'm not familiar with the S-ON flashing guides for GSM which will be a little different than those for CDMA, so someone else will have to help with that, but you can get the recovery.img file for 4EXT that you need from the OP of the XDA thread. It's right above the other download links on that page. Look for the following sentence that has the download link embedded:
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
Click to expand...
Click to collapse
ramjet73
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
EM|NEM said:
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
Click to expand...
Click to collapse
Thanks again for the quick replies!!!
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix the hboot problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Jaklo said:
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix those problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Click to expand...
Click to collapse
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
i know that i have to be in fastboot usb mode
it gives me cannot load recovery.img error.
Buuuuut i finaly managed to install yoda´ s ICS custom ROM and EVERYTHING workssss
THX guys
Theres no way to downgrade your hboot without the wire trick my friend. you need s-off to downgrade your hboot. any older hboot could have easily been downgraded and then s-offed
I would suggest you try some other rom. This ones a pretty good rom (sense 4.1 but no 3d) and i'm sure it works with s-on/1.53
http://beta.androidfilehost.com/?fid=9390113915771289764
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
---------- Post added at 03:50 AM ---------- Previous post was at 03:46 AM ----------
oh good you already did another rom. good for you
EM|NEM said:
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
Click to expand...
Click to collapse
ok sorry for a noob question but does wipe mean factory data reset?
that is what i meant. do factory data reset and wipe dalvik cache as well
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
The OP cant load his recovery because he might not have a file named "recovery.img" in his fastboot/adb folder.
Flashing a boot.img is just the part of flashing ROM, especialy on S-On state. It still has not flashing your ROM, until you "update from *.zip file" from recovery.
Hi
I got my HTC One replaced because of some screen issue . On my earlier phone i had the bootloader unlocked and had Trickdroid running great.
I got the replacement and unlocked the bootloader and flash CMW recovery , but i am not able to boot into recovery i tried both the AIO kit and
power + up and power + vold down the phone just keeps rebooting doesnt ever going into the recovery . Is there something i am missing ?
dint have this issues first time aroung on my other HTC ONe.
any help is appreciated
THanks
if i flash the stock att recovery and reboot to recovery , i am able to boot into recovery. this is strange
i flashed back CWM and see that it again keeps rebooting . i tried the perm root tool and this is the error i am gettign
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "echo 'boot-recovery ' > /c
ache/recovery/command"
/system/bin/sh: can't create /cache/recovery/command: Permission denied
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "echo '--update_package=SDC
ARD:SuperSU.zip' >> /cache/recovery/command"
/system/bin/sh: can't create /cache/recovery/command: Permission denied
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "reboot recovery"
reboot: Operation not permitted
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>pause
Press any key to continue . . .
event tried
fastboot boot Recoveries\TWRP.img
it still reboots the phone
assuming flashing the recovery was successful (fastboot flash recovery recovery.img), have you tried fastboot erase cache ?
what is the output of those two commands when running them from your pc's cmd prompt?
colmustrd said:
assuming flashing the recovery was successful (fastboot flash recovery recovery.img), have you tried fastboot erase cache ?
what is the output of those two commands when running them from your pc's cmd prompt?
Click to expand...
Click to collapse
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>fastboot flash recovery Recoveries\TW
RP.img
sending 'recovery' (7916 KB)...
OKAY [ 1.183s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.829s
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.057s
one thing i notice is in the bootloader mode it just says unlocked , but on my earlier HTC One it use to say both
Tampered and unlocked does that matter ?
i even tried to relock it and unlock it again hoping it would say tampered.
Thanks
anilkuj said:
one thing i notice is in the bootloader mode it just says unlocked , but on my earlier HTC One it use to say both
Tampered and unlocked does that matter ?
i even tried to relock it and unlock it again hoping it would say tampered.
Thanks
Click to expand...
Click to collapse
unlocked is for your bootloader, and tampered I dont remember exactly if it showed up after I flashed the new recovery or later (after rooting it).
I would try the following:
unlock your bootloader again
erase the cache again: fastboot erase cache
attempt to flash the recovery one more time: fastboot flash recovery recovery.img
reboot via adb: adb reboot recovery
thanks for your help
i was trying this and finally got it working
http://forum.xda-developers.com/showpost.php?p=40516203&postcount=40
anilkuj said:
thanks for your help
i was trying this and finally got it working
http://forum.xda-developers.com/showpost.php?p=40516203&postcount=40
Click to expand...
Click to collapse
you are very welcome, glad you were able to get the phone into recovery.
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
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!).