Related
Last night I flashed the gingerbread coredroid ROM and it worked fine. I just didn't really like the looks of some things, so I thought I'd change to a different ROM.
I thought about flashing the ICS Insertcoin ROM, so I flashed it, and it kept trying to boot, but turned off and kept repeating. But then I read that I was supposed to update the firmware, so I took out the SIM card and connected it to the computer and copied the 3.24 RUU to the SD card.
I followed the instructions and the RUU set up properly through HBoot the first time. Then i went in to recovery to wipe data. It had to reboot the phone before I did anything else, and it went back into HBOOT and tried to install the RUU again, but this time it failed due to CID being incorrect! I didn't give it a second thought, but then the insertcoin ROM was doing the same thing, going through the boot up images and shutting off right in the middle, and repeating.
I tried another ICS ROM, Android Revolution, and same result. Failed booting. Then I tried restoring my nandroid backup from before coredroid, and it also kept trying to boot and then shut down. Then I tried coredroid again, and it had the same reaction, failed booting! I redownloaded the ICS RUU 4 times and repeated this process 4 different times, even with other GB versions of insertcoin and ARHD, and no dice!
I'm not entirely tech savvy, so maybe there is soemthing I havent covered yet. Now the RUU fails not because of CID, but because of incorrect Model ID. I read about goldcards, but I can't make a new one because the phone won't even boot! Please help me!
edit: as of now, the phone does not turn on to any rom or homescreen, ONLY Hboot and recovery.
Hello Jagerlowe,
The 3.24 RUU installs fully with 2 Boots into Bootloader, so there is nothing to be worried about. Here's how you could solve your problem.
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ARHD 6.2.1 ROM.
3. Boot & flash the suggested radio if you are using the ARHD ROM.
You should be alright
Please keep me posted about your problem and hope it helped!
Remember to Thank me!
CursedBat said:
Hello Jagerlowe,
The 3.24 RUU installs fully with 2 Boots into Bootloader, so there is nothing to be worried about. Here's how you could solve your problem.
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ARHD 6.2.1 ROM.
3. Boot & flash the suggested radio if you are using the ARHD ROM.
You should be alright
Please keep me posted about your problem and hope it helped!
Remember to Thank me!
Click to expand...
Click to collapse
I can't quite do that because the phone doesn't turn on. It goes to the boot screen then shuts off. Then turns on, boot screen, off again. So I can't connect it to the computer or do anything like that.
This thread might help you... ICS flashing is little bit different than GB...
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation 4G with Beats
Jagerlowe said:
I can't quite do that because the phone doesn't turn on. It goes to the boot screen then shuts off. Then turns on, boot screen, off again. So I can't connect it to the computer or do anything like that.
Click to expand...
Click to collapse
Can you boot your device into Recovery mode?
Jagerlowe said:
Last night I flashed the gingerbread coredroid ROM and it worked fine. I just didn't really like the looks of some things, so I thought I'd change to a different ROM.
I thought about flashing the ICS Insertcoin ROM, so I flashed it, and it kept trying to boot, but turned off and kept repeating. But then I read that I was supposed to update the firmware, so I took out the SIM card and connected it to the computer and copied the 3.24 RUU to the SD card.
I followed the instructions and the RUU set up properly through HBoot the first time. Then i went in to recovery to wipe data. It had to reboot the phone before I did anything else, and it went back into HBOOT and tried to install the RUU again, but this time it failed due to CID being incorrect! I didn't give it a second thought, but then the insertcoin ROM was doing the same thing, going through the boot up images and shutting off right in the middle, and repeating.
I tried another ICS ROM, Android Revolution, and same result. Failed booting. Then I tried restoring my nandroid backup from before coredroid, and it also kept trying to boot and then shut down. Then I tried coredroid again, and it had the same reaction, failed booting! I redownloaded the ICS RUU 4 times and repeated this process 4 different times, even with other GB versions of insertcoin and ARHD, and no dice!
I'm not entirely tech savvy, so maybe there is soemthing I havent covered yet. Now the RUU fails not because of CID, but because of incorrect Model ID. I read about goldcards, but I can't make a new one because the phone won't even boot! Please help me!
edit: as of now, the phone does not turn on to any rom or homescreen, ONLY Hboot and recovery.
Click to expand...
Click to collapse
did you solve this because i think im having the same issue as you
Mookie_Jones said:
did you solve this because i think im having the same issue as you
Click to expand...
Click to collapse
Can you boot your device into Recovery mode?
CursedBat said:
Can you boot your device into Recovery mode?
Click to expand...
Click to collapse
Yes, I can boot it into recovery and HBOOT, thats it.
Jagerlowe said:
Yes, I can boot it into recovery and HBOOT, thats it.
Click to expand...
Click to collapse
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/showthread.php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
Goodluck! Cheers
CursedBat said:
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/showthread.php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
Goodluck! Cheers
Click to expand...
Click to collapse
Oh my gosh! Can I like marry you!? You fixed my problem! Thank you so much!
Jagerlowe said:
Oh my gosh! Can I like marry you!? You fixed my problem! Thank you so much!
Click to expand...
Click to collapse
You're welcome I'm just glad to be of any use.
Good luck experimenting with ICS
Cheers!
Hi guys,
im really desperate here, my sensation xe (hboot 1.23, s-off), won't let me boot any flashed rom.
My firmware is 3.32 and im using 4ext recovery 1.005 RC3.
Even my Nandroid backup of ARHD 6.6.3 won't boot, the phone gets stuck in a bootloop (it does't even show the boot animation, only the splashscreen for a few seconds, then reboots).
i bet someone on here can help me, because i don't know what to do.
thank you in advance
best regards
el
If your hboot is 1.23 then you DO NOT have 3.32 firmware. Re-flash the firmware and try to reboot...
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
GROGG88 said:
If your hboot is 1.23 then you DO NOT have 3.32 firmware. Re-flash the firmware and try to reboot...
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
Click to expand...
Click to collapse
thanks for your reply, yeah i wasn't sure about the firmware since i did't know how to check without rom
i will reflash firmware and see if it boots ...brb.
thanks again for your reply
GROGG88 said:
If your hboot is 1.23 then you DO NOT have 3.32 firmware. Re-flash the firmware and try to reboot...
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
Click to expand...
Click to collapse
i reflashed the firmware, formatted all partitions in recovery, and flashed ARHD, but no luck i'm still stuck in a splashscreen bootloop.
the recovery (after flashing arhd) prompted something like "boot update pending, will reboot after update is finished"
maybe there is a problem with the latest rc of the 4ext touch recovery?
thanks again for your help
Are you definitely s-off, or are you simply *unlocked*? Also, did you run the superwipe script?
GROGG88 said:
Are you definitely s-off, or are you simply *unlocked*? Also, did you run the superwipe script?
Click to expand...
Click to collapse
i don't know
when i turn it off by pulling battery and then turn it on by pressing vol down and power (i think thats fastboot?) the second line from the top says S-Off RL
Ok, that's s-off.
Did you run superwipe?
Did you run an md5 checker on all of your files?
Is it still reading 1.23 on hboot? (should be 1.27.1100)
GROGG88 said:
Ok, that's s-off.
Did you run superwipe?
Did you run an md5 checker on all of your files?
Is it still reading 1.23 on hboot? (should be 1.27.1100)
Click to expand...
Click to collapse
if by superwipe you mean flash a file that's named superwipe, no i didn't.
i chose format all (except sd) in the 4ext touch wipe menu.
i did run an md5 check on all files.
the hboot version number says 1.27.1100.
i just reflashed recovery from fastboot to see if it helps (altough i flashed the same recovery version, so maybe theres some kind of bug?) but it is still stuck on splashscreen.
aww man i'm really desperate right now, i kind of need this phone because i have no replacement
Go to ARHD thread, download the superwipe script, flash it from recovery, and then flash ARHD again...
GROGG88 said:
Go to ARHD thread, download the superwipe script, flash it from recovery, and then flash ARHD again...
Click to expand...
Click to collapse
did it, flashed arhd afterwards, didn't work.
still stuck on splashscreen.
thank you so much for your help! any other idea?
I'm going to lunch. I'll ponder on it...
okay i got it working and here is what i did:
it seems 4ext recovery was trying to flash a messed up boot image over and over again.
i pulled the boot.img from the arhd zip file and flashed it via fastboot. it now seems to boot (it has gone past the splashscreen and now shows the boot animation).
thanks again for your.
i can not recommend the latest recovery
elgubbo said:
okay i got it working and here is what i did:
it seems 4ext recovery was trying to flash a messed up boot image over and over again.
i pulled the boot.img from the arhd zip file and flashed it via fastboot. it now seems to boot (it has gone past the splashscreen and now shows the boot animation).
thanks again for your.
i can not recommend the latest recovery
Click to expand...
Click to collapse
Cool! Glad you got it sorted out. Which boot.img were you selecting in 4ext, and which one did you pull from the rom.zip? Also, please send a bug report to madmaxx82 so he can look into it...
GROGG88 said:
Cool! Glad you got it sorted out. Which boot.img were you selecting in 4ext, and which one did you pull from the rom.zip? Also, please send a bug report to madmaxx82 so he can look into it...
Click to expand...
Click to collapse
both faux kernel boot.img, but somehow 4ext was stuck with an "old" boot.img from a previous aosp rom.
the feature "smartflash" was activated and somehow could not be deactivated. that way the recovery, everytime when it was done flashing the rom, flashed an aosp kernel afterwards.
at least that is my guess.
thanks again.
best regards
el
elgubbo said:
both faux kernel boot.img, but somehow 4ext was stuck with an "old" boot.img from a previous aosp rom.
the feature "smartflash" was activated and somehow could not be deactivated. that way the recovery, everytime when it was done flashing the rom, flashed an aosp kernel afterwards.
at least that is my guess.
thanks again.
best regards
el
Click to expand...
Click to collapse
That's the culprit there.
It's not the problem of recovery
The smart flash option is for ppl with SON and unlocked bootloader.. And as you said it retains the previous boot.img
As you are soff you should not enable it
.To disable smartflash go to tools in recovery there you will find the smartflash option
Also the latest recovery is awesome..
You just need to know what should be enabled and what should be not before using it
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
That's the culprit there.
It's not the problem of recovery
The smart flash option is for ppl with SON and unlocked bootloader.. And as you said it retains the previous boot.img
As you are soff you should not enable it
.To disable smartflash go to tools in recovery there you will find the smartflash option
Also the latest recovery is awesome..
You just need to know what should be enabled and what should be not before using it
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
yeah, i know that now. there is just one thing: the disabling in the recovery did not work for me.
also: when the recovery is upgradet it asked if i am soff. i misclicked once, but didn't think much of it since it CLEARLY says "if you are not sure, choose no (s-on)".
the thing is it automatically activates smartflash.
the main problem for me was that it could not be deactivated from the recovery. the recovery said "deactivating smartflash" and afterwards "smartflash deactivated" but it wasn't :/
thanks anyways (i know the recovery is the **** i love it, too)
I decided to join the xda-developers community after I spent literally 9+ hours trying to get my phone to work and looking for the answers and couldn't find any for my situation. I am hoping an experienced user can give me some much needed answers!
The reason I am trying to flash the ROM in the first place is because I recently replaced the LCD/Digitizer from another HTC Sensation but for some reason I am not able to connect to T-Mobile network. I thought maybe it was the antennas and I had knocked something loose when I was repairing it when the WiFi wasn't working either, but when I took it to my parents house and used their WiFi it started working. So I decided to flash the the Android Revolution HD 7.2 ROM and followed the guide from http://forum.xda-developers.com/showthread.php?t=1192300. I followed the instructions and was able to do everything but the permanent root but I realized I could just flash the ARHD ROM and have it be rooted that way. I flashed the ROM and when it was done it got stuck at the beats audio screen. Then I realized I hadn't flashed the 3.33 firmware first and thought that was the problem so I went back and wiped partitions and data and flashed it to that and then flashed ARHD but it still got stuck at the beats audio logo. So I went and restored it to the backup I made on clockworkmod recovery but then it would just reboot to HTC logo constantly so I flashed to 3.33 again and it still does that same thing. I've flashed ARHD and 3.33 firmware multiple times and it either gets stuck on the beats audio logo or keeps rebooting from HTC. So now it's on 3.33 firmware and I'm leaving it there until someone can help me.
When I did the S-Off, in the beginning it said "revolutionary" at the top. When I flashed the ROM it said *LOCKED*. Now it says -Firmware-3.33-.
This is what it looks like on my HBOOT.
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.350431_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
What do I do next? I know for a fact that if I flash the ARHD ROM again it will get stuck on the beats audio logo. I can't even start the phone on the 3.33 firmware because it restarts over and over to HTC logo screen. Also does anyone think flashing to this new ROM will get my phone to connect to the network again?
PLEASE HELP!!
thisiisdaniel said:
I decided to join the xda-developers community after I spent literally 9+ hours trying to get my phone to work and looking for the answers and couldn't find any for my situation. I am hoping an experienced user can give me some much needed answers!
The reason I am trying to flash the ROM in the first place is because I recently replaced the LCD/Digitizer from another HTC Sensation but for some reason I am not able to connect to T-Mobile network. I thought maybe it was the antennas and I had knocked something loose when I was repairing it when the WiFi wasn't working either, but when I took it to my parents house and used their WiFi it started working. So I decided to flash the the Android Revolution HD 7.2 ROM and followed the guide from http://forum.xda-developers.com/showthread.php?t=1192300. I followed the instructions and was able to do everything but the permanent root but I realized I could just flash the ARHD ROM and have it be rooted that way. I flashed the ROM and when it was done it got stuck at the beats audio screen. Then I realized I hadn't flashed the 3.33 firmware first and thought that was the problem so I went back and wiped partitions and data and flashed it to that and then flashed ARHD but it still got stuck at the beats audio logo. So I went and restored it to the backup I made on clockworkmod recovery but then it would just reboot to HTC logo constantly so I flashed to 3.33 again and it still does that same thing. I've flashed ARHD and 3.33 firmware multiple times and it either gets stuck on the beats audio logo or keeps rebooting from HTC. So now it's on 3.33 firmware and I'm leaving it there until someone can help me.
When I did the S-Off, in the beginning it said "revolutionary" at the top. When I flashed the ROM it said *LOCKED*. Now it says -Firmware-3.33-.
This is what it looks like on my HBOOT.
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.350431_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
What do I do next? I know for a fact that if I flash the ARHD ROM again it will get stuck on the beats audio logo. I can't even start the phone on the 3.33 firmware because it restarts over and over to HTC logo screen. Also does anyone think flashing to this new ROM will get my phone to connect to the network again?
PLEASE HELP!!
Click to expand...
Click to collapse
I'm having the same problem my HBOOT was 1.17.111 and needed 1.27 to install elegancia mod.so i was reading and it said i needed the 3.33 FW so i updated it and i'm now stuck just like you.
Joethelegend said:
I'm having the same problem my HBOOT was 1.17.111 and needed 1.27 to install elegancia mod.so i was reading and it said i needed the 3.33 FW so i updated it and i'm now stuck just like you.
Click to expand...
Click to collapse
I only needed to flash to 3.33 was because it was for Android Revolution HD. I'm not sure if you need to do that for the elegancia mod.
How did you update the firmware? Did you use the PG58IMG.zip method and if so have you removed it from your SD card afterwards? I know ARHD is best used with 4ext recovery too but i'm not sure it's a necessity. Check out this thread. There maybe some info on it.
http://forum.xda-developers.com/showthread.php?t=1472298
thisiisdaniel said:
I only needed to flash to 3.33 was because it was for Android Revolution HD. I'm not sure if you need to do that for the elegancia mod.
Click to expand...
Click to collapse
try to flash the 3.33fw from this thread
http://forum.xda-developers.com/showthread.php?t=1459767
before flashing check md5 sums(it is important)
and follow the installation steps carefully
after that flash the rom
if fails again then flash the boot.img of the rom manually
if don't know how see extra 1 step from here
http://forum.xda-developers.com/showthread.php?t=1631861
3484jacks said:
How did you update the firmware? Did you use the PG58IMG.zip method and if so have you removed it from your SD card afterwards? I know ARHD is best used with 4ext recovery too but i'm not sure it's a necessity. Check out this thread. There maybe some info on it.
http://forum.xda-developers.com/showthread.php?t=1472298
Click to expand...
Click to collapse
I used the zip method and I did remove it afterwards. I am using the clockworkmod recovery instead of the 4ext.
rzr86 said:
try to flash the 3.33fw from this thread
http://forum.xda-developers.com/showthread.php?t=1459767
before flashing check md5 sums(it is important)
and follow the installation steps carefully
after that flash the rom
if fails again then flash the boot.img of the rom manually
if don't know how see extra 1 step from here
http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
Sorry for being a noob but how do I check md5 sums? What do I compare the sums too? And also, why is it important to check?
thisiisdaniel said:
Sorry for being a noob but how do I check md5 sums? What do I compare the sums too? And also, why is it important to check?
Click to expand...
Click to collapse
put the firmware zip in the root of the sdcard
use any file manager and navigate to that zip
press and hold to the zip until it pops up a menu
go to proprerties
then you will see calculate md5 checksum or something like that
then check if it is the same with the one from the firmware thread
it is important because if you mess up with fw probably you will damage your device
rzr86 said:
put the firmware zip in the root of the sdcard
use any file manager and navigate to that zip
press and hold to the zip until it pops up a menu
go to proprerties
then you will see calculate md5 checksum or something like that
then check if it is the same with the one from the firmware thread
it is important because if you mess up with fw probably you will damage your device
Click to expand...
Click to collapse
I can't access the zip because I can't start up the phone. Is there any other way of checking md5 sums?
thisiisdaniel said:
I can't access the zip because I can't start up the phone. Is there any other way of checking md5 sums?
Click to expand...
Click to collapse
Hi,
MD5 is checked in recovery.
What recovery do you have?
thisiisdaniel said:
I can't access the zip because I can't start up the phone. Is there any other way of checking md5 sums?
Click to expand...
Click to collapse
no i don't know other way
if someone else knows pls post
edit:maybru has right
i didn't think it at all
malybru said:
Hi,
MD5 is checked in recovery.
What recovery do you have?
Click to expand...
Click to collapse
I have clockworkmod recovery.
thisiisdaniel said:
I have clockworkmod recovery.
Click to expand...
Click to collapse
Hi,
That is odd.
You say you have flashed ARHD ROM.
That should install 4 EXT recovery.
So,that means the flash did not work.
Have you actually had a ROM working on your phone since you changed the digitizer?
Also,there is a md5 checksum checker in 4 EXT.
Have a look around the CWM recovery,to see if there is one there.
How do I check md5 sums from recovery?
malybru said:
Hi,
That is odd.
You say you have flashed ARHD ROM.
That should install 4 EXT recovery.
So,that means the flash did not work.
Have you actually had a ROM working on your phone since you changed the digitizer?
Also,there is a md5 checksum checker in 4 EXT.
Have a look around the CWM recovery,to see if there is one there.
Click to expand...
Click to collapse
I haven't been able to get my phone past the HTC logo after 3.33 and up to the beats logo after ARHD.
thisiisdaniel said:
I haven't been able to get my phone past the HTC logo after 3.33 and up to the beats logo after ARHD.
Click to expand...
Click to collapse
Hi,
With your s-off status and current 3.33 firmware,there is no reason why it should not work.
Maybe ,the phone was not re-assembled properly?
Or did it work before the 3.33 firmware installation?
rzr86 said:
try to flash the 3.33fw from this thread
http://forum.xda-developers.com/showthread.php?t=1459767
before flashing check md5 sums(it is important)
and follow the installation steps carefully
after that flash the rom
if fails again then flash the boot.img of the rom manually
if don't know how see extra 1 step from here
http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
I flashed from the thread you mentioned but it still does the bootloop..
malybru said:
Hi,
With your s-off status and current 3.33 firmware,there is no reason why it should not work.
Maybe ,the phone was not re-assembled properly?
Or did it work before the 3.33 firmware installation?
Click to expand...
Click to collapse
Yeah it was working before I did the firmware installation but the only thing was that it was not connecting to the network. What do I do??
thisiisdaniel said:
Yeah it was working before I did the firmware installation but the only thing was that it was not connecting to the network. What do I do??
Click to expand...
Click to collapse
Hi,
OK.
Let's go about this a different way.
Look HERE
2. Flashing a recovery
1.Flash 4 EXT recovery.
2.Go into 4 EXT recovery/wipe/ and format all partitions except sd card.
3.Flash ARHD ROM again.
The firmware is not preventing the installation of the software.
But using a different recovery,and wiping properly ,may get the ball rolling again.
Once you get the ROM up and running,you can look at the radio/ril combination.
thisiisdaniel said:
Yeah it was working before I did the firmware installation but the only thing was that it was not connecting to the network. What do I do??
Click to expand...
Click to collapse
try to change recovery
use 4ext
then from recovery format all partitions except sdcard
flash the rom
see how it goes
I'm at a loss I've been trying for hours with not luck at restoring my phone. there is no backup. no roms will seem to boot. my SD card was wiped. i can boot into recovery and see my SD card and everything. and when trying to revert to a stock rom I use "fastboot getvar version-main' to find what version i need but it comes back blank. i have tried relocking and running a ruu with no luck
I have it unlocked
CID is stock with telus
hboot is 2.14
radio -0.18a.32.09.01_2
Cbaird said:
I'm at a loss I've been trying for hours with not luck at restoring my phone. there is no backup. no roms will seem to boot. my SD card was wiped. i can boot into recovery and see my SD card and everything. and when trying to revert to a stock rom I use "fastboot getvar version-main' to find what version i need but it comes back blank. i have tried relocking and running a ruu with no luck
I have it unlocked
CID is stock with telus
hboot is 2.14
radio -0.18a.32.09.01_2
Click to expand...
Click to collapse
I'm going to guess you're S-ON. Also, Good thing Telus doesn't make a 3.17 RUU or you'd have a shiny paperweight. You're messing with dangerous things and have no idea what you're doing.
To get a rom to boot, flash it and then extract the boot.img from the rom and
fastboot flash boot boot.img
then S-OFF once you get a rom to boot so you can RUU in the future if you need to
Still stuck in the boot loop at the white htc screen. does it matter the rom? as well when flashing the rom it comes back successful however says there is no md5 file found
Cbaird said:
Still stuck in the boot loop at the white htc screen. does it matter the rom? as well when flashing the rom it comes back successful however says there is no md5 file found
Click to expand...
Click to collapse
the rom should not matter.
Did you check the MD5 after downloading?
There is never an md5 file within the rom so it will always say that. You have to manually check the md5 with an md5 checker.
What rom are you flashing?
exad said:
I'm going to guess you're S-ON. Also, Good thing Telus doesn't make a 3.17 RUU or you'd have a shiny paperweight.
Click to expand...
Click to collapse
Brick from RUU while S-on and the Telus CID?
the nightly cm rom 10.2 from the 27th
redpoint73 said:
Brick from RUU while S-on and the Telus CID?
Click to expand...
Click to collapse
Ack true I forgot no supercid *facepalm* im rusty.
You should ba able to boot it. Did you check the md5?
checked and tried a different rom (slimbeam) and still stuck in boot loop. does it matter the order in which i flash the boot.img and the rom in?
It shouldn't matter what order you flash them in, before or after the ROM is fine. Can you elaborate on what you were doing to the phone before all this happened?
Sent from my Evita
http://forum.xda-developers.com/showthread.php?t=2450305&highlight=no+main+version
I was having this issue then I got it to boot into recovery mode so I figured i got it fixed but its stuck in a boot loop now with no rom
Ok but what caused all this to happen? Phones don't usually just get stuck in that situation on their own.
Sent from my Evita
timmaaa said:
Ok but what caused all this to happen? Phones don't usually just get stuck in that situation on their own.
Sent from my Evita
Click to expand...
Click to collapse
exactly the same way as the post says relocking the phone to go back to upgrade the hboot to flash roms that required them.
Ok, but you need to be more specific if you want help, linking to someone else's problem isn't really ideal. I'm gonna have to guess that you relocked the bootloader and ran an RUU? Which RUU exactly did you use? What's the filename?
Sent from my Evita
relocked the phone through fastboot. then tried to run this ruu RUU_Evita_UL_TELUS_WWE_1.91.661.4_Radio_0.18a.32.09.01_2_10.94.32.20L_release_266645_signed.exe to update hboot to 2.14 which is where it is now. however like the other forum my install failed and only got half the update. used the fix in the other forum to get it to at least recovery. where i discovered the my sd card had become corrupted fixed that issue and everything seem to be working in recovery when i went to flash a new rom. attempted to flash new rom and now all i get is a boot loop
Ok, the RUU only partially succeeded? You might need to try running an RUU again in that case, as that's probably what's causing your issues at the moment.
Sent from my Evita
tried running it again and get error 155 but for telus there is only 1 ruu and one ota
You'll have to research what error 155 means and try to rectify the problem.
Sent from my Evita
its says its the wrong ruu however there is only this ruu and an older ota for telus
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
Cbaird said:
its says its the wrong ruu however there is only this ruu and an older ota for telus
Click to expand...
Click to collapse
you cannot run that RUU because you're hboot is from 3.17 and that's an older RUU you need to be S-OFF to run an older RUU. You can try running the OTA for 3.17
You will need to download the 3.17 telus ota zip. Extract the recovery.img, copy the 3.17 OTA zip file to the phone, flash the recovery img in fasboot, boot to recovery, it will say cant load sd card, this is normal as it's looking for an external sd card of which there is none. select install from phone storage or install from internal storage. If you pick install from sd card it will error as there is no external sd card. then select the telus ota zip file.
I dont see and recovery.img in the file. there is a boot.img though
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk