This is my second Samsung. I have put over a dozen different ROMs on my old Exhibit II 4G. Having said that, I realize many of you know more than I could ever hope to know. That is why I'm posting here. I have searched, but most of my searches take me to announcements of new CWM and TWRP recoveries.
I've had a Samsung Galaxy S4 Google Play Edition for over a month and still did not have a nandroid backup, so last night I installed ClockworkMod ROM Manager with the intention of flashing CWM Recovery. The app did not list my phone, so I told it to show all devices, where I found the i9505 (I don't remember if it was the i9505g or not). I told it to flash ClockworkMod Recovery, and selected the option that I had not yet flashed CWMR. I then used QuickBoot to reboot into recovery, where I performed my first nandroid to the microSD card.
When I rebooted after making that nandroid, it went right back to ClockworkMod Recovery. Subsequent reboots did the same thing. I could get into Odin mode with VolumeDown+Home+Power. Using Odin v3.09 I was able to flash the stock recovery. This did not resolve the boot-loop issue. Now it boots into the stock recovery, which is less functional than CWM. To me it is behaving as if the recovery tools were flashed to the /boot/ partition, or something is telling it to always boot from the recovery partition.
-In stock recovery, it will download ADB installations (from "apply update from ADB"), but every attempt fails it's signature verification. I have tried 6+ files, all have failed. I believe that the device has USB debugging enabled, but I cannot check while in this state.
-Stock recovery does not mount the microSD card, so I cannot install from there. CWM would mount the microSD card, but I did not think to try installs from the microSD at that time. Is it possible that I installed the wrong stock recovery?
-I do not know how to perform an ADB "push" with my phone in this state. To be honest, I have never done an ADB push. If I get to that stage, where on my S4 should I send a pushed file? "/system/bin"?
-If I try an adb push in this mode
-How do I get my phone to boot from the proper partition?
-If I have the wrong data in that partition, how do I get the correct information onto that partition?
Here is what it does when I try to sideload from stock recovery:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify while-file signature
E:failed to verify while-file signature
E:signature verification failed
Installation aborted
Thank you in advance for any help!
Solved - i9505g soft-brick/boot-loop
My problem was resolved by flashing a stock recovery and ROM, found here: http://forum.xda-developers.com/showthread.php?t=2569510
The package named "I9505GUEUBML4_FULL_ROOTED.tar.md5.gz" flashed from Odin is what worked.
Related
I'm updated to DI09 and rooted.
I installed Ti Backup and Rom manager
and also did odin flashing CWM recovery.
I got aborted msg few times, and tried again while installing CWM.
When it went thru alright, CWM installed, then bluetooth not working.
it keeps saying turning on then goes back to off mode.
before CWM installed, (after rooted) bluetooth working fine but if I install CWM then bluetooth not working.
I had to flash original stock back then did all the steps again to go that point.
I'm now stuck here "currently not trying to install CWM because I need bluetooth working!"
Anyone has an idea?
PLEASE HELP!!
Not sure which CWM .tar file you flashed, but I would suggest you flash this one. It has been modified for DL09. Once in recovery, I would recommend that you wipe data and cache. Reboot and BT should work fine
wow i just tried it and BT and CWM both working fine!! THANK YOU!!! =]
OMG, another prob is coming up!
after I successfully installed CWM, I launched Rom manager and clicked "flash CWM recovery(?)" and then selected Samsung Fascinate.
then I clicked backup current rom, the screen went to recovery screen says
"Installation aborted" so I chose "apply sdcard:update.zip" then this coming up
"Istall from sdcard...
Finding update package...
Opening update package...
Verifying update pakage...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
What did I do wrong?
maybe I shouldn't have clicked flash CWM recovery from rom manager?
Can't backup current rom!!! =[
Nevermind! Find the solution from another thread!
I've had problems with my phone for a while now, no stable roms or mods, phone doesn't wake up from deep sleep, lagg....
So I got in to recovery mode (latest TWRP) a few hours ago and I got asked for a password? :S didn't know that TWRP had a protection function.. I pressed BACK and that was that, I got in to the menu and pressed INSTALL but the SDCARD was empty?
Using the filemanager in TWRP the internal SDCARD was still empty, but the microsd worked fine.
After rebooting the phone I got stuck on the sgs4 screen, so the rom didn't boot.
I went back to recovery and wiped everything possible and formatted the sdcard, afterward I installed a rom and rebooted.
Still the same problem, got stuck on the sgs4 screen.
In TWRP the sdcard was still empty. So I downloaded a odin flashable rom and flashed the phone through odin but got stuck at the same place.
I now have the stock recovery and when selecting "apply update from external storage", I get the error message:
"E:failed to mount /sdcard (No such file or directory)"
Is there any function in a TWRP/CWM or modded recovery that can fix the internal sdcard?
Or perhaps repartition everything?
Just to let everyone know, the flashing in odin and TWRP worked as usual, so the system/data etc partition as fine.
Guess it's the sdcard partition that's corrupted OR if TWRP somehow locked the sdcard because I didn't enter a password?
I could be wrong but then I'm completely clueless.
Appreciate some help, thanks!
EDIT: [SOLUTION]
Since there is no way to use adb in recoverymode or downloadmode (I wasn't able to), you need to use odin.
1. Enter download mode and flash a clean rom through odin.
2. Enter download mode again and flash TWRP through odin.
3. Wipe DATA through TWRP and reboot.
4. Factory Reset through TWRP and reboot.
5. Done.
Seems like this is the wrong place to ask, but I think I found the problem.
It was TWRP with their "password protection" that cause the problem.
Downgrading to other versions wont help as it did for others with the transformer pad.
I did a search for "TWRP PASSWORD" and it looks like TWRP has a bug.
This is what I get in TWRP:
E:Mount: Unable to find partition for path '/sdcard'
EUnMount: Unable to find partition for path '/sdcard'
This is definitely the last time I'll use TWRP.
When flashing CWM, I'm unable to boot into recovery, only works with TWRP..
I'll keep posting here until I solve this if anyone get the same problem.
http://forum.xda-developers.com/showpost.php?p=44007919&postcount=1
In the link above, someone manage to fix their phone with the same problem I have, even though it's the nexus7.
So what I've learned is that I shouldn't let TWRP root my phone.
I need a system.img file, could it be just the system parititon? Don't know how to get that file, so could use some help.
EDIT:
I'm going to unpack a odin package, found a system.img.ext4 in there, guess that wont help so have to find one with stock filesystem.
Hi,
I'm at my wits end. I had SlimRom installed for a week and all was fine, but I was curious about what new ROMs were out there so I backed up my phone using ROM Manager and did all the usual stuff to get a new ROM. I installed Gummy, but didn't like it; I installed one other ROM that I can't remember its name, but also didn't like that. I realized my comfy home of SlimRom was where I wanted to be, so I tried to flash the backup.zip that I had created but it kept saying installation aborted (Status 0).
After hours of countless attempts and just weird behaviour (sometimes boot loops, sometimes not booting into recovery, etc.) I finally got my phone back to stock.
I downloaded the latest SlimRom file 3 times to make sure it wasn't a corrupt zip (twice from my PC and once from my phone directly). Both the zip directly from Slim as well as the backup.zip that I made with ROM Manager give me the same installation aborted. The other error it gives is "E: Error in /data/media/0/slim....zip". I'm wondering if somehow my partition is screwed up. I tried using Odin's repartition, which just erased my recovery partition, but I got that back thankfully! When I wipe data/factory reset it says wipe complete (and the ROM does reset to factory) but it also says "E:unknown volume '/sdcard/.android_secure' "...I'm wondering if that relates to why the backup.zip file won't read properly. Maybe the partition got screwed up somehow?
I can flash a SU zip so it's not a flashing problem, per se. And thankfully Odin always works!
I think I may need the stock PIT file for the Telus S4 l337m
UPDATE:
I think I found the proper pit (SGS-I337_16GB) but my phone says "secure check fail: pit".
Hello XDA Developers,
I had a device that was rooted on stock rom and recovery. What happened was that an OTA was installed and it went to the "boot verify certification" screen. I had to install Ubuntu to get TWRP running again.
I'm able to boot into TWRP, and I tried installing different ROMs, using adb sideload, from Stock ROM, ParanoidAndroid, and Madri-ROM.
The first one was able to install, but when I reboot the phone, I get stuck on the LG logo. I wait for an hour and it still does not do anything.
So now I try the other two custom ROMs, and I get an error saying "E:Error executing updater binary in zip "... .zip".
Then it reads "Error flashing zip '... zip'.
My question is: What else can I do to get this phone working again? I would like stock ROM, and preferably stock recovery back (Recovery is secondary).
Thanks in advance,
DaAznMan
Note: When I use adb sideload, the .zip file that gets transferred becomes a file called 'sideload.zip'. Is that correct? If not, what do I need to do to fix it?
Hi Guys.
I recently noticed that I couldn't create a backup with TWRP. Firstly, I thought it was a TWRP problem, as I had some issues installing it after the B588 update. So I flashed it again, but nothing changed. When my back up would reach about 70%, it would give me a reboot. Then I tried to install B588 again, to fix any errors. Although, I flashed it correctly, when I tried to restore the back up I had through Huawei's app, I got an unexpected reboot. So I decided to intall sokkoban's rom. During my first attempt to copy the zip files, it stoped the process. So I took the files directly to the SD card (with an adapter and not via usb cable). I re-flashed TWRP and then entered recovery, to flash the zip files (I am only able to enter custom recovery, only through xposed modules and adb commands since my latest update: 01-01-2017). After managing to enter TWRP, I tried to clear everything, but I got an error:
The message was: mkfs.fat /dev/block/mmcblk1p1 process ended with ERROR: 1 Unable to wipe sdcard. (just in case the image is not visible)
Can anyone help with this?
Currently I am trying to install the ROM ...
spirto82 said:
Hi Guys.
I recently noticed that I couldn't create a backup with TWRP. Firstly, I thought it was a TWRP problem, as I had some issues installing it after the B588 update. So I flashed it again, but nothing changed. When my back up would reach about 70%, it would give me a reboot. Then I tried to install B588 again, to fix any errors. Although, I flashed it correctly, when I tried to restore the back up I had through Huawei's app, I got an unexpected reboot. So I decided to intall sokkoban's rom. During my first attempt to copy the zip files, it stoped the process. So I took the files directly to the SD card (with an adapter and not via usb cable). I re-flashed TWRP and then entered recovery, to flash the zip files (I am only able to enter custom recovery, only through xposed modules and adb commands since my latest update: 01-01-2017). After managing to enter TWRP, I tried to clear everything, but I got an error:
The message was: mkfs.fat /dev/block/mmcblk1p1 process ended with ERROR: 1 Unable to wipe sdcard. (just in case the image is not visible)
Can anyone help with this?
Currently I am trying to install the ROM ...
Click to expand...
Click to collapse
This error is quite normal.....I have got this many times wiping everything and this isn't an issue...
With reboot during restore I think that your backup is corrupt at some point