unaccessible fastboot / recovery - Zenfone 5 Q&A, Help & Troubleshooting

Hi,
Currently on 2.22.40.54 firmware, and successfully rooted it, but with a wrong root method. Therefore I lost camera access. Followed this guide , and flashed the 2.22.40.30 fastboot / recovery (which was successful), but the firmware flash didnt proceed, (had to restart), which resulted in not able to access fastboot / recovery. Tried flashing a new recovery tru xFSTK, but encountered the driver error and the ASUS Flash Tool gives me "serial number not found" error... I usually get the USB logo on start up, but sometimes I get a normal boot (which is nice).
Now, what is the best way to recover my recovery / fastboot? I'm willing to try everything except bringing it to a Service Center.

turn off devices and then pres power buton and vol. up y will see asus logo then pres only vol. up .. if it will works please write there

Related

please help! d802 bricked-no download mode. no recovery. not hardware factory reset

lost my twrp after installing bootloader changer and then installing kk bootloader(for cloudy 3.3). (accidently marked install twrp inside the bootloader installation after already having the latest twrp installed)
phone restarts right after logo appears and seems to be unable to boot at all.
no download mode. no recovery. not even hardware factory reset is accessible.
im really lost here ! read all xda posts nothing works because i cant connect to
the phone from any pc. please help! i cant flash anything because i have no adb or any connection from the phone to the pc.
wont show up in device manager in any way(with the latest drivers installed) and wont show up on linux on /dev/sd*.
before the bootloader i had access to twrp and showed up just fine on my win 7.
problem solved!
was able to enter recovery mode by pressing pwr + vol-up release when logo appears and press vol-up + vol-down.

Lenovo A6000 plus on DU with a peculiar problem!!!

First of all, i'm a noob so please don't mind any technical mistakes.
I recently flashed RR on my device with TWRP, and all was working quite fine.
But then, I decided to try out DU, and flashed it. But my phone was stuck on the lock screen with a "com.android.phone stopped working" message.
I used ADB to wipe my data ( for if there were any conflicts) using : fastboot -w
My phone now is working fine, But i've lost root access, My phone DOESN"T BOOT INTO RECOVERY.. Holding vol+ and power just ends up in a screen with the RR logo( yes RR, even after flashing DU).
I've tried to flash TWRP using ADB again but it's not working.
ROM manager says I've got TWRP and CWM installed.
Also Kingo and Framaroot aren't working.
I would really want to get back:
1.Root access
2.TWRP
Some help will really be appreciated....
Press vol up+down and power button simultaneously, to access recovery.
I've tried that, my phone just shows the RR logo screen and nothing else.
Alternate method
dude you just need a pc with adb driver installed then go to bootloader mode by pressing vol- and power button, then using adb command write (fastboot boot recovery.img).
Here recovery.img is ur twrp recovery or other,then it will flash recovery.img in ur phone and automatically go into the (twrp) recovery.
(u need to copy recovery.img in ur adb folder before u write that command)
I have done that... It does flash twrp onto my phone..but my still doesnt boot into twrp...
then use another recovery, sevenmax twrp recovery is the best.

What Have I done.... Soft Bricked A7G

Hello All
I have problem with my Axon7 G. I had 8.00 version installed and tried to make a system write option with using a method mentioned in
Official (Beta) Android 8.0.0 V1.30B01 EU Version by NFound thread. I flashed zip mentioned in this tread -ZTE_A7_UniversalBootStack.
Then restart devices and...whats happened....soft (or hard) bricked my phone!!!!!
1. After restart i had a standard warning about unlocked bootloader with yellow fonts . After 5 sec yellow fonts changed into red and wrote my device is corrupt...
2 using vol down i can enter into bootloader mode - then i can choose option like fastboot, recovery,restart and power off.
- pressing recovery and restrt , phone restart and again boot into bootloader mode with option above (cant get into twrp or stock recovery mode)
-pressing fastboot i can enter into this mode .
3 . Use fastboot mode to flash recovery and boot ( fastboot flash recovery recovery.img and fastboot flash boot boot.img)
everything seems ok but...nothing changed , i cant boot into recovery -twrp or stock. Still go back after restart to bootloader menu
4. edl mode.....i can`t enter . Use vol + and vol- and power button then after 3 sec phone went black screen with red light upper left. Applications cant recognize phone in this mode...
somene can help me ???
I also get the warning but I can just continue with the boot. I can't access recovery however. Don't know hot to fix that.
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Antistar said:
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Click to expand...
Click to collapse
did you manage to get the error message away?
I got it recently after installing LOS 15.1, but for me everything works fine .
I'm just afraid if the device randomly reboots at night my alarm won't go off in the morning since it's the device is shutting itself down after the 30 second warning.
If you've fixed this can you please detail me through the steps.

Hard brick

Hey their. So i jsut bought a one plus 6t and started playing around iwth it. I tried to get twrp and i got it but when i rebooted to os i had no wifi. So i download magisk zip and flashed it. After this i got stuck in bootloop and so i wne to twrp and wiped everything except system. Then i rebooted and got this message Qualcomm CrashDump Mode Attempted to kill init! exit code=0x0000000b do_exit. Then i freaked out and accidently wipes system too. Now i think i have a complete brick as adb still works but i cant transfer any file from pc to phone because theirs no system. Please help!!!
Never wipe system and vendor on A/B devices, literally, never.
Boot twrp and flash OOS or use msmdownloadtool.
What do you mean flash OOS. Like flash a fastboot file? And what version of msmdownloadtool should I get as their is no system. Should I get 10 cause that was my last system or it doesn't matter.
Update. I left twrp after flashing a stock image and now adb doesn't recognize my phone. When booting into recovery I go into the one plus recovery. Now I'm really screwed.
Okay now im really screwed. Whenever I boot with power up or power down I get sent to the bootlaoder page that says fastboot mode products name. I cant leave this page however. On the options above the information I click reboot recovery I get sent back to this page.
UPDATE. My phone is a literal brick now. It won't even turn on. I tried to force reboot it before and after it powered off it wont turn on. Its fully charged and when connecting to charger of holding buttons nothing happens. I have no warranty so Im hoping that someone can help me.
The "bootloader page" is fastboot and that's normal because there's no system to boot, you wiped that partition... and ADB only recognizes the phone when the boot process ends and ADB is enabled in the phone.
If you press vol up + down when you connect the usb cable the phone boots in EDL (Emergency Download Mode) mode, long press power + vol up to leave that state.
Now, download msmdownloadtool from here, extract the file, power off you phone, conect the usb cable to your pc, press vol up + down and connect the usb cable to the phone, open msmdownloadtool and flash the OS.
Edit: Read this thread for more detailed instructions.
What do you mean by flash the OS. The OS in the system or do I have to download one?
whenever I plug in my device it vibrates and then goes into the fastboot page. Also adb can detect it if I type in fastboot devices.
So i go the device to work and MsM worked until 4 seconds and then It said param preload for status of connection and status of last communication says device not match image
Try with the fastboot ROM.
When i downloaded another version of MsM it did not say no image match instead it stays at 4sec and says recording download time
Can you give me instructions on how to use the fastboot room? Like after i download it what should i do with it?
Download the rom, unpack it, boot your phone in fastboot (Power + vol up + vol down), connect the phone to your pc and execute the "flash-all.bat" file, and just wait.
um what is flash-all... How does it work what am i supposed to do.
what does unpack it mean?
Hey their im going to assume you meant to unzip the file and then open the file called falsh-all.bash. In that case when i do that i get this message "error: failed to load 'images.zip': No such file or directory
Press any key to exit..." In a CMD window

Note 7 stuck in bootloop after failed flashing attempt. Can't get into fastboot.

ood morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.

Categories

Resources