Related
Hey guys,
I am trying to s-off my girlfriends Wildfire S.
MARVEL PVT SHIP S-ON RL
HBOOT-1.009.0099
MICROP-041
RADIO-7.57.39.10M
FEB 9 2012 18:29:31
I am following the directions from htcdev.com/bootloader
I got to the point where I am supposed to "get_identifier_token"
Now my phone is connected as it should be, I am in "fastoot usb".
Still, the only thing happens is that I get the following message in command prompt: "waiting for device". Nothing happens. I tried to restart PC and phone again: same problem.
Does anyone have an idea about what I'm doing wrong? I'm stuck.
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
szaboagoston said:
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
Click to expand...
Click to collapse
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
success
Karavasileiadis said:
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
Click to expand...
Click to collapse
Thanks a lot for the quick and professional answer. By the time I read it, I managed to root.
I used rezo609's all-in-one utility, which I found in at this location:
http://forum.xda-developers.com/showthread.php?t=1697985
I got the advice from this thread:
http://forum.xda-developers.com/showthread.php?t=1927757
I installed the Speeddroid ROM and data2SD as described here:
http://forum.xda-developers.com/showthread.php?t=1932534&highlight=data2sd+install
The result: so far everything working. It looks like a new phone!
stuck to root
Hi,
I have the same situation here.
But Which tool do you run of the [UTILITY]rezo609's All-In-One Utility ? (http://forum.xda-developers.com/showthread.php?t=1697985&page=3)
In the whole topic there is no how to.
I managed to unlock the bootloader, and clockwork recovery is also on there.
I just want to root the phone (not to put an other rom)
Thanks in advance,
dear all
i am using GN 4.2.2 stock
at the moment i can go to fastboot and i flash clockwordmod recovery v6.0.1.9
i did this because my phone startted to reboot
at the GB logo
.
now problem is i cant flash ROM to sdcard.
here is the output
=================
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.435s
==========================
sending 'radio' (12288 KB)...
OKAY [ 1.353s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 2.060s
===================================
in recovery when i am trying to mount sdcard.
===============
Error mounting sdcard
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
amith007 said:
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
zakisays said:
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
Click to expand...
Click to collapse
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
zakisays said:
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
Click to expand...
Click to collapse
Perhaps you didnt read the post, so I will quote it here:
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
Zepius said:
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
zakisays said:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
Click to expand...
Click to collapse
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
samersh72 said:
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
Click to expand...
Click to collapse
i gave the following command
H:\Galaxy Nexus (yakju)>adb -d push "H:\Galaxy Nexus (yakju)\Stock-Unroot Jelly
Bean GNex GSM.zip" /sdcard/
its almost 2 hours now the command hasnt finished executing, hope all is going ok
ok i cancelled the previous command .
rebooted to recovery , mounted /data and /system
then reran push command.
got the zip file into sdcard
then tried installing , error generated
finding update package
opening update package
installing update
Installation aborted
!!!!!
please help
thanks
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
well i followed the steps.
i got error as below
===================
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe flash bootloader bootloader-magu
ro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.507s
================================
i hope now its clear what i am facing.
i can boot to fastboot and to recovery , but cant do anything else
if i flash something then the "Too many links error" comes
thanks for the help , is there anything else i can try
========================
ok i found something interesting
when i flash something i get the error " Too many links"
then when i run fastboot.exe devices , i get
???????????? fastboot
and after reboot i get
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe devices
My IEMI number fastboot
y is this happening
*sigh* ...
Op, uninstall all drivers, reboot your system;
Connect device in fastboot to PC, manually update drivers, disconnect device, reboot PC
Connect device again, flash recovery, after it finishes, disconnect USB, use volume keys to "reboot recovery", reconnect USB, manually update drivers again
'adb devices' should return your SN
'adb push ROM.zip /sdcard/' or if that doesn't do it, 'adb push ROM.zip /data/media/'
Sent from my Nexus
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...
Hi there,
I have just tried to root my HTC one, and I am now stuck in the boot loader screen and it is showing *Tampered* at the top.
Can someone please advise me, or point in the direction of what I need to do now?
Thanks.
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
jeanxx said:
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
millhhaus said:
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
Click to expand...
Click to collapse
Once you have unlocked your bootloader then it will show you tampered.
Download a custom recovery (I prefer TWRP) and flash it via fastboot.
Then download @Chainfire Supersu flashable zip from his site and flash it in recovery.
You have rooted your phone.
Ater placing my device into fastboot mode, I have tried flashing my downloaded TWRP file to my HTC One in Terminal using these instructions:
Now let's flash your downloaded TWRP file to your HTC One. Type one of the following commands into your terminal window, depending on which file you downloaded above.
For the International editions, type:
fastboot flash recovery Desktop/openrecovery-twrp-2.7.0.2-m8.img
However I get the following error:
command not found
any help would be most appreciated.
Did you setup your mac to use adb / fastboot commands?
lazydesi said:
Did you setup your mac to use adb / fastboot commabds?
Click to expand...
Click to collapse
I feel like a total N00b at the moment. LOL.
No. How do I do that?
try this
http://forum.xda-developers.com/showthread.php?t=2638673
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
millhhaus said:
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
Click to expand...
Click to collapse
hi,
plz try CWM, M8 got some issues with twrp.
philz_touch_6.26.6-m8.img is the stable version plz try that.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
millhhaus said:
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
Click to expand...
Click to collapse
is your problem similar to this?
http://forum.xda-developers.com/showthread.php?t=2784232
May be you are using the wrong version.If you have international device you should try international version of philz/cwm recovery.I would suggest you to use TWRP since it is basically meant for htc devices.
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
millhhaus said:
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
Click to expand...
Click to collapse
because you are using M7 files mate. you need to use M8.
M7 - Htc one - 2013 model
M8 - Htc One - 2014 model
http://download.cyanogenmod.org/?device=m8
Hey guys,
I updated to the Android N Developer Preview, expecting to have to root my device again. I tried following the instructions here:
http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
and my device already shows as unlocked. When I try and flash the custom recovery though, I get this message:
Code:
$ fastboot flash recovery twrp-3.0.0-0-dragon-ryu-02112016-1.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
Am I just out of luck with rooting the Android N version, and if so, is there an easy way to downgrade?
Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
godzirra said:
Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
Click to expand...
Click to collapse
Try this, post #4
http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
Are you sure to have fastboot/adb tools update ?
Sent from my Pixel C using XDA-Developers mobile app
Read: http://forum.xda-developers.com/pix...al-twrp-2-8-7-0-pixel-c-dragon-t3288243/page4
TLTR, lock and unlock your bootloader to fix the mess.
I did that, and now it just shows the "Bootloader is unlocked" warning and then after 30 seconds, shows the google logo, then reboots into recovery.
ilpolpi65 said:
Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
Are you sure to have fastboot/adb tools update ?
Sent from my Pixel C using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have the most recent fastboot and ADB.
At this point, I have (I think) Android N installed, and I can boot into TWRP or fastboot or the menu that lets me choose recovery/fastboot, but I can't boot the system itself.