yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] Scruffyo_0:
Cheers cooza... Done as suggested, no joy, then wiped, sucked, blowed, smeared with KJ, read stories, visted its family in Wisconsen, you know the drill - the ROM counter's on its first lap...

Now back on stock everything, Optus an all... as I recieved it...

Each time i'm rebooted and re-connected via USB/or Mains it's, 'Charging Paused... Battery not interested...'

I'm almost ready to hand in my PhD on Charging Paused-BTHOTL searches (CP..... searches don't fare too well...), from the well meaning forum evangelists (no offence cooza!) to the unemployable, slightly overweight and hirsute 37 year old WOW addicts who get their teminally bewildered mums to type... HAHAH...LOL SHUD AV GUT A IpHONE WINKER...

It's just broken isn't it...

Although there's a nagging doubt that having Tegrak/SetCPU & Random others competing for the various Kernels might have contributed to some NAN somewhere indescribable...

Back to the shop?

Whad'ya think?
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
mate if ya tried everything humanly possible,and a visit to its family would have set you back a few bucks too,I guess theres no other option but to send it back but ya gonna have to make sure the bin counter is re-set to 0 or the samsung spy foundation will know yourve been flashin.Gotta jig it.The worrying part is the IMEI problems though.Send it back.Ill send you mine while yours is in the shop:D
[Galaxy S II Q&A, Help & Troubleshooting] Scruffyo_0:
301Ω, pins 4&5... check!

What tickles me is there's another counter to count the number of times the ROM flashing counter has been reset, ...makes me like the S2 even more!

Next issue, in an ideal world, given that the phone is insured... will Optus just replace the box - I don't hold out much hope! ;)
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
theyve got everything cover mate.Big brother is watchin:cool: and he dont wanna fix something for nothin if he can help it:D
[HTC Desire S] swordlink:
Hi guys..

"just check again in fastboot, ENG HBOOT version has changed to 6.98.2000 iirc. After running the RUU it should be 0.98.0000 again as ENG HBOOT can be overwritten in contrast to the AlphaRevX HBOOT. If you only want ENG HBOOT don't flash the RUU obviously"

This is what I read over at the thread on how to restore to default Rom and s-on...

But I don't get it...

I am currently on hboot 6.xxxxx and have the latest virtuous unity Rom installed.

I want to return to stock Europe Rom and the update to the latest sense 3 its from HTC. I don't want custom ROM anymore ;) Which hboot do I need to flash? Can I flash the enghboot over my curent alpharevx hboot? Is there a risk of bricking? thanks
[HTC Desire S] amidabuddha:
Just flash the coresponding RUU it will bring everything to stock, including hboot.

If the 6.xx.xxxx hboot really cannot be overwritten then flash this HBOOT

reboot to fastboot with debbuging ON

connect to PC

extract the hboot from the archive

rename it to hboot.img

open cmd

go to the folder where you have fastboot executable (android-sdk\...)

put the hboot there

type

fastboot devices

if the device is listed type

fastboot flash hboot hboot.img
fastboot reboot-bootloader

check the new version it has to be 0.98.2000

start your RUU on the PC
[HTC Desire S] swordlink:
Wow thanks! +1
[HTC Desire S] oLf06:
tried this and got :

sending 'hboot' (1024 KB)...

OKAY [ 0.210s]

writing 'hboot'...

(bootloader) image update is bypassed!

OKAY [ 0.016s]

finished. total time: 0.226s

and my phone says : can not roll back hboot

my hboot version is 6.98.1002

i tried your guide through fastboot usb mode.

what am i doing wrong ? sorry for being noob or talking bad english :/
[HTC Desire S] amidabuddha:
It seems that your bootloader cannot be downgraded to the old version. So try to flash this one. Flash only the hboot.img, not the kernel and lib images that are in the same zip in this thread. I flashed a RUU on it without a problem. Let me know is it working :)
[HTC Desire S] oLf06:
so i dont need to do the nandroid backup, just flash the hboot.img as described above?
[HTC Desire S] amidabuddha:
yes make a backup of course it will not harm :) You have to do backup before every eventually dangerous alteration of your system
[HTC Desire S] oLf06:
okay... didnt made a backup ( because im not able to / different error, dont mind ) but i flashed the hboot.img from the thread using the above method. same output on my phone and in cmd. "(bootloader) image update is bypassed! " etc....
[HTC Desire S] amidabuddha:
Hey what errors?

Can you please explain, because the thread opener was asking for a guidance to return to stock. He has no errors and my method is for him.

If you have different situation please explain in details before doing anything on you device...
[HTC Desire S] oLf06:
My problem is that i have the eMMc error :

E:cant mount cache etc....

i made the test and got no errors so the chip is not broken.

now i tried your method :

mke2fs /dev/block/mmcblk0p27

reboot recovery

. that runs without erros but clockwork still says "e:cant mount ..."

now i wanted to flash the hboot to 0.98 so i can use RUU ( with my hboot version it gets stuck at " restarting bootloader" or something like that.

But i am still not able to do that.

I spend the last 2 hours trying to flash the 4extrecovery without any success :/ can't flash with OneClick, installing the zip through recovery runs without errors but dont take effect. and the last 10 minutes i am watching the cmd window because i tried to flash the recovery using fastboot flash all i get is " writing 'recovery' "

edit: i am able to install a new rom ( virtous unity ) but my phone still stucks at the white HTC screen
[HTC Desire S] amidabuddha:
do you have output on adb command? Try to flash the 2.00.2002 bootloader like in the linked thread I gave you above

EDIT: when you run the RUU there is a temp folder created on your C: drive. Open the Windows Explorer and search for the file rom.zip. Copy the file to another location. Extract it and try to flash the hboot included there
[HTC Desire S] oLf06:
tried to flash the hboot from RUU ... still getting :

sending 'hboot' (1024 KB)...

OKAY [ 0.199s]

writing 'hboot'...

(bootloader) image update is bypassed!

OKAY [ 0.029s]

finished. total time: 0.287s
[HTC Desire S] amidabuddha:
have you tried the adb command shell from recovery???

a) copy STOCK hboot.img from RUU to sdcard

b)reboot into recovery

b1)In cmd run the following commands (after each command press enter):

adb devices

adb shell

su

c)backup your hboot dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img

d) flash new hboot dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

reboot to hboot and check your hboot version
[HTC Desire S] oLf06:
tried this method and getting:

~ # dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img

dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img

2048+0 records in

2048+0 records out

1048576 bytes (1.0MB) copied, 0.034664 seconds, 28.8MB/s

~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

2048+0 records in

2048+0 records out

1048576 bytes (1.0MB) copied, 10.633719 seconds, 96.3KB/s

got this hboot.img from "RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe"

hboot version still : 6.98.1002

edit : i cannot flash the 2.00.2002 bootloader like in the link you gave me because according to the instructions i have to make a nandroid backup. this is not possible for me because of the error " cant mount/data" . I cannot find this error at google.

sorry for my bad english by the way.....
[HTC Desire S] amidabuddha:
It seems that your partition table is messed up and the system cannot find the necessary partitions. A bit dangerous suggestion but maybe you can try skipping the backup. And the RUU that you are using is quite old, try the 1.47.401.4 - it worked for me
[HTC Desire S] Eclipse_Droid:
format ALL your partitions in recovery.

Then go here http://xdaforums.com/showthread.php?t=1113820

download the PG88IMG file from the 1st post.

open it on your pc and extract the hboot.img file to your desktop, then copy it to the root of your sd card.

connect phone vie adb again and enter the following commands, after each line press enter!

adb shell su

adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img

adb shell dd if=/data/local/tmp/hboot.img of=/dev/block/mmcblk0p18

adb reboot bootloader

Then you are on OLD ENG HBOOT!:D
[HTC Desire S] oLf06:
sorry about this noob question but what do you mean with ALL my partitions ?

wipe data/factory reset ?

wipe cache partition ?

format /cache ?

format /data ?

format /sdcard ?

format /system ?

should i do everything i mentioned above or am i missing something ?
[HTC Desire S] Eclipse_Droid:
format in this order,

system

data

cache

then select wipe data factory reset.

then follow the rest of my guide;)
[HTC Desire S] oLf06:
on some point this starts to be personal...

error formatting /system

error formatting /data

error formatting/cache

now i am making the factory reset,

trying to flash the hboot tomorrow.... but dont have much hope :/ Thank you guys for now for your great help ... maybe you have some more hints for me ..:)
[HTC Desire S] oLf06:
general question here.. i am typing the commands when i am in recovery ( clockwork ) because this is how i can see my device when i type " adb devices " .. is this right or am i doing something generally wrong ?

EDIT:

am i right that this doenst make sense ? because "/data/local/tmp/hboot.img" doenst exist?

however ... it is not working again :(

EDIT 2 : okay.. i searched a bit on google and found out that there is a hboot driver i didnt install .. but my device still cant get listed... dont know why... maybe because usb debugging is not enabled ? how do i enable it in bootloadeR?
[HTC Desire S] amidabuddha:
yes adb from recovery. you should have the device listed after command

adb devices

but not /data/temp, it is:

dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

before that you must copy the hboot.img to the root of the sdcard
[HTC Desire S] oLf06:
already done that... no effect :(

am i missing something ? am i doing something terribly wrong ?
[HTC Desire S] amidabuddha:
Ok, lets do some diagnosis here:

reboot to Recovery

connect to PC

type "adb devices" in the cmd

the output has to be |some numbers and letters| device

type "adb shell"

type "su"

type "cat /proc/emmc

paste the output here

type "cat /proc/partitions

paste the output here
[HTC Desire S] swordlink:
1. I have got the same hboot like you

2. It worked using the described method

3. You have to wait few minutes after installing a custum rom, so the system prepares the necessary files to run the new firmware... Just flash and after the splash screen comes up, make a cup of coffe and wait a bit ;)
[HTC Desire S] oLf06:
type "adb devices" in the cmd

the output has to be |some numbers and letters| device

C:\Users\oLf\tools>adb devices
List of devices attached
HT17CTJ01958 recovery

type "adb shell"

C:\Users\oLf\tools>adb shell
~ #

type "su"

~ # su
su
/sbin/sh: su: not found

type "cat /proc/emmc

paste the output here

~ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p27: 12bffe00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p28: 014bfe00 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"

type "cat /proc/partitions

paste the output here

~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 2202624 mmcblk0
179 1 500 mmcblk0p1
179 2 64 mmcblk0p2
179 3 4500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 30000 mmcblk0p5
179 6 12500 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 8751 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 8957 mmcblk0p16
179 17 256 mmcblk0p17
179 18 1024 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1280 mmcblk0p20
179 21 8701 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 256 mmcblk0p23
179 24 2047 mmcblk0p24
179 25 571391 mmcblk0p25
179 26 1203199 mmcblk0p26
179 27 307199 mmcblk0p27
179 28 20480 mmcblk0p28
179 64 7875584 mmcblk1
179 65 7871488 mmcblk1p1

thats it... typed those commands after going into recovery.
[HTC Desire S] Tectas:
Maybe a dump question, but are the partitions mounted?

Swyped from my Desire S
[HTC Desire S] amidabuddha:
Thanks for the results. Tectas is right.

Paste the output of the command in the adb shell

df

After a couple of hours I will be at home and I will look through the outputs carefully.
[HTC Desire S] oLf06:
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 313088 32 313056 0% /dev
[HTC Desire S] Tectas:
What happens if you try to mount /sdcard?

You mount it by typing mount /sdcard.

Or try mount /dev/block/mmcblk1p1 /sdcard if the first command failes.

After that type df and post the result or the failures from the commands if there are any, pls.

You could also try the same with /data.

At the first command just replace /sdcard with /data and at the second command you have to replace mmcblk1p1 with mmcblk0p26 and /sdcard with /data.
[HTC Desire S] oLf06:
here is what i've done :

~ # mount /sdcard
mount /sdcard
~ # mount /data
mount /data
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
~ # mount /dev/block/mmcblk1p1 /sdcard
mount /dev/block/mmcblk1p1 /sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Device or resource busy
~ # mount /dev/block/mmcblk0p26 /data
mount /dev/block/mmcblk0p26 /data
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
[HTC Desire S] amidabuddha:
Sorry man but I give up.

It seems to me that your internal memory is gone but I cannot say for sure. Hope somebody else can. Bring it for a repair and hope that it will be covered by your warranty....sorry
[HTC Desire S] Tectas:
Internal memory can't be gone, there would be no recovery, but it looks like you messed up your /data image.

pls try this in adb shell.

cd /dev/block

ls

and post the output.
[HTC Desire S] oLf06:
first of all: thank you amidabuddha .. i really appreciate you tried to help me !!! tank you very much..

Tectas : here you go .. hope you can give me some good news :)

~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop6 mmcblk0p12 mmcblk0p18 mmcblk0p23 mmcblk0p3 mmcblk0p
9
loop1 loop7 mmcblk0p13 mmcblk0p19 mmcblk0p24 mmcblk0p4 mmcblk1
loop2 mmcblk0 mmcblk0p14 mmcblk0p2 mmcblk0p25 mmcblk0p5 mmcblk1p
1
loop3 mmcblk0p1 mmcblk0p15 mmcblk0p20 mmcblk0p26 mmcblk0p6 platform

loop4 mmcblk0p10 mmcblk0p16 mmcblk0p21 mmcblk0p27 mmcblk0p7
loop5 mmcblk0p11 mmcblk0p17 mmcblk0p22 mmcblk0p28 mmcblk0p8
[HTC Desire S] Tectas:
Ok there everything looks fine.

I'm building an data.img file from my /dev/block/mmcblk0p26 but it has a bit more than 1 gb. This will take some time.

When you got this image you could try to flash it like the hboot with

dd if=/sdcard/data.img of=/dev/block/mmcblk0p26.

After that go back to recovery and restore an backup, wipe cache and dalvikcache and if we're lucky it works^^

But my next prob is that I have to look somewhere to get webspace where I can give it to you.

Cause of this the earliest time I could give it to you would be tomorrow evening.

Would be nice if someone that allready has the space and a fast internet connection could lend me a hand^^

But I also have to say that we can try this, but there's no security that it works, it's only a suggestion of me.
[HTC Desire S] oLf06:
thank you very much !! you could upload it to rapidshare :)

which backup do you mean ? and if i got your image... first wipe caches or first restore the backup ?
[HTC Desire S] Tectas:
An nandroid backup of your rom or you can also flash a new rom instead.

It doesn't really matter, cause you shouldn't reboot in between, but to be sure first wipe then restore^^

Oh and maybe make an factory reset also.
[HTC Desire S] amidabuddha:
register @ DropBox. You will have 2 GB of free space...then copy your file to the Public folder and you can take a public download link for sharing
[HTC Desire S] Tectas:
Unfortunately the max filesize is limited to 180mb at dropbox ;)

I will try RapidShare or mediafire.

Thx anyway^^

Swyped from my Desire S
[HTC Desire S] oLf06:
I am a bit afraid that, if you are wrong and it does not work, my phone is bricked forever ( if it is not already ) , could this be possible ?

Are those partition problems the reason why i can not flash a new hboot ?
[HTC Desire S] Tectas:
Here is the file data.img

The procedure isn't different to the procedure you wanted to use to update hboot, the only difference is the size of the image.

Before I took the image I made a factory reset, cause of this it should be an clean image, but to be sure i would recommend you to make one more reset after flashing the image.

For sure there is a chance to brick it, but in which case inside this forum there is no chance^^

The partition problems can affect the hboot, but i'm a little bit confused cause you allready changed it within this command

~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

2048+0 records in

2048+0 records out

1048576 bytes (1.0MB) copied, 10.633719 seconds, 96.3KB/s

maybe your image where an already s-offed.

Edit:

Ok dropbox has only a sizelimit within the mobile version (180mb) and the webpage (300mb), at the desktopapp not, sry.
[HTC Desire S] oLf06:
Okay just to be sure again ..

1.I make a factory reset and wipe everything i am able to .

2.I flash the image just like i would flash a hboot.img

" dd if=/sdcard/data.img of=/dev/block/mmcblk0p26. "

3. I flash a new rom ( which would be virtous unity propably )

what dou you mean with " one or more reset after flashing the image " ?

and.. yes my image is already s-offed... this is why i cannot use my warranty because when you boot into bootloader there is the word " REVOLUTIONARY " on top.

but i can't flash another hboot image.. dont know why any method does not seem to take effect.
[HTC Desire S] Tectas:
To put the things in order:

1.I flash the image just like i would flash a hboot.img

" dd if=/sdcard/data.img of=/dev/block/mmcblk0p26. "

2.I make a factory reset and wipe everything i am able to .

3. I flash a new rom ( which would be virtous unity propably )

If we can't get it working, you could try to mess up your hboot also ;), maybe then you get warranty^^

But maybe you also could get it without changing the hboot, cause there are some fried emmc chips out there who got warranty despite the fact their devices where s-off.

The reason was a hardware failure that got nothing to do with the software changes.

Maybe that's the reason why we can't revive it, but if the emmc chip is the reason I don't really understand why some parts work and others not, cause bad blocks are somehow normal within an flashdrive, this it should handle and if it'S completly dead the recovery shouldn't work also or am I wrong.

Anyway lets try it and maybe that's the solution, if not we think about what we could do next.

I meant that the data.img should be clean, but to be sure you could wipe it one more time, but with this order there's no need for it.
[HTC Desire S] oLf06:
..... this sounds ... not that good
[HTC Desire S] Tectas:
Calm down, it would be the last option, lets try this and look what's coming up next ;)
[HTC Desire S] amidabuddha:
Completely agree, but I do not know the solution unfortunately...Good luck
[HTC Desire S] escape21:
First of all you cannot use fastboot flash hboot hboot.img because revolutionary hboot version is 6.xxx and you’re trying tu UPDATE with a inferior version, because of that you need dd commands.

After I have read entire post, I think that in all you’re attempts never used the stock hboot.

This is the stock hboot

You know the rest, copy stock hboot (see attachment) to the root of the sdcard

While in recovery

dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

reboot bootloader

One more thing, your HTC is branded? If NO it is ok, if it is branded I really don’t suggest proceeding with the steps above, it might work but …
[HTC Desire S] Tectas:
Sry but he tried to use the dd command before to change hboot.

Why he shouldn't change his data partition cause of branding?

At data is only the userdata stored and it looks like it's corrupted, without chance to format, cause of this the best bet would be to replace it with a clean and working image or not?

Swyped from my Desire S
[HTC Desire S] oLf06:
doing this for about 2 and a half hours now ...this is bad ,right ?

should i restart ? plug the battery out .. ? the phone is not freezed ...

~ # dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
dd if=/sdcard/data.img of=/dev/block/mmcblk0p26

i am able to type something in cmd oO i am a bit afraid...
[HTC Desire S] amidabuddha:
It seems to me that not only the /data is a problem...

Sent from my HTC Desire S
[HTC Desire S] Tectas:
Yes but before he wrote that he couldn't backup cause of /data maybe a newly flash of a ROM solves the system problem, I don't know, but I hope so^^

Swyped from my Desire S
[HTC Desire S] oLf06:
i could try the method of escape21 ... but first i need to know what to do with my "command without response "
[HTC Desire S] Tectas:
It's an big image and if your sd isn't the fastest it could last long.

Response is showing up when it's done.

What do you mean with that you can type in the command?

Swyped from my Desire S
[HTC Desire S] oLf06:
okay... i am trying to describe that :

i typed in my command which you see above ...

now the " cmd cursor " is blinking under this command and i can type something in .

i dont think its important .. dont mind that... i just have to wait for a response...
[HTC Desire S] Tectas:
Ok that's ordinary.

Swyped from my Desire S
[HTC Desire S] escape21:
I was not referring to data partition, your method its fine indeed; I was talking about his hboot.

In my opinion if he can reverse to stock hboot then after running the RUU_WWE… all partitions are created/formatted
[HTC Desire S] oLf06:
yes escape this was what i tried to do first... but i thought this would not be possible.. i try your method after the command has finished

@Tectas : When can i start to get worried because of the time it takes?
[HTC Desire S] escape21:
As Tectas said, if sdcard is slow then maybe 2 hours is not enough.

Regarding pulling out the battery you may fry the chip; instead you can open another cmd (terminal) adb device

adb shell

# reboot bootloader

but maybe it will be best to wait a little more, and in the mean time you get lucky and have a full operational data partition
[HTC Desire S] oLf06:
ye... if i never pulled out the battery i wouldnt write that down right now.. it is 3 hours now .....
[HTC Desire S] Tectas:
Ok, I never played with ruu sry, I didn't new that :)

But if the partitions are newly build you could reboot your device and try the other solution, if it doesn't solve your problem you still can try mine^^

Swyped from my Desire S
[HTC Desire S] oLf06:
finally... now factory reset and wipe...

dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
2406399+0 records in
2406399+0 records out
1232076288 bytes (1.1GB) copied, 13037.834759 seconds, 92.3KB/s
[HTC Desire S] amidabuddha:
hey we have a step further! thats great! I keep my fingers crossed
[HTC Desire S] Tectas:
Is it know possible to mount /data?

Swyped from my Desire S
[HTC Desire S] Tectas:
OK I think he tries the solution of escape21^^

Swyped from my Desire S
[HTC Desire S] amidabuddha:
I hope it works. Actually we have tried the RUU hboot, but only via fastboot, not dd in shell...

Sent from my HTC Desire S
[HTC Desire S] Tectas:
Or he kicked his device out of the window :D

---------- Post added at 08:22 PM ---------- Previous post was at 07:44 PM ----------

ok no i'm getting a little bit nervos, doesn't look good :(
[HTC Desire S] amidabuddha:
Or maybe celebrating. I am eager to know as well...