Related
Apps 2 Virtual Disk 0.53b
For those of you that are wondering "What is this guy smoking?" (which I assume is all of you), this is an automatically re-sizing virtual apps 2 SD ext3 partition. It is stored as an image file on your existing Fat32 partition.
I have done my best to make this as idiot proof and bug free as possible but I always appreciate constructive criticism. Please be kind, I haven't had access to a computer while writing this so it was written entirely on my G1. Therefore I expect that it will have a few bugs.
This barrows very heavily from Cyanogen's work so please thank him for making this possible.
Installing
To install the utility just download the file on your phone, open your terminal emulator and run:
Code:
su
sh /sdcard/download/a2vd-0.53b.zip
It does the rest.
Please note, this is NOT a zip file! It is a shell script. XDA won't let you post any file this big unless it's a zip file. (Can we get an Admin on this?) Good thing linux doesn't give a crap about file extensions.
Once you reboot your phone the utility will create the virtual partition, move over your apps, then re-size the partition to have 15 MB of free space. Please note, it will reboot 3 - 4 times during the first boot.
This should run on any rom that executes /system/bin/a2sd during boot.
It has been confirmed to work on Cyanogen 3.5.2 and higher.
Automatic Resizing
The partition will automatically re-size so you don't have to guess how big you need to make it. Now you can take a bite out of crime, in stead of your Fat32 partition. ;-)
If you run low on space just reboot your phone. If the free space on your virtual partition is less than 10 MB or more than 20 MB it will be re-sized to have 15 MB of free space. Please ignore the fact that free space may be listed as 13 or 14 MB, as far as I can tell this is an issue with the OS, the readout becomes more accurate as the partition gets bigger.
Disabling the Partition
If you wish to boot up with the Apps 2 Virtual Disk partition disabled simply open up your terminal emulator and run:
Code:
su
a2sdoff
You can also remove the SD card while the phone is off.
This is useful if you need to transfer files over USB cable.
Automatic backup
If you boot with the partition disabled the utility will backup some system settings so your apps and widgets will all still work when you re-enable the partition. It will also maintain a separate launcher profile for when you boot with the partition disabled. Now you don't have to stare at a desktop full of broken icons every time you need to transfer files to your computer.
Upgrading to a New Rom
Transitioning to a new rom can break some of your apps and widgets. To prevent this follow this procedure:
1. Place your new update.zip file on the root of your SD card.
2. Open terminal emulator and run:
Code:
su
a2sdoff -u
This will reboot your phone, prepare the backups, and take you to recovery.
3. Flash your new rom. (If you exit recovery without flashing you must re-run "a2sdoff -u" before attempting another flash)
4. Boot up your new rom, open terminal emulator and re-install Apps2VD.
Okay, you can start downloading now.
Thank you for your support and enjoy!
As a side note, If you install this on a phone that already has a traditional Apps2SD partition it will NOT copy over your apps. I'm working on it but until then you'll have to either just deal with it or copy them you self.
Edit: Download has been removed due to security concerns. Will re-upload when solved.
Sweet !....so basically it allows app2sd without an ext partition ? so just a fat32 partition is gud enough right ?
this is really intriguing, but i think i'm gonna hold off until some brave souls try it out with some feedback
Daneshm90 said:
Sweet !....so basically it allows app2sd without an ext partition ? so just a fat32 partition is gud enough right ?
Click to expand...
Click to collapse
Exactly! In fact, it requires nothing more than downloading and typing in one command.
narcopolypse said:
Exactly! In fact, it requires nothing more than downloading and typing in one command.
Click to expand...
Click to collapse
Aight im nandroid'd...n ready to test lol...will post results
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
miketaylor00 said:
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
Click to expand...
Click to collapse
Didnt work on xRom....kept bootloopin the first bootscreen
grandomegabosses said:
this is really intriguing, but i think i'm gonna hold off until some brave souls try it out with some feedback
Click to expand...
Click to collapse
I've been running this build for 4 day and previous alpha builds for over a month.
So have all of my friends.
miketaylor00 said:
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
Click to expand...
Click to collapse
Performance is identical. The primary reason I built this is to have an automatically re-sizing apps partition. And the ability to boot disabled without breaking all of my widgets.
narcopolypse said:
I've been running this build for 4 day and previous alpha builds for over a month.
So have all of my friends.
Click to expand...
Click to collapse
hmmm i might try it later tonight or maybe tomorrow. after reading some more, i've gotten a little bit more confidence.
narcopolypse said:
Performance is identical. The primary reason I built this is to have an automatically re-sizing apps partition. And the ability to boot disabled without breaking all of my widgets.
Click to expand...
Click to collapse
It seems suprising to me that an image file on a FAT32 partition would perform the exact same way as an ext partition. I guess I will have to find out for myself
If this really does work and perform well, this could be google's solution to allow non rooted phones the ability to free up memory on their phone.
Either way, thanks for taking the time to do this.
Daneshm90 said:
Didnt work on xRom....kept bootloopin the first bootscreen
Click to expand...
Click to collapse
Yes, it will. And it would probably have a similar problem on later Cyanogen builds. You will have to modify the a2sd file to tell it not to automatically create apps2sd.
Daneshm90 said:
Didnt work on xRom....kept bootloopin the first bootscreen
Click to expand...
Click to collapse
It is supposed to reboot 3 - 4 times during the first boot.
this is really interesting, thank you for this. earlier today i made a modified a2sd script that makes the a2sd look for dev/block/mmcblk0p4 (fourth partition) and since there is none cyanogen's apps2sd will not be created. also in the file is a modified userinit.sh and user.conf that point to dev/block/mmcblk0p2 instead of 0p3 so that if you wanted to use this and only have a fat32 partition and linux-swap partition you could still get the benefits of it. saw this thread and thought this would be a place where these files could be used.
edit: was just thinking, does this overwrite the a2sd script? either way the modded userinit.sh and user.conf can still help.
david1171 said:
this is really interesting, thank you for this. earlier today i made a modified a2sd script that makes the a2sd look for dev/block/mmcblk0p4 (fourth partition) and since there is none cyanogen's apps2sd will not be created. also in the file is a modified userinit.sh and user.conf that point to dev/block/mmcblk0p2 instead of 0p3 so that if you wanted to use this and only have a fat32 partition and linux-swap partition you could still get the benefits of it. saw this thread and thought this would be a place where these files could be used.
edit: was just thinking, does this overwrite the a2sd script? either way the modded userinit.sh and user.conf can still help.
Click to expand...
Click to collapse
Yes this does replace /system/bin/a2sd and it stops checking for 0p2. It is based entirely off Cyanogen's a2sd that is used in every new rom out there and should be compatible with all of them.
Has anyone tested this yet? Which roms does it work on?
How does this work with mounting your phone on your computer? Like when you want to put music on. Can you do it the same way or do you have to shut your phone down and use a SDcard reader? Because I thought the was the main reason for not using fat32 for A2SD.
miketaylor00 said:
It seems suprising to me that an image file on a FAT32 partition would perform the exact same way as an ext partition. I guess I will have to find out for myself
If this really does work and perform well, this could be google's solution to allow non rooted phones the ability to free up memory on their phone.
Either way, thanks for taking the time to do this.
Click to expand...
Click to collapse
probably the wouldn't use it as you should be able to extract files from the img file
narcopolypse said:
It is supposed to reboot 3 - 4 times during the first boot.
Click to expand...
Click to collapse
Lol, no i tried again rebooted like 20 times so i gave up n nandroid'd.
speoples20 said:
How does this work with mounting your phone on your computer? Like when you want to put music on. Can you do it the same way or do you have to shut your phone down and use a SDcard reader? Because I thought the was the main reason for not using fat32 for A2SD.
Click to expand...
Click to collapse
That would be my concern as well. I don't see any way around this, though I'm not a dev by any means.
alritewhadeva said:
probably the wouldn't use it as you should be able to extract files from the img file
Click to expand...
Click to collapse
I'm sure they could make the img file only accesible by the sytem.
Introduction
If you are rooted and running a Hard SPL or a Stock SPL and really want to flash a ROM that claims to require Danger/Haykuro SPL, but you do not want to upgrade your SPL there are alternative ways to make these ROMs work on your phone without upgrading your SPL.
This is a very easy process, Ive done it with a few ROMs with no problems:
First off, keep in mind that on a Stock SPL
/system = about 67MB
Any ROM that has a system partition 67MB or Greater will require Danger/Haykuro SPL, UNLESS you can shrink that ROM's /system down below 67MB.
How do you do this, you ask?
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #1 (Easy) -Move/Delete unneeded Apps, Sounds, Files
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method does NOT apply to HERO/SENSE ROMs, they are way too big! Check Method 2 if you want to fit ANY ROM on any SPL (Advanced)
Make sure you have 7-Zip! Dont have it? Google is your friend!
1) Read the first post and changelog of the ROM you wish to install on your phone. After youve made yourself familiar with what needs to be Wiped (ie: dalvik cache, ext, data) the Partition Layout the developer suggests (ie: FAT32/Ext3/Swap), then go ahead and download the ROM. Unzip it to a folder, name it something short. for example: C:\1\rom
now click on the system folder, scroll down and click on the media folder, and delete the audio folder. This will erase every sound effect and ringtone on your phone and usually will free up about 2MB in system.
To get your ringtones and sounds back download this (thanks Robot Teapot!) and unzip the folder to the root of your sdcard. (note: your ringtones might not show up the first time you boot the rom, in this case, reboot and theyll all be right there)
If removing your ringtones isnt enough to keep /system under 67MB then move on to step 2), if youre already below 67MB skip to step 3)
2) Return to the first post and changelog of the ROM you are trying to install. Look for apps the dev has added to the ROM that dont seem necessary for the ROM to function such as Twidroid.apk, Facebook.apk, NeroMedia.apk, WirelessTether.apk, WiredTether.apk, Maps.apk(takes up a lot of room, and sometimes outdated...just delete it and install the latest from the market!)etc.
You can use Android Barebones/Necessary Apps - CyanogenMod Wiki as a general guideline to determine which apps are essential to Android running properly and the functions of many system apps.
Delete those unnecessary apps or move them to your sdcard, and use ASTRO File Manager or a similar app to install them after you flash the ROM.
3) Okay, assume youve trimmed /system down below 67MB, good job! now you need to get those folders you extracted and the boot.img zipped up and signed. select the folders from the ROM you extracted and modified, the boot.img, right click, and select 7-Zip < Add to .zip
4) Download Stericson's Autosign place it in any directory and follow the instructions in the thread to sign your zip file.
5) Move the signed zip to your SD Card, making sure you have the proper partitions, wipe the necessary things, then flash your zip file and cross your fingers!
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #2 (Advanced) -"Cache Hack"
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method will fit any ROM on any SPL but is more advanced than Method 1
lbcoder introduced the concept of moving files to the /cache partition of the phone and linking them back to /system or /data.
Firerat has come up with a way to make this concept work and explains the whole process in his thread and shows some examples of his method by providing some ports:
[HACK][ROM][BOOT.IMG][CACHE]-Stk SPL ROMs with Danger SPL size & extra 30mb! any SPL!
------------------------------------------------------------------------------------------------------------------------------------------------------
There you have it folks! Congrats if youve bypassed the Danger SPL requirements! Be sure to always keep a Nandroid/BART backup!!!!
Disclaimer: Not saying these methods will brick or damage your phone, but in the rare event this occurs I am NOT responsible for bricks or or any damages to your phone!
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Thanks for this excellent tutorial
Ace42 said:
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Click to expand...
Click to collapse
Really? I had no idea that the SDK wasnt required, ill remove that.
and yeah i know its usually a soft brick, if anything, and youre right its nonsense, and can be solved using a nandroid backup and wiping the proper things, but im playing it safe with that disclaimer just like the rom devs do lol
migalito said:
Thanks for this excellent tutorial
Click to expand...
Click to collapse
.
Youre welcome! I hope it works out for you!
Will this work with the Super D rom?
cg87 said:
Will this work with the Super D rom?
Click to expand...
Click to collapse
yes! I tried it on Super D!
speedysilwady said:
yes! I tried it on Super D!
Click to expand...
Click to collapse
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
cg87 said:
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
Click to expand...
Click to collapse
Well, to be honest, im not sure why, but im assuming some developers like to include features and apps that arent necessarily required for the rom to run properly but to make their rom more appealing to users, than other roms. keeping those apps in system prevents those apps from disappearing after you wipe your phone/ext. Plus devs always keep ringtones and sounds included in their roms for completeness's sake.
Now a Hero ROM on the other hand is loaded with system apps that cant be deleted and i dont think theyll ever fit on a Stock SPL, except maybe MicroHero, but im not sure.
But for whatever reason, a lot of regular ROMs are fat and bloated with apps and extras that dont necessarily have to be saved on the system partition,so the best thing to do is shrink those roms down till they fit, if you can't or dont want to upgrade your SPL.
How to make it work *WITHOUT TRIMMING*
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Seems someone else is in the same boat as I am.
Can't update my radio, looks like some kind of hardware problem almost. Tried everything in any possible way.
So it looks like we're stuck with the standard or engineering SPL, which is fine but means there are some restrictions.
I'll try some of the tips you gave and flash something besides Cyanogenmod tonight.
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
try the Fix apk uid mismatches maybe idk ill try it in a lil bit
*update*
Got a boot loop on openeclair1.0.1 not sure why but dont got the time to fig. it out right now.
also why does a boot loop drain the crap out of your battery?
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
yea anytime you wipe you would have to reflash the rom because a wipe deletes. data and cache folder
Dr-b said:
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
Click to expand...
Click to collapse
Might be a minor goofup on the permissions. Just verify the permissions and it will be fine.
What programming?
There is no programming involved in this.
Mainly cache is for OTA, but also some other crap related to the download manager.
As for the deathspl allocation, it puts *some* of the /cache into /system, *some* of the /cache into /data, and the balance of /cache remains in /cache.
xile6 said:
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
Click to expand...
Click to collapse
speedysilwady said:
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
Click to expand...
Click to collapse
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
lbcoder said:
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
Click to expand...
Click to collapse
true, with fix permissions, and wipe dalvik, there really isnt much use in wiping data anymore, but would fix permissions still work if the apps are in cache? i know theyre syslinked, but im not sure how that works with the fix_permissions script. sorry if im asking dumb questions, im still learning.
Ill try your idea a really big rom and see if it works.
just wanted to confirm that all Hero ROMs seem to require Danger SPL, I see no way of shrinking system anywhere close to 67 or less.
But my method should still work on any eclair or donut rom. I still havent had a chance to try lbcoder's method though it should work. if people can get lbcoders method to work ill add it to the first post!
Let's begin
1st download all the necessary files:
Motorola 5.4.0 Driver with MotoHelper http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
stock UK XT720 sbf and RSD Lite 4.9 from http://forum.xda-developers.com/showthread.php?t=953863
SuperOneClickv2.1.1 ftom http://forum.xda-developers.com/showthread.php?t=887416
OI File Manager or from Android Market
Open Recovery for XT720 from http://forum.xda-developers.com/showthread.php?t=1242259
CM6 RC3 from http://forum.xda-developers.com/showthread.php?t=1197655
Then proceed to install the windows drivers for XT720,
once that is done flash your XT720 back to factory stock,
to go into ROM flashing mode Hold Power + Volume Down + Camera buttons all at once, be patient, it will take a while and a couple of reboot.
When the phone is finally done booting up, go into Settings > Applications, and check the boxes for USB debugging + Stay awake,
now you can run SuperOneClickv2.1.1 to root your XT720, for step by step rooting instructions follow this guide http://forum.xda-developers.com/showthread.php?t=887416
Next you will want to install a File Manager to your XT720, the stock XT720 doesn't include any file manager,
open a command line (in windows run CMD),
switch to the directory ..\SuperOneClickv2.1.1-ShortFuse\ADB\
run the command line adb.exe install FileManager-1.1.6.apk
The next step is best done using a microSD card reader, then you can drag & drop all the files for your XT720 directly to the SD card from Windows Explorer
- OpenRecovery.apk,
- the unzipped files from OpenRecovery-XT720-01 folder,
- update-cm-6.3.0-RC3-MilestoneXT720-signed.zip,
- gapps-hdpi-20101114-signed.zip
Using the OI File Manager install OpenRecovery.apk (it should be at the root of your SDcard),
run Open Recovery from XT720 stock launcher's app drawer,
select Install Recovery System (allow super user),
then follow the instructions to install OpenRecovery-XT720-01 from http://forum.xda-developers.com/showthread.php?t=1242259
Once you are done proceed to install update-cm-6.3.0-RC3-MilestoneXT720-signed.zip, and gapps-hdpi-20101114-signed.zip using OpenRecovery-XT720 (for details follow http://forum.xda-developers.com/showthread.php?t=1197655),
select clear cache, dalvik, and factory reset
choose the reboot option from OpenRecovery-XT720 menu,
the first boot of CM6 will take a very long time,
when you see the launcher, let it finish loading, then reboot the phone again via power button > reboot,
after this last reboot, the phone is finally ready for normal usage.
Enjoy!
You can get the Dexter's OpenRecovery.apk here
you can use universal androot to root your phone alternatively. its super easy. just drag it onto your sd card (or download directly from your phone), install the apk, and click root. heres a link. http://www.4shared.com/file/HvHnis8C/Universal_Androot_v161.html
I actually did this to a friends xt720 yesterday and I needed to fix the APN settings, he wasn't getting data.
WARNING, about BusyBox newer than v1.17.1 and Link2SD
So i found out the hard way there's an odd bug with BusyBox 1.18.x or newer it conflicts with Link2SD, it wont mount and causes Link2SD to throw this message
Code:
Mount script error
Mount script cannot be created
mount: mounting /dev/block/vold/179:2 on /data/sdext2
failed: no such device
reverting BusyBox back to 1.17.1 fixed the problem
Help on Boot Loop
Followed all instructions here to update to the the cm 6.3.0 RC3. Everything appeared to go as stated, but after reboot i seem to be stuck in a vicious boot loop. I get the cyanogen mod droid logo but it seems to pop up every 10 seconds or so without the phone ever starting up. Any help would be greatly appreciated. It's cute as a paperweight, but not much good as a phone.
Disregard....after rebooting for nearly nine hours....the phone finally started up and appears to be working....Thanxxxx
I too now am unable to access data....i am not skilled enough to work with the APN settings. Could you please help me out on what i need to do to get my data working again...no internet access sux....
AllGamer said:
Next you will want to install a File Manager to your XT720, the stock XT720 doesn't include any file manager,
Click to expand...
Click to collapse
Awesome Instructions bud, much needed for the first timers. Just thought I would add that stock 2.1 always came with quickoffice for me and that's what I normally use at first to install Open Recovery but always end up needing a better File Manager anyway. So either way, I hate to be a stickler just might be one less step lol. Good job AllGamer dude!
Ps.. I should have just said good job dude your way is better lol.
hitech1 said:
I too now am unable to access data....i am not skilled enough to work with the APN settings. Could you please help me out on what i need to do to get my data working again...no internet access sux....
Click to expand...
Click to collapse
Install APN manager from the market and find your carrier there.
You could always just input them manually, doesn't require any skill bud, you just have to google the correct APN configuration details.
nice App
JiroPrinz8 said:
Install APN manager from the market and find your carrier there.
Click to expand...
Click to collapse
https://market.android.com/details?id=ale.android.apnmanager&feature=search_result
this is an Excellent recommendation.
I didn't even know such APP existed
it's so easy to enter APN data... pick and choose, done!
Don't think you should be flashing ROMS if you're hesistant about manually entering an APN, my 2 cents lol.
I would still rather recommend singapore rom, with the tv out and everything. Don't know of any cons with this atm.
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Leotronick said:
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Click to expand...
Click to collapse
I'm not certain but I think this means that Android thinks your battery has more charge than the hardware does. I would first try to redo battery calibration (there are threads in the XT720 general section about how to do this) if you can convince yourself that your battery is actually full. It can be a little tricky.
Leotronick said:
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Click to expand...
Click to collapse
might be your vsel being too low. it happened to me too, and i made the vsel a little higher and it didnt happen anymore.
Hi, I have a noob question...
Can I install this recovery image (CM6) directly from stock Videotron SBF?
I do have install open Recovery based on Androidiani. Can I flash this Rom (CM6) with that recovery or I need something diffrent?
Thanks for your help!
speedmax said:
Hi, I have a noob question...
Can I install this recovery image (CM6) directly from stock Videotron SBF?
I do have install open Recovery based on Androidiani. Can I flash this Rom (CM6) with that recovery or I need something diffrent?
Thanks for your help!
Click to expand...
Click to collapse
if you are already on stock, then yes you can flash CM6
but make sure you are rooted first
and use the Open Recovery XT720 listed in the OP topic
AllGamer said:
if you are already on stock, then yes you can flash CM6
but make sure you are rooted first
and use the Open Recovery XT720 listed in the OP topic
Click to expand...
Click to collapse
Thanks, I Will proceed tomorow.
Regards,
Sent from my MB860 using xda premium
Just installed! Working nice...
Camera and camcorder are working, it was a bug with stock Rom.
Is there a Overcloking kernel for XT720 CM6 rom?
Or is there a way to overclock it with the current one?
Regards et thanks for your help!
speedmax said:
Just installed! Working nice...
Camera and camcorder are working, it was a bug with stock Rom.
Is there a Overcloking kernel for XT720 CM6 rom?
Or is there a way to overclock it with the current one?
Regards et thanks for your help!
Click to expand...
Click to collapse
yes, just download the milestone OC utility from Android market
After searching for ages, I stumbled upon a solution for my tablet. Although all GTab ROMS work in the Zpad, I haven't been able to use the full 1GB RAM present in my Zpad.
So Finally today I stumbled upon a solution posted in slatedroid by Micky.
Instead of flashing the Viewsonic ROM to start with, we need to flash this ROM instead.
After you download the ROM from the link above, search for the TeamDRH CWM 5.5.0.4 and download. Extract the RAR file and replace the recovery.img in the folder with the TeamDRH CWM, cuz the one in the ROM is too old and doesn't support the latest ROMs.
[Note: If you want a larger system partition, follow this.
Open the file flash.cfg and find this no. 209715200 and replace it with this no.419430400
Now when you flash this ROM, you will get a system partition of 400MB.
If you use this method, you don't need to delete any system files after install from the ROM.]
Reboot the tab to CWM and wipe data/factory reset and wipe dalvik cache. Twice.
Shutdown and reboot to APX mode and connect to PC
NV Flash the ROM, let it boot and then shutdown.
Now to flash Jelly Bean.
Download Smoother Bean by nobe1976
Then boot the tablet to CWM
Again wipe data/factory reset and wipe dalvik cache. Twice just to be sure.
Flash the Smoother Bean zip file
Do not wipe data/factory reset or wipe dalvik cache this time.
Just reboot
Let it boot and run for a few minutes.
[Optional: Now install an app from play store to delete system apps and also a keyboard, Swipe or as such.
Open the system app remover and uninstall Gmail and AOSP Keyboard.
A few more apps can also be uninstalled, such as wallpapers, DSP Manager, Music FX, but not all.
Before deleting the AOKP Keyboard, you can copy it from the system folder if you want the stock keyboard. LatinIME.apk file.
(This does not apply if you modify the flash.cfg for larger system partition)
We need to uninstall these apps cuz after flashing with the above ROM, the system partition is only 209MB, so after flashing JB, we get around 5-6 MB free in the system partition. After uninstalling the apps, we get around 34 MB free.]
Hats off to nobe1976. He is able to develop a JB ROM that can be installed in a 200 MB system partition.
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
[After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Its a small request from us Zpad users.
(Note: From the help of all the users, I have been able to increase the system partitiom to 400MB)]
If anyone could help, I will be gratefull, we all will be very gratefull.
This is really pushing the limit.
Edit: Now you can use 1GB RAM present in your tablet and all the space available in the flash memory.
Note: This method can be used in all variants of the Zpad which has 1GB RAM and 16GB ROM.
Note: This tablet is sold by different names all over the world. The one I use is HCL AP10-A1
kank_fraud said:
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
Click to expand...
Click to collapse
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]su -c dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Click to expand...
Click to collapse
Though @rajeevvp is the best person on xda to give you solution that is more logical on this, I will tell you quick and dirty way to do this, which I have adopted.
1> download stock zpad rom if you don't have it already "ftp://112.5.164.225/tablePC/T2_nvflash_mp_3g(WCDMA)_20110824.rar"
2> unzip it, delete recovery.img from unzipped directory, copy part9.img from DRH nvflash which is used for prep 350M system partition to this directory, rename it to recovery.img
3> edit "android_fastboot_full_i_malata.cfg” change "size" of partition id 11 (which is a system partition)
Make sure you do not give any arbitrary size here; calculate it with the formula @rajeevvp posted here "http://forum.xda-developers.com/showpost.php?p=22138304&postcount=14"
4>now nvfalsh your tablet in apx mode with download.bat, now format /data /system /cache and flash whichever rom you want on top.
memory/partition config is supplied to kernel through CMDLINE parameter, so even if you nvflash tab with above procedure, its not necessary that default memory/partition sizes are maintained created by above prcoess, Team DRH boot.img has a blank CMDLINE. That is the reason
Above process will work on most of the ROM, which is using TeamDRH boot.img.
(more technical explaination stright from one of the posts of @rajeevvp "When the bootloader runs, it reads PT (partition 3) and constructs a command line telling the kernel what the partition layout is on the onboard NAND flash. Normally, the bootloader will pass this command line to the kernel as part of the boot-up process. However, if the bootloader sees that the boot.img already contains a default command line then that will take precedence")
I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
Click to expand...
Click to collapse
glad to hear that it worked, BTW you will have to change /system size to minimum 350MB if you plan to use TeamDRH rom in future (hopefully with camera working)
I'll have a try later.Thanks So much.
Thank You all for the help.
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
It shows 419 MB in Titanium Backup
I am happy with it.
Its way better then before.
Thanks evryone
Problem solved
If anyone has formated or resized the internal memory resently, please try the maximum possible size for the system partition.
I tried 512MB but it didn't work. Maybe 490MB might work.
According to my knowledge, Android should support atleast upto 999MB for any partition.
Is it cuz of our tab or is it cuz of the architecture.
And if anyone knows, is it possible to create a larger internal partition.
As in 8GB or if possible the whole internal memory.
CWM doesn't allow more than 4GB internal space.
kank_fraud said:
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
Click to expand...
Click to collapse
Well this was expected result, /system partion resides on NAND flash chip (with is only 512MB) and not on SDcard.
Read this "http://raywaldo.com/2011/07/format-the-gtab/" and this "http://forum.xda-developers.com/showpost.php?p=15558724&postcount=12"
Also you need to bare in mind that other partitions also use 512MB nand flash as per explanation in above threads.
so if you take a close look at falsh.cfg file in nvflash directory you will understand that size allocation is sequential ("allocation_policy=sequential") and system partition (11) which is last to allocate the space, so you need to calculate it accordingly if you want to utilize all remaining space from NAND flash chip.
Well I cant open the page "http://raywaldo.com/2011/07/format-the-gtab/".
So according to this info I have hit the limit. I am already using 489MB of the 512MB flash. And as always, cuz of our storage manufactures, we get only 490MB in a 512MB chip.
What I wonder is why Malata and Viewsonic did not utilise the full NAND space available in the first place.
Is it used for something else.
I mean even the 350MB prep for Viewsonic GTab uses 350MB instead of 400MB.
It is so easy to to utilise and partition the NAND, then why not use the full available space.
What is the empty space used for!???
Or is it just a waste!!!
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
fanguru said:
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
Click to expand...
Click to collapse
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
rajeevvp said:
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo > /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
Click to expand...
Click to collapse
Well I am very sorry for such a late reply. :angel:
I missed your post as I was out of station.
After I came back there were already solutions posted by a couple of users. :victory:
Well today while updating my original post, I noticed ur first reply. :silly:
Well thank you for your reply.
And thanks to all the ppl who provided for the solutions to our ZPad.
I guess the problems are solved for now.
:highfive: :highfive: :highfive: :good:
kank_fraud said:
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
Click to expand...
Click to collapse
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
kank_fraud said:
I guess the problems are solved for now.
Click to expand...
Click to collapse
I'd still like the output of those commands--for my own edification.
fanguru said:
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
Click to expand...
Click to collapse
Well for Me it worked the first time itself.
Why don't u try giv it a few more couple of times. :laugh:
BTW, are you using the Malata Zpad or Viewsonic Gtab
If you are using Gtab, try TeamDRH method but modify the size of the partition.
If u are using Zpad, try again.
Clear cache and reset before installing.
Try previous older ROMs and gradually update to newer ones.
Reset and wipe before each update.
As I didn't get any problems, so I can't say whats wrong with your installation.
And very sorry for the late reply.
I have exams.
But my tablet is very stable after this.
Everything is running smooth, even HD games.
Goodluck :fingers-crossed::fingers-crossed::fingers-crossed:
rajeevvp said:
I'd still like the output of those commands--for my own edification.
Click to expand...
Click to collapse
I tried it in terminal emulator, but it says 'Operation not permitted'
kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
same here.
kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
Fixed commands. Try them again.
I seem to have everything running and it seems really fast, the only problem I have is that the home button (hardware and soft) does not work!
I've tried installing a different home app, tried home switcher and I get asked when the tablet boots as to which home app to use, but still the buttons don't work (back and recent apps work).
Any ideas???
Hey XDA ! =D
I'm still interested in installing Cyanogenmod 10 on my LG Optimus One P500h, but I want to make sure I follow the steps properly first - this is my first time installing a custom ROM, and when I heard it was possible to install Android 4.0 on the P500h, I performed a backup from ROM Manager, and I "bricked" my device a few days ago. XD
I wouldn't want this to happen again, but at least, I must say I have more experience now, and learned a lesson.
Did many searches on how to install CWM with Cyanogenmod 10, I found many different ways to do it, and I'm still unsure of which procedure follow.
Read the FAQ and that was really helpful.
I will list the procedure that I would normally try - please correct me if I forget anything:
0. Root the device
Done that already. I'm on Android 2.3. When I flashed the KDZ on my LG (and so to my surprise, got me updated from 2.2 to 2.3.3) , I've used V20A_00.KDZ, so I *assume* this is the second baseband.
1. Compact/Trim Cyanogenmod ROM
Downloaded CM10 here. This look correct: http://forum.xda-developers.com/showthread.php?t=1811325
January 8: Build 7/Final
I chose C10 over C11 because more things are compatible I believe - was it Bluetooth that did not worked under C11, but does on C10 ?
Anyways, that solve a known problem: many users said they loose network after the ROM installation. Shinobisoft confirmed it was because of the lack of space on the System partition, right ? Compacting the ROM would also fix problems for installing Link2SD ?
I've downloaded the tool "OOne ROM Editor" and opened it - it doesn't look complicated at all. What apps are safe to delete ? Will converting them to "user app" save space for system apps (I'm not sure - Where are the apps stored when defined as "User"? SD card rather than /System ?) ? Can I delete fonts without problems (I don't see why I can't keep ONLY 3-4 fonts, not 10) ? Then how much space will be left on the device ?
Read I cannot delete LatinIME.apk. Is this the default keyboard? 20MB is huge, there's no way to compact this file, right ?
Assuming there's like 10MB free, network will work, but I will have no choice but to use Link2SD to install apps fully on SD card, is this correct ?
2. Baseband stuff
Ehm, what are we referring to as "baseband" in first place?
All ROMs starting with CM7 are new baseband. If your device had Android 2.2 prior to flashing, you are on old-baseband. There is a patch for that also in the LG Optimus One FAQ on the first page, not sure which post off the top of my head tho. If your device had Android 2.3 on it then you have a new baseband device which shouldn't require any patches.
Click to expand...
Click to collapse
Allright, this should make this a lot easier - as I said, I originally was on Android 2.2, when I bricked the phone, I flashed "V20A_00" throught KDZ Updated, then I rebooted as 2.3.3, so I shouldn't do anything, right ?
In "About Phone", it's listed "Software Version: LG-P500h-v20a".
3. Install ClockworkMod Recovery
This look like the tricky part.
A lot of people on other sites said to use ROM Manager...
shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
Click to expand...
Click to collapse
ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Click to expand...
Click to collapse
Yes, ROM Manager is completely broken in this regard. It needs to download a signed ZIP and discard it and report an error when verification fails. Heck, ZIP format has even its own CRC check. What ROM Manager is doing (download whatever .IMG and flash it no matter what) is a nice WTF! Broken by design, go rewrite from scratch!
Click to expand...
Click to collapse
I don't trust the use of ROM Manager anymore on my device, and I'm not comfortable with using it again. I actually wonder: When I press VolumeUp-Home-Power, the phone perform a factory reset (Many people asked already why. This apparently mean that CWM is not installed).
But is it really installed? ROM Manager actually says: "Actual Recovery: ClockworkMod Recover 5.0.2.0". What? Am I supposed to press VolumeUp-Home-Power to verify, only to do another factory reset?
So what would the non-ROM-Manager method be ? I found this one here:
http://forum.xda-developers.com/showthread.php?t=1146566
I know about the Android Terminal Emulator already, and as a Linux user on PC, the commands "su", "cat", "chmod", "mount" are not unknow to me. I should be able to do this... That's not risky ?
So when CWM will be installed, I should be able to boot in it using "VolumeUp-Home-Power"; in theory, this is a bootloader, so if the ROM get screwed up, I *should* be able to access the bootloader to restore the ROM (I compare this to a PC BIOS - the OS is screwed, but BIOS remain accesible) ?
How could I explain that when I bricked my device with ROM Manager, I couldn't perform a factory reset, and only had access to Emergency Mode (I assume there is not such thing as a "Recovery Mode" on a P500h stock, new/untouched. The equivalent immediatly perform a factory reset) ?
All Android devices have a recovery partition. This is essentially a section of the device’s memory devoted to a very basic recovery system that is separate from the normal operating system. This is normally used by manufacturers for recovering a broken device (as even if the operating system crashes, the recovery image has a chance of still being access and used to reflash the operating system, etc.).
Click to expand...
Click to collapse
By default, the LG P500h recovery partition perform an immediate factory reset - CWM will be installed here, so I should be able to access it if the ROM freak out. But why couldn't I access the factory reset, when I bricked the device? That's what I wonder.
4. Access CWM and do a Nandroid Backup to SD Card
I will now have the files boot, cache, data, recovery and system, as well as"nandroid.md5" on SD card.
5. Wipe everything, clean SD Card
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
Click to expand...
Click to collapse
6. Partition SD card (?)
Is this at that point that I should do it, in CWM ? Or wait until I access Cyanogenmod and use a software on PC to partition ?
Assuming I don't partition, I guess I definitely will lack space for applications (Due to the space of Android 4.0) ?
I will do "Partition SD Card>EXT4 1024MB>Swap:64MB. Is this correct?
7. Install Cyanogenmod
Install ZIP from SD Card, choose the CM ZIP;
8. Install Google Apps
Once the install is done, I won't reboot and immediately install Google Apps, with "Install ZIP from SD card". I chose this package (Working on JellyBean):
http://forum.xda-developers.com/showthread.php?t=1917411
Then I should reboot in CyanogenMod and finally install Link2SD, I believe.
***
..Did I forgot anything ?
I *believe* that makes sense, but this is my first time installing a ROM - I doesn't look *that* hard, I did researches, but things can go wrong... :/
What should I do if I screw things up? Use KDZ Updater again ?
I'm still a little worried about that baseband thing, and the lost network connection.
Thanks for the input, cheers!
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
GameX2 said:
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
Click to expand...
Click to collapse
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Allright, I got it!
I saw the success message, then used the keys to reboot in recovery, that worked!
At the boot, I can read "ClockworkMod Recovery v5.0.2.0 E: Bad boot message "recovery ".
I believe the "E: Bad boot message "recovery " is a known issue, and but is not a problem - please let me know if I have to do anything about this.
So now I will compact the Cyanogenmod ROM (I don't know how much space I should free, but I'll try to free a decent ammount), and perform a Nandroid backup to SD card.
I believe the hardest/scariest is done. From now, if the ROM install fail, I could just restore the backup, I guess.
Are they any case when CWM is unaccessible (When I bricked my device, I had no access to stock recovery (which only perform factory reset) but just Emergency Mode. Why was that?) ?
Thank you, I will let you know about the rest.
(Will press the thanks button at the end I don't know if it's OK to thanks on multiple posts on one thread, on this forum)
EDIT:
That error message means you dont have SD-ext. Ignore it.
Click to expand...
Click to collapse
EDIT 2: Nandroid backup succesfully taken! I now have the files .android_secure.vfat.tar, boot.img, cache.yaffs2.img, data.yaffs2.img, nandroid.md5, recovery.img and system.yaffs2.img. Will backup these on my PC.
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I appreciate the information;
It's quite akwards that ROM Manager broke everything (And I asked for a BACKUP - that's so broken, it brick the device when you want to BACKUP <__<) - when it rebooted, it was in Fastboot mode, and I never saw that mode before. Tried a few recommended commands without problems, but when I rebooted, I only had access to Emergency Mode.
What would be informative for me to know, is that ROM Manager seems to not only have screwed the ROM, but the stock bootloader as well. Weird.
Shinobisoft said we need to compact the CM10 ROM with his utility first, because the System partition is too small (Otherwise, I will have no network). I will do that, I have the tool, that doesn't look complicated.
From now, I am backing up my SD Card content (DATA is backed up too) with Nandroid present on SD, so I could start formatting, immediately followed by SD partitioning.
I guess I should be fine at that point - if anything goes wrong, I should have the option to restore the Nandroid backup.
Will let you know when I'll have the ROM compacted (Probably today).
EDIT: YAY !
Everything worked as we expected! I saved my SD Card on my computer, wiped it, partition it from CWM (EXT: 1024MB, SWAP: 64MB. I have a 16 Micro SD, class 4 (Can't afford higher class much, for now), then installed the compacted ROM. Immediately after, I installed Gapps, then rebooted.
That worked !! This ROM is DOPE ! Totally worth upgrading ! Blazing fast !! (Will be slower with apps installed, but well)
I also have a working network!
There is one thing that "failed", I cannot get Link2SD to work. It always says "cannot create mount script". I checked with Windows (I know by experience that I should absolutely not edit Unix partitions in Windows, I just check), and the FAT32 partition is the first, then I have a EXT4 partition, then the Linux-Swap, I don't know why it doesn't work.
I used Gparted to format the EXT4 partition to EXT2, but same problem, "cannot create mount script". What am I supposed to do ?
Thanks youuu !! =D
I'm really happy to have done this on my own, with help - I now have more experience with Android, I have experience with Windows, Linux OS and OS X, but never did I tried flashing a ROM yet.
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Hi,
Tanks for replying. out of 200mb, I have 70Mb free, but on /data. Last time i checked, /system was almost full (where can i check system size?).
Seems like lot of people have this link2sd issue.
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
@akiratoriyama
Yes, that's right. You can check /system space by using Root Explorer. Or go to
Settings>About phone>Partition info.
I got 10+MB space left on /system partiton after trimmed the ROM and installed mini gapps.
You're right, Link2SD only works if there is 3MB, at least, left in system partition.
Sent from my LG-P500 using xda app-developers app
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Click to expand...
Click to collapse
It worked !!
Geez, I went to 170MB of internal MB to 1GB, that's just plain insaneee !
Now I can use my LG P500h for an extra 2 years.
ibub said:
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! I was confused, because sd-ext2 at root is empty - nice to find it in /data/sdext2.
Suceess !!
Thanks !!
How Do I Install?
GameX2 said:
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
Click to expand...
Click to collapse
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Drachinos said:
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Click to expand...
Click to collapse
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
I guess I was thinking too much (or not at all!) Simplicity is the key a lot of times!
I tried all of the points in this thread and now this Optimus One has root, recovery and a new ROM. Thanks everyone! :good: