Related
Hi
Ive been trying all day to get this phone working properly, recently I s-off-ed my phone using alpharev, I attempted to flash the sensation rom which gave me a sdcard error cant mount mmcblk1 sdcard no such file....(mmcqblk0) ect... I fixed this with the fastboot enable command although I still cannot mount my sd either in recovery or when booted. I do have access to fastboot.
I flashed the new reflex rom 2.0.1 which works fine but when I make a call it drops, if I call tmobile it will drop the call, if I call again immediately after it continues with the call as if I'd never disconnected, if I call my partner the call is still connected at her end but if I call her again it just starts a new call and the other line is kept on hold....Wierd, Stranger still is that if I put the phone on speaker it does not disconnect, however if I turned speaker off and put the phone to my ear it disconnects after 10 seconds max.
Ive also tried this without the speaker on and away from my ear and it seems to stay connected, so this happening when I put my phone to my ear?
I dont think this is a technical issue as when I restored my phone to miui rom I had some months ago I was able to make calls without a problem although the signal was bad and it cut out if I moved too much but stayed connected more or less
Any Idea
So I tried re-partitioning my sd changing ext from 4 to 3 and back again, changing radio though I have only tried one, changing ril I have tried 3 of these, I cant make an goldcard because the although I have fastboot I cannot get adb to work, none of the apps for making goldcards detect my phone so I cant flash a new hboot or go back to stock, I am completely lost with this situation, can anyone help?
A while back I have had the same issue with line dropping as soon I put the phone to my ear. Your problem may be different, but maybe my findings will help you too.
I had an app installed, I think it was "Superpower" installed. It manages various settings for power saving, under which a setting for disabling things as soon as the screen turns off.
In my case this was the problem. Because as soon as you put the phone to your ear, the proximity sensor shuts down the screen automatically.
So then the app closed all connections, see? I uninstalled Superpower and it was OK again.
Maybe something similar in your situation, but it could be totally different as well..
Hope it helps!
ried uninstalling some likley coulprits to no avail i'm afraid, I am having trouble sorting out the usb brick I thought if I could get that working I might be able to resolve whatever is wrong, when I enter fastboot oem boot all it is giving me is
>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT******18
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =456
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.17.05.08 androidboot.cid=T
(bootloader) -MOB005 androidboot.carrier=TMUK androidboot.mid=PB9920000 a
(bootloader) ndroidboot.keycaps=qwerty androidboot.mode=normal androidboo
(bootloader) t.serialno=3118 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:20437 msec
FAILED (status read failed (Too many links))
finished. total time: 4.786s
there is no infotag, googled this and there is no info on this?
try to enable bluetooth if it doesnt then i know what the problem is
reaper7881 said:
try to enable bluetooth if it doesnt then i know what the problem is
Click to expand...
Click to collapse
I can't enable Bluetooth never have I been so happy to see that.
Sent from my HTC Desire using XDA App
i think you have a corrupt misc partition so u need to flash a new 1
let me compile the files for your CID:T-MOB005
THEN ILL UPLOAD AND TELL U HOW TO FLASH
does your usb connectivity work properly
I can fastboot but can't mount SD I can flash from SD if I use a SD reader just can't mount from recovery or pc
If u give my something to flash I can flash it from SD recovery
Sent from my HTC Desire using XDA App
first do fastboot oem enablqxdm 0
then extract and copy the two files in this archive to ur sdcard http://www.mediafire.com/?5h5593mcoblaykq
then install terminal emulator
THIS FIX IS ONLY FOR PHONES THAT ARE TMOBILE BRANDED
CID:T-MOB005
DONT TRY ON OTHER BRANDED PHONES
Ok done what now
Sent from my HTC Desire using XDA App
delete the post will all the fastboot oem boot since ur serial is still in ther
(bootloader) t.serialno=HT here 8 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
omg come to this page bro. but when u do then
move both files to /data
then open terminal then type
su
chmod 755 /data/flash_image
Im afraid that has not worked, I'm totally stumped
you havent flashed it yet lol
if you have applied the permissions then
in terminal emulator
/data/flash_image misc /data/mtd0.img
re check ur typing to make sure
then reboot and try to enable bluetooth if it enables then were done
delete the post will all the fastboot oem boot since ur serial is still in ther
(bootloader) t.serialno=HT HERE 8 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
serial number needs deleting in red on ur other post
Ok thanks Bluetooth enables yet to check usb but thank u so much hope this solves my call drop problem
Sent from my HTC Desire using XDA App
no problem bro
reaper7881 said:
no problem bro
Click to expand...
Click to collapse
Cheers reaper much respect all problems gone just by fixing the usb brick apparently it affects radio
i think i have soved the dropping calls
http://www.mediafire.com/download.php?7453qbvf78f5l50 and do the same as before
After flashing RUU fails with
Hi,
I'm just trying to get my Desire back to stock so I can sell it but the RUU that I have used in the past has failed. I've run the downgrader and flashed the stock ROM from Alpharev but now when I try to re-apply the RUU I get the black HTC screen with 4 warning triangles in the corners of the screen. If remove the USB an dreconnect then I get this....
---Alpharev----
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNW101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
RUU
1 Bootloader - Bypassed
2 Radio V2 - FAIL-PU
3 RADIO CUST - OK
4 BOOT - OK
5 RECOVERY - OK
6 SYSTEM - OK
7 USERDATA - OK
8 SPLASH1 - OK
9 SPLASH2 - OK
Partition update fail!
Update fail!
If I run fastboot oem boot then I get this...
C:\AndroidSDK\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is ORANG001
(bootloader) setting->cid::ORANG001
(bootloader) serial number: SH09DPL01345
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =423
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=O
(bootloader) RANG001 androidboot.carrier=ORANGE-UK androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=SH09DPL01345 androidboot.bootloader=6.93.100
(bootloader) 2 no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:423443 msec
FAILED (status read failed (Too many links))
finished. total time: 99.905s
I've got a gold card in. I'm not sure if I'm missing a partition or if my goldcard needs recreating. Oh, and I have tried various RUU's but no luck with any of them.
Does anyone have any ideas? Let me know if you need any more info.
Many thanks,
Baz
Did you flashed Stock Hboot partition table before downgrader?
I did bravo_downgrade.img followed by bravo_alphaspl.img and then the RUU.
Is there another one I have to do?
have you tried to run the RUU again while on the four-triangle-screen? that solved it for me.
Sent from my HTC Desire using xda premium
Don't open two threads about the same problem.
SwiftKeyed from CyanogenMod with Transparent XDA App
@Tillus - I had tried re-running the RUU but with no luck. I've also tried various other RUU's but can't get anything.
@MatDrOiD - Sorry, I think that's a forum screw-up because I was safely tucked up in bed at 12:48am. In response to your post on the other thread, I have flashed bravo_downgrade.img As far s I know that's the hboot downgrader, no?
Looks like a radio brick to me. You can try a,few things but you may end up contacting HTC
Sent from my HTC Desire using XDA App
I did bravo_downgrade.img followed by bravo_alphaspl.img and then the RUU.
Is there another one I have to do?
Click to expand...
Click to collapse
Why did you flash the stock after the downgrader?
First Flash the stock, then the downgrader.
That's why the bootloader is bypassed and radio can not be updated.
Exactly.
First you have to flash the partition table image, and then run the downgrader... if you do it backwards results might be unpredictable.
You do not have to flash stock, downgrader is enough. After downgrader run RUU and it will succeed.
Thanks Dave, I'll give that a go as soon as I've had a cup of tea. I did things that way round because I had an issue once before and someone said that was the way to fix it and it worked so this time I just did the same again. I'll get back to you and let you know how things went.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
OK, I flashed stock followed by the downgrader and then ran the RUU. My fault has changed to something that strikes me as being rather more serious. I have a feeling I was lead to the wrong RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) as after I ran this my screen went off and hasn't come back on at all so I'm thinking this might be a RUU for the led version of the Desire. Also I no longer have Super CID which seems to be preventing me from doing any further flashing. I'm just looking into reflashing misc to see if that might help.
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
RockyGothyBaz said:
OK, I flashed stock followed by the downgrader and then ran the RUU. My fault has changed to something that strikes me as being rather more serious. I have a feeling I was lead to the wrong RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) as after I ran this my screen went off and hasn't come back on at all so I'm thinking this might be a RUU for the led version of the Desire. Also I no longer have Super CID which seems to be preventing me from doing any further flashing. I'm just looking into reflashing misc to see if that might help.
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
Click to expand...
Click to collapse
why if you have dozen of ruu available, newbie always choice the damn old one??? U have to choice the damn last one! What wrong with the latest? How you can flash a such old ruu?
The next time, ask a confirmation before flash an ruu.
RockyGothyBaz said:
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
Click to expand...
Click to collapse
IF it boots into fastboot, you can flash a newer RUU, try the latest one, not one of the oldest
Hey guys,
I've also got a device from a mate who completely screwed it up. I also tried to flash the latest RUU but it failed.
My understanding is that with the device blocked at the HTC with 4 triangles boot, my only option is to use a Goldcard because of S-ON.
However my understanding is that to create a Goldcard you need to do this from your device whilst its working. Is it possible to create a goldcard without the device?
Thanks.
makcrellon said:
Hey guys,
I've also got a device from a mate who completely screwed it up. I also tried to flash the latest RUU but it failed.
My understanding is that with the device blocked at the HTC with 4 triangles boot, my only option is to use a Goldcard because of S-ON.
However my understanding is that to create a Goldcard you need to do this from your device whilst its working. Is it possible to create a goldcard without the device?
Thanks.
Click to expand...
Click to collapse
Read my thread.
hello, this desire is kicking my ass, 4 days not fixed? of trying and searching, can some one please help
was on orange,uk,htc branded dont know if was orange branded
tried several roms some they give error or just gets to black htc screen (waited) 30 min nothing
reboot loop after s-off ?
can flash this from gold card, shipped-roms.com/download.php?category=android&model=Bravo&file=OTA_Bravo_Froyrange_CH_2.22.71.4-2.22.71.2_releasevrnkzrd85wxshyvx.zip
but then just reboots continously
here is info i have
READING INFO: OK!
10:50:33 > MODEL: BRAVO / bravo
10:50:33 > VERSION: 0.5/None/0.93.0001
10:50:33 > FIRMWARE: 2.29.405.2/5.11.05.27
10:50:33 > HARDWARE: HBOOT-8x50
10:50:33 > HTC DESIRE READ INFO: END!
-----------------------------------------------------------------
C:\Users\POWERTECH 6000\AppData\Local\Android\android-sdk\platform-tools>fastboo
t oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT03PPL06282
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT03PPL06282 androidboot.bootloader=0.93.0001 no_c
(bootloader) onsole_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:56610 msec
FAILED (status read failed (Too many links))
finished. total time: 6.879s
which ruu can i use just want to factory or get going in anyway i also noticed bottom end of phone gets really warm sometimes ?
thanks
kammy6000 said:
hello, this desire is kicking my ass, 4 days not fixed? of trying and searching, can some one please help
was on orange,uk,htc branded dont know if was orange branded
tried several roms some they give error or just gets to black htc screen (waited) 30 min nothing
reboot loop after s-off ?
can flash this from gold card, shipped-roms.com/download.php?category=android&model=Bravo&file=OTA_Bravo_Froyrange_CH_2.22.71.4-2.22.71.2_releasevrnkzrd85wxshyvx.zip
but then just reboots continously
here is info i have
READING INFO: OK!
10:50:33 > MODEL: BRAVO / bravo
10:50:33 > VERSION: 0.5/None/0.93.0001
10:50:33 > FIRMWARE: 2.29.405.2/5.11.05.27
10:50:33 > HARDWARE: HBOOT-8x50
10:50:33 > HTC DESIRE READ INFO: END!
-----------------------------------------------------------------
C:\Users\POWERTECH 6000\AppData\Local\Android\android-sdk\platform-tools>fastboo
t oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT03PPL06282
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT03PPL06282 androidboot.bootloader=0.93.0001 no_c
(bootloader) onsole_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:56610 msec
FAILED (status read failed (Too many links))
finished. total time: 6.879s
which ruu can i use just want to factory or get going in anyway i also noticed bottom end of phone gets really warm sometimes ?
thanks
Click to expand...
Click to collapse
2.3 RUU.
desire
nlooooo said:
2.3 RUU.
Click to expand...
Click to collapse
hi thanks for help , i get error 155 ,please use correct update?
i am putting in fastboot to bypass battery low error!
is this incorrect?
i have s-off
hboot 0.93.001
thanks
kammy6000 said:
hi thanks for help , i get error 155 ,please use correct update?
i am putting in fastboot to bypass battery low error!
is this incorrect?
i have s-off
hboot 0.93.001
thanks
Click to expand...
Click to collapse
You cannot ruu while s-off is there. Make it S-ON and try aggain, but before making s-on flash a custom recovery. Just to be safe
desire
race55 said:
You cannot ruu while s-off is there. Make it S-ON and try aggain, but before making s-on flash a custom recovery. Just to be safe
Click to expand...
Click to collapse
thank you for telling me s must be on that why not work!
i tried to put recovery image bravo from clockwork from fastboot but no work cos i dont have eng boot i think,android flasher need eng boot aswell and i am not rooted
can you please tell me how to put s-off again please so i just factory
thanks
I'm not sure what are you talking about, what custom recovery before you do s-on?
The proper way to do that is to flash downgrade hboot from alpharev via fastboot and then run ruu.
Sent from my HTC Desire using Flashes and Thunders
desire
nlooooo said:
I'm not sure what are you talking about, what custom recovery before you do s-on?
The proper way to do that is to flash downgrade hboot from alpharev via fastboot and then run ruu.
Sent from my HTC Desire using Flashes and Thunders
Click to expand...
Click to collapse
ok sorry, phone was unlocked/ s off by, xtc clip
so no recovery installed!
i tried to write the image from alpharev website with fastboot commands i get starting recovery, then remote not allowed
C:\Users\ kammy\AppData\Local\Android\android-sdk\platform-tools>fastboo
t flash recovery bravo.img.img
sending 'recovery' (3256 KB)...
OKAY [ 0.485s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.502s
C:\Users\kammy\AppData\Local\Android\android-sdk\platform-tools>^A
how can i write the new img please, i am not very good with htc
thanks
kammy6000 said:
ok sorry, phone was unlocked/ s off by, xtc clip
so no recovery installed!
i tried to write the image from alpharev website with fastboot commands i get starting recovery, then remote not allowed
C:\Users\ kammy\AppData\Local\Android\android-sdk\platform-tools>fastboo
t flash recovery bravo.img.img
sending 'recovery' (3256 KB)...
OKAY [ 0.485s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.502s
C:\Users\kammy\AppData\Local\Android\android-sdk\platform-tools>^A
how can i write the new img please, i am not very good with htc
thanks
Click to expand...
Click to collapse
nlooooo ment flash Alpharev downgrader.img then run 2.3 ruu
Sent from my HTC Desire
desire
jmcclue said:
nlooooo ment flash Alpharev downgrader.img then run 2.3 ruu
Sent from my HTC Desire
Click to expand...
Click to collapse
can you tell me how to do that i thought it was through the run fastboot commands (i get errors) is there another way from sd card or something
or is there a exe file? sorry for noob q's
ok do i burn the alpharev iso to disk then boot from it then install new img to phone from the program?
thanks
As I understood you got s-off via htc site?
Then you don't have access to radio and hboot partitions only to recovery, system and data so it's not allowed to flash hboot via fastboot.
You can flash recovery from here:
http://www.clockworkmod.com/rommanager/
download proper recovery.img and flash it via fastboot. You have to type the path correctly to the space where you stored it, ie:
fastboot flash recovery c:\recovery.img
Then go here:
http://forum.xda-developers.com/showthread.php?t=809328
find and flash a rom of your choice. These are custom roms and are flashable from recovery (install zip from sd card command).
desire
nlooooo said:
As I understood you got s-off via htc site?
Then you don't have access to radio and hboot partitions only to recovery, system and data so it's not allowed to flash hboot via fastboot.
You can flash recovery from here:
http://www.clockworkmod.com/rommanager/
download proper recovery.img and flash it via fastboot. You have to type the path correctly to the space where you stored it, ie:
fastboot flash recovery c:\recovery.img
Then go here:
http://forum.xda-developers.com/showthread.php?t=809328
find and flash a rom of your choice. These are custom roms and are flashable from recovery (install zip from sd card command).
Click to expand...
Click to collapse
ok thats straight forward, and i followed it but why does it keep saying ,remote not allowed failed!
i have phone in usb displaying fastboot usb is highlighted!
users\kammy\appdata\local\android\android-sdk\platform-tools\fastboot
i dont get it,why the error
thanks very much
I didn't know what's xtc clip, now I found out and I'm sure that something failed in that process cause have s-off on your device but you actually don't have it cause you can't run fastboot commands. Sorry...
desire
nlooooo said:
I didn't know what's xtc clip, now I found out and I'm sure that something failed in that process cause have s-off on your device but you actually don't have it cause you can't run fastboot commands. Sorry...
Click to expand...
Click to collapse
ok thanks everyone for help, but i will be back with results
kammy6000 said:
ok thanks everyone for help, but i will be back with results
Click to expand...
Click to collapse
ok so now i have recovery clockwork installed i think ,i am able to install a custom rom , cyanogen , then it just crashes at the
load screen the screen goes all fuzzy or it looks like its loading but not going through the whole process
is this lcd,amoled issue?
or something else i am really close but what is stopping it loading
thanks
kammy6000 said:
ok so now i have recovery clockwork installed i think ,i am able to install a custom rom , cyanogen , then it just crashes at the
load screen the screen goes all fuzzy or it looks like its loading but not going through the whole process
is this lcd,amoled issue?
or something else i am really close but what is stopping it loading
thanks
Click to expand...
Click to collapse
ok now i have alpharev hboot cm7, but all roms just crash is there specific roms only please help me
kammy6000 said:
ok now i have alpharev hboot cm7, but all roms just crash is there specific roms only please help me
Click to expand...
Click to collapse
Here you go, just search the thread, for every rom it is written if it's cm7 hboot compatible.
http://forum.xda-developers.com/showthread.php?t=809328
Hello,
I have Desire Z. My cousin gave me to fix it. When I start to power on phone stucks on HTC Logo. When I try to run recovery I got phone with green arrows on display (some kind of download mode) and after 10 secs screen goes black and phone vibrates 5 times. How can I fix it?
http://forum.xda-developers.com/showthread.php?p=44244909
In here you will find necessary links and instruction on how to post in this forum to get appropriate help, once you read through the appropriate threads you will know how to fix it or know how/where best to post, let me know if you're still confused
Sent from my Nexus 7 using Tapatalk 2
I didn't find anything for me. I tried to update via .img file but it stucks on BOOTLOADER - Updating.
In particular I meant to give as much information as possible about your phone, there is clear instruction on how/where/what to post. I'm not trying to be a jerk here but without getting as much info as possible I or anyone else can't help much.
So if you can write down all info from bootloader, describe what you have tried in detail, read a few of the many many threads about bricked phones and post question in a relevant thread rather than creating yet another, when all solar questions are in similar threads there is far less for others to sift through to find answers to their dilemmas
There is a thread specifically devoted to bricked phones in that link, how to troubleshoot and how to ask for help
I don't mind helping at all, rather enjoy it, but I need info and you also should show you are researching and trying rather than just saying help
Sent from my Nexus 4 using Tapatalk 2
I see your point. I searched for solution but most of guides shows how to unbrick ROOTed phone. Mine is S-ON so it's not rooted.
Bootloader:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-BOOT
Apr 11 2011, 23:36:27
HBOOT
Unfortunately your not finding these guides because there is very little you can do at this point with an unrooted phone. You'll need to go to HTCs website and download the latest ruu, there is full instructions there how to run it. You will also need to get fastboot installed on your pc
Sent from my Nexus 4 using Tapatalk 2
But on Polish HTC website I can't download any RUU. HTC has stopped to publish RUU's for HTC's. I download this RUU: RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_12.56.60.25_26.10.04.03_M_release_224299_signed . I think it's lastest - I couldn't find anything newer.
Try here
http://www.androidruu.com/index.php?developer=Vision
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Try here
http://www.androidruu.com/index.php?developer=Vision
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
As I said before - I got the newest RUU: RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_ 12.56.60.25_26.10.04.03_M_release_224299_signed . I extracted rom.zip , changed name into PC10IMG and copied it to root of my SDCARD. Update stucks on Bootloader - updating.
Try booting into ruu mode and flashing it that way
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Try booting into ruu mode and flashing it that way
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
How can I boot into ruu mode? I tried to update via ruu when phone is in fastboot mode. Installation stucks on wait for bootloader.
Also I found something strange:
RUU is 2.42.405.3
and currently on phone I have 2.42.405.4 . I can't find this RUU.
When I'm trying to do "fastboot oem boot" I got:
C:\Android\Tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25202
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number: SH19PRT01523
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =504
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=HTC__032 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-EastEurope androidboot.mid=PC1011000 android
(bootloader) boot.keycaps=qwerty androidboot.mode=normal androidboot.seri
(bootloader) alno=SH19PRT01523 androidboot.bootloader=0.85.0013 zygote_on
(bootloader) eshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:517509 msec
FAILED (status read failed (Too many links))
finished. total time: 8.148s
The .04 is the newest, see the link I sent. Being your not rooted and have all security flags on there is little you can do.
the command is
fastboot oem rebootRUU
fastboot flash update nameofupdate.zip
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
The .04 is the newest, see the link I sent. Being your not rooted and have all security flags on there is little you can do.
the command is
fastboot oem rebootRUU
fastboot flash update nameofupdate.zip
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I can't find .04 . I tried to search before I posted but my search wasn't successful. I found zip based od .04 but it is CustomROM. If I checked corrently .04 is OTA. So how should I update via RUU when there is no such file?
Let my ask one more question: is there is any way to use ADB on my phone? Reboot in ADB Mode or sth?
It looks like you're right there, that was never released as an ruu, but if my memory serves me correctly, without super CID you can only flash newer RUUs anyway, your phone won't take an update unless its newer, not older or even the same.
This means there is no newer ruu and less likely a chance to resurrect your phone.
adb is a bridge between phone and PC and is to be used when booted to os, or custom recovery. Being you can't do either you can't use adb.
Try going to freenode irc #G2ROOT to get some real time help but I'm thinking this phone is helpless
Sent from my Nexus 4 using Tapatalk 2
Auto-information on this irc said that perm-root is achieved and the channel will be closed. U sure I will get help there?
BTW: Do u think that XTC-Clip can help me?
Fried mmc maybe, i had the same probleem with an unrooted Desire Z, if the phone is not older as 2 years contact HTC they will replace the Phone by a new one.
I have tried many things but nothing worked, I phoned to HTC and after 2 weeks i got a new Desire Z.
Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Answer me this quickly, if you have a Vodafone, S-ON, why on God's green earth would you flash a RUU for T-Mobile US?
arnasx69 said:
Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Flash a custom ROM. Put the firmware and gapps on your sdcard.
I think he should just restore his phone to stock ROM after he flashed a custom ROM. If he doesn't know the difference between Vodafone and T-Mobile then I don't know... To make matters worst he knows he has no OS on his device and then he goes to try and lock the bootloader, in the hopes of achieving what?
Put a ROM on a SD card, flash it through custom recovery, download a stock ROM for your device from the Collection thread in General section. Restore the device back to stock and rather leave the flashing until you read up on the basics and get a better understanding of these things before you really mess up mate.
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
arnasx69 said:
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
Click to expand...
Click to collapse
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
RossMacgill said:
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
Click to expand...
Click to collapse
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
RossMacgill said:
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
Click to expand...
Click to collapse
Also, your MID (model id) and CID must match the firmware you are flashing since you are not S-off, and therefore not superCID.
In fastboot and hooked up to your PC in ADB, type fastboot getvar all. The output it gives you will tell you your CID and MID(modelid).
Then look for firmware that matches those.
Or get S-off with sunshine (best $25 you will spend on your phone), and go superCID to flash firmware from any carrier.
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Gunman84 said:
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Click to expand...
Click to collapse
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
also éven if he would try on s-on a T-Mobile RUU von vodafone cid it would never work
if you really don't know how to Flash custom roms etc properly please Keep your phone stock!
If you got the stock Rom working i would go S-Off with Sunshine and go Super CID (11111111) with Sunshine.
Then you can flash what ever Rom you want.
arnasx69 said:
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
Click to expand...
Click to collapse
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Gunman84 said:
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Click to expand...
Click to collapse
Actually, CID is Carrier ID, not country identifier.. That's why his says VODAP001 (his carrier being Vodafone) and not his country (whichever of the 21 countries Vodafone is available in)
arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
Click to expand...
Click to collapse
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
ckpv5 said:
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
Click to expand...
Click to collapse
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
arnasx69 said:
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
Click to expand...
Click to collapse
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
One-M8-Master said:
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
Click to expand...
Click to collapse
Not true, not 100 %. Maybe V3 will do that. Keep in mind that the version of sunshine that is now on the market is not working with all the devices.