I can get my one plus 3 into fastboot mode but that is it, I have tried wiping the cache and user data from there, I have tried flashing both the stock recovery and TWRP, everytime I try to boot into recovery I get a few seconds of the boot screen and then nothing?
Any help would be wonderful, if you need more info let me know,
Mac
I had a similar problem as you, managed to get into fastboot, but no recovery at all, neither stock nor TWRP. Flashing TWRP again didn't help, although process ended successfully.
Same thing for flashing the whole ROM.
What saved me from getting remote support from OnePlus was this wonderful HOW TO:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I lost all data, but it's a price I payed gladly in order to get my OP3 back
Good luck
McreativeH said:
I can get my one plus 3 into fastboot mode but that is it, I have tried wiping the cache and user data from there, I have tried flashing both the stock recovery and TWRP, everytime I try to boot into recovery I get a few seconds of the boot screen and then nothing?
Any help would be wonderful, if you need more info let me know,
Mac
Click to expand...
Click to collapse
After flashing, try to boot directly to recovery by pressing the button combination.
I got it to work in the end by flashing CM recovery and then working my way from there
Related
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
I'm in an interesting predicament...
I tried flashing this rom but some how flashed boot.img incorrectly
Now my phone wont go past the boot image but I am able to get to recovery. I tried factory resetting / cache wipe / restore but it doesn't work. My best guess is to get to the bootloader and re-flash a boot.img to a stable rom. Thats where my problem lies.
How do I get to the bootloader? I can't power of the device because every time it restarts into recovery and I've tried holding vol down + power during these restarts but that doesn't work either.
Any suggestions?
[nvm: It was all about timing ]
shamy1000 said:
I'm in an interesting predicament...
I tried flashing this rom but some how flashed boot.img incorrectly
Now my phone wont go past the boot image but I am able to get to recovery. I tried factory resetting / cache wipe / restore but it doesn't work. My best guess is to get to the bootloader and re-flash a boot.img to a stable rom. Thats where my problem lies.
How do I get to the bootloader? I can't power of the device because every time it restarts into recovery and I've tried holding vol down + power during these restarts but that doesn't work either.
Any suggestions?
[nvm: It was all about timing ]
Click to expand...
Click to collapse
Hi friend,
I came across the exact problem of yours and spend hours to search thru the internet for answers. This case is rare but not so difficult to solve.
I suggest you read this thread in One X, it is the same as One V.
http://forum.xda-developers.com/showthread.php?t=1609190
I figured out the problem in the wrong boot.img. You can choose the boot.img of the ROM you installed, extract it and do as follow:
Boot into bootloader
- fastboot flash boot boot.img
- fastboot reboot-bootloader
- fastboot erase cache
To get into bootloader, you SHOULDN'T CONNECT the USB Cable into the computer, just unplug, power off (by long press the power button, at least 10 seconds, sure, you can). Then power-on + volume down, I am sure you can get into bootloader. Then, you fastboot to carry out all the process.
Reboot again into the Recovery. Clear/Wipe all cache, data, then restore or install new ROM from zip files, reboot.
DONE.
Wish you good luck, friend.
He solved his problem on 3rd Aug
ckpv5 said:
He solved his problem on 3rd Aug
Click to expand...
Click to collapse
Wua, haha, that's great. One more of my question, is the boot.img file is just "fitted" for its own ROM? I mean, for example if I extract the boot.img from MIUI.us ROMs, can I flash it for SuPrimo Rom ?
I can't give a concrete answer for that. But generally a CM based ROM and Sense based ROM use a different type of boot.img so it is best to use the one that comes with the ROM.
jacky_fgs said:
Wua, haha, that's great. One more of my question, is the boot.img file is just "fitted" for its own ROM? I mean, for example if I extract the boot.img from MIUI.us ROMs, can I flash it for SuPrimo Rom ?
Click to expand...
Click to collapse
Currently, they are the same
Sent from my One V using XDA
Similar problem
Hi, I am quite new here and have spent ages searching the forums.
I have a HTC one s and was in the process of installing cyanogenmod 10 via CWM, fairly straightforward but it appears as though the boot.img file just didn't transfer at all. So now i am stuck in CWM recovery, cyanognemod if i try and load but it is endless or bootloader. Worse is when i connect my phone to my laptop it is not recognised (it may be due to drivers, i cant find the driver for whatever state my phone is in). abd devices yields nothing. I have a ghost image of my phones drive in windows, unopenable. When in CWM i can't find my sd card, it gives E: can't mount /sdcard/.
I am really stuck.
I would happily take a fix or back to stock. ANYTHING.
Thanks in advance
ph324 said:
Hi, I am quite new here and have spent ages searching the forums.
I have a HTC one s and was in the process of installing cyanogenmod 10 via CWM, fairly straightforward but it appears as though the boot.img file just didn't transfer at all. So now i am stuck in CWM recovery, cyanognemod if i try and load but it is endless or bootloader. Worse is when i connect my phone to my laptop it is not recognised (it may be due to drivers, i cant find the driver for whatever state my phone is in). abd devices yields nothing. I have a ghost image of my phones drive in windows, unopenable. When in CWM i can't find my sd card, it gives E: can't mount /sdcard/.
I am really stuck.
I would happily take a fix or back to stock. ANYTHING.
Thanks in advance
Click to expand...
Click to collapse
You should post this in One S forum mate
http://forum.xda-developers.com/forumdisplay.php?f=1570
See : http://forum.xda-developers.com/showthread.php?t=1630459
hi there had rooted my phone just after xmas and yesterday decided i would try to install a custom rom for the first time. i used twrp and installed some apps with it no problem i then tried to flash my rom and all seemed ok tried to reboot and intro screen just kept looping now i only seem to be able to boot into odin mode or watch the intro loop. is there a way to recover from this/, flash a rom from a pc or have i had it and its now a paper weight? thanks for any help given guys.
mac
bgmacmck said:
hi there had rooted my phone just after xmas and yesterday decided i would try to install a custom rom for the first time. i used twrp and installed some apps with it no problem i then tried to flash my rom and all seemed ok tried to reboot and intro screen just kept looping now i only seem to be able to boot into odin mode or watch the intro loop. is there a way to recover from this/, flash a rom from a pc or have i had it and its now a paper weight? thanks for any help given guys.
mac
Click to expand...
Click to collapse
make a full wipe if not reflash the ROM again.
Hope I helped
Sent from my GT-N7100 using xda app-developers app
bgmacmck said:
hi there had rooted my phone just after xmas and yesterday decided i would try to install a custom rom for the first time. i used twrp and installed some apps with it no problem i then tried to flash my rom and all seemed ok tried to reboot and intro screen just kept looping now i only seem to be able to boot into odin mode or watch the intro loop. is there a way to recover from this/, flash a rom from a pc or have i had it and its now a paper weight? thanks for any help given guys.
mac
Click to expand...
Click to collapse
Boot into recovery (power the device and press power + volume up + home at the same time), do a full wipe (wipe cache partition, wipe data/factory reset, format system, format preload) and make sure that you read the Rom's thread just to see if some additional step is needed and then reflash it. Flashing a new rom without doing a full wipe are the usual cause of bootloops. Take into consideration that you will lose data this way.
If you can't access recovery, then try booting into download mode (power + volume down + home) and flash an stock firmware with Odin PC.
Hope it helps...:good:
wash, rinse, repeat
Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.
I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.
First of all check out this thread http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835. I had a problem with my phone because i rooted it, and i wanted to apply an ota so i unrooted and applied the ota, but that got me stuck in a bootloop. So i went to the thread above and did what the instructions said. Everything was fine until i started getting force closes on gapps and most apps on my phone, so i decided to reflash the system with the prerooted image from the link above. I did this and i decided to go into recovery from bootloader in order to format data as this stopped the force closes the first time. When i booted into recovery i got the same old android logo that says error, only this time it was blinking and i couldn't get into the recovery; I then force shut off the phone and tried to boot up normally but i got the same error android guy flashing again. So since i couldn't get into the stock recovery then i tried http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063. This cwm recovery booted up fine after a minute or two. Once in there I went down to wipe data/factory reset; It completed the process and i rebooted and there was no error this time, the phone booted up normally.
If anything similar happens to someone try first the guide in the first link, then the second link if you can't get into recovery.
I hope this helped someone with the same circumstances.
@Ratedzelaya, hey, it was good of you to share your experience with all people. Btw, you required CWM to do a factory reset, right? And that factory reset fixed the phone for you, right? Well, if that's the case, you could simply boot to bootloader mode, and then issue these commands to do a factory reset:
fastboot format userdata
fastboot format cache
No need of recovery in this case, and the device should be fine as per your method. Just sharing my opinion! Having CWM recovery isn't bad anyway
itskapil said:
@Ratedzelaya, hey, it was good of you to share your experience with all people. Btw, you required CWM to do a factory reset, right? And that factory reset fixed the phone for you, right? Well, if that's the case, you could simply boot to bootloader mode, and then issue these commands to do a factory reset:
fastboot format userdata
fastboot format cache
No need of recovery in this case, and the device should be fine as per your method. Just sharing my opinion! Having CWM recovery isn't bad anyway
Click to expand...
Click to collapse
That's helpful information in case I ever need it. I'm not the most familiar with fastboot or adb.
Ratedzelaya said:
That's helpful information in case I ever need it. I'm not the most familiar with fastboot or adb.
Click to expand...
Click to collapse
it's full of tutorials here,just search
Bro im not really familiar with bricked devices,
But may i ask again about what happened in your device
are you sure your device it is considered hard bricked not soft?
Just asking )))