Related
Over the last few days, I've been cooking up a ROM using the Incredible S system dumps and nandroids. Problem is, it doesn't work It flashes fine, everything works there, but when I boot up my N1, it stays on the Nexus splash screen (the one with the X on the padlock on it). If any devs could have a good look at it, and see if they can find the source of the problem I'd be eternally grateful When you've found the problem and confirmed it works, PM me the file, tell me how you solved the problem, and I'll just check everything is in working order, then upload it. I will also put your username in the thread!
I used the HTC Android Kitchen (link here) to make this, so you might want to use that.
Incredible S
Link to latest ROM
The zip is: 224.0 MB (234929825 bytes)
Desire S
Link to latest Desire S ROM.
The zip is: 233.1 MB (244429351 bytes)
Thank you devs,
redbullcat
I doubt you could get the whole image on the phone, 224mb is way to big without scripts to move files over to another partition.
http://forum.xda-developers.com/showthread.php?t=784260
That is 268mb and is a Sense ROM, so 224mb should fit.
I think that the system directory is way too big to be installed on a nexus one.
You should move some of the system content to data or move it to an ext3 sdcard partition.
What they said.
Put attention that even the ROM you linked REQUIRES A2SD partition, which it'll set up and use.
So to move the content from system to data: is that just a straight drag and drop procedure, or is some converting to make it work in data rather than system required?
Sent from my Nexus One using XDA App
I am not an expert in the porting roms topic but if I am correct you will have to symlink the things that you move.
This can be done modifying the updater-script.
OK, thank you
Sent from my Nexus One using XDA App
How would I move the stuff from system to an ext3 sdcard partition?
Sent from my Nexus One using XDA App
Good thread. Sounds like a simple matter of setting up a2ext.
Nice work dude!
I would take a look at eViL's desire HD port since its going to be the most similar to this ROM....
That should help you in figuring out what is/isn't okay to move to SD....
Sent from my Nexus One
Thank you thanks also for the tip
Sent from my Nexus One using XDA App
How big should the system and data directory's ideally be?
System - 140 MB is the phone limit, so I wouldn't go above 120-125 MB.
Data - all the rest, as much as you need. You're installing to EXT anyway.
Can you provide a LOGCAT when booting up?
MrNameless said:
Can you provide a LOGCAT when booting up?
Click to expand...
Click to collapse
I can certainly try
OK, so I've moved stuff to a folder in the root of the ROM called ext, as that is what was in the NXSense-HD ROM by eVil. Problem is, the system directory is still 20mb too big. The folders in system:
bin
etc
framework
lib
media
sd
usr
xbin
and build.prop
What can I move to ext/data from this selection of folders? I moved from system to ext:
app (now called system-app)
customize (now called system-customize)
fonts (now called system-fonts)
Thanks,
redbullcat
I'm not a developer, but if you move one folder to ext partition and create a symlink to this folder in system partition? Shouldn't it work?
Sent from my HTC Desire using XDA App
Atento said:
I'm not a developer, but if you move one folder to ext partition and create a symlink to this folder in system partition? Shouldn't it work?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I don't know if any folder can be moved though. For example, framework may not be movable.
EDIT: So I've moved some stuff from system to ext, but now the update-script is giving me grief. I'm trying to follow eVil's update-script, but it doesn't seem to be working. Does the update-script have to be done manually, or is there an automatic generator?
I've tried and tried, and I can't seem to get it to work. Could somebody either link me to an update-scipt generator, or help me build an update-script? I'd be so grateful
I found a fix on XDA forums right here. Instead of 'asia' I input north-american into the gps.conf file. For those of you that don't want tolook for the file, I have supplied the gps.conf file for you to download right here. Post responses with how well this works. Works 100% of the time for me nearly instant locks on all gingerbread ROM's I put on my device.
If you are downloading my file, simply use adb to push it to /system/etc/ and you are golden.
**Warning|Disclaimer|Blah Blah**
If you brick your phone I am not responsible ... yadda yadda, ya'll know the drill.
thank you! that did solve the problems i've been having with the latest cm builds.
Wow! Thank you so much! I went from a 2+ minute lock to a <20 second lock.
I did find a method to make this adjustment simpler. I used root explorer, available in the market, then simply copied your 'gps.text' file to system/etc. I then deleted the gps.conf file and renamed gps.text to gps.conf. Finally, I rebooted and opened maps, enabled gps, and waited for a lock. Then, after I was locked I did one final reboot and behold, locked in less than 20 seconds.
So, maybe not simpler but it can all be done without adb, straight from the phone.
Nevertheless, thank you, thank you, annnnnd thank you!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Did you guys use his file or make your own? Mine already said North America but was missing the extra servers.
skulnik, is your phone s-off? I can never make that kind of change with root explorer. It acts like it did something, but it doesn't. Same with ADB if the phone is on.
I read on another thread that apparently if you are s-off, you need to go into recovery, mount system and then use adb to push the files.
I am not sure this worked for me though, once I got the file in there, nothing much changed. I used the old fix which involved putting the cm6 gpslib.so file into the system/etc folder. Using both, I seemed to get a quick lock.
I made flashable fix for myself that includes both fixes and the wifi fix (just in case) and things seem better on both CM7 and the xm rom based on CM7.
The extra servers is what made the difference for me. Glad that this is helping. I stopped using cm7 for the longest time because GPS wouldn't lock for me. I loaded the xm7 and is was so awesome I just HAD to find something to make GPS work because I rely on it all the time. Downtown San Antonio is very easy for me to get lost in and MapQuest was never reliable.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I used a different file after reading his method. However same concept of replacing the config file. I'm just rooted without s off. Another method to replace the file is to mount via clockwork and use android commander to push the file. FYI after this i now I get an accurate gps lock in under 10 seconds.
WhoWhere said:
I used a different file after reading his method... after this i now I get an accurate gps lock in under 10 seconds.
Click to expand...
Click to collapse
What file did you use or what did your file contain? Locks are still taking around a 1 min for me.
ovar said:
What file did you use or what did your file contain? Locks are still taking around a 1 min for me.
Click to expand...
Click to collapse
I used the gps.conf file for the us midwest file on this thread: http://forum.xda-developers.com/showthread.php?t=953630
WhoWhere said:
I used the gps.conf file for the us midwest file on this thread: http://forum.xda-developers.com/showthread.php?t=953630
Click to expand...
Click to collapse
Thanks a ton. Instant locks!
WhoWhere said:
I used the gps.conf file for the us midwest file on this thread: http://forum.xda-developers.com/showthread.php?t=953630
Click to expand...
Click to collapse
You just used the gps.conf file right? Nothing else?
jacewt said:
You just used the gps.conf file right? Nothing else?
Click to expand...
Click to collapse
Yep thats all I did. But you may want to use a different file based off your location if you aren't in that area of the us
WhoWhere said:
Yep thats all I did. But you may want to use a different file based off your location if you aren't in that area of the us
Click to expand...
Click to collapse
Thanks! I used the southwest file and I am getting real fast locks, even indoors. I wonder if I need to keep a northeast file for when I travel east.
Just want to make sure i get the steps right, all i have to do is unzip the .zip file, put gps.conf in platform-tools folder for android sdk, run adb and type "adb push gps.conf /system/etc/" right? It's been a while since i did any sort of work with adb, so i don't want any major goof-up.
txdeathray said:
Just want to make sure i get the steps right, all i have to do is unzip the .zip file, put gps.conf in platform-tools folder for android sdk, run adb and type "adb push gps.conf /system/etc/" right? It's been a while since i did any sort of work with adb, so i don't want any major goof-up.
Click to expand...
Click to collapse
You could do that or a more foul proof method would be to use android commander. Just mount the system in clockwork plug your phone in "assuming you already have adb, jdk etc. Installed" and push it that way. Android commander is pretty much a gui for adb... also could push it in terminal emulator if you were feeling adventurus. hope this helps. Android commander is most likely going to be the safest method for you. That way you can easily do a backup of the file. Though I would do a nandroid backup just to be safe.
WhoWhere said:
You could do that or a more foul proof method would be to use android commander. Just mount the system in clockwork plug your phone in "assuming you already have adb, jdk etc. Installed" and push it that way. Android commander is pretty much a gui for adb... also could push it in terminal emulator if you were feeling adventurus. hope this helps. Android commander is most likely going to be the safest method for you. That way you can easily do a backup of the file. Though I would do a nandroid backup just to be safe.
Click to expand...
Click to collapse
Haha thanks, definitely gonna give Android commander a try. And definitely gonna remember that nandroid backup (lol, learned it the hard way today).
txdeathray said:
Haha thanks, definitely gonna give Android commander a try. And definitely gonna remember that nandroid backup (lol, learned it the hard way today).
Click to expand...
Click to collapse
Sorry guys, no dice for me, same performance as before.... dunno why...
Sent from my T-Mobile myTouch 3G Slide using xda premium
Ekorshus said:
Sorry guys, no dice for me, same performance as before.... dunno why...
Sent from my T-Mobile myTouch 3G Slide using xda premium
Click to expand...
Click to collapse
hmm can't imagine why it would be different for you. Did you push the correct GPS file for your location & confirm that it took the change /view the file after you pushed the file/rebooted your phone?
Yeah, took the midwest file & moved it to the system/etc folder & removed the old file., did it all w/ root explorer rebooted the phone & everything... got the same performance as I did before, 2 min or so for a lock. Then consecutive, immediate locks as long as I didn't leave the maps app alone for too long.. @ one point I wound up using gpsfix to actually get a damn lock, it was so bad....
I'll just have to settle for slow locks.
Sent from my T-Mobile myTouch 3G Slide using xda premium
Ekorshus said:
Yeah, took the midwest file & moved it to the system/etc folder & removed the old file., did it all w/ root explorer rebooted the phone & everything... got the same performance as I did before, 2 min or so for a lock. Then consecutive, immediate locks as long as I didn't leave the maps app alone for too long.. @ one point I wound up using gpsfix to actually get a damn lock, it was so bad....
I'll just have to settle for slow locks.
Sent from my T-Mobile myTouch 3G Slide using xda premium
Click to expand...
Click to collapse
Hmm. I wonder if it's a hardware or driver problem. One thing I did want to note; I had tried using the latest version of root explorer to replace the file, mounting the system as write, etc prior to using adb. The result showed the file as being replaced however after rebooting to confirm changes the file was back to default. It might be worth double checking the file to confirm that the replacement actually took. If not possibly mount the system in clockwork and push the file using adb.
Hmmmmm, good call, I DID make sure to mount the system as r/w as opposed to r/o but I didn't chk to see if the file got overwritten by the system on restart (if I'm understanding you correctly?).
I'll try it again, this time using adb...
Sent from my T-Mobile myTouch 3G Slide using xda premium
so I have a question about managing backups from our bootstrap recovery. This might be a stupid question but I have a lot of backups from the recovery and I was wondering how you can delete/manage these backups; I want to free up some more space by deleting them. I am currently on dragonzkiller's CM7.
I believe its under SD card/ clock work mod/ backups
sent from my mixer themed X duce
03civicdx said:
I believe its under SD card/ clock work mod/ backups
sent from my mixer themed X duce
Click to expand...
Click to collapse
Just navigate to the folder that 03civicdx mentions with the file explorer app and delete the directory or directories in question that reside in the backups directory.
mmk i got it to work. Thanks guys!
I have a back up from every ROM for our phone so I know how you feel. It got really confusing which one was which! But they are on the external or internal SD card (depending on which you picked when you backed up) under a file called clockwork. To figure out which one is which, you can rename them. They will have numbers like this:
2011-12-13.07.17.47
DONT mess with the numbers otherwise you just lost the back up. So at the end of it, put a . and what ever you want to tell the difference from other back ups. So it'll look like this:
2011-12-13.07.17.47.Molten
You can type what ROM KR what theme or what ever you want, just make sure you put a period AFTER all the numbers. To delete them, just delete it through ES File Explorer or Root Explorer
Sent from my MB870 using XDA App
You may mess / the num. JUST DO NOT USE SPACES. Also add to yo cwm folder the empty FILE ".hidenandroidprogress" and cut 1/3 off BU times.
Whaaaat! Ru serious? That's a cool tip! I also agree, the file name changed to anything you want, just no spaces.
Sent from my MB870 using XDA App
Hah, sweet! I didn't know that, I was told the other way. Thanks for the correction, going to go in and change the names, and thanks for the tip in .hiddennandroidprogress file!
Sent from my MB870 using XDA App
hide not hidden.
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Well presumably this is how ROM Manager and Metamorph both do their thing, just in a slightly more round about way (as they don't come with the files they need to copy). I'm almost 100% sure this is possible, but I've never tried it personally.
EDIT: Looks like this is how you'd do it: http://developer.android.com/reference/java/io/File.html. Specifically the renameTo() method.
CelticWebSolutions said:
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Click to expand...
Click to collapse
Well there are about a dozen ways to do this. First of one of the hardest things is comming up with the commands/script. I can defiantly do this. If you want an apk, there are a few guys whom could port my script to an apk. I'm going to make a script here that will format, and create partitions and extract directly from the nook, no need to go through the fancy formatting and such, just go into terminal and run the script. Ill post a prototype for you to have the testers test!
Do you think something like BacksideUpdater inside custom ROM for LG Optimus V?
made by JerryScript
JerryScript i very nice guy, I bet if you ask him, he will let you play with his code
if is it what you looking for
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
xdajunkman said:
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
Click to expand...
Click to collapse
So one of the problems is its not really copying. Its more of an extraction from one place to another. We are required to use dd, and fdisk(for formatting).
GREAT! I was worried updates would be to complicated for people
Sent from my Nook Tablet using xda premium
... and I was worried that I might have to wipe my NT clean again to get the updates. After a week with this wonderful upgrade, I've got a LOT of customization I don't want to lose...
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Sycobob said:
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Click to expand...
Click to collapse
Has to be simple, something like copy an update.zip onto the SD card then run the apk which will automatically run the update in the zip But my knowledge of such things is limited so I need help there
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Sycobob said:
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Click to expand...
Click to collapse
Hmm.... that sounds good.
Anybody know how to actually implement it ?
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.
The only downside to all this is that I don't know how you would flash a kernel.
Sycobob said:
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Click to expand...
Click to collapse
That makes two of us!
Sycobob said:
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.The only downside to all this is that I don't know how you would flash a kernel.
Click to expand...
Click to collapse
I'm guessing you'd just flash it as usual, surely that one is the easiest? Copying stuff to boot partition would hopefully be just as simple, I was mainly worried about updating system files. I could do with building one for the current update to test the theory!
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
waldojim said:
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
Click to expand...
Click to collapse
Well, I found a solution for now. Fire up Linux, use cat to combine all three files, then use tar to extract the contents. Not sure why this needed split in the first place, but at least the files can be extracted.
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
waldojim said:
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
waldojim said:
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
Click to expand...
Click to collapse
I guess what I meant to say by "zipped" was just in general they are compressed by the recovery in a way that it knows how to go and use them to restore data to the device.