Hi everyone,
Pardon me if I'm asking in the wrong place, this is my first thread.
I just bought Samsung Galaxy Young CDMA SCH i509 and successfully rooted it. I'm looking everywhere for any custom recovery like CWM or RZ to Nandroid backup my phone so I can safely start tinkering with it. Although lately I found a CWM custom recovery that is said to be compatible with my device, but when I tried to Nandroid backup it made some installed applications disappear. And when I roll back backed up image to verify the result, it made my phone boot in infinite loop.
My question is:
since I can't find any working recovery for my device, is it possible to just unpack another Samsung Galaxy recovery.img and edit some files in there or do I have to compile it from scratch? Because I'm tempted to just edit it but I don't know its partition layout and anything
soulbkd said:
And when I roll back backed up image to verify the result, it made my phone boot in infinite loop
Click to expand...
Click to collapse
I suppose maybe you should focus on the bootloop first? I don't know an answer though. Sorry.
Did I helped you? Click the THANKS button! My Galaxy Mini would like it, just like I do!
Related
After a search I did not find anything specific to the S2.
I have read a lot over the past week but something I have not found is, if I switch to the ClockWorkMod Recovery is it possible to revert back to the original samsung recovery I currently have?
Thanks
Yes.
Just flash an original Samsung stock kernel again, and you're back on the original recovery as well.
Excellent.
Much appreciated HellcatDroid.
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps? Or some other advanced or custom restore?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
CWM Recovery Flash Zip - Not able to find zip on SD
Some progress here...
Since I think the problem is that I renamed framework-res.apk to framework-res.apk2, and since I had a backup of the original, I found and applied the following:
[GUIDE] How to make a cwm recovery flashable zip
Specifically:
Stuck my saved framework-res.apk into the archive in the correct folder (system/framework)
Renamed from sample.zip to update.zip
Copied update.zip to the root of my micro SD (went to buy one since I didn't have a working one)
Since the Guide didn't specify, I assume that flashing requires booting into CWM Recovery (in my case Clockwork 5.5) and using one of the "install zip from sdcard" options there. But it couldn't find the file. Here are my attempt outcomes:
- apply /sdcard/update.zip:
E: Can't open /sdcard/update.zip
(no such file or directory)
Click to expand...
Click to collapse
- choose zip from sdcard:
This just shows me the directory structure inside my phone
So how can I flash from a zip on the (external) SD card? I can't connect via USB except maybe with Odin, so I don't think I can put anything on my device.
No luck
Well, attempted the stock restore from Epic and still have a soft bricked phone.
According to the thread, everyone else is reporting success with Epic's version 4, but it's not working for me. Maybe I'm tired after 48 hours of this and I've missed something or am trying something that cannot work. No idea what's wrong.
I even resigned to losing everything (no backup) and starting over. Didn't think I'd have a permanent brick though.
Here is what everybody is raving about. CWM Recovery on all SGS3 LTE Variants
Will try again, just in case.
Any Luck?
I have done something similar...
I've been trying to find the stock boot from Rogers for the last 5 hours.
I can get into recovery mode and the download screen, but that's as far as I can get.
If you figure it out PLEASE let me know!
same boat
i just bricked my Rogers S3 with apparently a wrong ROM.
can't even get into recovery, totally bricked!
Were you able to find any solution?
Gave up and swapped hardware
I wasn't able to fix it. I was stuck between three useless boot options:
Regular boot - splash screen only and a vibration every few minutes
ODIN - showing that I had flashed the ROM 3 times
CWM - Clockworkmod's custom flash install, replacing the stock one
(Search the forums for the key combinations to get into these.)
I took it back to the store and they kindly replaced it. Glad they didn't know the key combinations. When they told me they needed an hour "to look at it" I thought I'd come back to a finger wag and a flat denial. That was a tough hour.
Make a backup, people; actually, I'm completely sure that a backup is enough. I'm still green at this.
snoops609 said:
I've been trying to find the stock boot from Rogers for the last 5 hours.
Click to expand...
Click to collapse
I understand that the Rogers Galaxy SIII stock recovery isn't out anywhere. If someone is aware of one, please post a link.
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Details pls
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
Snoops, do you have a Rogers phone? Just trying to understand what you mean by "att boot img". Lol on the Odin count, I got up to 3 and thought I was badass.
Yes, I'd be interested in the files for future use, especially if you're on Rogers and have the LTE version of the Galaxy S3. Model SGH-I747M.
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
plese bro help me out...im stuck in the same hole..i just installed some font changer software and m:y phone just rebooted ....
Hello, thanks for taking a look.
My Eken a90 clone is now merely lighting the backlight of the display and not much else.
My unmodded device went into boot loop after I uninstalled an apk & I decided then was a good time to finally look into rooting it and installing custom firmware as the factory firmware is not available for download from the manufacturer. First I flashed cwm6028-a10-9part-v2.zip and I was able to boot into cwm. Then I flashed cm10_a10_20121011.zip and CM10 installed wonderfully and I was thrilled. Next I was supposed to flash gapps-jb-20121011-signed.zip but did not. I had confused myself and mixed up my steps. Instead I flashed t02_compatibility_1.2.0.zip which may not have been the compatability zip I even needed. I did not realize my error until it was too late and now the device has no display and I cannot enter recovery. I can push files but I cannot flash to it. I have tried pushing the cwm & cm10 .zips to sdcard but this has had no effect I felt I should ask for help. Though I have used android devices for years, this is my first experience with custom firmware.
Rodchenko said:
Hello, thanks for taking a look.
My Eken a90 clone is now merely lighting the backlight of the display and not much else.
My unmodded device went into boot loop after I uninstalled an apk & I decided then was a good time to finally look into rooting it and installing custom firmware as the factory firmware is not available for download from the manufacturer. First I flashed cwm6028-a10-9part-v2.zip and I was able to boot into cwm. Then I flashed cm10_a10_20121011.zip and CM10 installed wonderfully and I was thrilled. Next I was supposed to flash gapps-jb-20121011-signed.zip but did not. I had confused myself and mixed up my steps. Instead I flashed t02_compatibility_1.2.0.zip which may not have been the compatability zip I even needed. I did not realize my error until it was too late and now the device has no display and I cannot enter recovery. I can push files but I cannot flash to it. I have tried pushing the cwm & cm10 .zips to sdcard but this has had no effect I felt I should ask for help. Though I have used android devices for years, this is my first experience with custom firmware.
Click to expand...
Click to collapse
hey dont worry this tablet its almos unbrikable you just need this program LiveSuitPack_v1.07 on your pc, and find the original rom from your tablet and flashed
spideyjab said:
hey dont worry this tablet its almos unbrikable you just need this program LiveSuitPack_v1.07 on your pc, and find the original rom from your tablet and flashed
Click to expand...
Click to collapse
Thanks for that. I downloaded and installed it, drivers and all. Now I'll be good to go if I can find a suitable factory img. I have access to a second unmodded tablet of the same model, perhaps I can get an img file from it somehow.
Hello guys! I don't ever get the need to post in a thread or comments, but this time I'm entangled in some pretty confusing stuff, I'd like help with please.
I bought a used GS3 GT-I9300 and tried to install a custom rom on it. One thing lead to another, a problem after every problem and now I'm at a dead end :\
Last time I was able to boot into a ROM, was via restoring through nandroid backup. But the IMEI had become "unknown". I searched it around to find that this was a problem with the EFS folder. Luckily I had a backup of the efs part before hand! But I can't even utilize the backup! -_-
The Problem is, whatever I flash via odin (no matter which stock rom), I end up stuck at the "Samsung Galaxy SIII" screen. I have a backup of the efs, but if I go through philz recovery, it's not able to find my backup. I've tried every guide at there, and been searching about a whole day and now I give and ask for help from you guys with experience. What am I supposed to do, to get to a point where I can use my phone? Really sad after attempting so many things. NEED ASAP HELP PLEASE! :'( Thanks in advance.
hammadfozi said:
Hello guys! I don't ever get the need to post in a thread or comments, but this time I'm entangled in some pretty confusing stuff, I'd like help with please.
I bought a used GS3 GT-I9300 and tried to install a custom rom on it. One thing lead to another, a problem after every problem and now I'm at a dead end :\
Last time I was able to boot into a ROM, was via restoring through nandroid backup. But the IMEI had become "unknown". I searched it around to find that this was a problem with the EFS folder. Luckily I had a backup of the efs part before hand! But I can't even utilize the backup! -_-
The Problem is, whatever I flash via odin (no matter which stock rom), I end up stuck at the "Samsung Galaxy SIII" screen. I have a backup of the efs, but if I go through philz recovery, it's not able to find my backup. I've tried every guide at there, and been searching about a whole day and now I give and ask for help from you guys with experience. What am I supposed to do, to get to a point where I can use my phone? Really sad after attempting so many things. NEED ASAP HELP PLEASE! :'( Thanks in advance.
Click to expand...
Click to collapse
Start with the simple things first... Do you boot into recovery after flashing with odin and factory reset this is the most common thing that people don't do and this solves most bootloop issues.
Sorry if you have tried that but you really need to give a small brief list of eactly what you have tried to do because saying (quote) "attempting so many things" does not help us to narrow down what is wrong otherwise people will be suggesting things you have already tried.
Question makes no sense, if you can't find the backup in philz then you aren't using it correctly or the backup is in another format. You'll need to understand the basics before you go any further.
Search for people who've extracted the efs backup on their pc then copied all the files across, follow their example.
tallman43 said:
Start with the simple things first... Do you boot into recovery after flashing with odin and factory reset this is the most common thing that people don't do and this solves most bootloop issues.
Sorry if you have tried that but you really need to give a small brief list of eactly what you have tried to do because saying (quote) "attempting so many things" does not help us to narrow down what is wrong otherwise people will be suggesting things you have already tried.
Click to expand...
Click to collapse
Thanks mate. Well I've done that. Separately tried clearing cache alone and rebooting (didn't work). Then also tried factory reset (via TWRP) that didn't work either. Then I tried factory reset + clearing cache which didn't work too. No matter what stock rom I flash via odin, or a custom ROM via recovery, My phone does not proceed ahead from the "Galaxy S III 3G" Logo.
boomboomer said:
Question makes no sense, if you can't find the backup in philz then you aren't using it correctly or the backup is in another format. You'll need to understand the basics before you go any further.
Search for people who've extracted the efs backup on their pc then copied all the files across, follow their example.
Click to expand...
Click to collapse
Can you maybe give me the link for that please? I didn't even intend to backup efs, this is something which luckily happened accidentally haha.
In hope for seeing if I made a efs backup, I searched the internal storage + SD card of my phone and narrowed it down to 3 rar files:
1. efs_01Jan2012-0001.tar.gz (52KB)
2. efsbackup.tar (5.05MB)
3. efsbackup.tar.gz (62KB)
Hello. I've a Samsung Galaxy S4 i9505 running on stock Lollipop 5.0.1. I've been trying to flash a custom rom on the phone for some time now, but I get stuck on a boot loop every single time. I have to revert to my stock firmware either through odin on my pc, or just restoring my backup through recovery.
I've tried more than 5 different custom roms to no avail. I've also tried different flashing methods. First, I used Philz Touch recovery. Then I used the wonderful Flashfire from Chainfire. And then I tried TWRP. It was on TWRP that I came across: "E: Unable to mount Efs folder". I did a little research and I found out that my efs folder is empty (or at least, I can't see anything in the folder, even using Root Explorer). However, my phone is fine. No issues with network or wifi. My imei also seems untouched.
So, I'm wondering, is it possible that's the cause of my boot loops? If it is, how can I solve the issue? And if it isn't, what could be the cause of the boot loops, and how do I solve it?
Sorry for the length of the post. Please help.
d_myke said:
Hello. I've a Samsung Galaxy S4 i9505 running on stock Lollipop 5.0.1. .
Click to expand...
Click to collapse
Hello there,
albeit it's not the same phone but have you tried this way?
http://www.selftechgenius.com/how-to-geek-2/how-to-fix-e-failed-to-mount-efs-invalid-argument-in-all-samsung-galaxy-phones/
Nope
Frizz74 said:
Hello there,
albeit it's not the same phone but have you tried this way?
Click to expand...
Click to collapse
Came across that when I was doing research on efs folders. Doesn't work for me. Thanks anyway.