Related
Recovery
You should have fastboot installed properly on your system to be able to flash it.
Heres a quick guide for Mac (which is really similar to Linux, search for XP guides which are available all over)
FASTBOOT
Download Fastboot from http://developer.htc.com/adp.html
Unzip and move to whatever folder you want.
I put it in /Users/MyName/Android
OPTIONAL Rename from "fastboot-mac" to "fastboot" (makes following guides made for xp and linux easier)
Now you have to append it to your .bash_profile
Easy Way
Follow instructions on http://donovan.covblogs.com/archives/027838.html to edit the bash_profile visually with textwrangler.
Your .bash_profile should look like this:
Code:
export PATH=$PATH:/Users/MyName/Android
export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
remember to edit the path to wherever you put your fastboot file (some people like to put it in the tools folder in the android sdk so adb is added to the .bash_profile as well)
or
Terminal Way
Code:
export PATH="$Path:/Users/MyName/Android"
Hit enter
Now refresh your .bash_profile
Code:
~/.bash_profile
To see if you've done it right
Code:
fastboot --help
or
Code:
fastboot --h
If the help text shows in terminal in another directory other than where fastboot is then you've got it right
Code:
$fastboot --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
To use the fastboot command your device has to be in fastboot mode
Enter FASTBOOT_MODE
Hold power button with device off and when the Home/Menu/Back buttons light up, release power button then press and hold the camera button
Dell logo will appear shortly followed by a white screen.
Tap fastboot in the top right
Thank you mzsigler from modaco for pointing out this simple step i missed.
finally:
FLASH RECOVERY IMAGE
Download the attached file and unzip it.
Make sure terminal is in the directory where the recovery-US6601.img is.
Use
Code:
pwd
to see which directory ur in
Code:
$ fastboot -i 0x413c flash recovery recovery-US6601.img
sending 'recovery' (3280 KB)... OKAY
writing 'recovery'... OKAY
$
Now reboot your device and hold both volume keys to get into recovery mode.
To the 6 people who downloaded it first, i might of uploaded the wrong one because i forgot that before i did nandroid backup i had flashed a different recovery to get clockword mod to work. This should be the right one now which was pulled using adb shell before clockworkmod.
Dell Streak stock US 1.6 Build 6601
There are several ways to restore/flash this i'll mention 2 Fastboot and nandroid
Fastboot
Code:
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c flash system system.img
fastboot -i 0x413c flash cache cache.img
fastboot -i 0x413c flash userdata data.img
fastboot -i 0x413c flash recovery recovery.img
Technically you don't need to worry about flashing cache.img and data.img but i performed this backup after a factory reset so your not taking any of my personal info/data
fasboot didn't work for me for so i restored with nandroid
Nandroid
+Create a folder named "Clockworkmod" on your storage card
+In that folder create a folder named "backup"
+Create a folder in "backup" named whatever you want and place boot.img, system.img, cache.img, data.img, recovery.img and nandroid.md5 in that folder.
+Flash Clockworkmod Recovery
2.5.0.1 didnt work on mine but 1.8.1.7 did :/
+Enter clockworkmod recovery
-Power on device while holding both volume keys, then select "2. Software upgrade via Update.pkd on SD Card"
Now you should be in ClockworkMod Recovery
-Scroll down to nandroid using the volume keys and press the camera button to select it
-Select Restore and choose your folder (the one you placed in the backup folder)
Now although this flashes 1.6 build 6601 it doesn't return the baseband to *****31
this is what mine now reads
Basband version
GAUSB1A110421-US
Kernel version
2.6.29-perf
OEM version
GAUSB1a111231
Build number
6601
Click to expand...
Click to collapse
Also be warned that after i returned to 1.6 i got the crazy home/menu/back lights as seen in this video I'm guessing it has something to do with the 21 baseband and 31 oem version
I think this is worthy of a sticky great work my friend keep it up
thanks for the files. wonder how to restore the 6601 baseband.
johnnobts said:
thanks for the files. wonder how to restore the 6601 baseband.
Click to expand...
Click to collapse
Yep, trying to figure that out now.. well back it up first from a device that hasn't been messed with.
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
when i flashed the recovery my screen got stuck at a black screen after the reboot
Worked great for me. Back to the out of the box experience.
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
uberamd said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
Click to expand...
Click to collapse
Are the other items flashing?
lbj23numb1 said:
when i flashed the recovery my screen got stuck at a black screen after the reboot
Click to expand...
Click to collapse
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Same here. Finally no O2 logo...
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
I had flashing lights. Flashing r2-4399-streak-superboot fixed the problem.
I am still at my original baseband. 21-EU
Stock 31 update is 4917. Why would you want to downgrade from 6601?
because we are in the US and are a little concerned we may not be able to apply the 2.2 upgrade with a modified baseband. fone, i don't think the baseband change will make a difference. i am concerned about the flashing lights as of right now.
fone_fanatic said:
Are the other items flashing?
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Click to expand...
Click to collapse
I can still get to the recovery using the buttons but when I select the second option that's when I get stuck at a black screen. I flashed the recovery through fastboot
No change in numbers and now no flashing lights. Still can not get to recovery, clockworkmod just reboots and button mode goes to standard recover and selectin option 2 goes black screen.
Model; Dell Streak
Firmware; 1.6
Baseband; GAUSB1A111231-US
Kernel; 2.6.29-perf
OEM; GAUSB1A111231
Build; 6601
I haven't been able to find any information about backing up baseband in order to do a restore.
get stuck on dell logo boot
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Hi fone-fanatic
Could you explain how backing up the recovery.img to be able to flash it ?
Thanks
gomesj said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Click to expand...
Click to collapse
I am having the exact same issue. Any advice?
I initially flashed this via fastboot and was stuck at the dell logo. i then flashed to the 02 1.6 rom and re flashed the att rom via clockwork mod nandroid. i am up and running but the lights flash like crazy and everything has "an unexpected error" and closes. cant open contacts, set up gmail, open "phone" so i cant get to the dialer. am i the only one getting all the force closes?
I would reflash mate
I just got a replacement phone from Sprint...
I had to downgrade using the RUU posted in here in order to use the HTC Unlocker (See Sticky).
When I tried to fastboot the CWM image 4.0.1.5 or the latest 5.0.2.0 and go into recovery, my phone just reboots.
I fastboot 'ed 4.0.1.4 and It comes up fine.
Just a heads up...
Isn't the latest version of CWM 5.0.2.0? Have you tried to use that?
no go on 5.0.2.0
aplusmiami said:
no go on 5.0.2.0
Click to expand...
Click to collapse
With the 4.0.1.4 can't load any roms... Random lock ups and freezes after FRESH and Warm install.
No Rom for me I guess :-(
Don't use CWM. Use TWRP and see if it works.
Also, you're doing 'fastboot flash recovery.img' and 'fastboot boot recovery.img' right?
yousefak said:
Don't use CWM. Use TWRP and see if it works.
Also, you're doing 'fastboot flash recovery.img' and 'fastboot boot recovery.img' right?
Click to expand...
Click to collapse
I did fastboot flash recovery recovery.img (The filename was actually different)
I did NOT do fastboot boot recovery
I just selected bootloader - recovery...
CM works as long as it is 4.0.1.4
TWRp works fine... I just can;t flash any roms.. The two I tried seem to install fine then when the phone reboots, they lock up at various points during bootup.
You can try to use boot manager. It's a paid app on the market and I think people have had success with it and hboot 1.5.
Cwm works fine dunno what you were having issues with unless you were typing the flash cmd in wrong . Anyways u didn't have to downgrade the software all you needed to do was use the latest ruu exe the 2.17 one would of got you going.
Twrp 2.0 has been know to cause dirty flashes to themes not working along with apk files missing that were cooked into a rom. I have seen the issue did it for me.
Anyways make sure with cwm that when you rename it call it cwm do not put cwm.img
Other wise when you go to flash it will error
Cause the file will be cwm.img.img seen a lot of people do it that way and have issues.
I had to downgrade because I could not get root. In order to get root you have to downgrade the software on the phone and then use the htc method... as far as I know.
The only recent version of CWM I could get to run was 4.0.1.4, but so far I can not load any Roms. They all fail at what seems to be right before they complete booting up.
I have given up for now... I use this phone as my daily and will have to run stock until the geniuses out there figure out whats up...
reaper24 said:
Cwm works fine dunno what you were having issues with unless you were typing the flash cmd in wrong . Anyways u didn't have to downgrade the software all you needed to do was use the latest ruu exe the 2.17 one would of got you going.
Twrp 2.0 has been know to cause dirty flashes to themes not working along with apk files missing that were cooked into a rom. I have seen the issue did it for me.
Anyways make sure with cwm that when you rename it call it cwm do not put cwm.img
Other wise when you go to flash it will error
Cause the file will be cwm.img.img seen a lot of people do it that way and have issues.
Click to expand...
Click to collapse
aplusmiami said:
I did fastboot flash recovery recovery.img (The filename was actually different)
I did NOT do fastboot boot recovery
I just selected bootloader - recovery...
CM works as long as it is 4.0.1.4
TWRp works fine... I just can;t flash any roms.. The two I tried seem to install fine then when the phone reboots, they lock up at various points during bootup.
Click to expand...
Click to collapse
Do it via fastboot (fastboot boot recovery.img) and any ROM/Kernel will work.
If you do it via bootloader>recovery it cannot write to boot partition and hence device will hang/reboot etc.
Tried just
fastboot boot recovery.img
recovery image was CWM 5.x
Phone resets and sits on the HTC screen then reboots and boots to home screen, however it is as if the phone reset itself... Have to set everything up again.
I have no clue whats up!?
mnomaanw said:
Do it via fastboot (fastboot boot recovery.img) and any ROM/Kernel will work.
If you do it via bootloader>recovery it cannot write to boot partition and hence device will hang/reboot etc.
Click to expand...
Click to collapse
aplusmiami said:
Tried just
fastboot boot recovery.img
recovery image was CWM 5.x
Phone resets and sits on the HTC screen then reboots and boots to home screen, however it is as if the phone reset itself... Have to set everything up again.
I have no clue whats up!?
Click to expand...
Click to collapse
Download this =====> http://downloadandroidrom.com/file/H...otevo3dnew.zip (no need if you already have fastboot/adb files.If you are gsm user, there might be different files)
Download any ROM or use any ROM that you have.
Download a superwipe tool ( or you can manually wipe everything from recovery).
>extract the "rootevo3dnew.zip" you downloaded above in "C:\" drive.(So it should be like "c:\rootevo3dnew\*.* ")
> install "HTCDriver3.0.0.007.exe" from it.
> open the ROM.zip (that you want to flash) with winRAR/7z and copy the boot.img from it to the rootevo3dnew folder.
> open cmd prompt ( press the key between "alt and fn" and press "r" then type cmd and hit enter)
> navigate to fastboot folder ( command : "cd c:\rootevo3dnew")
> boot phone in bootloader
> select fastboot
> connect to PC (phone should say fastboot-usb)
> type command "fastboot flash boot boot.img"
> now type "fastboot boot cwm-4.0.1.4-shooter.img"
> Phone should boot into recovery ( make sure the red LED is lit up)
> now flash the superwipe tool.zip(or wipe everything manually from wipe menu in recovery)
> and then flash the same ROM from which you pulled the boot.img.......
Hope this helps...........
Will give it ashot later tonight... Will post results!
mnomaanw said:
Download this =====> http://downloadandroidrom.com/file/H...otevo3dnew.zip (no need if you already have fastboot/adb files.If you are gsm user, there might be different files)
Download any ROM or use any ROM that you have.
Download a superwipe tool ( or you can manually wipe everything from recovery).
>extract the "rootevo3dnew.zip" you downloaded above in "C:\" drive.(So it should be like "c:\rootevo3dnew\*.* ")
> install "HTCDriver3.0.0.007.exe" from it.
> open the ROM.zip (that you want to flash) with winRAR/7z and copy the boot.img from it to the rootevo3dnew folder.
> open cmd prompt ( press the key between "alt and fn" and press "r" then type cmd and hit enter)
> navigate to fastboot folder ( command : "cd c:\rootevo3dnew")
> boot phone in bootloader
> select fastboot
> connect to PC (phone should say fastboot-usb)
> type command "fastboot flash boot boot.img"
> now type "fastboot boot cwm-4.0.1.4-shooter.img"
> Phone should boot into recovery ( make sure the red LED is lit up)
> now flash the superwipe tool.zip(or wipe everything manually from wipe menu in recovery)
> and then flash the same ROM from which you pulled the boot.img.......
Hope this helps...........
Click to expand...
Click to collapse
aplusmiami said:
Will give it ashot later tonight... Will post results!
Click to expand...
Click to collapse
those instructions are to flash a rom perfectly so you dont face any issues........ it should be used for devices unlocked using htcdev method.
mnomaanw said:
Download this =====> http://downloadandroidrom.com/file/H...otevo3dnew.zip (no need if you already have fastboot/adb files.If you are gsm user, there might be different files)
Download any ROM or use any ROM that you have.
Download a superwipe tool ( or you can manually wipe everything from recovery).
>extract the "rootevo3dnew.zip" you downloaded above in "C:\" drive.(So it should be like "c:\rootevo3dnew\*.* ")
> install "HTCDriver3.0.0.007.exe" from it.
> open the ROM.zip (that you want to flash) with winRAR/7z and copy the boot.img from it to the rootevo3dnew folder.
> open cmd prompt ( press the key between "alt and fn" and press "r" then type cmd and hit enter)
> navigate to fastboot folder ( command : "cd c:\rootevo3dnew")
> boot phone in bootloader
> select fastboot
> connect to PC (phone should say fastboot-usb)
> type command "fastboot flash boot boot.img"
> now type "fastboot boot cwm-4.0.1.4-shooter.img"
> Phone should boot into recovery ( make sure the red LED is lit up)
> now flash the superwipe tool.zip(or wipe everything manually from wipe menu in recovery)
> and then flash the same ROM from which you pulled the boot.img.......
Hope this helps...........
Click to expand...
Click to collapse
Nope.. no fly
back to sprint ruu
i will try flashgui next...
Got it working..
Downgraded using ruu found in the root sticky for hboot 1.5
Used HTC unlock method
fastboot recovery teamwin 2
Installed super user
Got flash gui off the market place
Flashed the kernel from the ROM I was using (fresh 4.2)
Rebooted into recovery from flash gui.
Wiped cache
Installed fresh ROM
Rocking and rolling...
Sent from my freshevo 3d on the now network
aplusmiami said:
I had to downgrade because I could not get root. In order to get root you have to downgrade the software on the phone and then use the htc method... as far as I know.
The only recent version of CWM I could get to run was 4.0.1.4, but so far I can not load any Roms. They all fail at what seems to be right before they complete booting up.
Click to expand...
Click to collapse
I had a similar issue (see link in my signature for specifics & walkthru). The new Cwm Touch 5.img file loaded up for me. That Cwm v4 was the only other that would work on mine.
Keep in mind you may have problems restoring Nandroid (recovery) backups, boot.img/kernel, if you don't use fastboot to enter recovery first ( fastboot boot YourRecoveryFilename.img ) .
I had a few posts in this other thread that might help too...
http://forum.xda-developers.com/showthread.php?p=22054499
(Q) How To Flash A Recovery From Bootloader 1.5
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
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!
Sorry, this is likely a noob question. I am working to flash a new rom on my ATT HTC One (cant stand all the ATT BS). I was trying to get the Android_Revolution_HD-One_12.0 working. I have unlocked the phone, and flashed a custom recovery image (stock image linked here http://forum.xda-developers.com/showthread.php?t=2224752) The boot loader now shows unlocked and tampered. Next I attempted to enter the recovery mode, when I select it the phone appears to reboot then shows me a pic of a phone with the green circle of arrows on it for a few secs then pic of a phone with a red exclamation mark. After a few minutes the phone will then reboot and run normally.
I have tried:
1) 'fastboot erase cache' prior to entering recovery
2) adb reboot recovery command
3) GooManager to load TWRP, which it did, but it will not load a rom (says its starting then nothing happens) or reboot into recovery (nothing happens)
All of these result in nothing happening or the same phone with green circle, then phone with red exclamation... I have not been able to access the recovery menu... any other ideas, or am I missing something
Thanks
T
bluecoller33 said:
Sorry, this is likely a noob question. I am working to flash a new rom on my ATT HTC One (cant stand all the ATT BS). I was trying to get the Android_Revolution_HD-One_12.0 working. I have unlocked the phone, and flashed a custom recovery image (stock image linked here http://forum.xda-developers.com/showthread.php?t=2224752) The boot loader now shows unlocked and tampered. Next I attempted to enter the recovery mode, when I select it the phone appears to reboot then shows me a pic of a phone with the green circle of arrows on it for a few secs then pic of a phone with a red exclamation mark. After a few minutes the phone will then reboot and run normally.
I have tried:
1) 'fastboot erase cache' prior to entering recovery
2) adb reboot recovery command
3) GooManager to load TWRP, which it did, but it will not load a rom (says its starting then nothing happens) or reboot into recovery (nothing happens)
All of these result in nothing happening or the same phone with green circle, then phone with red exclamation... I have not been able to access the recovery menu... any other ideas, or am I missing something
Thanks
T
Click to expand...
Click to collapse
I think your trying to flash the stock recovery image. You need to flash either TWRP or CWM custom recoveries. GO to this link and at the bottom it will show the commands to install TWRP from fastboot. It will also give you the link for the newest version of twrp, which is 2.6.0.0 i believe,
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
Hope it helps
Jmarv said:
I think your trying to flash the stock recovery image. You need to flash either TWRP or CWM custom recoveries. GO to this link and at the bottom it will show the commands to install TWRP from fastboot. It will also give you the link for the newest version of twrp, which is 2.6.0.0 i believe,
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
Hope it helps
Click to expand...
Click to collapse
Exactly as he said above. Download twrp (I stuck with 2.3.3.1 bc 2.5 was having problems flashing ROMs)
Put the twrp file in your folder that has fastbootand launch a CMD window (hold shift and right click, there will be an option to launch a CMD window)
Boot into the bootloader and then fastboot (be sure your phone says Fastboot USB)
on the command terminal type:
fastboot devices -- to make sure your device is being recognized (should say HTXXXXXXXXXXXXXX)
fastboot erase cache -- clears cache
fastboot flash recovery recovery.img (recovery.img is the name of the twrp file you downloaded EXACTLY)
Worked like a Champ, thanks for the help. I loaded twrp and the rom installed without a hitch. This phone us definitely faster now that all of the att crappie is gone.
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!).