I've been flashing various ROMs, but continuously am running into force close/waits, lag, apps shutting down, but only random reboots on one of the ROM's and it got fixed. I get fc/w's on android.process.acore, calendar storage, alarm clock, you name it, I've probably had it error out on me.
I'm wondering how I can clean up my phone entirely.
I don't know what a ROM writes, or doesn't, but I think I've got something in there that escapes a wipe and a flash that seems to be interfering with the system.
I'm not the only one in the Cyanogen's Experimental thread, nor the lastest stable thread that has had this issue. I haven't been keeping up on the other ROM threads, so I can't say if anyone has had these issues with other ROMs or not.
The Mod on Cyanogen's thread has recently threatened bans for non-ROM -related posts, and to be honest, I don't think this is the ROM because it happens to few, but not all. I'ts not a ROM related question, since it shouldn't matter what ROM I'm using, if I'm rooted, I just want to clean off my phone entirely.
I'm also wondering f these issues could be hardware related, perhaps a different manufacturer of a chip or something.
So, how do I really scrub the thing?
From what I understand, going back to a stock, unrooted phone and going through the rerooting process should "unclutter" things.
I followed this how to
http://forum.xda-developers.com/showthread.php?t=491350
I think I solved my issue
Going back to an unrooted phone doesn't deal with anything on the apps2sd partition that might be messing things up if I go back to it.
I ended up deleting the ext4 partition on my card and recreating it. The last time I cleaned up, which didn't do the trick, I just deleted everything I saw. I don't know if there was something left in lost&found or something hidden, but that's what I did.
I also flashed from RC29 instead of JF1.5.1. The first time I thought it would be easier to flash to a ROM I had on my PC that already had Terminal Emulator and Telnet already on it than to download the two apps. I don't think anything would get left in place from that, and I think people have had success with flashing CM's from JF, so I doubt it was that, but who knows. I did both just to be sure.
I also didn't enable any swapping, but i can't imagine that swapping would create acore force closes. ???
So, flashing from RC29 and starting from a freshly created ext4 did it for me.
Every time I try to flash a Hero ROM, I get an error of sorts during the copy file portion saying that a "xbin" file of sorts is missing. I had JACxROM on the phone, and tried to go from that to a Hero ROM, with no avail. I just flashed to the newest CyanogenMOD no problem(I did flash the HTC ADP 1.6 recovery img first)
I have the newest radio, deathSPL, as well I have the RA1.2.3 recovery image. Is there something I am missing here?
Do I need to downgrade to 1.5, since as it stands I am running 1.6 ROMs?
Or is it likely something else was a "bad flash" and I should just go back to R29, and work my way forward from there?
are you sure you have the "death/danger" spl installed on your phone? make sure, but even if you don't, why not just install it again, it repartitions the phone memory, and makes it clean when you flash things on top of it.
that's the most common problem for xbin errors when flashing a hero rom , it's too big to fit in the stock system memory alone. Try re-doing everything. Make sure your ext partition is clean (format that) , do a wipe to clear cache/data, repair ext partition,
and if all else fails, maybe you might just wanna repartition your sd card, might have broken/corrupted partitions.
maybe you might even have a broken sd card. and you might have to get a new one
lotta maybe's , but try trouble shooting random things.
hope you can find your answer, noone can exactly help you with this one with any sorta direct guide or how two since they're not there to deal with your phone on site
goodluck flashing!
Thank you! I figured it could be one of many things... I am starting fresh, doing RC29 forward.
I am certain I had death, et al, I have been a bit of a lurker for a while on the Android end, and finally got a G1 about a week ago, so I don't have a lot of experience with it, but I have over a year with a Kaiser, and for several months I ran Android on it.
I tried a couple differnt SD cards, and unless both are dead, I think it is just a bad flash somewhere along the way that didn't show up until that broken file system got tested with a Hero flash.
Anyways, I am confident I will get it sorted out eventually. I am smart enough to not brick the damn thing...fingers crossed... not really, I should be all good.
YAY!!!!!!!!!!!!!!!1
I think my first time through I didn't wipe at some point I should have.
I’ve just updated from MoDaCo’s 1.5 ROM to the CM6 2.2 ROM and since it’s been so long (over a year) since I’ve rooted my phone and dived into all the information involved in doing so. Back then it wasn’t as easy as it is now with some of these rooting methods. In fact I remember it being a real mess ha. (http://forum.xda-developers.com/showthread.php?t=583291)
So basically, I’ve managed to do quite a lot of things and I want to help a friend out but I want to make sure all my info is right.
ALL of this is basically on giant question. I just word it as if I know what I’m talking about. But please help me correct everything that is wrong (and I know there is a lot), help answer some of my questions, and even let me know where I’m right. I didn’t type everything up as questions so that it reads easier. If I need to repeat some sections to get clarification I can.
Customizing you Phone
The first step is to gain root access via installing (flashing) a recovery program (image).
This program (image) is only accessible via boot (boot into recovery). It allows you to make a back-up of the phone in its entirety, restore said back-ups, allow PC access connectivity (via USB), flash programs/files (“installing” in a sense), partition an SD card, perform various wipes, and some miscellaneous things.
Ok – I’ll pause here to get some info. Wipe Data/Factory Reset; this means erasing everything off the phone and it resets the current ROM back to its native state. Wipe Dalvik-cache… I’m not sure what this does exactly but I assume it has something to do with the programs installed or the SD card. Furthur, why would I want to ‘wipe battery stats’ or ‘rotate settings’ ? And wipe SD:ext partition has to do with Apps to SD?
Also, when you do these wipes and flashes and re-do your phone from scratch, the only thing that is never touched is the recovery image. It’s fair to say, when you flash the recovery image during your rooting, it’s the only set in stone thing on your phone… that is until you re-root your phone or flash an alternate recovery.
Apps2sd – When I first rooted my phone and installed MoDaCo’s ROM, I ventured into the land of Apps2sd. This too was a PAINFUL process partitioning my SD card and learning all about the ext2/3/4 and I’ve already forgotten everything. After going through all that to clear up what little space I had on my Hero, I then read all kinds of people saying Apps2SD is bad cuz it’s slow and blah blah. So I took it off. Now it seems that Google has made an Apps2sd native? I just need updated on the whole Apps2sd thing both in general and for the Hero.
Ok – Back. Some of the things you can flash are custom ROMs (a ROM is the Operating System essentially), data that tells the computer to work differently such as custom kernels (what makes the phone work, basically communication between hardware and software), new radios (what retrieves and uses signals), and battery stuff (what would it be called? “Battery kernel info”? haha). You can even flash programs right to the phone (apk files).
The biggest reason to root your phone, is to install a custom ROM. Custom roms typically cut out a lot of bloat that the stock OS would have such as un-removable programs (Sprint NFL and NASCAR… Thanks but no thanks Sprint) and OS things. Many developers have even tweaked ROMs to optimize performance and battery life. Why would the stock ROM not do this? And why would it seem the dev’s (developers) making custom ROMs are better than the devs at Google/Sprint/Samsung/etc.? Certain applications also require rooted phones (or just simple ‘root’) due to their extended abilities or required securities (such as WaveSecure?).
Reminder – everything is a question even tho some things have ‘?’ and some don’t. I know that I do not know what I’m talking about. I just want to confirm what I do know, and learn where I’m wrong!
Now some straight up questions:
When you get a custom recovery, ROM, and kernel on your phone… you’ve just about altered all major parts of your phone (software speaking of course)?
When you want to put on a custom ROM, you first wipe everything then flash the ROM. Then you may flash additional items such as gapps (google applications pack), custom Kernals, etc. When you want to change roms, do you have to undo everything and start from scratch and put new gapps back on, a new kernel, etc? What about just updating a ROM? What if you have a ROM you like, but just want to un-install(un-flash) gapps – possible?
[*]So example, If I needed something I forgot on an old setup – like a text message or file from EasyNote, I would have to nandroid backup, wipe everything, flash old ROM and additional files, restore OLD nandroid, grab the files, wipe everything, flash back newer ROM and additional files, restore new nandroid that was just created to be back where I started? (I actually have to do this too haha – want to make sure that’s right.) Basically I’m making sure I’m right about nandroid. It back’s-up all data and setting type files for current ROM?
What would happen if I tried to restore a nandroid back-up created during another ROM?
MoDaCo’s old custom ROM had WaveSecure installed with it so that it could not be removed. Is it possible to still do this with other ROMs?
Why do some people talk so negatively about gapps? Is there something wrong with them?
Back when I first tried learning all this a year ago, the Hero’s messaging app was known to be a real battery-eater and never slept so it was recommended to switch to a 3rd party and disable the stock app’s notifications. What’s the development on that?
I still have a whole paper full of other questions, but I think this is already getting loooong… so I’ll leave it here for now. The point of all this is to yes, educate myself so that I may help others…. But I plan on writing up a real all-inclusive guide to android and rooting and the like. I’ve searched a lot and learned a lot, but nowhere (including the wiki) did I find a nice, chronological guide of information. Hopefully I can fill that niche once I know exactly what I’m talking about, and even then I’ll need some peeps to clean my stuff up a bit. I also happen to be a filmmaker so I’d like to make a good video on this as well. It won’t be one of those videos where you can barley understand the person talking, shot in the basement with all the lights off, camera held in hand and shot with web-cam, etc. (Note: Just today I saw the XDA-TV post… sorry I missed it) D:
LAST NOTE:
Ok I promise I’m almost done. I just wanted to say that if anyone would not mind talking on the phone… I would love to just blow through this stuff a lot faster and be able to have a convo with some 1 on 1 feedback allowing me to get lots of questions answered. Even just 10 minutes would help me out tons! So if anyone who is a genious on this stuff (like devs… ) and wouldn’t mind chatting for a few – please PM me. I can do Skype as well.
I hope someone will take the time to answer you, it will help me too LOL. Last thing I rooted was the G1 years ago, & just yesterday rooted the Hero (& flashed CM6 today) I got off of Craigslist. Seems like some phones have better wikis than others.
I haven't been in the rooting/flashing game for a while since I've owned tons of different devices before & after the G1. Since then the only flashing I did was flashing Android onto a WM device LOL. Never bothered flashing the Vibrant, Epic, or Evo (sold, sold, & sold.)
Anyway, yeah, I hope someone answers! You have my support!
Root and recovery are two totally separate things - you can root your phone and not flash a recovery, it's totally up to you. Root gives you access to things on your phone, that you would otherwise not have - like flashing recovery, ROM(s), apps that need root access, etc. Goto the wiki there's a link which gives a high level idea of what root gives you.
Recovery - gives you features such as Nand backup/restore, wipe cache, dalvik-cache, flash stuff (ROMs, kernels, etc.,)
Apps2SD - allows you to install apps to the SD card. If you are using android 2.2 or above, this feature is available natively, so you don't need something line apps2sd
Now, answers to your "Straight up questions..."
1. Yes, once you root, flash recovery, flash ROM... you have altered your phone from a software stand point. You can return it to "out-of-the-box" state by running any official RUU provided by HTC/Sprint (for HTC Sprint Hero)
2. This varies from ROM to ROM, you should read the specific instructions provided by the ROM builder. About removing gapps, it is pretty easy to remove any apps once you have root access - read up the wiki or search for removing apps
3. Depends on what you want to get back - for all your daily needs, there are backup applications that can help you backup stuff from the phone, which you can then restore, once you have the app running and backup available
4. If you restore a nand backup, it will put your phone to a stage when you had created the backup
5. You will have to read up about MoDaCo ROM, that is a ROM specific thing
6. There's nothing wrong about the gapps - not sure what you are referring to
7. There are multiple messaging apps - handcent, chomp, google voice, etc. It all depends on your personal preferences
I would honestly recommend you to search on the forums and also visit the wiki. There's a whole lot of information about everything here. Also, Hero being a bit old phone, more often than not, the problem you might be facing... might have been already answered. Yes, it is time consuming, but will surely help you. The more you read, the comfortable you will feel.
Hope this helps. Let me know if I can help you further. Again, I started the same way as you, rooted the phone, flashed CM6, played around, something went horribly wrong, then had to RUU, root, flash... everything. But, that taught me a lot.
Enjoy!
So basically, I’ve managed to do quite a lot of things and I want to help a friend out but I want to make sure all my info is right.
Customizing you Phone
The first step is to gain root access via installing (flashing) a recovery program (image).
This program (image) is only accessible via boot (boot into recovery). It allows you to make a back-up of the phone in its entirety, restore said back-ups, allow PC access connectivity (via USB), flash programs/files (“installing” in a sense), partition an SD card, perform various wipes, and some miscellaneous things.
Click to expand...
Click to collapse
Not sure which phone you are working with, but I'm pretty sure, as a general
rule, you need root before you can flash the recovery image. Could be mistaken
on that, but that's how it was for my hero. Once you have the recovery image
flashed, you are correct, you can make and restore backups, you can access
the phone's internal storage and SD card, push/install apps, remove apps, etc.
Ok – I’ll pause here to get some info. Wipe Data/Factory Reset; this means erasing everything off the phone and it resets the current ROM back to its native state. Wipe Dalvik-cache… I’m not sure what this does exactly but I assume it has something to do with the programs installed or the SD card. Furthur, why would I want to ‘wipe battery stats’ or ‘rotate settings’ ? And wipe SD:ext partition has to do with Apps to SD?
Click to expand...
Click to collapse
Wipe/Factory Reset basically formats the various partitions in the phone's
internal memory, if you do a wipe and reboot your phone, you'll boot loop, as
the phone no longer has an operating system. To restore back to original,
you would need to use an official RUU as andythegreenguy stated. You can
get the official rom upgrades (RUU's) from your carrier's website.
I'm still learning a lot of this myself, but the Dalvik-Cache is basically the OS's
cache, which has files randomly dumped into it and removed from it. Wiping
the Dalvik-Cache is beneficial (and sometimes required) when making
modifications to your rom. It can help improve your performance under some
circumstances, but will make your phone boot slower while the cache is being
recreated. SD:EXT only applies if you have partitioned your SD, for example,
to be used with Apps2SD. If you have no EXT partition, you can't format it.
If you are using Apps2SD, and have partitioned your SD card, this will erase
the EXT partition.
As a general rule that I follow, whenever I am making major changes, and
especially when I am flashing between different roms, I wipe everything, and
repartition/format my SD card. This helps me to know that any problems I run
into are not caused by something from a previous rom that didn't get erased.
I've never messed with wiping rotate, but wiping battery stats can be useful.
Lithium batteries have a little controller board that basically stores the battery
state. Sometimes this can get messed up, and a perfectly healthy battery will
think it's out of power a lot faster than it should. Resetting the battery info
can sometimes fix this issue. A recommendation I saw was to run your battery
down, reset the battery state, let the phone die, then do a full charge/discharge
cycle. Never had to do this, myself..
Also, when you do these wipes and flashes and re-do your phone from scratch, the only thing that is never touched is the recovery image. It’s fair to say, when you flash the recovery image during your rooting, it’s the only set in stone thing on your phone… that is until you re-root your phone or flash an alternate recovery.
Click to expand...
Click to collapse
Sorta.. hboot and the radio are both beyond the recovery, and messing with
either of those without knowing what you are doing can cause your phone to
become a brick. Any recovery you flash should remain in place unless you use a
RUU, flash a different recovery, flash a rom that includes a different recovery,
(haven't run across that except for the RUU's), or mess with the MTD partitions.
Apps2sd – When I first rooted my phone and installed MoDaCo’s ROM, I ventured into the land of Apps2sd. This too was a PAINFUL process partitioning my SD card and learning all about the ext2/3/4 and I’ve already forgotten everything. After going through all that to clear up what little space I had on my Hero, I then read all kinds of people saying Apps2SD is bad cuz it’s slow and blah blah. So I took it off. Now it seems that Google has made an Apps2sd native? I just need updated on the whole Apps2sd thing both in general and for the Hero.
Click to expand...
Click to collapse
Apps2SD is fine, any speed issues would primaryly be loading delays on slower
SD cards. Apps2SD also requires your SD card to be properly partitioned. The
Apps2SD that is in Android 2.2 is a little different, in that from my nderstanding,
it uses the Fat32 partition on the SD card, and thus does not require you to
partition your SD card. It is also to my knowledge only available on roms based
on Android 2.2.
A lot of custom roms have some form of Apps2SD now, but they require you to partition the SD card, and, as far as "speed" issues, I have ran my apps from
a class 2 card just fine, but moving the Dalvik-Cache to the SD card will cause
lag if you have a slow card. Class 4 or higher is recommended for moving your
cache.
Ok – Back. Some of the things you can flash are custom ROMs (a ROM is the Operating System essentially), data that tells the computer to work differently such as custom kernels (what makes the phone work, basically communication between hardware and software), new radios (what retrieves and uses signals), and battery stuff (what would it be called? “Battery kernel info”? haha). You can even flash programs right to the phone (apk files).
Click to expand...
Click to collapse
Correct, you can flash ROMS, Kernels, Radios, apps (if packaged properly),
apk files that aren't packaged in an update.zip will either have to be pushed
via ADB, or can be installed from your SD card with a file manager.
The biggest reason to root your phone, is to install a custom ROM. Custom roms typically cut out a lot of bloat that the stock OS would have such as un-removable programs (Sprint NFL and NASCAR… Thanks but no thanks Sprint) and OS things. Many developers have even tweaked ROMs to optimize performance and battery life. Why would the stock ROM not do this? And why would it seem the dev’s (developers) making custom ROMs are better than the devs at Google/Sprint/Samsung/etc.? Certain applications also require rooted phones (or just simple ‘root’) due to their extended abilities or required securities (such as WaveSecure?).
Click to expand...
Click to collapse
As far as the biggest reason to root your phone, I would have to say that the
answer to that would vary from person to person. Most users root to install
custom roms, but rooting gives you full control of the operating system. Since
android is Linux, having root access on your phone will allow you to change the
things that you otherwise could not. Utilities like Titanium backup can be used
to back up and restore your apps and data, performance benefits are always
a huge consideration. Companies like HTC and Sprint don't take performance
concerns into consideration because they are providing a product that is in their
opinion disposable, and "generic enough" for most users. Asking why they don't
fix the performance issues is like asking why every car on the road can't run 160
miles per hour while getting 40 miles per gallon. Some people don't care to have
the fastest, most efficient phone, and some people can't stand having sluggish
and unresponsive phones.
Now some straight up questions:
When you get a custom recovery, ROM, and kernel on your phone… you’ve just about altered all major parts of your phone (software speaking of course)?
Click to expand...
Click to collapse
With a recovery, rom, and kernel, you've flashed all of the major software components
that you will be concerned about. Performance gains are all found in the ROM
and Kernel, and so most people have no need to go further than that. Basically,
think of the Kernel as the brain, and the ROM as the rest of the operating system
The recovery is important, but is transparent to the function of the phone once
everything is up and running.
[*]When you want to put on a custom ROM, you first wipe everything then flash the ROM. Then you may flash additional items such as gapps (google applications pack), custom Kernals, etc. When you want to change roms, do you have to undo everything and start from scratch and put new gapps back on, a new kernel, etc? What about just updating a ROM? What if you have a ROM you like, but just want to un-install(un-flash) gapps – possible?
[*]So example, If I needed something I forgot on an old setup – like a text message or file from EasyNote, I would have to nandroid backup, wipe everything, flash old ROM and additional files, restore OLD nandroid, grab the files, wipe everything, flash back newer ROM and additional files, restore new nandroid that was just created to be back where I started? (I actually have to do this too haha – want to make sure that’s right.) Basically I’m making sure I’m right about nandroid. It back’s-up all data and setting type files for current ROM?[*]What would happen if I tried to restore a nandroid back-up created during another ROM?
Click to expand...
Click to collapse
I'll try to answer these in one shot. It's recommended that you always wipe
everything before installing a custom rom, except if the rom you are installing
is *SPECIFICALLY* an update for the rom you are running, and the dev states
that a wipe is not necessary. Generally, you want to make a nandroid backup,
wipe, install the rom, make sure everything is fine, nandroid, install the kernel,
check things over, rinse and repeat.
In my case, I generally return to configs that I've already tested, so I skip some
steps, but the order is ROM, Kernel, then the other parts.
If you forgot a text message from another rom, as long as you have the nandroid
you should be OK. You can boot into recovery, make a nandroid backup of your
current configuration, then wipe everything, restore the nandroid from the
old configuration, retrieve your message or data, Then you can reboot, wipe,
and restore the nandroid from the new configuration. Keeping multiple nandroids
can be userful if you are using an AOSP rom as your daily rom, since on the
Hero, to my knowledge, you can only update your PRL under a Sense based rom.
A lot of users will restore the sense backup to update their PRL, then restore the
AOSP rom.
[*]MoDaCo’s old custom ROM had WaveSecure installed with it so that it could not be removed. Is it possible to still do this with other ROMs?
Click to expand...
Click to collapse
Never used WaveSecure, but as a general rule, if you can download the APK, you
should be able to install it on any rom.
[*]Why do some people talk so negatively about gapps? Is there something wrong with them?
Click to expand...
Click to collapse
Some people like fat chicks, and some people don't. The argument about
gapps is akin to asking what's better, PC or Mac, Linux or Windows, sports cars
or station wagons. It's all personal preference. What's right for you might not
be right for your best friend.
[*]Back when I first tried learning all this a year ago, the Hero’s messaging app was known to be a real battery-eater and never slept so it was recommended to switch to a 3rd party and disable the stock app’s notifications. What’s the development on that?
Click to expand...
Click to collapse
The messaging app had a bug that would lock the dialer and prevent the phone
from sleeping. This bug was supposedly fixed in the 2.1 update, but 2.1 also
introduced a whole plethora of other bugs. Some people still prefer third party
messenging apps, but I use the stock app with no issues. on a good day I can
get 27 hours on a charge, but I do a lot and so most days I get 12 hours or so.
Hope this has helped.
LAST NOTE:
Ok I promise I’m almost done. I just wanted to say that if anyone would not mind talking on the phone… I would love to just blow through this stuff a lot faster and be able to have a convo with some 1 on 1 feedback allowing me to get lots of questions answered. Even just 10 minutes would help me out tons! So if anyone who is a genious on this stuff (like devs… ) and wouldn’t mind chatting for a few – please PM me. I can do Skype as well.
Click to expand...
Click to collapse
This may sound strange from a guy with a cellphone, but I actually hate talking
on the phone. Feel free to send me a PM now and then with questions. If I know the answer, I'll help out.
I'm not as knowledgeable as any of the devs, I'm still learning all of this myself. My answers might not be
'correct', but they work for me. most things related to android have no 'correct' or 'definitive' answer, but
that's the beauty of a platform that can be customized to taste. We can all make recommendations, and
can even tell you our reasoning or logic behind them, but we can all also learn a few things.
andythegreenguy said:
Root and recovery are two totally separate things - you can root your phone and not flash a recovery, it's totally up to you. Root gives you access to things on your phone, that you would otherwise not have - like flashing recovery, ROM(s), apps that need root access, etc. Goto the wiki there's a link which gives a high level idea of what root gives you.
Recovery - gives you features such as Nand backup/restore, wipe cache, dalvik-cache, flash stuff (ROMs, kernels, etc.,)
Click to expand...
Click to collapse
Ah! So the recovery is a nice, built-into-phone way of flashing, whiping, etc; otherwise you would need to use the command prompt. (Correct?)
andythegreenguy said:
Apps2SD - allows you to install apps to the SD card. If you are using android 2.2 or above, this feature is available natively, so you don't need something line apps2sd
Click to expand...
Click to collapse
Excellent. But does running apps from the SD card cause the apps to run slower or open slower? Should I keep primary apps or most commonly used apps on the phone or it doesn't matter?
andythegreenguy said:
If you restore a nand backup, it will put your phone to a stage when you had created the backup
Click to expand...
Click to collapse
So the Nand-Backup saves ALL information including flashed ROMs, Kernels, BatteryTweak, etc? What about information on the SD card especially not that apps can be moved there)?
andythegreenguy said:
There are multiple messaging apps - handcent, chomp, google voice, etc. It all depends on your personal preferences
Click to expand...
Click to collapse
I understand this, but I just wanted to know If it's a mistake to be using the stock texting app - if the messaging app in CM6 is even the stock one. I have tried Chomp and Handcent and I actually love handcent, but it's just WAY to slow.
I have searched the forums and wiki quite a lot, thats how I got this far. I try to search for some as many things as I can, but it's just hard to get some real clarity on some things and especially the broad things. That's why I plan on taking the results of this thread and making a nice 'general' guide and possibly a video.
Thanks a lot andythegreenguy. Appriciate the help a lot
To moxlon69:
moxlon69 said:
you need root before you can flash the recovery image
Click to expand...
Click to collapse
Yes you are right. I was a bit mixed up on that (even though I've done it twice! haha)
moxlon69 said:
Wipe/Factory Reset...
Click to expand...
Click to collapse
Lot of good clarification there. Very good, thanks!
moxlon69 said:
Sorta.. hboot and the radio are both beyond the recovery...
Click to expand...
Click to collapse
Ah. What is hboot? Had some trouble finding general info on it. What is there to know about the radio? I haven't done it nor think i need to, but isn't changing the radio just the same as flashing something? (http://geekfor.me/faq/flash-radio/)
moxlon69 said:
Apps2SD is fine, any speed issues would primaryly be loading delays on slower SD cards. Apps2SD also requires your SD card to be properly partitioned. The Apps2SD that is in Android 2.2 is a little different, in that from my understanding, it uses the Fat32 partition on the SD card, and thus does not require you to partition your SD card. It is also to my knowledge only available on roms based on Android 2.2.
A lot of custom roms have some form of Apps2SD now, but they require you to partition the SD card, and, as far as "speed" issues, I have ran my apps from a class 2 card just fine, but moving the Dalvik-Cache to the SD card will cause lag if you have a slow card. Class 4 or higher is recommended for moving your cache.
Click to expand...
Click to collapse
So if I have a 2.2 ROM... would I need to make a partition? I never read anything about needing it in CM6 threads. What was all the jazz about making different ext-s? Like 2, 3, or 4? I guess it's not relevant any more.
How do you move the Dalvik-Cache to SD?
Quick note:
AOSP and PRL are not on the wiki - not that many people don't know what they are... but why not?
Q: Why do some people talk so negatively about gapps?
A:Some people like fat chicks
Click to expand...
Click to collapse
Well said haha. The whole analogy was good.
Thanks a million moxlon69 - That helps out more than you can imagine. I'm going to begin working on a write up of all this, but I do still have lots of questions. I'll probably continue posting in this thread for a while to keep it simple... unless I have an embarrassingly stupid question I can't find an answer for then I'll PM ya!
Thanks again moxlon69 and andythegreenguy.
Edit: This thread is going to become the tl;dr thread! haha
One more try.
I know it's a lot of reading, but any help you guys can offer is much appreciated and will be returned in the form of a video. You could then just send all the newbies to the video and hopefully many of their questions will be answered.
I just don't want to make the video without being precisely accurate. I have more questions, but I should probably wait for the current queue of my questions to go down.
Thanks again for the help thus far!
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Magicnet2 said:
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Click to expand...
Click to collapse
First thing I would do is just factory reset it through recovery (power on while holding home) and see if all works after this. Super d is for sure one of my favorite donut ROMs and it shouldn't be having the issues you have.
If that does little or nothing than write down all info from bootloader (power on while holding camera) here and the version of recovery you have (written in recovery screen)
Sent from my Nexus 7 using Tapatalk 2
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Magicnet2 said:
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Click to expand...
Click to collapse
Yes it is strange, try finding a ROM called donut by Laszlo, search is down right now but it should be within the first five pages or so in developers thread. Put on sdcard along with this
http://www.androidfilehost.com/?fid=23212708291678371
First flash super wipe in recovery and then flash new ROM
If it all does not work still we will go from there
Sent from my Nexus 7 using Tapatalk 2
Right, so I've got some new info on this. I wanted to go reflash, but just for the sake of it, I re-wiped though recovery and nothing changed. then on the second time, the market suddeny started working through wifi, which it has not for the past few months, even after 3 or 4 wipes. So it started working, but the signal kept failing. It found the first application, downloaded, installed, then "network problem" so I reflashed using the files you mentioned. It worked beautifully on the first fly, for which I am grateful. This was my main concern - I had no idea, whether I needed to change the radio or bootloader or anything prior to trying to flash the rom. So the rom works nice, the market and facebook and teamviewer do connect now using wifi, but I keep loosing the signal. Better said - he stays connected to wifi, just that the applications keep throwing network errors and loose connection. So I presume, it will be either hardware related, or I was wondering, if a change of radio might help... Secondly, I keep getting one more problem I had with the old Rom and that is - when using ES File explorer, when I close by pushing the back button, it closes and then an error says it stopped working and needs force closing. Wondering how this kind of error can transfer between different Roms. Again - posibly hardware related? I don't know.
Anyway, the rom works nice, so I'll try it out and see if it's better than the previous one. One question though - when flashing to a different Rom, do all of them have specific requirements for radio and bootloader and recovery and so on, or is the setup I have ok for flashing anything, that is suited for the G1?
EDIT: One more thing I just remembered. The Superwipe, as I read the description, was supposed to wipe everything + the SD card as well. First of all I noticed that it took just about a second or two, which I thought was a bit too quick, but the SD card was not wiped at all, so I'm thinking, that theoretically there could be a file on there, that causes the problems, that have transfered from Rom to Rom, as it was not wiped at all. I'll reformat the SD card, superwipe it, reflash the Rom and see what will happen. Will post the results first thing tomorrow.
It only wipes ext partition not fat32
Only newer ROMs will require a different bootloader/radio, which also will give you more ram so it is preferred. See ezterrys post on the 2708+ update or read the through the thread below this on where I discussed the benefits of upgrading with another dream user
Sent from my Nexus 4 using XDA Premium 4 mobile app
Right, so from what I see from the other thread of yours, CM5 should be a good Rom to try. I will definitely wanna go there, cause while the current Rom seems a bit better than the Super D, it seems it uses up more memory - can't install as many apps as before and I'm keeping it pretty low on apps. And I definitely want to see, whether it will improve any of the lingering problems I've been having, or whether it'll be worse. So judging by what you told the other guy, I already have the right bootloader as I have the 2005 with fastboot enabled, but I'll have to update the radio. Here's what I'm not sure and that is, which to choose. Should I stay with the current SPL and get the same radio the other guy had (RADIO-2.22.19.26i) or should I go straight for the 13d SPL with radio-2.22.27.08? I would say, for now would be safer to stay with current SPL, update the radio and then flash Rom + Gapps and see what it does. Plus if I remember right, you said that to get the ramhack I need the 13d spl, which doesn't support fastboot...
You got it all, well you don't need to change radios, the one he has is a Europe version, yours is more us. Both work fine for cupcake, donut and eclair ROMs. You can try out the other if you were getting poor reception but not needed
Cm5 will work fine for you as of now, just full make a backup, wipe, superwipe, fastboot -w whatever, then flash ROM, then gapps then reboot
The ram hack is awesome but so is learning fastboot. I do recommend you at some point upgrade to the .13d SPL but I think its a good idea to flash a few things first and be comfortable before doing so. If you have issues having fastboot is helpful in fixing things
Sent from my Nexus 4 using XDA Premium 4 mobile app
Ok. So what I did is partition the SD card using the nice "Mini tool partition wizard" and went for a 250 MB ext4, made a backup, left the radio be so far, wiped, flashed the CM5 and Gapps and I have to say I'm impressed at how swift the Rom works. It appears to be generally faster than both the SuperD and Laszlo Donut Roms. I have been testing it only a short while yet, but the wifi, although it shows constantly weak signal (one or two lines), it hadn't lost connection yet, which gives me hope and the apps2ext seems to work perfectly right away. At least I'm able to move them around and it installs straight there, without any failure so far and the apps work so thumbs up.
This deserves a big thanks to you for the supplied info. Before I wrote this thread, I was about to try one of the long guides - which would take me through downgrading and everything - you saved me a lot of stress man I'll play around with this and will try going for the ram hack a bit later. I'll let you know any bugs I notice...
P.S.: You were right to suggest getting familiar with fastboot and adb - it's a great thing and it's good to know I've got it set up and running fine.