Related
Hello, I have a T-Mobile HTC Sensation 4G, and I've ran into some problems recently. I'm a basic-intermediate user when it comes to Android, but I can't find a solution specifically for this. It started with a small problem but got worse and worse until I couldn't even boot correctly.
I started out installing a small custom battery mod, but that led to a few problems with the notification bar (not a big deal).
Then I tried to revert to the stock battery to fix the problem, format cache and dalvik cache in recovery, and reset. Then I was put into an infinite boot loop with the HTC splash, but going into cwm recovery was still possible.
Then, in recovery, I could not access my sd card for some reason, so I shut off, reinserted the sd card, and remounted it, then I reset again.
Now, it's impossible to boot to android at all, and I am completely stuck at HBOOT/FASTBOOT, and cannot access recovery OR perform a hard reset.
If I try to reinstall cwm recovery, I get a partition update fail as well...
I have full root, s-off, etc.
ROM- InsertCoin 3.3.1
Kernel- Stock
Hboot- 1.17.1011
Clockwork version- 5.0.0.8
Any suggestions? Am I bricked? I can give more details if needed.
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
neoissuperman said:
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Alright, thanks, I'll try that soon and see if it works.
Update: Unfortunately, I don't think I can flash anything, it just comes up with a partition update fail...
Anyone else know what I could try? I also tried to flash the 1.45 RUU, but it can't continue past the search for the bootloader.
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
joshndroid said:
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
Click to expand...
Click to collapse
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
joshndroid said:
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
Click to expand...
Click to collapse
Nope, still nothing, I even tried different sd cards and usb cables, with no difference...
So has my phone been reduced to a paperweight?
APmoss13 said:
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
Click to expand...
Click to collapse
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Divine flaw said:
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Click to expand...
Click to collapse
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
APmoss13 said:
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
Click to expand...
Click to collapse
ok.... i was just askin cause did the exact same thing (well almost, i tried to change the notification icons which resulted in my notification bar completely gone) you did and got into that infinite boot loop. and couldnt boot into android. and couldnt figure it out. the only thing i did was just install the ruu while i was in the fastboot screen and it worked. i wasnt aware that there was a 1.45 ruu for tmous but i dont think that should matter since you are scid anyways. now im just wonderin if you tried any other ruu's besides that one. for me i flashed the 1.29 ruu for tmous and that got me up and running...... sorry i couldnt help
well i recently came across a evo design (codename: kingdom), or hero-s as its called in other markets.
long story short, i flashed it to a local carrier revol (similar to metro/cricket).
and during that process i foolishly flashed some non-vol items to it and it is now bricked.
it only boots to the white htc splash and restarts in a loop
i can only access hboot and fastboot. i cant even get into recovery.
the only good things i have going for me are that i have my Unlock_code.bin so i can unlock/relock my bootloader (no s-off on this device)
and that i got a copy of my non-vol items from CDMA Workshop from before i borked it, and a copy of what broke it (from whiterabbit.org)
...im just not sure if thats enough
sucks cause it would be an easy fix if i could just use adb :/
any help is appreciated...tia
-d
a little more info on what ive tried so far
ive installed new recoveries, cwm and twrp, via fastboot PH44IMG.zip...they install fine but will not boot into the recovery.
ive installed the same recoveries via fastboot usb and RUU (flashboot flash recovery recovery.img)...they install fine but will not boot into the recovery.
ive tried the 'downgrade ruu' (RUU_Kingdom_S_Sprint_WWE_2.12.651.5_Radio_1.11.00.1228_NV_SPCS_2.97_removeCIQ_release_234636_signed.exe)...it flashes fine but still a boot loop (phone was 2.12.651.8 originally i believe).
ive tried ics ruu's but all ive found are for boost so i get a cid error...when i changed the cid to sprint i got another error that i cant recall.
i got my hands on sprints newest OTA update (OTA_Kingdom_ICS_35_S_Sprint_WWE_3.14.651.0-2.12.651.8_release_27047061zjyiwl2kn4vskn.zip)....but its a 'scripted update' so it will not install via hboot or fastboot.
i extracted the above OTA update, and retrieved the firmware.zip (contains boot, hboot, radio and recovery) and installed that fine...but no recovery still even after cwm/twrp reinstall.
even though my phone is unlocked its still s-on, so the only things i can manage to install manually with "Fastboot flash" are signed binaries (boot_signed.img and recovery_signed.img) anything else i get "FAILED (remote: 12 signature verify fail)"
anyone know if i can flash the rest of the update without error?
i still have dzdata.img, splash1.nb0,NV_MFG_eMMC_SPCS_2.97_1206_PRL51082.nb, ramdisk.img, rcdata_2.97.img and tp_atmel224_20aa.img maybe one of those will overwrite the spot i fudged up...idk
Hey, First post and it going to be about whether my phone is bricked for good or not. =/ I'd really appreciate some help as I've clearly not researched enough into this.
-My Rogers HTC One X had previously been rooted and unlocked to hboot 1.09 with cyanogenmod.
-I wanted to install Android Revolution HD, so i figure I needed an hboot update. I went ahead and flashed the phone with the 'firmware.zip' in 'OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip' (HUGE MISTAKE)
-After flashing, I tried to install Android Revolution HD but it had crashed mid way.
-Im able to access hboot and Im also able to go into fastboot and recovery (recovery-clockwork-6.0.2.8-evita).
-Rebooting the phone results in a blank screen after the HTC loading screen. So no adb.
My hboot shows this:
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I've tried locking it, flashing it with PJ83IMG.zip but it says: 'FAILED (remote: 44 hboot version check fail)'.
I've tried running 'RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe' but it gets half way and has Error 155.
Can anyone recommend a rom that will work in this configuration?
Any chance that I can still get S-off on the phone?
Any way to recover the phone at all? Just to be clear, I've flashed my Rogers phone with a Rogers OTA.
Thanks!
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Nevermind
Sent from my One XL using XDA Premium
Also that Rom is for the international HTC one x if the install hadn't crashed it would have bricked your phone
Sent from my HTC One X using Tapatalk 2
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
certitude said:
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
Click to expand...
Click to collapse
If you are going to s off, no need to really downgrade. This because you are turning security checks off. So it actually makes things a bit easier, and decreases the chances of bricking. I'm s off and on hboot 1.14 and was able to flash plenty of roms without a computer.
Sent from my Carbon-ize Evita using xda-developers app
You're not limited. You just need to fastboot flash boot boot.img any time you flash a ROM. If you're not a flashaholic like most of us, it's no big deal.
I wouldn't RUU with S-ON though, even though you didn't supercid, I bricked without supercid running an RUU after rooting.
So, if you don't plan to RUU you don't need to S-OFF either.
If you do intend to S-OFF, since you didn't need to supercid to unlock your bootloader, you would need to hex edit your CID to 11111111 if you wanted to S-OFF.
If you have any other questions, don't hesitate to ask but I suggest reading the stickies in all the sections. Good Luck
Thanks for the info everyone. I'll be keeping that in mind.
exad said:
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Click to expand...
Click to collapse
I got a Telus HTC one x yesterday. Spent all day reading about rooting etc and finally went ahead and did it. The unlocking part went without a hitch. I then went to install the clockwork recovery and I think I used an outdated one, because after I did it, it wouldn't boot into recovery. I could get into the bootloader, but checking anything else it wouldn't do anything. At that time I was still able to boot up my phone as normal. I then saw an updated clockwork recovery and tried that one, and it still wouldn't respond when I clicked on recovery. Now I can't do anything except get into the bootloader. My screen says the exact same thing as the original poster in terms of
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I'm so upset right now. I read your instructions on what you suggested to the OP but theirs was Rogers and mines Telus, and I never did have a custom ROM on there, and I don't have a clear cache option, just a 'clear storage'
Even selecting the 'reset phone' doesn't work. I'm ready to cry lol. I don't want to touch anything without guidance so I don't screw it up even further. I know this is the rogers forum but it's what came up when doing a google search.
Please help me. Please tell me this can be fixed. :crying:
Don't use CWM, use TWRP instead. Find version 2.3.3.1 at goo.im (just Google TWRP 2.3.3.1 evita download). Check the md5 of the download is correct. I'm assuming you have fastboot on your pc.
Put the TWRP recovery.img in your fastboot folder
Boot phone into bootloader, wait for it to say "fastboot usb" on the screen of your phone
Open a command prompt in that folder on your pc
Type in the following command:
fastboot flash recovery openrecovery-TWRP-2.3.3.1-evita.img (whatever the name of the recovery image is, I think that's right)
It will now write the recovery to your phone, wait for it to finish, it should only take a few seconds
Now type the following command in:
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to disconnect your phone and flash superuser.zip in your new recovery and have root access.
Sent from my HTC One XL using xda premium
omg!!!!! TY TY TY TY TY!!!!!!!!
It flashed into recovery!!!!!
I can't find where my superuser went...is there a way I can get it onto my phone? At this point I'm so nervous about screwing anything up that I'm afraid to play (which is rare for me as I'm normally quite good at all this stuff)
Do I really need the superuser? I'm planning on putting the ViperXL 3.2.7 rom on my phone. Can I just go straight to installing the rom?
I know where I went wrong now though. I used the international root instructions and not the AT&T ones as I assumed since I was Telus instead of Rogers or AT&T that that was the one I needed. Ugh! I feel like such an idiot!! I had android for quite a while then went to iphone for a little while (mistake) and had gotten so good at doing everything with those and forgot most of the steps involved with rooting android and the terminology. I'm happy to be back home with android!
You can just go ahead and flash ViperXL, that is pre-rooted so you'll be good to go. I just assumed you had a ROM running, so flashing the superuser zip would have just given that ROM root access.
Now, just make sure you stay here in the One XL (AT&T) forum. Make sure you only flash ROMs from here, because flashing one of the International ROMs can brick your phone, and we don't want that.
Sent from my HTC One XL using xda premium
I will be staying here!! lol
Just to be sure I have this correct...
I downloaded Viper and the boot img.
I'm going to go back to my cmd prompts, install the boot img
I'm getting hung up with understanding how to place the zip on my phone storage...My computer isn't showing it as being a separate drive.
I keep getting 'failed' errors with everything in TWRP. If I try to mount as USB storage, my computer says it needs to be formatted...
When I try to do anything else it shows up with failed.
Ok here's what you'll need to do:
Boot your phone into the bootloader (hold power and volume down key together, release power after a second but keep holding volume down until you're in bootloader)
Select recovery
Once recovery boots up, connect to pc with usb cable, select mount in recovery menu, then select mount storage
Your phone should now show up on your pc as a drive, copy the entire ROM zip to your phone
Once it's copied, do eject and safely remove the drive from your pc, and hit unmount on your phone screen
Hit the home button (little house on bottom left) in recovery
From main recovery select wipe, once in wipe menu you must wipe cache, dalvik cache, factory reset, and system
Once you've wiped all those, hit the home button again
Select install from the main recovery menu, then find the ROM you previously copied to your sd card and select it, then swipe to install, let the install finish (please note: if you're installing viper, it will have a few options to select during the install, select the ones you want. But right at the end of the install process there will be a checkbox for "reboot device now" and it will be checked, make sure you uncheck that before you hit finish/done)
Now you'll see two options, wipe cache/dalvik is one, do that, once that's done hit the home button again
From the main menu, hit reboot, and then bootloader, your phone will now boot back into the bootloader and fastboot usb should show up in red text on your screen if your usb cable is still connected
Now back to the pc, Copy the boot.img from the ROM zip and place it in your fastboot folder
Make sure you're connected with usb and fastboot usb is showing on your phone screen
Open a command prompt in your fastboot folder on pc and type in:
fastboot devices
You should see a device number return in the command prompt, if that shows up you're connected properly, so now type in the following command:
fastboot flash boot boot.img
This will flash the boot.img to your phone, let it finish
Once that's done you can reboot and you should be able to reboot into your new ROM
Sent from my Evita
It's not mounting...just keep getting a message from my computer that the drive needs to be formatted before I can use it...
btw, ty for all your help on this you've been amazingly helpful!
You may have corrupted your sd card. You'll have to format it, which means you'll lose all your data off it unfortunately. Do that first and then start again.
Sent from my Evita
It worked!!!!!! It booted up into Viper!!!!! TY a million times over!!!!!!!!!!
Awesome, so glad to see you got it going :thumbup:
And no problem at all, my pleasure, this is what XDA is all about.
Sent from my Evita
I have an XE, HBOOT 1.27 Unlocked and S-ON and I flashed many ROMs, always enabling SmartFlash in 4Ext.
Yesterday I tried to flash Sebastian's ROM, Revelation, and now my phone is stuck at HTC Splash Screen.
First I did a nandroid to my current ROM, Pac 1.1, then format all(except SD Card), then flashed Revelation and something went wrong.
After flash complete I confirmed reboot and right before 4Ext closed, it showed a message saying something like : It has been detected a change in your boot partition, a backup of previous has been made in /sdcard/4Ext/boot.
It stays like that for a few seconds(I always had this message when flashed other ROMs) and soon after says something "there has been an error, report it" (never seen this message before) and reboots, but keeps showing Splash Screen for ~5 seconds, turns black, then Splash Screen again and so on until I remove the battery.
What can I do and how?
Someone told me to push via fastboot the ROM's boot.img but there is a problem.I have a PC where the phone has never been connected via USB cable, so I have no driver/tool anything.
When I connect it to PC, nothing shows up.
If I select FASTBOOT from the bootloader menu, still nothing shows up on PC.I tried from 4Ext menu Toggle usb connection, but still no trace on my PC.
I beg you, help me.
EDIT : I just found out that Sebastian messed up something in the installer, and all I have to do is to flash the boot.img through fastboot.
doublin said:
I have an XE, HBOOT 1.27 Unlocked and S-ON and I flashed many ROMs, always enabling SmartFlash in 4Ext.
Yesterday I tried to flash Sebastian's ROM, Revelation, and now my phone is stuck at HTC Splash Screen.
First I did a nandroid to my current ROM, Pac 1.1, then format all(except SD Card), then flashed Revelation and something went wrong.
After flash complete I confirmed reboot and right before 4Ext closed, it showed a message saying something like : It has been detected a change in your boot partition, a backup of previous has been made in /sdcard/4Ext/boot.
It stays like that for a few seconds(I always had this message when flashed other ROMs) and soon after says something "there has been an error, report it" (never seen this message before) and reboots, but keeps showing Splash Screen for ~5 seconds, turns black, then Splash Screen again and so on until I remove the battery.
What can I do and how?
Someone told me to push via fastboot the ROM's boot.img but there is a problem.I have a PC where the phone has never been connected via USB cable, so I have no driver/tool anything.
When I connect it to PC, nothing shows up.
If I select FASTBOOT from the bootloader menu, still nothing shows up on PC.I tried from 4Ext menu Toggle usb connection, but still no trace on my PC.
I beg you, help me.
Click to expand...
Click to collapse
Hi,
Try flashing a STOCK ROM
Choose the XE in the second post.
Otherwise you will have to setup your PC to run a RUU,and return everything back to square one.
The weird thing is that even if I try to flash another ROM, stil the same problem.
I format all except SD card,wipe cache+dalvik, mount SD card into PC and delete folder 4Ext/boot_backup.
Go back to 4Ext, enable SmartFlash and flash CM 10.1 by Albino . Reboot, I get the message about my boot partition has been modified, but not the error too, and when it reboots, stuck at splash screen.
I'm desperate.
doublin said:
The weird thing is that even if I try to flash another ROM, stil the same problem.
I format all except SD card,wipe cache+dalvik, mount SD card into PC and delete folder 4Ext/boot_backup.
Go back to 4Ext, enable SmartFlash and flash CM 10.1 by Albino . Reboot, I get the message about my boot partition has been modified, but not the error too, and when it reboots, stuck at splash screen.
I'm desperate.
Click to expand...
Click to collapse
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
malybru said:
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
Click to expand...
Click to collapse
Ok thank you for your links.
I'll try to do it tomorrow `cause right now I can't keep my concentration, too late and had a long day.
malybru said:
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
Click to expand...
Click to collapse
actually if he setup the pc with adb and fastboot files he will be able to flash the boot.img manually
so why the ruu.exe?
rzr86 said:
actually if he setup the pc with adb and fastboot files he will be able to flash the boot.img manually
so why the ruu.exe?
Click to expand...
Click to collapse
I tried that yesterday with the help of a guy, but no success.
I installed all necessary drivers, adb and fastboot, but I can't get my phone discovered on my PC.
If the boot partition would be screwed, why it doesn't work when I try to flash other ROM? Like CM 10.1 or the XE Stock that I've been suggested a few posts above. Flashing this ROMs, shouldn't the boot partition be written with the ROM's files, and everything should turn back as normal?
doublin said:
I tried that yesterday with the help of a guy, but no success.
I installed all necessary drivers, adb and fastboot, but I can't get my phone discovered on my PC.
If the boot partition would be screwed, why it doesn't work when I try to flash other ROM? Like CM 10.1 or the XE Stock that I've been suggested a few posts above. Flashing this ROMs, shouldn't the boot partition be written with the ROM's files, and everything should turn back as normal?
Click to expand...
Click to collapse
It should rewrite the boot partition. Are you sure 4ext says "a pending update to..." and the process completes?
First boot after a new flash can take as long a 10mins. Wait it out.
Anyway if it diesnt work, try another wipe (all except sdcard) flash another rom, and if you're still stuck, use an ruu.
Happy to help.
Far_SighT said:
It should rewrite the boot partition. Are you sure 4ext says "a pending update to..." and the process completes?
First boot after a new flash can take as long a 10mins. Wait it out.
Anyway if it diesnt work, try another wipe (all except sdcard) flash another rom, and if you're still stuck, use an ruu.
Happy to help.
Click to expand...
Click to collapse
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
doublin said:
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
Click to expand...
Click to collapse
There you go. The reason your phone is in a bootloop is that the correct boot.img is not written.
And something is not right with your recovery. It could be a bad flash (I'm not sure).
I don't think you need to use an ruu. Just get on a pc that recognizes your device, and flash the correct boot.img.
I would advise that you flash the recovery.img again.
EDIT: Change usb port to 2.0. Try all usb ports on your computer. It is quite common that fastboot recognizes devices on some usb ports and not on others.
Alternatively read this, point 4. This will surely work if you can't get another pc
doublin said:
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
Click to expand...
Click to collapse
Hi,
If you need windows 7 & 8 drivers, look HERE
If it worked on your old computer,then,it will still work now.
Far_SighT said:
There you go. The reason your phone is in a bootloop is that the correct boot.img is not written.
And something is not right with your recovery. It could be a bad flash (I'm not sure).
I don't think you need to use an ruu. Just get on a pc that recognizes your device, and flash the correct boot.img.
I would advise that you flash the recovery.img again.
EDIT: Change usb port to 2.0. Try all usb ports on your computer. It is quite common that fastboot recognizes devices on some usb ports and not on others.
Alternatively read this, point 4. This will surely work if you can't get another pc
Click to expand...
Click to collapse
I think this is the key to my problem. I checked the link you gave me and I think I might get it done using that method.
Gonna give it a try as soon as I get some free time later today.
PS : I tried all 3 usb ports on PC, ofc.
Thank you, I will keep this topic update with results.
I'm having a hard time finding the right RUU for my phone, as I don't have access to fastboot, which would make my job a lot easier.
I found a list with providers and CIDs and I suppose mine is HTC-ITA HTC__405 , since I bought it in Italy and it was unbranded.
But i can't get software version, as it asks me to go to setting/About phone . I can't do that.
I think the right RUU is RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504, so now I'm downloading that and then move on step 4 on that tutorial.
Hope I just won't brick the phone.
doublin said:
I'm having a hard time finding the right RUU for my phone, as I don't have access to fastboot, which would make my job a lot easier.
I found a list with providers and CIDs and I suppose mine is HTC-ITA HTC__405 , since I bought it in Italy and it was unbranded.
But i can't get software version, as it asks me to go to setting/About phone . I can't do that.
I think the right RUU is RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504, so now I'm downloading that and then move on step 4 on that tutorial.
Hope I just won't brick the phone.
Click to expand...
Click to collapse
You can flash only one particluar ruu. Just make sure it's pyramid le(sensation xe). You will not be able to flash a wrong one, so no need to worry.
Far_SighT said:
You can flash only one particluar ruu. Just make sure it's pyramid le(sensation xe). You will not be able to flash a wrong one, so no need to worry.
Click to expand...
Click to collapse
Yea I'm downloading right now RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504
Says LE, so I should be fine.
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
did you check also if the bootloader screen says fastboot usb?
malybru said:
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
Click to expand...
Click to collapse
OOps, forgot that step (I flash ruu via ruu.exe)
malybru said:
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
Click to expand...
Click to collapse
But I'm gonna do the step 4 which says only to execute the RUU .exe but don't do anything, and in the temp folder on my pc I will find a file which then I'll have to move to the SD Card and flash straight from my recovery.
rzr86 said:
did you check also if the bootloader screen says fastboot usb?
Click to expand...
Click to collapse
When I vol down & power to get in bootloader I see :
FASTBOOT
RECOVERY
FACTORY RESET
SIM LOCK
IMAGE CRC
I don't know about fastboot usb...
Anyway, selecting FASTBOOT and connecting my phone to PC, nothing shows up, and running fastboot commands doesn't work, there's no link between pc and phone.
doublin said:
But I'm gonna do the step 4 which says only to execute the RUU .exe but don't do anything, and in the temp folder on my pc I will find a file which then I'll have to move to the SD Card and flash straight from my recovery.
When I vol down & power to get in bootloader I see :
FASTBOOT
RECOVERY
FACTORY RESET
SIM LOCK
IMAGE CRC
I don't know about fastboot usb...
Anyway, selecting FASTBOOT and connecting my phone to PC, nothing shows up, and running fastboot commands doesn't work, there's no link between pc and phone.
Click to expand...
Click to collapse
when you select fastboot does it say after that fastboot usb in bootloader screen?
actually have you enabled usb debugging mode from tettings?
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Update:
The phone is working and has an update but it can not update on the device, is there a way i can get the downloaded OTA file on to my PC?
CoolAndroid1 said:
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Click to expand...
Click to collapse
Hi,
What do you want to flash stock sense 6...??
greets
shivasrage said:
Hi,
What do you want to flash stock sense 6...??
greets
Click to expand...
Click to collapse
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
CoolAndroid1 said:
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
Click to expand...
Click to collapse
Ok
First I recommend you to unlock your bootloader.
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
I´m sorry but without get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
shivasrage said:
Ok
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
With out get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
Click to expand...
Click to collapse
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
CoolAndroid1 said:
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
Click to expand...
Click to collapse
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Ok, I will use a win 7 pc and let you know
shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
After i fix my drivers issue what can i do afterwards?
shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
I can now do the fastboot command from CMD
CoolAndroid1 said:
After i fix my drivers issue what can i do afterwards?
Click to expand...
Click to collapse
If you have a connection via fastboot you first have to decide what ROM you want, search for the matching firmware.
for example flash the latest firmware for M_4... 4.09.401.3 from here (new partition layout for e.g. sense 6):
https://docs.google.com/file/d/0BzCFBBNdXagdcEMybkdBME5iUE0/edit
After that flash TWRP 2.7.1.1 or philz and format all you have to try one of this recoverys should work.
Next push or sideload a ROM via adb I recommend you one them:
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
You can decide what you want rooted or not it doesn´t matter.
After installing with succsess try to reboot that´s it.
greets
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
jollywhitefoot said:
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
Click to expand...
Click to collapse
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
CoolAndroid1 said:
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
Click to expand...
Click to collapse
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
jollywhitefoot said:
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
CoolAndroid1 said:
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
Click to expand...
Click to collapse
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
jollywhitefoot said:
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
Click to expand...
Click to collapse
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
CoolAndroid1 said:
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
Click to expand...
Click to collapse
That's what i had to do when i first tried to root my phone. I was on Windows 7, but it was an old install and had all kinds of software on it that might have been preventing usb from working (iTunes, HTC Sync, some other random software, etc.) Sometimes, I would even have trouble connecting an external HD!
I ended up installing a clean copy of XP on an old computer that i now use strictly for flashing stuff to my phone.
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
CoolAndroid1 said:
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
Click to expand...
Click to collapse
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
jollywhitefoot said:
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
Click to expand...
Click to collapse
Hello,
I found an FUU for 4.4 Kitkat on the link you posted earlier, It does all the necessary actions with no failures and completes with a Congrats screen but the firmware is the same?