Related
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.
Does any one here know if some of the Kernal cleanser zips from the s2 for TMO would work on the s3? If not are there any similar options?
Also is there a davlik wipe that works properly on the s3? Similar to the dark side zips. Cwm is not doing so correctly.
Sent from my SGH-T999 using xda premium
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
This is the link for superwipe for the Hercules
http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
Sent from my SGH-T999 using xda premium
Well not exactly what I was looking for but it will work for clean flashes. Thanks kind sir. This is from the same dev as the s2 so it's solid I am sure.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
I have been using TWRP since I rooted my phone back in June, have not had 1 issue with it. Everything works flawlessly, I have flashed almost every AOKP, CM10, TW ICS & TW JB ROM out there thru TWRP and never lost my IMEI and the wipe functions in it work just fine. I usually wipe cache/delvik, system & factory reset 3 times. For me it seems to wipe pretty fast ( that's why I do it 3x ).Just to be safe.
belial20xx said:
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Well isn't this normal since there is no external sd ext partition? I mean sure one could write a simple zip to delete /data/dalvik-cache.
And there really isn't a way to check it either. Cause I don't think adb works in recovery mode.
Sent from my SGH-T999 using Tapatalk 2
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Aerowinder said:
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Click to expand...
Click to collapse
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
I made a dalvik cache wiper.
If you notice when you use CWM to clear dalvik cache, then reboot, it doesnt say android is upgrading at all. Making me think it doesnt work.
But when you just flash my script, it says its upgrading.
the zip is simple, all it does is delete_recursive("/data/dalvik-cache/") and thats it.
elesbb said:
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
Click to expand...
Click to collapse
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Aerowinder said:
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Click to expand...
Click to collapse
So did i.. but it optimized the same amount of apps that the "wipe cache" option does. I seriously wonder now if they are one in the same. Like if they are coded to wipe /cache and /data/dalvik-cache. Cause when using my zip, i only optimize 58 apps.
My Incredible running CM7.2 keeps showing a warning in the notification bar that says "Low on space". I don't understand it, because when I click on the notification, it goes to the manage applications screen, which indicates that there are 207MB used with 541MB free internal storage, and 156MB used with 184MB free RAM.
This "Low on space" message is what prompted me to root and install CM7.2 in the first place.
Can anybody explain this to me, and give suggestions on how to fix it?
how did you miss this?
http://forum.xda-developers.com/showthread.php?t=1488351
tekweezle said:
how did you miss this?
http://forum.xda-developers.com/showthread.php?t=1488351
Click to expand...
Click to collapse
Well, I didn't, but I thought CM7.2 was supposed to fix that issue, and therefore, the problem was being caused by something else. Was I wrong?
what ROM are you running? I have found out that the Touch of Blue ROM integrates this fix already but my understanding is that others do not.
tekweezle said:
what ROM are you running? I have found out that the Touch of Blue ROM integrates this fix already but my understanding is that others do not.
Click to expand...
Click to collapse
Thanks for the reply. I'm using CM7.2 (CyanogenMod 7.2).
Are you using Touch Of Blue V2.2 available from http://forum.xda-developers.com/showthread.php?t=1492720 ? Have you noticed anything not working properly with Touch Of Blue?
Does anybody else know of any other ROM that fixes this issue with the Incredible? Thanks!
its not the rom that fixes the issue, it;s the ext4 conversion and moving the data partition mod. you might be able to apply it using CWM to your installation without changing the ROM. I only mention that one because it had the fix integrated into it.
i tested it out and it worked okay but I switched to a CM10 Rom because I was still getting the dreaded 2am reboot issue. So I switched to the CM10 Rom in hopes of solving that issue.
tekweezle said:
its not the rom that fixes the issue, it;s the ext4 conversion and moving the data partition mod. you might be able to apply it using CWM to your installation without changing the ROM. I only mention that one because it had the fix integrated into it.
i tested it out and it worked okay but I switched to a CM10 Rom because I was still getting the dreaded 2am reboot issue. So I switched to the CM10 Rom in hopes of solving that issue.
Click to expand...
Click to collapse
The mod found in the dev section should work for all ROMs.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
The mod found in the dev section should work for all ROMs.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I don't seem to find anything about this in the dev section. Do you mean
[HOW TO] Fix the "Low on space" problem (in plain English) in Droid Incredible General? If not, which mod were you meaning? Thanks!
Boz1 said:
I don't seem to find anything about this in the dev section. Do you mean
[HOW TO] Fix the "Low on space" problem (in plain English) in Droid Incredible General? If not, which mod were you meaning? Thanks!
Click to expand...
Click to collapse
Yes and also this one http://forum.xda-developers.com/showthread.php?t=1623038 which is the main thread for the no_data_limit mods. The thread you posted is more of a guide for people who arent rooted.
The no data limit mods are very simple to use. They are just a zip file like a rom or any other mod, that you flash thru recovery. The mod then does all the work for you. Just remember to do a backup before flashing, just in case.
Thanks for all of the help everyone has provided so far!
Would it be best to start with Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip?
In what scenario would Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip be used?
(The above files are at http://goo.im/devs/tiny4579/mods )
Boz1 said:
Thanks for all of the help everyone has provided so far!
Would it be best to start with Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip?
In what scenario would Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip be used?
(The above files are at http://goo.im/devs/tiny4579/mods )
Click to expand...
Click to collapse
No data limit normal dalvik is the most commonly used. It converts /cache and /data to ext4 from ext3, moves the /datadata partition to a folder on the /data partition, leaves dalvik as is.
The dalvik moved mod does the same thing except it takes the dalvik cache, and moves it to the now empty /datadata partition. This one has been known to cause issues for some people with a lot of apps, as it fills up the now tiny dalvik partition messing with and slowing down apps.
So yeah use the no data limit normal dalvik.
Ok. One final question, I hope, and I apologize for my lack of knowledge, but will flashing Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip cause me to have to reinstall all of my apps and redo the OTA (*22890) programming?
Boz1 said:
Ok. One final question, I hope, and I apologize for my lack of knowledge, but will flashing Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip cause me to have to reinstall all of my apps and redo the OTA (*22890) programming?
Click to expand...
Click to collapse
No it it wont, at least its not ment to. Like i said make sure you do a backup first. I have seen a few issues where apps dont get moved correctly, but its rare. As to the ota programing definitley wont have to do that.
cmlusco said:
No it it wont, at least its not ment to. Like i said make sure you do a backup first. I have seen a few issues where apps dont get moved correctly, but its rare. As to the ota programing definitley wont have to do that.
Click to expand...
Click to collapse
Once again...THANK YOU! I think I got it applied. I checked, and "noauto_da_alloc" shows in the results of the "mount | grep /data" terminal emulator command.
Boz1 said:
Once again...THANK YOU! I think I got it applied. I checked, and "noauto_da_alloc" shows in the results of the "mount | grep /data" terminal emulator command.
Click to expand...
Click to collapse
No problem. You should be good to go then.
If I decide later to try the "dalvik_moved" version, would I be able to flash it over the "normal" version? Or would I first have to use one of the other files at http://goo.im/devs/tiny4579/mods ?
Boz1 said:
If I decide later to try the "dalvik_moved" version, would I be able to flash it over the "normal" version? Or would I first have to use one of the other files at http://goo.im/devs/tiny4579/mods ?
Click to expand...
Click to collapse
Just flash it over. If you want to undo the dalvik move after you try it, there is a file for that the dalvik moved revert.
Did the mod fix your low space issue?
Sent from my ADR6300 using Tapatalk
tekweezle said:
Did the mod fix your low space issue?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
It seems to have fixed it. Of course, my internal storage has been reduced to 411MB from the original 541MB because the app data, which was previously in the 149MB app data storage partition, is now using space in internal storage.
I'm now debating whether or not to try the "dalvik_moved" version of the mod so that the 149MB partition isn't just wasted space. My dalvik-cache is currently at 133MB, so I'm not sure. If anybody has any thoughts on this, I'd appreciate the input!
Boz1 said:
It seems to have fixed it. Of course, my internal storage has been reduced to 411MB from the original 541MB because the app data, which was previously in the 149MB app data storage partition, is now using space in internal storage.
I'm now debating whether or not to try the "dalvik_moved" version of the mod so that the 149MB partition isn't just wasted space. My dalvik-cache is currently at 133MB, so I'm not sure. If anybody has any thoughts on this, I'd appreciate the input!
Click to expand...
Click to collapse
You can try it, but if you run out of space for dalvik it may make apps go slower. You can always revert it if you het issues.
I just got my phone and had to do alot of reading on how to just root it...I couldnt stop there.. So I picked the ROM I liked the best.. It was the Peoples Choice ROM.... I downloaded it and installed in via CWM... It worked great for about 2 days.. Even wifi tether... Then it started to freeze and almost like it was rebooting... But the only thing that happened was the lights on the bottom would stay on... Ive had to do about 4 clean installs and everytime it freezes... Im not saying the ROM is bad.. But maybe I didnt do something right... Im new to this phone and all these different kernals, Roms etc...
All I did was d/l put on the phone via usb cable, chose a kernal during setup and still the same problem... I had to flash a stock rooted ROM because I thought I did a backup in CWM but I guess I didnt...
Please help... I dont know what I did or need to correctly do to get this ROM to work....
Are you sure the download wasn't bad? Try downloading it again and then check the md5sum to make sure, bad downloads happen more often than you'd think
Noob question... How do I check the md5sum?
On your computer, or on your phone me in terminal emulator (download md5sum for windows binary if you're doing it on your computer):
Code:
cd path/to/download/folder
md5sum fileNameHere.zip
CNexus said:
On your computer, or on your phone me in terminal emulator (download md5sum for windows binary if you're doing it on your computer):
Code:
cd path/to/download/folder
md5sum fileNameHere.zip
Click to expand...
Click to collapse
I just did that and the ROM matches to the one listed http://forum.xda-developers.com/showthread.php?t=2013463
I even downloaded the rom again to compare both... Both match the md5 on the page above...
xtreemgreen said:
I just did that and the ROM matches to the one listed http://forum.xda-developers.com/showthread.php?t=2013463
I even downloaded the rom again to compare both... Both match the md5 on the page above...
Click to expand...
Click to collapse
I'm a bit stumped, but maybe you could try using TWRP to flash the Roms. I'd recommend using version 2.4.1.0 in Naddict's thread, as version 2.4.4.0 doesn't seem to work as well for some people. You'll have to redo your backups, as TWRP and CWM use different methods for making nandroids, so your CWM ones won't work on TWRP.
topherk said:
I'm a bit stumped, but maybe you could try using TWRP to flash the Roms. I'd recommend using version 2.4.1.0 in Naddict's thread, as version 2.4.4.0 doesn't seem to work as well for some people. You'll have to redo your backups, as TWRP and CWM use different methods for making nandroids, so your CWM ones won't work on TWRP.
Click to expand...
Click to collapse
I can do that as Im on the stock rooted rom now... how do I uninstall CWM?
xtreemgreen said:
I can do that as Im on the stock rooted rom now... how do I uninstall CWM?
Click to expand...
Click to collapse
The thread I posted you to has the various TWRP and CWM versions which are flashable from within the recoveries themselves. All you have to do is go into CWM and flash the TWRP zip in the thread.
I don't think your download was bad or the md5 check was bad. I suspect since you said it worked well for several days that at some point you downloaded a bad app or something corrupted some data. I would imagine a wipe of cache and dalvik and fixing permissions would have been the first thing you should have done before reflashing or anything else. Oh well water under the bridge now. What kernel did you choose during your installation?
Please try flashing the rom again, make sure you do factory reset, wipe dalvik and wipe cache and do a clean install. If you have any problems or questions go to the thread itself you will find that all of us are very helpful and will welcome you to The People
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
I don't think your download was bad or the md5 check was bad. I suspect since you said it worked well for several days that at some point you downloaded a bad app or something corrupted some data. I would imagine a wipe of cache and dalvik and fixing permissions would have been the first thing you should have done before reflashing or anything else. Oh well water under the bridge now. What kernel did you choose during your installation?
Please try flashing the rom again, make sure you do factory reset, wipe dalvik and wipe cache and do a clean install. If you have any problems or questions go to the thread itself you will find that all of us are very helpful and will welcome you to The People
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
i dont have 10 posts yet.. That why Im posting here...
I dont remember the name of kernal I tried.. but I know on the last try it was the stonk one.. but I will admit... i didnt do the fix permissions on any of them...I also always did the 3 wipes you mentioned when I had a metro phone...
I will do another clean install and flash the TWRP and re flash the rom... Let you guys know how it went...
xtreemgreen said:
i dont have 10 posts yet.. That why Im posting here...
I dont remember the name of kernal I tried.. but I know on the last try it was the stonk one.. but I will admit... i didnt do the fix permissions on any of them...I also always did the 3 wipes you mentioned when I had a metro phone...
I will do another clean install and flash the TWRP and re flash the rom... Let you guys know how it went...
Click to expand...
Click to collapse
I wouldn't bother with TWRP just yet CWM is just fine. Try installing on a clean flash. Use the Ktoonsez kernel. And let us know here. I will keep following this thread until you can get to the main thread.
Transmitted with a portable device using Xparent Blue Tapatalk 2
...I just noticed when I went to load the rom onto my sdcard... My internal said 11gb used... No way have I use that much.. So I formatted everything except my sd card...
I just loaded the rom using the Ktoonez kernal...The new rom booted up just fine so far...
edit
Sorry didnt read your last replay before I installed TWRP...
Something else I just noticed.. It automatically downloading apps from the market that I previously had...Is that something new?
When you set up the phone (log into Google, etc.), if you choose "backup my account to this phone" it'll automatically download all of your apps that you previously had.
Sent from my SPH-L710 using xda app-developers app
xtreemgreen said:
Something else I just noticed.. It automatically downloading apps from the market that I previously had...Is that something new?
Click to expand...
Click to collapse
That's just Google backup and restore, happens on all of the more recent android versions
^exactly what he said. So keep us posted as to how it goes.
Transmitted with a portable device using Xparent Blue Tapatalk 2
So far so good.. But I haven't used it much yet... I'll keep you posted.. Thanks for all your help so far..
Still running strong.. I've used it all morning...
How do I get rid of the side bar?
Sent from my SPH-L710 using Tapatalk 2
xtreemgreen said:
Still running strong.. I've used it all morning...
How do I get rid of the side bar?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Long press the back key. It's not a sidebar it's multiview mod. Watch this.
https://www.youtube.com/watch?v=6XPRPf_Fzvs&feature=youtube_gdata_player
Transmitted with a portable device using Xparent Blue Tapatalk 2
That is cool. Maybe I'll keep it..
Sent from my SPH-L710 using Tapatalk 2
Ok guys, these are modded versions of TDJ's tools to add the preload partition. This should allow you to wipe cache and dalvik without jacking up the symlinks. Also for you guys having issues installing a ROM, the superwipe should fix that. First flash the ROM and reboot (important), then if you are having issues flash the super wipe and then the ROM again. Reboot and you should be good.
Thanks again TDJ!!! You rock bro.
Note to other developers: Feel free to link here from your thread, just don't re-upload them please. Thanks
Everyone else: if you see these uploaded anywhere else please let me know. I have no problem with others linking to these but do not want them uploaded anywhere else.Thanks
Saved. . . . . . .
One more. . . . . .
I'm awesome
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
thx for this, i was annoyed by the preload problem.
Is this for CWM recovery or TWRP as well?
Sent from my SGH-T989 using xda app-developers app
Will work for both.
Thanks Jamison this will solve alot of headaches!
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
euklid said:
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
If on a TMo based 4.1.2 ROM, yes.
Whats the difference between the two downloads?
inpherknow said:
Whats the difference between the two downloads?
Click to expand...
Click to collapse
One is cache/dalvik, superwipe is data/factory reset.
Well before using the scripts ROM would not boot but after super wipe no problems, TWRP 2.5.0.0 :thumbup:
Sent from my SGH-T989 using xda premium
Jamison-does the cache wipe also fix permissions?
Sent from my SGH-T989 using xda app-developers app
Yes it does.
Sent from my dark hole called an office.
I used these scripts installing a ROM and I am having very serious issues. I was using Clockwork and when I rebooted I got stuck in a boot loop. I booted back into recovery but I was not getting fully back into recovery. I tried several times. I finally ODINed back to stock but I can't get the ****ing phone to boot up. It gets toa popup that says ""unfortunatley google partner setup has stopped" and then if I clear that "Google account manager has stopped", "google calender storage has stopped""unfortuantely the process com. android.phone has stopped". ****. I have tried ODIN to 3.5 stock and 4.0.3 both having similar issues.
Anyone have any idea, may have absolutley nothing to do with these scripts but any ideas would be very much appreciated.
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Jamison904 said:
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Click to expand...
Click to collapse
I was running CWM 6.0.2.9 touch and trying to flash the StockWalk ROM. I don't know if you have seen something like this before but it seems like I am totally unable to install any GAPPS even when flashing stock ROM in ODIN. I had flashed the same ROM before attempting to use the scripts, the reason was that I was unable to add my google account (may be a defect in the ROM but others are saying they have not had issue).
*when I say install GAPPS I am just refering to the ones that install on TW ROMS, I am not flashing a GAPPS file of any kind
ArcticFish said:
thx for this, i was annoyed by the preload problem.
Click to expand...
Click to collapse
blackangst said:
If on a TMo based 4.1.2 ROM, yes.
Click to expand...
Click to collapse
OK so I thought I knew enough to not feel like a noob, but here I am with three questions.
First question is what is a "preload problem"?
Second question is this will only work on 4.1.2, and not 4.2.2 (CM 10.1)?
And the third question is will using the original DS wipes mess something up?
T mobiles 4.1.2 loads a preboot partition. Wiping cache with anything but these scripts also wipes these partitions. This script is modified to not do that. No preboot partition = boot loop.
Thus, if you're on anything BUT Tmobiles 4.1.2 you don't need this script and there's no advantage to using it.
Sent from my SGH-T989 using xda app-developers app