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:
Related
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
I have a d802 . I had cloudy1.3 and twrp 2.7 installed with autorec. I tried to update it using
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(from twrp page, with the latest img file).
But I coudn't access recovery, some error about security. Then I shutdown my phone and then it booted fine into system. I retried to access recovery but nothing.
So I decided to return to autorec, I installed it, I clicked "Flash Recovery" and now my phone doesn't boot in any way.
It show "lg security error" and then shutdown.
I can access download mode. Is there a way to fix my phone without deleting everything?
I'm sure the problem is the recovery, I was messing with it, can I bring my phone back and don't delete my configuration, photos, apps?
Thanks
I'm so happy!
I did it!!!
I managed to boot into recovery with the usual combination of keys (with the method that ask you if you want to format, but then you press power and it boot into recovery).
From there I saved everything using adb pull (Just in case). Then I dirty flashed Cloudy 1.3 and my phone is back !
I hope my experience can help someone
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
hi new here so i was trying to install cyanogen on my a300fu and i wiped my os etc and then i acciddently rebooted my phone and know it is stuck at the samsung charging screen not the green moving one) the static with the electricity help what i am gonna do?
1. you can use odin to flash the stock rom
2. you can use odin to flash TWRP
2b. when you enter TWRP, on the mount section, disable MTP, and ADB should see the device, meaning you can PUSH the ZIP file to it, and install it.
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?