yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] Saf98:
ok make sure you format your sd card with 4ext recovery installed and make a 1gb partition. make sure you follow the instructions, i dont think you need mounts2sd cos it already has a2sd script that can be activated in terminal.
[Desire Q&A, Help & Troubleshooting] tasgo:
Settings stoped working

Hi,

After flashing GApps I'm unable to go to settings, contacts, play store...

Any ideas?

Thanks in advance.
[Desire Q&A, Help & Troubleshooting] dark_saian:
How to flash an hboot (simpliest way):

Quote:

1) download the alpha jelly zip and ensure its integrity by checking against the md5

2) save the alpha jelly zip to the root of your SD card and rename it into PB99IMG.zip

3) reboot into bootloader

4) apply the update

5) enter recovery

6) format all partitions except SD card

7) reboot into recovery -- now you can flash the ROM

I don't get step 4) . How do I know if the hboot flash is successful ?
[Desire Q&A, Help & Troubleshooting] Saf98:
When you go into the boot loader it will search the file and ask you to flash it vol up for yes and then it will tell you to reboot. Then you should see the hboot name changed.
[Desire Q&A, Help & Troubleshooting] yoyofool:
Hi everyone, I need some help with my Desire. I just installed the CM11 rom. The rom seems to works perfectly fine. But when I flash Gapss, Google Play Store crashes (Play store with the error: "Unfortunately, Google Play Store has stopped." en when I try to log into my Google account "Unfortunately, the process com.google.process.gapps has stopped.")

I took the following steps to install the CM11 rom:

1.	Starting up in recorvery mode (4EXT recovery touch 1.0.0.3 Beta 6)

2.	Wipe data/factory reset

3.	Wipe cache and wipe dalvik cache

4.	Format SDcard (with 4EXT recovery touch)

5.	Partition my SDcard (1024mb , with 4EXT recovery touch)

6.	Flash CM11 (cm-11-20150404-UNOFFICIAL-bravo)

7.	Boot rom and enable A2SD (using the method described in post #1 of the "[ROM] [4.4.4] UNOFF. CyanogenMod11 based on Nightly 15/04/04 | KitKANG v1.1 | STABLE" thread)

8.	Flash GAPSS (spz_gapps-slim-kitkang-1.1)

Did I forgot any steps here?
[Desire Q&A, Help & Troubleshooting] Saf98:
Have you flashed the alpha jelly hboot?
[Desire Q&A, Help & Troubleshooting] yoyofool:
oops, I forgot that! I just flashed the alpha jelly hboot and everything seems to working fine now! Thanks!
[Desire Q&A, Help & Troubleshooting] vidx31:
I flashed phone yesterday. Pretty enjoy improvement done in performance. However, got exchange service stop working when phone boots up every time.

Thanks.
[Desire Q&A, Help & Troubleshooting] xemul:
Hi, I have installed last version of CM11. I can't use my existing Google account - there is the message "There is no connection to server". Howewer, I can surf over Internet by Browser. I have installed CM11 and pa_gapps-modular-pico-4.4.4-20150308-signed.zip using Recovery recommended in 1st post.
[Desire Q&A, Help & Troubleshooting] spezi77:
I claim no responsibility for Google apps and stuff.

Sent from my Nexus™4 ?
[Desire Q&A, Help & Troubleshooting] vidx31:
The initial download may have issue. After I flashed rom again exchange problem is gone. I can feel speed improvement on video playback in browser and image seems more clear when play movie clips. Thanks for your work!
[Desire Q&A, Help & Troubleshooting] spezi77:
Great to hear. We switched the video codec now to m4v instead of h.264 :D

Sent from my Nexus™4 ?
[Desire Q&A, Help & Troubleshooting] userx404:
install problems

Installing KitKANG

set_metadata_recursive: some changes failed

E: Error in /sdcard/cm-11-20150419-UNOFFICIAL-bravo.zip

(Status 7)

Installation aborted.

Same problem here. I have installed the modded 4ext recovery and formated the SD with recovery and MiniTool partition wizard. Always the same error.

At "info" i see my partitions, but on SD always "sd-ext is not formatted" is displayed.

Any Hints to go further?
[Desire Q&A, Help & Troubleshooting] Saf98:
Are you s off?
[Desire Q&A, Help & Troubleshooting] userx404:
Yes, S-off

Also Tested with another SD with 1GB ext4 partition.... same result
[Desire Q&A, Help & Troubleshooting] Saf98:
So u made a partition with minitool?
[Desire Q&A, Help & Troubleshooting] spezi77:
Which recovery?

Sent from my nexus 4 :D
[Desire Q&A, Help & Troubleshooting] userx404:
AlphaRev LP-loopbk

BRAVO PVT3 SHIP S-OFF

HBOOT-6.93.1002

and the modified 4EXT Touch Recovery (v1.0.0.5 RC9 Testing. built 40),

...which were mentioned at the installation notes.

Starting without SD, at info following is displayed:

system mtd3 420.0MiB 418.9MiB

data ext4 --MiB -- MiB

cache mtd4 5.0MiB 4.2MiB

is there anything wrong with the data partition?

with SD:

....

data ext4 1.5GiB 1.5GiB

.....

sdcart fat32 6.06GiB 5.8GiB

warning: sd-ext is not formatted!

but no chance to get a rid of this warning
[Desire Q&A, Help & Troubleshooting] ze7zez:
How you created partitions?

On the SD must be two primary partitions.

First - fat32

Second - ext4

With me on the Stock Hboot partitions look like in the picture.
[Desire Q&A, Help & Troubleshooting] userx404:
tried both, with minitool and 4ext format tool

with a 8GB and 2GB SD

but the install-zip on fat32 and tried to install. always the same result. (KitKANG v1.2 / CM11 UNOFFICIAL 19/04/04 - md5 checked)
[Desire Q&A, Help & Troubleshooting] ze7zez:
Do it by gparted.

In gparted first delete all partitions, and then create from scratch.
[Desire Q&A, Help & Troubleshooting] userx404:
tried with GParted leads to the same result... sd-ext is not formated.

comparing my screen with yours -> it seems to me you have a different HBOOT version (250M System)
[Desire Q&A, Help & Troubleshooting] Saf98:
What hboot have you got? Are you sure its stock?
[Desire Q&A, Help & Troubleshooting] userx404:
No, not stock hboot

I installed the hboot verion mentioned in the "Updated Installation notes!"

Hboot with at least 400mb on system

(see the first post in ROM-Thread)

is it not the correct version for KitKANG version 1.2 ??
[Desire Q&A, Help & Troubleshooting] ze7zez:
He deceived me the title of the thread.

Now I know that you want to install KitKANG 1.2.

In this case, strictly follow the instructions to install from the second post (What's new in v1.2 etc).

The trick with the transfer of data partition on the sd-ext require careful installation as suggested by the OP.

I am not in favor of killing flash memory.

Transfer intensively used data partition on the flash memory threatens to rapid wear.

Such roms I will not be using. Too bad my nerves and waiting when it all falls.
[Desire Q&A, Help & Troubleshooting] samworm:
Congratulations spezi77 - exceptional work.

My daughter's phone broke and I remembered my Desire lurking at the back of a box on my shelf. Followed your instructions on the front page to install the HBOOT, 4EXT Touch Recovery, ROM and GAPPs. All worked first time and faultlessly. Very quick and easy.

Had to do the initial account setup over the phone connection because the WIFI took several minutes to detect my router. Installing apps was very slow, in fact the whole OS bogs down whenever the SD is written to but that could be the ancient card. This device hasn't been turned on for at least 2 years and you've put some new life into it. Superb. Not a single FC yet. Thanks a lot for your efforts, there is absolutely no way I would ever allow my child to slum it on an obsolete OS. You've saved the day ;)
[Desire Q&A, Help & Troubleshooting] Saf98:
You could try with a class 6 sd card?
[Desire Q&A, Help & Troubleshooting] rumunpl:
Hello. I have a problem. After changing hboot and install ROM does not reboots the system. It shows the logo of commissioning, load and nothing. I left so the phone for 20 minutes and still nothing. Help.

PS. sorry for my bad language. :D
[Desire Q&A, Help & Troubleshooting] say hi:
Stay in htc logo

A long time
[Desire Q&A, Help & Troubleshooting] ze7zez:
Before installing remove the SIM card. In addition, try on another SD card.
[Desire Q&A, Help & Troubleshooting] code4bugs:
Wipe and flashed with pa gapps, work well. Only 2 things:

- The link for using the radio fm is incorrect (from xda this works http://xdaforums.com/showpost.php?p=57261804&postcount=8695 )

- Is it correct to see from "about phone" 356 MB of ram?

always thanks for your & the other's work
[Desire Q&A, Help & Troubleshooting] eardor:
Hi

Thanks for you work.

I have install the new build but my wifi network is not visible. I change the region code to the same in my router but it does not work. WIth carbonrom the wifi works.

I have install the rom few times but my wife does not appear. And yes the wifi on my desire is on and also on my router. As I say it before with the new carbon rom i works

Thanks
[Desire Q&A, Help & Troubleshooting] Axora:
I update from V1.2 to 2.0. After full wipe twice, I try to install from sdcard and it endup with error:

set_metadata_recursive: some changes failed

E:Error in /sdcard/cm-11-20150815-UNOFFICIAL-brave.zip

(Status 7)

The md5sum seems correct: 80fd7c54d83c2e5addb24deedbb80639
[Desire Q&A, Help & Troubleshooting] spezi77:
You also have to update the recovery. See instructions.

Sent from my Nexus™4 :D
[Desire Q&A, Help & Troubleshooting] Axora:
I've download again and flash it via PB99IMG method. It doesn't prompt for update. So I flash it via fastboot.

But the same error again when flash the rom...
[Desire Q&A, Help & Troubleshooting] spezi77:
Hum, you could try to delete the kitkang.zip from the SD and then copy it over again. Take care to properly eject the SD and then try again to flash it.

Sent from my Nexus™4. :D
[Desire Q&A, Help & Troubleshooting] Axora:
I've even download it again but the same error.:crying:
[Desire Q&A, Help & Troubleshooting] spezi77:
Edit: Maybe you could try to start from scratch. Sometimes it helps to reboot the recovery after copying files to the SD and before flashing.
[Desire Q&A, Help & Troubleshooting] Grizzly`:
blue arrow circling into eternity...

Hi spezi,

having used your ROM for most versions since 0.7 on my primary phone without major issues, I first have to say thank you. You're doing great work, and I love that I can still use my 5 year old phone with 4.4.4.

Unfortunatelly this time, updating to 2.0, I am stuck. Strangely enough this is the first time I actually followed your instructions :). In the past, I never bothered to update hboot and/or recovery. I just used the really ancient ones that were used when the stock htc rom was originally replaced by a custom rom years ago. I always just wiped everything, occasionally repartitioned the sd, flashed the rom, and everything was fine.

This time I wanted to do things properly, so for the first time Iactually upgraded hboot and recovery to the versions you suggest. Both updates worked just fine using the PB99 method. Then I wiped and flashed, and .... the rom gets stuck with the cyanogen boot screen with the blue arrow circling for infinity.

I have since tried about a dozend more times, doing things in different order, re-updating hboot and recovery, repartitioning the sd (using 4-ext recovery), with flashing gapps, without flashing gapps, .... Nothing seems to help, the result is always the same. The blue arrow circles around the evil face for eternity. I actually left it over night tonight, so If it just took a long time, this should really have been long enough.

Is there anything else I can try? Anything I can do to find out where it hangs? Even though I have used custom roms for a long time, I am still pretty helpless once there are some issues, exactly because in the past there never were any, it just always worked ridiculously easy.

I hope you can help.

Thanks,

Griz
[Desire Q&A, Help & Troubleshooting] Sting085:
Spezi, Thanks for these mods!

I have exactly the same problem as described here, below my story :)

I first installed kitkang 1.2 and had 2 problems:

1.	Screen flickering at random moments, which then required a reboot to fix it.

2.	With incoming calls, the phone rings and vibrates, but the screen remains off. After 4 seconds it turns on and I see the number that is calling me, and I see the button that allows me to answer or decline the call. After another 2 seconds, the phone number turns into information gathered from my contact list (so I finally know who is calling). People now ask me why it took me so long to answer the phone…

Seeing the release of kitkang 2.0, I decided to start from scratch, hoping this new release would resolve the issues. I whipped/formatted everything, flashed latest advised Hboot and recovery, repartitioned the class 10 microsd (1.5GB ext4 and 14.5GB fat32), and then installed Kitkang2.0. Everything went well until the first boot. The cyanogen boot screen comes up and keeps loading forever. Sometimes it freezes, other times it just shuts down the device completely after 30 minutes of loading (after which I have to remove the battery for at least 30 secs to boot again). Every time the booting of the phone failed, I whipped/formatted everything I could find in the EXT4recovery menus and started from scratch. After 6 times I gave up, and recovered back to Kitkang1.2 using the EXT4recovery backup/restore function (works great btw).

Surprisingly the screen flickering issues have now been resolved in 1.2. However, the incoming call issue still remains. Disabling and clearing dialer cache has not worked. Does anybody else have this problem? I can only find people with nexus5 reporting similar sounding problems, but not exactly how I describe it.

Anyway thanks for all the work and support!
[Desire Q&A, Help & Troubleshooting] spezi77:
Hey there [MENTION=6907630]Grizzly`[/MENTION]and [MENTION=6907922]Sting085[/MENTION] !

You could have provided for two things to allow a remote diagnosis.

1. Copy the recovery.log to your SD after ROM installation

2. Take a logcat at 1st boot

Please share it in this thread.

Cheers! ;)

Sent from my Nexus™4. :D
[Desire Q&A, Help & Troubleshooting] Grizzly`:
Hi spezi,

thank you, that is exactly what I was looking for.

I tried to post the recovery.log (its 1428 lines long!), but the forum would then always tell me "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" and refuse my submission. I looked through the whole log but could not find any lines that, to my human eyes, looked like they could be interpreted as an external link. What to do? I'm not sure if it is a good idea to paste such a long file here anyway... what is the custom?

I'm now wondering about four lines in the log that say "mtd: not erasing bad block at 0x0b080000" (four different addresses of course). They occure right before the ca. 1200 lines about minzip extracting files, and to me they look like the only hints in the entire file that there might be something going wrong. Can this be the problem?

I use a fairly new (ca. 6 months) class 10 16gb sd card. I successfully reverted to version 1.2 of the rom this morning and it run fine all day (I needed a working phone).

I did not manage to generate a logcat during first boot. I hope I did it right: I entered "adb logcat -f spezi20_firstboot.txt" (adb server was started as root). It stuck with "- waiting for device -" for about 15 minutes, then I gave up.

Is there anything I should do differently to get this working?

Edit: I did manage to generate a logcat now. I was missing the -d flag. Still the same question as above applies: Is it a good idea to paste several thousand lines of code here?

Edit2:

Close to the beginning it says:

--------- beginning of /dev/log/system
I/auditd ( 90): Starting up
I/audit_log( 90): Previous audit logfile not detected
E/audit_log( 90): Could not open audit log file /data/misc/audit/audit.log : No such file or directory
E/auditd ( 90): Failed on audit_log_open
I/auditd ( 90): Exiting
--------- beginning of /dev/log/main
D/AK8973 ( 100): AK8973 daemon 1.3.4 Start
D/AK8973 ( 100): (Library version : 1.2.1.620)
I/installd( 98): installd firing up
I/DEBUG ( 92): debuggerd: Aug 14 2015 23:06:13
E/cutils ( 98): Failed to read /data/.layout_version: No such file or directory
E/installd( 98): Could not create directories; exiting.

and then most of the file are endless repetitions of long segments of lines like:

I/dalvikvm( 95): Unable to open or create cache for /system/framework/conscrypt.jar (/data/dalvik-cache/system@framework@conscrypt.jar@classes.dex)
D/dalvikvm( 95): Unable to process classpath element '/system/framework/conscrypt.jar'
E/dalvikvm( 95): Could not stat dex cache directory '/data/dalvik-cache': No such file or directory
I/dalvikvm( 95): Unable to open or create cache for /system/framework/okhttp.jar (/data/dalvik-cache/system@framework@okhttp.jar@classes.dex)
D/dalvikvm( 95): Unable to process classpath element '/system/framework/okhttp.jar'
E/dalvikvm( 95): Could not stat dex cache directory '/data/dalvik-cache': No such file or directory

Thanks a lot for trying to help!

Griz
[Desire Q&A, Help & Troubleshooting] Sting085:
Being new to the forum just like Grizzly, I can also link to external files. But maybethese adresses will make it through? (I will remove the links after you have replied)

-link removed-

-link removed-

Thanks!
[Desire Q&A, Help & Troubleshooting] Grizzly`:
Sting seems to have a similar, if not the same problem as I. At least the logcat seems to indicate that.

After googling around I am trying to create the file "/data/.layout_version" with a single digit "2" as content ;)

Just an idea, poking around in the fog....

Unfortunately I can not enter the /data/ directory from adb shell, since I can not become root. It is, by default, disabled in the system setting, which I can not access to enable it...

Is there another way to create that file? Any place in the zip file, where I can add a few lines of shell code so it gets created after flashing?

Any ideas are appreciated :)... Until then I keep poking around in the darkness...

Thanks,

Griz
[Desire Q&A, Help & Troubleshooting] spezi77:
Guys, did you install the modified 4ext recovery mentioned in the installation instructions? ..other than that, I have no idea right now. Give me some time to look into it..

Edit: reading the logcat, it becomes clear that the ROM is stuck at boot time because it cannot create the dalvik cache.

E/dalvikvm( 95): Could not stat dex cache directory '/data/dalvik-cache': No such file or directory

Sent from my Nexus™4. :D
[Desire Q&A, Help & Troubleshooting] Grizzly`:
This one: d-h.st/PGVJ ? That's what I installed.

Hehe...

Still poking around in the fog here, but as an experiment I added some lines to the 00banner startup script in /etc/init.d to create the /data/.layout_version file if it does not exists and repacked the rom zip file.

The upside: my code is obviously executed. The downside: it can't work, because the filesystem seems to be read only at that time in the boot process...

This is what I get in logcat now:

I/run-parts( 102): /system/etc/init.d/00banner[15]: can't create /data/.layout_version: Read-only file system

I don't know if it would help anyway, but I got a feeling it might...

Anybody got an idea where to put the code to create that file so that it might actually work? Where are the scripts that start the installd?
[Desire Q&A, Help & Troubleshooting] Sting085:
Yep, this one:

PB99IMG_4ext_LP-loopbk.zip

MD5: 63626d496459279ff61a3538dfa74e52

v1.0.0.5 RC9 testing. build 40

Unlike Grizzly, I cannot think along with you.. I'm a complete newbie. :)
[Desire Q&A, Help & Troubleshooting] Grizzly`:
Hehe,

sting, don't be too dazzled by my brilliance... I have really no idea what I'm doing, I'm just too impatient to sit still and wait until a professional finds a solution, thus I keep tinkering until I either fix it or break it completely...

usually I break it completely :o
[Desire Q&A, Help & Troubleshooting] spezi77:
Alright, I have checked your recovery.log and I have found that for you the problem is that you have made the sd-ext partition as ext3. But we require it to be ext4.

See here:

recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data ext3 /dev/block/mmcblk0p2 (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)

And here is how the partition #3 /data should look:

3 /data ext4 /dev/block/mmcblk0p2 (null)

---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------

[MENTION=6907630]Grizzly`[/MENTION]

Can you also post your recovery.log?

You are not required to wipe or flash anything.. Just boot into recovery and copy to SD for sharing it.

Thanks.
[Desire Q&A, Help & Troubleshooting] Grizzly`:
Hi spezi

Mine is ext4 though:

Starting recovery on Thu Aug 27 16:31:24 2015
framebuffer: fd 3 (480 x 800)

Welcome to 4EXT Recovery Touch

by madmaxx82

Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data ext4 /dev/block/mmcblk0p2 (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)

Preparing boot.. 1I:end load volumes..
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Command: "/sbin/recovery"

Edit:

entire recovery log is here:

pastebin.com/epVybxDT

and beginning of logcat is here: (it never ends, keeps cycling until I turn it off)

pastebin.com/6uUUjJ2i

(edited again to put the CORRECT logcat, the other one was after my ill advised tinkering, this one is with your unchanged rom zip)
[Desire Q&A, Help & Troubleshooting] spezi77:
Yes, your partition layout looks fine. But something goes wrong at the time when the rom attempts to create the dalvik-cache.

Please give this a try.

1. Do a full wipe by using "Format all partitions except sdcard"

2. Flash the rom

3. Boot it and take logcat.

I think that you forgot to format all partitions after changing the hboot.
[Desire Q&A, Help & Troubleshooting] TheWooky:
Griz, the fact that you are using a recovery called 4EXT does not mean that your partitions will automatically be ext4....

Very, very confusing indeed. Look for the options when formatting and choose "ext4" .

Verstuurd vanaf mijn TF300T met Tapatalk

---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------

Edit: after reading the rest of your log (Tapatalk was hiding it initially) I can see your filesysdtem is ext4 indeed. Sorry for confusing.

Verstuurd vanaf mijn TF300T met Tapatalk
[Desire Q&A, Help & Troubleshooting] Grizzly`:
Well, I am not sure I remembered wiping all partitions every single time I retried flashing during the last few days, but I am sure I did at least a few times.

Anyway, I did so again now, just to be sure. This are the two logs (first recovery.log, then logcat log from trying to boot first time):

pastebin.com/0eMRNUrj

pastebin.com/hbExLjGW

I now just noticed this line in both the new and the old logcat log, close to the top of the log:

D/Vold ( 89): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)

Does that mean there is an issue with the sd card?

I reinstalled release 1.2 successfully twice in between many tries of flashing release 2.0... but I'll try another sd card anyway, I have an older, smaller card lying around unused.

Griz
[Desire Q&A, Help & Troubleshooting] TheWooky:
Wiping is not enough, you should really format. Takes some time though!

Verstuurd vanaf mijn SM-G900F met Tapatalk