Hello,
First to get this out of the way i have searched the topic and there were several "solutions" none worked for me.
How it started, I downloaded the latest LieneageOS update as always, set the phone to do it's thing, came back and the phone was stucked on OP log, tried a little reboot, nothing.
No access to recovery or fastboot.
computer wouldn't recognize device even after installing drivers, this guide helped me a little https://forums.oneplus.com/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
found tools got fastboot back and original recovery.
via fastboot attempted to installed TWRP
fastboot flash recovery twrp****.img
and then tried to boot into recovery
fastboot boot twrp****.img
Not able to boot into twrp
after all that my phone still stucked on the boot OP logo
any help would be greatly appreciated.
Anyone has any idea, sorry I have been scouring and reading everywhere, but I can't find a solution.
Thank you
So i have been trying many things and finally getting somewhere. I apologize for the long post, but i have been trying so many things to get this device back to speed.
So flashing TWRP newer version for some reason is not letting me boot into recovery.
I have flashed twrp-2.8.7.0 and i am able to boot into recovery, however when trying to install the ROM (LineageOS 16) i get error E3004.
Searching the web i find that the correction is to that error is to update TWRP, thus i have tried flashing
twrp-3.2.1-0 and twrp-3.1.1-0 and once installed i am not able to boot into recovery again.
I flashed 2.8.7.0 and i was able to get in, thus from inside TWRP i did an image install of twrp-3.1.1-0 and rebooted, recovery won't load. I proceeded to repeat this until i get a result.
I flashed twrp-3.0.2-0 and be able to boot. However still not able to install LOS.
Once i tried flashing twrp-3.0.2-1, recovery won't load.
For sake of argument i flashed twrp-3.0.2-0 and attempted a image install for twrp-3.0.2-1, but the system still won't boot to recovery.
I have completely formatted the phone.
I hope someone could give me a little advice . Thank you.
Related
I'm having a problem getting into my recovery. I have the D800. It started out I sideloaded cwr thru twrp. And it said it flashed fine. I selected to reboot back into recovery and got a fastboot error. So i tried just rebooting and couldnt get passed the splash image. So I did the whole flash stock firmware. And after i got done with that, I think I did the ota update, And I got my phone rerooted. But still no recovery, it loads to a black screen and my pc says I have to format drives from like u-z but one has a folder titled image with these files. I've tried adb pusing and flashy and nothin,.Please help
never mind I got it fixed I think. Please delete post
All my beloved XDA memebers, I need your help badly.
I screwed up. I'm on TruePureX 6.0 but updated Super SU through TWRP (Popped up a message; I learned later the mistake I made).
1. The phone got stuck at Android boot screen and won't start.
2. I then researched to find out I could flash this SuperSU 2.62 version to get the phone started but nothing happend .
3. I then researched to find out I should fash a clean version of TruePurXMM as SuperSU 2.62 was not working for me. I used this thread
4. But this thread said TWRP 3.0 is minimum so I flashed that from my TWRP 2.8.7
5. I can no longer boot into the TWRP recovery mode as I'm getting fail to start up error on the recovery , Error: Failed to start the kernel
6. I'm not able to connect the phone to PC as the phone is not going in recovery mode and its not going passed the android screen due to super SU upgrade.
I'd immensely appreciate your help as I love my moto X and XDA tweaks, tips.
sarveshsj said:
All my beloved XDA memebers, I need your help badly.
I screwed up. I'm on TruePureX 6.0 but updated Super SU through TWRP (Popped up a message; I learned later the mistake I made).
1. The phone got stuck at Android boot screen and won't start.
2. I then researched to find out I could flash this SuperSU 2.62 version to get the phone started but nothing happend .
3. I then researched to find out I should fash a clean version of TruePurXMM as SuperSU 2.62 was not working for me. I used this thread
4. But this thread said TWRP 3.0 is minimum so I flashed that from my TWRP 2.8.7
5. I can no longer boot into the TWRP recovery mode as I'm getting fail to start up error on the recovery , Error: Failed to start the kernel
6. I'm not able to connect the phone to PC as the phone is not going in recovery mode and its not going passed the android screen due to super SU upgrade.
I'd immensely appreciate your help as I love my moto X and XDA tweaks, tips.
Click to expand...
Click to collapse
It sounds like you flashed the recovery to the boot partition instead of recovery. I would suggest flashing back to stock with fastboot, if you can get there.
Im in the same situation. was on my phone, it started freezing. i power cycled the phone and plugged it in. phone stuck on boot animation for several minutes until i powered it down and tried to go to recovery to wipe caches. however the phone stayed on the recovery boot image as well. finally got the phone to boot past the boot animation but was just on a black screen for several minutes. i need serious help. im already downloading the revert back to stock files just in case...please help!
thank you!
so I made a really bad dumb mistake, I flashed over a perfectly good twrp to try a cwm recovery out, and I did so after installing a linage rom not even sure one exactly but I remember reading something about "insecure adb" or something?..anyway, all was ok until the needless recovery flash, reboot after yielded no o/s and worse no recovery partition at all, it just boots straight back to trying to boot recovery, followed by the endless bootloop, I can boot download manually, but now my pc will not recognize the phone at all no matter what I do nothing changes just not recognized. my adb setup was working great I flashed the broken recovery with adb so can someone please offer me a clue as to where to go now cause I'm out of ideas. MANY THANKS for any and all help in advance.
Verizon phone ??
Try Verizon forum .
CWM well out of date and usage now .
I would start by flashing stock rom via Odin .
Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.
Hello
Sorry for my bad english
a few months ago, i decided to flash my first custom rom (One UI rom) and it worked fine
then i was testing a lot of other roms too until i tried lineage os 20
when i flashed lineage os 20, i decided to try another rom but i was stuck on the twrp logo screen. i tried methods of fixing it but none of them worked.
after trying a method of flashing twrp once again, it failed and i got stuck in a reboot loop and could only boot into download mode. so i booted into download mode and flashed a stock rom.
everything was working fine again until i wanted to try another custom rom. At first whenever i would flash twrp, they would always fail. but later i found the cause of that and fixed it. then, flashing twrp would always pass but my device would get stuck on a reboot loop once again and i had to flash stock rom again.
i tried rooting using auto root but it would show me a verification failed error and i had to reset my device. so now im stuck on a device which cannot flash twrp, nor can it be rooted. its been 1 month and i could not find a viable solution so any help would be extremely appreciated.
You have to just reflash your fastboot rom with fastboot mode unzip it and double click on flash_all.bat file or something like that
it is a samsung, there is no fastboot mode