Related
Hey Guys
First time poster here and not massively technical at all so be gentle with me
Ok so over the weekend I decided I wanted to see what all the fuss was about with these custom ROM's that you can download. So I did some research and decided to give it a go. Please bear with me dudes. So what I did was as follows:
1) Unlocked the bootloader following HTCdev.com guide. Success
2) Rooted the phone, now have super user and can grant SU permissions to apps. Success
3) Installed ROM Manager, latest version. Success
4) Attempted to Flash clockworkmod to recovery using ROM Manager. Stated success in the app.
5) In ROM Manager I attempted to make a backup of my stock rom, asked me to enter a backup name and click OK, device reboots and I see a red exclamation mark when it tried to reboot into recovery, suggesting that step 4 was actually a failure.
6)Downloaded latest clockworkmod image file from the clockworkmod site and using a tool called android flasher (I think) I was able to flash the recovery image to the recovery partition. Phone reboots and boots into recovery and boom I have the clockworkmod recovery available to me.
7) Immediately took a backup of my stock rom so can convert back if things go pear shaped. Success.
8) I downloaded 2 custom rom's, Cyanogenmod latest 7.1.0 build and MIUI custom rom, both for Desire S. Success
9) Put both rom's onto my 8GB sd card as instructed by a guide I was following and booted into clockworkmod and wiped cache, data and system. Success
10) In clockworkmod selected install zip from SD card, found the Cyanogen zip and selected it, it proceeds to install. Reports success.
11) Reboot phone and it hangs on the HTC logo screen, nothing doing. Failure.
12) I have to boot back into CWM and restore my backup which is a success.
So what I end up with is my stock rom with an unlocked bootloader, rooted as I have superuser app and can grant SU permissions to ROM Manager and titanium backup. But I don't seem to be able to get a custom rom on there. I have tried formatting sd card, putting a new rom on and then taking battery out for 15 mins but again nothing doing, everything I try I just get a hanging HTC logo after reboot and again I have to restore my backup that I made to get a working phone again.
Here are some details from the bootloader:
**** UNLOCKED ****
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
RADIO - 3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Sorry for the mahoooooossive post guys but its really bugging me that I cant get a custom rom on there, stock rom rooted just wasn't what I was looking for.
Really hope you guys can give some help/advice
Stewie
All yours steps seems fine to me.
The first time you flash a custom rom, it could takes MINUTES before boot (Once I waited 10 min with a rom).
How long did u wait when the HTC logo appeared?
Have you tried to S-OFF your Desire S?
It could be one of the reason why you can't flash properly.
Here all the guides (maybe you already know everything):
http://forum.xda-developers.com/showthread.php?t=1186401
EDIT:
As I suspected, it does stated it clearly in the link I gave you:
FAQs:
1. What's S-OFF and S-ON?
- If your phone is S-ON, you won't be able to root or flash custom ROMs to your phone. S-OFF let's you to have full control of your phone.
(NOTE: S-OFF is not ROOT, S-OFF your device does not mean that your device is Rooted. They are totally two different things.)
yukinok25, dude thanks for that, I was kinda thinking that it may have something to do with the s-on / s-off thing.
I'll have a butchers at trying to s-off the device, but I thought it was supposed to be a pretty tricky procedure with the version of HBoot that I have on my device, i.e 2.00.0002. So I was hoping to avoide the s-off process but if I gotta do it then I gotta do it, just hope it all goes ok.
Again thanks for the link man, good to get some help as im a bit of a rookie at this sort of stuff ;-)
Cheers
Stewie
Anytime mate.
Just because you are new to XDA: you can use the thanks button next time...
Not sure if this is still relevant, but there is a simple guide on the Dev forum on how to S-OFF the new HBOOT:
http://forum.xda-developers.com/showthread.php?t=1525100
Also, the recommended custom recovery is 4EXT, which is based on Clockwork but more advanced. There is even a touch version now:
http://forum.xda-developers.com/showthread.php?t=1377745
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?
onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.
http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium
tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.
Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium
heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.
an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know
Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.
We need more details .....which kernels did you flash ??
I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.
sagarsaoji said:
I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.
Click to expand...
Click to collapse
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE
malybru said:
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE
Click to expand...
Click to collapse
I flashed a RUU through the rom.zip. The process seemed to be stuck at step [4] System for quite a while, kept unzipping and updating over and over again. It eventually completed but now I'm stuck in bootloop with a large BEEP sound after "htc simply brilliant" screen, then phone reboots and have to pull the battery out. PLEASE HELP ME
Did you install stock kernel ??
Because some roms need specific kernels which only work on the Rom and your going to stock so its not gonna boot
sagarsaoji said:
Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.
Click to expand...
Click to collapse
IS the Phone S-OFF?
This step is extremely important, because we are not s-off and there is a problem with creating the "boot.img". T-Macgnolia explained it nicely:
When you use HTC Dev to unlock your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read those partitions. But there is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the .zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed the New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
Click to expand...
Click to collapse
There are 2 ways to enable smartflash, one is a temporary way inside the 4EXT recovery itself (only for first time!) and the second way is permanent, through the 4EXT application.
The permanent way can only be enabled if your phone has ROOT! It's impossible to do it when you are going to flash a ROM for the first time.
Once you have flashed your ROM you have to install the 4EXT application and enable smartflash through it, which is explained in Step 5.
3A. Enable 4EXT Temporary smartflash
Enabling this is as simple is getting into the recovery and enabling it as an option.
NOTE: You only need to do this right before flashing your first ROM, so you should skip this step and come back here when the guide tells you to.
Disable "Fast Boot" on your phone.
Code:
Settings
Power
Untick "Fast boot"
Turn off your phone
Hold the Power AND Volume Down button until you see a white screen which says: "Fasboot".
Navigate to "RECOVERY" and select it, you should now boot into the 4EXT recovery
Select "Tools"
Scroll Down and select "Enable 4EXT SmartFlash"
Again, you only need to do this ONCE, once you have flashed your first custom ROM and enabled permanent smartflash, you don't need to this any more!
Click to expand...
Click to collapse
Source
Hope I am not talking nonsense
wetfoot said:
IS the Phone S-OFF?
Source
Hope I am not talking nonsense
Click to expand...
Click to collapse
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?
Sure thing .......
Do you know how to get the stock kernel from the ruu ?
sagarsaoji said:
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?
Click to expand...
Click to collapse
Hi,
The RUU contains a stock ROM ,recovery,kernel,firmware,and radio.
It should be the only thing you need to flash/run.
I do not know why the RUU did not work.
Now that it is "Locked", then you cannot flash an RUU with version less than your phone's current version.
The RUU should reset all your partitions,(Except s-off), and restore your phone to stock.
If your current version is the same as the RUU,try running it again by doing it manually (section 4 in the guide)
Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
EDIT: just some further info...can't get adb to find device even though it is in fastboot usb mode..any way to get that working?
sagarsaoji said:
Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
Click to expand...
Click to collapse
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.
malybru said:
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.
Click to expand...
Click to collapse
Still not booting, making a beep after "simply brilliant" screen and reboots constantly. I was able to get ADB to finally work. I also followed Step 4 from the guide but even after the RUU flashes completely the phone is stuck in bootloop.
Hi,
so my phone doesn´t work after my attempt to upgrade to MIUI 4.
I started of being on the old, Ginger Bread based MIUI rom. So I updated my hBoot following this guide. After finishing all the steps I was not able to boot back into my original ROM, which I restored from the nandroid backup, as instructed. I got stuck at the HTC logo.
So I went to this MIUI thread in order to download the new ICS based MIUI zip. Unfortunately, the link provided in this thread is broken. So I went to the official English MIUI website and downloaded the latest MIUI rom. I flashed this, and now I get beyond the HTC logo, but remain stuck at th "mi" logo.
So i thought I might try to flash the kernel provided in the MIUI thread here on xda, but I just can´t seem to be be able to find any downloadable file at the location provided.
So I tried to reflash the kernel provided in the hBoot update guide with no success. I was stuck at the htc logo again.
Reflashed latest MIUI - stuck at "mi" logo again.
I kindly ask the community for help..........
Oh yea and I can access bootloader and 4ext recovery.
mimirom said:
Oh yea and I can access bootloader and 4ext recovery.
Click to expand...
Click to collapse
You may need to wipe cache in the recovery after the hboot update.
Anyway you have already flashed stuff on top so it probably will not work.
The file from the official MIUI site requires the files in your new /lib partition to be present before installation. So if you desperately want MIUI go to miuiandroid.com and download it from there.
Or just use a Sense 4 of a JB ROM from this forum. Remember to make a full wipe in recovery before install.
And BTW there is a link in the Download section of the kernel thread. In your panic you haven’t noticed the "SHOW CONTENT" button
Wow,
so now the phone seems to be back to previous. Somehow the restore from nandroid worked out. Thanks God...
Still, I wasn't successful updating to MIUI 4.
The hBoot now shows:
*** LOCKED ***
SAGA PVT ENG S-OFF RL
HBOOT-2.00.2002 (PG88*****)
RADIO-3805.06.02.03_M
eMMC-boot
Aug 12 2011,20:40:03
Great, thanks for being with me. Well I'm used to MIUI and I'd like to stay with it.
Somehow I will work my way through to it hopefully.
I think I actually downloaded the latest MIUI zip from miuiandroid.com. I mean the one that didn't work for me.
Now I can see the link to the kernel.
mimirom said:
Wow,
so now the phone seems to be back to previous. Somehow the restore from nandroid worked out. Thanks God...
Still, I wasn't successful updating to MIUI 4.
The hBoot now shows:
*** LOCKED ***
SAGA PVT ENG S-OFF RL
HBOOT-2.00.2002 (PG88*****)
RADIO-3805.06.02.03_M
eMMC-boot
Aug 12 2011,20:40:03
Click to expand...
Click to collapse
I had stucked problem trying to install miui after chging my hboot, so i tried wiping everything 1 by 1(using 4ext) instead of everything except sd.
Then before installing i reboot recovery then did my install and it booted fine.
rain987 said:
I had stucked problem trying to install miui after chging my hboot, so i tried wiping everything 1 by 1(using 4ext) instead of everything except sd.
Then before installing i reboot recovery then did my install and it booted fine.
Click to expand...
Click to collapse
Didn't work. Thank s though.
amidabuddha said:
You may need to wipe cache in the recovery after the hboot update.
Anyway you have already flashed stuff on top so it probably will not work.
The file from the official MIUI site requires the files in your new /lib partition to be present before installation. So if you desperately want MIUI go to miuiandroid.com and download it from there.
Or just use a Sense 4 of a JB ROM from this forum. Remember to make a full wipe in recovery before install.
And BTW there is a link in the Download section of the kernel thread. In your panic you haven’t noticed the "SHOW CONTENT" button
Click to expand...
Click to collapse
Ok, so I can give it a second try and download the latest MIUI from miuiandroid.com once again and flash that (although I think that's what I did once already without success.) Do i get you right that this rom is supposed to be different from the one from the Chinese MIUI website?
Anyway, given that this probably won't work, are there any other suggestions/solutions? How about going through all the steps of the hBoot flashing guide once again?
Anyone?
Can't flash anything, keeps saying "E:footer is wrong signature verification failed"
I think I've done messed up now...
I've been having a lot of issues with my HTC One M8 (Verizon) (rooted, s-off) phone since the screen was replaced. Mainly, my GPS signal completely stopped working. Anyway, that has led me flashing various ROMS, update.zip files, and 0p6bimg.zip files. Previously, I was working on a 32-bit Win7 laptop during the first round of nonsense. I'd be able to trace back my steps better but since that laptop is no longer in my possession, along with all the various files I used during the process. During that time, I had pretty much bricked my phone where it was stuck on the red Verizon splash screen indefinitely. Eventually, through much trial and error and internet searching, IRCC I flashed some new FUU and RUU files. Ultimately, I was able to successfully sideload the ViperOneM8_4.3.0_OTA Lollipop ROM and get back up and running (still minus GPS lock, but that's beside the point right now).
Fast forward to today, I was intending to flash a different ROM and messed up big time. I loaded the new ROM onto my storage, then powered the phone on into the bootloader. When I tried flashing the new ROM I was given an error (I don't remember specifically what it was, but the flash didn't go through). I then tried wiping data and cache, then tried again. Still didn't work.
Now I'm stuck here with the only the stock recovery mode and the unlocked bootloader as my only options. I'm now working on a different 64-bit Win8 laptop and for the life of me can't even get ADB properly setup where a command prompt "adb devices" command shows that my phone is being recognized. Any time I try to flash any firmware or ROM from the stock recovery I get the following error:
E:footer is wrong
E:signature verification failed
Aborting installation
I'm totally stuck and have no clue what to do. I can't even flash back to the previous Venom ROM I had installed before today's wipe... Can anybody help???
FWIW, my bootloader screen currently shows this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RARIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Feb 3 2015,21:50:28.290
trevorparsons said:
I think I've done messed up now...
I've been having a lot of issues with my HTC One M8 (Verizon) (rooted, s-off) phone since the screen was replaced. Mainly, my GPS signal completely stopped working. Anyway, that has led me flashing various ROMS, update.zip files, and 0p6bimg.zip files. Previously, I was working on a 32-bit Win7 laptop during the first round of nonsense. I'd be able to trace back my steps better but since that laptop is no longer in my possession, along with all the various files I used during the process. During that time, I had pretty much bricked my phone where it was stuck on the red Verizon splash screen indefinitely. Eventually, through much trial and error and internet searching, IRCC I flashed some new FUU and RUU files. Ultimately, I was able to successfully sideload the ViperOneM8_4.3.0_OTA Lollipop ROM and get back up and running (still minus GPS lock, but that's beside the point right now).
Fast forward to today, I was intending to flash a different ROM and messed up big time. I loaded the new ROM onto my storage, then powered the phone on into the bootloader. When I tried flashing the new ROM I was given an error (I don't remember specifically what it was, but the flash didn't go through). I then tried wiping data and cache, then tried again. Still didn't work.
Now I'm stuck here with the only the stock recovery mode and the unlocked bootloader as my only options. I'm now working on a different 64-bit Win8 laptop and for the life of me can't even get ADB properly setup where a command prompt "adb devices" command shows that my phone is being recognized. Any time I try to flash any firmware or ROM from the stock recovery I get the following error:
E:footer is wrong
E:signature verification failed
Aborting installation
I'm totally stuck and have no clue what to do. I can't even flash back to the previous Venom ROM I had installed before today's wipe... Can anybody help???
FWIW, my bootloader screen currently shows this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RARIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Feb 3 2015,21:50:28.290
Click to expand...
Click to collapse
You need to flash my ruu from ruu mode in boot loader. Nothing posted on here is going to flash on stock recovery for you. Nothing.
Sent from my HTC6535LVW using Tapatalk
dottat said:
You need to flash my ruu from ruu mode in boot loader.
Can you either point me in the right direction or give some guidance on this pretty please? I don't remember how I did this the first time around.
Click to expand...
Click to collapse
trevorparsons said:
dottat said:
You need to flash my ruu from ruu mode in boot loader.
Can you either point me in the right direction or give some guidance on this pretty please? I don't remember how I did this the first time around.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3047103
EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(tweaks zip)(newest)
If you are still stuck tomorrow I can help you remotely using team viewer
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
dottat said:
trevorparsons said:
http://forum.xda-developers.com/showthread.php?t=3047103
EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(tweaks zip)(newest)
If you are still stuck tomorrow I can help you remotely using team viewer
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Yesssss!! That got me back up and running back to Android 4.4.2 (along with HTC Sense 6.0). Might be jumping the gun but it also looks like my GPS is able to lock on now too!ust
But I think I overlooked the custom recovery part. I'm not clear on when I flash this portion:
RUU Mode TWRP 2.8.6.0 TWRP that will flash while in RUU mode
https://www.androidfilehost.com/?fid=96042739161893174
md5 5fb9035b4f860487a24b357b59edb18f
Click to expand...
Click to collapse
I tried to install TWRP through the Goole Play app TWRP Manager [Root] which prompted installation of BusyBox and a few other features. Once I tried to reboot into recovery mode I got the red triangle with exclamation point that doing volume_up + power brought me into the stock recovery, which of course failed at flashing anything. At that point I went to reboot back to normal and it then hung up forever on the white HTC splash screen, this time with the red text at the bottom "This build is for dev purposes only. Do not distribute out of HTC..."
Gonna reflash the RUU and get back to where I was for now.
UPDATE: Reflashed the RUU, now back to Android 4.4.2 with working GPS and wifi. Still not so sure about getting a custom recovery going though.
I still haven't figured out how to get ADB commands to work yet, so this part (if I understand it correctly) I'm still SOL on:
Optional If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_8_5.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_8_5L.zip
Click to expand...
Click to collapse
Otherwise, I downloaded Flashify from the Google Play and tried first flashing TWRP. Downloaded and installed just fine seemingly, but then when I tried to reboot to recovery I got the white screen with the green HTC logo in the middle along with the purple text at the top that reads "Loading (or booting?) into recovery..." but it just hangs. Went back to Flashify and tried CWM. Also downloaded and installed fine, but this time trying to reboot into recovery it'd show that same white screen only for a second and then go right back to the bootloader. Back in Flashify, tried the third option, Philz, and it wouldn't even download ("something went wrong, try again later").
Obviously I'm in need of getting a custom recovery on there, but once that's done I'd also like to update to Digitalhigh GPE. Once I do have a custom recovery working again, would I be okay to go ahead and go through the process linked below?
http://forum.xda-developers.com/showthread.php?t=2716306
And FWIW, my bootloader screen now has this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000 --- Used to be 3.19.0.0000
RARIO-0.89.20.0321 --- Used to be 1.12.20.1211
OpenDSP-v38.2.2-00542-M8974.0311 --- Used to be v47.2.2-00564-M8974_FO.1024
OS-1.55.605.2 --- Used to be 4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Apr 1 2014,00:26:53:290 --- Used to be Feb 3 2015,21:50:28.290
Click to expand...
Click to collapse
trevorparsons said:
dottat said:
Yesssss!! That got me back up and running back to Android 4.4.2 (along with HTC Sense 6.0). Might be jumping the gun but it also looks like my GPS is able to lock on now too!ust
But I think I overlooked the custom recovery part. I'm not clear on when I flash this portion:
I tried to install TWRP through the Goole Play app TWRP Manager [Root] which prompted installation of BusyBox and a few other features. Once I tried to reboot into recovery mode I got the red triangle with exclamation point that doing volume_up + power brought me into the stock recovery, which of course failed at flashing anything. At that point I went to reboot back to normal and it then hung up forever on the white HTC splash screen, this time with the red text at the bottom "This build is for dev purposes only. Do not distribute out of HTC..."
Gonna reflash the RUU and get back to where I was for now.
UPDATE: Reflashed the RUU, now back to Android 4.4.2 with working GPS and wifi. Still not so sure about getting a custom recovery going though.
I still haven't figured out how to get ADB commands to work yet, so this part (if I understand it correctly) I'm still SOL on:
Otherwise, I downloaded Flashify from the Google Play and tried first flashing TWRP. Downloaded and installed just fine seemingly, but then when I tried to reboot to recovery I got the white screen with the green HTC logo in the middle along with the purple text at the top that reads "Loading (or booting?) into recovery..." but it just hangs. Went back to Flashify and tried CWM. Also downloaded and installed fine, but this time trying to reboot into recovery it'd show that same white screen only for a second and then go right back to the bootloader. Back in Flashify, tried the third option, Philz, and it wouldn't even download ("something went wrong, try again later").
Obviously I'm in need of getting a custom recovery on there, but once that's done I'd also like to update to Digitalhigh GPE. Once I do have a custom recovery working again, would I be okay to go ahead and go through the process linked below?
http://forum.xda-developers.com/showthread.php?t=2716306
And FWIW, my bootloader screen now has this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000 --- Used to be 3.19.0.0000
RARIO-0.89.20.0321 --- Used to be 1.12.20.1211
OpenDSP-v38.2.2-00542-M8974.0311 --- Used to be v47.2.2-00564-M8974_FO.1024
OS-1.55.605.2 --- Used to be 4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Apr 1 2014,00:26:53:290 --- Used to be Feb 3 2015,21:50:28.290
Click to expand...
Click to collapse
I am not sure how....but you downloaded my older ruu. Use the one in the link to flash. There's also instructions for twrp in there as well.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse