yashsingh1/xdaforums huggingface dataset:
[Touch HD General] shnopse:
hey,guys

how are u doing, hope all are right with u

i have an htc blackstone, am noob but am trying to learn about flashing.

since i was bored with wm6.1 i wanted badly to have wm6.5 or android on my htc at least for a change,i tried many roms, and my screen is freezinge and not responding all time,i mean with the process of flashing it's fine but when everything is done,the rom works but the screen freeze,so i need to know how to update this hspl 1.56 or any other solution that will allow me to use wm6.5 or any good rom.please help i was suffering for 3 days now,and can't get anything smooth :(

Cherrs,

Yassine
[Touch HD General] Chef_Tony:
first, enter bootloader mode by shutting down the device completely, then pressing vol down and power and have a look at the 4 colored screen. it will show your current spl. please post that here.

since you already tried different roms, i assume it is hspl 1.56 already.

hspl is meant for unlocking your device to all kinds of roms, like roms from other countries (if your device is not a native wwe device).

it does not affect the speed of roms, it just makes it possible to flash and boot them at all.

things you can do to speed up your device, is perform a task 29 before flashing and perform several hard resets after flashing. probably your device is still carrying around waste from previous operating systems which makes it slow and unstable.

also, any cooked rom found here will perform slower than the stock rom you are used to but the trouble you describe is beyond the expected.
[Touch HD General] shnopse:
Thx Tony ,i appreciate your replay.this what it shows on the bootloader screen:

Blac100 32 m

Spl-1.56.olinex

microp-blackstone(led)V6

this displayed on the red part,of the bootloder,no info in the green and blue one,and usb showed on the white one down

As i told you i tried various rom, i even tried the original one which i download from htc website,the phone was working smoothly before,but after flashing,the room are installed,but the screen touch is not responding anymore,is there any way to get back the phone to the original setting,or any solution like compatible rom with spl 1.56 oilnex,i can't use that phone anymore ,only voulme button and power one works for the moment,please help me to fix those issues

i already perform task 29 and i cleaned the whole things,but still the some issue

best regards
[Touch HD General] raving_nanza:
strange

if it was a bad rom flash, it would be fixed after a reflash of a new rom or even a task29.. defo not rom related.

are you sure you have not droppend your device recently because its starting to sound like it is a hardware issue = lcd/digitizer

to be honest i cannot see this being a hardware issue either, if the device was fine before you flashed a new rom :confused:

*but i could be wrong

my personal opinion would be to try a couple more custom roms, if it still does not respond to touch then its time you opened your device and took a look inside..

Rn
[Thunderbolt Q&A, Help & Troubleshooting] Darkestred:
If this was posted already, i apologize as i didn't see anything. I just finished matching the hash from step 6. Before step 6 ends, there is a disclaimer about non-matching hashes and then below it, "reboot." I'm a bit thrown off by reboot. Is that implying that i should be doing adb reboot bootloader? or am i putting the upgrade onto my sd card and then rebooting (adb reboot bootloader)? or am i physically rebooting the device?

Thanks for any help.
[Thunderbolt Q&A, Help & Troubleshooting] scassel:
If you are referring to the reboot at the end of step six in this tutorial

http://xdaforums.com/showthread.php?t=996616

you are to reboot (adb reboot) the device.
[HTC EVO 3D] |Jason8|:
Hey guys! Just wanted to post a few videos of some extremely loud events I've had the chance to attend. Any other phone (or midrange video camera) that I've ever seen has taken decent videos but the sound quality has been awful.

Anyways, here's a video of some (2D) fireworks from last night:

https://picasaweb.google.com/lh/photo/upxdeIgX-DoVgpZe6qFB3g?feat=directlink

And a 3D clip from the NASCAR Nationwide Series race at Road America a few weekends ago:

http://www.youtube.com/watch?v=m_qnavY3ZbE

Hardly any distortion, especially for a phone! I'm super happy with it.
[HTC EVO 3D] heathmcabee:
I'm impressed.. Gonna do the same with my phone tonight and see how it turns out.
[HTC EVO 3D] VoXHTC:
Totally agree OP. Great firework vid!

FINALLY - Apple/iPhail have absolutely nothing to brag about. - top notch camcorder on this phone!
[Galaxy S II General] Breece:
Well.. I've got a problem:

Today I wanted to use my Samsung headset that came with the S2, plugged it in, and the music sounded wierd. Like there was an echo, or if all my music was a karaoke version..

Turns out:

Non-Headset headphones work perfectly, but the "3-ringed-jack" headset does not work! I do not have another headset to test this, but the headset works @my pc (got a connector for that..)

So the 3.5mm jack at my S2 seems to be broken? :(

I will try a software reset (right now I am @stock rom+root) and then send it to Amazon. Anyone heard of that problem or got some ideas?

Breece

[edit]

Reset didnt help, but the headset does *not* work on my Nexus one (same problem) but my BH905i do not work on both phones with the 3.5mm jack (the one that has "3 rings")
[Galaxy S II General] kaotickelly:
Did you push the pin in far enough?

For 3 weeks I didn't know I had to push it hard into the jack, until it clicks. After that, it was perfect. I'm using Ultimate ears 220vi, 3 ring.
[Galaxy S II General] rwj5279955:
That has to be the pin. you must give it a good press to seat it properly.
[Galaxy S II General] sandeep10:
The SGS2 headset jack is a bit 'finicky'. Some aux cables / headsets work, some sound funny or do not work and yes, one has to ensure it is really pushed in firmly.
[Galaxy S II General] Breece:
I pushed as if my life depended on it :( Just last week the headset worked...
[Galaxy S II General] elkikin:
The same thing happened to me, but I noticed ealier. :D
[Galaxy S II General] Breece:
I re-installed the firmware but nothing seems to help. I guess its hardware..

Will send it back to Amazon today...

Maybe the headset is broken after all, who knows :(
[Galaxy S II General] Breece:
Just an update:

Has been @ the amazon repair center for two days and apparently something did indeed brake in the hardware... atleast it says on the homepage "being repaired"

Now I hope the S2 will be back soon.. want to flash 2.3.4 ;)
[Galaxy S II General] Extreme184X:
Shoot I was just about to ORDER a replacement Audio Jack, until I read the second poster reply. For me, my headset worked only by wiggling the cable around into the audio jack in order to finally hear sound (had do this every single time and was very annoying), the audio did sound distorted and the mic would never work :-(

I personally thought that I inserted the cable in the audio jack as hard I could (after many attempts having this phone for 2 months)

but after reading kaotickelly's reply, I noticed i never EVER heard a click before inserting the cable in the jack throughout many attempts.

So I put my "trying to over protect my phone" ignorance aside, and FORCED the dam thing in, and it clicked!!! not only did I forced it, but I didn't scratch or break phone as i feared, Headset sounded correctly without any distortion and microphone worked!

Unlike Breece, my audio jack now works and I got to UPDATE to 2.3.4! (Don't take it personal)

GOOD-LOOKING OUT KAOTICKELLY!
[Epic 4G Q&A, Help & Troubleshooting] ecooce:
So I'm trying to make a GB theme and can't find the wifi icons,not in their normal folder???

Help support autism awareness,it only takes 2 seconds to help make a difference...

http://picketfenceblogs.com/vote/3616

Sent from MyEF02 using XDAPA...
[Epic 4G Q&A, Help & Troubleshooting] crawrj:
I think they are in systemui.apk but haven't tried it myself.
[Epic 4G Q&A, Help & Troubleshooting] ac16313:
Yup in system/app/systemui.apk its called stat_sys_wifi_signal_*.png

Sent from my SPH-D700
[Epic 4G Q&A, Help & Troubleshooting] ecooce:
Thanks to the both of you, looked in every folder before I asked...

Help support autism awareness,it only takes 2 seconds to help make a difference...

http://picketfenceblogs.com/vote/3616

Sent from MyEF02 using XDAPA...
[Desire Android Development] k3lcior:
Thanks ill try it tomorrow. ;)
[Desire Android Development] madmaxx82:
Thanks ;)
[Desire Android Development] Nyto75:
Good job I'll test it :)
[Desire Android Development] madmaxx82:
Thnx :) Please let me know.
[Desire Android Development] keyra74:
installed and for now it works

just used it to change my rom and wipe cache/dalvik but i'll test ext4 and stuff later today

the weird thing is that it says i have 1gb swap partition but it's in fact the ext4 partition since i use app2sd with lot of apps
[Desire Android Development] bugfix2k:
Tried using this and at first it detected my ext3 partition and everything seemed fine. I made a backup and chose to convert sd-ext to ext4 on that backup at next restore.

Made a full wipe and restore from the latest backup. After reboot this recovery now detected my sd-ext as a 512MB swap and refused to restore ext-data to it.

I had to go back to CWM 3.1.0.1 and do a full wipe -> restore to get my system up and running again.

Did I do something wrong, or did I not understand how the recovery is supposed to work?
[Desire Android Development] beanbean50:
it didn't quite work for me, I'm using RCmix S V2 3.1 test

tried flashing it through ROM Manager Premium v4.3.2.4 (2.5.0.7)

-- Installing: SDCARD:/4EXTRecovery_v1.9_RC1_bravo.zip

Finding update package...

Opening update package...

Installing update...

4EXTRecovery v1..0 RC1

Installing..

assert failed: write_raw_image("/tmp/recovery.img"_

"recovery")

E: Error in /sdcard/4EXTRecovery_v1.9.0_RC1_bravo.zip

(Status 7)

Install aborted.

it's probably something that I'm doing wrong rather than the program itself though....
[Desire Android Development] bestdaniel20:
Thank you for your hard work , works perfectly for me
[Desire Android Development] tekarn:
I get the same message...
[Desire Android Development] keyra74:
looks like it doesn't see my ext when i use cm7_legacy_a2sd_r3, dunno why, it works with CM 4.0.0.5
[Desire Android Development] bestdaniel20:
try like this : http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
[Desire Android Development] tekarn:
thanks, but when I try that i get "error writing recovery: no space left on device"

I´m S-ON. Do you have to be S-OFF for this?
[Desire Android Development] madmaxx82:
Yes, most probably..

To you who are S-ON what do you use? Fake flash?

Sorry I don't know much about the desire.

Regarding the Bug identifying sd-ext as swap: can it be that the partition types are mixed up with some of you? I mean swap not being the LAST one?

I always thought with all those a2sd techinques, you would partition swap at last, i.e: fat32,ext,ext,swap, or fat32,ext,swap, or fat32,swap

If it's possible that you have fat32,swap,ext,ext or something like that, the recovery won't work right!
[Desire Android Development] bugfix2k:
I don't have swap. I only have one ext partition at 512MB.

The partitions that were detected on my device were initially:

Data - ext4

Cache - ext4

sdcard - fat32

sd-ext - ext3

Then after I tried to convert sd-ext to ext4 using a restore method (supported by the recovery?) my partitions were detected as:

Data - ext4

Cache - ext4

sdcard - fat32

swap - swap

I have no idea what this means.. and I can't really help you with bugtracking coz I need my phone up and running during daytime :P
[Desire Android Development] madmaxx82:
This is strange indeed. This feature works without problems since many weeks.

Could you please tell me how your partition table looked like and what file system you had on your sd-ext partition that you migrated to ext4?
[Desire Android Development] madmaxx82:
It detected data cache as ext4?!?

That's a major bug then. I'm very sorry.. extremely strange that sebastiaan and me didn't find that one.

Will look into that..

Please anyone who discovers any bug, please use the menu item in advanced to copy recovery.log to sd-card and send me the log.

Thanks in advance :)

I 'll take this recovery offline if it's like you say!
[Desire Android Development] AlxMAX:
Is this the source repository: github.com/arco/?
[Desire Android Development] madmaxx82:
???

It's based on koush's sources in the cyanogen repo only
[Desire Android Development] bugfix2k:
I'll try it again and post the log then. Gimme a few mins.
[Desire Android Development] madmaxx82:
Np!

Marking this release as unstable as it doesn't backup all roms for the desire it seems..

Tried really many, but this one slept through and even if it was the only one (which I doubt), this is really bad, because this shouldn't depend on the rom.. if the romname isn't suitable for a backup name the recovery should have backed up without name.. as a "fallback" option..

But this has failed..

Will go to sleep now and look resolve that later..

Thnx for reporting!
[Desire Android Development] bugfix2k:
I tried the newest 2.0.1 rc1 but still not able to backup my rom.

Going back to 1.9.1 rc1 since it's the only version that's worked perfectly for me :)

I'll attach it here for others that may have the same problem as me with backing up. This version doesn't add rom name to the backup, but atleast backups work :D

Thanks a million for your hard work madmaxx82, I will continue to test new releases to see if they fix my weird bug :P

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at 0
I:Set boot command ""
SD Card space free: 6159MB
mkdir: can't create directory '/sdcard/clockworkmod/backup/2011-07-08.06.01.18_AceSMod007v14
': Invalid argument
Backing up boot image...
error opening /sdcard/clockworkmod/backup/2011-07-08.06.01.18_AceSMod007v14
/boot.imgError while backing up boot image!mtd: successfully wrote block at 0
I:Set boot command ""
[Desire Android Development] madmaxx82:
Hi Bugfix :)

Thanks for posting and for the feedback!

I tried backing up with Acemodv17 (is this the newest one?) and it worked..

Strange..

I downloaded pretty much any rom I could find and tried it..

Just if you have time.. could you try if it works with newest acemod?

Would be very interesting and would save me a lot of time ;) (I mean to find the problem... )
[Desire Android Development] rophaq:
go to sleep man.

it's not the end , i'm sure you'll get it sorted.:cool:
[Desire Android Development] bugfix2k:
Ok, I'll try.
[Desire Android Development] madmaxx82:
:)

Yes you are right...

Absolutely... also I hate this to be rom dependant! This must stop! Today :D

I thought I already had something for any opportunity.. but failed :D

This is my last version before I go to bed ...

There seems to be a big problem with error correction.

This version should be very sensitive (I hope it's even too sensite) and should only backup with the romname if it's more than sure it will succeed, otherwise it should backup without romname like normal... don't know if it will work, haven't tried it.. too tired already.

Please tell me if this works for you who have trouble backing up.

Thank you!

edit: will press the thanks button later as I have reached xda's limit / day ;)

md5sum: 3d7b976ef07ad64c4cea55fb046b1c07
[Desire Android Development] rophaq:
here is a recovery log, if that help.

extracted the build.prop somehow wouldn't upload.
[Desire Android Development] madmaxx82:
Thanks! This might be all I need!

I think I found the problem...

Ok, but now good night :D
[Desire Android Development] rophaq:
goodnight, i'm gonna try cool sensation and see , if not i'll revert back. i like cool kingdom,
[Desire Android Development] bugfix2k:
I've upgraded my ROM to AceSMod007v17 and flashed 2.0.1 RC2 (even though it says RC1 in the recovery ;)). Everything is working fine now :) Thanks buddy!!
[Desire Android Development] bmonster:
all good for me, Thanx :)

One Question can we still use rom manager to rename the roms without messing up the MD5.

Tested Renaming the Rom and works fine, tested most functions of the recovery now, with no problems.
[Desire Android Development] rophaq:
upgraded to cool sensation now, backup worked fine, must be a bug in cool kingdom,that's why it could'nt backup.

thanks for all the hard work you put in,( been at it all night till the morning) , sorted at last, loving this recovery, theee best.

:)

cheers
[Desire Android Development] madmaxx82:
Could someone please help me out with a build.prop from Kingdom v8 and acesmodv14?

Thnx very much!
[Desire Android Development] ziggy1001:
Cool-Kingdom-v8 build.prop ;)
[Desire Android Development] madmaxx82:
Thank you :) that was fast!

Edit: Yes!!! This helped me to find a little but nasty bug! Fixed :) Now some more error handling and I hope this problem will never return :)
[Desire Android Development] madmaxx82:
Seems to be really fixed now..

Forgot to terminate the string if the romname didn't contain spaces or was short. This caused the backup to fail.

Even impossible romnames with very strange characters are now backed up without problem.

Example: ;C."o;ol-Kin$gd%o,:m-v(8

Will be backed up as for example: 2011-07-08.14.14.22_C.ool-Kingdom-v8

I hope I now found any possible case..

Will upload shortly..
[Desire Android Development] suiller:
well done freund ;)

I'll test soon as you upload corrected version :cool:
[Desire Android Development] rophaq:
hi madmaxx, hope you've had a good sleep, just got back, here is the build prop,the one you've asked for, from the kingdom rom , i was having trouble with, extracted earlier but couldn't upload it, if it helps.

as for backing up, it's fine.

file description is good. here is a screen shot , bit naff, showing 4, it's only one on the phone.

somehow it took a good shot of the bootanimation, i got from the EVO 4G forum, and it worked on the desire.

cheers
[Desire Android Development] bugfix2k:
Nice work madmaxx82 :) you're really dedicated to squash all bugs! :D
[Desire Android Development] madmaxx82:
Don't say that before it's proven that it works :D

Thnx anyway !
[Desire Android Development] ghiki:
I saw some SDCard's that are "limited" from manufacturer, try "creating new partition table" from GParted...maybe it would work
[Desire Android Development] bmonster:
Works fine for me, and everyone else. so guess you should stick with cwm.
[Desire Android Development] John_Blaze:
Haha i know right?!
[Desire Android Development] octa_amide:
Maybe you need to format your SD card with the format tool from SDcard.org

Using brand new card straight out of the box is not a good idea.

The tool did help me to correct some "error" before my phone can "see" the SDcard.

After doing it once. No problem for me so far.

Hope it helps you.

Sent from my HTC Desire running SuperNova 2.1.0.0 with a 32GB Class10
[Desire Android Development] chrismast:
I assume you quoted the wrong post? ;)
[Desire Android Development] ZeGuitarist:
Oh my.
[Desire Android Development] John_Blaze:
Hahahaha yep i sure did! My bad.. :D
[Desire Android Development] madmaxx82:
New versions of recovery and 4EXT Recovery Control.

Big changes :)
[Desire Android Development] madmaxx82:
Hahahaha

Thank you for that :D
[Desire Android Development] Telek:
Does anyone know if it is possible to install this via recovery mode? I have 4EXT installed but an older version and right now cannot get an OS installed. Would like to update 4EXT to the latest version - is there a way to do it from recovery mode?
[Desire Android Development] madmaxx82:
Why do you want to update recovery to the very latest version now before you install an OS when you already have 4ext?

You can use the PB99IMG.zip in the first post to update recovery if your version is really that old and update to the latest after you installed your rom..

I know I need to add links, but I was working full time on the last changes that were badly needed that I didn't assign this a high priority.
[Desire Android Development] Telek:
BTW I did just purchase today since this is a very useful piece of software :)

Ok so I can use the "Install from ZIP" option with PB99IMG.zip to update from within 4EXT to the latest version?

I'm hoping that the latest version will help since my phone is pretty broken right now. It can't format any of the internal flash without error.

BTW does using "Wipe all partitions" erase 4EXT as well?
[Desire Android Development] madmaxx82:
Thank you very much :)

Bad to hear about your phone though.. I can't imagine the new version would help bad blocks though :(

No.. the PB99IMG.zip must be placed on your sdcard.. then you boot into the bootloader and it will flash it automatically.

Edit: uploaded the image for you. It's the same you get when you download through the app!
[Desire Android Development] Telek:
Ok, is there an updated PB99IMG.zip ? The one from the first thread seems to be old.

So the important part for me to know right now is even if my flash is b0rked I can still get into the bootloader via vol-down when powering on?

My phone is inside 4EXT right now and having a great deal of trouble getting anything to install without errors. I don't want to power off or reboot because I don't know if I can get back into here.

Does "wipe all partitions" erase 4ext as well?

I've got a thread going http://xdaforums.com/showthread.php?p=18043750#post18043750 with some snippits of the recovery.log . If you could take a look I'd be forever grateful and will even donate :)
[Desire Android Development] madmaxx82:
I have attached the current recovery.img for you in the above post.

You can't flash it from inside recovery..

No when you wipe all, then recovery will stay..

I would extract the bravo.zip, and put it inside your PB99IMG.zip replacing the old recovery.img there.

I will take a look at your thread!
[Desire Android Development] madmaxx82:
You have a Desire HD?!?

Forget the PB99IMG.zip and forget the bravo.zip I uploaded.. you are in the wrong forum!
[Desire Android Development] Telek:
Ahh nurtz. Didn't notice that (just did a google search and it showed Desire though it was the right thread).

I assume this is the right thread? http://xdaforums.com/showthread.php?t=1161710&highlight=4ext
[Desire Android Development] crasher:
Annoying Problem

I've just realised an annoying problem after you have made it downloadable only from your app. If I do not already have a version on my pc, I will be unable to flash the img to my phone after I change the hboot, as the recovery now hangs on preparing boot, and will have to fall back to the previously downloaded v2.1.3RC4. I just hope it can restore the files correctly.

The whole point is to be able to backup and restore with a piece of mind, this situation however, is not.

btw, does anyone have the latest .img file that you can share?
[Desire Android Development] madmaxx82:
You are right!

I'm just so busy that I don't know what to do next.

It's a lot of work to update 7 threads when there is a new version.

I need to add auto generated links to the website.

I will give you a link.

Give me 1 min

Edit: www.4ext.net/bravo.zip <-- 2.2.6 RC4
[Desire Android Development] crasher:
That was some quick reply and support. Cleared all partitions and flashed 2.2.6RC4 with fastboot commander. Restore is running as I type. You deserve more app purchases in the market. I would still like the img on my pc thou:D
[Desire Android Development] madmaxx82:
Thank you :)

I will add those links as soon as possible!

BTW: I know this is no real alternative, but you can download all versions and save them to your sdcard with the app too ;)

And there is also a setting to always save the recovery.img additionally to your sdcard when you flash a new version.
[Desire Android Development] VekiCRO:
Hi

On the screenshots in the first post you can see informations about system,data and cache partitions but i can see only informations about sd-ext and sd card partitions?

I am running the latest version 2.2.6 RC4