Hi all,
Im having a little trouble with my dhd. It won't boot up !
I can get into HBOOT, but thats it. (ie. no recovery CWM)
When trying to boot normally it hangs at spash screen.
so far i have tried:
- fastboot flashing (system.img dosn't flash (for known reasons))
- this thread (http://forum.xda-developers.com/showthread.php?t=841890) (tried with 2 different RUUs)
everything seemed to go according to plan, but still exactly the same problem.
- I've even tried flashing back the stock spash screen via fastboot in preperation to send it back to tmobile/htc to fix BUT, despite fastboot telling me flashing was succsessful, i still have my custom splash!
- pulling my hair out!
ive got eng hboot s-off radio s-off supercid and stuff??
my hboot info screen looks like this:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-boot
Oct 11 2010, 12:44:14
SYSTEM INFO
SN-HT0CPRX05836
LCD-SHARP
TOUCH PANEL-SYN3KT_0108
Commit-7eafc656
OS ver.-1.39.110.1
IMEI-
CID-11111111
RAM-768MB
eMMC-Sandisk 2223MB 4554751sectors
Thanks in advance to anyone with ideas
Which cw recovery is installed?
Sent from my Desire HD using XDA App
First question, what did you do immediately before you turned you DHD off, hence the reboot?
From the bootloader can you enter fastboot? You should be able to flash recovery from there. You mention "for known reasons" what are these?
Hi pwraggcan,
I'm not too sure? and I'm not sure how I can check either, as I can only enter hboot/fastboot.
AndyHarney,
As far as I can remember I was using my phone as normal. (no risky installs/flashes to speak of). Then overnight it ran out of battery, and now won't boot up .. ?
fastboot flash system system.img returns:
sending 'system' (410134 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
fastboot flash recovery recovery.img returns:
sending 'recovery' (8701 KB)... OKAY [ 1.494s]
writing 'recovery'... OKAY [ 0.837s]
finished. total time: 2.331s
but when I choose 'RECOVERY' form hboot menu it still hangs on splash.
jason9 said:
Hi pwraggcan,
I'm not too sure? and I'm not sure how I can check either, as I can only enter hboot/fastboot.
AndyHarney,
As far as I can remember I was using my phone as normal. (no risky installs/flashes to speak of). Then overnight it ran out of battery, and now won't boot up .. ?
fastboot flash system system.img returns:
sending 'system' (410134 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
fastboot flash recovery recovery.img returns:
sending 'recovery' (8701 KB)... OKAY [ 1.494s]
writing 'recovery'... OKAY [ 0.837s]
finished. total time: 2.331s
Click to expand...
Click to collapse
So you have recovery, and you're rooted, well I'd say install a ROM as ROMS flash system, boot and cache img files. Sending a 410mb file ofver adb seems a bit risky. Also, if you have no ROMs on the SD Card go into recovery, mounts and storage and at the bottom is usb or something.
MrYuiM,
I don't mean to act the fool, but I don't fully understand you're post.
"well I'd say install a ROM as ROMS flash system, boot and cache img files"
not sure how I can go about doing this? using fastboot?
"Also, if you have no ROMs on the SD Card go into recovery"
which ROMs do you mean? I have on my sdcard "LeeDrOiD_HD_V1.5.1.zip" and others. I also have some nandroid backups.
Currently, I have not found a way to enter recovery..
P.S I apologize for spewing my ignorance all over this thread.
Get PD98IMG.zip from my downgrade guide, put it into your SD card and go to the bootloader. Then tell us what what happens.
By the way, you still have fully warranty despite the fact that your device has S-OFF. There is nothing about software mods in warranty terms. For example mike1986 sent his phone to HTC's service center, it was S-OFF and it even had a custom ROM in it, and they did not complain.
jkoljo said:
Get PD98IMG.zip from my downgrade guide, put it into your SD card and go to the bootloader. Then tell us what what happens.
By the way, you still have fully warranty despite the fact that your device has S-OFF. There is nothing about software mods in warranty terms. For example mike1986 sent his phone to HTC's service center, it was S-OFF and it even had a custom ROM in it, and they did not complain.
Click to expand...
Click to collapse
When I asked HTC they were pretty stern on the fact that rooting voids their warranty despite it not being in the guidelines :/
jason9 said:
MrYuiM,
I don't mean to act the fool, but I don't fully understand you're post.
"well I'd say install a ROM as ROMS flash system, boot and cache img files"
not sure how I can go about doing this? using fastboot?
"Also, if you have no ROMs on the SD Card go into recovery"
which ROMs do you mean? I have on my sdcard "LeeDrOiD_HD_V1.5.1.zip" and others. I also have some nandroid backups.
Currently, I have not found a way to enter recovery..
P.S I apologize for spewing my ignorance all over this thread.
Click to expand...
Click to collapse
To enter recovery turn your phone off completely and plug it into the charger, recovery will auto open. Also, everyone starts off somewhere.
But go with jkoljo first as he is more experienced
Hi jkoljo,
Downloading now,
It's also a big relief to hear that software modding dosn't effect warrenty *phew*
jason9 said:
Hi jkoljo,
Downloading now,
It's also a big relief to hear that software modding dosn't effect warrenty *phew*
Click to expand...
Click to collapse
Good luck mate, report back on how it goes
Might be futile but you could try a different recovery. If you're s off it should work. Try a 2.x.x.x then a 3.x.x.x. flashing from fastboot, it could be that. If the pd98img doesn't work then it might be a faulty motherboard and htc will have to fix it.
Sent from my Desire HD using XDA App
I tried jkoljo advice, but still no dice! ... (hey that rhymes!)
One thing I noticed as it was checking SD card: -
SD Checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
are those errors normal?!
just to clarify, after jkoljo's PD98IMG.zip update, I reboot and it hangs at my custom spash screen, just as before.
It's as if I hadn't tried to update/recover at all!
Anyways, Thankyou all for your help, assistance and advice.
I have to go out now, but ill be back tomorrow to try again.
It seems that you have to format your SD card. Do a full format to FAT32 (no quick format), and try it again.
Ok, formatted and tried again.
But same results as my last post.
I even tried with 2 SD's (4gb + 8gb).
Does this mean my phone is not recoverable..?
....I hope not..
oopes, delete this post please
pwraggcan said:
Try flashing a different recovery while in fastboot.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Could you recommend one?
The only one I've ever known is CWM.
Also I don't have much faith in fastboot right now.
When I flashed my stock splash, it said 'OK' but never changed!
Thanks pwraggcan
Try flashing a different recovery while in fastboot.. Try the stock one first and if you can boot into recovery wipe data/factory reset.
fastboot flash recovery nameofrecovery.img
recovery zip attached. good luck.
Thanks for the suggestion pwraggcan,
I tried that recovery.. and it flashed 'OK' but still no change from my previous attempts.
Soo... Shall I call this a write-off and let HTC deal with it..
Or are there any last ditch solutions I could be trying.
Jason9
As a last resort try the attached recovery. If this recovery doesn't work it's gotta be a hardware issue. I'm thinking if you backed up with a 2 series cw recovery then updated the recovery with rom manager to a 3 series cw recovery it won't let restore the backup. So, try the attached and fingers crossed, you're up and running. Probably won't sort it but definitely worth a try.
Related
Have been getting this error of late after i run unrevoked, then when i go to recovery to flash rom i get this error...is there any solution to this, or is there a new version of unrevoked to solve this porblem? Im using unrevoked v3.32.
Thank you.
Phone details? recovery version? Which Rom?
davebugyi said:
Phone details? recovery version? Which Rom?
Click to expand...
Click to collapse
Unfortunately i gave the phone back to a friend who need help, so cant provide any info
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
lowkey1979 said:
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
Click to expand...
Click to collapse
Do you have a pvt4-desire? If, you have to flash amonra-recovery, because cwm is incompatible with pvt4-desires.
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
ghalalb said:
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
Click to expand...
Click to collapse
Can you tell me how to flash recovery with fastboot?
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
MatDrOiD said:
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
Click to expand...
Click to collapse
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
andrew21 said:
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
Click to expand...
Click to collapse
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
hi mates,
to flash recovery with fastboot need to be s-off.
the command are really simple.
boot in hboot, select fastboot (shoul see fastbbot usb on the phone screen)
open a command line
Code:
fastboot flash recovery c:/wheretefileis/yourecovery.img
MatDrOiD said:
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
Sir,
I tried this method but i get a "flash_image: not found". It seems like i don't have the flash_image command on my phone. I've looked everywhere to find a way to get that command and i found this - http://www.villainrom.co.uk/forum/s...)
finished. total time: 1.094s
Thank you sir
chage a sd card for try!
zk7513153 said:
chage a sd card for try!
Click to expand...
Click to collapse
Already did change the sdcard sir.
On another note, whenever i tried remounting the /system for RW access to copy flash_image, free space drops to Zero Kb. To isolate, i tried remounting to just Read access, free space remained the same. Anything I'm missing here, or do I really have to S-OFF my phone before I can make changes on my /system ?
Thank you very much.
nonofficialcover said:
I also tried flashing via ADB and I get this:
C:\fastboot flash recovery c:\recovery-RA-desire-v2.0.1.img
sending 'recovery' (3936 KB)...
OKAY [ 0.687s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.094s
Thank you sir
Click to expand...
Click to collapse
For this part I think you need to disable signature verification in recovery.
I was able to solve my problem after I did S-OFF.
UPDATE: Still no solution found - new Ideas very welcome.
Hi there,
I'm at the end of my wits with my HOX which is with a german o2 branding. After getting stuck in bootscreen after athe OTA-Update from 1.26.207.2 to 1.28.207.9 - which failed for some reasons. I tried to install different Custom-Roms, none of which would boot beyond the first HTC-Screen.
The latest one I tried was Cyanogenmod, that did boot fully but I got constant "andoidupi crashed" messages, so I tried to reflash it.
After that things got weird, because right now I can't really do anything anymore. If I try to relock it via "Fastboot oem lock" it just reboots and it boots straight into CWM 5.8.3.1 but when I get back to bootloader its still "**** UNLOCKED ****"
I can flash boot.imgs via fastboot flash... but even so its says at the command prompt that it was successful flashed, it really isnt. No matter what - at reboot I will boot into CWM.
It is like working on a virtual machine - the HOX gives all the right responses, but noting I try to flash is permanent.
I can't relock, I can't flash new recoverys, can't flash new boot.img and everything I push onto the SDCARD via adb is gone after reboot. If I delete a file that is actually on the SDCARD it will be back after reboot, like it was never really deleted.
I already checked my drivers, switched off Antivir, tried it on a different PC, reinstalled the drivers etc etc.
My HOX is from German o2
I've got HBOOT 0.94.0000 and Radio 1.1204.90.13
If anyone has any suggestions besides "You have to fastboot flash recovery/boot..." and "Don't forget to erase cache after every flash" I'd be very thankfull
Best regards,
Thad
did you try to re-download your fastboot ?
and did you navigate on CMD to the right place where your fastboot folder is stored ?
You need to flash the stock recovery before you relock your bootloader.
Flash stock recovery
Relock bootloader
Install ruu
Hope this helped
EDIT: Just read your post again and you said you've tried flashing recoveries, sorry, its late here
Sent from my HTC One X using xda premium
i made a compilation of threads about this matter, it might help you. check it out..
http://forum.xda-developers.com/show....php?t=1692681
Thanks for all suggestions on the topic
@muamers
I redownloaded fastboot multiple times, but its all the same, sadly The problem is: It seems to work. I get all the right replies on the command prompt, but after rebooting nothing is flashed.
@mikey0105
The link goes to a 404 page - could you post it again?
Thank you
tadeausz said:
Thanks for all suggestions on the topic
@mikey0105
The link goes to a 404 page - could you post it again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1692681
Thank you Gibeon & mikey0105
I retried all the steps there, but still no change.
The problem still is the same. This is what I get in response:
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.044s]
finished. total time: 0.045s
>fastboot flash boot boot.img
sending 'boot' (4156 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.470s]
finished. total time: 1.008s
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.034s
>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
sending 'recovery' (5760 KB)...
OKAY [ 0.829s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.548s]
finished. total time: 1.377s
So everything should've worked out great. But not so, because in reality he really hasn't flashed anything to the HOX permanently. When I reboot to recovery I still have the OLD CWM without fixes. The boot.img isn't flashed either.
As I said: It's like working on a virtual machine, where nothing really has any effects, it's a if all the fastboot commands only affect the RAM but are not really flashed to Memory.
And I still can't relock, still can't reboot-bootloader from Bootloader.
Any other ideas are welcome...
Greetings,
Thad
Bump.
Nobody any more ideas?
Bump. Still no solution after many month
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
robchongke said:
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
tadeausz said:
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
Click to expand...
Click to collapse
are you doing
fastboot flash recovery recovery.img
Or
fastboot boot recovery.img
I'm not sure the second one works, but if it did, it would do what you describe. So do the first.
help
I'm running ICJ ROM AOKP. last time I flashed this rom and flashed the gapps too,
Now I want to install a new package of gapps, SO, do I need to wipe data, cache, dalvic cache to install the gapps ???
Note that I'm going to install ONLY the gapps...
THANKS
aimen7 said:
i'm running icj rom aokp. Last time i flashed this rom and flashed the gapps too,
now i want to install a new package of gapps, so, do i need to wipe data, cache, dalvic cache to install the gapps ???
Note that i'm going to install only the gapps...
Thanks
Click to expand...
Click to collapse
That's the third time I've read this question from you.
STOP POSTING IT NOW!
BenPope said:
That's the third time I've read this question from you.
STOP POSTING IT NOW!
Click to expand...
Click to collapse
sorry, I'm CONFUSED about that
Aimen7 said:
sorry, I'm CONFUSED about that
Click to expand...
Click to collapse
Make 1 new thread or search....don't go posting it in every Q&A thread !
That is confusing ! :thumbdown:
I have a Verizon ADR6350VW HTC Incredible 2. I decided to 'upgrade' it to a new ROM.
I unlocked the boot loader and installed ClockwrkMod Recovery v5.0.2.0
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011,12:39:36
I tried putting an incredible 2 ROM (Viper) and since then it won't fully boot, it gets stuck forever on the green HTC logo on the white background.
I can get to the bootloader, and tried reflashing the same or other downloaded ROMs (all meant for the HTC incredible 2). Without much luck.
The original flashing process was not interrupted. I did a lot of googling and reading (but missed the S-ON/S-OFF part originally), and have tried many different ways to get out of this without luck.
3rd party ROM will flash and complete the process (but still won't boot), Verizon ROMs will give me an error (cannot open flash, bad). I did check the md5 checksums on ALL the files I used, and tried flashing from adb to no avail.
Before anyone asks, Yes I do clear the data, cache and Dalvik cache before flashing. I am at a loss of what to try next, short of finding someone reputable online to do it for a fee.
Thanks,
Wahran
wahran99 said:
I have a Verizon ADR6350VW HTC Incredible 2. I decided to 'upgrade' it to a new ROM.
I unlocked the boot loader and installed ClockwrkMod Recovery v5.0.2.0
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011,12:39:36
I tried putting an incredible 2 ROM (Viper) and since then it won't fully boot, it gets stuck forever on the green HTC logo on the white background.
I can get to the bootloader, and tried reflashing the same or other downloaded ROMs (all meant for the HTC incredible 2). Without much luck.
The original flashing process was not interrupted. I did a lot of googling and reading (but missed the S-ON/S-OFF part originally), and have tried many different ways to get out of this without luck.
3rd party ROM will flash and complete the process (but still won't boot), Verizon ROMs will give me an error (cannot open flash, bad). I did check the md5 checksums on ALL the files I used, and tried flashing from adb to no avail.
Before anyone asks, Yes I do clear the data, cache and Dalvik cache before flashing. I am at a loss of what to try next, short of finding someone reputable online to do it for a fee.
Thanks,
Wahran
Click to expand...
Click to collapse
1st recommendation: go s-off
2nd recommendation: flash the boot img from the rom in fastboot...I don't know the exact process because I am s-off, but it is discussed in many of the development threads, so now you know what terms to search for at least.
gtdtm said:
1st recommendation: go s-off
2nd recommendation: flash the boot img from the rom in fastboot...I don't know the exact process because I am s-off, but it is discussed in many of the development threads, so now you know what terms to search for at least.
Click to expand...
Click to collapse
Thank you for your reply.
Going S-OFF: I tired, most guides online will show you how to do by going to the OS first (and enabling USB debug). The only one I found from Revolutionary involved doing it from the adb. When I boot into ClockwrkMod, I can run adb just fine (doing adb devices returns the correct S/N amongst other things), but revolutionary tool complains it can't find the device.
I will google again your second recommendation.
wahran99 said:
Thank you for your reply.
Going S-OFF: I tired, most guides online will show you how to do by going to the OS first (and enabling USB debug). The only one I found from Revolutionary involved doing it from the adb. When I boot into ClockwrkMod, I can run adb just fine (doing adb devices returns the correct S/N amongst other things), but revolutionary tool complains it can't find the device.
I will google again your second recommendation.
Click to expand...
Click to collapse
From Nitsuj17 in the viper thread post 2:
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
The process will be the same for any rom as long as you are dev unlocked.
gtdtm said:
From Nitsuj17 in the viper thread post 2:
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
The process will be the same for any rom as long as you are dev unlocked.
Click to expand...
Click to collapse
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
wahran99 said:
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
Click to expand...
Click to collapse
I'm really guessing here, but try fastboot flash boot boot.img
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
wahran99 said:
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
Click to expand...
Click to collapse
Try this one. The author includes 2 ways to flash boot.img
http://forum.xda-developers.com/showpost.php?p=22639929&postcount=1
gtdtm said:
I'm really guessing here, but try fastboot flash boot boot.img
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
Try this one. The author includes 2 ways to flash boot.img
http://forum.xda-developers.com/showpost.php?p=22639929&postcount=1
Click to expand...
Click to collapse
fastboot flash boot boot.img worked without error, then I followed it with "fastboot reboot", it took about 15mn, but now it's booted to the SIM unlock screen (that would be my next step).
Thank you very much for all your help! I just registered today to these forums, I see a thank you meter next to the avatar, but can't see I way to 'officially' click and thank you, I will look again....
wahran99 said:
fastboot flash boot boot.img worked without error, then I followed it with "fastboot reboot", it took about 15mn, but now it's booted to the SIM unlock screen (that would be my next step).
Thank you very much for all your help! I just registered today to these forums, I see a thank you meter next to the avatar, but can't see I way to 'officially' click and thank you, I will look again....
Click to expand...
Click to collapse
I'm glad you got it going. You'll probably want to remember that method since you'll have to do it any time you flash a rom.
gtdtm said:
I'm glad you got it going. You'll probably want to remember that method since you'll have to do it any time you flash a rom.
Click to expand...
Click to collapse
Since I posted that message, I had to put back the Verizon stock ROM, so I can SIM unlock the phone (apparently you cannot use the unlock code with a 'cooked' ROM, something I didn't know), and while doing that, HBOOT got downgraded to 0.97, which allowed me to S-OFF the phone with revolutionary. I got the phone SIM unlocked and put back the Viper ROM on it.
In summary, learning from my mistakes, and if I am not mistaken:
1. If you plan to SIM unlock the phone, do it while it is still on stock firmware, it will save you a lot of time and headaches.
2. If you are unlocking the boot loader, S-OFF the phone as well (and put Clockworkmod on it as well), it would make life a lot easier.
3. Then you can go an experiment with ROMs....
gtdtm: Thank you again for your help and patience, and most importantly for keeping me going, as I was about to give up on this phone.
Wahran99
wahran99 said:
Since I posted that message, I had to put back the Verizon stock ROM, so I can SIM unlock the phone (apparently you cannot use the unlock code with a 'cooked' ROM, something I didn't know), and while doing that, HBOOT got downgraded to 0.97, which allowed me to S-OFF the phone with revolutionary. I got the phone SIM unlocked and put back the Viper ROM on it.
In summary, learning from my mistakes, and if I am not mistaken:
1. If you plan to SIM unlock the phone, do it while it is still on stock firmware, it will save you a lot of time and headaches.
2. If you are unlocking the boot loader, S-OFF the phone as well (and put Clockworkmod on it as well), it would make life a lot easier.
3. Then you can go an experiment with ROMs....
gtdtm: Thank you again for your help and patience, and most importantly for keeping me going, as I was about to give up on this phone.
Wahran99
Click to expand...
Click to collapse
No problem. Next challenge: Put TWRP on it instead of Clockwork.
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Did you make a Gold card before placing PG76IMG in SD card?
tahaice said:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Click to expand...
Click to collapse
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
varun26296 said:
Did you make a Gold card before placing PG76IMG in SD card?
Click to expand...
Click to collapse
thanks for reply
i did not make a gold card.. my phone crashed on me without consent lol..
and i cannot make one now coz there is no shell or rom on my phone.. just bootloader and thats it..
unless there is a way around to make a goldcard via fastboot menu??
heavy_metal_man said:
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
tahaice said:
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
Click to expand...
Click to collapse
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
heavy_metal_man said:
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
tahaice said:
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
Click to expand...
Click to collapse
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
tahaice said:
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
Click to expand...
Click to collapse
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
heavy_metal_man said:
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks for your help heavy metal.. seems i am left with a dead fone after all RIP :crying:
omnomnomkimiiee said:
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
Click to expand...
Click to collapse
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
im sorry for your loss man what do you think you will do with the device? bin?
Recover soft-bricked HTC Wildfire S
tahaice said:
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
Click to expand...
Click to collapse
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Click to expand...
Click to collapse
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
heavy_metal_man said:
im sorry for your loss man what do you think you will do with the device? bin?
Click to expand...
Click to collapse
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
bolzass said:
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
Click to expand...
Click to collapse
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
BY THE WAY I CANNOT ERASE USERDATA
it says FAILED (remote: not allowed)
can this be causing other errors???
tahaice said:
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
Click to expand...
Click to collapse
At this point its probably for the best
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
tahaice said:
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
Click to expand...
Click to collapse
Ops!?!?..., Can you detail these errors?.
I'm also reading your message bellow about erasing Userdata...:$, detail also this scenario so we can think about your concret issues.
Keep fighting till you're sure there's nothing to do...
I've been trying to flash an AT&T HTC One M8 with the GPe ROM found here: http://forum.xda-developers.com/showthread.php?t=2706441
I've used this guide and everything went fine: http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
I was in the TWRP Recovery and wanted to format the internal sd card for a fresh start, so I formatted. Afterwards I was unable to get back into the recovery, for some reason I can't erase or format recovery using fastboot, erasing the cache and flashing the recovery image again only brings me to a flickering TeamWin screen, then tries to normally boot but nothing is there for it to boot into so it just sits in a boot loop.
I've tried Philz recovery as well. That works for a little bit but after 10-15 seconds the phone tries to boot normally again and I get stuck in the boot loop.
I tried running `fastboot oem rebootRUU`, that brought me to a black HTC screen and gave me the ability to use fastboot. In RUU mode, I erased the cache again and reflashed the recovery, then erased the cache again and rebooted to fastboot. Tried to boot into Recovery and was greeted with the flickering TeamWin logo and a boot loop.
Can anyone give me a hand here?
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I'm trying that now, will post back with results
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
JustLikeThat said:
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
Click to expand...
Click to collapse
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
JustLikeThat said:
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
Click to expand...
Click to collapse
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
JustLikeThat said:
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
Click to expand...
Click to collapse
if you are able to do fastboot commands.. try using the firewater s-off http://firewater-soff.com/instructions/
you may not be to do this either since you said you don't have adb. Can't help you beyond here.. If you are able to get to RUU mode.. I would suggest trying flashing RUUs since they are most comprehensive.
Did you try flashing the sense RUU?
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
Using Philz, I see that it can't mount or open anything in `/cache/`... I'm guessing that that's because I wiped the internal storage with TWRP initially. Is there anyway I can mount my phone and add the directories manually?
It really sounds like I need access to ADB but I can't run anything because nothing can mount the internal storage.
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
I've tried that now. It looks as if it's trying to boot but then I just end up back in the bootloader. I'll try with a different image.
In the mean time: I had managed to get Philz CWM formatting the storage properly (with /system, /data, etc), and without any errors that it couldn't mount /cache/recovery (because I had managed to format /cache manually before it rebooted). It's still rebooting 10-15 seconds after booting into recovery, even in the middle of formatting...
I have done more exploring in between reboots and it doesn't look like there's an `/sdcard` directory that it can mount either
umjammerlammy said:
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
Click to expand...
Click to collapse
Nothing, since it was wiped earlier.
JustLikeThat said:
Nothing, since it was wiped earlier.
Click to expand...
Click to collapse
Try flashing the recovery using the htc one all-in-one toolkit. see if that helps. I'm pretty much out of ideas beyond this point.
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
Restore a stock backup in twrp then flash the att ruu
If you are in the US message me your number and I can walk you through it
Sent from my HTC One_M8 using XDA Premium 4 mobile app
UPDATE
As mentioned in my initial post, I wiped/formatted my internal memory so I have no internal file structure.
My attempts at booting into or flashing a recovery are failing after 10-15 seconds since they can't mount to anything in the internal memory.
I'm stuck in Bootloader and it seems like the only tool I can utilize is `fastboot`.
I'm currently looking for a way to restore a file structure to my internal memory.
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
What about flashing the stock recovery and then trying a factory wipe?