Man, Ive really screwed up now... I didn't back up the stock ROM, tried to root her phone using the HTC Sync method described here.
I successfully unlocked the bootloader and rooted, but still have S-ON. I have HBOOT ver 0.98, by the way.
Then after installing a Cyanogenmod 7.2 ROM through ClockworkMod Recovery (no errors there), the phone freezes on boot at the white screen with green HTC letters.
I tried flashing another ROM (several actually), but they all do the same thing. Freeze on the white boot screen, doesn't matter how long I wait.
So in an effort to get it back to stock, I tried flashing a stock RUU through the bootloader, and I get an error "Main version is older!". Checked my version through "fastboot getvar all" and the main version on phone is 6.01.605.05, so apparently I can't flash anything less than that. The latest version RUU that I've been able to find for download is 5.10.605.9.
Im fairly new to this, but I don't think I can use ADB commands without booting into the OS, is that right?
So in short:
-unable to boot to OS
-can't find a custom ROM that will boot
-can't use ADB commands to downgrade HBOOT or get S-OFF (or can I somehow?)
-can't flash an RUU because my phones version registering higher than anything I can find on the net
So does anyone have any ideas?
Calm down, did you flash the boot.img through fast boot?
To me it looks like you didn't, flash your rom open the rom on computer take out the boot.img and but phone in fast boot then enter the following command
Fastboot boot boot.img
Sent from my SCH-I535 using xda app-developers app
Yes, I tried but it keeps failing. Do you know if my phone has to be unlocked before I flash the boot.img? Also, I am still s-on and don't know how to get s-off from a 6.01.605.05. I am stuck in bootloop and can't get into recovery only hboot/fastboot. Will the Roms you mentioned work with s-on? Should I try flashing the boot.img, system.img, and recovery.img from one of those roms?
GoonAssJuan said:
Calm down, did you flash the boot.img through fast boot?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
mrkmzo said:
Yes, I tried but it keeps failing. Do you know if my phone has to be unlocked before I flash the boot.img? Also, I am still s-on and don't know how to get s-off from a 6.01.605.05. I am stuck in bootloop and can't get into recovery only hboot/fastboot. Will the Roms you mentioned work with s-on? Should I try flashing the boot.img, system.img, and recovery.img from one of those roms?
Click to expand...
Click to collapse
Any rom will work as long as you flash the boot.img from that specific rom
Sent from my SCH-I535 using xda app-developers app
Had the same problem
I had the same problem and flashing the boot.img does work. Make sure your fastboot and boot.img are in the same folder and and you hold shift and open command prompt from there. Also make sure your drivers are working properly. After you flash your boot image to you phone the clear all data/cache/davsik and then instal cyanogenmod!
Related
Hey, i unlocked the bootloader, flashed a CWM (That does not allow me to mount my phone storage to the PC), tried to flash 2 .zips (the Remove menu thingy, and the SuperSU V.0.87) and when i tried to do that it went in a bootloop(or bootstuck? gets to the "HTC One X - Beats Audio screen, and never gets any further) WHAT DO I DO? Help me please!
Hi, i did exactly the same thing and...i got the same result ....Please, anyone knows how to solve it???????
I am guessing you didnt take a backup in CWM prior to flashing the mods? If not, unfortunately, your only solution would be to bring it back to complete stock and flash the RUU that originally came loaded on your phone.
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Thanks!!!!! thank to you I managed to unlock my mobile
Can't really tell you what worked, i flashed my RUU but it failed, i tried flashing stock and all that (which i put on there beforehand as CWM can't mount the drive), but in the end it was just persistence that got it, so just keep trying!
askemil said:
Can't really tell you what worked, i flashed my RUU but it failed, i tried flashing stock and all that (which i put on there beforehand as CWM can't mount the drive), but in the end it was just persistence that got it, so just keep trying!
Click to expand...
Click to collapse
If the guild didden work. then you have done somting rong. cuz doing that guild works in all casese
exept Branded devices cuz Custom roms from the carryer
askemil said:
Hey, i unlocked the bootloader, flashed a CWM (That does not allow me to mount my phone storage to the PC), tried to flash 2 .zips (the Remove menu thingy, and the SuperSU V.0.87) and when i tried to do that it went in a bootloop(or bootstuck? gets to the "HTC One X - Beats Audio screen, and never gets any further) WHAT DO I DO? Help me please!
Click to expand...
Click to collapse
I think the Menu removal caused bootloop. I don't have my PC with me if someone can upload the stock Framework-res.apk and SystemUI.apk you could replace that to boot it back again. If nothing works then download one of the Custom ROM (ARHD or LeeDroid) then wipe everything and flash that it should work for you.
End to unlock again?
DaDoctor said:
I am guessing you didnt take a backup in CWM prior to flashing the mods? If not, unfortunately, your only solution would be to bring it back to complete stock and flash the RUU that originally came loaded on your phone.
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Click to expand...
Click to collapse
How can it be unlocked again? Is there a simple command also or it is htcdev all over again?
kaskonjunf said:
How can it be unlocked again? Is there a simple command also or it is htcdev all over again?
Click to expand...
Click to collapse
You should have received a code from HTC when you unlocked, check your email for it. Then you place it in file with fastboot on computer, open cmd prompt, type in fastboot oem unlock and it should unlock.
Sent from my HTC PH39100 using xda premium
i agree with this method my problem is my phone will not charge
http://www.youtube.com/watch?v=DPE5CDupEsk&feature=youtu.be thats the youtube video with the issue im having. my phone will not charge in fastboot nor hboot and even if i power it off it will turn on again please helpo
dgstarcraft said:
i agree with this method my problem is my phone will not charge
http://www.youtube.com/watch?v=DPE5CDupEsk&feature=youtu.be thats the youtube video with the issue im having. my phone will not charge in fastboot nor hboot and even if i power it off it will turn on again please helpo
Click to expand...
Click to collapse
Maybe devs can come up with a way to charge while in cwm, that would be great.
Sent from my HTC PH39100 using xda premium
I'm going to update my htc one x to jelly bean from ICS, using custom ROM (ARHD), it was noted that I need a firmware package, and now that I found the package for my CID because took sometime before I found it, is it really required to flash it? TIA
For JB roms you need a JB hboot those are the 1.31 and higher up. Except for the aosp JB roms, those run also on the lower ics hboots.
So if you are on a lower hboot then 1.31 then yes you need to upgrade the hboot
Now I think everything's messed up and I badly need help here, so stupid with I did.
At one moment, my phone is stuck at One tm screen, after I flash the boot.img and installed the custom ROM. I tried to restore my phone using CWM but it still stucked. It was too late before I realized how to flash the firmware package that I need to rename what I downloaded to firmware.zip. I tried flashing the firmware without knowing that I have to relocked my phone before I flash it. Now I relocked my phone and I'm stucked with hboot and I can't do anything at the moment.
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zip
Once completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zipOnce completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cannot load "firmware.zip" always shows up. My CID is HTC_044, and as far as I know I downloaded the correct firmware package for my phone according to ARHD forum. Thanks in advance.
Did you have the firmware.zip in your fastboot folder?
Yes. And I downloaded it 3 times just to make sure it is the right firmware.
Oh and sometimes you need to flash it 3 or 4 times to succeed. I had to do the command 3 times when I flashed my firmware.
So try it multiple times in a row.
Sent from my One X
Sorry but I tried several times and "error: cannot load 'firmware.zip' all the time. What could be the problem?
During at work. I thought if is it possible just to return to stock ROM? But I just can't find the proper RUU yet.
cid: htc_044
version-main: 1.29.707.11
I'm currently charging my phone using the batch file I found here in xda. I saw a lot of posts regarding flashing the current version of CWM so you can charge your battery, I think my CWM is in version 5.8.1.0, and as far as I know you have to unlock your hboot before you can flash recovery, so it's impossible for me to flash 5.8.4.0? Am I correct here or I can just proceed to the other steps?
I can check tonight if i have your RUU !
Mr Hofs said:
I can check tonight if i have your RUU !
Click to expand...
Click to collapse
Thank you Mr Hofs! And, should my battery level is 30% or higher before I can flash the RUU?
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Mr Hofs said:
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Click to expand...
Click to collapse
I was done in re-unlocking my bootloader, but then I still can't flash cwm recovery because it says low battery, then I tried to use the batt script again and of course it cannot work since I just re-unlocked my bootloader.
I never tried it with a unlocked bootloader, have you tried it ?
Yes, I tried it and it doesn't work.
What I did for the past hours, I tried to restore my phone again using cwm recovery, still nothing changed, still stucked at htc one logo, then I turned it off trying to charge it using the main charger and it does have light in its LED, left it for a while and now it doesn't turn on.
Try it with phone connected to the pc, it seems to make a difference sometimes....and if you are capable again to run the bat script then leave it for 2.hours or so !
Now it's working. The first time I used the batt script, I thought it could charge more than 3681mV but It didn't work as it didn't get higher than 3681mV. I HOPE it's enough just to flash the cwm recovery. Thanks Mr Hofs, will update asap.
I'm trying to help a friend remotely fix his current brick of a HOX and would like some pro advice to ensure im telling him the right thing. Info I have:
Its S-On UK T Mobile CID T-MOB005.
He obtained a 1.39 firmware from somewhere that matched his CID
At some point in the process the firmware flash failed or partially flashed
His Custom Recovery is gone
His HBoot version has not increased (i think 1.12)
He has a security warning under the 'relocked' message in bootloader
Before he tried the firmware upgrade he flashed viper x 3.4.0 + boot.img so the phone wont boot up normally now
He has a nandroid backup from before the process.
Im going to recommend to him to download the 1.36 firmware from Mikes thread here http://forum.xda-developers.com/showthread.php?t=1957376 (i notice there is no 1.39 available for his CID so im suspicious this was a duff file he had for 1.39)
If he cant flash it because of low power then he should use the charging batch script first or re-unlock, flash CWM, restore nandroid and flash the boot.img from it so he can boot phone and charge it normally or from cwm.
I guess after that start to look at an RUU or a stock nandroid backup download to be able to do the firmware OTA ?
My own HOX is S-Off so im not as familiar with the process as i never worried about the correct firmware or had to flash boot.img separately from roms or nandroids.
Any tips appreciated.
Cheers
Re: Hboot upgrade attempt failed
Yeah that's about it.....only flashing the rom is not going to work because of the low hboot.
Just charge the battery and and unlock the bootloader, then reflash a custom recovery and charge the battery up in there.
With enough power he can relock the bootloader and flash the firmware
Fastboot oem lock
Fastboot rebootRUU (watch the capital letters)
Fastboot flash zip firmware.zip
Unlock the bootloader
Fastboot flash unlocktoken unlock_code.bin
Then flash the custom recovery again and install a new rom ! :thumbup:
Cheers, so out of interest what causes the Security Warning in the bootloader ? Is it because the phone knows there is a screwed up firmware flash or knows it cant boot\has low power ? It must have done something as his custom recovery was wiped even though the Hboot ver didnt change.
how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now
Re: Hboot upgrade attempt failed
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Great will check, just assumed he had tried it twice as all instructions I've seen state that you must but then again i dont know what instructions he followed - maybe he didnt ! Ive not seen this explanation of whats being flashed and in what order before - cheers.
Mr Hofs said:
how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now
Click to expand...
Click to collapse
Ive not seen it but i assume its something like this
*** RELOCKED ***
*** Security Warning ***
Then all the usual bootloader stuff
based on images ive seen before on web. can find them with a quick google of images.
Re: Hboot upgrade attempt failed
Yeah that's normal :thumbup:
Re: Hboot upgrade attempt failed
Ok it lives ! Was a combination of the firmware file and his battery being too low to flash so he put cwm back on, charged and then followed my instructions. Cheers for help
This is the what I sent him incase anyone else finds them useful. Assumes you know roughly what your doing and that you must get back to fastboot usb for the commands .
-----------------------------
So get phone into fastboot mode by power plus vol and choose it in bootloader., plug usb in so it says fastboot usb, then get command prompt in directory with fastboot in on pc.
1. Lock bootloader with: fastboot oem lock
2. Vol and power down to get into bootloader again
3.fastboot oem rebootRUU
4. Should now get phone with silver HTC in middle on black
5. fastboot flash zip firmware.zip where this is the new firmware for your cid.
6. Might fail first time. Do it again and it works
7. Should now see green bar completed under the htc
8. Power and vol to get to bootloader. The hboot should now be updated.
9. Now to unlock bootloader again
. fastboot flash unlocktoken unlockcode.bin (where unlockcode.bin is the file you got from htcdev)
10. Now on the phone select yes and it reboots.
11. Don't wait just use power and vol to get into bootloader.
12. Flash custom recovery again. fastboot flash recovery recovery.img where recovery.img is the cwm 5.8.4.0
13. You can now flash your chosen Rom boot.img. fastboot flash boot boot.img
14. fastboot erase cache
15. Now use recovery to flash the Rom.
16. Done
Sent from my HTC One X
Very good :thumbup:
CASE CLOSED !
I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app
ViktorN said:
I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So true !
Indeed. Not very often you can tell exactly where a problem is without having to ask for more info. In fact. A thanks to the op for providing a very detailed diagnosis without even having the device to hand
Sent from my HTC One X using xda app-developers app
Hello everyone,
After having unlocked the boot loader I flashed via fast boot TWRP. The only problem is that I flashed "fastboot flash BOOT recovery.img" instead of RECOVERY... I wasn't paying enough attention...
The phone still boots but it goes straight to recovery. What can I do? Fast boot still recognizes it. I was thinking of extracting the boot.img file from a sense based rom like android revolution HD for the m8 or putting the whole rom android revolution HD on an sd card and flashing via recovery. In other threads users had already flashed a custom rom so they could flash the boot.img extracting it from that but I don't know since I still had the stock unlocked rom.
Would one of these solutions solve the problem?
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
djkinetic said:
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
Click to expand...
Click to collapse
I'll try flashing a boot.img, the other solution is beyond my current skills...
Just extract the boot.img from the ROM you were using. If stock, download one of the stock Roms and then extract the boot.IMG from it and then
fastboot flash boot boot.img
Obviously the boot.img will need to be in your fastboot/adb folder.
Sent from my HTC One_M8 using xda app-developers app
thank you both, I flashed the correct boot.img and everything is fine now
djkinetic said:
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
Click to expand...
Click to collapse
What... He just needs to flash a kernel, why potentially cause someone to brick their device by flashing a hboot which wouldn't even solve the issue?
where did you get the boot.img file ? care to share it I am stuck too. My phones is from Rogers
tawer said:
where did you get the boot.img file ? care to share it I am stuck too. My phones is from Rogers
Click to expand...
Click to collapse
Go to my backup thread and get a nandroid ....the kernel is inside the backup.
Thank you so much.
HI
I have a problem with my htc and i was wondering if i could get some help please.
I unlocked the bootloader of my HTC WFS and installed twrp i installed a costume rom based on android 2.5.7 (alquez and it worked fine
but now whenever i turn on my phone it would stay on the white htc screen and even when i try recovery NOTHING
my HTC WFS is S-ON (GSM) PG7610
PS: I tried every tip i could find on XDA DEVELOPERS like
*GOLD CARD
*flash rom with RUU while phone is on FASTBOOT mode
*and since my phone is S-on i cant wipe the system via FASTBOOT
*i tried DIAG files but that only works for (CDMA) phones
*cant use ADB since phone wont boot
ANY THOUGHTS?
THANK YOU.
caymera94 said:
HI
I have a problem with my htc and i was wondering if i could get some help please.
I unlocked the bootloader of my HTC WFS and installed twrp i installed a costume rom based on android 2.5.7 (alquez and it worked fine
but now whenever i turn on my phone it would stay on the white htc screen and even when i try recovery NOTHING
my HTC WFS is S-ON (GSM) PG7610
PS: I tried every tip i could find on XDA DEVELOPERS like
*GOLD CARD
*flash rom with RUU while phone is on FASTBOOT mode
*and since my phone is S-on i cant wipe the system via FASTBOOT
*i tried DIAG files but that only works for (CDMA) phones
*cant use ADB since phone wont boot
ANY THOUGHTS?
THANK YOU.
Click to expand...
Click to collapse
Hey pal first off, this is the wrong forum. This is the old wildfire forums not the wildfire s. But I shall help you out none the less
Since your phone is hboot unlocked but not s-off you need to flash your custom roms boot.img via fastboot just after you flash the rom via recovery. When you download the rom it comes in a zip file, unzip a copy of it and place the boot.img in your fastboot folder, then copy the zip to your sd card and then flash via recovery. Once it's flashed boot into hboot by using advanced reboot options I think its called. Then flash the boot.img using the command
Fastboot flash boot boot.img
Where boot.img is the name of the .img you took from the zip file (just in case you have renamed it and don't know why the command is not working)
Then do fastboot reboot and the phone should boot up okay. You need to flash the boot.img for every rom change that you do. Also should you decide you want to run a RUU you must relock you hboot or it won't run.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
Hey pal first off, this is the wrong forum. This is the old wildfire forums not the wildfire s. But I shall help you out none the less
Since your phone is hboot unlocked but not s-off you need to flash your custom roms boot.img via fastboot just after you flash the rom via recovery. When you download the rom it comes in a zip file, unzip a copy of it and place the boot.img in your fastboot folder, then copy the zip to your sd card and then flash via recovery. Once it's flashed boot into hboot by using advanced reboot options I think its called. Then flash the boot.img using the command
Fastboot flash boot boot.img
Where boot.img is the name of the .img you took from the zip file (just in case you have renamed it and don't know why the command is not working)
Then do fastboot reboot and the phone should boot up okay. You need to flash the boot.img for every rom change that you do. Also should you decide you want to run a RUU you must relock you hboot or it won't run.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
HI.
firste off i would like to thank you for taking the time to responde to my question and im sorry about posting in the wrong forum.
i watched the XDA DEV noob video on youtube about being a noob so before i posted my question i looked through each and every post i could find about my phone s problem but NO LUCK so i decided to ask the experts
*i did relock my bootloader before i ran the Ruu and it didnt work it said main version too old and since my costume rom is based on andoird 2.3.7 and my htc can only go as far as 2.3.5 and ruu wont let you downgrade so i figured it might not work.
*now you suggested that i flash the costume rom via recovery and thats the problem i cant even get in to my recovery it just gets stuck on the white htc screen and i tried flashing the recovery Again (twrp) and nothing. even other recoveries wouldnt work.
*i flashed about 4 roms and they all worked just fine even this last one and i didnt flash the boot.img and i was able to reboot normally
THANK YOU.
caymera94 said:
HI.
firste off i would like to thank you for taking the time to responde to my question and im sorry about posting in the wrong forum.
i watched the XDA DEV noob video on youtube about being a noob so before i posted my question i looked through each and every post i could find about my phone s problem but NO LUCK so i decided to ask the experts
*i did relock my bootloader before i ran the Ruu and it didnt work it said main version too old and since my costume rom is based on andoird 2.3.7 and my htc can only go as far as 2.3.5 and ruu wont let you downgrade so i figured it might not work.
*now you suggested that i flash the costume rom via recovery and thats the problem i cant even get in to my recovery it just gets stuck on the white htc screen and i tried flashing the recovery Again (twrp) and nothing. even other recoveries wouldnt work.
*i flashed about 4 roms and they all worked just fine even this last one and i didnt flash the boot.img and i was able to reboot normally
THANK YOU.
Click to expand...
Click to collapse
Okay so, let's recap.
You are on a custom android rom.
You have a custom recovery installed.
Your cannot flash the RUU as your run version is higher than the RUU.
Lastly you cannot boot into your custom Rom, or your recovery?
Do you want to return to stick it get a custom Rom flashed?
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
Okay so, let's recap.
You are on a custom android rom.
You have a custom recovery installed.
Your cannot flash the RUU as your run version is higher than the RUU.
Lastly you cannot boot into your custom Rom, or your recovery?
Do you want to return to stick it get a custom Rom flashed?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
at this point i just want to get pass that white htc screen i am sick of it
Q: if i flash a system via fastboot successfully will it automaticly erase the old one because i tried to erase it but it said remot controle not allowed (S-on)
ok, ive requested this thread be moved to its correct forum.
before proceeding can you tell me when your htc wildfire marvel was made? after 2012?
can you flash clockworkmod recovery and then try flashing a custom htc sense rom
Then reboot back into cwm recovery (by selecting advanced/ reboot-recovery in the menus) and plug the phone into your computer via usb cable. open up your command prompt and move to your adb folder. type the following commands ( a # denotes instructions and should not be typed into the command window)
Code:
adb devices
#this should show your device up, maybe saying its in recovery mode
adb shell
# the command prompt should change to a # symbol
Now make sure you have a sdcard in the phone and then run the following command
Code:
cat /dev/mtd/mtd0 > /sdcard/misc.img
This should leave you with a file called misc.img on your sdcard. Lastly
Code:
exit
exit
exit
your command window should have closed. now upload this file to a online storage system like dropbox and send me a pm with a link to it. I will edit it and you can flash it back, this will relock your hboot and downgrade your software version so that RUU's will work. then we will run a RUU, returning your phone to stock and functional state
heavy_metal_man said:
ok, ive requested this thread be moved to its correct forum.
before proceeding can you tell me when your htc wildfire marvel was made? after 2012?
can you flash clockworkmod recovery and then try flashing a custom htc sense rom
Then reboot back into cwm recovery (by selecting advanced/ reboot-recovery in the menus) and plug the phone into your computer via usb cable. open up your command prompt and move to your adb folder. type the following commands ( a # denotes instructions and should not be typed into the command window)
Code:
adb devices
#this should show your device up, maybe saying its in recovery mode
adb shell
# the command prompt should change to a # symbol
Now make sure you have a sdcard in the phone and then run the following command
Code:
cat /dev/mtd/mtd0 > /sdcard/misc.img
This should leave you with a file called misc.img on your sdcard. Lastly
Code:
exit
exit
exit
your command window should have closed. now upload this file to a online storage system like dropbox and send me a pm with a link to it. I will edit it and you can flash it back, this will relock your hboot and downgrade your software version so that RUU's will work. then we will run a RUU, returning your phone to stock and functional state
Click to expand...
Click to collapse
WOW. first off thank you for going through all this trouble just to help me.
..when was your htc wildfire marvel was made?
*my bootloader says FEB/8/2012
..can you flash clockworkmod recovery and then try flashing a custom htc sense rom?
*I can flash any recovery (twrp or clockworkmod) which i did BUT i cant boot into the recovery (STUCK on white htc screen)
*and ADB does not work since i cant get in to my ROM. ONLY fastboot
THANK YOU.
caymera94 said:
WOW. first off thank you for going through all this trouble just to help me.
..when was your htc wildfire marvel was made?
*my bootloader says FEB/8/2012
..can you flash clockworkmod recovery and then try flashing a custom htc sense rom?
*I can flash any recovery (twrp or clockworkmod) which i did BUT i cant boot into the recovery (STUCK on white htc screen)
*and ADB does not work since i cant get in to my ROM. ONLY fastboot
THANK YOU.
Click to expand...
Click to collapse
Hmm.... Okay reflash twrp and see if it boots up. Without a recovery your options are limited. You need to be careful as your device uses a different kernel from older versions of the wildfire s. If you flash a older RUU version it will kill your phone.
Do you have any phone unlock shops near you?
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
Hmm.... Okay reflash twrp and see if it boots up. Without a recovery your options are limited. You need to be careful as your device uses a different kernel from older versions of the wildfire s. If you flash a older RUU version it will kill your phone.
Do you have any phone unlock shops near you?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
i did reflash it and it did not boot and Yeah you r probably right ill take it to a phoneunlock shop but i dont think it could save it.
anyway THANK YOU for everything.
caymera94 said:
i did reflash it and it did not boot and Yeah you r probably right ill take it to a phoneunlock shop but i dont think it could save it.
anyway THANK YOU for everything.
Click to expand...
Click to collapse
Make sure when you go to the unlock shop you make sure they use an XTC clip http://www.fonefunshop.co.uk/Unlocking/xtc_clip.htm
If they don't have it then do not pay for an unlock. You need s-off not SIM unlocked. Make sure to ask for it. Once your S-off you can run any RUU and fix the phone but check in here first so I can ensure that its compatible with your 2012 edition of the phone ( as I said flashing one that is too old will kill the phone!)
heavy_metal_man said:
Make sure when you go to the unlock shop you make sure they use an XTC clip http://www.fonefunshop.co.uk/Unlocking/xtc_clip.htm
If they don't have it then do not pay for an unlock. You need s-off not SIM unlocked. Make sure to ask for it. Once your S-off you can run any RUU and fix the phone but check in here first so I can ensure that its compatible with your 2012 edition of the phone ( as I said flashing one that is too old will kill the phone!)
Click to expand...
Click to collapse
Will do.
Thanks for the heads up