So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
chadouming said:
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I told it already, the "custom" folder is not filled. It will be kept empty. The user can put a file, which ofcourse is the file of the device he/she have or want to get repaired. All he has to do is copy and paste the file from the working zip( zip file of his currently installed rom, that encounter the problem) of his rom to the custom folder inside the rescue.zip.
And the things that are common will be scripts, but those too will contains device specific mound points, paths, etc. I think that will be common( ie, the working of script, once the mound is done). Am i right?
So all i have to figure out is mount points, paths etc.. i got a couple of them, about 15 or so. And pls help me to find the rest.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Mikevhl said:
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
Click to expand...
Click to collapse
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
wilwilwel said:
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Pls pm me the idea how to make the checking script. Or links that have info in this. Thank u in figuring out such a prob. I am unaware of that.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
showlyshah said:
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
Click to expand...
Click to collapse
I'll send this as a PM as well, but people might learn from this. I am not talking about any specific mount points for LG phones, I just pointed out that there are some roms which use sed to check the filename of its update.zip and do tasks according to that, you need to have one line in your updater script to run the script which detects what to do. That way a user of a Galaxy Nexus would rename it to update-maguro.zip and it would know to use mount points for the maguro, while if the exact same update.zip was to be named update-p990.zip, it would know to use the mount points for the LG optimus 2x. This way you could easily keep the zip up to date for any device, because they all use the same update.zip
About the recovery, you would need to build it for every phone once, but you could make one change to the recovery source and easily compile the recovery for all phones which are capable of running CWM. I believe this method to be more user friendly, as a recovery image has support for actually choosing what you want to do, instead of having to rename the file. A recovery image also has a better way of communicating with the user. Where a update.zip can only say "Hey, I had an error and I'm quitting now, I won't give you any details what the problem was because that's just how update.zips roll", a recovery image would be able to give more advanced outputs, like "An error occurred when trying to mount /data." And then give you the option to either try again, manually fix it by using a computer with adb, or quitting.
But that's just my personal opinion. The recovery would be way harder to make, but I was the original porter of CM6, CM7 and HTC Sense to the xperia mini pro and mini back in the days. I also made a custom recovery and roms for the HTC desire Z, maintain a CWM port for the HTC Chacha which I don't even own and have used the LG optimus 2x before. (currently a maguro owner) but I'm trying to say that I've been experimenting a lot with different phones and know what the possibilities of Android are. you could even make a live Android build, tailored for recovering your phone, which is ran by an update.zip! How cool is that? That would be VERY device specific though..
let me know what you think is the best way to do this. I was thinking of making a mobile time machine app for some time so it's good I saw this thread.
Rogers S3 i747 need some serious help and advice
Ive spent the last 9 hours trying to find a solution to this issue and I cant seem to wrap my head around it, so I am kindly asking for some help.
I was attempting to flash the CM 10.1 12/18/2012 yesterday but every time I flashed it...the data was not working. I tried 12/17, 12/16 files but still the same issue.
So finally I gave up hope and I tried to flash back to the CM M2 experimental. I was using this before and other than the occasional force closes and once a week reboots at least it was useable.
So after I flashed everything again, of course with wiping the data and what not for the proper procedures, I was trying to load up my apps again from Google. About 15 apps in I get the message that there is not enough room? Puzzled I went to see why this was....
My internal memory of 12gigs only has available 678megs... WTF???????
Ive tried to locate how this was possible, but no programs I use can seem to see why the space is taken up. The funny thing is...all the movies and songs and pictures from the internal SD are still there. They can be seen on the phone play lists and picture lists. BUT I cant access the internal SD card!!!!
I am at a loss for solutions. I dont know what I did wrong here.
Ive reflashed Odin. Ive reflashed all the roms. I was able to finally mount the SD from Clockword MOD, but still no sign of these files.
Any and all help would be greatly appreciated at this point as Im about to give up.
ps..has anyone gotten CM10.1 to work with data? cause everytime I used it... it kept saying No Internet Connection
PLEASE HELP.... :silly::crying::crying::crying:
Delete unused backup data in CWM.
Sent from my SAMSUNG-SGH-I747 using xda premium
try format sdcard via cwm
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
lyrad12 said:
try format sdcard via cwm
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
tried formatting sd card via cwm but its not able to because its not mounted
so ive been trying to flash stock Samsung ROM back on my phone with ODIN...
twice its failed.
this is what its saying so far:
<ID:0/019> NAND Write Start!!
<ID:0/019> recovery.img
<ID:0/019> system.img.ext4
<ID:0/019> amss.bin
<ID:0/019> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
im using this TAR file
Odin3_v3.07_SGSIII\I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
after careful examination i see that it might be the wrong version...
so now im using this TAR file
Odin3_v3.07_SGSIII\root66_RWC_I747MVLDLK4.tar.md5
wasabiGT said:
Odin3_v3.07_SGSIII\I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
Click to expand...
Click to collapse
If I'm reading that correctly, that isn't even an image for any sort of S III, being instead for a variant of the S II.
wasabiGT said:
Odin3_v3.07_SGSIII\root66_RWC_I747MVLDLK4.tar.md5
Click to expand...
Click to collapse
This, on the other hand, should be the right (pre-rooted) image for your device.
Well, its the right i747image for a Canadian variety.
Verify these folders.
Verify in your internal SD Card if you have these directories:
/storage/emulated/0
and
storage/emulated/legacy
And by /storage I believe it means just the internal SD Card root directory.
According to a post, CM10.1 for some reason makes a copy of the entire contents of your internal sd card to these folders after installing it... not exactly sure why. Take a look at the link below for more information:
http://forum.xda-developers.com/showthread.php?p=35646339&highlight=emulated#post35646339
I simply formatted the SD Card through CWM Recovery after flashing back to stock ROM and the space was recovered, you will however lose data unless you try and take the contents out from these folders to your PC first.
SO basically im trying something out and i need to add a partition to my android device thats about 100mb big. Is this possible? the Sdcard wont work as a partition
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
CNexus said:
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
Click to expand...
Click to collapse
will modifying that file be able create an extra 100mb partition so when i hook it into my comp two partitions show up?
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
CNexus said:
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
Click to expand...
Click to collapse
Alright thanks im looking into it know do you know how to dump one from a phone? as google is not bringing up anything besides info on what it is
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
CNexus said:
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
Click to expand...
Click to collapse
its a 16gb lph 710 ill look into heimdall thanks
What's your current bootloader version? If not known, run
Code:
getprop ro.bootloader
In a shell on your device/terminal emulator app
And then post the last three alphanumeric characters
Sorry I realized the bios of a comp doesn't recognize the android phone as a peripheral or a mountable boot device which ruins my plans as of now I'm going to try to find a way to at least get the bios to pickup the SDcard if I can I'm doubtful though
Hey everyone! As some of you may already know, there has been a guide on how to re-partition the internal memory for the Samsung Galaxy S II for some time. The problem is that guide was for model I9100 of the S II (for those who are curious, the guide is located here). I have looked around extensively to see if anyone has had success re-partitioning the internal memory of the T989, and it looks like several people have asked about this in the past - but nobody's provided any answers (I am assuming because nobody's done it). So I went ahead and experimented, and to my surprise it was quite easy to do!
Background Info:
The Galaxy S II by default allocates only 2GB to the /data partition. This partition is used for all app installations and their associated data. Unfortunately, 2GB is completely insufficient by today's standard, and the phone often runs out of storage space for app installations quickly (my wife's T989 for example was not even able to receive app updates anymore due to low memory errors). The problem is further compounded by the fact that many custom Kitkat (or later) ROMs do not include a "Move to SD Card" feature for app management (though this can be circumvented by using an utility such as Link2SD), so many users are stuck with a very limited number of apps on their T989.
On the other hand, the phone has over 11GB allotted for the internal SD partition (which is not an actual SD card; this is part of the internal memory). Now, most of us have an external SD card, and don't really store much on the internal SD. So to me it is rather silly to have only 2GB of space in the /data partition for apps (which is what the internal memory should be for!) while the internal SD partition just sits around with over 11GB of space.
What a Re-Partition Does:
Re-Partitioning the internal memory of the phone relocates the available memory (16GB total) from one partition to another. In this specific case, we will be reducing the amount of memory allocated to the internal SD partition and increase the amount allocated to the /data partition.
Does re-partitioning have a high risk of bricking your device? Yes. But we actually won't be doing that much tinkering for the purpose of this guide, and it should be fairly safe (at least in my case, everything went smoothly). That said, I will not be responsible if you manage to brick your device because you didn't follow the steps carefully, do your research, or did something silly like using the included .pit file for a wrong model of Galaxy S II.
What You Will Need:
PIT Magic: Utility for editing the .pit file, which defines your device's memory structure.
ODIN: To upload the .pit file to your device and re-partition it.
The .pit file for Samsung SGH-T989 (see attached).
For your convenience, if you do not want to mess around with the .pit file in PIT Magic (it can get a bit confusing), I have attached a modified .pit file for the SGH-T989 which allots 8GB of space to the /data partition (leaving 5.25GB for the Internal SD). You can flash this directly through ODIN (see below for instructions).
Editing the .PIT File For Samsung SGH-T989 (Hercules):
Download and extract the attached .pit file, "T989_PIT_(Unmodified).zip".
(If you decide to use my pre-modified .pit file, T989_PIT_(Modified,8GB).zip, skip to the next section of the guide: "Flashing .PIT File Through ODIN")
Launch PIT Magic and click "Open". Select the .pit file you downloaded.
Click on PIT Entry List - this will open a drop-down menu. You will see 28 entries, each is a partition (for comparison, the international I9100 model only has 12 PIT Entries). For reference, I will include their names and sizes below (the info below is actually that of a Skyrocket, the AT-T variant of the phone. But the file structure is the same for our device).
Code:
#00 100MB SMD_HDR (partition info)
#01 500KB SBL1 sbl1.mbn
#02 1500KB SBL2 sbl2.mbn
#03 1KB (unnamed partition with '55 AA' MBR signature)
#04 500KB RPM rpm.mbn
#05 2MB SBL3 sbl3.mbn
#06 2500KB ABOOT aboot.mbn
#07 10MB BOOT boot.img
#08 500KB TZ tz.mbn
#09 500KB SSD n/a (empty partition)
#10 500KB PIT celox.pit
#11 10MB PARAM param.lfs
#12 98MB MODEM amss.bin /system/etc/firmware/misc
#13 3MB MSM_ST1 efs.img
#14 3MB MSM_ST2 n/a
#15 3MB MSM_FSG n/a
#16 98MB MDM mdm.bin /system/etc/firmware/misc_mdm
#17 3MB M9K_EFS1 efsclear1.bin
#18 3MB M9K_EFS2 efsclear2.bin
#19 3MB M9K_FSG n/a
#20 10MB DEVENC enc.img.ext4 /efs
#21 10MB RECOVERY recovery.img
#22 3MB FOTA n/a
#23 598MB SYSTEM system.img.ext4 /system
#24 2GB USERDATA userdata.img.ext4 /data
#25 302MB CACHE cache.img.ext4 /cache
#26 129MB TOMBSTONES tomb.img.ext4 /tombstones
#27 11.2GB UMS ums.rfs /mnt/sdcard
The only entry you actually have to alter is #24. When you select it under PIT Entry List, you will see it listed with:
Block Size: 512
Block Count: 4,198,400
Since each block is 512KB, that effectively results in 2,149,580,800 KB (2GB). Now, we want to increase this, so just enter a larger value in the "Block Count" field. For ease of calculations, I recommend simply using a multiple of the default value (so if you double the value, you get 4GB for the /data partition. Triple it and you get 6GB, and so on).
Now, what about the UMS (internal SD) partition? The short of the long is, you don't need to touch it (for our device). In the guide for the I9100 model, it mentioned having to adjust the value for the UMS partition manually - but if you view the UMS partition (#27 in the PIT Entry List), you will see that it's listed with the following attributes:
Block Size: 512
Block Count: 10
Obviously, the UMS partition can't be only 5,120KB in size, so I presumed that our device automatically adjusts the size of the UMS partition based on available space. I turned out to be correct in my presumption.
WARNING: Do NOT change the values of any partition other than /data! If you alter the sizes of crucial system partitions (modem, etc.), it can seriously mess up your device. For safety, ONLY change the size of the /data partition as instructed.
After you have altered the value for the /data partition, save it as a new .pit file.
Flashing .PIT File Through ODIN:
Boot your phone into Download Mode. For the T989, this is done by holding Vol+, Vol-, and Power button at the same time. You will see a warning message about custom ROM's. Press Vol+ to continue, then connect your phone to the PC via USB.
Launch ODIN. Make sure device shows as connected (use a good USB cable!!!) Click the "PIT" button and select the modified .pit file. The checkbox for "Re-Partition" should automatically be checked when this happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click "Start", and ODIN will re-partition the memory on your device as specified by the .pit file.
When ODIN is done, the device will automatically restart (unless you told ODIN not to do so). When this happens, hold the VOL+ key to boot into Recovery (the re-partition shouldn't have affected the Recovery partition, at least in my case it didn't. If it did somehow, you can just flash Recovery through ODIN).
Now, in Recovery, you may notice a series of "Failed to mount /_____ (partition name)" errors. Don't worry - this is because the partition info has changed but they haven't been re-formated yet. You just have to manually re-format them. To do so, click "Wipe" --> "Advanced Wipe" --> "Repair or Change File System" --> "Select Partition to Repair or Format" --> "Change File System" --> "EXT4" (or F2FS, if your ROM and Recovery supports it). Note that you will have to do this individually for each of the partitions (when I tried to simply do a wipe of all the partitions, it resulted in errors). Make sure you do not use the "Repair" function, it won't work for this!
After you have re-formatted all the partitions, you can now check the /data and /sdcard to make sure they are now the desired size (before you re-formatted the partitions, many of them will show 0MB for size; don't freak out. The correct size will show once re-formatted). If you have increased the size of the /data partition, the /sdcard partition should have received an automatic reduction in size.
After you have done the above steps, you can then proceed with ROM installation or recovery. Feel free to check the "Storage" info under System Settings to see if the partition sizes are correct.
(Left: Size of the /data partition on my T989.) (Right: Size of the /sdcard partition on my T989.)​
I Messed Up Somehow & My Phone Appears To Be Bricked! What Should I Do???
Don't panic. Plenty of people have bricked their phones and recovered. Re-partitioning the phone's memory does NOT damage the hardware (I don't see how it could), so as long as ODIN can still detect your phone, you should be able to restore the original memory structure (flash the unmodified .pit file) and flash Recovery. If in doubt, ask for help.
Much appreciate this awesome guide, cool I was first to reply on g+ and here lol, great writeup bro. This is great news for the t989
Hey thank you soooooooooo much for this, you just fixed a major headach I had with my trusty old T989D....
Everything went almost perfectly smooth following your instructions, the only thing I had trouble with was re-formatting the partitions... it kept giving me "Invalid Partition" when clicking on Repair or Change File System. I had to reboot to Recovery twice before I was able to re-format them.
The only thing missing in the following step is the actual selection of the partition you want to fix (in red below)
"Wipe" --> "Advanced Wipe" --> "Select partitions to reformat" --> "Repair or Change File System" --> "Change File System" --> "EXT4"
Thanks again for the tutorial! Working great !
Ok - I'm having issues...
Since I did the repartition, I'm having a hard time with apps writing to the internal data partition.
I did try to fix permission, did not help.
One example is Swiftkey, not being able to save language packs to storage. I tried restoring from a Titanium backup instead and although the app itself works, its unable to load the language packs that were working before the repartitioning...
The stock rom camera is also unable to store pictures to the internal storage, it prompts to insert an SD card when rtying to set the storage to Internal SD.....
-- EDIT -- EDIT -- EDIT -- EDIT --
Something probably went wrong when I reformatted the partitions, I re-formatted everything again, fixed permission and it seems to be working fine now.....
Ricthot did u clean install or restore a nandroid from your external sd
Hey there ricthot! A few questions:
What did you change in your .pit file? I need to know if you changed any partition size other than the /data and /sdcard partitions (I probably should have included a warning, but I did try increasing the sizes of /system and /cache partitions, and that resulted in a bunch of issues. If you did something similar, that may have been the cause of the problem). That's why the guide only mentioned changing the size of the /data partition.
What recovery are you using, and what version? I used Chet's custom TWRP (which supports F2FS) - if you suspect something went wrong during your partition formats, may be give this recovery a try: http://uber.oceighty.co/HERCULES/TWRP/download.php?file=TWRP_2.8.1.0_Hercules_F2FS_Red.zip
BTW I just noticed your phone model is the T989D - not sure if that had anything to do with your errors or not (it may have been better if you grabbed a .pit file specific to the T989D device; I am not sure if there are any differences, but it could be possible considering how big the difference was between the T989 .pit file and the I9100 version).
Glad you managed to sort it out in the end though.
Lorien_Silmaril said:
Hey there ricthot! A few questions:
What did you change in your .pit file? I need to know if you changed any partition size other than the /data and /sdcard partitions (I probably should have included a warning, but I did try increasing the sizes of /system and /cache partitions, and that resulted in a bunch of issues. If you did something similar, that may have been the cause of the problem). That's why the guide only mentioned changing the size of the /data partition.
What recovery are you using, and what version? I used Chet's custom TWRP (which supports F2FS) - if you suspect something went wrong during your partition formats, may be give this recovery a try: http://uber.oceighty.co/HERCULES/TWRP/download.php?file=TWRP_2.8.1.0_Hercules_F2FS_Red.zip
BTW I just noticed your phone model is the T989D - not sure if that had anything to do with your errors or not (it may have been better if you grabbed a .pit file specific to the T989D device; I am not sure if there are any differences, but it could be possible considering how big the difference was between the T989 .pit file and the I9100 version).
Glad you managed to sort it out in the end though.
Click to expand...
Click to collapse
Hi,
I used the provided modified PIT file.
Using TWRP 2.8.4.0
I probably did something wrong the first time... Everything went back to normal after I reformatted everything carefully...
Cheers!
Well my phone's a dud now. Tried this, and it failed in odin. Now I just keep getting an error saying "Firmware upgrade encountered an Issue." Trying to see if recovery mode in Kies will help, but i have feeling it ain't. Device ain't getting recognized. I wanna say Odin can probably flash a stock rom, but i'm wondering if the partition was tampered at all when it failed.
---------- Post added at 03:47 PM ---------- Previous post was at 02:56 PM ----------
Yea Odin ain't fixing it. Not sure what I can do to get it going again. dam there goes my 5 year old t989 :c lol..:crying:
It should be mentioned that this is very dangerous. There is a reason most of our Rom developers work with virtual partitions instead.
arusiasotto said:
It should be mentioned that this is very dangerous. There is a reason most of our Rom developers work with virtual partitions instead.
Click to expand...
Click to collapse
I kept messing with it once I got home, I have a small collection of stock roms I've kept over the years. The one I downloaded while @ work was not stock (and very unstable) so it didn't help at all. Secondly, the USB cable I was using was crap. I was able to wipe it back to ICS stock and worked back up. Re-ran the pit. and I wanna say it worked, I can't tell where the 8GB went, but it went somewhere. Have not tested lollipop yet, running Slim's 4.4.4. with full gapps. The only partition that comes up in TWRP is 'preload' missing. My t989 lives again! whooop! Dam little sucker refuses to give out on me, GS2 FTW! lol :victory::victory:
---------- Post added at 08:14 PM ---------- Previous post was at 08:06 PM ----------
And I just did another format & wipe on partitions. Still can't fix 'preload' but I can now see the 8GB on Data, and the 5GB on Internal Sdcard. Good enough for me lol. Whoop whoop! It works! ;D
A bit more info would help - did ODIN fail during re-partition? Did it throw an error?
Regarding the Preload being missing, you said it doesn't even show up in TWRP? Did you use my modified .pit file or did you make your own? Preload is only used by the stock ROM, thankfully most custom ROMs don't use it. But you might want to fix that if you ever plan on running stock again.
arusiasotto said:
It should be mentioned that this is very dangerous. There is a reason most of our Rom developers work with virtual partitions instead.
Click to expand...
Click to collapse
Lorien_Silmaril said:
A bit more info would help - did ODIN fail during re-partition? Did it throw an error?
Regarding the Preload being missing, you said it doesn't even show up in TWRP? Did you use my modified .pit file or did you make your own? Preload is only used by the stock ROM, thankfully most custom ROMs don't use it. But you might want to fix that if you ever plan on running stock again.
Click to expand...
Click to collapse
Sorry, I did give me an error - but I can't recall exactly what it was exactly. I would re-create the issue but I tossed the defective USB cable (janitors take out the trash overnight so It's long gone lol). When I used a different USB once I got home, I didn't get the same issues anymore. I was able to get ODIN to work.
But essentially, I ran ODIN 3.10 - and It would just hang after "<OSM> All threads completed. (succeed 0 / failed 0)" but not progress.
So I tried ODIN 3.7, and It would start running:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
(succeed 0 / failed 1)
Then would just fail. But once I got home, It didn't give me any more errors on ODIN. After I got it to stock, all the errors were on TWRP. Which is where I fixed the partitions, then flashed the .pit (your modified pit file, I did not modify it myself) and went back into TWRP and fixed partitions again. Did two clean installs, and everything cleared up.
Sorry, when I say 'Preload' is the only one missing, I meant 'Preload' was the only partition it fails to mount - TWRP can see it, but cannot mount it, even though I've fixed every partition twice now. It doesn't really bother me though - I can live without it lol.
I assume that If needed i can flash the "unmodified" pit to reset partitions to stock and flash a stock rom, correct? I've been able to bring this puppy back from the dead so many times - It's incredible. I only ever used stock roms when I really mess it up or need a full clean reset. Which is rare. Until yesterday lol. Before that the last time I ran stock was for an unstable ROM with a virtual partition back in 2011-2012 lol.
I may do another full wipe - just for an extra clean start - but rom has been running fine since last night. So I think everything is good. Well the exclusion of one app that gets stuck laoding static data. Not sure If it's the rom, or the partition affecting it - so I'll probably test another rom out before giving it another go.
Thanks though! Feels alot more roomy now - hardly use the internal space since everything is on a 64gb microsd lol. GS2 FTW! :highfive:
Worked like a dream for me, Odin 1.85 and chet keners modified twrp with f2fs support. Loving 8gb for [email protected]
Gekko.Shadow said:
Sorry, I did give me an error - but I can't recall exactly what it was exactly. I would re-create the issue but I tossed the defective USB cable (janitors take out the trash overnight so It's long gone lol). When I used a different USB once I got home, I didn't get the same issues anymore. I was able to get ODIN to work.
But essentially, I ran ODIN 3.10 - and It would just hang after "<OSM> All threads completed. (succeed 0 / failed 0)" but not progress.
So I tried ODIN 3.7, and It would start running:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
(succeed 0 / failed 1)
Then would just fail. But once I got home, It didn't give me any more errors on ODIN. After I got it to stock, all the errors were on TWRP. Which is where I fixed the partitions, then flashed the .pit (your modified pit file, I did not modify it myself) and went back into TWRP and fixed partitions again. Did two clean installs, and everything cleared up.
Sorry, when I say 'Preload' is the only one missing, I meant 'Preload' was the only partition it fails to mount - TWRP can see it, but cannot mount it, even though I've fixed every partition twice now. It doesn't really bother me though - I can live without it lol.
I assume that If needed i can flash the "unmodified" pit to reset partitions to stock and flash a stock rom, correct? I've been able to bring this puppy back from the dead so many times - It's incredible. I only ever used stock roms when I really mess it up or need a full clean reset. Which is rare. Until yesterday lol. Before that the last time I ran stock was for an unstable ROM with a virtual partition back in 2011-2012 lol.
I may do another full wipe - just for an extra clean start - but rom has been running fine since last night. So I think everything is good. Well the exclusion of one app that gets stuck laoding static data. Not sure If it's the rom, or the partition affecting it - so I'll probably test another rom out before giving it another go.
Thanks though! Feels alot more roomy now - hardly use the internal space since everything is on a 64gb microsd lol. GS2 FTW! :highfive:
Click to expand...
Click to collapse
Sounds like it was probably a bad USB cable; might have messed the partitions up that first time.
Regarding the "Preload" partition mounting issue, one thing you could try is changing the file system to a different one (F2FS, or a different EXT format if your recovery doesn't support F2FS), then change it back to EXT4. This should force a reformat if it didn't work before for whatever reason. On the Google group someone mentioned he had a similar issue with Preload and had to do this extra step, see if it works for you.
And yes, you can flash the original .pit file to re-partition the phone back to factory memory structure. But if you can get the Preload partition working, you can use a stock ROM with the modified partitions, too.
arusiasotto said:
It should be mentioned that this is very dangerous. There is a reason most of our Rom developers work with virtual partitions instead.
Click to expand...
Click to collapse
Unless you REALLY mess with the memory structure (i.e. changing the partition sizes for modem, etc., or deleting partitions), this shouldn't cause a brick. Over on the Google community, the vast majority of re-partitions were reported successful and went without issues. Heck, I even messed up the partitions once on my wife's phone (changed the partition sizes for /System and /Cache, then was unable to go into Recovery), but easily recovered by flashing back the .pit and recovery through ODIN.
Originally I was gonna go the virtual re-partition route as well, but that simply comes with too many limitations: As far as I know, only Sultan's CM build supports it, and that ROM has been discontinued.
Lorien_Silmaril said:
Unless you REALLY mess with the memory structure (i.e. changing the partition sizes for modem, etc., or deleting partitions), this shouldn't cause a brick. Over on the Google community, the vast majority of re-partitions were reported successful and went without issues. Heck, I even messed up the partitions once on my wife's phone (changed the partition sizes for /System and /Cache, then was unable to go into Recovery), but easily recovered by flashing back the .pit and recovery through ODIN.
Originally I was gonna go the virtual re-partition route as well, but that simply comes with too many limitations: As far as I know, only Sultan's CM build supports it, and that ROM has been discontinued.
Click to expand...
Click to collapse
Working great for me. Thanks
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
is it possible for the OP to create a PIT file that contain the following:
1GB /system + 8GB /data partition?
this will help with users flashing a lollipop rom with pa stock gApps package (no more gApps flashing failures due to insufficient /system memory).
let me know, i'm willing to test..
Lorien_Silmaril said:
Unless you REALLY mess with the memory structure (i.e. changing the partition sizes for modem, etc., or deleting partitions), this shouldn't cause a brick. Over on the Google community, the vast majority of re-partitions were reported successful and went without issues. Heck, I even messed up the partitions once on my wife's phone (changed the partition sizes for /System and /Cache, then was unable to go into Recovery), but easily recovered by flashing back the .pit and recovery through ODIN.
Originally I was gonna go the virtual re-partition route as well, but that simply comes with too many limitations: As far as I know, only Sultan's CM build supports it, and that ROM has been discontinued.
Click to expand...
Click to collapse
And a side note on this, over on the g+ community, anyone that has had failures have been able to be resolved quickly and painlessly. Usually something very minor, example 3.09 Odin note working for one of the individuals but was successful with 3.07.
vakkah said:
is it possible for the OP to create a PIT file that contain the following:
1GB /system + 8GB /data partition?
this will help with users flashing a lollipop rom with pa stock gApps package (no more gApps flashing failures due to insufficient /system memory).
let me know, i'm willing to test..
Click to expand...
Click to collapse
Great minds and all... I am just now testing a 1.2gb system 8gb data Pit file, successuflly odined (3.07) reformatted partitions including data which should be fat by the way the others ext4...
flashed a 4.12 touchwiz rom successfully restoring from the market now...
see attached zip...
The new partitions are working great. I can confirm that heimdall works just fine for this. The only issue is that you can not flash the pit file by itself. I had to get a jelly bean image for odin. I unzipped it and flashed the cache.img.ext4 file to my phone. Thank you for your work. :good: