Develop Bugs

Noob, May have bricked my phone :(

Okay so i am in desperate need of help!
I wanted to root my desire. I have the telstra next g A8183 Desire, i attempted to root it using this method:
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
Only to find out it doesnt work because apparently my phone has a bootloader of 0.80.
So i used a method on Xda;
http://forum.xda-developers.com/showthread.php?t=696189
I used the method for rooting an unlocked desire, with a gold card.
I got almost to the end, up to the step;
"In the command prompt/terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate"
However, my zip i downloaded didnt contain "'step2-windows.bat'"
which now has lead me to a problem where i am stuck on the 'recovery' screen.
Please can anyone help me, im afraid ive bricked my phone

Follow exactly what it says in that XDA thread, ignore what is says in the nimbu thread and download what the XDA thread tells you to download, you should be goldcarded and rooted in about 20 mins (not kidding) as i did this last night (difference being i didnt need a goldcard)
but again follow the XDA stuff and ignore the rest for now

i cant actually get my phone past the boot screen, it just hangs..
so i cant follow those steps!

can you get into bootloader??
Vol- + Power??

yes, but i dont know what to do from there..

put your phone into the bootloader and start again/resume
no harm is done if you can get into the recovery screen
you are hanging because you have formatted your system, this is meant to happen
now you simply flash the rooted rom
download the files needed to root your phone from here and complete step 2

cgrec92 said:
put your phone into the bootloader and start again/resume
no harm is done if you can get into the recovery screen
you are hanging because you have formatted your system, this is meant to happen
now you simply flash the rooted rom
download the files needed to root your phone from here and complete step 2
Click to expand...
Click to collapse
You took the words right out of my keyboard

i continue step 2 but i get an error message..
"Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes..
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu."

Are the files already on the SD???
What happens when you procede onto wipe and applying rootedupdate.zip?

all i have is a blank sd card in there at the moment, because i had to wipe my gold card, i cannot connect it to make another one.
BUT i re ran step 1 and now its going through a completely different process.
im pretty sure its flashing now, its saying stuff like
INFO[RUU] UZ, radio 05..
INFO[RUU] UZ, system 100
does that mea its flashing properly?

Okay ive pretty much gone through the process, however im up to the 'green' screen where i have to choose wipe.
which buttons do i use to select wipe? haha
i must sound like an idiot lol

See
Yeh wipe and format (or whatever it says) then flash from update.zip on SD
Simples!

Thanks so much for your help!! :

If we had a Karma or a Thanks Button on this forum feel free to click it for me

[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help

I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)

If you have CWM did you made a nondroid backup?

Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you

@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)

Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.

Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!

How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system

EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)

Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why

Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img

ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?

Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA

Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done

@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.

Can get to HBOOT, but dead end from there...

Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
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
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!

BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
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
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.

cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?

BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.

cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?

BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?

BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...

BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.

cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )

Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!

So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app

nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?

BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.

cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )

There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off

eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...

I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app

eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.

BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243

eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!

[Q] Can't wipe phone (GSM Galaxy Nexus)

I can't wipe my phone. So far I've tried:
Factory reset from Settings menu
Hard reset from recovery mode
fastboot -w
Flashing latest version of Yakju from Google
Locking and unlocking bootloader
Wiping from TWRP
Formatting userdata
In addition, I've tried uninstalling apps and removing files via adb shell. In both cases, the apps/files would return on reboot. (And the phone will reboot spontaneously when booted normally, although uninstalling some apps will make it take longer.)
Some background: I forgot to plug in my phone Friday night, and when I checked on it Saturday evening, it was dead. I plugged it into the wall charger, but it wouldn't charge. I poked around the charger port a bit, and got it working again. At 1/4 charge, I tried booting it, only to find that when doing a normal boot, it would stall at the Google start-up screen, while a recovery boot would show the dead android image with no text.
I had some more trouble getting it to charge, and ultimately damaged the USB port. (I got it replaced earlier today (Monday).) To fix the booting problem, I downloaded the latest yakju image from Google and tried flashing it. Not realizing that it would take 25 minutes to write system, I pulled the battery before that point. In spite of this, I was now able to boot the phone, even if it could no longer charge.
Today I got the USB port replaced, but found that the phone would crash every minute or so. I suspect that this is symptomatic of the larger problem of the phone not wanting to change from how it was Saturday morning when it died. No settings changes seem to stick. Every time I start up, I get the same SMS notification from Friday night. Deleted files are restored, and even my attempts to replace the recovery img with TWRP failed. (I managed to load it with fastboot boot, but it didn't do me much good.)
I've also run it through a successful flash of yakju, once I realized it would take half an hour to run. So far the only thing I can think of that I haven't tried is ODIN!
I have three sets of logs from logcat running up until the time of a crash, and the output of adb bugreport, if those are helpful.
Does anyone have any other suggestions?

I've attached the logs.
I've poked around a bit more, trying to get things working, or failing that, not working in a different manner. I started it up TWRP and ran a few tests. I uploaded the zipped image files to /sdcard, downloaded them again, and verified that result was identical. I used dd to copy the recovery partition to a file, grabbed it from the phone, and tried to use dd to copy TWRP over top. dd seemed to think it was successful, but grabbing the partition again, I get the same contents as before.
I'd assume it's something like the flash memory is never actually flushing its cache, so none of the changes I make get committed. I can run 'sync', and it will pause briefly if there was recent activity, but if I write data to a partition, unmount then remount it, the change is gone. If this is the case, I have no idea how I'd go about fixing it - the problem is sufficiently low level that the OS doesn't seem to be aware of it. If there are any tools available to test this, could you let me know?
At this point, I'm considering cutting my losses and getting a new phone.

Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent

ifly4vamerica said:
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
Click to expand...
Click to collapse
"userdata"
Sent from my Nexus

Yeah userdata! Thanks man.
G-Nexus Sent

alfedenzo said:
I can't wipe my phone. So far I've tried:
Factory reset from Settings menu
Hard reset from recovery mode
fastboot -w
Flashing latest version of Yakju from Google
Locking and unlocking bootloader
Wiping from TWRP
Formatting userdata
In addition, I've tried uninstalling apps and removing files via adb shell. In both cases, the apps/files would return on reboot. (And the phone will reboot spontaneously when booted normally, although uninstalling some apps will make it take longer.)
Some background: I forgot to plug in my phone Friday night, and when I checked on it Saturday evening, it was dead. I plugged it into the wall charger, but it wouldn't charge. I poked around the charger port a bit, and got it working again. At 1/4 charge, I tried booting it, only to find that when doing a normal boot, it would stall at the Google start-up screen, while a recovery boot would show the dead android image with no text.
I had some more trouble getting it to charge, and ultimately damaged the USB port. (I got it replaced earlier today (Monday).) To fix the booting problem, I downloaded the latest yakju image from Google and tried flashing it. Not realizing that it would take 25 minutes to write system, I pulled the battery before that point. In spite of this, I was now able to boot the phone, even if it could no longer charge.
Today I got the USB port replaced, but found that the phone would crash every minute or so. I suspect that this is symptomatic of the larger problem of the phone not wanting to change from how it was Saturday morning when it died. No settings changes seem to stick. Every time I start up, I get the same SMS notification from Friday night. Deleted files are restored, and even my attempts to replace the recovery img with TWRP failed. (I managed to load it with fastboot boot, but it didn't do me much good.)
I've also run it through a successful flash of yakju, once I realized it would take half an hour to run. So far the only thing I can think of that I haven't tried is ODIN!
I have three sets of logs from logcat running up until the time of a crash, and the output of adb bugreport, if those are helpful.
Does anyone have any other suggestions?
Click to expand...
Click to collapse
i have the exact same issue.. i cant wipe anything, after rebooting everything comes back to the phone, even if the flash or odin success, the same old files and OS come back again and nothing changes.
and as in your case, system take like 30 min to write, or even more.
i've tried fastboot erase userdata, fastboot erase system, etc, odin, format partitions from adb, toolkits, etc everything you can think of, and nothing works.
please, post if you fix your phone, because mine has been dead for a month atleast, id like to fix it but i dont know how.

ifly4vamerica said:
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I ran the commands just now:
Code:
$ ./fastboot devices; ./fastboot erase boot; ./fastboot erase system; ./fastboot erase userdata; ./fastboot erase cache 130 ↵
016B75D71500B013 fastboot
erasing 'boot'...
OKAY [ 0.006s]
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.007s]
finished. total time: 0.007s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.881s]
finished. total time: 1.882s
Then it just boots up into the same old. (I'd tried at least some of those earlier, but I couldn't remembe which ones.)

This happened on the incredible to one of my rom users. Emmc or hardware related most likely. Either way there's not much hope to fix it if the usual methods don't work.
Sent from my Galaxy Nexus using Tapatalk 2

can't wipe & phone powers down right after boot
Ok it looks like I have the same problem as alfadenzo, except when my Nexus finishes booting, I get a buzz, a red exclamation point in the battery icon, and a popup saying "battery is not charged, please plug in charger", and powers down.
I've flashed 3 or 4 different stock firmares via Odin.
I've flashed complete sytem img's via fastboot, first wiping everthing.
Despite all this, the same splash screen loads. I think its a from CM7
I've flashed cwm by itself via fastboot , but it doesnt stick. Instead I get the "exclamation point android" , and then the stock recovery which I cant do anything with.
I have *3* whole smacking batteries that I've used, allong with two seperate usb cables. One that came with the phone, and on that came with a different Nexus.
Is this a kernel or bootloader issue? Im all out of the options that I know of
Galaxay Nexus I505
Tuna
variant - toro
bootloader - primekk15
baseband I515 EK02 CDMA
carrier - none
Unlocked

Hi,
I am having the same issue. I tried everything. The recovery mode shows that partitions and files are erased/deleted. However, on next boot all comes live ! and my phone boots. but restarts within a few seconds!
When trying to flash using ODIN, the "system" update fails!
Anyone to help?

Hi, I'm having the same problem.
Have you found the solution??
I'm trying to
- Flash ROM from fastboot
- Flash TWRP from fastboot
- Erase partition from fastboot
- Go to recovery and delete all data in /sdcard using adb
- Trying to delete 1 widget from home screen and reboot
- Try to restore stock image using Odin, Fail in system.img
Nothing happened. My gnex boot like usual to the old home screen and nothing changed.
Then it reboot by itself.
Any ideas?

Same problems with me as I reported earlier! Some are saying that the internal memory has gone readonly and its permanent!
Do you think you can contact Samsung service for a solution? I have thought of so, but need to bring out some time for that.
rakun123 said:
Hi, I'm having the same problem.
Have you found the solution??
I'm trying to
- Flash ROM from fastboot
- Flash TWRP from fastboot
- Erase partition from fastboot
- Go to recovery and delete all data in /sdcard using adb
- Trying to delete 1 widget from home screen and reboot
- Try to restore stock image using Odin, Fail in system.img
Nothing happened. My gnex boot like usual to the old home screen and nothing changed.
Then it reboot by itself.
Any ideas?
Click to expand...
Click to collapse

sudiptochoudhury said:
Same problems with me as I reported earlier! Some are saying that the internal memory has gone readonly and its permanent!
Do you think you can contact Samsung service for a solution? I have thought of so, but need to bring out some time for that.
Click to expand...
Click to collapse
I haven't contact samsung service center yet. This is my old phone, it's already out of warranty so it might be costly.
I thought read only mode should give you an error message at least.
In this case, I'm feeling like using Deep Freeze but for Android

Looks like my gnex chip have emmc brickbug. I cannot check anymore using brickbug app checker because it always crashed after booting. But the symptoms is the same.
Still haven't found a way to fix it

Indeed sounds like a fried emmc. Sorry guys.
Sent from my Galaxy Nexus using XDA Free mobile app

On the same boat as you guys !
Same Scenario here ! :silly: ..... i got a GT-9250 brand new in box , was pulled out only once to try it out and it's in the EXACT same condition as mentioned by previous posters ! i have tried : Odin , fastboot flashes , Cyanogenmod Installer ( the one i had the most progress but failed as well ) , the regular reset procedure , nothing works ! its impossible to clean wipe the device !!! no matter what you do .... once the phone restarts , everything comes back again ! old apps , old data , old software !
I've read somewhere that the problem was related to the READ , WRITE permissions on the phone partitions , somehow .... and i know everyone of us come from different specific scenarios , but it may be worth to give it a try if someone knows how to help us out on that part because it makes sense, it seems the filesystem on the device is protected somehow and when we try to overwrite everything things go wrong ...
Too many people with that crazy issue without a solution , warranty claims or checks on that device are long gone blues ... so dont even think about it .... not with samsung or with the carriers ... its over for us , so we need to figure out a solution for this issue and get our devices back working properly ! :highfive:

HTC Desire 300 in boot loop

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...