My zenfone 4 was stuck on intel logo(no recovery,no droidboot) after which I directly used fastboot command to flash stock rom. It worked somehow(show devices command showed 0 devices) and phone booted normally but droidboot is still gone and factory reset option is also gone. Now I want to update from stock kitkat to lollipop I dont know how it will happen. Please help
I have same problem. No one can help??
I don't use the phone anymore but I found a solution to bring back the phone. Note: Dont use this method if your phone boots up. Try this as last resort if your phone does not boot. This will not help you update to lollipop, that problem still remains. Follow the steps in the post and I have attached the files I used(only for zenfone a450CG). If you get stuck at the intel logo use fastboot command "reboot droidboot" then flash the stock rom
https://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
Related
Hey guys, last night I tried to root my device (XT1058) following the guide [here](http://forum.xda-developers.com/moto-x/general/howto-root-moto-x-ver-4-4-4-xt1060-t3118342). Stupid me decided I wouldn't need to go back to stock ROM like it says in the first step. I continue with the guide, follow every step, until I reboot. After rebooting my Moto X gets stuck at the white screen with the blue circle M. I panicked, read a lot of things online, followed them, and nothing worked. I reset the cache partition in recovery mode when rebooting into fastboot, still nothing. I also noticed that my device is no longer detected in ADB at all, even in fastboot. So after just giving up, I read online in multiple places going to recovery mode, and wiping the whole phone/factory resetting would fix it. It still is not recognized by ADB or finishing booting. I realize I should've been more careful. Please help!
First thing... when the phone is in Fastboot AP menu, you can't use ADB. ADB wont work and wont see your phone unless the phone is fully booted. (i.e. adb.exe and fastboot.exe use two different modes on the phone).
Next, I've seen that symptom before, but I don't recall how to fix.
I would really consider asking in the thread for the process you were following.
If no one gives you any suggestion, you could always try re-flashing the stock image for your phone that matches the highest version you've had installed on your phone. (On fastboot screen you can see bootloader version, so match you stock version to that. see the list of known bootloader versions at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 ) And use mfastboot to flash it (follow option 5 in the 2nd post at -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
I'm pretty sure I saw this on reddit. You had a mac right?
You need fastboot installed on your mac:
http://forum.xda-developers.com/showthread.php?t=1917237
Assuming you have fastboot working on your mac and your phone this thread method two:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Use fastboot instead of mfastboot for the sytem.img file.
If you receive an error with flashing system you could try:
Code:
fastboot -S 0 flash system system.img
If u can still enter recovery mode, factory data reset from it , if u can't boot still after resetting , u have to flash the full stock ROM.....
Sent from my HM NOTE 1LTE using XDA Free mobile app
Hi everyone
Since I restarted my phone last night, my phone has been in a endless bootloop and I can't even enter recovery, without it rebooting again and going into the same endless bootloop again, around 2 seconds after showing the "Teamwin" logo.
I'm using ARHD, and if I remember correctly it's version 71.1. TWRP is "openrecovery-twrp-2.6.3.3-m7" and running ElementalX kernel.
I expect my partition is somehow corrupted, but I'm at a loss of ideas as to how I can recover my phone again. I would apreciate if I could somehow manage to make a backup of my data, but it that's totaly hopeless, I'm thinking of going for the ArtMOD ROM instead and starting fresh.
Is there a helpfull soul out there, that could maybe give me some insights as to what I can do from here? Thanks in advance!
I was hoping I could install a stock ROM and start from scratch again, but I somehow suspect having used a modified ROM has gotten me in trouble now and the ROM Upgrade utility sees this as a downgrade. I've not been able to find a newer ROM for the .401. series than "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". Although the updater believes I'm updating from 4.19.401.11 (the ARHD ROM).
I can get into FASTBOOT USB and the phone goes to the black HTC logo screen when trying to update, but quickly fails on the PC during the process at "Updating 1/5". When unplugging the USB cable the phone shows:"
RUU
Security fail!
Update Fail!
I've attached two screenshots, to better explain
Can some kind soul out there please help me getting a working phone again? What ROM I'll end up with doesn't really matter
Since you're using unlocked bootloader, why don't you try RUU to get back on Stock ROM.
Here is the collection of ROMS
Download your ROM.
from Windows Command prompt
adb reboot bootloader #
If it didn't work, Press and Hold Power button along with Volume down of your phone,
When you reach to bootloader, get into fastboot mode.
Now follow the following commands to restore the STOCK Rom. (make sure your downloaded ROM are in the same directory where you have fastboot.exe, abd, and abdwin.api etc)
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip RUU.zip (RUU.zip is of course your downloaded Stock ROM). If it says Failed, try again.
4) fastboot erase cache
5) fastboot reboot-bootloader
6) fastboot reboot
Good Luck
Hope that helps.
Thank you so much for helping out!
After several tries, tries and retries, I finally managed to get the phone back up and running with the stock ROM. I believe what finaly did the trick, was to use "fastboot oem lock" to get the stock ROM installed. From here, I'm now able to unlock it again and install a custom recovery (TWRP) and ROM (I went for ARTMOD). Thanks again!!!
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
how about this, adb NEVER EVER works in fastboot mode. that is reserved exclusively for fastboot. you have to use fastboot to flash a recovery, then the recovery to flash supersu.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
now it also seems as you have to fastboot flash a factory image as well.
turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: link removed to satisfy forum policy...
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
I asked for help before searching thoroughly enough! I figured out that I needed to download another ROM, transfer it into the phone's storage, and install using TWRP. I really didn't understand the capabilities of this fabulous application and had simply flashed it because the thread instructed me to.
Thread Closed
tell what you did, to brick phone.
what android version was before, what android wersion you tried to instal, what recovery you used. ?
oh, but if fastboot isnt working, you more or less are done. if im correct, even dc phoenix use fastboot..
"Step 1
Write compatible UPDATE.APP file in fastboot with DC Phoenix"
Arnys said:
tell what you did, to brick phone.
what android version was before, what android wersion you tried to instal, what recovery you used. ?
oh, but if fastboot isnt working, you more or less are done. if im correct, even dc phoenix use fastboot..
"Step 1
Write compatible UPDATE.APP file in fastboot with DC Phoenix"
Click to expand...
Click to collapse
i just use the SRKTool Lod Chan and try to unlocked the bootloader
and it success , after that i proceed to replace recovery with TWRP
but doesn't work . afterwards i bring back to re-lock bootloader
then the phone reboot . the phone stuck at android boot logo
no recovery no fastboot cannot identify even in PC
but when the phone gets drain and i plugged the charger on it
the phone reboots directly into the system or its OS
but when i try to power it off again ( reboot )
the same thing happen it will stuck in the boot logo
until the battery dries again ,.
i never upgrade to Nougat so my phone still in Marshmallow version
thank you .
vinfrix said:
i just use the SRKTool Lod Chan and try to unlocked the bootloader
and it success , after that i proceed to replace recovery with TWRP
but doesn't work . afterwards i bring back to re-lock bootloader
then the phone reboot . the phone stuck at android boot logo
no recovery no fastboot cannot identify even in PC
but when the phone gets drain and i plugged the charger on it
the phone reboots directly into the system or its OS
but when i try to power it off again ( reboot )
the same thing happen it will stuck in the boot logo
until the battery dries again ,.
i never upgrade to Nougat so my phone still in Marshmallow version
thank you .
Click to expand...
Click to collapse
what wersion of twrp ? link. there are MM and N versions, and, if you on MM put N version twrp, you will brick phone.. and, even with dead battery i was able to enter fastboot, when i instaled wrong twrp. but for me solution was simple, instal right twrp and all was good (ofcorse if you didnt delete system)
i can't remember the version but im sure it all arounds in 2.1...something
no i wasn't load the Nougat version because i know i am MM the only thing i remember is the TWRP i load is from SRKTool Lod Chong there was an option there to install twrp recovery
can i be able to enter the fastboot ?
if i can go over to fastboot i can repair this
but i can't go fastboot
volume rocker technique doesn't work
even using adb reboot bootloader too
when i am doing volume down ( hold )
the phone only vibrates then stuck at logo
even when its connected to adb command
when the phone reboot it stuck at the logo
can't go to fastboot ?
is there any way of forced
reflash the boot.img & recovery.img?
Hi, i have P9 L19 with C432 B210 i want to update do Android 7, but mistakely put wrong UPDATE to phone memory. Now I'm stucked at Huawei logo and cant turn off device.
Only I can get to Fastboot&Rescue Mode. After press all three buttons nothing happened, phone juest restarts and stuck at logo. I tried put right UPDATE to SD card but no luck
Bootloader: locked
FRP: locked
debbuging: off
Please help me.
no one knows how to fix our problem so sad
Please close the thread
problem issue solved!
please help me same problem as you...
JCB117 said:
please help me same problem as you...
Click to expand...
Click to collapse
Easily Unbrick Your Phone via this method
https://forum.xda-developers.com/p9/help/huawei-p9-brick-easiest-to-unbrick-t3662350
Hi everybody
I need to find an update.zip to flash it on stock recovery and attempt to repair the phone system.
Long story short..
I restore my D415 (previously with Lineage 14.1) to stock firmware (KK) via KDZ file and LG flash tool, then update it to LP with LG Mobile Support Tool and everything was good, then i tried to root the device with the LG OneClick Root (which i used several times before to root my phone without problems) but i don't know what happened during the batch process and now Download Mode has been replaced with Fastboot mode and the device hangs on the T-Mobile startup screen, so i can't flash a KDZ file again to restore the phone without a Downlaod Mode. The fastboot mode throws "remote: unknown command" with every command i tried (except fastboot getvar all; which shows "unlocked: no") even reboot doesn't work.
Tried everything even booting on Qualcomm Qdload mode (shorting the phone with test points) to reflash the firmware files but couldn't succeed because QFIL, QPST Software Downloader and BoardDiag they all threw errors.
I can access the stock recovery mode by pressing home button when the "erasing" screen appears after selecting "yes" on factory reset menu, so i need an official update to try to fix this phone, don't know if its gonna work or if this is a hardware issue but at least i want to try. Buying a new one is very difficult for me right now.
Thanks for any help.