Database Develop

htc vivid unbootable system

hello,
I have a problem guys i was flashing a rom (rom holics) happens to finishing flash, and in the process of restarting the device, I think for hurry I gave ah update.zip and rebooting, the screen stays there with the htc logo in black and restarts and the cycle repeats, could enter the bootloader, but now when I go into recovery at the beginning and who wants to enter (see the logo and lettering recovery) but then again with the white screen logo vibrates and reboots, I can do? by fastboot usb I can do something?
re-flash the recovery?
I ask for your support please

In fastboot, flash the recovery again I recommend wxcrecovery and then flash the ROM again. If you are s-on then you have to fastboot flash the kernel.
Sent from my Holiday using xda premium

Marshmellow92 said:
In fastboot, flash the recovery again I recommend wxcrecovery and then flash the ROM again. If you are s-on then you have to fastboot flash the kernel.
Sent from my Holiday using xda premium
Click to expand...
Click to collapse
I get the following (attached screenshot)

cancha said:
I get the following (attached screenshot)
Click to expand...
Click to collapse
Recovery was written fine. Now you need to reboot to recovery. Instead of
fastboot reboot
do
fastboot reboot recovery
Or just select bootloader on the phone, then select recovery
Now you're in recovery, flash the ROM of your choice. If you're s-on, you'll then need to reboot to fastboot and fastboot flash the boot.img included with the rom

homeslice976 said:
Recovery was written fine. Now you need to reboot to recovery. Instead of
fastboot reboot
do
fastboot reboot recovery
Or just select bootloader on the phone, then select recovery
Now you're in recovery, flash the ROM of your choice. If you're s-on, you'll then need to reboot to fastboot and fastboot flash the boot.img included with the rom
Click to expand...
Click to collapse
If I did that, try to get into recovery, but still I can not access = recovery restarts in white screen and htc logo, I did going into bootloader then recovery, not tried from the console of the pc

In boot loader does it say locked or unlocked?
Edit: try a different recovery
Sent from my Vivid 4G using Tapatalk 2

homeslice976 said:
In boot loader does it say locked or unlocked?
Edit: try a different recovery
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
says JuopunutBear S-OFF

when I try to load from the image with the following command
fastboot boot recovery.img file-
It's the same goes for the recovery time is then restarted the typical htc logo with white screen
I'm already starting to worry is brick?

cancha said:
when I try to load from the image with the following command
fastboot boot recovery.img file-
It's the same goes for the recovery time is then restarted the typical htc logo with white screen
I'm already starting to worry is brick?
Click to expand...
Click to collapse
If all else fails flash stock recovery, re-lock bootloader, run an RUU ( or flash a PH39IMG.ZIP file ), unlock the bootloader, re-root, flash a custom recovery and restore your phone from a nandroid backup or titanium backup. and all should be well.

camo_flage said:
If all else fails flash stock recovery, re-lock bootloader, run an RUU ( or flash a PH39IMG.ZIP file ), unlock the bootloader, re-root, flash a custom recovery and restore your phone from a nandroid backup or titanium backup. and all should be well.
Click to expand...
Click to collapse
Thanks friend, if I had no need to use the RUU and install the RUU now achieved again the whole process thanks XD

Cannot enter recovery mode?

Hello, i have an htc one on 4.1.2 and want to flash android_revolution_HD-One_10.3 on it through revovery but i cant seem to go into recovery mode. I hold vol down and power button and enter bootloader menu. Now when i press rcovery, i get black screen then red triangle. I then press power on for a while and enter into main screen. How do i get into recovery mode? Help. I have enabled usb debugging and disabled fast boot.

That's the stock recovery, you need to flash CWM/TWRP first

EddyOS said:
That's the stock recovery, you need to flash CWM/TWRP first
Click to expand...
Click to collapse
I have One_All-In-One_Kit_v, how do i flash TWRP with it?

andrew21 said:
I have One_All-In-One_Kit_v, how do i flash TWRP with it?
Click to expand...
Click to collapse
Just flash it manually. I'm sure there's a guide in the first post of TWRP recovery thread. If you are already unlocked you can just do
fastboot flash recovery nameofrecovery.img

fastboot flash recovery recovery.img
Whereas recovery.img is the name of the custom recovery you want to use (I rename mine to recovery.img for ease of use)

BenPope said:
Just flash it manually. I'm sure there's a guide in the first post of TWRP recovery thread. If you are already unlocked you can just do
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Ill try and post results

[Q] Dev Ed Unlocked and Flashed Won't Boot Recovery

Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4

cw18306 said:
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
Click to expand...
Click to collapse
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way

danger2u said:
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
Click to expand...
Click to collapse
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?

cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X

flashallthetime said:
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
Click to expand...
Click to collapse
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?

cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
look alot of people are having this issue it is a simple fix follow the directions step by step
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
as soon as you type the above command to flash TWRP we need to boot the phone into recovery before we let it boot to android we can do that via the command below.
Code:
adb reboot recovery
MAKE SURE THAT AFTER YOU TYPE THE FIRST COMMAND DO NOT LET THE PHONE BOOT TO ANDROID.
right after you hit enter for the mfastboot command type the reboot command it will boot into recovery. if not i would redownload the correct TWRP recovery for 4.4
there is a link here
http://forum.xda-developers.com/showthread.php?t=2603358

cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
If recovery flashes but is not available, your best bet is to flash the sbf firmware and flash recovery, its worked for numerous folks including me
Sent on my Moto X

cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.

xawen said:
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
Click to expand...
Click to collapse
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:

cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
Like I said previously ,flash the kitkat firmware, forget jb. You can not flash back to the pre camera ota, gpt.bin is the bootloader which if is incompatible will fail, saving you from hard bricking your device
Sent on my Moto X

cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
What errors are the RSD and fastboot actually failing with?
When you're trying to do the fastboot flash, does "fastboot devices" actually show your device as connected?
-----Edit----
Are you sure that is the right version of the firmware? I'm waiting for access to the files from the moto site right now so I can compare the full file name, but I'm pretty sure you have the Maxx Dev Edition firmware file there.

cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
fastboot reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted

@cw18306 just got turnt up

SuperSU.ZIP Move to Phone?
dray_jr said:
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
adb reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
Click to expand...
Click to collapse
You are THE MAN! Quick question regarding SuperSU.zip...Do I unzip it in windows and MOVE the 4 folders to the phone, OR do I only need to move the UNZIPPED SuperSU file to the phone? I am about to flash recovery and want to be sure. Thanks so much!!!

Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.

nhizzat said:
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
Click to expand...
Click to collapse
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android.

cw18306 said:
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android. I rebooted to bootloader again, reflashed TWRP, highlighted Recovery, hit UP, and the screen goes black and does not boot. If I press the power button, the phone will boot to Android. That is where I am now. Something must be up with my Recovery file?
Click to expand...
Click to collapse
@dray_jr

cw18306 said:
@dray_jr
Click to expand...
Click to collapse
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:

cw18306 said:
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
Click to expand...
Click to collapse
no problem glad everything worked out for you enjoy

[Q] Process of flashing while rooted

I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?

Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.

simms22 said:
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
Click to expand...
Click to collapse
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.

Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Click to expand...
Click to collapse
it is easy, enjoy

simms22 said:
it is easy, enjoy
Click to expand...
Click to collapse
So to reassure, the process I listed is good to use for updates?

Forerunner326 said:
So to reassure, the process I listed is good to use for updates?
Click to expand...
Click to collapse
yea, its fine, but you dont have to reboot the bootloader after each flash.

simms22 said:
yea, its fine, but you dont have to reboot the bootloader after each flash.
Click to expand...
Click to collapse
Rebooting the bootloader like this doesn't hurt correct?

Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
i wouldnt think so

simms22 said:
i wouldnt think so
Click to expand...
Click to collapse
What does rebooting the bootloader do?

Forerunner326 said:
What does rebooting the bootloader do?
Click to expand...
Click to collapse
just that, reboot the bootloader, nothing else. its been too long since i flashed a factory img! good thing too

Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked?
Click to expand...
Click to collapse
You don't.
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.

efrant said:
You don't.
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
Click to expand...
Click to collapse
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.

Forerunner326 said:
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Click to expand...
Click to collapse
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.

efrant said:
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
Click to expand...
Click to collapse
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?

Forerunner326 said:
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Click to expand...
Click to collapse
Yes.

This is my method verified with 5.1.0 D and E variants, this will not wipe your device.
Download images from: https://developers.google.com/android/nexus/images#shamu
Extract all files to your comp including the main .tgz and the .zip inside that
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img (optional if keeping TWRP or you can flash the latest TWRP here)
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot (Or enter recovery and re-root if you kept TWRP)

efrant said:
Yes.
Click to expand...
Click to collapse
Is there anything else I should know before I flash any update files onto the device?

Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.

gee2012 said:
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
Click to expand...
Click to collapse
What about the cache image? Would it go after boot.img gets flashed? Or do I not worry about it?
This is what I have so far.
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. Connect to pc and load platform tools command window
4. fastboot flash bootloader {bootloader-shamu-xxx.img}
5. fastboot reboot-bootloader
6. fastboot flash radio {radio-shamu-xxx.img}
7. fastboot reboot-bootloader
8. fastboot flash system system.img
9 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
10. Boot into TWRP by selecting Recovery Mode on device and pressing power button
11. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm)
12. Reboot (Main menu > reboot)

You can do that after boot:
fastboot erase cache
fastboot flash cache cache.img
11, 12, 13.

Can't Access Recovery or Device, only Fastboot

Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?

same problem here... were you able to fix it?

You might have to use the QFIL method to get your phone going again. Remember you MUST backup the EFS partition and anything associated with your phones imei and SN

Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
flash the boot partition then flash stock recovery then try to flash twrp then try to flash a custom or stock rom what you want.

Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Anyone solve this problem?

Juninalilla said:
有人解决这个问题吗？
Click to expand...
Click to collapse
这两个可怕的重锁码吓了我一跳，以为手机没电了。幸运的是，我找到了解决方案。你可能需要找个老股rec，跟着视频操作，不用拆机，重点解压。进入adb文件夹，生效

Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...