Hello all,
I have problem with my HTC Desire 300. When phone is turned on it vibrates for a second and screen gets white with green htc letters on it. The screen stays that way for few seconds and phone is turned off and then back on and this loop goes on forever. The only way to stop this is to remove battery. At that point phone is as it was from factory - it was not rooted nor anything else was done on the phone.
I have searched on Internet and found solution to try to do factory reset.
So I pressed volume down and power key and entered menu with option for factory reset. I choose factory reset and thought that everything will be fine but.....everything was as same as on the beginning. Phone vibrates for a second, white screen + green htc letters for few seconds and then turns off and back on again and loop goes forever.
My next try was to choose recovery option from menu, but it ended up the same way.
Then I searched for solution and found this article: http://forum.xda-developers.com/showthread.php?t=2602301
I thought that installing recovery image might help so I followed steps as described. First I had to unlock my phone's bootloader and, at my surprise, I managed to do that. Now my phone's bootloader is in unlocked state. Then I run fastboot and managed to flash recovery.img as described. I powered phone down, up again, choosed Recovery option and phone restarted. Again, short vibration, white screen with green htc letters on it, BUT in upper part of screen is written entering recovery! Unfortunately, it stayed that way for few seconds, then turned off, turned back on and endless loop is here again. But only first time there was written entering recovery in upper part of screen.
Then I tried another option. I found on: https://drive.google.com/folderview...WkFRSjRaMjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
ROM for this phone. I changed name to 0P6AIMG.ZIP, save it to an SD card and choose fastboot option. Now I received error Lack of heap!
I found that problem might be that my bootloader is unlocked so I relocked it again but I receive same error.
Seems to me that each time phone tries to start something (portion of software) but it can't so it turns off and then back on.
Could it be that something else need to be flashed or phone memory itself is bad?
I can use fastboot commands but I can't use adb.
Can you advise me what to do next and what to check.
On above site I found 4 more files:
boot_init.img
boot_stock.img
recovery_stock.fstab
recovery_stock.img
What are those files for and how can I try to use them?
Here is output of fastboot getvar all command:
C:\HTC\ADBFAST\ADBFAST>fastboot getvar al
INFOversion: 0.5
INFOversion-bootloader: 1.18.0002
INFOversion-baseband: 14.11.36Q4.21
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.10.401.4
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH3BEWL01916
INFOimei: 358280055226720
INFOmeid:
INFOproduct: g3u
INFOplatform: HBOOT-8225
INFOmodelid: 0P6A10000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4100mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e1c32097
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.044s
Please help as I run out of ideas and knowledge......
Best regards,
Ivo
Now, that does not sound promising...
Looks like hboot is unable to start both of your phones ramdisks (boot.img / recovery.img)
You could try my recovery build but I doubt it will change anything since SPSPawns build should
also boot 'fine'... [into a panic state until the hardware resets itself after ~5 minutes]
If you are unlucky somehow hboot (or radio) got corrupted and the phone is now unable to
boot permanently. Since you are still S-ON this should not be possible unless the
hardware is faulty.
I don't see a lot of options here.
It might have been a better idea if you had tried getting a replacement instead of unlocking it.
But honestly I can understand the need to try and fix it yourself. In any case if you ask htc nicely,
and explain the situation to them, they might still be willing to help.
You could try to find a working recovery and flash it (fastboot flash recovery recovery.img)
You could try extracting the boot.img from the stock odex rom and flash it. (fastboot flash boot boot.img)
You could wait and hope that HTC will release an official RUU for this device. (But if yours is branded this would be pointless)
You could wait for S-OFF and try to flash a working radio or hboot
fyi:
The files you found on the google drive look more like data gathering to me.
boot_init.img (no idea, maybe the first build of a bootable ramdisk)
boot_stock.img (could've been used to grab anything essential for a ramdisk)
recovery_stock.fstab (the mount point layout of the stock recovery)
recovery_stock.img (could've been used to grab anything essential for a recovery)
Also, adb only works once adbd gets started. (during boot of system or recovery)
Thank you for your answer.
Is there any way to check hardware or parts of hardware of phone with fastboot or some other tool. If it is hardware failure then nothing can be done Can I check that somehow?
However, if it is software problem, then I would like very much to go on
You have suggested to try to find a working recovery and flash it. I have one working Desire 300 bought at same time in same shop with same mobile provider. Can it be used for necessary files (images) or whole phone ROM - can I take files from that phone?
I can try to flash your recovery image, but as you sad, I successfully flashed SPaWn's recovery. During flashing process on phone screen was visible small vertical green progress bar for loading and then red progress bar for writing and double OK confirmation on prompt window. Is this indication that phone RAM and other hardware is good after all?
I can extract boot.img from the stock odex rom (downloaded from link in my previous post) and flash it to see if regular boot is ok.
If hboot or radio is corrupted, can I use file(s) from working phone to fix? Before that should I try to put it in S-OFF? I saw few pages where this procedure is described. Should working phone also be in S-OFF for getting these file(s)?
What do you suggest to do first?
You sad:
"It might have been a better idea if you had tried getting a replacement instead of unlocking it.
But honestly I can understand the need to try and fix it yourself. In any case if you ask htc nicely,
and explain the situation to them, they might still be willing to help."
Unfortunately, phone is out of warranty and this was not an option since screen is a bit cracked (but it worked for months that way). I repair electronics for years and I am glad that you understand my need to try to fix it myself
Than you very much in advance,
Ivo
I don't know of a way to use fastboot for hw diagnostics, sorry.
I've never seen a progressbar while flashing via fastboot, then again I'm only checking
the output of fastboot. (written x kb in y seconds etc)
But I never had to confirm anything while doing so. Are you sure you did everything correctly?
You mentioned 0P6AIMG.ZIP in your first post. This is not the right way to flash a custom boot or recovery!
You need to use fastboot for this to actually work.
web: grab my recovery and extract it to get recvovery.img
phone: Boot to hboot and select fastboot don't forget to connect USB
pc: in bash or dos prompt > fastboot flash recovery recovery.img
pc: check if everything went ok
phone: select bootloader and then start recovery
fingers: crossed
And yes, your secondary device could be very helpful in order to restore the primary BUT
there is no way to switch this phone S-OFF, at least none that I know of, so you won't have the permissions to modify hboot or radio.
Still it's an excellent source to get system data and boot.
I've never tried restoring a cwm backup of one device on another of the same model, but as long as the partitioning
is the same I can think of no reason (except a cwm sanity check) why this shouldn't work.
You could also use dd if cwm fails but let's try the uncomplicated way first
Hello,
I tried with your file, but crossed fingers didn't help...endless loop is here again, first time with entering recovery written.
About confirmation during flashing, I thought on this confirmation (this is taken with your recovery.img file):
C:\HTC\fastboot-win>fastboot flash recovery recovery.img
sending 'recovery' (6484 KB)...
OKAY [ 1.214s] <----this confirmation
writing 'recovery'...
OKAY [ 2.321s] <----this confirmation
finished. total time: 3.537s
Sure I didn't need to click on anything to confirm. Sorry for my unclear explanation at previous post
About 0P6AIMG.ZIP in my first post - I saw procedure for upgrading here: forum.gsmhosting.com, guide-how-upgrade-your-htc-android-phone-microsd-card (I am not allowed to put external link yet)
In step 2 there is explanation for renaming upgrade file to model number + inf. I found that when SD card is inserted, during fastboot I see on screen following:
SD Checking...
No gift file...
Loading...[0P6ADIAG.zip]
No image!
Loading...[0P6ADIAG.nbh]
No image or wrong image!
Loading...[0P6AIMG.zip]
Loading...[0P6AIMG.nbh]
No image or wrong image!
So I thought that phone expect any of these files for booting. This is why I renamed original ROM that I found and put it on SD card and try to boot. Then I got 'Lack of heap' error.
One more try that you have suggested is to try extracting the boot.img from the stock odex rom and flash it. (fastboot flash boot boot.img). Is this image from zip file which I found on link from my first post, or should boot.img file be taken from working phone (if yes, how to do that)? Zip file name 'HTC_Desire_300(Zara mini)_stock_odex_1.10.401.4_root_updated_v.1.0.1.zip' indicates root updated and my phone is/was not rooted.
You sad:
"And yes, your secondary device could be very helpful in order to restore the primary BUT
there is no way to switch this phone S-OFF, at least none that I know of, so you won't have the permissions to modify hboot or radio.
Still it's an excellent source to get system data and boot."
Can you please tell me how to get needed files from working phone and which files? I assume that I should use commands in ADB tool?
Thank you for your time that you are spending for my problem
Ivo
For now focus on getting the phone to boot again. So far the recovery partition seems to be broken.
Next try flashing the recovery image on the boot partition (flash boot recovery.img) to check if you can boot from there.
If it works you can continue by replacing it with the boot.img from your other device.
If you can't get recovery to boot from either the boot or recovery partition, you can consider this phone a brick.
At least until S-OFF is available so you can try replacing hboot and radio.
To get the boot image from the the other device you will have to install a recovery.
Afterwards you can just make a backup and you'll find the boot.img in the backup folder
You could also grab any files you want from system or data by renaming *.tar.a to *.tar and extracting it with 7z
Alternativly dd can be used from an android terminal to backup any partition to an img file on the sdcard, (requires superuser)
It is true that the files hboot lists while starting are used to start diagnostics and updates depending on the zip file
but I'm pretty sure it requires the contents to be signed by htc in order to work.
I tried to flash boot.img extracted from the stock odex rom (fastboot flash boot boot.img), but endless loop is still present. So obviously phone can't continue in any direction after first initialization.
Since currently there is no way for S-OFF, is there anything else to try or we came at stop point?
Technically it's over. But just to be completly sure try to flash the recovery.img as boot.
We can't be certain that your system partition might be corrupted aswell unless we try a 100% working ramdisk.
if recovery can't start from either the boot or recovery partition you'll have to wait for S-OFF or just use the device for spare parts.
If it actually boots you can still use it to restore your device but remember if you restore a backup or flash a new rom you will
permanently loose recovery until you reflash it to boot again, sacrificing your system in the process.
Still, good luck for your final attempt and my condolences if this last resort also ends as a failure.
I will try that, just tell me can I run 'fastboot flash boot recovery.img' (with your recovery image or SPaWn recovery image) or should I rename recovery.img to boot.img and then run 'fastboot flash boot boot.img'
What I mean does file name during flashing matter or only content of file is important?
the filename is completely irrelevant. The important part is that it is smaller or equal to the partition size of boot.
Since both boot and recovery are roughly 16MB, everything should be fine. Well in your case probably not...
but you know what I mean.
btw:
After a little pondering my guess would be a broken RAM.
For one it is unlikely that your device managed to kill radio (which wouldn't matter for recovery)
or that hboot got damaged, since it would usually end in it not booting whatsoever.
Furthermore it is highly unlikely that two partitions of your internal emmc broke at the same time.
And since ramdisks (like boot and recovery) get loaded into RAM in order to work. (hence the name)
I'd guess, with a rather high certainty, that somehow your RAM got damaged and now your device is toast.
For your sake, I hope I'm completely wrong. :angel:
I have tried, but with same results......
I think that we can conclude that I indeed have hardware failure (most probably) with access to RAM.
What else can I say except thank you so much for time spent and for advices that you gave me.
My next step will be to disassemble the phone and see if there are any obvious cracks on printed circuit board, although I think that chances to repair this are close to nothing since this is double or multiple layer board packed with SMD components.......
I will certainly let you know if I make any progress!
Once again, thank you very much for all. If you come to Zagreb, we can always go for a beer
Best regards,
Ivo
EXTRA! EXTRA! Read all about it...!
It works!!!!!!!!!!! Yes, it works again!!!!!!!!!!!!!!!
A friend of mine has friend who works in repair shop and, as she heard sad story about phone, told me to bring it to see if anything could be done. So I left phone at shop and tomorrow she called me and told me that it works! She explained me that her colleagues put new software and after 40 minutes phone was working!!!
So, after all, it was not hardware failure. It could be that part of software which is protected with s-on was corrupted. However, it works again!!!
I just wanted to share news with you
Glad to hear you got it booting again.
enjoy the working wifi on the stock rom.
i have same problem plz help me...
Related
hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.
Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated
can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed
What would i need for that? That's going into new territory
j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot
to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense
Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse
Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App
Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084
It is still the same.
If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...
Hi guys I have a mytouch 3G slide and I was able to get the bootloader unlocked. However even before I unlocked the bootloader I was unable to get the phone to work it would stay at the mytouch slide splash screen. Im on the new hboot and a am able to get into fastboot and hboot. However when I click recovery in hboot it takes me to the tmobile slash screen and never gets into recovery. I have flashed the original recovery but still no luck. I can't reboot the phone all they way. Anyone know what's wrong?
Sent from my MB611 using Tapatalk 2
Anyone have a solution
Sent from my MB611 using Tapatalk 2
Hey Moe92,
I'm pretty much in the same situation as you!
I was given a phone to fix that has water damage, the owner disclosed that up front and I can see this based on the moisture sensor on the device.
The phone boots up and is stuck on the splash screen with out any activity after this. This is the same screen that I see when trying to enter recovery.
The only thing the phone can do is go into fastboot and hboot. Let me make a list of all the activities I have tried to perform and what ended up happening. As of now I still cannot fix the phone.
Device Details in Hboot
Code:
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0002
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.15.35.16
Dec 13 2001,11:34:01
The items I've performed so far are:
* Downloaded two different versions of ESPRIMG.zip and placed them on the SDCARD for the device. Neither loads up by the device and they both fail.
The MD5 hash for each version is: 892b885010563208edc3037dfec40425 and 9e80d53b4afa73ecf0d58f703831ac82
* Created a goldcard and tried to run the above two files with the same result.
* Tried to enter recovery from the device; ends up on the boot splash screen and hangs
* Tried to use fastboot to flash several recovery images: Clockwork 2.5.0.7, recovery-RA-Saphire-v1.7.0, recovery.img from the ESPRIMG.zip files
* Each time fastboot flashes the recovery sucessfully, but trying to get to it ends up with a boot splash screen hang.
I'm starting to believe the phone is bricked, or something occurred internally when it became wet. I have no idea what the software was on it prior to it being wet.
From your experience does this phone have any luck of being restored? I've spent two days looking over the threads and trying to avoid asking a question that may be answered; but have had no success.
Any help would be greatly appreciated.
dustbyter said:
Hey Moe92,
I'm pretty much in the same situation as you!
I was given a phone to fix that has water damage, the owner disclosed that up front and I can see this based on the moisture sensor on the device.
The phone boots up and is stuck on the splash screen with out any activity after this. This is the same screen that I see when trying to enter recovery.
The only thing the phone can do is go into fastboot and hboot. Let me make a list of all the activities I have tried to perform and what ended up happening. As of now I still cannot fix the phone.
Device Details in Hboot
Code:
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0002
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.15.35.16
Dec 13 2001,11:34:01
The items I've performed so far are:
* Downloaded two different versions of ESPRIMG.zip and placed them on the SDCARD for the device. Neither loads up by the device and they both fail.
The MD5 hash for each version is: 892b885010563208edc3037dfec40425 and 9e80d53b4afa73ecf0d58f703831ac82
* Created a goldcard and tried to run the above two files with the same result.
* Tried to enter recovery from the device; ends up on the boot splash screen and hangs
* Tried to use fastboot to flash several recovery images: Clockwork 2.5.0.7, recovery-RA-Saphire-v1.7.0, recovery.img from the ESPRIMG.zip files
* Each time fastboot flashes the recovery sucessfully, but trying to get to it ends up with a boot splash screen hang.
I'm starting to believe the phone is bricked, or something occurred internally when it became wet. I have no idea what the software was on it prior to it being wet.
From your experience does this phone have any luck of being restored? I've spent two days looking over the threads and trying to avoid asking a question that may be answered; but have had no success.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Actually sometimes and this rarely happens... I can load into the welcome screen but everythine that happens, the phone is in safe mode. When I power down the phone it goes back to the splash screen and hangs there. I have to keep flashing the Tom many many time and pray that it gets into the welcome screen again.
BTW I can unlock the bootloader. Does anyone know what I can do after I unlock the boot loader?. I tried to flash zips via fadtboot but got the error where it cannot determine the signature. When unlocking the hboot, are there specific things I can do via fastboot? Please let me know. Thanks
I have also unlocked the bootloader by using the token provided by htcdev.
What zip did you try to flash to yours? I haven't tried that from fastboot yet. I only tried to flash each component of the ESPRIMG using fastboot with out any luck.
Moe,
Do you have any information on how to boot the device into safe mode?
I tried to use fastboot to flash an update.zip but that method did not work either :crying:
Does anyone have access to the ESPDIAG.zip for this device?
Ran out of ideas at this point .
dustbyter said:
I have also unlocked the bootloader by using the token provided by htcdev.
What zip did you try to flash to yours? I haven't tried that from fastboot yet. I only tried to flash each component of the ESPRIMG using fastboot with out any luck.
Click to expand...
Click to collapse
well when i unlocked the bootloader. i then decided to relock it. once i relocked it. i went to the HTC website and got the 2.2.1 RUU. once the RUU downloaded, i reloaded the phone with the firmware and once it was done, it booted o the entire OS but it was in safe mode. i didnt press any buttons for it to get into safe mode. it went in by itself...
also when i shut the phone off and truend it back on, i was back in square one where i was stuck in the boot loader screen.
Also you can extract the original ESPRIMG.zip file from the offical 2.2.1 ruu. In order to extract the .zip file, you first have to run the RUU. Once you click on the Downloaded RUU program, let it run. once the first page of the RUU comes up, follwo the below directions to extract the .zip file. DO NOT flash the phone with RUU if you want to extract the .zip file.
Here are the step by step instructions
1. open my computer
2. click on the main drive. (for me it was the C: drive)
3. click on users
4. click on you computer name (the one that has the lock on it)
5. click Appdata. (appdata is a hidden folder. to un-hide it, click---> Organize/Folder and search options/view/ scroll down to hidden files and folders/ click on show all files and folders)
6. click on Local (NOT Locallow or Roaming)
7. click on Temp
8. when you get into the folder, sort the files to the DATE MODIFIED
9. when you have it sorted, you will see some folders such as ({95153F7E-B880-4656-B55D-54DD7869F984}), the name of the folders can and will be different. open each folder and when you come across a folder that has the ADB application, scroll down the folder until you reach the LETTER "R". you will then see a .zip file named "rom". copy that file onto the desktop or any other folder. rename it to ESPRIMG.ZIP.
10. format your SD CARD to FAT32. once the format is complete, copy/move the extracted rom/ESPRIMG.zip file into the sd card.
11. put SD card in the phone.
12. Hboot should then detect the esprimg file.
google for mt3srooter
---------- Post added at 06:11 AM ---------- Previous post was at 06:03 AM ----------
open folder u would find esprimg dat de file mt3gs
Thanks! I'll check this out. Unfortunately I returned the phone to its owner, I'll have to get it back to see if I can resolve his issue.
Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse
master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse
master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse
master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse
master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!
Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
stormsight said:
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
Click to expand...
Click to collapse
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
If not we turn our attention to your hboot. The error is because it is not updated enough to have that command. So we have two choices here. You can either upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom. Or you could create a Goldcard, flash a ruu that has the same hboot as the one you have. This should fix your rom and enable the phone to boot again.
In any event you will need to extract the rom.zip from whichever ruu you choose. To do that have a quick google search for a guide but its easy enough. After that rename the rom.zip to PC49img.zip and place it onto your sdcard, boot into hboot and allow it to flash it. The golcard process should be covered in one of my downgrade threads or one of the others from this forum.
Post back here if your having and trouble or need a hand
heavy_metal_man said:
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
Click to expand...
Click to collapse
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
heavy_metal_man said:
You can upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom.
Click to expand...
Click to collapse
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
heavy_metal_man said:
Or you could create a Goldcard
Click to expand...
Click to collapse
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
stormsight said:
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
Click to expand...
Click to collapse
All usb debugging is for is so that adb can reboot the device to hboot. If you google for how to extract the rom.zip from the ruu and then put it on the sdcard (after renaming it to PC49IMG.zip) and boot to hboot it is the same thing. Just without usb debugging needed.
You will need a micro sdcard adapter pal.
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
stormsight said:
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
good stuff pal.
when you are in clockworkmod recovery the controls are different. use the trackball to scroll and select. power button is now the back button.
I would recommend this custom rom as it is stable and has a stock vibe to it. just follow its install instructions and you should be good to go
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
stormsight said:
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
Click to expand...
Click to collapse
That suck man.
Hmmm. Slow boot times are normal on this phone to a certain degree. Usually 20secs to 3 minutes at first boot aftet rom flash.
Once the phone has booted up does the trackball still work? Could just be a damaged digitizer. They are fairly cheap these days. Look here http://m.ebay.co.uk/itm/281644653982 and here http://m.ebay.co.uk/itm/281644653982 fairly straight forward to install, but you could buy a used version of the phone for £30 minimum so its up to you
Edit: although, on reflection 15 boot time and constant reboots are not a good sign. I was hoping it was a software issue. If the trackball is functional you could go into settings, enable usb debugging and then get a logcat. That would at least give us somewhere to work from :-/
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
stormsight said:
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
Click to expand...
Click to collapse
Lol! Well at least thats a plus :-/ theres not much else we can do here. We could try to enable usb debugging fron within clockworkmod by editing the build.prop and see if we can get a logcat but if the phones just locking up we might not even get one :-/