Sorry if this is a double post but I need help badly
I cannot get any recoveries to work on my OnePlus 3. Not even stock. Ill flash twrp to it and it will say successful but I cannot boot into it and using fastboot boot twrp.img says it works but my phone just hangs at the fastboot window and then crashes so I have to hard restart it.
Any suggestions on how to fix it?
Hello
As you said, youve already asked here so this thread will be closed
http://forum.xda-developers.com/general/xda-assist/oneplus-3-recovery-t3483564
Wait for one of our Assist team to point you to the right place to get help.
Thanks.
Related
I have messed up my lg volt it was on the stock rom zv5 and was running fine with root. I decided to flashify a deodexed version of my rom onto my phone, this of course went wrong as all my phone displays is the Lg boot animation with Fastboot in the top right corner i cant enter recovery mode as I have a bad recovery. I can open up the adb sideloader within Android System Recovery but have no idea how to get it to work as my command prompt does not recognize the command. I have tried a factory reset and rebooting. Help please I am getting desperate. FYI I am 14 and my knowledge on flashing is minimal.
XDA Visitor said:
I have messed up my lg volt it was on the stock rom zv5 and was running fine with root. I decided to flashify a deodexed version of my rom onto my phone, this of course went wrong as all my phone displays is the Lg boot animation with Fastboot in the top right corner i cant enter recovery mode as I have a bad recovery. I can open up the adb sideloader within Android System Recovery but have no idea how to get it to work as my command prompt does not recognize the command. I have tried a factory reset and rebooting. Help please I am getting desperate. FYI I am 14 and my knowledge on flashing is minimal.
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try to adb sideload a rom and flash it. Or fastboot flash a working recovery onto your device, and then sideload a rom and flash it. Or you may have to reflash stock firmware onto your device to get it to work. Here is a guide as to how to flash roms: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android. To sideload, the command is simply "adb sideload name of file" without the quotation marks. For further help regarding your problem, you can register and post your questions in the XDA help forum: http://forum.xda-developers.com/general/help.
Good luck!
after using command fast boot flash recovery boot.img my phn got stuck in blue light...command prompt shows' waiting for device'..how long it will take to flash twrp or am i got stuck!!!pls help me
XDA Visitor said:
after using command fast boot flash recovery boot.img my phn got stuck in blue light...command prompt shows' waiting for device'..how long it will take to flash twrp or am i got stuck!!!pls help me
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Does not sound like anything ill was done, as it did not connect. This could be a cause of one of three things:
Phone is not in the bootloader
Even if in the bootloader, fastboot mode is not activated
PC drivers for fastboot may not be appropriate (or maybe even an outdated fastboot program)
To help you further, can I get the make, model and carrier (if bought through said carrier) of your phone?
Many thanks.
I mistakenly flashed twrp as an update in flashify, after that both startup and recovery mode shows "Invalid boot image". I managed to fix the startup by flashing the compatible boot.img for my phone, while recovery mode is still like that. I can now open my phone but after that I can't turn on my wifi and hotspot and the camera is not turning on too. I tried to restore factory thought it might fix it but it directed me to "Invalid boot image" again. I really need some help right now. Someone know how to fix it?
Asus Zenfone Go ZB551KL
Aharu said:
I mistakenly flashed twrp as an update in flashify, after that both startup and recovery mode shows "Invalid boot image"...
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/asus-zenfone-go
With that stated...
I believe that you should be able to obtain some member guidance within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3282861
https://forum.xda-developers.com/showthread.php?t=3460995
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I GOT!
Comrade, I had the same problem, and at the expense of a lot of sweat, blood and tears, I got a IMG.
Here is the recovery.img of the ZB551KL, Enjoy
Code:
mediafire.com/file/tetjmun58gxm6mv/recovery.img
Code:
fastboot flash recovery recovery.img
lethemooca said:
I GOT!
Comrade, I had the same problem, and at the expense of a lot of sweat, blood and tears, I got a IMG.
Here is the recovery.img of the ZB551KL, Enjoy
Code:
mediafire.com/file/tetjmun58gxm6mv/recovery.img
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh wow, I forgot about checking this post because I replaced this phone quickly after that. I have 0% knowledge about flashing the time I posted this. Well, I just fixed it right now by doing EXACTLY that.
Quick recap what I did back then:
Thought of flashing TWRP recovery but I have no idea about adb, fastboot and stuff. Only used Kingroot and Flashify. My very first flash was a mess. Used twrp.img as an update which almost broke my system completely, revived the system by flashing stock boot.img but wifi, hotspot and camera doesn't work and recovery is missing. My dumbass back then tried adb, used
Code:
fastboot flash recovery
to flash boot.img IIRC (facepalm). That's when I thought the phone is now bricked and can't be fixed.
Now years passed I learned all about adb, I tried everything I can think of, installing root apps like kingroot or kingoroot so that I could flash again but failed, looked for a solution to unlock bootloader (oem unlock is missing) but only method that works is to downgrade firmware which is also a no because I don't have recovery.
Found a firmware with recovery.img but thought you couldn't even flash stock recovery through fastboot because bootloader is locked but I just did it because that's the last hope I got and IT WORKED. Figured fastboot recovery flashing is fine as long as it's the stock one. Recovery is back, flashed the latest firmware, phone system is now back to normal.
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
BikerFry said:
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
Click to expand...
Click to collapse
Try flashing the stock boot img, it should but back stock recovery, you should be able to do it in fastboot too.
BikerFry said:
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
Click to expand...
Click to collapse
Follow steps here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Sent from my OnePlus6 using XDA Labs
I can't flash anything. I get "Failed remote flashing is not allowed in lock state".
I can fastboot boot twrp so maybe could try flashing that way, but I can't get the phone to show up in windows explorer to transfer any files.
Wrong forum.
matze19999 said:
Wrong forum.
Click to expand...
Click to collapse
Sorry about that.
Might have just made a little progress. Learned the ADB Push command, loading an ota.zip and a boot image now. Hopefully can flash one or the other or both via twrp. Fingers crossed. Thanks either way guys.
tried Flash Image - boot image I had downloaded. It flashed successfully lol but I still can't boot the OS. And now I can't fastboot boot twrp either. ****. What have I done? lol. Come on it's android there has to be a way.
I appear to now be officially ****ed. Must have somehow been the wrong boot image, now I can't even boot into TWRP. I think I'm dead in the water. Can't flash anything, can't boot into TWRP. Any ideas? Will happily paypal a few bucks to anyone who can un**** me.
BikerFry said:
tried Flash Image - boot image I had downloaded. It flashed successfully lol but I still can't boot the OS. And now I can't fastboot boot twrp either. ****. What have I done? lol. Come on it's android there has to be a way.
I appear to now be officially ****ed. Must have somehow been the wrong boot image, now I can't even boot into TWRP. I think I'm dead in the water. Can't flash anything, can't boot into TWRP. Any ideas? Will happily paypal a few bucks to anyone who can un**** me.
Click to expand...
Click to collapse
have you tried the unbricking tool
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Will try it now. Thanks!
BikerFry said:
Will try it now. Thanks!
Click to expand...
Click to collapse
how are getting on with the unbrick tool ??
hallelujia the unbrick tool worked!!! So excited to be back making playing with the new toy! I was sure I was screwed, somehow didn't come across that tool in my googling. Thanks man. Imma kick a couple bucks your way with that donate button. Saved me from sending it back to oneplus and going a couple weeks without the new phone.
Now carefully...
BikerFry said:
hallelujia the unbrick tool worked!!! So excited to be back making playing with the new toy! I was sure I was screwed, somehow didn't come across that tool in my googling. Thanks man. Imma kick a couple bucks your way with that donate button. Saved me from sending it back to oneplus and going a couple weeks without the new phone.
Now carefully...
Click to expand...
Click to collapse
its fine my friend dont need the money just glad it helped ya :good::good::good::good:
Well thank you very much. I'm not too proud to freely admit I'm a happy kid with a new toy now. Thanks!
Hey guys,
I need some help with my phone. I tried to install twrp recovery on it, but I messed up.
Here's what I did: I unlocked the bootloader using "fastboot unlock" and then I flashed the twrp image using "fastboot flash recovery twrp-3.7.0_11-0-RMX1941.img". Then I tried to boot into twrp using "fastboot boot twrp-3.7.0_11-0-RMX1941.img", but it didn't work.
I should lock the bootloader again, so I stupidly ran "fastboot lock" without doing any research. Then I selected "recovery" from the bootloaders options, hoping it would boot into twrp. But instead, it showed me a message saying "the current image have been destroyed and cannot boot..." And now it won't boot at all.
Additionally, I can enter the recovery mode nonetheless, the error is still showing up and I'm unable to connect my phone to my PC using cable either anymore, so no fastboot.
Here's my hypothesis: I think this is just a soft-brick however, is there a way out?
Specifications: Realme C2, Mediatek (I don't know which MediaTek it is)
Did I brick my phone? Is there any way to fix this? Please help me out, I'm desperate.
I really appreciate any help you can provide. Ask me freely if you want some further information regarding this.
You have messed it up bad. You should NEVER lock the bootloader without restoring everything back to stock.
An unlocked bootloader allows you the flexibility to try several things to fix a bricked device. By locking it, you have put yourself in deep trouble.
I don't know if MSM tool will be of help here. Try your luck.
Peezzied said:
Hey guys,
I need some help with my phone. I tried to install twrp recovery on it, but I messed up.
Here's what I did: I unlocked the bootloader using "fastboot unlock" and then I flashed the twrp image using "fastboot flash recovery twrp-3.7.0_11-0-RMX1941.img". Then I tried to boot into twrp using "fastboot boot twrp-3.7.0_11-0-RMX1941.img", but it didn't work.
I should lock the bootloader again, so I stupidly ran "fastboot lock" without doing any research. Then I selected "recovery" from the bootloaders options, hoping it would boot into twrp. But instead, it showed me a message saying "the current image have been destroyed and cannot boot..." And now it won't boot at all.
Additionally, I can enter the recovery mode nonetheless, the error is still showing up and I'm unable to connect my phone to my PC using cable either anymore, so no fastboot.
Here's my hypothesis: I think this is just a soft-brick however, is there a way out?
Specifications: Realme C2, Mediatek (I don't know which MediaTek it is)
Did I brick my phone? Is there any way to fix this? Please help me out, I'm desperate.
I really appreciate any help you can provide. Ask me freely if you want some further information regarding this.
Click to expand...
Click to collapse
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com