I have, in the past had fastboot working on my Desire S in Windows 7 so perhaps this is a Windows 8.1 driver compatibility issue?
Firstly, I tried to downgrade from a very slow Jelly Bean to the Ice Cream Sandwich RUU, but the device got stuck in a bootloop showing the HTC logo and the RUU USB connection times out. So I figured that I might need to re-lock my device for the RUU to work. So I tried, but fastboot devices, and fastboot oem lock dont work. Windows 8.1 says Device unrecognized and I have tried reinstalling different versions of the drivers.
adb devices works when the phone is in Jelly Bean. It's just fastboot that doesn't work.
Please help?
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
try this
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
i will try this tonight.
i copied PG88IMG.ZIP to sd card,and i booted in bootloader,and it finds the file,it says loading then just parsing for 1 sec and nothing happens.
will post results tomorrow.
saga pvt ship s-on rl
hboot 2.02.0002
radio 3831.19.00.110
eMMC-boot
unfortunately it didn't work.
the driver provided didn't detect my phone.
if i format the sd card will it work?
is there any method to relock the bootloader from hboot or fastboot?i can enter recovery but every time i flash a new rom,i get a bootloop .
alllexander said:
i will try this tonight.
i copied PG88IMG.ZIP to sd card,and i booted in bootloader,and it finds the file,it says loading then just parsing for 1 sec and nothing happens.
will post results tomorrow.
saga pvt ship s-on rl
hboot 2.02.0002
radio 3831.19.00.110
eMMC-boot
Click to expand...
Click to collapse
Sorry for the newbish question, but have you both tried using different cables? I had this problem once, and it was the cable that was faulty. Charged fine, sdcard mounted fine - but neither adb nor fastboot worked.
allexander: I dont think PG88img.zip will run with s-on unless its an official, signed update thing. I think thats correct, anyway.
hello.
the pg88img.zip file is in fact the rom.zip renamed after a stock RUU installation.
I tried usint 3 different cables for the phone.
i can however connect through wifi adb.
can i do something to flash a different boot.img and then flash a ROM i know it works with usb connection and adb debugging?
alllexander said:
hello.
the pg88img.zip file is in fact the rom.zip renamed after a stock RUU installation.
I tried usint 3 different cables for the phone.
i can however connect through wifi adb.
can i do something to flash a different boot.img and then flash a ROM i know it works with usb connection and adb debugging?
Click to expand...
Click to collapse
Hmm interesting problem. Generally when the hboot says 'parsing PG88img.zip' but then that flashes for a second and goes away again, its because its trying to find a valid PG88IMG.zip but cant find one it thinks is valid enough to use. So I still think this relates to you being S-ON. For example maybe the hboot file is too old for your current version, in which case there may be fixes available using misc_version hack. That's just my instinct though. My radio has always been s-off via a cheap hardware clip, but I still struggled at first to flash PG88IMG.zip because I didnt understand the file format.
There is alot you could do if you could get PG88IMG.zip working.
Regarding your strange bootloop: are you certainly using 4EXTRecovery to wipe all partitions except the SD card before flashing a new rom?
nothing worked for me in windows 8.1 , cannot recognise the device in fastboot. only recognised in adb.
so just installed windows 7 in another partition. then fastboot recognised the phone. and i could flash the 4ext recovery. :good:
I am using twrp 2.4 and i can't flash another recovery.every time i try,it says recovery flashed then i get the same recovery when i reboot
rimpy said:
I have, in the past had fastboot working on my Desire S in Windows 7 so perhaps this is a Windows 8.1 driver compatibility issue?
Firstly, I tried to downgrade from a very slow Jelly Bean to the Ice Cream Sandwich RUU, but the device got stuck in a bootloop showing the HTC logo and the RUU USB connection times out. So I figured that I might need to re-lock my device for the RUU to work. So I tried, but fastboot devices, and fastboot oem lock dont work. Windows 8.1 says Device unrecognized and I have tried reinstalling different versions of the drivers.
adb devices works when the phone is in Jelly Bean. It's just fastboot that doesn't work.
Please help?
Click to expand...
Click to collapse
Hi your biggest issue is with windows 8 and Fastboot. They don't play nice. You will need a windows 7 PC to proceed. Once you have that. Reunlock your bootloader and flash a stock ROM from the dev section.
alllexander said:
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
Click to expand...
Click to collapse
It sounds like your micro USB port may be damaged. Is it loose feeling at all?
radical.entropy said:
Hmm interesting problem. Generally when the hboot says 'parsing PG88img.zip' but then that flashes for a second and goes away again, its because its trying to find a valid PG88IMG.zip but cant find one it thinks is valid enough to use. So I still think this relates to you being S-ON. For example maybe the hboot file is too old for your current version, in which case there may be fixes available using misc_version hack. That's just my instinct though. My radio has always been s-off via a cheap hardware clip, but I still struggled at first to flash PG88IMG.zip because I didnt understand the file format.
There is alot you could do if you could get PG88IMG.zip working.
Regarding your strange bootloop: are you certainly using 4EXTRecovery to wipe all partitions except the SD card before flashing a new rom?
Click to expand...
Click to collapse
You are correct good sir, s-on is the issue here. If the IMG.zip passed to the hboot is a lower version that the img installed to the device the hboot will skip it anyway. A misc hboot downgrade would work but you would need a unlocked hboot+ working recovery and to make a gold card to bypass the cid check of the ruu.
Its not that hard to do once you have done it before, but it can be daunting at first
Sent from my HTC Desire S using Tapatalk
i flashed just now flinny cm,and i got passed the htc logo,and the boot animation started but it was in a very low resolution and not centered on the screen.
i get to the point where my charging led is on,then nothing.it remains the same,through the boot process.
i am usint twrp 2.4 and i cannot flash another recovery ,not via terminal or apps in the phone.i will try to flash in recovery.can i do that?
ContactFront said:
try this
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Tried this and it didn't work.
DroidArmy said:
nothing worked for me in windows 8.1 , cannot recognise the device in fastboot. only recognised in adb.
so just installed windows 7 in another partition. then fastboot recognised the phone. and i could flash the 4ext recovery. :good:
Click to expand...
Click to collapse
Sounds like I need to do this. It worked for me last time I checked in Windows 7.
heavy_metal_man said:
Hi your biggest issue is with windows 8 and Fastboot. They don't play nice. You will need a windows 7 PC to proceed. Once you have that. Reunlock your bootloader and flash a stock ROM from the dev section.
Click to expand...
Click to collapse
Makes sense. I'm surprised there isn't a fix for it in Windows 8. My phone is already unlocked and I am wanting to install the RUU. Are you suggesting that I can't downgrade with RUU and need to install a stock ROM instead?
rimpy said:
Makes sense. I'm surprised there isn't a fix for it in Windows 8. My phone is already unlocked and I am wanting to install the RUU. Are you suggesting that I can't downgrade with RUU and need to install a stock ROM instead?
Click to expand...
Click to collapse
correct. while you could do it, its alot of hassle you would need to edit your misc partition so it states that your mainversion is lower than it really is. then the ruu is considered an "upgrade" and gets flashed. you would also need to make a goldcard using your sdcard and the goldcard tool in order to bypass the hboots cid check on your ruu. then it would run.
but much easier to flash a rooted stock rom go for one of these
alllexander said:
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
Click to expand...
Click to collapse
It is the incompatible of the driver with either Windows 8 & 8.1. I have to PCs, one with Windows 7 and the other with Windows 8.1; under either bootloader or recovery mode plugged in works with Win 7. On the other hand on win 8.1, recovery mode plugged in works fine but bootloader mode win 8.1 does not recognize the phone. I have tested them with the same phone and the same rom C11 by Devin Kin. No matter which HTC drivers installed, I got the same result.
i have now windows 7 64 bit,and it doesn't recognise my phone.
if i install usb mass storage app on the phone,if i connect the usb cable the phone notifies me about mass storage toggle,but not the usual from the ROM,the one from the app.
if i enable the usb mass storage the device isn't recognised,if i disable it it is also not recognised.
i can connect through adb wifi,i will post the logcat here,maybe someone can help.
also,can i use a command in adb shell to relock the bootloader?
if i can do that i cand try to flash PG88IMG through hboot .
i noticed i can push files through adb,can i flash boot.img from a different rom then flash the rom vie recovery immediately after?like fastboot flash after flashing a rom in recovery.
hello all.
i found the problem
it was the umt connector on the phone.
alllexander said:
hello all.
i found the problem
it was the umt connector on the phone.
Click to expand...
Click to collapse
Please tell us how to solve the problem.
Related
my phone info
hboot 1.18.0000
radio 10.14.9035.01_M
image 1.45.401.2
its not getting even stock rom with same image version
ruu says
trying to reboot in bootloader .............
but no luck
ever tried with htcdev bootunlock method to S-Off
gots this
fastboot oem get_identifier_token
C:\sdk>fastboot oem get_identifier_token
Program too big to fit in memory
Try to go fast-boot and run ruu should work.
If not take out the battery and hold volume down and swith on,run recovery or fast-boot and then run ruu.
yes i have done that too
in fastboot ruu runs and read info of my set (which show that its conected with pc)
but when ruu tried to reboot in bootloader
it takes almost 30 minutes then error comes of usb conectivity
problem is that bootloader are locked
it shows when pluged in fastboot mode
"Locked"
It will do, that's completely normal
i think still a driver problem with your laptop.
download the official one from HTC, just following the installation and STOP the installation when it wants you in install HTC SYNC!!
EddyOS said:
It will do, that's completely normal
Click to expand...
Click to collapse
what will do what ???
i could'nt get that
Rawahi said:
i think still a driver problem with your laptop.
download the official one from HTC, just following the installation and STOP the installation when it wants you in install HTC SYNC!!
Click to expand...
Click to collapse
tried on three different systems with three differernt os and checked all drivers
it does'nt make sense that its a conectivity problem
cuz ruu shows all info of my set. so its conected in fastboot with pc
So in my infinite wisdom I decided to download one more ROM and successfully bricked my phone bootlooped and cant seem to anything with it !! I cant mount the SD card and I have tried everything I have seen on here from the Fast boot kit etc...any enlightenment from someone would be appreciated..I have CWM on my phone but can not get past the boot animation....nor can I download a new rom or boot img....:crying: btw I have been at this since 9 and it is now 4 30 AM !!!
You need to download the RUU file and run it from your pc
Sent from my HTC One S using xda app-developers app
Adb push a rom onto the phone and flash
Sent from a man, using a mobile phone
k1llacanon said:
Adb push a rom onto the phone and flash
Sent from a man, using a mobile phone[/
I tried this no success....
Click to expand...
Click to collapse
flash original recovery (can be taken from the RUU), Relock bootloader afterwards run RUU on your computer
septamobile said:
flash original recovery (can be taken from the RUU), Relock bootloader afterwards run RUU on your computer
Click to expand...
Click to collapse
Ok can someone please explain to me whats ruu...I have no idea what that is or where I can get it from !!!
Ruu takes the phone completely back to stock but u need to find the right version for u so we need some information
What country are you in?
What is your radio version
Is your phone branded? E. G does it have t mobile on it
Sent from a man, using a mobile phone
Okay download an appropriate ruu for your device, international, tmobile, etc. Power down the device (Power button and volume down for 10 seconds) plug in the usb from the wall and power on and charge for a few hours. (Don't want your phone to permanently turn off and hard brick your device) Follow the instructions on the ruu to get back to stock.
Relock your bootloader before starting the ruu process. "fastboot oem lock" You should know the basics by now.
I'll Pm you some ruu that may work..
i have messed everything
I accidentally formatted my internal storage , cache , data, system and everything.
I cannot able to mount the USB and not even fastboot as it is saying waiting for device. My bootloader is the only thing thats working,not even my philz recovery is of no use . adb is not recognizing my phone . please help me
Please let me know about any solution for the problem
kt92 said:
I accidentally formatted my internal storage , cache , data, system and everything.
I cannot able to mount the USB and not even fastboot as it is saying waiting for device. My bootloader is the only thing thats working,not even my philz recovery is of no use . adb is not recognizing my phone . please help me
Please let me know about any solution for the problem
Click to expand...
Click to collapse
First thing you need to do is get fastboot working. At this point, you cannot do anything without it.
So go into bootloader, select fastboot, connect to pc and you should see it change to fastboot USB on your phone after a few seconds.
Navigate to the folder containing fastboot and hold shift and right click somewhere on the window, select open command prompt here. Now, enter the command:
fastboot erase cache
If it goes through, great. If not, you need to update drivers. Install the latest version of HTC sync on your PC.
Of no luck, try another PC, different USB port, different cable, whatever. You need to get it working.
Once it is working, you will need to fastboot recovery, boot.img, etc, but do what I said first, then report back.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Solved
ryanshew said:
First thing you need to do is get fastboot working. At this point, you cannot do anything without it.
So go into bootloader, select fastboot, connect to pc and you should see it change to fastboot USB on your phone after a few seconds.
Navigate to the folder containing fastboot and hold shift and right click somewhere on the window, select open command prompt here. Now, enter the command:
fastboot erase cache
If it goes through, great. If not, you need to update drivers. Install the latest version of HTC sync on your PC.
Of no luck, try another PC, different USB port, different cable, whatever. You need to get it working.
Once it is working, you will need to fastboot recovery, not.omg, etc, but do what I said first, them report back.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
yeah I followed the steps for making my bootloader work again , then i flashed RUU for my device and this worked without any error. I had the HTC__001 CID . soo it helped me in the RUU process
thanks for the solution
Today I flashed the last CleanRom 5.1 then I flashed kernel BeastMode evita 4.4 and the phone has bricked in the screen of HTC. So I did a big mistake, in the bootlloader i am pretty sure I have wiped the phone, now I have no ROM in the phone, and the TWRP will not let me select mount sd card. I have thinking in push the ROM in ADB but sincerely I have no idea how to do that. Actually I´m in the bootloader screen and connected the phone, appearing "Fastboot USB". Could someone kindly tell me what are the orders in the Command Prompt to connect the phone to my pc and push the rom?
The phone was with CM10 ROM, rooted and TWRP provided by a friend who is not available to help me.
BTW sorry for my regular english, I´m from Argentina.
juanfranrod said:
Today I flashed the last CleanRom 5.1 then I flashed kernel BeastMode evita 4.4 and the phone has bricked in the screen of HTC. So I did a big mistake, in the bootlloader i am pretty sure I have wiped the phone, now I have no ROM in the phone, and the TWRP will not let me select mount sd card. I have thinking in push the ROM in ADB but sincerely I have no idea how to do that. Actually I´m in the bootloader screen and connected the phone, appearing "Fastboot USB". Could someone kindly tell me what are the orders in the Command Prompt to connect the phone to my pc and push the rom?
The phone was with CM10 ROM, rooted and TWRP provided by a friend who is not available to help me.
BTW sorry for my regular english, I´m from Argentina.
Click to expand...
Click to collapse
My First advice, relock bootloader and run ruu...If your on the newer hboot don't you have to flash boot.img as well before flashing the rom? Did you wipe cashe and dalvik when you flashed? Did you see if rom first worked before flashing kernel?
WhatTheAndroid? said:
My First advice, relock bootloader and run ruu...If your on the newer hboot don't you have to flash boot.img as well before flashing the rom? Did you wipe cashe and dalvik when you flashed? Did you see if rom first worked before flashing kernel?
Click to expand...
Click to collapse
I have flashed boot.img in the aroma installer of cleanrom. Then I wipe cache and dalvik after flash rom. But I made the mistake of not checking if it worked the ROM before installing the new kernel.. I installed after the rom.
Could you explain me how to relock bootloader and run ruu?
Appreciate your help
juanfranrod said:
I have flashed boot.img in the aroma installer of cleanrom. Then I wipe cache and dalvik after flash rom. But I made the mistake of not checking if it worked the ROM before installing the new kernel.. I installed after the rom.
Could you explain me how to relock bootloader and run ruu?
Appreciate your help
Click to expand...
Click to collapse
I'm sure someone will provide a ruu download based on your phone. Fastboot oem lock command in fastboot to lock bootloader. I would wait though to see if there is still a way to flash Rom and mount your phones sd card.by the way did you create a recovery in twrp of stock rooted version?
You dont need to RUU. I don't know why everyone runs to that.
Open TWRP, mount usb storage.
If you're on windows, it should prompt you to format your sd card. Format it to fat32.
Copy whatever rom you want onto the card.
Install in TWRP.
Dance
He wiped his phone from bootloader... Therefore corrupting his SD card. He could adb push the rom to his card though
Sent from my One X using xda app-developers app
WhatTheAndroid? said:
I'm sure someone will provide a ruu download based on your phone. Fastboot oem lock command in fastboot to lock bootloader. I would wait though to see if there is still a way to flash Rom and mount your phones sd card.by the way did you create a recovery in twrp of stock rooted version?
Click to expand...
Click to collapse
Myrder said:
He wiped his phone from bootloader... Therefore corrupting his SD card. He could adb push the rom to his card though
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi, I still cannot solving my problem :/ I locked the phone with the command "fastboot oem lock" in fastboot. Then I downloaded a RUU called htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and I´ve executed the file in fastboot but appears during the installation process an error message that the phone is not connected with the USB cable, when obviously connected.
I have no idea what to do, I tried to check the connections, right now I'm trying to download another RUU apparently compatible, my CID is 11111111 and my HBOOT is 1.09.0000. Can you think of anything else I can do?
juanfranrod said:
Can you think of anything else I can do?
Click to expand...
Click to collapse
Did you reformat your SD card?
iElvis said:
Did you reformat your SD card?
Click to expand...
Click to collapse
Yes, I did it. I will try with another RUU (1.85) and see what happens.. for now I accept suggestions. Thanks
Your hboot is 1.09 which means you need the 1.85 firmware
area51avenger said:
Your hboot is 1.09 which means you need the 1.85 firmware
Click to expand...
Click to collapse
Newer RUU version should still work, but avoiding the 1.14 hboot is a good idea. So I too would recommend getting the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
OP should make sure he has the latest HTC drivers installed on the PC, or try re-installing them. Also try a different USB port. I've seen more than a few times on here, where it was simple as the drivers or the USB port.
redpoint73 said:
Newer RUU version should still work, but avoiding the 1.14 hboot is a good idea. So I too would recommend getting the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
OP should make sure he has the latest HTC drivers installed on the PC, or try re-installing them. Also try a different USB port. I've seen more than a few times on here, where it was simple as the drivers or the USB port.
Click to expand...
Click to collapse
damn.. now adb devices doesn't show my phone, there is no way to connect the phone to the pc, sooner if I did, I find it very strange
maybe for this reason the install of the RUU 1.85 has failed
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
Don't freak out, if your phone can be turned on it can be fixed.are you sure you have done everything they have said? Or have you tried unlocking again wiping and flashing a Rom? Does the computer make those 2 beeps when you plug your phone in?
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
You can't use adb in fast boot
Use
Fastboot devices
Sent from my HTC One X-
WhatTheAndroid? said:
Don't freak out, if your phone can be turned on it can be fixed.are you sure you have done everything they have said? Or have you tried unlocking again wiping and flashing a Rom? Does the computer make those 2 beeps when you plug your phone in?
Click to expand...
Click to collapse
Ok I unlocked the phone again, and wiped the phone. I tried typing in commands "fastboot flash zip Cleanrom5.zip" and gave me FAILED.. and yes, the computer make the beep (1) when I connect the phone, as a usb sound.
iElvis said:
Did you reformat your SD card?
Click to expand...
Click to collapse
hey iElvis, had not understood exactly where reformatting the SD card, as I did through the recovery and failed, will be the problem?
I have relocked the phone again, and I have tried to run the RUU in fastboot, but the last step in the installation appear an Error 170: Usb Connection Error... sigh
almost a complete day for nothing
juanfranrod said:
I have relocked the phone again, and I have tried to run the RUU in fastboot, but the last step in the installation appear an Error 170: Usb Connection Error... sigh
almost a complete day for nothing
Click to expand...
Click to collapse
This happened to me and I was able to do
fastboot flash recovery recovery.img (using original recovery)
Then reboot into bootloader then fastboot
fastboot boot TWRP.img
Then, once you're in TWRP, you can just flash a rom
Hope it helps! I'm still kinda nooby w/ htc as I was with motorola forever! I got my phone 1 month ago so... yeah
Try it! I was hopeless but I just kept trying!
Good luck!
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
Also, that just means your battery is low.
Just charge the phone while in bootloader overnight.
You should then be able to detect USB
juanfranrod said:
hey iElvis, had not understood exactly where reformatting the SD card, as I did through the recovery and failed, will be the problem?
Click to expand...
Click to collapse
You connect the phone to the PC, select "Mount USB" in TWRP. Then on your PC format the phone's SD card.
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?