Hi.
Seems I bricked my Desire, but before I give up and send it to repairs I’m trying to get help from this forum.
To explain what happened:
First and most important thing: “’I’m an idiot”
Second – I had working InsertCoin 1.9.5 ROM installed (rooted phone with S-OFF. )
Occasionally I’m trying other Roms and this time I wanted to try 2.3 rom. During install process I checked some additional information and I run into topic regarding AlphaRev 1.8. –there was a recommendation to upgrade HBoot. So I did. Same time I upgraded Clockworkmod from 2.5.0.7 to 3.0.0.5
When Installed “PB99IMG_bravo_stock.zip” from Alpharev site this is when my problems started. (probably it was corrupted file. I dint check MD5Sum so this is probably why I’m an idiot.
When I found out that something is wrong I tried to restore backup but seems I’t worked partially. Actually when backup was restored I couldn’t switch off the phone – exit the screen. So I had to remove battery. Then I got stuck in AlhpaRev screen and only way to continue was to remove battery again and redo restore. I got everything work but started to disconnect few seconds after call was connected and phone did not connect with windows any more (when usb connected) it doesn’t show anything on the phone.
Now When tried to make advanced restore via Fastboot, I had problems to restore Boot. So I messed around with different options to restore boot without success and in the end only solution I could think of is to restore the phone to its original state. Backed up SD card and installed PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed file that I found (can be installed without windows). It installed correctly and my phone switched on (unrooted), can send emails and messages but still problems with connection (drops calls) and phone not recognizing usb connection still remained.
In bootloader my phone data is this:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
… long story.
But now is the question how I can root and or downgrade my phone if it’s not recognized by windows? When connecting via usb if in HBOOT mode everything ok (HBOOT USB PLUG).
I think that complete reinstall would fix connection problem, but how to reinstall + root without connection to pc, this is mystery for me.
So under windows 7
.. unrevoked doesn’t recognize a phone
… ruu installer doesn’t recognize a phone
…HTC sync doesn’t recognize a phone
…Phone doesn’t recognize usb connection in normal mode.
When picking “fastboot” in bootloader, phone will go to black screen with red triangle. Nothing happens.
Is there a way to root via bootloader or fastboot or anything… ?
Appreciate any help here.
Thanks.
First of all.. Why oh why did you flash a stock s-on bootloader... It makes everything so much more complicated.
Second are you sure the black screen with the red triangle comes up when you choose fastboot and not when you choose recovery, because it is the recovery.
Third it sounds exactly like your problem is similar to those with usb-brick. This means your misc partition is corrupted, so you will need to flash a new one(this would have been a piece of cake if you hadn't flashed the ruu with stock hboot).
thanks for the quick reply,
well... at this point i have understood this is going to be complicated... Im actually not home but on a business trip without a phone connection - so if not anything else, this will be good lesson for the future to read all the instructions carefully... '
but anyway... regarding red triangle... you are right as this is recovery and I have found how to enter android system recovery menu: "volume up +power"
so as I understand from your post I need to flash new partition... any directions?
Well year i'll try to find some instructions for you, and i might be able to help you do it on pm, but it involves editing a std. misc.img file with your cid and flash it.
The tough part is the flashing, as this is not possible without root. Had you not run the "PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49 .00.32U_5.11.05.27_release_151783_signed" it would have taken 30 seconds, but now you are unrootet, so you will need to use an exploit to gain temporary root in order to flash the misc.img from a terminal emulator. You will also need access to putting files on the sd-card(sd-card reader or dropbox as you dont have usb-connection)
Edit: First boot into fastboot and connect it to your pc. From here you need fastboot.exe from the android sdk. Then you run "fastboot oem boot" and take note of the CID you get in the console.
edit 2: here is the full guide:
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usbbrick
You will need to do somethings different, as you don't have root, but i might be able to guide you thrugh it.
...ran fastboot oem boot , this is what I got:
C:\android\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A0D
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT09HPL05298
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =428
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
INFOTC__032 androidboot.carrier=HTC-EastEurope androidboot.mid=P
INFOB9920000 androidboot.keycaps=qwerty androidboot.mode=normal
INFOandroidboot.serialno=HT09HPL05298 androidboot.bootloader=0.9
INFO3.0001 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:36923 msec
FAILED (status read failed (Too many links))
finished. total time: 5.339s
Ok what you need is "HTC__032" Now you need to download the img file from the thread i linked and install a hex-editor. Then you can use the hex-editor to insert "HTC__032" into the img file instead of the one it came with.
After that you just need to flash it I can't help you on that until tomorrow though it's past midnight here.
To get temporary root try to get visionary+ app (not available from market) then look at USB brick thread in development section. I had a similar issue
Sent from my HTC Desire using XDA Premium App
mortenmhp said:
Ok what you need is "HTC__032" Now you need to download the img file from the thread i linked and install a hex-editor. Then you can use the hex-editor to insert "HTC__032" into the img file instead of the one it came with.
After that you just need to flash it I can't help you on that until tomorrow though it's past midnight here.
Click to expand...
Click to collapse
... stuck.
downloaded img file.
downloaded hex editor
changed img file line to HTC__032
now this guide you mentioned says:
3. Get flash_image from the attached files below
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
question is where is this "data" folder?
there is no this kind of folder on the SD card (should I create it?) , also there is no Data folder on Android sdk folder. I must missing something.
P.S. before flashing I probably need to run "fastboot oem enableqxdm 0" to enable SD card?
anyway... thanks now. Im going to sleep as well. tomorrow is a busy day, so I might not be able to watch this thread until later in the evening. lets keep fingers crossed that Ill fix this.
... good night.
abz54 said:
To get temporary root try to get visionary+ app (not available from market) then look at USB brick thread in development section. I had a similar issue
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
... got up now. Good morning
I have downloaded Visionary+ and tried temporary root. It seems it worked as superuser has created after reboot. However I will not proceed until next step is clear. Thanks a lot at the moment.
manager2a said:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'[/I]
question is where is this "data" folder?
Click to expand...
Click to collapse
The data folder is present on the phone's filesystem.
You should put the two files on the sdcard (not inside any folder) and then issue the commands in a terminal emulator on your phone.
Hi,
I had the same problem when my Misc partition got corrupted and I also flashed a RUU update which broke my SLCD screen as well (not to mention unrooting my phone).
So in the end I had a stock rom, unrooted phone which wasn't recognized by my laptop, unrevoked, adb etc.
Quanchi's guide : http://forum.xda-developers.com/showpost.php?p=9056719 helped solve my problem.
The rageagainstthecage exploit gives you temp root after which you can flash the correct mtd0.img for your phone from your SD card. All steps are outlined in that guide
This will solve your problems!
thanks a lot for the information.
I have downloaded this Rageagainstthecage and already modified mtd0.img earlier.
Ill try this later when I will have time and let you guys know if succeed.
manager2a said:
thanks a lot for the information.
I have downloaded this Rageagainstthecage and already modified mtd0.img earlier.
Ill try this later when I will have time and let you guys know if succeed.
Click to expand...
Click to collapse
You dont need to follow the rageinthecage method as that is another way of getting root, you should already have root through visionary+, so you only need to follow the methods on the usb-brick thread
just entered this command from emulator:
'cat /sdcard/flash_image > /data/flash_image'
got response : cannot create /data/flash_image: permission denied .
...damn need to run... back after few hours
manager2a said:
... got up now. Good morning
I have downloaded Visionary+ and tried temporary root. It seems it worked as superuser has created after reboot. However I will not proceed until next step is clear. Thanks a lot at the moment.
Click to expand...
Click to collapse
Downloaded the visionary+ APK??? Where did you place it? How and where did u execute it?
How do we get this terminal access? I understand that we need to move the image & mstd0 files to /data from /sdcard. But the problem is, I do not have any access to the file system on the phone of on the SD Card at this moment. The only access we have is the bootloader interface.
How did you manage to execute visionary+ (or any other terminal emulator or file manager) apk on your bricked phone?
Can you pl elaborate?
well bricked is not fully "bricked" as you read from the thread I have most of the functionality but problem is with dropping calls and no connections with PC. so everything can be instaled via market at the moment as I have no problem with internet connection.
for now I got USB connection back. wohoooo ...!!! Thanks to everybody who helpe me so far.
So one problem solved.
next plan would be to :
root again,
reinstall InsertCoin rom,
restore data from old nand backup.
... boarding plane right now, continuing after few hours...
Now I can say its done!
everything is back to normal like it was before.
In the end I
USB-Unbricked the phone
Rooted with Unrevoked3
Restored old rom and data.
only thing is Im currently S-ON. so I need to proceed with this issue as well.
Last remaining question: should I still retry to install new updated HBoot withAlpharev 1.8?
Related
This is my first Android phone and it is (was) awesome compared to my iPhone. And this site is an awesome source of info!! With that being said i think i bricked my phone or at I am missing a step or file somewhere along the way.
When I turn on my phone - it freezes at the HTC screen. (if i plug in the usb cord the device is found by windows and then drops and continues the cycle endlessly)
When I go into Hboot - I can see the phone via fastboot however I can not access the phone through ADB?? Nor can i get to the clockwork mod recovery screen.
HBOOT 0.79.0000 w/ 1.47.651.1 by calkulin
Radio 1.39.00.04.26
cid: SPCS_001
I had successfully rooted using Parts 1 & 2 by toastcfh (and i had flashed a ton of roms - so recovery did work successfully)
WHAT I HAVE TRIED SO FAR:
1. back to the basics and tried toastcfh's method again - "main version older"
2. fastboot - tried flashing images via fastboot - "signature check fail"
3. fastboot - fastboot erase - "FAILED (remote: not allowed)"
4. fastboot -supercid mode - "INFO[ERR] Command Error !!!!
5. revert back to OEM via RUU's - "ERROR[140]: BOOTLOADER VERSION ERROR"
I am putting phone into fastboot and then running executables
RUU_Supersonic_Sprint_1.06.651.4_Radio_1.20.00.03.09_146812.exe
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe
all failed same error message - and if i look at the ruu logs i get see the same error message "remote: 43 main version check fail"
Not sure if this is helpful - from fastboot oem boot - (FAILED (status read failed (Too many links)))??:
C:\sdk\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07DAEC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x23301
INFOTAG:hero panel = 0x1
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is SPCS_001
INFOsetting->cid::SPCS_001
INFOserial number: HT05NHL12163
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =493
INFOactive commandline: board_supersonic.disable_uart3=0 board_s
INFOupersonic.usb_h2w_sw=0 board_supersonic.disable_sdcard=0 dia
INFOg.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata
INFO_sel=0 androidboot.emmc=false androidboot.baseband=1.39.00.
INFO04.26 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_
INFObattery androidboot.carrier=COMMON androidboot.mid=PC3610000
INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb
INFOoot.serialno=HT05NHL12163 androidboot.bootloader=0.79.0000 n
INFOo_console_suspend=1 console=null
INFOaARM_Partion[0].name=wimax
INFOaARM_Partion[1].name=misc
INFOaARM_Partion[2].name=recovery
INFOaARM_Partion[3].name=boot
INFOaARM_Partion[4].name=system
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOpartition number=7
INFOValid partition num=7
INFOmpu_nand_acpu_rw D3E 2000
INFODelay 99998(us) for dpram command before goto AMSS...
INFOjump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:284665 msec
FAILED (status read failed (Too many links))
finished. total time: 7.225s
***
Where do i go next? Besides back to the sprint store to buy another EVO?
Thanks ahead of time!
You need to use one of the OTA root methods
Connect the phone to pc and try the command "adb reboot recovery". I had a similar issue, adb devices showed nothing but issuing that command somehow forced it back into my recovery.
lol... its tough to do an OTA update when my phone is stuck at HTC screen
adb doesnt work b/c android isnt loading: "error: device not found"
If you rooted using toast's method, then your hboot should be 0.76 not 79. What you can try is reflashing the pc36img.zip from toasts method. You can use/acquire a card reader to connect your sdcard up directly to your computer and copy the pc36img onto it. Then boot into hboot and it should scan and find the image on your card.
Sent from my PC36100 using XDA App
jwterminator said:
If you rooted using toast's method, then your hboot should be 0.76 not 79. What you can try is reflashing the pc36img.zip from toasts method. You can use/acquire a card reader to connect your sdcard up directly to your computer and copy the pc36img onto it. Then boot into hboot and it should scan and find the image on your card.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Good info!
i noticed the difference in the hboot also - i went back to square one and tried to flash the pcm36.zip from my sdcard first and i keep getting the "main version older" error.
Ok, the indication here is that you've lost root access by having installed the sprint ota update. Are you unable to get to recovery via hboot? If you can get there, you might be able to restore a nand backup
Sent from my PC36100 using XDA App
mikeinghilterra said:
i noticed the difference in the hboot also - i went back to square one and tried to flash the pcm36.zip from my sdcard first and i keep getting the "main version older" error.
Click to expand...
Click to collapse
Go here and start @ step 2 and complete it http://forum.xda-developers.com/showthread.php?t=701835
If your NAND is still unlocked then after completing the above your hboot will have been downgraded. Please report back so that I may know if I did point you in the right direction.
nunyabiziz said:
Go here and start @ step 2 and complete it http://forum.xda-developers.com/showthread.php?t=701835
If your NAND is still unlocked then after completing the above your hboot will have been downgraded. Please report back so that I may know if I did point you in the right direction.
Click to expand...
Click to collapse
I am going to resurrect this thread because I have the EXACT SAME issue as the OP here but I don't seem to be NAND unlocked. (S-ON)
Going back to toast's method, I get the "main version older"
Any ideas?
Hi,
My EVO was happily rooted under 2.1 using the Fresh ROMs and adb commands since I got it, and I recently rushed into 2.2 and may have screwed myself. I know people throw around the term 'BRICK' but I'm worried I'm stuck until I either bring this to sprint (it's been RUUd to newest stock and doesn't work) or wait for people to better crack .93.
I'm a linux server admin and have experience with things like putting Linux on a PS3 and building Hackintoshes, so I'm real comfortable getting into bootloaders and fixing permissions and flashing stuff (even if the manufacturer frowns upon it . But I think I'm stuck after letting the damn .93 enter the equation and getting USB disabled - here are the symptoms:
USB Debugging is dead so no ADB possible. Fastboot USB and Hboot USB works (but no flashing from there - 'REMOTE NOT ALLOWED' because of .93 and S-ON.) I've tried on Win7 64, XP, OSX, and Ubuntu and it worked before I broke it. I do have the SDK drivers loaded (so it shows as Android Bootloader in device manager during fastboot usb screen) but have also tried HTC Sync drivers. Yes, USB debugging is on and it's set to 'charge only'. The device manager shows 'Qualcom CDMA Device' three times. I can see 'uart disabled' in the fastboot oem boot so I'm quite sure it's been toggled off somehow.
The phone boots normally to a stock unrooted RUU of 2.2 and locks up after about a minute and restarts. So, anything I can try within android must be accomplished in this one minute, then it shuts down and reboots. I've tried turning off all services in a rush, and airplane mode to kill the radios and it won't stop it from crashing. I've stared at CatLogger set to error and nothing is major ... but it's not rooted at this point so i can't flash from within android, run ROM Manager, or run connectbot su to fix the USB. Everything works perfectly for this one minute - network, sd, etc.
So my options for getting into the phone are: PC36IMG.zip on SDCard through reader (fails unless hboot = .93, can't roll back), update.zip on SDCard (recovery can't be written), connectbot (non root, and only a minute at a time), and limited fastboot usb commands.
I've spent hours trying to flash anything with the above options and have failed.
The sequence that got me here was (stupid?):
When I got my 2.1 phone I did: geekfor.me/faq/how-to-root-your-evo-4g/
Then updated with new Fresh ROMS to the 2.2 pre-release. I flashed the radios too. Everything worked besides 4G and I was itching for an update ...
Then I tried to download the newest Stock Fresh Evo 3.2.0.0 and install it and did a total wipe of the system from the stock Bootloader trying to 'wipe first' - instead of a cache wipe from a custom recovery or factory reset in the OS. At this point I reinstalled an older PC36IMG.zip to be able to boot, but I lost USB and SDcard at this point.
So I then STUPIDLY got the Sprint 2.2 update through the phone - thinking it would fix the USB and SD card, and to see if the 4G was working in the stock 2.2, since it didn't work in the preview Fresh 2.2 rom. And I thought I could always roll back, or that there'd be some way out. (I fixed sd with fastboot oem enableqxdm 0, but the USB fix steps I found need root and connectbot)
Well, it put the damn .93 on. I would be fine if it was just stock for now since everything is working - but only for a minute! then reboot, reboot, reboot.
I've tried a few RUUs but can only apply the newest one successfully, (others fail because it's trying to apply .76 bootloader and fails with 'wrong bootloader') I've done the RUU a number of times and factory reset the hell out of everything.
Is anyone else having the reboot problem? Could it really be a hardware issue? Why is it rebooting?
Do I just have to wait for people to break the .93 with a new tactic?
Does anything below look out of place?
Here is my bootloader menu:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.93.0000
MICROP-041F
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.28
July 23 2010, 16:41:47
Here is the fastboot OEM boot output:
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x23301
INFOTAG:hero panel = 0x1
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is SPCS_001
INFOsetting->cid::SPCS_001
INFOserial number: HT05SHL14545
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =480
INFOactive commandline: board_supersonic.disable_uart3=1 board_s
INFOupersonic.usb_h2w_sw=1 board_supersonic.disable_sdcard=0 dia
INFOg.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata
INFO_sel=0 androidboot.emmc=false androidboot.baseband=2.15.00.
INFO07.28 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_
INFObattery androidboot.carrier=COMMON androidboot.mid=PC3610000
INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb
INFOoot.serialno=HT05SHL14545 androidboot.bootloader=0.93.0000 n
INFOo_console_suspend=1
INFOaARM_Partion[0].name=wimax
INFOaARM_Partion[1].name=misc
INFOaARM_Partion[2].name=recovery
INFOaARM_Partion[3].name=boot
INFOaARM_Partion[4].name=system
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOpartition number=7
INFOValid partition num=7
INFOmpu_nand_acpu_rw D3E 2000
INFODelay 99998(us) for dpram command before goto AMSS...
INFOjump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:326240 msec
FAILED (status read failed (Too many links))
finished. total time: 5.127s
THANKS!!!! I'd love to get my phone back!
sorry - I meant to post in Q&A and am trying to move it ... can an admin help? I can't delete or move this.
Since you managed to get it back to stock, Id just take it back to sprint and get a new one....
GadgetMonger said:
Since you managed to get it back to stock, Id just take it back to sprint and get a new one....
Click to expand...
Click to collapse
If he gets a new one possibly it will probably have .93 on it and wont be able to revert back to .79
xxbabiboi228xx said:
If he gets a new one possibly it will probably have .93 on it and wont be able to revert back to .79
Click to expand...
Click to collapse
Yeah, this is what I was afraid of. But at least it'll work stock.
I've also just been playing with:
fastboot oem rebootRUU
which lets me
fastboot flash zip rom.zip
but the only thing that passes the signature verification is the rom.zip from the new RUU
I'm clearing my flash card getting ready to go to the Sprint store but was curious if anyone had any other grand ideas. I know this .93 is a biotch ...
Wish i could help ya man but im not that knowledgable, all i could say is best of luck and if all else fails... Just grab a new one from Sprint... eventually the guys over here will have it rooted.
I have an appointment at the sprint store in an hour - the woman on the phone says that a lot of people are having issues with the stock update and that they may be able to reset it ... but wondering what they might be able to do.
you should come into the irc chanell man, there are some geniuses in there, and according to the revoked team as i recall they have only once ever come across a true brick, and there dev's do play in our irc channel, hope you get her up and running
Even if they reset and update you to a true unrooted 2.2 thats fine because you can still root 2.2,,, i dont see where the worry is coming from.
How many "how to root 2.2" threads do we have.
This should be a moot point by now, just let them try and then if it doesnt work they will get you a new one that you can root.....
Sent from my PC36100 using XDA App
Hi
Appologies for a another bricked DHD Thread, I was wondering if anyone could give me some advice. (I've tried stuff from a few other thread's to no avail)
I rooted my phone back in January and the phone was working fine running CM7 (so I'm pretty sure rooting didn't cause this). About Two weeks ago my phone was running low on battery (I had no charger to hand and was working away), and went into a couple of random restarts but booted fine after about 10 mins of being on the phone started to constantly vibrate for about 15 mins, so I pulled the battery out. and left it out over night.
additional info: I'd been caught in some seriously heavy rain that evening when the phone was in my pocket, but phone did not seem wet and the moisture damage sensors on the battery is still white (not sure theres another).
I borrowed a charger from someone at work and charged the battery for about an hour before switching the device back on (I don't like to switch on devices when they have really low battery), but since then the phone only goes so far as the green HTC logo on a white background, I can get in to hboot/fastboot (via power + vol down) but, if I try to get in to recovery I just get the green on white HTC logo (I've left it running for two hours before pulling the battery out)
After reading up a few threads I decided to restore from an RUU file. so I booted into fastboot and pushed the unbranded 1.32 RUU on to the phone by running the RUU .exe file, this loaded successfully but my phone still stayed stuck on the HTC logo with no access to recovery. Tried this with SD card in the phone and with the SD card removed, also tried with the SIM card out, to no avail, I then tried another RUU (2.36) but ended up with the same result.
If I try to boot from fastboot (via fastboot oem boot) I get the following output then it just hangs (while the phone displays a white and green HTC logo):
Code:
INFOsetup_tag addr=0xA0000100 cmdline add=0x8D088398
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26503
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is HTC__001
INFOsetting->cid::HTC__001
INFOserial number: HT0B9RX11266
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =461
INFOactive commandline: board_spade.disable_uart2=0 board_spade.
INFOusb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
INFOrd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=true androidboot.baseband=26.03.02.26_M androidboot.cid
INFO=HTC__001 androidboot.batt_poweron=good_battery androidboot.
INFOcarrier=HTC-WWE androidboot.mid=PD9810000 androidboot.keycap
INFOs=qwerty androidboot.mode=normal androidboot.serialno=HT0B9R
INFOX11266 androidboot.bootloader=0.85.0007 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOpartition number=8
INFOValid partition num=8
INFOjump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
The RUUs seem to have removed my ENG S-OFF bootloader so I no longer have access to the command that would allow me to try loading a new recovery image. Heres what it shows on the hboot menu.
Code:
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011,00:55:45
HBOOT USB PLUG
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
then three Droids on skate boards.
Selecting Recovery or factory reset just get the phone stuck at the HTC logo.
Anybody have any advise on this? Or should I give up and admit its knackered, since I'm pretty sure it no longer under waranty since I've rooted it. (Although put the RUU is meant to unroot the phone, I'm pretty sure if I return it they'll be able to tell it modded because of the bootloader (not 100% on that though)).
Any help would be welcomed.
Thanks
Andrew
andrewwardrobe said:
Selecting Recovery or factory reset just get the phone stuck at the HTC logo.
Anybody have any advise on this? Or should I give up and admit its knackered, since I'm pretty sure it no longer under waranty since I've rooted it. (Although put the RUU is meant to unroot the phone, I'm pretty sure if I return it they'll be able to tell it modded because of the bootloader (not 100% on that though)).
Any help would be welcomed.
Thanks
Andrew
Click to expand...
Click to collapse
The fact that HBoot is intact would suggest that you should theoretically be able to bring it back to life, however I'm not gonna try and answer how as I really don't know, you've tried everything that I would have tried. Although having said that, did you have 'radio s-off' and super-CID? If so you might be able to flash a new recovery via fastboot (can't remember if this is possible with only radio s-off)
With regards as to warranty. HTC don't really seem that bothered about custom stuff and the fact that you have a stock HBoot, they would most likely fix it under warranty.
to flash a recovery via fastboot the command would be "fastboot flash recovery <path to><filename of recovery>" There is a very fine new recovery based on CWM in the DEV section. It's worth a try.
Yes as Doktaphex said, flashing a new recovery is the next step.
Cheers guys, I'll give that a go when I finish work and let you know how I get on.
Ship S-OFF -> shiped hboot, radio s-off. The ship hboot doesn't support fastboot commands so there is no way to flash a recovery thru fastboot.
But you have Radio s-off so i guess you also have super cid. That means that you can flash any shipped ruu.
I suggest you to try to flash any shipped wwe ruu (1.32 if possible, dont know if it will work if you have only radio s-off).
If it won't flash, try any shipped ruu with a build number higher than the one you had on your phone.
Sent from my Desire HD using Tapatalk
EDIT: forgot to say that your phone must be in the Fastboot menu in the bootloader if you want to flash a ruu.
Trying to flash recovery failed (remote not allowed), for the reason Flussen has stated.
I've allready tried to flash RUU files which still get stuck on the reboot. I think i'm going to try to return it to HTC see if they can do anything.
Thanks for the help guys I really appreciate it.
Andrew
andrewwardrobe said:
Trying to flash recovery failed (remote not allowed), for the reason Flussen has stated.
I've allready tried to flash RUU files which still get stuck on the reboot. I think i'm going to try to return it to HTC see if they can do anything.
Thanks for the help guys I really appreciate it.
Andrew
Click to expand...
Click to collapse
How about rename the ruu into something like pdsomethingsomething.img ?
Sorry, couldn't remember the name. You should see the hboot is looking for this file when you load the bootloader. I guess it will automatically load this file in sdcard if you have any.
Yes,also possible.
Take a look into the downgrade to 1.32 thread. There should be an 1.32 PD98IMG.zip file.
Download it and place it in the root of your sdcard. The bootloader should detect it automatically.
Sent from my Desire HD using Tapatalk
andrewwardrobe said:
Trying to flash recovery failed (remote not allowed), for the reason Flussen has stated.
I've allready tried to flash RUU files which still get stuck on the reboot. I think i'm going to try to return it to HTC see if they can do anything.
Thanks for the help guys I really appreciate it.
Andrew
Click to expand...
Click to collapse
Before you send it back try putting the same rom on the sd card if your on Cyanogen 7 make sure your using 3.*.*.* in clockwork mod (if using Clockwork mod 2.*.*.* use CM6) if your not thats why you are bootlooping! First wipe the cashe, then wipe the dev cashe, then factory reset, then flash your rom, now wait it will take inbetween 2-7mins to load up again!
That should have solved your problem so press the thanks button if it helps
Hi All.
Not my phone, but a friends:
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
If you go into recovery, the phone just vibrates a few times and turns off. If you go Factory Reset, the phone just freezes.
I've tried:
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
I assume all my issues have been due to S-ON.
I'm stumped - any ideas?
There have been a few folks on here with the same issue in the last few weeks. Not that the phone is terribly old, but I wonder if it can be that some hardware component (eMMC or other) is failing over time?
expza said:
Hi All.
*snip*
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
?
Click to expand...
Click to collapse
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
oelly said:
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
Click to expand...
Click to collapse
I was able to create a working GoldCard using my phone, it no longer gives Model-ID Incorrect. HOWEVER, new problem. It's now moaning about Main Version being older, update failed.
I see android-info.txt in the ZIP is:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
However, this phones info is:
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
I assume it's the Radio Version number that is not matching up - however, the one RUU's in Shipped-Roms with that Radio Number are EXE's and not ZIPs.
Does anyone know how I can get a ZIP RUU that would work with this phones current versions?
edit: p.s. ZIP I'm currently using is PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U_26.08.04.30_M3.zip (renamed when on SDcard to PC10IMG.zip)
double edit: Have found a way to extract zip from EXE. Loaded it to Gold Card and update is currently flashing via HBOOT. Still on Bootloader. Assume this takes a while (10 - 15 minutes), so I'll be patient.
combo edit: should state the the RUU ZIP I extracted was RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Phone honors the PC10IMG.zip, but gets stuck on BOOTLOADER - Updating.
Any suggestions? Is it safe to delete items out of the RUU .zip? Want to try flash recovery.img only.
edit: looks the the rom.zip I extract is always corrupt (when trying to edit it using WinRAR or something)
You can't edit the zips, they are signed, so anything you do to them will cause them to not flash.
Winrar might be complaining because of the signing.
-Nipqer
Given up on trying to flash the RUU via HBOOT - it just freezes on "Bootloader - Updating" - pulling battery causes no issues so I assume it doesn't even attempt to flash anything.
Next step, using HTCDev to unlock the bootloader? Safe? I worry that the Bootloader not flashing via RUU means that HTCDev Bootloader Unlock won't work, or could possibly break it.
same problem
hi mate, im having the exact same problem as you...did you manage to fix it?
i have found the same ruu for my radio version but it gets stuck on the bootloader as the bar moves but the fone stays on the same screen.
do u think i need to make that goldchip card? how do i make one please?
i had that same problem just 2 days ago so in order to get the ruu to flash right it has to be a radio thats higher than the one you already have ... but if that dosnt work you will have to change it manualy using adb in recovery mode so wat you do is power offf the phone comptley and plug it in your computer via usb then open up adb and type adb devices the phone has to be off and it should show your device id then the word recvery next to it then your gunna wanna pull the misc.img from the phone and edit it with a hex editor i did this method to downgrade my g2 kus my sdcard dosnt read but after you change the misc the ruu shuld flash fine 1.power off phone Connect phone to computer,
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. 1.00.000.0
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/misc.img of=/dev/block/mmcblk0p24
14.Reboot to fastboot then fastboot reboot to RUU then fastboot flash PC10IMG.zip and it shuld flash fine
---------- Post added at 11:42 PM ---------- Previous post was at 11:37 PM ----------
or yu can try this http://forum.xda-developers.com/showthread.php?t=1526316 and should work its alot easier than the adb method
Never managed to fix this (tried the exact same thing ari3z suggested, but ages ago) - just kept freezing when trying to write anything to flash.
Phone was eventually swapped out in warranty.
Dear xda community,
I have a HTC Desire Z from Bell.
I wanted to get a CyanogenMod on my phone so I started by attempting to downgrade from Gingerbread to a stock and exploitable Froyo.
It ultimately failed and now I am stuck on the RUU - a black screen with a gray/silver "HTC" logo and a triangle with an exclamation mark at each of the four corners of the screen. I can not use adb commands but I CAN use fastboot commands.
What Happened In Detail:
I followed this guide: HTC Desire Z: Firmware Downgrade (Gingerbread)
Everything went fine until I got to step #8 where I selected Bootloader to flash the 1.34.707.3 firmware where the flashing said it failed.
The phone was still fine after this but I still wanted to flash it so I tried a different guide: [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
I succeeded in the following steps - "Gaining Temp Root" and "Changing Version Number to Allow Downgrade and Gaining SuperCID with a Goldcard" but the problem occurred on "Fastboot Downgrade".
I downloaded the Vision_DZ_1.34.405.5_PC10IMG.zip ROM (2nd mirror for Desire Z) and got to step #9 where it got stuck (at this point I don't recall what I saw on the screen). Since I couldn't restart it manually I pulled the battery and then put it back in. Then what I saw was the black screen with a gray/silver "HTC" logo and 4 exclamation triangles.
The peculiar thing is that the phone would restart continuously (about every 5 seconds) which is essentially it goes to a black screen and then back to the gray/silver "HTC" logo periodically.
I can not use adb commands but the fastboot commands work ONLY when the screen has the HTC logo on it.
Also, if I wait long enough (~1 hour maybe) with the phone plugged into the computer (using USB) the screen will stay at the "HTC" screen where I can use fastboot flash command without the connection being disconnected (it would give me an error* otherwise when I try to send a large file). Interestingly, it would return back once again to the periodic restarting after I wait another hour (roughly).
*The error it gives is:
FAILED (data transfer failure (Too many links))
Click to expand...
Click to collapse
Attempted Fix:
I tried to flash another ROM using
fastboot flash zip StockRom.zip
Click to expand...
Click to collapse
when the screen isn't rebooting all the time but when the file has supposedly finished transfering it says:
INFOsignature checking...
FAILED (remote: 13 battery low)
Click to expand...
Click to collapse
I tried to flash "recovery-clockwork-5.0.2.7-vision" as well but then it gave me the following error:
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
I tried to recharge the battery after sticking it into the wall socket but it would still end up giving me the same error.
I also tried to do these commands without the SIM card and the SD card in the phone but to no avail.
I ran the "fastboot getvar all" command and got the following:
INFOversion: 0.5
INFOversion-bootloader: 0.85.0005
INFOversion-baseband: 26.10.04.12_M
INFOversion-cpld: None
INFOversion-microp: 0425
INFOversion-main: 1.00.000.01
INFOserialno: HT0ALRV01556
INFOimei: 352244040029140
INFOproduct: vision
INFOplatform: HBOOT-7230
INFOmodelid: PC1012000
INFOcidnum: BM___001
INFObattery-status: good
INFObattery-voltage: 4130mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-9ddda97c
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Question:
What steps should I take in order to get my phone back to the way it was before I attempted any downgrades?
If there is no possible answer to the previous question - What should I do so that at least I can use my phone to talk on it?
I appreciate any help and hopefully I can get this phone in to working condition again.
Please let me know if more information is required.
Thank you.
Moejoe123
log onto #g2root on freenode, ask your questions there, with realtime help you should be good
Sent from my HTC Vision using xda premium
Try running 'fastboot oem boot' to force the phone to boot up (hoping it will actually boot up)
If you manage that, you can then use misc_version 0.5 to clear the ruu flag.
Code:
adb push misc_version /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 755 misc_version
# ./misc_version -r off
which will let your phone reboot normally by itself.
Otherwise let it charge up, and retry flashing the rom (might pay to try do it from hboot, rather than fastboot)
-Nipqer
Nipqer said:
Try running 'fastboot oem boot' to force the phone to boot up (hoping it will actually boot up)
If you manage that, you can then use *url* to clear the ruu flag.
Code:
adb push misc_version /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 755 misc_version
# ./misc_version -r off
which will let your phone reboot normally by itself.
Otherwise let it charge up, and retry flashing the rom (might pay to try do it from hboot, rather than fastboot)
-Nipqer
Click to expand...
Click to collapse
Thank you very much for the response Nipqer.
I used 'fastboot oem boot' and that got me back into the normal mode and I could even call!
I tried to do the next steps of code that you provided me with but I had "$" instead of "#" and when I executed the last line of code I got:
Code:
--setRUUflag off set. RUU flag will be cleared!
[1] Segmentation fault ./misc_version -r off
I don't know if this is supposed to happen or not but it appears I didn't have temporary root...
The only thing now is that the phone is version 2.2 and the interface has changed around.
Is there some kind of clean-up I should do of the phone? Such as delete the PC10IMG.zip file on the SD card?
It would be nice to also get the phone rooted, I am thinking of following "STRAWMETAL's Downgrade From Gingerbread to Froyo Guides and Tools" which has the guide very specific to Desire Z so hopefully there won't be any unexpected failures... What do you recommend for how I should proceed?
I appreciate the time you took to help me, I was phoneless for a week!
Yeah misc_version failed to clear the RUU flag as you didn't have root access. As you say you're on a froyo rom now (Android 2.2) you can use psneuter to gain temp-root, and wipe the RUU flag (check Strawmetal's guide for psneuter).
Have you managed to complete a flash of the PC10IMG? cause from your first post, you're still on the 26.10.04.12 radio (you need 26.03.xx.xx to root)
If you are onto a good radio, go ahead and remove that PC10IMG from your sdcard, otherwise try and flash it again, and remove it once you're done.
Other than that, there shouldn't be anything else you need to 'cleanup' on your phone.
Strawmetal's guide is quite good, so follow that and you should be able to get root fairly easily.
-Nipqer
Nipqer said:
Yeah misc_version failed to clear the RUU flag as you didn't have root access. As you say you're on a froyo rom now (Android 2.2) you can use psneuter to gain temp-root, and wipe the RUU flag (check Strawmetal's guide for psneuter).
Have you managed to complete a flash of the PC10IMG? cause from your first post, you're still on the 26.10.04.12 radio (you need 26.03.xx.xx to root)
If you are onto a good radio, go ahead and remove that PC10IMG from your sdcard, otherwise try and flash it again, and remove it once you're done.
Other than that, there shouldn't be anything else you need to 'cleanup' on your phone.
Strawmetal's guide is quite good, so follow that and you should be able to get root fairly easily.
-Nipqer
Click to expand...
Click to collapse
Thank you for the reply.
Strawmetal's guide gives the following code:
Code:
adb push psneuter /data/local/tmp/
which then sends the file through... and then I typed:
Code:
adb shell /data/local/tmp/psneuter
which then tells me:
Code:
/data/local/tmp/psneuter: permission denied
I searched the internet for some solution and I found the following code to get temporary root (#):
Code:
adb shell
$ chmod 777 /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
$ exit
adb shell
which indeed did grant it to me.
Then I proceeded per your instruction to turn off the RUU flag but it gave me the same error message.
I also tried to do "adb push misc_version /data/local/tmp/misc_version" instead of "adb push misc_version /data/local/tmp" but the end result was the same.
Could you please let me know the code I should use to proceed?
My apologies if I am misunderstanding what I was supposed to do.
PS. I never did manage to get a complete flash of PC10IMG.zip. I tried it once again just now using the temp-root method I quoted above and it got up to some point and then suddenly the phone decided to go into those periodic reboots and I got the error message that "FAILED (status read failed (Too many links))". The error message was just after it did "INFO[RUU]WP,userdata,67".
Hi,
Could you please try to use misc_version 0.4 and check if it still gives you the segfault?
Get it from here: misc_version_04.zip
Use the the same commands as you already tried but make sure it is version 0.4 by running the command:
Code:
/data/local/tmp/miscversion -v
before you use the
Code:
/data/local/tmp/miscversion -r off
Have fun - Guhl
Stuck at Splash screen
Nipqer said:
Try running 'fastboot oem boot' to force the phone to boot up (hoping it will actually boot up)
If you manage that, you can then use ...
-Nipqer
Click to expand...
Click to collapse
I cant proceed by "fastboot oem boot" ..getting following error
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8D089C40
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x25209
INFOTAG:hero panel = 0xF
INFOTAG:engineerid = 0x4
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is HTC__044
INFOsetting->cid::HTC__044
INFOserial number: SHxxxxxxxx
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =474
INFOactive commandline: board_vision.disable_uart2=0 board_visio
INFOn.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
INFOboard_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=true androidboot.baseband=26.03.02.26_M androidboot
INFO.cid=HTC__044 androidboot.batt_poweron=good_battery androidb
INFOoot.carrier=HTC-Asia-SEA-WWE androidboot.mid=PC1011000 andro
INFOidboot.keycaps=qwerty androidboot.mode=normal androidboot.se
INFOrialno=SHxxxxxxxxxx androidboot.bootloader=0.76.2000 no_cons
INFOole_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOpartition number=7
INFOValid partition num=7
INFOjump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
INFO-------------------hboot boot time:131081 msec
FAILED (status read failed (Too many links))
Also, i have done fastboot flash boot boot.img, whereas boot.img was from Stock Rom that i had downgraded successfully.
still no luck..
Please help me i can boot into recovery tried clockwork and 4EXT.. done wipe/format all..wipe cache etc. etc.
Still i am stuck at splash screen..
some other details:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1011000)
MICROP-0425
RADIO:26.03.02.26_M
eMMC-boot
Aug 20 2010,16:51:01
Kindly help me, i have tried seeking help from #g2root , but no replies from anyone..except alexbobp but he's away..
What happens if you just flash a known stable ROM (like cm7) through recovery? Does it error? Does it flash but then you get stuck in boot loop?
Sent from my Nexus 4 using xda premium
Helllllllllpppppppppppp!!!
hi
i have this problem,i ran RUU too,but the RUU file wait on 14% but without any error!!! and now my phone is on splash screen(dark screen with an htc logo in center)....what should i do???? helppppppp
cannot load stockrom.zip:unknown error
Hellow folks! Tank God for u guys and xda... Pls I'm a new user and I'm having problems flashing stockrom... I was using slimbean and trying to flash stockrom....I already installed fastboot and adb.... I ensured I had the correct command line..and I ensured d folder name was stockrom.zip but its telling me "ERROR: CANNOT LOAD STOCKROM.ZIP" pleas any help in stuck on the Blue screen with the HTC LOGO on it...mm PLEASE HELP
fastboot reboot-bootloader
Sent from my Nexus 4 using Tapatalk 2