Related
Hey guys,
I'm looking for some info from a knowledgeable dev on how to create a custom ODIN backup that can be restored using the ODIN executable for Windows? My goal is to create a complete hard image of my entire device (including my apps/personal data) that I can restore at anytime (as if it was never touched since the backup) using ODIN.
If anyone can fill me in on the details I would highly appreciate this.
Thanks in advance.
EDIT: I see some other guides here, here, and here. But I noticed some of the blocks they reference are nonexistant on the Galaxy Nexus.
Update #1: Looking for answer to this - Link to post
Update #2: May have found it - Link to post
Info that may help #1
Info that may help #2
would also like to know how to backup with odin since my nandroids always fail at restoring data and then im forced to fresh install a rom
The Race To Die said:
would also like to know how to backup with odin since my nandroids always fail at restoring data and then im forced to fresh install a rom
Click to expand...
Click to collapse
Yes! Thank you! I'm glad I'm not the only one who has this issue. Are you using Touch CWM 5.8.0.2? Or the regular 5.5.0.4?
open1your1eyes0 said:
EDIT: I see some outdated guides here, here, and here. But I noticed some of the blocks they reference are nonexistant on the Galaxy Nexus.
Click to expand...
Click to collapse
How are these guides outdated? They work just fine for the devices they were written for. The Charge uses a completely different device layout compared to the Nexus. They are meant for completely different phones, hence the reason stuff isn't the same. Someone needs to find the proper names for the items that are dumped, and then an Odin package can be put together, but every device will have it's own guide on how to make the packages.
open1your1eyes0 said:
Yes! Thank you! I'm glad I'm not the only one who has this issue. Are you using Touch CWM 5.8.0.2? Or the regular 5.5.0.4?
Click to expand...
Click to collapse
Haven't tried koush's touch yet. Doesn't look as good to me as the unstableapps touch recovery, but have no luck with unstable or regular cwm recovery
Sent from my Galaxy Nexus using Tapatalk
imnuts said:
How are these guides outdated? They work just fine for the devices they were written for. The Charge uses a completely different device layout compared to the Nexus. They are meant for completely different phones, hence the reason stuff isn't the same. Someone needs to find the proper names for the items that are dumped, and then an Odin package can be put together, but every device will have it's own guide on how to make the packages.
Click to expand...
Click to collapse
I see, so each device has different blocks allocated. I wonder how people figure out what blocks go to what?
The Race To Die said:
Haven't tried koush's touch yet. Doesn't look as good to me as the unstableapps touch recovery, but have no luck with unstable or regular cwm recovery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm assuming you're referring to the first Touch Recovery (Unofficial) that was released? But really? Even the regular CWM doesn't work for you? This is a serious issue if we can't restore backups. How are we the only ones who noticed?
Yes that is the one I am talking about. Creating backups works fine, but restoring always fails while restoring data.
Sent from my Galaxy Nexus using Tapatalk
The Race To Die said:
Yes that is the one I am talking about. Creating backups works fine, but restoring always fails while restoring data.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I can confirm the same on the official Touch CWM 5.8.0.2 however I think I can recall making and restoring backups back when there was only the regular 5.5.0.4. Do you mind flashing that and testing if you can make a backup and restore it again?
open1your1eyes0 said:
I see, so each device has different blocks allocated. I wonder how people figure out what blocks go to what?
Click to expand...
Click to collapse
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
open1your1eyes0 said:
I can confirm the same on the official Touch CWM 5.8.0.2 however I think I can recall making and restoring backups back when there was only the regular 5.5.0.4. Do you mind flashing that and testing if you can make a backup and restore it again?
Click to expand...
Click to collapse
sure, will report back in a little. could it have been that i ran out of space? i only had 5 or 6 gigs left, but just erased all my backups and now have about 18gb
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'll take a look right now.
The Race To Die said:
sure, will report back in a little. could it have been that i ran out of space? i only had 5 or 6 gigs left, but just erased all my backups and now have about 18gb
Click to expand...
Click to collapse
That is possible actually, I only had about 2-3GB left when I had the failed restores. Now that I redid my phone maybe it won't be an issue.
I am very interested in this topic since the stock image for my phone is not available. I would like to have an option to restore the stock image in case of a warranty issue.
I was exploring using ADB backup. Would it make sense to do a factory reset before creating the backup image?
Stuck on 4.0.1
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
How do you differenciate which one refers to which partition (data, dbdata, system, etc...). I think this is the main issue here.
open1your1eyes0 said:
How do you differenciate which one refers to which partition (data, dbdata, system, etc...). I think this is the main issue here.
Click to expand...
Click to collapse
Not really sure what you are referring to. Each of those is a partition. User data is the data partition, system is the system partition, boot is the boot partition, etc, etc.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Not really sure what you are referring to. Each of those is a partition. User data is the data partition, system is the system partition, boot is the boot partition, etc, etc.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
EDIT: Disregard I was looking in the wrong directory.
flashed 5.5.0.4 through rom manager
rebooted into recovery
backup completed fine
https://dl-web.dropbox.com/get/Public/IMG_20120208_204435.jpg?w=d80708cb
now making a backup through rom manager just for the hell of it to see if one works over the other
The Race To Die said:
flashed 5.5.0.4 through rom manager
rebooted into recovery
backup completed fine
https://dl-web.dropbox.com/get/Public/IMG_20120208_204435.jpg?w=d80708cb
now making a backup through rom manager just for the hell of it to see if one works over the other
Click to expand...
Click to collapse
Really hope it works.
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ok so I figured out which block goes to what partition (here). Now using this, how can I make a flashable package for ODIN? Also do the filenames of the "of" have to be a specific extension or name or it can be named anything? How does ODIN know which "of" file to treat as which partition in that case?
amazingly it worked! must not have had enough space to restore all of the data or something. now to figure out this odin thing. first samsung ive owned so ive never used it, had an og before my nexus.
The Race To Die said:
amazingly it worked! must not have had enough space to restore all of the data or something.
Click to expand...
Click to collapse
Thank you for testing this! I will stick to 5.5.0.4 for now and make sure I have enough space from now on.
FYI, I found another backup method: Link and More Info. For that you need to have the latest adb.exe from the Android SDK. I am attaching it to this post.
When I first rooted the phone I had installed an 8 gig memory card; however, after having some issues and deciding the internal storage is sufficient, I removed the memory card. Before doing so I moved the clockwork folder from the external card to internal memory. I got into recovery and tried to do a new backup, and it said Cant mount /sdcard. I thought by moving the default folder I confused CWM, so reflashed it via Odin, but still getting the same error.
What do I need to do to get CWM to use the internal storage as default?
I am pretty sure there is an option to "backup to internal sd card" Click that.
Sent from Darth Hercules
GBGamer said:
I am pretty sure there is an option to "backup to internal sd card" Click that.
Sent from Darth Hercules
Click to expand...
Click to collapse
No, there is not.
Sent from my SGH-T989 using XDA
blackangst said:
No, there is not.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
In touch yes there is. I am using sk8erwitskil recovery that he tweaked. I think that how u spell his name. Anyways its in developnent section pretty sure his new one is good to go the only bug it had was backups hanging and now when u flash the recovery it will flash fix. Also there is a cwm zip to flash recov which is cool u wont have to use odin.....here
http://forum.xda-developers.com/showthread.php?t=1510478
Thx sarni. I'll keep that in mind although I'd like to keep the non-touch CWM if possible. worst case scenario I can flash back to stock and re-flash.
Anyone else have any ideas?
Sent from my SGH-T989 using XDA
blackangst said:
Thx sarni. I'll keep that in mind although I'd like to keep the non-touch CWM if possible. worst case scenario I can flash back to stock and re-flash.
Anyone else have any ideas?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
I seriously just checked. Try flashing CWM 5.0.2.7 from ROM Manager. It is in Backup & Restore.
Sent from Darth Hercules
GBGamer said:
I seriously just checked. Try flashing CWM 5.0.2.7 from ROM Manager. It is in Backup & Restore.
Sent from Darth Hercules
Click to expand...
Click to collapse
Well I guess I have other issues..i'm getting "an error occurred while trying to run privileged commands" in ROM manager. Strange. Root explorer is running fine as is titanium backup.
Sent from my SGH-T989 using XDA
Holy crap.. wit the root guide they give u old cwm, install rom manager n install t-mobile cwm through that, has internal sd option n works better.. also on android, it "mounts" the sdcard similar to a hdd, to remove ALWAYS unmount from settings b4 removing, in cwm goto mounts and storage, unmount sdcard otherwise u can corrupt data
doug36 said:
Holy crap.. wit the root guide they give u old cwm, install rom manager n install t-mobile cwm through that, has internal sd option n works better.. also on android, it "mounts" the sdcard similar to a hdd, to remove ALWAYS unmount from settings b4 removing, in cwm goto mounts and storage, unmount sdcard otherwise u can corrupt data
Click to expand...
Click to collapse
I have no idea what youre trying to say here. There is no tmobile cwm. Theres tmobile's recovery and theres cwm.
Anyway. I flashed back to unrooted stock, rerooted, installed cwm 5.0.2.6, and still having the same issue. Nandroid says "cant mount /sdcard, and ROM manager, when trying to download a newer version of cwm, says "an error occurred while trying to run privileged commands", I have a feeling my internal sd card is corrupt.
Im going to flash back to unrooted stock again, perform sd card wipe/format, factory reset, and start again.
blackangst said:
I have no idea what youre trying to say here. There is no tmobile cwm. Theres tmobile's recovery and theres cwm.
Anyway. I flashed back to unrooted stock, rerooted, installed cwm 5.0.2.6, and still having the same issue. Nandroid says "cant mount /sdcard, and ROM manager, when trying to download a newer version of cwm, says "an error occurred while trying to run privileged commands", I have a feeling my internal sd card is corrupt.
Im going to flash back to unrooted stock again, perform sd card wipe/format, factory reset, and start again.
Click to expand...
Click to collapse
I never said t-mobile cwm, I said simply install rom manager feom market and install cwm from there the version under guide is old..
And yes actually, under cwm when it asks u to verify jr model it lists it as tmobile, I stated this BECAUSE OF THE WAY ITS LISTED and the EASIEST way for a n00b to get it, at least try the above before posting and rying to correct me.
Thx
doug36 said:
Holy crap.. wit the root guide they give u old cwm, install rom manager n install t-mobile cwm through that, has internal sd option n works better.. also on android, it "mounts" the sdcard similar to a hdd, to remove ALWAYS unmount from settings b4 removing, in cwm goto mounts and storage, unmount sdcard otherwise u can corrupt data
Click to expand...
Click to collapse
Eh.....u did say t-mobile cwm my dude lol no need to get hostile wit the guy just try to help if u can. To the op did u try touch?
sarni84 said:
Eh.....u did say t-mobile cwm my dude lol no need to get hostile wit the guy just try to help if u can. To the op did u try touch?
Click to expand...
Click to collapse
Well, since rom manager isnt working that doesnt seem to be an option. Im in the middle of a 100% complete wipe/reformat of everything including sd card.
sarni84 said:
Eh.....u did say t-mobile cwm my dude lol no need to get hostile wit the guy just try to help if u can. To the op did u try touch?
Click to expand...
Click to collapse
Yep try installing it through rom manager and c wat it lists it as under their own program, then come back n try n correct me, thx
doug36 said:
I never said t-mobile cwm, I said simply install rom manager feom market and install cwm from there the version under guide is old..
And yes actually, under cwm when it asks u to verify jr model it lists it as tmobile, I stated this BECAUSE OF THE WAY ITS LISTED and the EASIEST way for a n00b to get it, at least try the above before posting and rying to correct me.
Thx
Click to expand...
Click to collapse
You didnt? Perhaps you should re-word what you said.
install rom manager n install t-mobile cwm through that
Click to expand...
Click to collapse
Nevertheless. Your suggestion that I install CWM through rom manager suggests you didnt read my post. Did you read my error in rom manager?
And FYI Im not a n00b. Ive been flashing phones since the old WM days. Thanks for the suggestion though.
doug36 said:
Yep try installing it through rom manager and c wat it lists it as under their own program, then come back n try n correct me, thx
Click to expand...
Click to collapse
Umm no i dont want too.... I know what it says tmobile galaxy s2 our phones in there whats your point guy? Ive used the rom manager way i like the custom touch better. Listen u said u didnt say what u said about "tmobile cwm" and i corrected u n even showed u that u said it. Just take it on the chin man i proved u wrong no big deal. U seem a little hostile towards everyone in every thread i see u in aint u a little to new to be jumping down everyones throat? Regardless of how long u been "following xda before ur acct" people dont know that. Be a little nicer it gets u far in life.. KTHXBYE
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Hey blackangst so did u try that touch by sk8? And if u think internal is corrupted u might just have to format that ****. It will suck but lets save that for a last option and try to narrow it down
sarni84 said:
Umm no i dont want too.... I know what it says tmobile galaxy s2 our phones in there whats your point guy? Ive used the rom manager way i like the custom touch better. Listen u said u didnt say what u said about "tmobile cwm" and i corrected u n even showed u that u said it. Just take it on the chin man i proved u wrong no big deal. U seem a little hostile towards everyone in every thread i see u in aint u a little to new to be jumping down everyones throat? Regardless of how long u been "following xda before ur acct" people dont know that. Be a little nicer it gets u far in life.. KTHXBYE
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Hey blackangst so did u try that touch by sk8? And if u think internal is corrupted u might just have to format that ****. It will suck but lets save that for a last option and try to narrow it down
Click to expand...
Click to collapse
Ye idc bout u correctin me, I wrote that in 2min on my way home from my phone, excuse me if I worded it quickly.
My entire basis is simply the version in guide is OLD, 5.0.2.6 to be exact.
N no not hostile, just can't stand stupidity, and there is a difference between lack of knowledge and stupidity (not callin u stupid here don't jump to conclusions here..) and no, not new had an account a few years back left bout almost a year ago cuz of the stupidity and ammount of people who would rather DL and complain about it then look at wat goes into it, or simply rather flame people and throw off a topic rather then post relative information (last few posts are comming close to being under this category) or the trolls and morons who like to post crap or responses to which they no nothing about.
And fine, if u don't wanna use rom manager download odin flashable from their site, its 5.0.2.7 and has internal support, I said rom manager cuz technicly its the easiest manoeuvre.
Again I'm not new, just grew tired of the scene and decided to come back fresh and c if things have changed..
And I'm as nice as I need to be, when I need to be. Simple as that.
As far as "jumping down everyones throats in every post",
I never once said anything outa line (k, mayb that once when buddy told me to piss off, I gut pissed off alright)
Everything Ive said ive had a reason for. And actually, I try 2 help out, but topics like this are a prime example, if u don't word it 100% people are WAY to quick to jump on it.
When I do jump in pissed off its cuz I see a new post go up with the exact thing stated a couple posts down.
sarni84 said:
[/COLOR]Hey blackangst so did u try that touch by sk8? And if u think internal is corrupted u might just have to format that ****. It will suck but lets save that for a last option and try to narrow it down
Click to expand...
Click to collapse
I think my internal was corrupted. Here's what I did:
In CWM 5.0.2.6 formatted all possible things, including emmc.
Flashed back to unrooted stock via Odin
Re-rooted with recovery-cmw-hercules.tar (CWM 5.0.2.6)
Downloaded ROM mgr again, and flashed to CWM 5.0.2.7
Now I have the choice in CWM to backup to internal (5.0.2.6 doesnt have that option)
Re-flashed Darkside 2.5.1
All is working flawlessly now. Looks like I had a corrupt internal partition somewhere.
And doug36, I appreciate your attempt to help, I really do. But frankly, your posts are extremely difficult to read and follow.
Can anyone advise how one would go about fixing the S3's internal partition tables? I believe I need to flash someone else's table?
Help!
Some context:
I've been having this issue where my S3 runs into a symlink failure/Status 7 error whenever I try to flash a Jelly Bean rom, ie. CM10/PA/Jellybro. This occurred despite me having the latest 5.8.4.7. CWM, wiped and reformatted EVERYTHING, etc. I posted a sample of where the recovery error log shows the flashing processes failing here:
http://forum.xda-developers.com/showpost.php?p=30287780&postcount=302
Lots of XDA member offered advice with no avail. I remember one member mentioned something about partition tables, so I dug a little deeper. I noticed that the error log also contained error messages about missing directories and my sd-ext not mounting, which is strange since I can access my external sdcard under /mnt/extsdcard directory, and the two directory names aren't matching. So I downloaded an partition table app and saw the following:
http://imgur.com/6r4Vo
Basically, it looks like my partition tables are somehow corrupted and my sdcard and external SD is being mounted for use, but somehow...incorrectly. I'm thinking this is the likely culprit.
What was the app you ran to get that? And what rom were you running when you took that screenshot?
You said its happening when you try to flash jellybean. Do you have any problems with cm9, or stock?
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
What was the app you ran to get that? And what rom were you running when you took that screenshot?
You said its happening when you try to flash jellybean. Do you have any problems with cm9, or stock?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I ran this app called partition table.
https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsImNvbS5jbHMucGFydGl0aW9uIl0.
Oy, I missed the reviews where people are saying that this returns bogus info.
Anyways, here's the situation with what I could/could not flash
-Could not flash CM10/ParanoidA/Jellybro/one other ICS rom that I couldn't think of
-COULD flash CM9, as well as restore nandroid backup of older redrum stripped stock (which is what I ran this off of)
-Tried to flash from CWM/TWRP, neither worked
Back to the partition table, even though that app may be malfunctioning, there were still lines in the recovery error log that indicated that the loader was trying to access /sd-ext, when the external SD in my CWM is displayed as /external_sd. Also, it was trying to reference, edit, and delete from non-existent sources, which seems to indicate that these instructions are being misdirected. If this sounds like another error, I'm all ears.
Well, that is an odd problem! If stock based and other roms flash and run normally, I seriously doubt it'll be a partition related problem. While in cwm recovery, in mounts and storage did you check to make sure your sd was mounted? I may be wrong but I seem to remember some had problems with it correctly recognizing the external sd. In twrp there should be an option just above the slider to use either internal or external.
Sounds like its a problem more with your recovery to me. Try downloading goo.im from play store and use that to install the latest twrp recovery.
If that doesn't work the only other thing I can think to try is to apply the FULL latest update from samsung, UVALH I believe. Install using kies and I think it will rewrite the whole system to pure stock. You will have to reroot, but its definately worth trying before messing with the partitions. If you do that, use goo.im to reinstall twrp and give it a go again.
If I think of anything else to try ill let you know but for now that's the best I can think of.
Just to be sure what model phone do you have? T999, T999V, i9300?
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Well, that is an odd problem! If stock based and other roms flash and run normally, I seriously doubt it'll be a partition related problem. While in cwm recovery, in mounts and storage did you check to make sure your sd was mounted? I may be wrong but I seem to remember some had problems with it correctly recognizing the external sd. In twrp there should be an option just above the slider to use either internal or external.
Sounds like its a problem more with your recovery to me. Try downloading goo.im from play store and use that to install the latest twrp recovery.
If that doesn't work the only other thing I can think to try is to apply the FULL latest update from samsung, UVALH I believe. Install using kies and I think it will rewrite the whole system to pure stock. You will have to reroot, but its definately worth trying before messing with the partitions. If you do that, use goo.im to reinstall twrp and give it a go again.
If I think of anything else to try ill let you know but for now that's the best I can think of.
Just to be sure what model phone do you have? T999, T999V, i9300?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm on the T999, T-Mobile.
To your question I've tried TWRP and CWM and neither works. The external SD cards were mounted in recovery during my attempts. I've actually tried using an earlier version of CWM to flash directly from the external SD card, to the exact same results.
I'll try the Samsung update; my hope is that it also provides a partition refresh. It is indeed a unique problem!
Its the best thing I can think of, so hope it fixes everything. If it is a corrupt partition it should rewrite it, so lets hope!
One other thing, what version of twrp were you using? 2.2.1.1 is the latest for our phone. I think there's an older unofficial one out there and even though it would say the sd was mounted, you would have to go into the backup section and look at available space to confirm that. There were also problems with the touch cwm recovery...
I think the way the gs3 handles the sdcard is part of the problem with those though.
Anyway, good luck! Let me know how it goes!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Its the best thing I can think of, so hope it fixes everything. If it is a corrupt partition it should rewrite it, so lets hope!
One other thing, what version of twrp were you using? 2.2.1.1 is the latest for our phone. I think there's an older unofficial one out there and even though it would say the sd was mounted, you would have to go into the backup section and look at available space to confirm that. There were also problems with the touch cwm recovery...
I think the way the gs3 handles the sdcard is part of the problem with those though.
Anyway, good luck! Let me know how it goes!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
TWRP didn't work and neither did flashing the new Samsung update.
I'm absolutely baffled at this point. I can't find what the hell are causing these symlink errors anywhere.
Sorry I don't have any other ideas. Just to be sure though, did you flash the rooted rom, or use kies or odin to install the update directly from samsung?
Actually, one or two more ideas, though I wouldn't expect much at this point.
You could try using odin to reflash the original shipped version....you never know.
Or
Go into the updater-script and wherever it tries to use /sd-ext, change it to /external_sd, or whatever your error log says its looking for.
Definately ask another dev if its worth trying before doing that!
You may want to examine what is happening with any simlinks in there as well. Unfortunately Im probably not the best person to troubleshoot that stuff. But if you want to attach a copy of your logfile ill be glad to take a look.
Sorry I haven't been better help for you.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Sorry I don't have any other ideas. Just to be sure though, did you flash the rooted rom, or use kies or odin to install the update directly from samsung?
Actually, one or two more ideas, though I wouldn't expect much at this point.
You could try using odin to reflash the original shipped version....you never know.
Or
Go into the updater-script and wherever it tries to use /sd-ext, change it to /external_sd, or whatever your error log says its looking for.
Definately ask another dev if its worth trying before doing that!
You may want to examine what is happening with any simlinks in there as well. Unfortunately Im probably not the best person to troubleshoot that stuff. But if you want to attach a copy of your logfile ill be glad to take a look.
Sorry I haven't been better help for you.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
No I'm more than appreciative, believe me.
I've attached some log files from various attempts. There are some common error lines, including various referencing missing directories and such.
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Click to expand...
Click to collapse
Cool, just got home so ill take a look at these in a bit.
In the meantime there's a new rom, Speed Rom which you may want to try. A few min ago I saw the dev had posted that it is in fact based on cm10.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Cool, just got home so ill take a look at these in a bit.
In the meantime there's a new rom, Speed Rom which you may want to try. A few min ago I saw the dev had posted that it is in fact based on cm10.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Hey, I actually fixed it; It turns out I had to reflash a stock insecure kernel, reboot into recovery, AND force a signature check to get it to work. It's strange, because the first flash had some issues and upon trying to reflash it I had to repeat the whole kernel flash process all over again or else it ran into the same symlink error.
I had tried flashing other kernels before but still had errors; it took be sitting down and flashing every kernel for the phone I could find, paired with a ODIN stock flash, to get it to work. I'm still not sure why this phone seems to have this sensitivity about it.
Anyways, thanks for your help; I'm going to post this around in case anyone else has this issue.
Awesome! Great work figuring that out!
(And props for changing the title!)
I'm still a little confused as to why symlinks were failing, but in the end as long as there's a resolution Im thinking it'll be ok!
After getting it to install again have you tried installing anything from recovery? Just curious if its a problem you will have to dance around on future flashes, or if this seems to have solved it altogether.
Either way, excellent job! I love solutions!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Awesome! Great work figuring that out!
(And props for changing the title!)
I'm still a little confused as to why symlinks were failing, but in the end as long as there's a resolution Im thinking it'll be ok!
After getting it to install again have you tried installing anything from recovery? Just curious if its a problem you will have to dance around on future flashes, or if this seems to have solved it altogether.
Either way, excellent job! I love solutions!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I just can't tell. And it's also worth noting that that failure occurred with different kernels.
I'm going to flash more JB roms as they come along but I'll have backups ready this time. Ostensibly, now that I have a base down I should be able to get around similar errors with a little elbow grease, as opposed to days of OCD-driven anguish. But you'll note that I already ran into the error right after successfully flashed it the first time. I still feel like there's some setting or another that needs to be adjusted in the background. But for now, at least I can sleep.
Cheers and thanks for the help and suggestions mate. :good:
Rest well! You deserve it after all that!
And id be keeping multiple nandroid backups laying around!
Anyway, I've only had a chance to glance at those logs you posted. Now that things have calmed down ill look at em more closely in case anything jumps out at me. I think you are probably right that there is still some issue in there somewhere. I don't know about you but I hate that feeling!
But at least that sense of urgency is diminished!
Ill let you know if I find anything a little later.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Rest well! You deserve it after all that!
And id be keeping multiple nandroid backups laying around!
Anyway, I've only had a chance to glance at those logs you posted. Now that things have calmed down ill look at em more closely in case anything jumps out at me. I think you are probably right that there is still some issue in there somewhere. I don't know about you but I hate that feeling!
But at least that sense of urgency is diminished!
Ill let you know if I find anything a little later.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I just tried to flash the latest 8/20 CM10 with all of the aforementioned precautions and it failed a couple of times, even reflashing the 8/18 rom from last night didn't work. It seems like after several tries it just...clicked? And it then did flash.
I wonder if it's a bad sector in my internal memory?
Ugh, I would hope not. How long have you had the phone? If you can it may be worth thinking about trying to exchange for another.
Bad memory can cause all sorts of crazy problems. If it were me I might not want to risk waiting to see how it goes.
Sent from my SGH-T999 using xda app-developers app
I have similar issues. If I flash speed rom or any cm10, I get the error. Also if I flash wicked v2 it won't boot, this is a rom based on stock4.0.4. My question is where did you find the signature verification? I have stock recovery 3e I believe, but don't see that option.
Btw, all other roms flash and run fine, including aokp, wicked v1, xquisite, and everything else.
You'll have to have a custom recovery installed.
Sent from my SGH-T999 using xda app-developers app
feckmu said:
I have similar issues. If I flash speed rom or any cm10, I get the error. Also if I flash wicked v2 it won't boot, this is a rom based on stock4.0.4. My question is where did you find the signature verification? I have stock recovery 3e I believe, but don't see that option.
Btw, all other roms flash and run fine, including aokp, wicked v1, xquisite, and everything else.
Click to expand...
Click to collapse
DocHoliday77 said:
You'll have to have a custom recovery installed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Right, you'll want CWM or (I think) TWRP. CWM definitely has it; you should be able to flash it from rom manager if nothing else.
Meh, looks like I'm right back where i started, symlink failures up the wazoo again.
Need to find way to flash roms in ODIN, if that's even possible.
I reverted back to a stock EL29 kernel today & then re-rooted using the appropriate sfhub's method. I also formatted my Internal SD Card, or USB Storage as it's called in Settings > Storage, from within the stock ROM. I then wiped & flashed the Blazer ICS ROM. Wanted a fresh start! Finally, I flashed Agat's recovery via Mobile Odin, as I did not want the rogue CWM that was packed with the EL29 rooted kernel using sfhub's method. I then set up my phone as usual, & all seemed normal.
However, when I took a look at my internal SD/USB storage, I noticed the following files! :
efsdev-mmcblk0p1.img
efsbackup.tar.gz
efsdev-mmcblk0p1.img.gz
These were not there when I was transferring the flashable zips for Blazer, Agat, etc, but at some point after flashing the ROM & new recovery, they appeared! I have heard of some ROMs backing up efs when flashing, but I flashed Blazer a few weeks ago & didn't see these files. I didn't install any new apps, just my usual & the only apps I installed that have any real power, although I can't see how they would be of any relevance, are ES File Explorer & TB.
I have absolutely no idea how these file ended up my Internal SD card. Just to avoid confusion, the device has no external sd card, but the internal, or USB storage, is also referred to as an SD card. There seems to be some confusion around the sd cards on the E4GT, so I thought I'd be as clear as possible.
I know little about EFS, but it would seem that at least one is a backup...cause it says "backup":good: Simply, what are these three files & how might they have been created, because I certainly didn't do it. The only major difference with these flashes, was that for the first time, I flashed an ICS kernel from a GB kernel, whereas I initially rooted from stock ICS FF18, not GB EL29. So, perhaps this has something to do with the newly found efs files.
Any insights would be appreciated. Thanks so much!
Try open them in winrar. Might have been created by recovery as a part of the flash process
Sent from my SPH-L710 using Tapatalk 2
nacron said:
Try open them in winrar. Might have been created by recovery as a part of the flash process
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply! I wouldn't think it would have been created by Agat's recovery, the recovery to which I flashed, as I have flashed it before & the files were not created. However, I was flashing from Team Rogue's version of CWM, which I have never used before. Could it somehow have been set to back up the efs files upon its removal? Even my question seems like a bit of a stretch, I'm just trying to think of a how this could have happened...
I would think I could remove the files from the internal sd card, but considering that they are efs files, I prefer to do some homework first. I will open them later & have a look, not that that's going to help!
Just back it up to your computer and delete it if it's taking up a lot of space
Sent from my SPH-L710 using Tapatalk 2
So, I finally got around to deleting the efs files on the sd card only to have them automagically reappear! What the !$%&[email protected]? Not sure what's going on! I initially thought it might have have been ES File Explorer's auto back up upon removal of system files, since I just changed those settings before I reverted back to a stock & re-rooted, as I had my apps backed up. This was just a guess, because I have no other answers, but even after deactivating the backup option in ES File Ex, the efs files returned.
Again, I am running Agat recovery w/ Blazer ICS, the exact same set up that I was running. The only difference that I can see with my phone before rerooting & after, is the EL29 Baseband version & a newer version of Agat, 0.5.4 vs 0.5.2.
Also, when I dl'ed the files to my pc & scanned them, one was detected as a decompression bomb, which may mean absolutely nothing...or not...
Anyone have any ideas why these files continue to appear? Thanks!
What third party apps do you have ? This might be the problem.
sent from my BAD A$$ Epic touch
---------- Post added at 07:50 PM ---------- Previous post was at 07:47 PM ----------
You can also try a factory reset then delete the folder. If it comes back at that point I have no idea. If it does not. Try adding your apps with data one by one and see what is doing it.
sent from my BAD A$$ Epic touch
patrao_n said:
What third party apps do you have ? This might be the problem.
sent from my BAD A$$ Epic touch
---------- Post added at 07:50 PM ---------- Previous post was at 07:47 PM ----------
You can also try a factory reset then delete the folder. If it comes back at that point I have no idea. If it does not. Try adding your apps with data one by one and see what is doing it.
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
Appreciate the reply but doesn't appear to be app related. Actually, learning that it may be related to Agat recovery v 0.5.4, still waiting on confirmation.
GWashington said:
Appreciate the reply but doesn't appear to be app related. Actually, learning that it may be related to Agat recovery v 0.5.4, still waiting on confirmation.
Click to expand...
Click to collapse
Definitely let us know if it is. I have been on cm9 for a very long time. But if I end up using twiz I would like to know the situation with the efs files. Thanks.
sent from my BAD A$$ Epic touch
It's kernel related are you agats kernel? Try going to his thread it may have answers.
Sent from my SPH-D710 using Tapatalk 2
Should be a script from agats kernel/recovery he uses parts of my kernel and also parts of siyah wich both have such scripts wich backup efs to sdcard if it does not already exists
Sent from my GT-I9100 using xda app-developers app
Ya I believe rujelus blu kuban kernel also does this. Just found it after I flashed that rom.
sent from my BAD A$$ Epic touch
Agat confirmed that backing up the efs files to the sd is a function of his latest kernels. V 0.5.2 did not perform such a backup but 0.5.4 does. So the change took effect in 0.5.3 or 0.5.4. He just put out 0.6.0 today... I'm under the impression this efs back up feature is still present in this version as well, but I haven't checked.
Took a while, but finally a definitive answer...don't like strange files showing up on my device w/o knowledge of how they got there! Didn't think to ask Agat, as I had been using his recovery for a while, just a different version, which didn't contain this feature. Never thought it might have been added in a newer version.
Appreciate the input folks!
I made a noob mistake... I had a rooted Samsung Galaxy S3 SPH-L710 with the auto brightess being to dim for me. I jumped the gun and installed the "auto brightness" fix for the i9300 without thoroughly researching and finding that it wasn't for my model - DUH! :crying:
My phone will not boot now. I can get into CWM but cannot restore to a backup because apparently it didn't complete correctly and I get a MD5 mismatch error. No backup, no boot, no joy. <more tears>
My plan of action is to download and install the stock ROM using Odin 3.07, then re-root, and reinstall my apps with Titanium Backup. (Then take a new backup that I'll TEST before making any further changes!! )
Does this sound like the appropriate course of action?
Does anyone have a link to download the stock firmware fast? The samsung-updates-com stock ROM for the SPH-L710 is so slow it timed out on me already.
Thanks.
And yes I know I'm an idiot...
ninjadave007 said:
I made a noob mistake... I had a rooted Samsung Galaxy S3 SPH-L710 with the auto brightess being to dim for me. I jumped the gun and installed the "auto brightness" fix for the i9300 without thoroughly researching and finding that it wasn't for my model - DUH! :crying:
My phone will not boot now. I can get into CWM but cannot restore to a backup because apparently it didn't complete correctly and I get a MD5 mismatch error. No backup, no boot, no joy. <more tears>
My plan of action is to download and install the stock ROM using Odin 3.07, then re-root, and reinstall my apps with Titanium Backup. (Then take a new backup that I'll TEST before making any further changes!! )
Does this sound like the appropriate course of action?
Does anyone have a link to download the stock firmware fast? The samsung-updates-com stock ROM for the SPH-L710 is so slow it timed out on me already.
Thanks.
And yes I know I'm an idiot...
Click to expand...
Click to collapse
Best course of action back to stock :::: http://forum.xda-developers.com/showthread.php?t=1904099
I assume you know how to use Odin so here's the file as posted by Skunk Ape1. All credit goes to him.
http://d-h.st/GVs
Thank you!
Also, you can connect your sdcard to your computer through recovery...then just put any rom on there (doesnt have to be stock) and flash it (full wipe), because it seems as though you've corrupted the /system partition in some way since the the phone starts up at all
No need to go back to stock necessarily
Also, I would suggest that you make a backup of your phone as is now...that way when it get it functioning again you can manually restore your apps and data and any tweaks you mightve had in your build.prop or init.d
Sent from my PG06100
Why don't you just put into the recovery and wipe your system and just reinstall the rom. All your data will remain.
Anthraxed MA4
CNexus said:
Also, you can connect your sdcard to your computer through recovery...then just put any rom on there (doesnt have to be stock) and flash it (full wipe), because it seems as though you've corrupted the /system partition in some way since the the phone starts up at all
No need to go back to stock necessarily
Also, I would suggest that you make a backup of your phone as is now...that way when it get it functioning again you can manually restore your apps and data and any tweaks you mightve had in your build.prop or init.d
Sent from my PG06100
Click to expand...
Click to collapse
As you see:
My plan of action is to download and install the stock ROM using Odin 3.07, then re-root, and reinstall my apps with Titanium Backup. (Then take a new backup that I'll TEST before making any further changes!!
So I suggested the closest thing to what he/she was looking for...problem solved long ago, again theres this troll rambling off more gibberish
No need for your input necessarily
take a hike, dont worry bout me/my/my posts and buy a real phone...
SGSIIIJB said:
So I suggested the closest thing to what he/she was looking for...problem solved long ago, again theres this troll rambling off more gibberish
No need for your input necessarily
take a hike, dont worry bout me/my/my posts and buy a real phone...
Click to expand...
Click to collapse
That was a little unnecessary, there's no need to be a jerk when someone else suggests something.
metalfan78 said:
That was a little unnecessary, there's no need to be a jerk when someone else suggests something.
Click to expand...
Click to collapse
no all help is great! from everyone!!! except that person (lil history there)
SGSIIIJB said:
no all help is great! from everyone!!! except that person (lil history there)
Click to expand...
Click to collapse
Which one?
Transmitted with a portable device using Xparent Blue Tapatalk 2
SGSIIIJB said:
no all help is great! from everyone!!! except that person (lil history there)
Click to expand...
Click to collapse
History? Really now, you would think that people would be more mature when others offer alternative advice, even if it may differ from your own
Note that I never said your answer was wrong, I was simply offering another solution and I believe its up to the OP to decide which is better, not you or me.
Sent from my PG06100
I'm glad I did a search because I would have hated starting a new forum for nothing. I'm having the exact same issues with my GS3. I flashed a 4.4 kit kat rom and after that now I can't restore my stock 4.1.2 ROM, or flashed any others. I get the same MD5 mismatch when trying to restore the old rom. I went back into to ODIN and tried bringing back to stock but and it does is reinstall the stock recovery and give me a whole list of "FAILED" messages. I like the 4.4 ROM but I want out and I can't figure out how. Do you guys have any idea what I can do?
---------- Post added at 03:23 PM ---------- Previous post was at 03:12 PM ----------
CNexus said:
Also, you can connect your sdcard to your computer through recovery...then just put any rom on there (doesnt have to be stock) and flash it (full wipe), because it seems as though you've corrupted the /system partition in some way since the the phone starts up at all
No need to go back to stock necessarily
Also, I would suggest that you make a backup of your phone as is now...that way when it get it functioning again you can manually restore your apps and data and any tweaks you mightve had in your build.prop or init.d
Sent from my PG06100
Click to expand...
Click to collapse
@CNexus, I tried this as well. I actually tried installing your stock rooted 4.3 rom and it just get's stuck on the splash screen. Any advice?
Try again but perform a full wipe (data, internal storage [if nothing important is there], cache, dalvik cache, and system)
No go. I'm going nuts over here. I know I'm a noob this is probably annoying but I want to thank you for your help. So I tried restoring after doing a full wipe and still get the "md5 mismatch". Then I wiped again and trued installing 4.3 and it stayed on the splash screen for over 20 minutes. Aside from flashing a stock tar file on odin, is there another method to fully restoring the phone to stock?
Sent from my SPH-L710 using xda app-developers app
http://forum.xda-developers.com/showpost.php?p=48637859&postcount=1223
FYI:
http://forum.xda-developers.com/show...php?p=48620997
Latest CWM won't let you flash anything other that KitKat (4.4.x) ROMs per this post...
Sent from my SPH-L710 using Tapatalk
Got this tip from pitcherj, it solved everything. I'M BACK BABY!!!!:laugh::good: