This morning, there was an update for the Xposed Framework, tried to install it and installed via TWRP recovery. However after install and reboot, there is still notification on some components not installed so I decided to tick the Install automatically option in TWRP.
However, upon reboot and enter into recovery, I ended up being in boot loop
Now my phone is just flossing the Teamwin splash screen, so i assume that its going into boot loop.
I hope someone can guide me on what to do to fix the problem.
By the way, once connected to PC it is detected, however, ODIN and Kies seems not to detect the device
Tried demoing batteries, removing sd card but problem sis still there
Make sure u have the right drivers installed on ur computer so ur computer recognizes it.
My phone did this same thing the other day BC i was messing around with some files in Root Explorer anyway, after I got the correct drivers installed, I was able to fix it using an older version of ODIN (the new ODIN would not work for some reason), all I did was reflash TWRP and when my phone rebooted all my stuff was still there and nothing was changed.
Hope this helps.
Sent from my Sexy Samsung S5
Related
Delete
Nikolay15 said:
I tried to install twrp on my d802 and the first method didnt work ,so i tried the second and it looked like it had worked but when I rebooted in recovery it said :
boot certification verify
secure booting eror
couse: boot certifiction verify
and after that it goes to a black screen.
I also tried to boot into bootloader and it just booted up normaly. The phone works normaly it can boot. I am on kitkat stock rooted I also tried instaling other recoverys like cwm philz and other versions of twrp and it didnt work.
Shoud i try doing this http://forum.xda-developers.com/showthread.php?t=2582142 , or there's some easiar way
Click to expand...
Click to collapse
If you can get your PC to recognize your phone with the phone's drivers installed, then you have hope. If you can still get into android itself, install twrp installer from the Play Store. Update to the latest recovery from there (assuming your rooted).
If you cannot get into android, but when pressing volume up while plugging a usb cable connected to a PC in, your phone is recognized by the PC, you have to flash the stock KDZ file using the R&D test tool that floats around on these forums. It will unroot your device, but it will give you the chance to start clean and unharmed.
For me, I have to send mine in under warranty because now my G2 doesn't even pop up on Windows or Linux.
MDA400 said:
If you can get your PC to recognize your phone with the phone's drivers installed, then you have hope. If you can still get into android itself, install twrp installer from the Play Store. Update to the latest recovery from there (assuming your rooted).
If you cannot get into android, but when pressing volume up while plugging a usb cable connected to a PC in, your phone is recognized by the PC, you have to flash the stock KDZ file using the R&D test tool that floats around on these forums. It will unroot your device, but it will give you the chance to start clean and unharmed.
For me, I have to send mine in under warranty because now my G2 doesn't even pop up on Windows or Linux.
Click to expand...
Click to collapse
I can boot in android and i am rooted. I instaled twrp manager and it says that there's no compatble recovery with my device samo goes for goomaneger.
I tried to install stock recovery and it got me stuck on lg logo .
I instaled it with this comand dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I wanted to completely reformat my phone as my phone was buggy with Cyanogen Mod 12, so I formated everything.
The problem is that my PC was not detecting the drivers when in recovery mode, so I couldn't side-load with ADB, and I have no way of getting a .zip on to it.
I tried re-installing the clockwork mod using ODIN but it would just crash the application. I then tried heimdall and that said it installed it (I was hoping that it would fix adb)
Now I can't boot in to the clockwork mode recovery as it just instantly turns the phone off, however I can just boot normally in to the Galaxy S4 logo screen.
When I'm in the logo screen I do have access to ADB, however my phone is unathorised and I have no way to authorise it.
How can I A) fix clockwork recovery so it works again and B) put a zip on the phone or fix ADB detecting my device in recovery?
If you can get into download mode, flash a full stock ROM via Odin and start again
DSA said:
If you can get into download mode, flash a full stock ROM via Odin and start again
Click to expand...
Click to collapse
That worked great, thanks.
no probs, i find it to be a pretty good fall back in case of issues (just annoying reinstalling games etc..)
Phone "bricked"? Unable to detect phone via adb, or go to recovery. Suggestions?
Hi,
I was trying to sideload the new MM update over adb. Somehow it got stuck at 49%. So, I rebooted my phone and tried again. MM update was getting stuck at 49% every time.
So, I tried to reboot to recovery to install the update from there. But now, my phone is not going to recovery mode. It just shows me 4 options (Reboot, Install update, Wipe data, Power off). And install update does not allow me to select sd card, so I cant even choose the update.
When I try to boot normally, it just shows the first screen (Lenovo in white, with "powered by android" at the bottom).
I tried connecting to PC, but my phone is not detected by that K3 Note manager tool, or by Pda.net tool. So, I am not sure, what I can even do next.
Solved the problem. Had to flash the whole thing again using SP flash tools and old stock roms. Newer rom was not working for some reason.
Finally on 6.0. Sadly, lost all my settings.
Hey bro tell me how to flash the MM STOCK ROM I got stuck at 49% it shows install failed & gives only option for BACK & when I does the same It goes to Main Recovery screen. I don't know what to do even. Help me please
I basically ended up flashing the full thing from the beginning. See the attached text file for the steps I followed. Finding the tools is easy, just type the tool name on google.
Tools needed:
mt65xx drivers
SP flash tool
Stock rom (only the chinese version has full rom, so you have to download that rom).
After that, you can update the stock rom to marshmallow using the recovery.
Lenovo k3 note bricked. Unable to detect it via pc , On a bootloop , SP flash tool
I replaced recovery from twrp v3.0.0 to stock recovery using its image and my phone is in bootloop and when I boot my phone it shows the first screen . After a lot of research I found its the bootloop.
But the main problem is that SP flash tool cannt detect my phone so I am unable to flash it again and install new recovery in it. I have installed k3 note manager, pda net ,ADB driver and many other but still it's not working.
Can anyone help me out regarding this problem?
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 .
After I used ODIN to install successfully Magisk_patched_boot.tar as the first step in order to root my phone, I installed successfully Twrp_3.2.3-1_a750.tar but when I tried to reboot my phone, the logo of TWRP appeared for a few seconds and disappeared. I tried to reboot my phone in recovery mode using kies, but with no luck. The worst part is that my phone can't recognize by my laptop even though there are correct drivers.
Please, any help would be appreciated.