Develop Bugs

Desire root and only instapp App2SD keep original firmware?

Hi guys i need more space for apps, Can root be reversed i.e reset the whole phone like it was oringinally?
I got my phone last tuesday and all i want it apps2sd, do i have change the HTC firmware or does that stay and it hacks it and allows me to added apps2sd option?
Also am i able to restore it back to original ? if i brick it while trying to do this is there way to unbrick?
thank you from an andriod newbie

I've just flashed the apps2sd update over on the original firmware after rooting and the phones constantly rebooting at the quietly brilliant screen

technocat said:
I've just flashed the apps2sd update over on the original firmware after rooting and the phones constantly rebooting at the quietly brilliant screen
Click to expand...
Click to collapse
really, are you able to revert to original state?

managed to install custom rom with apps2sd on it and its working after 3rd attempt thank god! Apps2sd aint working on the rom either though (Pays-ROM Desire with Sense v1.4)...dont know whats going on.....wonder if its cause its an ext4 extension?.....

My advice to anyone is to NOT install APPS2SD, just wait for an official FroYo build to be leaked and installed on the Desire. It's full of issues at the moment.

Agreed. Wait for your sweeties

managed to install custom rom with apps2sd on it and its working after 3rd attempt thank god! Apps2sd aint working on the rom either though (Pays-ROM Desire with Sense v1.4)...dont know whats going on.....wonder if its cause its an ext4 extension?.....
Click to expand...
Click to collapse
Ext4 is not supported

My advice to anyone is to NOT install APPS2SD, just wait for an official FroYo build to be leaked and installed on the Desire. It's full of issues at the moment.
Click to expand...
Click to collapse
A2sd works fine, but it has a lot of downfalls. here are some examples:
not easy for beginners
Sd cards have to be in the device to boot
Cannot access apps with sd card mounted
Access to apps can be laggy due to card transfer rates
Etc....
If you guys are new to android, you're probably in the "download everything" phase. It's not realistic to keep every single thing. Be reasonable and you should be fine.
A2sd will be a thing of the past once 1gb+ roms become the norm.

eViL D: said:
A2sd works fine, but it has a lot of downfalls. here are some examples:
not easy for beginners
Sd cards have to be in the device to boot
Cannot access apps with sd card mounted
Access to apps can be laggy due to card transfer rates
Etc....
If you guys are new to android, you're probably in the "download everything" phase. It's not realistic to keep every single thing. Be reasonable and you should be fine.
A2sd will be a thing of the past once 1gb+ roms become the norm.
Click to expand...
Click to collapse
Or when FroYo is released
I still don't know how they'll manage to get APPS running from a FAT partitioned SDCARD?
How will they manage to make the Sdcard usable for apps and readable by Windows and other operating systems which don't support ext2/3?

abc27 said:
How will they manage to make the Sdcard usable for apps and readable by Windows and other operating systems which don't support ext2/3?
Click to expand...
Click to collapse
Correct me if Im wrong, but the only reason you have to use ext filesystems for A2SD is because that is what the 2.1 expects??
I can't see why you would need an ext filesystem for the APK files. The 'special' permissions on apps are not provided by the filesystem. Maybe cache and app data would require some level of security, but at least the APKs should happily live on FAT32.
Fingers crossed! I hope they sort something out.

Excellent advice, eViL D: I was a bit nervous about trying and Android phone in the first place but took the plunge due to the fantastic reviews on the Desire. I absolutely love this phone and I managed to root it without any problems. Fortunately I read about the A2SD issues before I installed it. Whew!!!
Being a complete newbie to Android, I am in the 'keep everything' phase but am starting to realise that there are a lot of apps that I simply don't need and probably won't use very often anyway. I reckon that if I find that I need them later, then I'll install them then. I've gotten rid of a number of apps and am really happy with the phone as it is. For now, I'm going to leave well enough alone. Will definitely keep an eye on the A2SD issue more out of curiosity than the need to use it.
I really wish I had the knowledge to help solve this problem and wish everyone who is working on it the best of luck.

[Q] multiple roms?

I'm wondering if its possible to partition my sd card so that half of it can remain baked snack with everything I have set up then the other half to cm6 final then just flash the roms and kernels from the applicable side when I want to run it. So essentially I have 2 to choose from each with their own backups ext...
Possible?

Kinda like a dual boot box... Is there an app for that?

I don't really want an app for it. I think that would end up slowing the system down substantially. I just want to be to choose a partition flash the rom from that partition then do a nand restore for that rom(located on same partition) and have that side of my sd card already set for that particular rom.

cool idea. for now I just nand restore when I want to switch back and forth but it takes a bit of time. If it was as quick as rebooting to another partition that would be hot.

That's very possible. We dualboot our pc from Windows to Linux so should not be impossible. Someone just needs to make it work.
Sent from my PC36100 using XDA App

Maybe I'll suggest it in the Dev section someone in there will have the know how to get this done.

well the rom doesnt install to the sdcard. hence the reason you can format the sdcard and still have a working phone. it installs to the phones internal memory.
your best bet is to do what is stated above. do a nandriod of the roms you want, setup how you want and a titanium backup of each to restore your settings.

So I can't just partition it and have 2 different "sides" for each roms information like I can't tell Baked Snack to look at "A:" and CM6 to look at "B:"? are we sure about this? Maybe even partition the memory inside the phone to 2 different roms then choose 1 from boot loader? Think I'm going to try to post something in dev section and hope they won't get too angry at me.

You know, i think the main reason this hasn't been discussed before is that previous phones didn't have the nand capacity to hold multiple roms that you would switch between. Even at 512mb it is pushing it depending on how many apps you are going to have installed on the phone on each rom that aren't going to be insstalled to sd.

Well I have 270 free on the phone and I still haven't moved every app I can over to the SD cdard. I think Cyanogen is smaller then most other roms the Zip is only 70 mb compared to baked snack wich is 170, well over double. I think it would be pretty easy to have enough space. This may hinder performace if internal memory is completely maxed out though, not quite sure.

wy1d said:
cool idea. for now I just nand restore when I want to switch back and forth but it takes a bit of time. If it was as quick as rebooting to another partition that would be hot.
Click to expand...
Click to collapse
Yeah thats what I doo I have Fresh 3.1.0.2 and CM6 and I just restore depending on my mood.

MODS PLEASE CLOSE THREAD --- new kernel by scooter fixed YAFFS error

Mods please close these thread

clemsyn said:
OK, this is from l1q1d latest 2.6.32 (10-29) and merged with dream kernel by ezterry. I used HTC Android kitchen by dsixda and with help from scooter, got me an nbh from a zimage file.
I installed my ROM with this kernel and then installed iGO, ran some GPS and wifi, restarted about 30 times (clean shutdown) and yaffs stayed intact. Reset the device 5 times after each reboot..First, second, third reset was good...Fourth reset gave me a Google Framework error..Fifth reset gave me yaffs error....Anyone interested can try it and let me know how it works in your Kaiser. BTW, edit the Kaisimg.nbh depending on your device.
I recommend acayoeme or scooters ROM.
Click to expand...
Click to collapse
Thanks for the recommendation, I will give the kernel a try with my build to personally test it and see if I can figure out a way to keep it stable enough.

aceoyame said:
Thanks for the recommendation, I will give the kernel a try with my build to personally test it and see if I can figure out a way to keep it stable enough.
Click to expand...
Click to collapse
Ur welcome, thanks for trying out my kernel My friend is currently testing out this kernel with my ROM but since your ROMs are optimized for 2.6.32, I think it's best that this kernel be tested with your roms

Yeah I just downloaded it and just copied it to the phone, will let you know how it goes.

NAND did not work with the nbh for me. SD worked though, going to test further. With NAND it just hung at the android part of the nbh and in the install menu it did not detect the NAND in it. I have a TILT with display type 2 if that narrows down perhaps a difference in the NAND that there could be.

aceoyame said:
NAND did not work with the nbh for me. SD worked though, going to test further. With NAND it just hung at the android part of the nbh and in the install menu it did not detect the NAND in it. I have a TILT with display type 2 if that narrows down perhaps a difference in the NAND that there could be.
Click to expand...
Click to collapse
I'm pretty sure he had a type 2 Tilt too. I'll ask him.
Yes, he does have a Tilt type 2

Hmm thats odd, also I noticed it seems like I can't overclock to 570 mhz with the kernel so far, seems like its a little less tolerable to cpu instabilities. Other than that though all features seem to be working and 6+ reboots later with both on SD I haven't seen any corruption yet.

aceoyame said:
Hmm thats odd, also I noticed it seems like I can't overclock to 570 mhz with the kernel so far, seems like its a little less tolerable to cpu instabilities. Other than that though all features seem to be working and 6+ reboots later with both on SD I haven't seen any corruption yet.
Click to expand...
Click to collapse
It was pretty snappy at 400 mhz...so we never did overclock and kept it at default speed. Just wondering why it won't install nand for you while we did not have any issues in his tilt.

Has anyone on a vogue or kaiser or anything else tried this yet?

I just tried NAND again and the error is a umount error, it seems like it tries to format with the wrong parameters, it gives an invalid argument error.
err seems like it is trying to unmount properly so it cant format it.

Looked a little closer at the error and it is actually saying it cannot find a flash device and that is why the sub sequent umounts are failing.

OK, got a hold of my friends Tilt...I am currently installing your Build..I'll post the dmesg and boot messages...somehow it installs with no issues on this Tilt both system and data on NAND. Currently on bootanimation.
OK booted fine...here are the files
BTW, very nice build Very fast..cant find the reason to overclock with this combo in NAND

I can't possibly think of why it isn't finding the NAND on mine. I am going to try reloading winmo and then re-loading the nbh fresh tomorrow. Thank you for the compliments, I overclock mine so high just because I have a hunger for speed, trying to make it as fast as I can, to compete with the dream and be faster even if possible.

Works fine with NAND. No problem detected yet.

Clean installation on NAND/NAND seems to install and boot just fine on a tilt screen 2

Grandelama said:
Clean installation on NAND/NAND seems to install and boot just fine on a tilt screen 2
Click to expand...
Click to collapse
Thanks for trying it...LMK how it goes for you eg. stability, adb, SD removal and insertion while running etc..

I will just install it and see how it goes. Looks good

Installed, and so far so good using scooters cyanomod. Did a boot-reboot-boot-reboot-boot-reboot stress test, and so far no yaffs errors, and no data corruption. This is using a tilt with panel 3. I'll run it for a few days and keep you posted.

matcha20 said:
Installed, and so far so good using scooters cyanomod. Did a boot-reboot-boot-reboot-boot-reboot stress test, and so far no yaffs errors, and no data corruption. This is using a tilt with panel 3. I'll run it for a few days and keep you posted.
Click to expand...
Click to collapse
I appreciate you guys trying it...I suggest you no overclocking since it is very sensitive to overclocks

I have tried this kernel today with "Scoot CyanogenMod RLS4" and "Galaxy S for AndroidonHTC 11/1" which is based on Fresh Froyo. After the setup with both builds I installed a few apps and then I made an normal reboot (switch off, switch on again). Then I got the same error with both builds:
init: untracked pid xxx
And then the phone is in a loop and does not boot. Seems, that there are yaffs errors with this kernel after the reboot?
So I think this error belongs to the kernel and not the build because these are both different builds. My installation was system and data on nand and not overclocked. Maybe someone can help?

[DEVQ] Custom MTD Partitions - Possible on the HeroGSM?

I have been reading this thread with great interest, and then became even more excited when I found out that it was succesfully working on the HeroC. I think I understand most of it, but I am not a dev and I really wanted to check with a seasoned dev wether or not it OK to go ahead and give it a go, or if it obvious that I will totally screw up my phone and I am being and idiot.
I would also be curious to know recommended sizes for the partitions, I am not sure what would be acceptable for system ( I appreciate it depends on the size of the ROM), I can't seem to find the total size for system+cache+data the Hero has.

l0st.prophet said:
I have been reading this thread with great interest, and then became even more excited when I found out that it was succesfully working on the HeroC. I think I understand most of it, but I am not a dev and I really wanted to check with a seasoned dev wether or not it OK to go ahead and give it a go, or if it obvious that I will totally screw up my phone and I am being and idiot.
I would also be curious to know recommended sizes for the partitions, I am not sure what would be acceptable for system ( I appreciate it depends on the size of the ROM), I can't seem to find the total size for system+cache+data the Hero has.
Click to expand...
Click to collapse
I am pretty sure Maxisma got this to work at some point, but I think he then pulled it off and stopped recommending it. Hold on, I'm off to search
EDIT: http://forum.xda-developers.com/showthread.php?t=755204 is his thread

Thanks, for the link, looks like it works, just the limitation of having to patch the recovery every time you want to flash a new ROM...
I'll have a play, see if I can do it without destroying my Hero
EDIT: Am I misunderstanding something, or does the dev need to change the boot.img for this to work?

l0st.prophet said:
Thanks, for the link, looks like it works, just the limitation of having to patch the recovery every time you want to flash a new ROM...
I'll have a play, see if I can do it without destroying my Hero
EDIT: Am I misunderstanding something, or does the dev need to change the boot.img for this to work?
Click to expand...
Click to collapse
you need matching boot.img AND recovery iirc...

Interesting, just been reading up on the htc desire rooting/flashing process for a friend, it has a very similar process for switching partitions. I think they've actually gone the whole hog and got a recovery which can switch between 4 different layouts.
It seems to me that with a2sd+ working pretty much seamlessly and thus being in common use these days (for anyone using a custom rom) that having extra internal data space is almost redundant.
Is there likely to be a need to expand the system partition from its default? Just wondering if any of the later sense and/or ICS roms are getting fat enough to need extra space...
edit: doh! replied in the wrong thread, sorry for the inadvertent resurrection!

[Q] Transferring EVO 4g to grandaughter

Hi all,
I've had my EVO 4g for nearly 2 years now and recently stepped up to the 3D.
Over the last summer I had a terrible problem with my EVO rebooting using two different MicroSD 8 GB cards taking it into the Sprint store they said both cards are defective. So I bought a 4GB card and it worked nearly flawlessly since then (maybe a reboot once a month)
I had not rooted my phone until last fall when I bought a WIFI only iPad and needed to get the wireless tether option enabled...
Not knowing much about rooting or flashing ROMS and any of that stuff, I followed a sticky guide to rooting and went with the Warm 2.2 ROM from last fall.
When I got my EVO 3D I decided to sell my EVO 4G to my 20 year old granddaughter, I did a Wipe and installed CleanROM 2.0 which had rave reviews and I thought it would be as close to stock as possible.
I hadn't gotten around to wiping the SD card is it is 3/4 filled with my junk on it still.
2 days into her having the phone it is rebooting a dozen times a day for her.
Not good. I'm not sure if it's the new ROM or a corrupted spot on the SD card now?
If I just reflash the CleanROM 2.0 and then have the phone format the SD card might that clear it up?
No point doing a nandroid backup since that would have all my apps that wouldn't work for her, correct?
She really doesn't care about it being rooted, so what would be the easiest way to get it work for her in a stable way?
I apologize in advance if the solution seems easy to people hear, it seems complicated to me.
Thanks Crodley

Personally I would do a complete wipe and do a fresh partition on the SD card to remove anything you had on there. After that I would suggest installing MikG 3.11 as it is probably the most stable of the Sense ROMS.
I try other ROMs but keep going back to MikG as it performs flawlessly for me with no restarts or crashes of any kind.

ItsLasher said:
Personally I would do a complete wipe and do a fresh partition on the SD card to remove anything you had on there. After that I would suggest installing MikG 3.11 as it is probably the most stable of the Sense ROMS.
I try other ROMs but keep going back to MikG as it performs flawlessly for me with no restarts or crashes of any kind.
Click to expand...
Click to collapse
Sounds like a good plan. Partition the SD card? Not sure how to do that part. I can do a google I guess.
Thanks

Crodley said:
Sounds like a good plan. Partition the SD card? Not sure how to do that part. I can do a google I guess.
Thanks
Click to expand...
Click to collapse
The option is in the recovery but there are some easy to follow guides around the site.
Here are the basic settings and it's pretty straight forward in the recovery.
- Swap partition = 0mb ( If you must have it but doubtful, 32mb should be enough.)
- Ext partition = 512mb to 1gb (MAX 2Gb if you have loads of APPs)
- Upgrade ext2 to an ext3 partition (but not 4).
Click to expand...
Click to collapse
GUIDE <<< It's quick and easy.

ItsLasher said:
The option is in the recovery but there are some easy to follow guides around the site.
Here are the basic settings and it's pretty straight forward in the recovery.
GUIDE <<< It's quick and easy.
Click to expand...
Click to collapse
Thanks yet again, I just woke up and am off to work, I'll give it a try went I get home and let you know how it went.
Crodley

You shouldn't need to partition the card if you are going to have mikg on there.
It sounds like your granddaughter doesn't need anything that would require any extra steps on her part.
Just reformat the card so that its a fresh start. Put any ROM on there (mikg is pretty much maintenance free). And boot it up and test it out before you give it to her...
A partition would be necessary only if you or your granddaughter have a huge amount of apps. Something tells me that she's not a power user...
~ I'm a fungi

Your other option is that if she isn't going to use any root functions, just unroot it for her. You don't have to bother with s-on or relocking the bootloader, just run an RUU to get it back to stock. This should eliminate any problems, unless the rebooting issue is a hardware problem. You also don't have to worry about her messing anything up with root, since she won't have that ability.
Of course if she uses any of the root functions - wireless tether, overclocking/undervolting, removing bloatware, etc, then this isn't the way to go. You could just flash a rooted stock rom as well.
In my opinion, if someone doesn't know what to do with root, or if they don't use it, they shouldn't have it. It'll just complicate things.

Thanks for all the information, I wiped the SD card and installed the Miks rom so far all smooth as silk.

Crodley said:
Thanks for all the information, I wiped the SD card and installed the Miks rom so far all smooth as silk.
Click to expand...
Click to collapse
Nope still rebooting about a dozen times a day, we're going to swap the 4gb sd card with an old 8gb card and see if that helps...

Well, it seems the 4GB card was the culprit. After swapping in another card, no reboots. Yay!