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
This thread serves as a guide to install both firerats and data2ext mods on a single rom and have them work simultaneously.
I do not take any credit for the creation of any files mentioned or attached, nor methods for the installation of each individual mod, nor roms, gapps, or otherwise mentioned content. All credit goes to those who created each mod, rom, gapps, and the methods for installing each individually. I only claim responsibility for my own research and the order and hierarchy of steps below that combine these incredible feats of development into a working system of internal storage expansion and space management.
Even though it is impossible to brick your phone using the guide below, I am not responsible if you break your device, because you have willfully chosen on your own to void your warranty by rooting your phone and installing the mods mentioned below.
To make firerats work with data2ext simultaneously, follow these over-detailed instructions EXACTLY. This is written so that anyone who has never held a smartphone in their lives can understand and do this right the first time, so those of you that know what you're doing, sorry about the length, but it should be pretty easy for you.
Note: I've uploaded some pertinent files from the following steps and added all links to all files needed so you don't have to go find them yourself. I did not include any roms, gapps, or the freespace app from the Play Store(just download from your phone, or from the link in step 6d). Links for all necessary files are in their respective steps below. The only links to a rom or gapps are for ICS. Otherwise you'll have to find and use your own downloaded roms and the correct gapps for your rom. If you would rather use the links below to download the files instead of using the ones I provided, be my guest.
I've updated this guide to make installation much easier and work with Sense roms!
Now on to the good stuff!!
Steps 1 through 7a are written for you to collect the files necessary, and to prepare your phone, sd card, and recovery for the correct method of installation of the collected files.
Steps 8 through 10 are to install the mods.
Preparation
1. Be sure to start from scratch!!! This means an UNPARTITIONED, FULLY WIPED sd card, fully wiped and rooted phone, and fully wiped recovery. Fresh file downloads for roms, gapps, and other mods you like wouldn't hurt either. If your phone is not rooted, go here, it's the best and easiest root method I've found.
1a. If you already have a partitioned sd card, insert it into your computer via a microsd adapter or other means(you cannot use your phone for this; it will not recognize that it's partitioned), delete the partitions and wipe the card using partition management software on your computer. I recommend EASEUS Partition Manager 9.1.1 Home Edition(Windows users only). If you use this program, after you delete partitions on your sd card, you will be left with unallocated space. Create a partition that takes up the entire unallocated space and set it as a Primary and FAT32 file system(remember, only do this to your sd card, NOT THE C: DRIVE!!!!).
2. Boot to recovery(hold down home, press and release power, then release home once recovery shows up)
2a. Be sure you have a recovery that supports flashing unsigned .zip files. If your recovery does not support flashing unsigned .zip files, flash a rom and then the corresponding gapps that are signed(cyanogenmod roms and gapps are the easiest way to go), boot into rom, sign in, download rom manager from Market/Play Store, open rom manager, flash clockworkmod recovery, and boot to recovery.
3. Make sure you are using latest 5.5.0.4 recovery, found here.
3a. If you are not already using the 5.5.0.4, flash the 5.5.0.4.zip in your current recovery(or follow the instructions from step 2a if you cannot flash unsigned .zip files) and reboot back into recovery.
4. In your new recovery, make sure you wipe everything, and go to advanced>partition SD card. Choose whatever size you want to have as internal storage(the 'M' means Megabyte, if you didn't already know...). I use 1024M or 2048M(i.e. 1Gb or 2Gb), depending on what mood I'm in, but it works with any of them. Then choose 0M swap size and wait for it to process.
5. Wipe everything once again(just to be safe), including sd-ext, and place your rom and preferred gapps on sd card, along with any other flashable modifications you like to use(I use the sd card speed boost, which can be found here. 2048Kb works best for my card, a 16Gb Class 4).
Note: For ICS users only! I use official, larger ICS gapps, found here(download the one next to 4.0.X, the link will be: '20120429'). The smaller gapps, as well as the current best ICS rom, can be found in whoshotjr2006's thread, here.
6. Make sure you have the latest firerats(1.5.8), which can be found here.
6a. Don't use any of the alphas or betas. Just 1.5.8. Download only the recovery-v1.5.8-CustomMTD_S.zip and boot-v1.5.8-CustomMTD_S.zip and place on sd card. Create a .txt file named 'mtdpartmap' and type 'mtd XXX XX'. These X's represent the size in numbers that you want your /system and /cache partition sizes to be, and therefore will not actually be used. See step 6b or 6c, depending on what rom you'll be using, for information on how to determine the correct partition sizes/numbers to use. DON'T KEEP THE X's IN THE FILE! REPLACE THEM WITH THE NUMBERS YOU WILL USE AFTER YOU DETERMINE WHAT YOUR /SYSTEM AND /CACHE SIZES SHOULD BE!
6b. For ICS users: If you are using the official, larger gapps, type 'mtd 190 60' into the text file and save to sd card. If you are using smaller gapps, type 'mtd 190 30'. Proceed to step 7.
6c. For Non-ICS users: To find out what numbers to replace the X's with in your mtdpartmap.txt, first wipe everything and install only the rom and gapps you'll be using this mod with. Then boot into rom, sign in, and follow step 6d. After you do this, however, you will need to repeat steps 5 and 6a, then proceed to step 7.
6d. You can download 'freespace' from the Play Store, which needs root access, and will show you the total size and space remaining for each of the /system, /data, /cache, /sdcard, and /ext partitions, so you can change the numbers in your mtdpartmap file to what you want the /system and /cache to be that best suits the rom you want to flash. The first number after 'mtd' is for the /system partition, the second number is for /cache. You can't change the /data, because it is dependent on what you set the system and cache sizes to, and will be set to what you partitioned the sd card to anyways. Also, keep at least a 5Mb allowance over what you need for both /system and /cache partitions as you will run into force closing problems if there is no breathing room, especially for the /cache partition.
7. The data2ext thread and .zip file can be found here.
7a. Download the unCoRrUpTeD_data2extV2.2.zip at the bottom of the post and place on sd card. DO NOT FLASH!!!
Summary of what should be accomplished after following steps 1 through 7a: You should now be using CWM Recovery 5.5.0.4, have a partitioned sd card, wiped everything, and placed the boot-v1.5.8-CustomMTD_S.zip, recovery-v1.5.8-CustomMTD_S.zip, unCoRrUpTeD_data2extV2.2.zip, mtdpartmap.txt, the rom and correct gapps, as well as any other mods you want to use onto your sd card. If all of this is true, move to step 8. If not, go back and find what you missed.
The Installation Process
8. Flash recovery-v1.5.8-CustomMTD_S.zip, then under mounts and storage, wipe /system, /cache, and /data in that order.
8a. Reboot to recovery(go to advanced>reboot recovery).
9. Flash rom, gapps, and whatever other mods you have or like, then flash boot-v1.5.8-CustomMTD_S.zip, then unCoRrUpTeD_data2extV2.2.zip, and reboot.
Note: the firerats installation thread for the HeroCDMA says to flash boot-v1.5.8-CustomMTD_S.zip after anything that changes the kernel specifications, but the unCoRrUpTeD_data2extV2.2.zip does not change these. The thread also says that adb is necessary to reboot; it's not. After wiping /system, /cache, and /data, just go to advanced>reboot recovery. It will work just fine, I promise. Newer recoveries don't need to use adb for this step.
10. Reboot immediately after signing in for data2ext to take effect.
That's it! You're all done! Set up your phone the way you want and start installing apps!
Summary of steps 1 through 10: By now, you should be using 5.5.0.4 recovery, have a partitioned sd card, have placed all necessary files, your rom, gapps, and other mods onto your sd card, flashed the correct files in the correct order and rebooted, signed in, and rebooted after signing in. You should now be looking at the home screen(or lockscreen) of your rom, and if you check storage from settings, you should see internal storage showing the size you partitioned the sd card to be in step 4.
Hopefully this wasn't too confusing...good luck!
If you have any questions, don't hesitate to post in this thread!
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Hammerfest said:
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Click to expand...
Click to collapse
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
goliath714 said:
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
Click to expand...
Click to collapse
I think 1.59 alpha... after a system crash a few months ago, i havent had the need to re-bookmark the firerats mediafire folder... I really should, and seeing as most file share hosts are closing down or restricting free access to files I really should re-download and archive them... god knows how many things I have lost because of the MAFIAA fiasco's...
Yeah that might be a good idea. Personally I've never used any alphas or betas so I really don't have any input for them lol
Sent from my HeroC using XDA
Bumping my own thread...lets get some more views for this thing! If you haven't tried it yet, or have questions about it, or simply don't know what it does, send me a message or post on this thread! It's really a very useful mod for those of you that use or like installing lots of apps...
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Hmoobphajej said:
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
Click to expand...
Click to collapse
You have to unmout the partition first.
#Root-Hack_Mod*Always\=LTE
App2sd
Yea, I got that too, is it not working for you.
If not, add "/system/etc/init.d/40data2ext --enable" That made it work for me. Don't add "".
after reboot and the memory still hasn't change then go back in to terminal manager and add the above line and then reboot, should work then, never got firerats to play nice with the script, so i just use data2sd
laie1472 said:
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
goliath714 said:
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
Click to expand...
Click to collapse
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
fforward72 said:
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
Click to expand...
Click to collapse
You can install from the market
Sent from my HERO200 using xda app-developers app
ajrty33 said:
You can install from the market
Sent from my HERO200 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot!
laie1472 said:
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
How? The firerats mod allows you to change the /system and /cache partition sizes, but from what I can find, data2ext only applies the /ext partition to the /data partition to make the phone utilize the /ext partition as /data, and doesn't allow for modification of the /system and /cache partitions.
Updated
Edit: Updated again to fix minor wording issues and make links much prettier!
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Sent from my HERO200
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed".
Any ideas?
dankdank11 said:
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Click to expand...
Click to collapse
Firerats has nothing to do with recovery. It's about resizing partitions. Recovery functions on a level above, so whatever you do with firerats won't affect it. TWRP is a great recovery program.
Tux2609 said:
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed". Any ideas?
Click to expand...
Click to collapse
Try again. Go through the instructions verbatim, as outlined. I wouldn't deviate in any way.
So after rooting and flashing the "Clean" ROM v1.1 I had internal storage issues. First the gallery app would not work. It would give me a message "not enough memory" when trying to open it. Also I could not save any downloads, I would get a message that download failed. So, I recovered to the stock ROM provided in the guide (I have a GT-p5113). Recovering to this stock ROM fixed the above issues. However at this time I noticed that my internal storage shrank from the stock 16GB to about 2 GB total (even if i deleted everything my total internal storage would only be 2GB). So it's like my internal memory went from 16GB to 2GB for no reason. See attached screenshot. I'm not sure if that happened after installing the custom "Clean" v1.1 ROM or when I recovered back to the stock ROM. I've since flashed both the "Infected" ROM and the CM9 ROM and with those I still have the reduced storage area and the problems with the gallery app and inability to save downloads.
Anyone have any ideas what happened and how I can get my storage space back?
Same Problem here
Im having the same problem with mine Ive flashed all three of those roms and have no internal storage space left really. the Misc Files in internal storage has jumped to 8.34 GB and an available 2.18 left.
Please someone help us.
P.S. if you figured out how to fix this please post back.
Thanks!
Gallery "not enough memory"
Similar issue. Tried wiping Dalvik but still not working. Installed 3 times wiping data each time. Any ideas?
Same exacts specific problem as kdubbfive.
im not sure Dunkn.Mynes has the same problem. He is losing free space as if something is taking up room .Dunkn, check you r. clockworkmod directory isnt on your internal memory, taking up more room each time you r un a back up.
Just to underline kdubbfive's problem.
have gt-p5113 - same here
installed cleanrom 1.1 - - same here here
total internal memory shrunk from 16gb to 2gb - same here
restored and tried other roms, internal memory remains 2gb
Weird thing is i had the exact same problem putting clean rom on my phone - Motorola atrix
if i dont he of any fixes ill probably try factory restore with kies and the computer image. i only have a chinese stock image that is suppoosed to be the same as USA version. but I'm not convinced of it.
ill post if i get the nerve to try this our find another fix. if anyone has stock image for gtp5113 p please post. good luck.
Thanks for the Info - Hope to find Solution
Glad to hear someone else is having the exact same issue. I've been going crazy trying to find a solution. Please post if you are successful. I'll do the same.
SaintMatthew said:
Same exacts specific problem as kdubbfive.
im not sure Dunkn.Mynes has the same problem. He is losing free space as if something is taking up room .Dunkn, check you r. clockworkmod directory isnt on your internal memory, taking up more room each time you r un a back up.
Just to underline kdubbfive's problem.
have gt-p5113 - same here
installed cleanrom 1.1 - - same here here
total internal memory shrunk from 16gb to 2gb - same here
restored and tried other roms, internal memory remains 2gb
Weird thing is i had the exact same problem putting clean rom on my phone - Motorola atrix
if i dont he of any fixes ill probably try factory restore with kies and the computer image. i only have a chinese stock image that is suppoosed to be the same as USA version. but I'm not convinced of it.
ill post if i get the nerve to try this our find another fix. if anyone has stock image for gtp5113 p please post. good luck.
Click to expand...
Click to collapse
Solution
kdubbfive said:
Glad to hear someone else is having the exact same issue. I've been going crazy trying to find a solution. Please post if you are successful. I'll do the same.
Click to expand...
Click to collapse
HERE's what worked for me (kind of a complete wipe)
I'm a novice, first time writing instructions, and 2nd time ever posting so let me know if I missed something, and I'll try to get back to you on it.
Make backups as best you can (CWM recovery, Titanium, nandroid)
ALL DATA WILL BE LOST. Haven't tried recovery of data yet. That's the concept behind all the backups above.
Not sure all was neccessary, or what step was key so here is all of it:
Install Kies http://www.samsung.com/us/kies/
Connect tablet and follow any Samsung Instructions exactly
What is says there is updated ROM available, allow it to to install.
On reboot your system will not be rooted, and data will be there (only for the moment), on mine internal storage was still 2GB
Do a factory reset, wipe any cache and all that. Maybe repeat for good luck.
Follow the rooting instructions exactly here including re-downloading files and following all precautions:
http://forum.xda-developers.com/showthread.php?t=1657056
(I noticed the cwm file has a PIT file in it which relates to internal memory partitioning. I suspect this may have been key here.)
Follow instructions all the way to the end.
In the end I had 12GB internal which is normal because I think there are 2 2GB hidden partions there for ROM and maybe swap file, I don't know)
I'm going to make a backup now, then go back to see what I can recover. On second thought, maybe I'll just start fresh. Also, I think I'm done with custom roms. I can deal with the junk Samsung programs for the sake of dependability.
Good luck. I'll check back to see if you have questions.
Thank You!!!
Worked like a charm! Thanks, a million!
SaintMatthew said:
HERE's what worked for me (kind of a complete wipe)
I'm a novice, first time writing instructions, and 2nd time ever posting so let me know if I missed something, and I'll try to get back to you on it.
Make backups as best you can (CWM recovery, Titanium, nandroid)
ALL DATA WILL BE LOST. Haven't tried recovery of data yet. That's the concept behind all the backups above.
Not sure all was neccessary, or what step was key so here is all of it:
Install Kies http://www.samsung.com/us/kies/
Connect tablet and follow any Samsung Instructions exactly
What is says there is updated ROM available, allow it to to install.
On reboot your system will not be rooted, and data will be there (only for the moment), on mine internal storage was still 2GB
Do a factory reset, wipe any cache and all that. Maybe repeat for good luck.
Follow the rooting instructions exactly here including re-downloading files and following all precautions:
http://forum.xda-developers.com/showthread.php?t=1657056
(I noticed the cwm file has a PIT file in it which relates to internal memory partitioning. I suspect this may have been key here.)
Follow instructions all the way to the end.
In the end I had 12GB internal which is normal because I think there are 2 2GB hidden partions there for ROM and maybe swap file, I don't know)
I'm going to make a backup now, then go back to see what I can recover. On second thought, maybe I'll just start fresh. Also, I think I'm done with custom roms. I can deal with the junk Samsung programs for the sake of dependability.
Good luck. I'll check back to see if you have questions.
Click to expand...
Click to collapse
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.
My K1 has been stock rooted for awhile now, and this past weekend I decided to flash a rom on it. I downloaded everything and went into TWRP to start wiping per instructions.
In my haste I selected to wipe EVERYTHING! Internal, SD, cache- the whole works. Abbot the time the wipe finished, I thought "Oh no, I did not leave anything on there to give the tablet instructions!" No new ROM, no old one either.
I have left it in TWRP since Saturday, afraid to reboot it. I fear it will permanently brick because there isn't anything on there. It is still in TWRP, plugged in.
I tried using am OTG flash drive but TWRP does not see it. I took the SD card out & loaded the new ROM on it, but TWRP does not see it either.
I am using a Linux Mint terminal with ADB commands to do this. Sudo ADB devices sees it, shows the serial #, and says Recovery.
How do I get a ROM on this device and get it functional again? Can I reboot it? To bootloader, or to recovery again? What is my next step?
I am an amateur with Linux, so please, keep the commands simple!
Thank you!
Don't worry it's not broken. Just put your SD card in and mount it (click mount and check usb otg or sd card or whichever media you're using) and you should be able to see your media when you click install and expand devices.
You can also connect your tablet to your pc and simply drag and drop files into its internal storage, your linux pc should be able to see your shield if it's in twrp. Just open nemo (win+E) and place the files you want to flash. Just make sure if you're transfering files from linux to give it a few more minutes after transferimg before unmounting your tablet and starting to flash.
I LOVE YOU, MAN!!! I tried mounting (had not seen that in TWRP before) the SD card, but it still did not see it. I put the OTG drive back in and mounted, it saw it! I proceeded to flash the rom. I had a hard time installing gapps, I am going to reinstall it tomorrow.
Thank you, thank you, thank you for your help!
biknut1 said:
I LOVE YOU, MAN!!! I tried mounting (had not seen that in TWRP before) the SD card, but it still did not see it. I put the OTG drive back in and mounted, it saw it! I proceeded to flash the rom. I had a hard time installing gapps, I am going to reinstall it tomorrow.
Thank you, thank you, thank you for your help!
Click to expand...
Click to collapse
No problem
Make sure you've downloaded ARM and not ARM64 gapps for your android version (7.1.1 or 8.1 depending which ROM you use, you can find the version on the bottom of the first post).
I downloaded the link in the Rom post, but I will double check. Thanks again!
biknut1 said:
I decided to flash a rom on it. I downloaded everything and went into TWRP to start wiping per instructions.
In my haste I selected to wipe EVERYTHING! Internal, SD, cache- the whole works.
Click to expand...
Click to collapse
Maybe already lessons learned, but a couple points I often tell folks on these forums:
- The TWRP default WIPE option (which only wipes data, Dalvik and cache) says "this is the only wipe you need most of the time". It says that for good reason, and they mean it when they say that! This default works great for flashing ROMs. Some folks will swear by wiping "system" when flashing a ROM. But this is already done when you flash the ROM, so it really is redundant.
- The option to wipe other partitions (besides the default) is labeled "Advanced" and again, it is called that for good reason. My advice would be, to not wipe anything under this section, unless you know exactly what it is, and what the result will be. There are sometimes valid reasons to do so, such as you want to completely wipe internal storage, and start fresh (various ROMs and apps dump a lot of extraneous stuff there, that never gets cleaned up unless you do so by some manual means). But again, you need to be prepared, such as not having your backups or ROM (that you intend to flash) on the partitions you are about to wipe.
- If/when you do choose to use the Advanced wipe features, always double check (triple check, for that matter) what you are about to wipe. It is easy to click the wrong box, and there will not be any confirmation of what you are wiping once you swipe. It's easy (maybe too easy) to intend to wipe something harmless like cache, but accidentally tap SD card or internal storage.
@redpoint73- Believe it or not, I know that! I did want to wipe the SD Card, and the rest of the tablet, so i could get rid of everything old that was making it lag. Good thought, just not all at one time. Lesson learned!
Nothing was harmed, tablet is better, gained some Linux experience, so all around it was a win!