I want to flash TWRP but just discovered that i cannot enter download mode.
I can enter bootloader mode (white screen), recovery mode. But as long as i try to enter download mode i see small HTC logo then after a while phone reboots again and go normal android boot.
I've tried to enter download mode from bootloadr, from recovery, from adb "adb rebood download"
Result is always the same.
FW 1.80.709.
What i'm doing wrong??
fastboot oem rebootRUU also doesn't boot into download mode. Same small HTC logo and then reboot automatically into normal android boot.
Can anyone help?
from bootloader mode i cannot even flash firmware.zip to correct possible errors. Such a stupid developers are in HTC - don't leave any chance to fix the problem!
very angry at HTC!
I had many Samsung devices, and ASUS Zenfone - and never had such stupid softbrick...
Everything is done from download mode. Seems like your out of luck. Maybe put a description what you have done to your phone prior this happening.
Nothing special i did.
Bought this phone couple months ago. Had no time to configure it, so it just laid on table. I only unlocked the bootloader through htcdev site and was updating it when new fw out. And yesterday i've decided to start to use it. The first thing i wanted to do is flash TWRP. And discovered that i can't enter to download mode.
Probably the last OTA wasn't sucessful because phone didn't restart when finished updating.
That could be the cause....
Tryed a factory reset?
yldlj said:
Tryed a factory reset?
Click to expand...
Click to collapse
of course
Probably the part where download mode code is, didn't update to v1.80 and thus don't agree with bootloader.
Although, HTC has long history in PDA/Phone manufacturing, they still don't know how to write the proper code. They don't understand how to write protected bootloader with high resistance to bricks. Why they don't allow to flash protected partitions with OFFICIAL SIGNED images?? Stupidity!
They should learn from Samsung and even ASUS how to write correct bootloaders.
"You asked for it, we delivered" in boot unlock page looks like loud laughing to their customers
sorg said:
I want to flash TWRP but just discovered that i cannot enter download mode.
I can enter bootloader mode (white screen), recovery mode. But as long as i try to enter download mode i see small HTC logo then after a while phone reboots again and go normal android boot.
I've tried to enter download mode from bootloadr, from recovery, from adb "adb rebood download"
Result is always the same.
FW 1.80.709.
What i'm doing wrong??
Click to expand...
Click to collapse
DId you ever get your phone working? I can't enter download mode either, which means I can't flash any recovery. I can boot to the bootloader and fastboot recognizes a devices but adb doesn't from the bootloader screen and i get stuck in a bootloop if i try to select the boot to recovery or download mode options. So i also can't boot into recovery.
I pretty desperate at this point. I don't know what to do. The bootloader says
software status: official
unlocked
s-off
bootloader screen also says:
DDR TEST (LOOPING)
and I'm not sure what that means.
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
Extract hosd.img from your current firmware.zip and flash in bootloader.
Fastboot flash hosd hosd.img
Had the same issue with my M9 before.
I've repaired in HTC service center. And since i had to request new key to unlock the bootloader (old key didn't work) - they've replaced motherboard!
hi there,
did you manage to fix the problem? im having the exact same issue...please advise if do so...thanks
CPUser20 said:
DId you ever get your phone working? I can't enter download mode either, which means I can't flash any recovery. I can boot to the bootloader and fastboot recognizes a devices but adb doesn't from the bootloader screen and i get stuck in a bootloop if i try to select the boot to recovery or download mode options. So i also can't boot into recovery.
I pretty desperate at this point. I don't know what to do. The bootloader says
software status: official
unlocked
s-off
bootloader screen also says:
DDR TEST (LOOPING)
and I'm not sure what that means.
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
Click to expand...
Click to collapse
In a similar boat here - 1-week-old HTC 10 bricked
I flashed the Nougat OTA zip successfully, then realized that TWRP doesn't yet work with Nougat. I tried flashing back to M with fastboot flash zip m_ruu.zip, but fastboot refuses to downgrade.
So I went into download mode, and flashed a backup of M's boot partition with fastboot flash boot m_boot.img, thinking that this will allow me to downgrade the other partitions back to M. Ooops.
Now I can only get to the white background bootloader screen, but neither download mode, nor recovery, nor system.
I tried flashing both M's and N's hosd image, and neither will allow booting into download mode. As mentioned in previous posts, unless you can boot into download mode, you can't flash any other partition.
Furthermore, looks like you can only flash an HTC-signed kernel / initramfs to the hosd partition. I tried flashing both M's / N's boot image to hosd, and in both cases got an error saying it failed ASN1 verification.
Sad :crying:
Maybe this will help:
http://forum.xda-developers.com/showpost.php?p=69870232&postcount=974
Tarima said:
Maybe this will help:
http://forum.xda-developers.com/showpost.php?p=69870232&postcount=974
Click to expand...
Click to collapse
Nope...on the white background bootloader screen, when trying to flash (with fastboot) any other partition except hosd, I'm getting
Code:
sending 'radio' (54625 KB)... OKAY
writing 'radio'... FAILED (remote: cannot flash this partition in s-on state)
...but I can't figure out how to s-off in the current state either. Sunshine is an APK and requires the phone to boot into system. XTC2Clip's s-off instructions require entering into recovery mode.
Flashing different firmwares & RUUs without s-off is a big gamble
Sent from my HTC6545LVW using XDA-Developers mobile app
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
jichuan89 said:
In a similar boat here - 1-week-old HTC 10 bricked
I flashed the Nougat OTA zip successfully, then realized that TWRP doesn't yet work with Nougat. I tried flashing back to M with fastboot flash zip m_ruu.zip, but fastboot refuses to downgrade.
So I went into download mode, and flashed a backup of M's boot partition with fastboot flash boot m_boot.img, thinking that this will allow me to downgrade the other partitions back to M. Ooops.
Now I can only get to the white background bootloader screen, but neither download mode, nor recovery, nor system.
I tried flashing both M's and N's hosd image, and neither will allow booting into download mode. As mentioned in previous posts, unless you can boot into download mode, you can't flash any other partition.
Furthermore, looks like you can only flash an HTC-signed kernel / initramfs to the hosd partition. I tried flashing both M's / N's boot image to hosd, and in both cases got an error saying it failed ASN1 verification.
Sad :crying:
Click to expand...
Click to collapse
You should be 100% to RUU. It's just a good practice
CPUser20 said:
DId you ever get your phone working? I can't enter download mode either, which means I can't flash any recovery. I can boot to the bootloader and fastboot recognizes a devices but adb doesn't from the bootloader screen and i get stuck in a bootloop if i try to select the boot to recovery or download mode options. So i also can't boot into recovery.
I pretty desperate at this point. I don't know what to do. The bootloader says
software status: official
unlocked
s-off
bootloader screen also says:
DDR TEST (LOOPING)
and I'm not sure what that means.
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
Click to expand...
Click to collapse
Sent from my HTC6545LVW using XDA-Developers mobile app
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
And i've left the phone charging over a longer time period, but every time i plug the phone in while it's off, the Orange LED light turns on, then the battery icon pops up, and then the phone turns on and its begins looping all over again. I read here on XDA that the phone isn't charging unless the LED light is registering a signal.
Ultimately, an RUU doesn't work for me. I get the error saying my battery is below 30%, and it aborts. I'd really like to get it running again so any help will be very much appreciated.
sjpritch25 said:
Flashing different firmwares & RUUs without s-off is a big gamble
Sent from my HTC6545LVW using XDA-Developers mobile app
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
You should be 100% to RUU. It's just a good practice
Sent from my HTC6545LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
sjpritch25 said:
Flashing different firmwares & RUUs without s-off is a big gamble
Click to expand...
Click to collapse
You are absolutely right, it was totally dumb :crying:
Unbelievable - I actually managed to unbrick my HTC 10!! :victory::victory::victory: I still don't understand exactly what happened, but I'll document everything I did...
Before:
S-ON
Flashed bad boot image in download mode
Could not enter download, RUU, recovery, or system mode - all of them enter into bootloop
Could only enter white background bootloader mode (Volume Up + Volume Down + Power), which only allows flashing signed hosd image
What I did:
Followed @Tarima's link above. With the phone in the white background bootloader mode, I ran fastboot flash $x $x.img with $x = each of the partitions. Except for hosd, all the other commands printed an error like
Code:
sending 'xbl' (1809 KB)... OKAY
writing 'xbl'... FAILED (remote: cannot flash this partition in s-on state)
but I continued anyway.
Selected "REBOOT TO BOOTLOADER" from white background bootloader
Downloaded an RUU exe file from here (I got the 1.96.617.20 version, but in hindsight it probably doesn't matter which version), and extracted an RUU zip file (following this guide on Linux)
Renamed the RUU ZIP to 2PS6IMG.zip, copied it to the root of an empty FAT32-formatted microSD card, and inserted the card into the HTC 10 (inspired by this post and this post)
Selected "BOOT TO DOWNLOAD MODE" from white background bootloader
This triggered a screen prompting whether to install update from SD card (photo).
I didn't need to actually install the update from the SD card; instead, the presence of a valid update on the SD card may have short-circuited whatever was causing the download mode to crash loop, and allowed the phone to enter download mode and accept fastboot flash commands. Since my problem was a bad boot image, I just did
Code:
fastboot flash boot boot.img
with the boot.img extracted from the official Nougat OTA zip's firmware.zip, and it worked! Phone was able to boot back into system / download / RUU / recovery. :victory:
I'd already given up hope and bought another HTC 10 off Swappa I've now learned my lesson and I'm going to S-OFF at once.
jichuan89 said:
Unbelievable - I actually managed to unbrick my HTC 10!! :victory::victory::victory: I still don't understand exactly what happened, but I'll document everything I did...
Before:
S-ON
Flashed bad boot image in download mode
Could not enter download, RUU, recovery, or system mode - all of them enter into bootloop
Could only enter white background bootloader mode (Volume Up + Volume Down + Power), which only allows flashing signed hosd image
What I did:
Followed @Tarima's link above. With the phone in the white background bootloader mode, I ran fastboot flash $x $x.img with $x = each of the partitions. Except for hosd, all the other commands printed an error like
Code:
sending 'xbl' (1809 KB)... OKAY
writing 'xbl'... FAILED (remote: cannot flash this partition in s-on state)
but I continued anyway.
Selected "REBOOT TO BOOTLOADER" from white background bootloader
Downloaded an RUU exe file from here (I got the 1.96.617.20 version, but in hindsight it probably doesn't matter which version), and extracted an RUU zip file (following this guide on Linux)
Renamed the RUU ZIP to 2PS6IMG.zip, copied it to the root of an empty FAT32-formatted microSD card, and inserted the card into the HTC 10 (inspired by this post and this post)
Selected "BOOT TO DOWNLOAD MODE" from white background bootloader
This triggered a screen prompting whether to install update from SD card (photo).
I didn't need to actually install the update from the SD card; instead, the presence of a valid update on the SD card may have short-circuited whatever was causing the download mode to crash loop, and allowed the phone to enter download mode and accept fastboot flash commands. Since my problem was a bad boot image, I just did
Code:
fastboot flash boot boot.img
with the boot.img extracted from the official Nougat OTA zip's firmware.zip, and it worked! Phone was able to boot back into system / download / RUU / recovery. :victory:
I'd already given up hope and bought another HTC 10 off Swappa I've now learned my lesson and I'm going to S-OFF at once.
Click to expand...
Click to collapse
Similar thing happened to me .. I'm S-ON and had been flashing the proper firmwares from the get go by renaming them to 2PS6IMG with no problems.. then I upgraded to N firmware and it was smooth sailing.. then i decided to start fresh and formatted. That's when the problem of not being able to get into download mode started. I guess formatting did something to the partition I dunno.. anyway I did your steps of formatting a new sd in my phone as FAT32, dropped the 2PS6IMG zip on the card and it triggered download mode.. really strange.. thanks for posting your steps :good:
Glad to know it helped :victory:
Related
Due to the lack of time, I cannot update this thread as frequently as I want to, so from now on, please refer to the HTC One X - XDA Developers Wiki
This guide is based on information found in leejames55 HBOOT loop thread and torxx tutorial, I just wanted to make thing clear, simple and consolidate all information in one place for non-dev users. So thanks to them and everyone who contributed.
After seeing alot of people having problem after flashing a rom, restoring RUU, re-locking bootloader, I've decided to make this guide in order to help everyone. If you follow this guide there's a good chance that you will manage to recover your phone
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30% - IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
On computer type:
Code:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
If you cannot flash RUU, go into recovery etc. because battery is below 30%
IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery. So, flash the new recovery and this problem will NOT happen.
ckpv5 said:
I don't think he can do that as more and more people have this problem as stated on OP:
Cannot flash RUU because battery is below 30%
But there is no explanation on how to to solve the problem. All the suggestions are good only when you have at least 20% battery.
So here I want to share on how I solve my problem to get the battery up to at least 20% so that you can fastboot flash anything, but to run RUU you need to have more than 30%. This works for me and hopefully it will work for others too.
Instead of plug in and plug out the usb cable to and from your phone when connected to PC (which actually not working for me), what I did was :
1) connect the phone to PC, your phone will boot into bootloader with red light flashing on and off or all the way red or no light at all.
2) use the vol button to scroll to power down and press power to off.
3) if the phone boot again to bootloader, repeat (2)
4) if the phone not booting, press the power button to on the phone, it will boot to bootloader again. Try the fastboot flash ** (whatever you want to do, either flash unlock.bin to unlock bootloader to flash CWM recovery or relock bootloader and flash stock recovery). If it fails due to low battery, repeat again (2) then (3) and (4). I did this less than ten times to have fastboot flash working.
What I notice is whenever we press power on, it will go to splash screen but unable to pass the bootanimation due to lack of battery, it will go back to bootloader. In the process, the battery get charging but stop when we are in bootloader. So restart again & again (power down in bootloader & power on again) will charge the battery until you have enough juice for fastboot flash.
Note: item (4), I did the fastboot flash ** before power on, it will say "waiting for device", once the phone is on and in fastboot mode, the command will runs. So once the battery reach about 20%, it will runs succesfully.
Click to expand...
Click to collapse
wolfraim said:
Well, i discover it because i brick my phone haha now i share it to you.
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
PD: Sorry for ortography, im from Chile, my native speaking is spanish but i want to share my knowledge with XDA COMMUNITY !
Click to expand...
Click to collapse
If you re-locked the bootloader
Unlock with the same Unlock_code.bin file provided by HTC and follow this link: http://www.htcdev.com/bootloader/unlock-instructions/page-4/
If you have stock recovery
Download a Custom Recovery (e.g http://forum.xda-developers.com/showthread.php?t=1594819)
Then flash it with the command:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img
If you have Custom ROM on or nandroid backup internal SD card
Reboot in recovery (If your still in fastboot, choose "Reboot Bootloader" and then go into recovery)
Restore a Nandroid Backup or flash Custom ROM
Reboot and go into fastboot
Clean cache in fastboot
If you DON'T have custom rom or Nandroid backup on internal SD card
torxx said:
So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)
Download a RUU from here, thanks to Football!
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
After that:
Code:
fastboot flash system system.img
If everything worked, just reboot:
Code:
adb reboot
Click to expand...
Click to collapse
If you want to restore to original HTC ROM or have new HBOOT/Radio, you will have to do the step above and then the following:
Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
Clear fastboot cache
Code:
fastboot clear cache
Boot your phone
Charge you phone completely
Download stock recovery
Flash stock recovery
Code:
fastboot flash recovery endeavoru_recovery_signed.img
Relock bootloader
Code:
fastboot oem lock
Run 1.26 RUU
Useful Links
HTC One X - IRC - This is the best way for you to get answer to you questions and help if you have problems
HTC One X - XDA Q&A
Don't hesitate to contibute to this guide, as this is made to anwser alot of questions and resolve most common problem when flashing custom roms.
We are all here to learn, take from community and give back to community!
thanks man, great thread
+1
Nice u will be helping a lot of people with this....
Any tut for no boot no recovery formatted sdcard ?
Sent from my HTC One X using XDA Premium HD app
I have a problem that I cant find a way to recharge my phone...
neo-kamui said:
I have a problem that I cant find a way to recharge my phone...
Click to expand...
Click to collapse
More information is needed, like which Recovery..
Anyway, good thread!
Help..
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)... OKAY [ 0.562s]
writing 'boot'... INFOFormat partition LNX done
OKAY [ 0.468s]
finished. total time: 1.030s
C:\Android>fastboot flash system system.img
sending 'system' (960424 KB)... FAILED (remote: (00000006))
finished. total time: 0.016s
C:\Android>
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
more info.. Was t-mobile branded but i flashed custom rom, then tried to update (epic fail) i the went back into recovery and was no files on phone sd.
i have tried with locked bootloader and unlocked bootloader with stock recovery and CWM recovery, i think iv tried all..
i`v just found a ruu_endeavor for t_mobile uk 1.26.110.2 i will give that ago when it downloads in about 1hr haha
This is really an excellent guide for everyone! THX from munich
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
Click to expand...
Click to collapse
SAME
Read my part..
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Edit: sry i meant S-on
Raz0rX said:
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Click to expand...
Click to collapse
S-off???
If not, what u need to do is flash stock recovery and lock ur device. Then place it on the charger while its off (Fastboot > Power Off). Let it charge (higher than 30%) and download and run RUU for your device.
S-OFF, really?
BTW, your device is not bricked, if you can enter the bootloader..
Raz0rX said:
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Click to expand...
Click to collapse
No problem lucky guy.
With s-off you can supercid your Phone and flash every RUU.
How do you get s-off?
OH **** ... my brain was shortly off...
I mean S-ON, sry
The problem is .. there is no RUU for 1.28
So i can do nothing, this system and boot.img trick dont work for me
itswick said:
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)... OKAY [ 0.562s]
writing 'boot'... INFOFormat partition LNX done
OKAY [ 0.468s]
finished. total time: 1.030s
C:\Android>fastboot flash system system.img
sending 'system' (960424 KB)... FAILED (remote: (00000006))
finished. total time: 0.016s
C:\Android>
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
more info.. Was t-mobile branded but i flashed custom rom, then tried to update (epic fail) i the went back into recovery and was no files on phone sd.
i have tried with locked bootloader and unlocked bootloader with stock recovery and CWM recovery, i think iv tried all..
i`v just found a ruu_endeavor for t_mobile uk 1.26.110.2 i will give that ago when it downloads in about 1hr haha
Click to expand...
Click to collapse
OMG i did it... My x1 is now up and running,,,
You need to find the right ruu for your device,
mine was t-mobile uk 1.26.110.5
i download RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.26.110.2_Radio_1.1204.90.13_release_251224_signed
and all flashed first time. with stock recovery and relocked bootloader.
I hope this will HELP you with your 1X..
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Raz0rX said:
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Click to expand...
Click to collapse
Im not expert... but i had stock recovery and relocked bootloader and all work for me.
Raz0rX said:
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Click to expand...
Click to collapse
Yes, make sure u put ur device as stock, stock recovery, and locked bootloader.
Also you have flashed the boot_signed.img and the system.img?
I load a new RUU i hope this will work with it
Edit: How do i become a stock recovery ?
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Look at the following thread, may be this can help
http://forum.xda-developers.com/showthread.php?t=2662787
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Just a little more info Gizmoe please
Gizmoe said:
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Click to expand...
Click to collapse
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Dugoutdog said:
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Click to expand...
Click to collapse
Can you send fastboot commands like
Code:
Fastboot devices
And see your device listed?
PS: to above
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Dugoutdog said:
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Click to expand...
Click to collapse
Did you read my other post. Can you confirm if you have fastboot connectivity? RUU mode is a command not a list option.
gizmoe
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Dugoutdog said:
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Click to expand...
Click to collapse
You have connectivity then. It's not going to list it in " my computer" unless its booted into Rom. Just use this thread
http://forum.xda-developers.com/showthread.php?p=46286588
To flash RUU. Don't do relock or s on just flash the stock RUU.
This is where I'm lost again
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Dugoutdog said:
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Click to expand...
Click to collapse
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
my sub-directory
Gizmoe said:
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
Click to expand...
Click to collapse
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Dugoutdog said:
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Click to expand...
Click to collapse
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
now waiting
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Waiting for download to finish and getting ready for work. It will be close to see if I get it done before I have to leave. If not will finish at 3:00am when I get home and get back to you either way.
almost home
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Dugoutdog said:
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Click to expand...
Click to collapse
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Command Error
Gizmoe said:
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Click to expand...
Click to collapse
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Dugoutdog said:
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Click to expand...
Click to collapse
First type fastboot devices and make sure its connected. Phone needs to be in fast boot mode. Screen should read fastboot usb in red letters. Then type exactly
Fastboot oem rebootRUU
Then
Fastboot flash zip RUU.zip
RUU.zip needs to be in the same directory cmd is reading.
Something is happening . . . . . "sending zip"
resent as failed like you said.
failed as you stated . . . resent. It also said failed resend immediately. something is gyrating.
OK. at bottom of command prompt it says "Successful OKAY 249.248s" Finished total time 312.192 sec.
My phone has HTC in white small letters and a solid green bar below it.
Before I screw anything from this point, what do I do now? Just press the power button?
Hi guys,
So i run into this problem this morning that my phone wont charge at all. Did a reboot and got stuck there somehow.
Some time ago i flashed TWRP recovery and Unlock the bootloader. Everything went ok, but had the red text under HTC logo every time i was booting up.
Now i can access the bootloader by pressing VolUp + VolDn + Power buttons but that's it.
If i try to Boot into Download Mode to use fastboot (as far as i know this way it can be used) it goes back to the boot-loop. Same happens with Boot to Recovery. Also ADB and Fastboot won't show it at all.
Even when i select Power Down it goes into boot-loop.
So far i've tried on a Linux machine without any luck. I'll try on a Windows but i suspect the same result.
Linux can't see it at all on the USB interface (only for a really short period of time when is looping, like half a second. not enough to adb or fastboot)
It got bricked? Just like that? Any way to flash anything on it? Like a recovery or the stock ROM.
Hope you can help me guys. Thanks
Update:
I've just installed on Windows the HTC 10 Drivers and ADB, Fastboot tools.
The device is shown in Device Manager as "My HTC 10" and its listed in "fastboot devices".
The Recovery is still unreachable and if I try to reflash the recovery i get this error message.
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (53680 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.392s
I have to say that first time i did this it went smooth without errors and i was S-ON the entire time. Do you have any ideas? Please.
I believe you need to use htc_fastboot.exe rather than the stock fastboot.exe. Google is your friend for finding it, then do the exact same command but with htc_fastboot rather than fastboot.
so: htc_fastboot flash recovery twrp....
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
iakelclaudiu said:
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
Click to expand...
Click to collapse
You need to be in download mode
iakelclaudiu said:
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
Click to expand...
Click to collapse
Try fastboot oem reboot-download when in bootloader to see if it'll boot to download using fastboot commands.
Sent from my HTC U11 using XDA Labs
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
iakelclaudiu said:
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
Click to expand...
Click to collapse
Hi, do you finded any solutions?
iakelclaudiu said:
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
Click to expand...
Click to collapse
Try to search for the HTC Decrypt Tool here. You'll find the thread which will help to decrypt the RUU and receive the images needed to flash.
On thebother hand you got to be in download mode to flash them. If you're not able to reach it, I guess it's a case for a professional repair.
Sent from my HTC U11 using XDA Labs
Hi there,
Yesterday phone just turned off and since then there is no way to turn it on. I've managed to download RUU File and ive tried to run it form sd there is a problem :
ibb.co/cnu2DH
ibb.co/cqbcfx
Is there any way to turn s-off from bootload mode? Because there is no way to turn this on so i can turn off it from programmer options
ibb.co/nG3ZSc
I cant post links as a new user so please copy it yourself.
You need to flash recovery from download not bootloader and you need an unlocked bootloader.
Also you can't flash ruu from recovery, you need to put the file named as 0PJAIMG.zip in the root of your fat32 formatted sdcard and boot in download.
If you need more help you need to boot in download and run "fastboot getvar all" then post the result here(remove imei, sn).
lucyr03 said:
You need to flash recovery from download not bootloader and you need an unlocked bootloader.
Also you can't flash ruu from recovery, you need to put the file named as 0PJAIMG.zip in the root of your fat32 formatted sdcard and boot in download.
If you need more help you need to boot in download and run "fastboot getvar all" then post the result here(remove imei, sn).
Click to expand...
Click to collapse
Thanks for your advices
Is there any way to unlock bootloader when i cant turn on phone?
Did all thing as you said. When I try it it just keeps reseting phone with HTC logo. Ive left phone for almost hour and it was still resetting, nothing other happens.
heres screen ibb.co/iK4qOH
Satreb said:
Thanks for your advices
Is there any way to unlock bootloader when i cant turn on phone?
Did all thing as you said. When I try it it just keeps reseting phone with HTC logo. Ive left phone for almost hour and it was still resetting, nothing other happens.
heres screen ibb.co/iK4qOH
Click to expand...
Click to collapse
No, you need to enable oem unlocking in settings to be able to unlock it.
Your only option is to flash it by ruu.
This is the ruu for your phone: https://androidfilehost.com/?fid=457095661767124956
Rename it to 0PJA100.zip and put in root of your fat32 formatted sdcard then boot in download and follow onscreen instructions.
Sent from my OnePlus 2 using XDA Labs
Well did as you said and problem is the same - when I start it from download mode it just keeps rebooting phone with HTC logo.
Looks like this phone is really dead thanks for your support
Satreb said:
Well did as you said and problem is the same - when I start it from download mode it just keeps rebooting phone with HTC logo.
Looks like this phone is really dead thanks for your support
Click to expand...
Click to collapse
The process completed successfully, without any errors? If so, the nand is most probably dead.
Also you can try the fastboot method to flash, maybe you have some luck...
You need htc_fastboot.exe for this
"fastboot oem rebootRUU"
"fastboot flash zip RUU.zip" - do the command again when/if it asks.
"fastboot reboot" - when the process finish.