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 :-/
Related
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 ,
I have an HTC who planted and I can not do anything.
I try to put a zip on the memory card but nothing about it. RUU does not work on htc, bug at the time of restart in bootloader: s
BRAVO UNKNOWN SHIP S-ON
HBOOT-0.75.0000
TOUCH PANEL-SYNT0101
RADIO-4.05.00.11
Mar 5 2010,21:12:15
I can't do a Goldcard i don't know why, and change cid does not work because it is not recognizing the command "writecid"
Pleas help because i have no warranty now, so I can not send it to HTC
Use the 2.3.3 RUU
Which RUU is
EDIT: I found one in htcdev
Mixyde said:
Which RUU is
EDIT: I found one in htcdev
Click to expand...
Click to collapse
Instead of asking straight away try to do some searching, it helps.
I have the same problem with 2.33 : it gets stuck in waiting for bootloader , the phone get black screen and few second later : ERROR [171] : USB CONNECTION ERROR
EDIT: The logo Boot have change : I have black screen with HTC in grey
EDIT2 : after reboot because it still stuck int boot logo, the original boot came back
Mixyde said:
I have the same problem with 2.33 : it gets stuck in waiting for bootloader , the phone get black screen and few second later : ERROR [171] : USB CONNECTION ERROR
EDIT: The logo Boot have change : I have black screen with HTC in grey
EDIT2 : after reboot because it still stuck int boot logo, the original boot came back
Click to expand...
Click to collapse
So it's back to normal?
And for your USB connection error I'm guessing you weren't in fastboot.
Turn off the phone, hold BACK and POWER, then run the RUU with the phone plugged in.
No, nothing back to normal, I always was in fastboot, and when it says: reboot to bootloader, then the screen get black and nothing ..then ERROR [171]
look at my guide and using a RUU without usb
I tried and I get a message that passes very quickly, and I can not create GC.
I am in this situation [2]ADVANCED BOOT PROBLEMS S-ON
Mixyde said:
I tried and I get a message that passes very quickly, and I can not create GC.
Click to expand...
Click to collapse
you don't need to with the 2.3 update, are you sure you're doing this right?
Yes, and with the 2.3 update I juste have a .cab, not a rom.zip
EDIT: Sorry, I haven't seen the good directory
I placed the rom.zip in the root of my SD, and I renamed in PB99IMG.zip, I then placed the SD in the Desire and VOLDOWN + POWER ... and nothing
Okay I have absolutely no idea what on earth you're doing to your phone, so before you break it:
Download this
Extract the rom.zip and rename to PB99IMG.zip
put it on the root of your sd-card (NOT in any folders)
poweroff, hold VOLUME DOWN & POWER
when it asks to update, select yes.
After the bootloader, I have the fast message that the phone did not found a file or a wrong file
Well, this is weird, really don't see why it doesn't work..
You can try one more thing, make a goldcard (use this to get CID [copy without commas, spaces. Just letters/numbers], then follow this tutorial, and skip the part where they get the CID using the phone)
Then download this PB99IMG.zip and try it with that.
....Nothing, always the same quick message.
Mixyde said:
....Nothing, always the same quick message.
Click to expand...
Click to collapse
and you tried running the RUU from the PC in fastboot mode? I dunno, there's nothing else you can really try... if PB99IMG doesn't work and RUU doesn't work there are no other options...
Backup your sd-card, format it, then put the PB99IMG.zip on it, then try it one last time.. otherwise I dunno send it to HTC
Nothing works, so i will try to find a friend who had a Desire to help me doing a GC , now I have a Brick
Mixyde said:
Nothing works, so i will try to find a friend who had a Desire to help me doing a GC , now I have a Brick
Click to expand...
Click to collapse
I just said how to make a goldcard without a phone.. use the program to get the CID and then continue the tutorial without the phone (use an sd adapter)
Don't know whether it'll do you any good though..
By the way are you using the original cable when running the RUU?? sometimes it doesn't work if it's not.
Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.
Hi guys. Sorry if this is a repost but... i cant find anything useful..to help with my problem...
So i have this HTC Wildfire Buzz... The first wildfire ever made, and it gets stuck in bootloader, I cant change options with volume keys, i cant do nothing. It freezes up in bootloader, i cant even turn it off. i need to take out the battery to turn off the phone..
What to do? I dont know how to install a RUU and which one. Please help?
BUZZ PVT SHIP S-OFF
HBOOT--1.01.0001
MICROP-0622
TOUCH PANEL-ATMELC03_16AC
RADIO-3.35.20.10
Nov 17 2010
Try update with PD98IMG ZIP find something like that, put it on sdcard and boot to HBOOT it should start updating ROM.
throw183 said:
Hi guys. Sorry if this is a repost but... i cant find anything useful..to help with my problem...
So i have this HTC Wildfire Buzz... The first wildfire ever made, and it gets stuck in bootloader, I cant change options with volume keys, i cant do nothing. It freezes up in bootloader, i cant even turn it off. i need to take out the battery to turn off the phone..
What to do? I dont know how to install a RUU and which one. Please help?
BUZZ PVT SHIP S-OFF
HBOOT--1.01.0001
MICROP-0622
TOUCH PANEL-ATMELC03_16AC
RADIO-3.35.20.10
Nov 17 2010
Click to expand...
Click to collapse
you need to take out the sdcard. the bootloader is failing because the stuff on it is too large or its a dud card.
using a different sdcard go to the "how to downgrade from hboot 1.02.0000 to hboot 1.01.0001" thread in the general section and download the package. open it and rename the 1.01.zip to pc49img.zip (making sure its not.zip.zip) and then put it onto the sdcard. put that into the phone and reboot to bootloader. assuming all is well it will find the "update" and ask you to flash it. select volume up to flash. wait for complete install and full reboot into stock rom. job done
nop didnt work, any other idea??????
i rename the 1.01.zip to pc49img.zip and then i put it into the sdcard
i start the phone holding the "down volume" boot into bootloader mode after 3 sec started
searching image.. image not found..image not found..image not found..
and back to bootloader without can move any button.
i'm 6 hours trying to find a solution even adb i tried but this not founding device cause i cannot debug usb.
plz HHhhheeeeelp
angelos83gr said:
i rename the 1.01.zip to pc49img.zip and then i put it into the sdcard
i start the phone holding the "down volume" boot into bootloader mode after 3 sec started
searching image.. image not found..image not found..image not found..
and back to bootloader without can move any button.
i'm 6 hours trying to find a solution even adb i tried but this not founding device cause i cannot debug usb.
plz HHhhheeeeelp
Click to expand...
Click to collapse
Your sdcard is incompatible (make sure its a genuine card, like sandisk ect and is preferably under 4gb) or you have renamed it to pc49img.zip.zip, if you are using windows search on Google for how to enable file extensions and see if its named zip.zip
Sent from my HTC Sensation using Tapatalk
im not that rookie
the file extension is correct.
and the sd card is 2gb from my other mobile(st15i)
Also, just because your card came from another phone and is 2gb does not mean a htc bootloader will like it. Sometimes they just reject reading from some cards. Nothing wrong with them other than the hboot simply not liking them. Try a different card if possible.
Please do not post private correspondence in public. Especially in the manner that it did. Please be patient when asking quesitons, as others do have personal lives and cannot respond instantaneously.
Hi,
I just have the exact same pb (except my HBOOT is 1.01.0002 and it is branded Bouygues). I had no SD card in my phone. At first I thought it was hardware because I found some other thread saying that this could be a short circuit resulting in power + vol down behing hold at all time, hence the bootloader and kesy not responding but it turns ou it was not it... So hope for you I guess.
* I download a RUU : RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
* plugged the phone without battery
* put battery in (which resulted once again in bootloader screen)
* waited for the device to be installed on my computer
* after that I run the RUU.exe which wipped user data, did some other stuff... (meanwhile the screen went from bootloader to HTC) and at some point the instalation failed with a error 131 id client (because the version was older than the one installed on the phone)
* after that the phone restarted normally and everything is fine now
well, nevermind..
It works as long as I don't turn off the phone.... This is driving me nuts. I managed to downgrade the HBOOT to 1.01.1001, gained S-OFF with revolutionnary (couldn't install clockwork recovery though). I even run the RUU successfully but if I turn off the phone, next time I power it on, I end up on the bootloader screen and power and volume buttons are not working.
[Edit] I found more info in this thread http://forum.xda-developers.com/showthread.php?t=2354199#post58713960.
Instead of running the RUU, I can skip the bootloader by simply running the command :
fastboot reboot
I don't want have to do this every time I turn off my phone to make it work again. So, I'm still looking for a more definitive fix.
heavy_metal_man said:
Hmm. When your in your stock rom does the volume buttons work?
Click to expand...
Click to collapse
Actually I managed to solve this 2 days ago (I am pretty sure I already posted to say that, can't find the reply though) by copying a CMW 5.0.2.8 PC49IMG.zip (http://www25.zippyshare.com/v/70647552/file.html) file in my sdcard and inserting it in the phone.
I could boot the phone in normal mode without going through bootloader screen (even without flashing anything...).
After I restarted to bootloader (willingly this time) keys were working, it prompted for the update, so I could install CMW and after CM 7.
So everything is fine now thank you.
Fatsebz said:
well, nevermind..
It works as long as I don't turn off the phone.... This is driving me nuts. I managed to downgrade the HBOOT to 1.01.1001, gained S-OFF with revolutionnary (couldn't install clockwork recovery though). I even run the RUU successfully but if I turn off the phone, next time I power it on, I end up on the bootloader screen and power and volume buttons are not working.
[Edit] I found more info in this thread http://forum.xda-developers.com/showthread.php?t=2354199#post58713960.
Instead of running the RUU, I can skip the bootloader by simply running the command :
fastboot reboot
I don't want have to do this every time I turn off my phone to make it work again. So, I'm still looking for a more definitive fix.
Click to expand...
Click to collapse
Hmm. When your in your stock rom does the volume buttons work?
You can install clockworkmod recovery by using fastboot commands pal. If your on your stock rom and dont have advanced reboot you can download an app called quick reboot and use that to reboot. We need to work out if its your volune buttons that are broken or not. If they are we may be able to replace them, or worst case senario we can disable them.
Sent from my LG-D802 using Tapatalk
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...