yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Drizin:
I was going nuts with the bootloops. After lots of image backups/restores, I finally found that PlayStore was causing the boot loop, and then found here everyone else having the same problem. According to previous solutions, I could kill and delete the broken PlayStore, but had some problems to install the new PlayStore because of the packages.xml having previous signature.

This is what I came as my complete solution:

During the boot loop, I just send these commands from adb:

• adb remount

• adb shell rm -r /data/data/com.android.vending

• adb shell rm -r /data/data/com.android.vending.updater

• adb shell rm -r /sd-ext/app/Vending*.apk

• adb shell rm -r /sd-ext/app/MarketUpdater*.apk

• adb shell rm -r /system/app/com.android.vending*.apk

• adb shell rm -r /sd-ext/app/com.android.vending*.apk

• adb pull /data/system/packages.xml

In a few moments the bootloop will stop and boot will go on.

While boot goes on you can open the downloaded packages.xml in a text editor:

• Search for: name="com.android.vending"

• You'll find a "package" block, and an "updated-package" block.

• Remove both blocks (from the start up to the closing tag)

Now go on with putting back the packages.xml, putting new Play Store apk, clearing cache and rebooting:

• adb push packages.xml /data/system/packages.xml

• adb shell chmod 664 /data/system/packages.xml

• adb shell rm -r /system/app/Vending*.apk

• adb shell rm -r /system/app/MarketUpdater*.apk

• adb uninstall com.android.vending.updater (dont know if necessary)

• adb push "D:\path-to\Vending-3.8.15.noupdate.norestrictions.dpi240.apk" /system/app/Vending.apk

• adb shell chmod 644 /system/app/Vending.apk

• adb shell rm /data/dalvik-cache/*com.android.vending*

• adb shell rm /data/dalvik-cache/*MarketUpdater.apk*

• adb shell rm /data/dalvik-cache/*Vending.apk*

• Some people tell you to clear dalvik-cache... Dont think it's necessary... that would be adb shell rm /data/dalvik-cache/*

• adb reboot

Hope it works for everyone as it worked for me. :)

PS: Please note that as other have said, apks may be installed in different locations ...
[Desire Android Development] Sandvold:
I don't have any time today, but I'll see if I'll be able to release a quick fix with the most important issues (probably not before Friday). To bad a small error like that ruins the experience.
[Desire Android Development] Hammerbak:
Did you remember to run the following commands in the terminal emulater after the reflash?

su
a2sd install
[Desire Android Development] nate51:
I did this only when I used the stock a2sd in the custom install, do I have to do that for all of the a2sd versions?
[Desire Android Development] mascolel:
In my opinion, I think its better to wait for Android 4.2 (“Key Lime Pie”), since it is supposed to be released on 29/10/2012 (in 5 days).
[Desire Android Development] rickiri69:
In my case mount USB storage do not work in Recovery (I don't know why :confused:). That's why I was talking about taking out the micro SD ;)

I simply replace the original vending apk from Sandvolv Beta zip with a no restriction one and re-zip the beta zip. Then simply put it into my sd and make a fresh install from recovery (wiping everything except sd before)

Simly worked for me. :good::good::good:

If somebody wants it I can try to put it on download
[Desire Android Development] mattmanwrx:
I might have made a wrapper script (for windows) that would adb remove the offending vending and install the non updating one... haven't tested it though so cannot release it confidently... will test over the weekend if I have time... :)
[Desire Android Development] nate51:
Sorry if this is a dumb question. I am coming from a different ROM, I am getting "Insufficient space" errors when I download from the Play Store. I am not sure if I need to go into terminal and use su a2sd install for all the a2sd options in custom install? I only did it when I installed the stock a2sd as it requested it in the install settings.

I want to continue with this ROM because of the great support here and the continued support from the developer.

I am coming from BCM/Spaze Dogs so my space is set up as follows...

- 8GB class 2 micro SD card (I know small and slow, but it does the job)

- 4EXT Recovery

- Stock HBOOT

- SD card fat32 6.6MB, sd-ext ext4 256MB, swap 256MB

Now I have no idea what setting to use for my sd-ext etc as I set this up long ago and it never gave me any trouble.

Any help on getting rid of that error would be great, this ROM seems awesome.
[Desire Android Development] komani86:
As far as I've read the swap should be 64MB and sd-ext 2-4GB (up to you) with a 8GB card to run apps. I have 1GB, thats plenty for me. But 256/256 is just wrong.

I miss my desire Z, i got this phone after I dropped my Z 1 to many times. Such a hassle to find a rom that doesnt get stuck in bootloader. Even more hassle to fix it. Still not fixed and followed the posts around page 1666... sigh i'm reflashing and not entering google account for now.
[Desire Android Development] nate51:
Thanks for the info komani86, but do I need to run terminal with the su install a2sd?

Also if you are having the Play store problem with the bootloop stuck on Evervolv screen, let me know, I got stuck on the description a couple of times but figured it out eventually. Without adb or any complicated methods.
[Desire Android Development] ciccillover:
Had the same Evervolv screen bootloop, solved following Drizin's instructions. But my paths were almost all different from the ones pointed in his post above. Using INT2EXT+ here. Might this be the cause?
[Desire Android Development] bliblablub:
It would be so nice if someone could upload a recovery-fix so that we can fix the issue directly after flashing the rom without stucking in any bootloops and without being necessary to run any adb commands :)
[Desire Android Development] mattmanwrx:
What was the location of your offending vending.apk, please?

---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------

Problem is that all the different variants of a2sd and int2sd the vending.apk will be in so many different places it would be hard to make..
[Desire Android Development] komani86:
All Vendor apk's here.

This is the specific version (3.8.15)

@nate51: Yes I think so. I did it via my computer using MS-DOS and "Adb shell" but its the same if you open terminal and type. Odd thing is that I dont have space neither to install apps, but I reserved 2GB before installing any..

I finally managed to get out of bootloop via EZ explorer as described in your post.

Might have to add to that explanation that "Framework Android" can be called "Google Framework Services" and that you can get there via "AppMgr>Catagory>Select All" to see all the applications running.

Now google play store doesnt work I get "server error" and tried to replace the Vending.apk with all the 3.8.15 possible options! Anyone had this problem and fixed it?
[Desire Android Development] nate51:
@komani86: But if you ran su install a2sd and you're still getting the error with more than enough free space, then it sounds like the terminal or adb command didn't fix anything.

Does anyone have this ROM working on their phone without the space error coming up? And if so what setting are you running on your sd card and what option did you select for the a2sd option in the install?
[Desire Android Development] Coempi:
16GB class 6 card with 1GB ext4 partition, activated a2sd in terminal, no problem with space, only with Play Store boot loop. Couldn't solve it with the method described in previous post, had to restore nandroid, and no restarts until now. Anyway no issues with free space.

Best regards Coempi
[Desire Android Development] nate51:
Thanks for the info Coempi, Have you tried rickiri69 method? I am not good with adb and this worked perfect for me.

This worked for me, I added a touch more detail to his explanation to make it really easy.
[Desire Android Development] Drizin:
I'm glad it worked. :cowboy:

My paths were based on a2sd.

Maybe someone can come up with some kind of piped-commands to find/grep where Vending is installed and remove them wherever they are. My linux skills are not what they used to be :)

As far as I remember the bootloop happens even without a2sd/int2ext/etc.
[Desire Android Development] Coempi:
I followed a similar description without success. I will try it again later.

Best regards Coempi
[Desire Android Development] Arbelac:
As I posted before, doing a ' find -iname "*vend*" ' will show you all the files. The different A2SD implementations all change the paths to different spots.

You need to dump com.android.vending, com.android.vending.updater, Vending.apk, and any vending-#.apk files.
[Desire Android Development] freakymonkey:
I'm trying this ROM from a week.

It's a fantastic work, so I'm glade with Sandvold! :good:

I found the system a little bit laggy and unresponsiveness for a while (maybe when I use a specific service). This lags shows up installing apps, opening whatsapp, opening chrome etc... Sometimes the phone shows up a pop-up with a message for killing the app because it don't responds, or sometimes the same message is for the "system" that don't responds.

I hope that Sandvold, with his beautiful work can resolves this issues and cooks the definitive ICS ROM for our Desire! :fingers-crossed:
[Desire Android Development] nono_vienna:
Tried this way, but always failed to copy the apk to /system/app. I also tried to copy it with adb, but the same - "out of memory"

After every reboot the playstore updates to 3.9.16 :(

Any idea what goes wrong?
[Desire Android Development] nate51:
Are you using stock HBOOT? I only got the "out of memory" error because of my a2sd set up. You should not be getting that error to move a file from one location to another.
[Desire Android Development] nono_vienna:
yes, using the stock, but found the real problem: i don't have s-off :D

mounted /system in recovery and it worked fine for me.
[Desire Android Development] nate51:
This is killing me. I am on stock HBOOT, My SD is now set up as follows...

These are the details from 4EXT

mount point - fs - size - free

sdcard - fat32 - 3.3GiB - 3.1GiB

sd-ext - ext4 - 2048MiB - 1.9GiB

sd-ext2 - ext4 - 2048MiB - 1.9GiB

swap - swap - 129MiB -

I am on the stock SD-EXT and Dalvik a2sd, I ran terminal and set up su install a2sd.

I am trying to not even install, just update Google Maps and getting this error "Insufficient storage available". My storage info is as follows from the Android system.

INTERNAL STORAGE - Total space 148MB

Apps - 91.23MB

Available - 27.11MB

SD CARD - Total space 3.27GB

(and so on)

Normally I would not be frustrated and I would just keep trying different options, but having to change around the Google Play store vending file each time is eating at my time.

Can someone please tell me what I am doing wrong with my SD-Ext that is causing this to just not work?
[Desire Android Development] Coempi:
You don't need swap and sd-ext2 partition, ONLY 1 EXT4 partition with 1,5GB MAX. Repartition your SD and try again. Hope that helps.
[Desire Android Development] nate51:
Yeah I gave that a try last night, I repartitioned my SD and only did a 1GB partition EXT4 format ran su, then ran install a2sd.

I jumped back to my old HBOOT (data++) and my previous ROM and am also getting a low space error. I have never really looked into it because things have just always worked, am I supposed to see my internal storage space total as 253MB on data++ or should it be higher since it's supposed to be using my sd card as memory expansion?
[Desire Android Development] Coempi:
Use Quick System Info to check free space on internal and ext partition.

Best regards Coempi
[Desire Android Development] nate51:
Not sure how checking my free space on my internal will help the situation. It's telling me 16.26MB free space, but what I am saying is if a2sd is on (or I think it is) should my internal space not be reading as larger now? Or when I install apps my internal space should not be eaten away?

I need hand holding I hate to say on this part as I am not sure what exactly a2sd does or if it's even running correctly on my device any more, all I know is I never had this problem before with internal space until this ROM and due to me re-partitioning my sd card it now seems to affect the previous ROM I was running too.
[Desire Android Development] pawan1993:
A2SD just moves your apps to your sd-ext partition. Your internal storage should still stay remain the same as the internal data partition. But if you chose not to move app data or dalvik cache then your internal storage will fill up quite quickly, especially with dalvik still there. How many apps do you have?
[Desire Android Development] nate51:
On average I have 8 or 9 apps out side of the OS apps like Chrome, Apollo, email app, Google Maps, Street View.

They take up quite a bit of space but I never used to get the low internal storage message, now I am lucky if I can get on 6 of the out side apps.

Edit: Ok hopefully this shines some light on my problem, I found this in an earlier post by looking up sd-ext mod

Now when I first set up the ROM, I go to Terminal, type in su (enter) grant su permission, the indicator then goes from $ to #, I then type in install a2sd (enter) and I then get a list menu of options, but I have no idea what to do from there. So I am assuming that is where the problem is. I am not setting something up I should be. Can anyone shed light on that part for me?
[Desire Android Development] pawan1993:
So you didn't enable it? That's the entire problem haha. The recommended options are y for dalvik n for app data and y to reboot.
[Desire Android Development] nate51:
You got to clarify, if I knew what "y for dalvik n for app data and y to reboot" If I knew what to do, I wouldn't be asking the questions I am asking. Am I supposed to go into terminal and type "install a2sd y" or something like that? I go into terminal and type in "su (enter)" then "install a2sd(enter)" then I get a list

I am pretty sure I need to do something at this point but I have no clue what.

Also does the sd-ext mod Dalvik2SD need to be set up in Terminal? or is it not supposed to automatically install with the ROM? Full wipe, all partitions except SD.
[Desire Android Development] pawan1993:
Type the following in Terminal Emulator with each line signifying the enter key:

su

a2sd install

y

n

y

For the y, n, y options it will ask a question before you put those answers in.
[Desire Android Development] nate51:
I get as far as "as2d install" then I get this

"10apps2sd is either missing or not executable Aborting"

I selected Dalvik2sd in the as-ext mods in the install process if that makes any difference.
[Desire Android Development] pawan1993:
Reinstall the rom with internal a2sd as the option. The script isn't there that's why nothing is working.
[Desire Android Development] nate51:
Ok, kind of went a different route. I re-installed after full wipe and chose Amarullz ad2sdx as the sd-ext mod. My internal space read 0.98GB, I put 110MB of apps on it and it gave me a low space warning in the top left of the status bar. I tried terminal with that, got the same messages as before.

I then reinstalled after full wipe the stock a2sd and pawan your details worked. Followed them to a "T" and now I am able to put back on and run all my apps with no low space warning or insufficient space error so far.

Thanks so much for being patient and helping me out with that.
[Desire Android Development] Xelio:
I have the same problem with 0.18.2.1 and int2ext+

As i look into logcat, it complaint that "/data/misc/wifi/wpa_supplicant.conf" is read only.

So i run "mount" in adb shell, i got following,

/dev/block/mmcblk0p2 /data ext3 ro,nosuid,nodev,noatime,nodiratime,barrier=1,nodelalloc,data=ordered 0 0

It show that /data is read-only, but I can't remount /data as read-write, only a reboot can solve it. But the problem reappear after a few hours. :(
[Desire Android Development] pawan1993:
No problem :) I would just like to point out that instructions for this were on the OP so it might be best to follow instructions on the OP or dev's website for future references and then ask questions.
[Desire Android Development] mmg06:
Can anybody tell me where i find Themes 4 this rom?
[Desire Android Development] nate51:
Hey pawan, yes I did do what the OP stated, but I think the first few times I tried I didn't have my sd card partitioned properly or something because a2sd install never worked for me in terminal on any of the sd-ext I chose during install (I never got the questions, it was always the BusyBox list). I re-partitioned again before the last install and checked alignment of partition and wiped all ext except sdcard. So there must have been something wrong with my sd-ext I think.

Trust me I feel pretty bad with how smooth it worked this round after all my posts.
[Desire Android Development] pawan1993:
Haha don't worry about it :) Just letting you know, that's all. I highly recommend using gparted from a Linux distribution to partition your SD card. It works almost 100% of the time perfectly well. As good as 4ext is in doing things it doesn't compare to using gparted and it perfectly aligns your partitions too. Just partition the Fat32 partition before the Ext partition each time. You won't run into any issues there :)

---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------

I'm not sure if this rom uses the T-mobile theme chooser. If the settings menu has a Themes section then you can pretty much use any CM9/AOKP theme I think.
[Desire Android Development] ntn_labs:
Yeap, amarullz has some issues here, but the stock one should work.

---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------

BTW: any ideas how to get the new google now on 0.18.2.1? Will it update through google play or will I need new velvet.apk?
[Desire Android Development] Hammerbak:
I had the problem that int2sd+ didn't work on my initial try and therefore I went with stock a2sd, but now I'm missing space on my desire so I wanted to try with the int2sd+ script again.

I get stuck in a wierd boot-loop after removing the vending apks when I run with int2sd+ unlike when I use stock a2sd.

Following 5 lines is what I get from logcat as for when it loops over again. A full logcat can be posted if needed:

I/ServiceManager( 130): service 'media.audio.flinger' died
I/ServiceManager( 130): service 'media.player' died
I/ServiceManager( 130): service 'media.camera' died
I/ServiceManager( 130): service 'media.audio_policy' died
I/Netd ( 327): Netd 1.0 starting

Has anyone fixed the "market update"-gltich while using the int2sd+ script? Or does someone have some suggestions of what I could try?

I haven't tried with the normal int2sd script, but for now I don't have time. I will try that tomorrow or on wednesday and post back my findings
[Desire Android Development] Coempi:
Search XDA (e.g. like this: http://xdaforums.com/sitesearch.php?q=google%20now%20zip) and you can choose from a variety of possibilities.
[Desire Android Development] freakymonkey:
I've a little problem with 3g.

Sometime my 3g stop working and the only way to restart it is to shut down mobile data and power on it again (I use the specific button on QwikWidgets).

I installed 18.2.1 with tiamat kernel, int2ext+, old RIL and I have 5.17.05.08 radio.

Anyone have the same issue?
[Desire Android Development] Skippernl:
Known problem.

Sandvold is working on it.
[Desire Android Development] mascolel:
Sandvold,

Will you start developing 4.2 Key Lime Pie for HTC? That would be fantastic!
[Desire Android Development] aardappel12:
4.2 is not KLP, it's still Jelly Bean
[Desire Android Development] Hammerbak:
Yup.

KLP is still "unnamed" :Android (operating system) on Wikipedia.com
[Desire Android Development] Arbelac:
Did you wipe the Dalvik cache after deleting the APKs? You'll still get a boot loop if you don't wipe Dalvik.
[Desire Android Development] Hammerbak:
I did what everyone else did, in the case that it helped them to avoid the boot loop. I read every post all the way back to 1600 and forward to this.

Nothing fixed my problem.
[Desire Android Development] nate51:
There must be a step missing, do you try the ADB method or the ES File Explorer method?
[Desire Android Development] Hammerbak:
I tried both. Without success both times. I'm guessing that I ended up in the loop due to the int2sd script.

Only thing I can think of as being the problem could be that int2sd isn't supported on stock hboot, but as far as I know it is. I used it for some time before the "market" problem together with the cm7r2 hboot, but due to not being able to use google now on that hboot I switched back to stock.
[Desire Android Development] Coempi:
One solution for the Market problem: settings, applications, go to Play Store, uninstall updates, restart phone and there you go: No bootloops.

Hope this helps.

Best regards, Coempi
[Desire Android Development] nate51:
It could be the int2sd script, I'm not sure. I am using stock HBOOT with the stock a2sd, activated through terminal and the method done with ES Explorer works fine for me. I would say if you don't have any ties with int2sd I would switch to stock a2sd, save yourself the headache of trying to solve the problem.

---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------

But if he does that won't he have to do it every time he shuts the phone down or restarts? Otherwise wont the market update the second he connects to the internet?
[Desire Android Development] lifeisfun:
Time to upgrade from Leedroid

I'm thinking going to this ROM from Leedroid 3.3.3,

is there step by step guide how to?

I tried to find it but having no luck

Thanks :confused:
[Desire Android Development] Hammerbak:
It's pretty straight forward since it's implemented with the aroma installer. Just remember to wipe (data, sd-ext and etc) your device before booting it up. I would though suggest that you go with the "customized" setup. Once the installer ask whether you want the "Typical" or "Customized" setup - choose customized. Most of the stuff you're able to activate has descriptions. If it doesn't and you don't know what it is, don't touch it. At least that is my experience ;)
[Desire Android Development] lifeisfun:
Thanks for the prompt reply,

I did not flash the phone for over a year now so this wont be easy for me.

I upgrade my tablet using CWM but the Desire was always flashed using PC.

The CWM version on the desire is 2.5.X.X, do I need to upgrade that?

Right now I'm on LeeDrOiD HD V3.3.3 A2SD

Do I need to do something special ?

Thanks for your time!
[Desire Android Development] nate51:
I would put in 4EXT it will replace CWM in a way and usually recommended by developers I find. Also just make sure your SD card has 1 partition no more than 1.5 GB. That's why 4EXT is recommended I think. And just make sure to read back on peoples experiences with this ROM and its features. I recommend stock a2sd, I had nothing but headaches with the other sd-ext mods. And also look up the boot loop issue with Play Store. Some have had success with the fix, some have not.