I tried to install Loki TWRP on the ATT Galaxy S4 using a Jar file which would automatically install everything for you via PC.
Upon reboot, it goes to the downloading, do not turn off target screen.
Odin cannot find the device even after installing proper drivers.
Is there anything I can do or is the phone permanently bricked.
If your phone has a locked bootloader, you can't install cwm or twrp.
Was the phone running a stock 4.3 ROM or higher?
Related
Hello,
When i tried to flash the rom carbon all the phone does is sit on the carbon screen will not boot after that.
I just rooted my phone and i have a backup of the phone before i rooted it. But i can not get the phone to boot into the recovery mode. At the top of the screen it says booting recovery but never boots into the recovery mode. I have the Galxay S4 SPH-L720. I have tried to load a stock firmware via odin but its keeps failing.
Any help would be greatly apprieced. like i said i do have a full backup of my phone i just need to get it to boot into the recovery so i can restore it
Hi all,
I am not sure whether this the right forum to post my query. It's been a year a since I bought my S4 (i9500) so O thought of rooting and installing recovery on my phone. I was on stock 4.4.2 and I was able to root my phone using the CF-AUTOROOT, but after that when i am trying to flash a custom recovery using Odin it ends up in the download mode. I have disabled knox after rooting the phone and my phone status is now custom and so I cannot get any official update.Is there anything I did wrong which is forcing the download mode to overwrite the custom recovery I am tryjng to install???? Any help is highly appreciated.
Thank you,
Bobby Thomas.
Just boot into download mode. Uncheck auto-reboot in Odin and flash the recovery. That's it.
Thanks Lenny for your prompt reply, actually I did try that but after the manual boot it again goes back to the download mode instead of recovery mode....I even tried to install it through ADB shell but with no luck...I just goes to the download mode whatever I tried to do...
I was having a problem with the system trying to enforce the stock recovery every time I flashed TWRP through Odin. Turns out I got it by simply removing the battery as soon as Odin finished the job and restarted my phone. Waited for a few seconds, put battery back on and voila.
It worked for me. Do it at your own risk.
I also had the same trouble and had to untick auto-reboot, take out battery reboot back into download mode flash again. The first time I tried that it didnt work and the only way I got it to work was you Cyanogens windows installer, then went into recovery and flash the rom of choice.
What happens when you boot your phone, download terminal emulator from the market (or use adb) and type the following:
su
reboot recovery
ANY ideas would be appreciated.
So I tried to return to the original build.prop file as i had a backup of it. I had changed it so i could have s5 status bar.
So i replaced modified one with the original backed up file. Then rebooted.
But gets stuck/black screen after samsung initial boot anim.
Device is rooted with stock firmware and stock recovery.
Tried using latest adb to pull and push build.brop files or change permissions but device shows as "unauthorized" and there is no way to authorize it as i can't get past samsung s4 logo.
i CAN enter download and recovery modes. So i could flash stock firmware with ODIN but not certain it would fix build.prop issue. and download could take hours from samsung updates page.
i could try flashing custom recovery but not certain if this would help in any way.
Any adb command shows error: unauthorized device.
1. You can either reflash the rom you are on.
or
2. Flash a custom recovery. Then flash Aroma Filemanager from within the recovery. It will open a filemanager and you will be able to restore the backup you made.
Thanks for the reply Lenny. I have flashed a stock firmware through Odin and everything is up again. Just lost all my data but had some of it backed up. :good:
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
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..)