Related
Ok Guys.
I created this thread cause in the JACHero thread on at least every page everyone asks how to install it, what am I doing wrong, and why is it broken.
So let me give you step by steps of what exactly I have done for me and others to run Hero with out a problem. I will also create a thread with step by step on how to use Ubuntu Linux Live distro to partition your card.
Things you will need to make this work.
Your Brain
G1 Phone
SD Card reader
And the files I included in this thread.
My phone right now is running.
JACHero 2.3
NEW SPL
cyanogens recovery 1.2
8gb class 6sd with Swapper(Swap file on ext2 sd)
setCPU slightly overclock.
Results.
Ever since I did my new Buttons, and the SPL I included in this write up, I have not had one problem flashing any hero rom at all on my phone, nor did I ever have problem actually running hero roms.
So here goes.
First before you partition your card or do anything make sure your card is at least portioned to fat32, don't worry about any other partitions yet.
OK once you do that go ahead and take the radio zip file I am including in this thread and flash it on your phone.
But first make sure you don't already have new radio installed which is 2.22.19.26I THIS IS VERY IMPORTANT. To check what radio you have, power off your phone, and power it on while holding the camera button.
If you do have new radio you can continue on to flashing the new SPL.
Flashing your SPL. (PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED)
Ok this is where it might get a little tricky, and you might require a SD card reader I know I did and frankly I think this is the best way to do it and I recommend every time you do put a new update on your sd card to update your phone do it through a card reader.
Now after you flash your SPL you might or I should say more then likely will get stuck at the T-Mobile G1 screen, this also might happen after new radio flash in the previous step. If this is the case do not freak out it's normal and your phone is not bricked, but this is why having a sd card reader is important.
Ok so Here is what you do after you have flashed new Radio and SPL(Note:The steps on running Linux live distro and using it to partition your card is coming up). Boot up Live distro of Ubuntu, when its done booting, go ahead and go into the partitioning program while your sd card is hooked up in the computer.
Go ahead and set up two partitions at this time. One EXT3, and of course the other one Fat32. Your ext3 partition doesn't have to be all that big. I actually have mine set up to 512.
Once you are done creating partitions, go ahead and put the latest JACHero on the FAT32 portion and flash away (don't forget to rename to update.zip).
At this point if you follow all of these steps there is no way possible that your phone should not boot right into the system to run the initial setup.
These steps pretty much walk you through steps as if you were starting with a phone that has completly nothing on it.
Also the first boot up after flashing the new ROM, might take a few mins at the HTC screen.
Once your phone loads up and you go through the setup process go ahead and run swapper, it should be an APP that's already pre-installed.
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp
Here is the reason why. The default location is your FAT32 partition. If you all of a sudden mount your phone to the computer with the swap file running on FAT32 you will corrupt your sd card, and then you will have to wipe and reinstall everything.
If you set the location of your swap file on /system/sd/ that's actually your ext2/3 partition and never gets mounted and you never have to turn swapper off.
Well I hope this helps some of you out. I will be writing the walk through on loading up live distro of Linux and partitioning your card sometime today.
I have used this method on a couple different phones and it has worked each time. Also I really recommend installing cyanogens recovery 1.2, as its an excellent way of making a back up of your phone and doing future flashing.
If there is anything anyone thinks that could be done better feel free to post in here.
Remember different people have different ways. I have posted this way cause it has worked for me on my phone and two other phones I setup, and each time there was no hicups.
FILES:
Radio 2_22_19_26I
NEW SPL
CM-Recovery-1.2
Ubuntu Linux Download
DISCLAIMER:
I am not responsible for anything that you might have done to your phone by following these directions. Like I mentioned before so far every time I have used this method, I have had nothing but success.
While I can appreciate this topic, I think you need to speak with less certainty that this will always work properly the first time.
For example - I'm coming from the Ramjet ROM, and the process that I have taken.
Freshly formatted 4gb sd card with a 700mb EXT3 partition, the rest is fat32.
Loaded JACHero 2.3 and renamed update.zip
Wiped twice
Installed ROM
Phone went into boot loop - allowed to run for 10 minutes
Removed battery
Attempted to install ROM a second time
Boot loop again - allowed to run 10 minutes
Wiped again
Installed ROM
Boot loop again - allowed to run 10 minutes
It seems strange, as going from a standard JAC build previously I was able to just wipe, wipe, install and had JACHero 2.1 working without a hitch. I found this strange, as people were complaining about that build, but it seems 2.3 is what's giving me the most headache.
/shrug. Guess I'll go back to Ramjet.
Great post, dude. I've rooted my phone, flashed a few ROMs, including Haykuro's Hero, moved Rosie back to run on the phone instead of the SD card, overclocked and run Swapper. I was still a bit confused and hesitant to flash the JAChero ROM. I'm feeling better about it now. Gonna flash when I get home from work today.
TooSlo said:
While I can appreciate this topic, I think you need to speak with less certainty that this will always work properly the first time.
For example - I'm coming from the Ramjet ROM, and the process that I have taken.
Freshly formatted 4gb sd card with a 700mb EXT3 partition, the rest is fat32.
Loaded JACHero 2.3 and renamed update.zip
Wiped twice
Installed ROM
Phone went into boot loop - allowed to run for 10 minutes
Removed battery
Attempted to install ROM a second time
Boot loop again - allowed to run 10 minutes
Wiped again
Installed ROM
Boot loop again - allowed to run 10 minutes
It seems strange, as going from a standard JAC build previously I was able to just wipe, wipe, install and had JACHero 2.1 working without a hitch. I found this strange, as people were complaining about that build, but it seems 2.3 is what's giving me the most headache.
/shrug. Guess I'll go back to Ramjet.
Click to expand...
Click to collapse
I can completely see what you mean by that. But only reason I decided to make this, because two other phones that were having the exact same problems, started working after I did this.
They both had the same symptoms everyone else, and no one really knows where it came from.
So I made sure they had the right radio, then the right SPL, and every time I did something to the SD Card I killed the partitions completely not just format them.
But I destroyed the partition, recreated it and then formatted it to a file system of my choosing.
my g1 is fine ive flashed every rom here and never gotten stuck on boot loop, if anything the files youre downloading for recovery and spl must be corrupted try re downloading your radio file and spl's again.
Include Disclaimer
I like your post but here is something that I would add to your post.
Even though this has worked every time for you do not assume that it will work for every one, therefore make sure you put a disclaimer out there. As you may have seen before, there have been a lot of posters that have blamed others when their phones were either bricked or stuck in boot loops.
Remember....some people may do something wrong during a step and swear that they followed it perfectly and then blame you.
A detailed disclaimer could be of some help since a lot of people will be taking your post as LAW......
for somereason im not able to update my spl is it something u must do i keep gettin a veification faild message when im tryin to flash it wiht alt + s and i cant seem to update to jachero 2.3 im using a 1 g micro sd im really not sure whats going on i have the proper raido settings and everything. also im not really sure how to create 2 partitions on my memory card im running good ol windows vista
how fast is this running.
i tried it once without swapper and it was way to slow in my eyes in order to use at as an everyday phone.
hope you have something for me (is swapper this perfect solution?)
In my opinion the perfect solution is making a a linux swap partition on your sd card.
However last time I created a linux swap partition and created my swap file there after I rebooted my phone I got stuck at the G1 screen.
I think this might have been cause because of having three partitions on the card but I am not 100% sure.
So instead I just use swapper and make it mount the swap file on my ext3 partition which seems to make this rom run really freaking smooth.
Also I have noticed significant improvements of using ext3 vs ext2, but when research how the two different file systems work it makes sense why it would make a difference.
So to answer your question, is swapper the perfect solution? Im not sure if there is anyone perfect solution but I do know that this sure ass hell makes a huge difference in how your Hero rom runs.
for those having boot loops, how about help us help you, run ddms from sdktools and grab a log of whats going on, this way we can determine an issue, because those asking for help with bootloops and asking for help is like asking me to tell you whats wrong with your car over the phone. we cant tell if we cant see whats going on. so helps us, if you have adb and not the sdktools just type
Code:
adb logcat
this way we can see what your phones trying to do.
Excellent post! I wish I this was available yesterday when I did my first Hero ROM ever. The JAC thread is huugggeeee.
Not to hijack your post, but I'll add my two cents and experiences from yesterday if you do not mind.
-------------
Ok first time on Hero. Coming from DudesCupcake.
Pre
Formatted 1gb SD card 500mb Fat32, and the rest Ext3
hxxp://allshadow.com/forum/viewtopic.php?f=9&t=5870
1. Flashed Radio 2.22.19.26I from (update.zip) successful (camera+power to check)
hxxp://code.google.com/p/sapphire-port-dream/
2. Flashed SPL 1.33.2005 from (renamed update.zip) successful (new three android skateboard logo on bottom)
hxxp://code.google.com/p/sapphire-port-dream/
3. Updated to JACHero r2.2.1 from Page 1
Now I have a boot loop, Hero -> HTC...
After installed 2.2.1 should I pop my SD card out and format it again on my computer?
Trying to do the 2.2.1 again.... Wish me luck!
**Update**
Updating to the 2.2.1 again worked.
Ok, everything works!! Much thanks to Luckenbach for the moral support, and thanks to JAC and all the other guides that I linked in my process. So if anyone else is a noob like me you can do exactly what I did (I provided links for each step where I got it from) you should be ok.
XDA rules!
------
Quick questions for people with loop problems.
is your linux partition ext2 or ext3?
southeastbeast said:
Excellent post! I wish I this was available yesterday when I did my first Hero ROM ever. The JAC thread is huugggeeee.
Not to hijack your post, but I'll add my two cents and experiences from yesterday if you do not mind.
-------------
Ok first time on Hero. Coming from DudesCupcake.
Pre
Formatted 1gb SD card 500mb Fat32, and the rest Ext3
hxxp://allshadow.com/forum/viewtopic.php?f=9&t=5870
1. Flashed Radio 2.22.19.26I from (update.zip) successful (camera+power to check)
hxxp://code.google.com/p/sapphire-port-dream/
2. Flashed SPL 1.33.2005 from (renamed update.zip) successful (new three android skateboard logo on bottom)
hxxp://code.google.com/p/sapphire-port-dream/
3. Updated to JACHero r2.2.1 from Page 1
Now I have a boot loop, Hero -> HTC...
After installed 2.2.1 should I pop my SD card out and format it again on my computer?
Trying to do the 2.2.1 again.... Wish me luck!
**Update**
Updating to the 2.2.1 again worked.
Ok, everything works!! Much thanks to Luckenbach for the moral support, and thanks to JAC and all the other guides that I linked in my process. So if anyone else is a noob like me you can do exactly what I did (I provided links for each step where I got it from) you should be ok.
XDA rules!
------
Click to expand...
Click to collapse
When you do the CAMERA+POWER boot, what exactly does the second line from the top say?
lol I wasn't requesting help, I was adding to your post! To hopefully help other people =)
Oh I know I'm just collecting data right now that's it.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CLPD-4
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
--
Edit: Also changing location of swapper from your info helped a lot! Thanks, I had the SD problem when I pulled out my SD card to put photos back on (instead of using adb) and I got stuck in a boot loop, I thought I was done for. Just rebooted it a few times and it was back up and running. Good tips =D
what do you mean by "new buttons"?
A quick question that ill ask here as to not clutter up JADs thread any more than it alreadsy is.
I have put on 3 of his roms in the last few days and where as they are stable they are dead slow at times for me. I am using a 2g class 2 sd card with an ext3 partition. How much more would a class 6 card speed swapper up? Is one worth getting?
Sorry to post up in this thread again, but I just wanted to provide some more of my experiences here.
I'd picked up Paragon Partition Manager and used that to format my SD card and create the ext3 partition on it as well. It seems something is wonky with how it created it, as every time I've created the partition, even with different sizes, I always get stuck in a boot loop when trying to install JACHero even though any other ROMs will install just fine.
I've put the update.zip onto my older 1gb card that came with my phone just to see if it would install, and though it took a while, it installed without any issues.
After going through the setup process, I attempted to put in my 4gb card with ext3 on it. Lo and behold, boot loop.
Seems something is funky with the way that Paragon Partition Manager creates an ext3 partition.
I'm now going to install an older ROM and go through the "creating an ext2 partition through the G1" method and then attempt to convert it to an ext3 through Cyan's instructions.
I'll try to keep up to date what's going on. I know this place isn't a blog, I'm just hoping someone will point out my idiocy if I'm making any huge mistakes somewhere.
TooSlo said:
While I can appreciate this topic, I think you need to speak with less certainty that this will always work properly the first time.
For example - I'm coming from the Ramjet ROM, and the process that I have taken.
Freshly formatted 4gb sd card with a 700mb EXT3 partition, the rest is fat32.
Loaded JACHero 2.3 and renamed update.zip
Wiped twice
Installed ROM
Phone went into boot loop - allowed to run for 10 minutes
Removed battery
Attempted to install ROM a second time
Boot loop again - allowed to run 10 minutes
Wiped again
Installed ROM
Boot loop again - allowed to run 10 minutes
It seems strange, as going from a standard JAC build previously I was able to just wipe, wipe, install and had JACHero 2.1 working without a hitch. I found this strange, as people were complaining about that build, but it seems 2.3 is what's giving me the most headache.
/shrug. Guess I'll go back to Ramjet.
Click to expand...
Click to collapse
did you try going into recovery and then choosing fix file extensions... that happend to me, it might be because you have no ext 2
I've been crawling forums looking for several ways to partition my SD, but to no avail.
Recently upgraded from damagecontrol 2.08 to 2.09. Bought a new 8gb micro SD.
I'd like to partition the SD card so that Apps2SD runs, and I remember the first time I rooted my phone and loaded a rom, there was an option in recovery to partition the SD card. Now, my phone boots into clockworkmod recovery v1.8.1.4, and the list of commands doesn't include a card partition option.
How can I get this option back?
I resorted to using adb and trying to work around this problem through the command line, but all of those attempts failed. "parted not found" etc.
I'm at my wit's end and my school work is suffering! (I'm crazy if my phone is not working perfectly) PLZ help this girl stay in med school!
Try this thread and let me know if that's what you're trying to do.
Actually I found that post after the fact that I set my hero back to factory settings in desperation.
What I did with my rooted and fully functioning hero was...
back up apps
changed SD cards
set to factory settings via an option of the clockwork recovery
updated my rom to damagecontrol 2.09
found that apps2sd wouldn't work
tried to get back SU capabilities unsuccessfully
tried to mimic my first root and flash attempt unsucessfully with flashrec
Now I'm stuck with a slowed down hero which can't allow Su and won't do apps2SD
I'm at the point of insanity with this thing
any sugestions?
UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery
Wow ! thats dualboot for i9003 ! sweet gud to see development back in action
Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.
Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.
Whats the benefits of dual boot? I heard about it but i dont have an idea
juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.
shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.
ok here is my problem i flashed custom roms trying to see what they were like on the tf101, after flashing cyanogenmod my sd card no longer mounted so that was kind of a deal breaker so i flashed the stock rom back to the device and my sd card still doesn't mount unless i use paragon NTFS +HFS and format it as NTFS and then mount via the app. (NTFS and fat32 worked fine by default with no app in the stock rom)
then i tried the ubuntu touch os for phones and tablets, keyboard freaked out and closed every time i went to type so again back to the stock rom now wifi doesnt work right and it wont get on the internet half the time or see other computers on the network. anyone know a fix for these issues?
both of these things worked fine before using custom roms/os's.
nvflash it back to total stock, since there is probably leftover junk from when you flashed your device that is causing things to not work.
Wheelie (NvFlash)
androidroot.mobi
Images
xdafileserver.nl
So the other day I decide to get a new SD Card and gift myself with a sd-ext partition so my FIT can have more apps than it already has. :laugh: After creating the partition succesfully I installed Link2SD and tried to install the script. This somehow didn't work.
Then I tried flashing the darktremour apps2sd script and using the apps2sdgui application, which again gave no fruitful results. A2SDGUI displays a message saying could not start for one of these reasons:
1. Device not rooted
2.A2SD Script could not be found.
3.No EXT partition found.
Now I know that the script did get installed successfully. My device is obviously rooted. So finally it boils down to 'No EXT partition found'. I tried mounting the sd-ext partition from the recovery and booting the device, to no effect. :crying:
I would appreciate it if anyone can help me with the issue. I really need that ext partition!
PS: I'm using Official CM7 ROM without any additional scripts other than apps2sd script.
I remember when I bought a new sdcard(class 10), my FIT(with 2.3.6 gingerbread/based rom) didn't even recognized it. Then the shop guy formatted it from the phone itself & then my FIT detected it. Then I created the ext4 partition(512mb) using cwm recovery 5.0.2.7 & all is well since then.
So I can only advice u to first backup the sdcard contents & format it from ur phone; then use 5.0.2.7 cwm recovery to partition it & hopefully all will go well for u too.
Also maybe the A2SDGUI app is conflicting. & there are some roms in which ext4 partition don't work/mount(my experience) but it should work for official cm7. I have cm7 of 28-10-2012 & 01-03-2013(last build) but I faced serious call issues in the last build: other person keep listening the callertune while my phone didn't even ring. So I reverted back to cm7-20121028-NIGHTLY-s5670.zip:sly: & it worked like charm.
Galaxy_Rohit said:
I remember when I bought a new sdcard(class 10), my FIT(with 2.3.6 gingerbread/based rom) didn't even recognized it. Then the shop guy formatted it from the phone itself & then my FIT detected it. Then I created the ext4 partition(512mb) using cwm recovery 5.0.2.7 & all is well since then.
So I can only advice u to first backup the sdcard contents & format it from ur phone; then use 5.0.2.7 cwm recovery to partition it & hopefully all will go well for u too.
Also maybe the A2SDGUI app is conflicting. & there are some roms in which ext4 partition don't work/mount(my experience) but it should work for official cm7. I have cm7 of 28-10-2012 & 01-03-2013(last build) but I faced serious call issues in the last build: other person keep listening the callertune while my phone didn't even ring. So I reverted back to cm7-20121028-NIGHTLY-s5670.zip:sly: & it worked like charm.
Click to expand...
Click to collapse
I did partition the SD card from the CWM Recovery.. Now, I don't understand how the A2SDGUI app is conflicting. It is just an app to manage the partition rather than using commands in the terminal.
Anyway, I tried the unofficial versions of CM7 and now I have a working partition. I used Link2SD to install the scripts. Link2SD installs the ext4 scripts , even thought the partition is ext3. Well, I can't complain as long as everything is working
Thanks for the reply though. :good: :highfive: