Related
None of the existing tutorials or threads have accurate information on how to push the twrp recovery.
Following the very VAGUE instructions results in the fastboot cmd just listing the instructions instead of doing it's job.
Anyone have the correct commands to flash any working recovery or is there one?
Sure would like to flash a recovery of some sort. Anyone know how? Posting the existing methods is fail since they fail.
completely incorrect, followed instrucions precisely, albeit sounds like he skipped a hundred steps, so it's no wonder this method fails
http://forum.xda-developers.com/showthread.php?t=1192245
anyone else actually flash a recovery?
This is what I did:
First I renamed the recovery to avoid typos to TWRP.img
Second I made sure Fastboot.exe and the twrp.img file were in the same directory as the adb files.
Third, I booted my phone to the hboot and selected fastboot.
Fourth, I opened a command prompt in that directory and typed: fastboot flash recovery twrp.img
Then hit enter and bam!!! You have a custom recovery. Make sure you do a nand backup before you play with your phone.
fastboo
The link you posted is step by step. Is there any particular question you have that wasn't covered in the post? Not trying to be a ****, I just need to know exactly where you need help. And yes, I have s-off, recovery, and root access.
I figured it out - it's not clear that you have to acutally TURN OFF YOUR PHONE AND RESTART IN FASTBOOT MODE.
I found another thread that was clear. Now...
How do I boot into TWRP? lol jesus.
Make sure fastboot is off in settings>>>power, then turn phone off and power back on holding power and volume down.
From the link
clark44 said:
2.) Plug in you phone to your pc and make sure you have fastboot drivers and your phone is in fastboot mode
Click to expand...
Click to collapse
Sorry, I had to
cruise350 said:
This is what I did:
First I renamed the recovery to avoid typos to TWRP.img
Second I made sure Fastboot.exe and the twrp.img file were in the same directory as the adb files.
Third, I booted my phone to the hboot and selected fastboot.
Fourth, I opened a command prompt in that directory and typed: fastboot flash recovery twrp.img
Then hit enter and bam!!! You have a custom recovery. Make sure you do a nand backup before you play with your phone.
fastboo
Click to expand...
Click to collapse
What directory do I put fastboot.exe and recovery.img in?
Any. But in order for the commands from this thread to work it should be in the same as your fastboot command. Usually /androidsdk/tools or possibly /platform-tools. Which ever has the fastboot, put it there.
Otherwise make sure you declare the path in the fastboot execution command.
Thanks got it. SO how do you boot into twrp, without booting to bootloader first?
MikeC84 said:
Thanks got it. SO how do you boot into twrp, without booting to bootloader first?
Click to expand...
Click to collapse
adb reboot recovery
Thanks got it rooted and installed quickboot for easy boot to recovery
[[ SOLVED ]]
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
rikrdoVe said:
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
Click to expand...
Click to collapse
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
reaper90 said:
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
rikrdoVe said:
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
Click to expand...
Click to collapse
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
reaper90 said:
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
Click to expand...
Click to collapse
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
rikrdoVe said:
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
Click to expand...
Click to collapse
Did you use the right version of CWM for android 4.4+?
reaper90 said:
Did you use the right version of CWM for android 4.4+?
Click to expand...
Click to collapse
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
rikrdoVe said:
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
Click to expand...
Click to collapse
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
reaper90 said:
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
Click to expand...
Click to collapse
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
rikrdoVe said:
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
Click to expand...
Click to collapse
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
reaper90 said:
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
Click to expand...
Click to collapse
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
rikrdoVe said:
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
Click to expand...
Click to collapse
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
reaper90 said:
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
Click to expand...
Click to collapse
A month without phone and thanks to you it works again!
Thank you so much, I could not pass the zip in any way but with "adb push rom.zip / data/media/0 /" if it happened and I could flash ...
I Repeat .... THANK YOU!
have the same problem with my HTC One X.
Can you gave me an answer?
Hey guys.
SGP312 model here, unlocked bootloader.
not sure what i did wrong here - i got to Fastboot mode and the blue light is on, when i run "Fastboot devices" i get the device name.
so i followed the explanation here: https://forum.xda-developers.com/xp...pment/ub-twrp-v3-2-1-xperia-tablet-z-t3735110
and did: "fastboot flash boot twrp-3.2.1-0-pollux_windy.img"
however, now my phone won't boot, and when i type "adb reboot recovery" i get "error: device not found" (even thought "Fastboot devices" gives me a response")
i tried fixing it with Flashtool, and everything works well until i get to "Wait for Flashmode" and im instructed to "unplug, power off, pres vol down, plug in USB cable" - this simply doesn't do anything =X
so.... how do i get out of this? all i want to do is install one of the newer roms from the forum (either Marshmallow or Oreo)
can anyone help me get out of this issue i've gotten myself into?
Caniv said:
Hey guys.
SGP312 model here, unlocked bootloader.
not sure what i did wrong here - i got to Fastboot mode and the blue light is on, when i run "Fastboot devices" i get the device name.
so i followed the explanation here: https://forum.xda-developers.com/xp...pment/ub-twrp-v3-2-1-xperia-tablet-z-t3735110
and did: "fastboot flash boot twrp-3.2.1-0-pollux_windy.img"
however, now my phone won't boot, and when i type "adb reboot recovery" i get "error: device not found" (even thought "Fastboot devices" gives me a response")
i tried fixing it with Flashtool, and everything works well until i get to "Wait for Flashmode" and im instructed to "unplug, power off, pres vol down, plug in USB cable" - this simply doesn't do anything =X
so.... how do i get out of this? all i want to do is install one of the newer roms from the forum (either Marshmallow or Oreo)
can anyone help me get out of this issue i've gotten myself into?
Click to expand...
Click to collapse
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I made same stupid mistake, so after getting the boot.img and ur command I get waiting for device. Any solution?
NoSuperHero said:
I made same stupid mistake, so after getting the boot.img and ur command I get waiting for device. Any solution?
Click to expand...
Click to collapse
enter recovery if it is installed and flash boot.img from there.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I did the same thing knowing the outcome and then successfully flashed Lineage.
For future reference, with the Xperia Tablet z where should I be flashing the recovery if not to boot:
"fastboot flash *What goes here?* twrp-3.x.x-0-pollux_windy.img"
big ach said:
I did the same thing knowing the outcome and then successfully flashed Lineage.
For future reference, with the Xperia Tablet z where should I be flashing the recovery if not to boot:
"fastboot flash *What goes here?* twrp-3.x.x-0-pollux_windy.img"
Click to expand...
Click to collapse
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
where twrp.img is your recovery image.
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!
I recently found my old HTC desire 526g and I decided to flash a custom ROM, but its volume buttons aren't working so I had to use adb, I am not really an good in these types of things. I tried to flash TWRP on my htc using adb (Followed a YouTube tut) but this is coming up.
I have attached a screenshot below.
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Rajveer chauhan said:
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Click to expand...
Click to collapse
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
YourLocalClown69 said:
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
Click to expand...
Click to collapse
So if you're rooted so you can flash recovery via twrp app on playstore, or if magisk installer for twrp exists for your phone or by flashfire if you have your working recovery
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
LR7875 said:
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
Click to expand...
Click to collapse
This comes later now lol, Due to my lack of knowledge and not enough patience, I tried to flash custom recovery through TWRP app, and I didn't found my phone model on device list, SO i just selected random htc model phone and now it is restarting over and over again, Is there any fix to this? I am obviously a complete noob in this field.
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Rajveer chauhan said:
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Click to expand...
Click to collapse
Even If I find the this whatever you said, how am I supposed to fix it, as I mentioned,Volume buttons aren;t working and its stuck in bootloop, it won't past its manufacturers logo, so adb is no help in it, Only way to fix it would be to fix sound buttons. sad me, Well, R.I.P. HTC Desire 526g dual sim 2015-2021
I hope that this phone is not your primary driver
YourLocalClown69 said:
I recently found my old HTC desire 526g
Click to expand...
Click to collapse
Rajveer chauhan said:
I hope that this phone is not your primary driver
Click to expand...
Click to collapse
He unearthed his phone from some drawer, so this is not his daily driver.