Related
this is the first time i am posting, i do hope i can get some help.
my phone is now s-off and i can boot into the Hboot during boot up, but i can't boot into my phone. It just stuck at the HTC logo screen without booting into my phone.
its my first time playing with android and i would appreciate if anyone could help me out here. I've read i think almost all the relevant problems and solution out there to help but i am really confused by all of them. what i need is a simple and clear way of doing it. step by step would really be perfect.
thank you and please be patient with me.. i am a noob..
cheers
Did you install a custom recovery like Clockworkmod?
Sent from my HTC Vision using XDA App
hi Sleef,
i don't think i have. could you guide me in installing one? thanks
I assume it would involve using adb to push it to your phone and beyond that, I'd probably have to do as much reading as you to be up to speed on how to do that.
Check the stickies in the development section. I'm willing to bet that somewhere in there will be the files you need and some instructions on how to make it all happen.
It'll be worth your while to brush up on using adb.
Sent from my HTC Vision using XDA App
thanks sleef,
right now i am trying to use the sdb to push the clockworkmod. but the problem is the adb does not recognize my phone.
i have the same problem on my desire z,
i need help
If you have adb setup correctly on your PC, then you should be able to boot the phone into fastboot mode (hold down the trackpad button and press Power, with it turned off), and then when you plug it into the PC, you can do "fastboot devices" and get it to see your phone.
If you have got fastboot working, and you have the engineering hboot installed, then you can do "fastboot flash recovery recovery.img" to flasha new recovery image. You can get the Clockwork image for Vision from http://koush.tandtgaming.com/recoveries/ (2.5.1.3 is the latest).
steviewevie said:
If you have adb setup correctly on your PC, then you should be able to boot the phone into fastboot mode (hold down the trackpad button and press Power, with it turned off), and then when you plug it into the PC, you can do "fastboot devices" and get it to see your phone.
If you have got fastboot working, and you have the engineering hboot installed, then you can do "fastboot flash recovery recovery.img" to flasha new recovery image. You can get the Clockwork image for Vision from http://koush.tandtgaming.com/recoveries/ (2.5.1.3 is the latest).
Click to expand...
Click to collapse
Thanks for stepping in. I wasn't sure how much more I could say without making the problem worse.
steviewevie said:
If you have adb setup correctly on your PC, then you should be able to boot the phone into fastboot mode (hold down the trackpad button and press Power, with it turned off), and then when you plug it into the PC, you can do "fastboot devices" and get it to see your phone.
If you have got fastboot working, and you have the engineering hboot installed, then you can do "fastboot flash recovery recovery.img" to flasha new recovery image. You can get the Clockwork image for Vision from .
Click to expand...
Click to collapse
i guess my adb is working on the PC. For the fastboot mode, can i enter it by holding the power button and volume down, then enter fastboot mode? is that the same?
my main problem is that adb does not detect the phone currently, this prevents me from going further to save my phone.
keitaro1986 said:
i guess my adb is working on the PC. For the fastboot mode, can i enter it by holding the power button and volume down, then enter fastboot mode? is that the same?
my main problem is that adb does not detect the phone currently, this prevents me from going further to save my phone.
Click to expand...
Click to collapse
Yes, that's the other way of getting into fastboot. It should say "fastboot usb" on the phone screen if it's working properly.
I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..
eddi2004 said:
I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..
Click to expand...
Click to collapse
Try this:
1. power down
2. remove battery
3. press and hold power button for 10 sec.
4. reinstall battery
5. press and hold the volume down button
6. press the power button to turn the phone on but DO NOT release the volume button until you can see the boot screen.
when you are in the boot screen one of the options in the list should say recovery. use the volume button to navigate down to that option and press the power button to select it. your phone should then boot into recovery and you will get the recovery screen and choices.
thanks
i did it but when i get into recovery i see the phone with the sing and then i reboot get stock in htc evo 4g logo if u have any idea how to get into the phone to flash any rom would b perfect tnx
Sounds like it could be a USB brick. This has happened to me before. I remember when that happened to me and couldn't get into recovery. For some reason when I plugged in the micro usb to the phone it would let me boot into recovery. Give that a shot and try searching usb brick. Also my sd card could not be recognized once I booted into recovery.
How did you try to downgrade?
Sent from my PC36100 using xda premium
ok well i flash 2 programs 1 flash_image 2 mtd-eng then run the pc36img but nothing happen it says cant roll back hboot n i reboot the phone n i went to the bootloader n it was locked n i try to enter to the recovery n show me the phone w/ the sing...
any idea where can i get an usb brick??
I'm not familiar with a USB brick, but I believe that your computer can still read your phone through USB. I see that you were trying to S-OFF the phone. Looks like something went wrong when you flashed the misc partition, which locked your bootloader once again.
You should try running an RUU file from your computer with your phone connected which can be found here.
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
But first, you will need to install the Fastboot drivers to your computer which can be found here
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
You need to run the RUU from your phone's bootloader from FASTBOOT USB (click on Fastboot then run the RUU from your computer).
If that works, that should at least get your phone back going again (unrooted of course).
i did but w/ the ruu doesnt work too appears error 155 unknow problem n stops i dont know what else to do
Just checking, did you run the RUU in FASTBOOT USB which should have been highlighted in red from your bootloader after clicking FASTBOOT? Also, with your phone connected to your computer while in FASTBOOT USB, check your computer's device manager from the control panel and see do you see anything under Android USB devices.
And too, which PC36IMG file did you try to run?
Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng
{ParanoiA} said:
Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng
Click to expand...
Click to collapse
Yea, I was afraid that the wrong PC36IMG file was indeed used. Generally on the newer phones, any downgrade of the Hboot below 2.02 is a guaranteed brick. That's why Captain Throwback only recommends PC36IMG files down to Hboot 2.10 (the 2.02 ones don't work with S-ON phones). On the older hardware however, the Hboot can be downgraded to anything, including 0.76 from 2.18. I've done it on mines. You just have to know which hardware version and partition erasesize your phone has.
the one that i get from evohacks pc36img i think i need one way to flash a rom
the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick
eddi2004 said:
the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick
Click to expand...
Click to collapse
The best advice that I can give you is to reboot the phone into FASTBOOT USB (connect it to your computer, then go to your bootloader and click on FASTBOOT), then go back to the HTCdev site, start over and try to re-unlock your bootloader. If you can do that, then I may have a workaround for you If not, there might not be much else that you can do.
ok i did everything that u tell me n now i rename the zip (ss_stock_4.67.651) in PC36IMG n then reflash recovery-RA-supersonic-v2.3 now i can get into the recovery menu n i flash the rename (ss_stock_4.67.651) PC36IMG n i have a rom from sprint but now i still cant use adb command so what else shuld i do to recovery to normal n there r many issues that cant load like mail that is forced to sptop unexpected n thank u for all ur help!!
in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot
eddi2004 said:
in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot
Click to expand...
Click to collapse
Oh no. I don't know which tutorial you got those instructions from.
I'm also lost with your description of what happened. I hope you unlocked your bootloader, and can now boot into the operating system. If so, you were not suppose to rename the ss_stock_4.67 file to PC36IMG. You were suppose to flash that through RECOVERY as is. If I were you, I would go back to RECOVERY, and wipe All Factory/Reset (or whatever it says) and Dalvik-cache, then reflash the ss_stock file or another ROM.
Second, the adb commands only work from the operating system, not FASTBOOT. You need to be inside the operating system with your phone connected to your computer and USB Debugging enabled under Settings/Applications.
ok here i am
i change the name cos the bootloader let me flash the recovery amon ra 2.3 then i can see the recovery menu n i flash the rom named pc36img n give me the sprint w/ errors now i download another rom that i flash n now my computer can read the sdcard but im still locked n i dont know if im still rooted so the what i think is i have a usb brick so i need to unbrick my usb to use the adb command so i apreciate ur help w/ this thanks all of u for ur help
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.
Hi,
I searched a lot withouth luck.
After flashing a kernel my amoled Desire is stuck on the HTC logo.
It is s-off with latest hboot.
The problem is that the volume keys are broken..
So I cannot use power+volume down to enter fastboot or hboot..
From the pc with adb devices I cannot see the device.
Is there a way to recover my poor phone?
Or to enter hboot without
thank you very much for your attention
Use back+power to enter fastboot and select "bootloader"
Thank you very much!
It was so simple, but I didn't know this method, sorry.
After some little problems I manage to restore it. :victory:
I write down the difficulties I found, so if someone has the same issues, he could use that.
After entering fastboot adb could not see the device again.
Fastboot commander 1.51 could, but was unable to write a new rom from a zip.
So I write on the phone a nandroid backup (with fastboot commander).
It booted but was stuck on "Optimizing Applications".
From there adb coul see it.
So I rebooted into recovery with adb, flashed the same nandroid of before from the SD and it booted successfully.
Thank you again!
And thanks to all that keep this device alive and help who need it
HTC desire doesnt boot to OS
RoKKo_TM said:
Hi,
I searched a lot withouth luck.
After flashing a kernel my amoled Desire is stuck on the HTC logo.
It is s-off with latest hboot.
The problem is that the volume keys are broken..
So I cannot use power+volume down to enter fastboot or hboot..
From the pc with adb devices I cannot see the device.
Is there a way to recover my poor phone?
Or to enter hboot without
thank you very much for your attention
Click to expand...
Click to collapse
I too searched for the thread of my problem but couldn't find it.
I was given this Desire and I switched it on, it booted directly to hboot. I thought may be I pressed the volume key unknowingly. But then I tried to reboot it via hboot, I found out that volume keys do not work. So I removed the battery and tried to switch it on again, and it did the same, booted to hboot directly.
It is s-off and does not have any recovery app installed.
What do i do. I really need some help.
P.S. Sorry for my english, and this is my first post/comment in here. I thought this thread somehow matches my problem.
Thanks
Alternative HBoot entry
dreamer8ful said:
I too searched for the thread of my problem but couldn't find it.
I was given this Desire and I switched it on, it booted directly to hboot. I thought may be I pressed the volume key unknowingly. But then I tried to reboot it via hboot, I found out that volume keys do not work. So I removed the battery and tried to switch it on again, and it did the same, booted to hboot directly.
It is s-off and does not have any recovery app installed.
What do i do. I really need some help.
P.S. Sorry for my english, and this is my first post/comment in here. I thought this thread somehow matches my problem.
Thanks
Click to expand...
Click to collapse
Heh guys,
You can enter hboot by holding down the back button then the power button together.
See abaaaabbbb63's reply above
Ps. Thank me if this helps.
But he can enter hboot, so I think the question was different, or I'm wrong?
When you are stuck on hboot, could you see the device with the command "adb devices"?
Have you installed the correct drivers on the pc?
If you haven't got a recovery I think it is not a problem, you can at least flash the original gingerbread ruu.
Have you tried fastboot commander?
Me noob
RoKKo_TM said:
But he can enter hboot, so I think the question was different, or I'm wrong?
When you are stuck on hboot, could you see the device with the command "adb devices"?
Have you installed the correct drivers on the pc?
If you haven't got a recovery I think it is not a problem, you can at least flash the original gingerbread ruu.
Have you tried fastboot commander?
Click to expand...
Click to collapse
Umm... I'm a noob, the lowest one... Honestly I haven't done anything to this device coz I have no idea what to do. I tried googling hoping I would find some helpful infos to start with, but I didn't.
So can you please explain how do I get/do the above things??
The phone has been modified in any way by the previous owner?
First you need to connect the phone with the pc.
From hboot, if you see "fastboot" higlighted, press the power button one time to go into fastboot mode.
I cannot find my exact same drivers, but this should be just fine:
Code:
http://dl.xda-developers.com/attachdl/fe66812c2a4bd7da49a109b357afe420/518cba12/5/6/0/4/1/4/adb_driver_htc.zip
Download also Fastboot:
Code:
http://d-h.st/OFs
Plug the phone in the pc, when it asks for drivers, give it manually the folder that is inside the adb_driver_htc.zip.
It should see now the device from the device manager.
Extract the Fastboot.zip folder in a folder you want. (Like C:\).
With the phone inserted in the pc, open cmd (using the search function over start) and navigate to the directory where you've extracted fastboot.
After type "adb devices" without quotes, and see if it lists a device .
Sorry for my bad guide, hope we could figure it out .
You must understand how to use adb and fastboot, that are the tools we use to interface ourselves with the phone, so if needed the internet is full of little and friendly guides
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