So... I am gone try and put my question in this post as detailed as I can... And I really hope that someone can help...
I have an HTC Wildfire S (Marvel, bought in Denmark) that had 2.2.1, I wanted to use ICS on it and so I started researching for a good ICS ROM. My phone had the below,
Marvel S HTC Europe
HBoot 1.09.0099
2.26.401.3 Radio 47.23e.35.3038H 7.57.39.10M
I decided to flash the below ROM,
Paranoid Android pa_marvel-1.6a-beta1-24AUG2012-142650
My steps were the following,
1. Went on HTCDEV.com and unlocked the bootloader
2. I downloaded the necessary SDK files on a folder on C drive (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe) I then used the following command to flash a recovery “fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img”, this was a ClockWorkMod official recovery.
3. When I tried to access the recovery it seems that it was ok but I had a black screen with the tactile buttons switched on for about a minute and then it booted... I research in XDA and I found a solution... the following.... http://forum.xda-developers.com/showthread.php?t=1781105 it is a small jave software that enables you PC screen to display your htc screen when it is black to actually see what is happening... this saved me!!!!!! Thanks to “rajanand”....
4. After I managed to see my recovery on my PC screen I flashed Paranoid Android... doing always the norm of Wiping Data, Cache and Dalvik first.
5. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC!!!) I assumed there was something wrong with the ROM.
6. I then flashed CM9 from Alquez... doing always the norm of Wiping Data, Cache and Dalvik first.
7. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC AGAIN!!!)
8. I then decided to put it back to its original state by running the official RUU of the phone by downloading it from here http://forum.xda-developers.com/showthread.php?t=1074445
9. When I run the RUU, but first I relocked the bootloader with the following command in the bootloader “fastboot OEM Lock”, (RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed), the phone got an error 140, meaning that my bootloader was a higher version... and the is not other RUU which is higher than this... so I was a bit stuck and confused as to how this happened.
10. I WAS REALLY NERVOUS...
11. I then read a post from someone, I can’t remember saying that only EQDKP ROMs worked for him.
12. I unlocked the bootloader again using the same key when I unlocked it the first time. Keep it.
13. And I flashed the following, [Drk_mod]EQDKPv4.9_multi_deodexed_mhr.zip, and finally my phone booted in the ROM and it is currently working...
See below a screen shot from the Java program and my cwd... it seems that this ROM things a bit different when flashing things or is this a misunderstanding...
Can anyone explain why NO OTHER ROM is working?
Hello, after applying the 4.1.2 GSM PRIMOU AOKP ROM ( http://forum.xda-developers.com/showthread.php?t=1882990 )my phone was stuck in a boot loop. What happened was I followed this guide:
http://www.theandroidsoul.com/aokp-for-htc-one-v-gsm-installation-guide/
Well It wasn't that exact guide, but it was quite similar. The only difference was that after you install the files, you flash the boot img. What I did wrong first was install the files and since I was in the recent CWM the only way to go back was to reboot. SO what happened was that it got past the HTC screen, but it got stuck in this "INITIALIZING SWAGGER" screen. After about 20 minutes I forcefully shut off the phone (held the power button until the buttons flashed like 10-15 times and shut off)
After this, I redid the upgrade, but I followed the guide I posted above. This time it did not get past the HTC boot up screen. All I see now is that whenever I start it up, it goes to the HTC logo screen and then to the HTC logo screen with the red text and stays in a loop. And when I applying the upgrade I did wipe the data.
Here is what I have tried so far:
- nandroid backup/restore, it does not work. I made the backup before I did anything with the ROM. After doing the restore, I am still stuck in the same HTC logo red text boot loop
- I tried reinstalling the ROM multiple times, no solution.
What I hope will save me:
-I have not done the RUU yet. BUT here is the problem. I have a fairly new plan with rogers (still 2 years to go). The HTC One V is from koodo, but I bought it from someone and it came unlocked. All the RUUs I have seen are for telus or do not apply. I am wondering that if I do the RUU and my phone is locked to koodo/telus, and somehow my nandroid backup works after this, will the phone be unlocked (because I have to use rogers)? Or do I have to pay money to get it done =( ?
-also I can connect another phone with the micro SD HC. So I might be able to put files onto it and then try stuff on the bricked phone.
-my nandroid backup might just have something wrong with it, I'm also guessing that the countless "wipes" I have performed with each attempt to get the ROM installed probably doesn't do anything to the recovery. HOPEFULLY there is another "stock" nandroid backup that may work for me (as I can access the microsd).
Another few things to note:
- I didn't do anything with the "Latest boot.img" - I installed the "boot-TK-USB-CM10-OC-VDD-201210112240.img" but I didn't use it... It might be the reason this didn't work for my GSM phone.
The phone info on HBOOT:
- *** UNLOCKED ***
- PRIMOU PVT SHIP S-ON RL
- HBOOT - 1.18.0000
- RADIO-3831.19.00.120
- eMMC-boot
- Jul 2 2012, 20:51:45
Someone please help. This is causing me much distress. Any ideas are welcome. If anyone can even point me in the right direction with the nandroid backup or RUU (but also keep in mind my dilemma with rogers and unlocking the phone) that would also be great. Thank you in advance.
johnpetrucci said:
Another few things to note:
- I didn't do anything with the "Latest boot.img" - I installed the "boot-TK-USB-CM10-OC-VDD-201210112240.img" but I didn't use it... It might be the reason this didn't work for my GSM phone.
Click to expand...
Click to collapse
What does this mean?
Have you flashed the kernel or not?
You MUST flash the kernel using fastboot
fastboot flash boot boot-TK-USB-CM10-OC-VDD-201210112240.img
maxwen said:
What does this mean?
Have you flashed the kernel or not?
You MUST flash the kernel using fastboot
fastboot flash boot boot-TK-USB-CM10-OC-VDD-201210112240.img
Click to expand...
Click to collapse
WOW. Thank you. I will do this right away. The guide told me to extract a file "boot.img" from the ROM itself... I'm guessing this bricked my phone.
It worked!! Thank you so much!!! The guide didn't specify to download 3 files (one being the boot.img with the really long name) and said the dw just the 2 zip files. You are a life saver!! Also can you explain to me how the overclocking works? As I used the OC boot.img
Go to rom control in the settings A's then click on performance then over clock but do not over clock above 1497 or u may fry ur phone
Sent from my One V using xda app-developers app
Please ask all questions in the Q&A section. Thread moved there.
Hello Guys .... I need proffessional help PLEASE ... I'm a little bit noob in all these things !!
Here's all information I can say if there are more needed I can provide ...
My phone history.
Maybe it can be helpful !!
Am gonna begin to say that i bought a Used DHD and its previous owner had installed a custom ICS 4.0.4 BLACK OUT rom it was rooted and has 4EXT Recovery touch everything was gr8 but i had a problem in all applications that uses mic such as VIBER-SKYPE-KAKAO ... etc so i thought it must be a problem with the rom or something so why not changing it ...
I Downloaded Several Custom Roms such as ...
codefireX_ace-SR2-V4.2.1
FullySamsung-ACE-1.0.1_V4.1.1
Jelly Time_R30_V4.1.2
JellyMIUI_2.12.28_v5
PACman-v19.1-Ace-V4.1.2
Here is what i did
1)Went to recovery mode(4EXT Recovery touch)
2)Choose Wipe Data/Factory Reset
here my phone just restarted and had a factory reset to the Black Out
... i thought there is another way to wipe out the rom so i entered the recovery again
and choose
A) Format system
B) then Format Data
C) then format boot ... and i think i've done something like hell
D) then Factory reset .. after restarting my phone keep going automaticlly into recovery mode
I though its all ok till now so I flashed the first codefireX_ace-SR2-V4.2.1 rom and it was successfully installed .... restarted my phone and it stuck on black screen (Dead) i waited for it about 30 min but its no use.
so i though maybe the rom has corrupted while download but I tried the same operation on all these roms and it still the same problem(Black Screen).
I read about the AAHK Operation and I followed the instructions as it is listed but still not working maybe I'm doing it wrong I dont know really Cuz im new to it.
I downloaded and tried to restore the Official rom using RUU
RUU_Ace_HTC_ARA_1.83.415.4_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168914_signed
RUU_Ace_Sense30_S_hTC_Asia_WWE_3.13.707.4_R_Radio_12.65.60.29_26.14.04.28_M_release_234022_signed
it continue and finishes installing but it give me some error number after few steps
I checked the phone drivers it's all checked correctly(I can't guarantee it).
HTC Sync cant see the device at all.
Phone Informations shown in the Hboot are:
Unlocked
ACE PVT SHIP S-ON RL
Hboot-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
In the Recovery Info:
Current rom: cfx-ace-4.2-20130109
**Current phone situation is: Bootloader + 4EXT Recovery touch can be accessed but if I don't press (Power button + Volume down) it will continue to load the rom and stuck at black screen.
If anyone can work with me on TeamViewer to work it out or anything that helps !!
Pleeez help me ...
Put new rom on sd-card, go to recovery mode (4ext) made a full wipe (data/factory resete, cache, cache+dalvick, dalvick, battery stats) made a full format (format all partitions except sdcrad), back and "Install from sdcard" -> "Choose zip from sdcard" -> choose your rom and waiting -> ok -> reboot and ready
Grady22 said:
Put new rom on sd-card, go to recovery mode (4ext) made a full wipe (data/factory resete, cache, cache+dalvick, dalvick, battery stats) made a full format (format all partitions except sdcrad), back and "Install from sdcard" -> "Choose zip from sdcard" -> choose your rom and waiting -> ok -> reboot and ready
Click to expand...
Click to collapse
It Didn't Work my friend I tried that already .... same problem
TheLord990 said:
Hello Guys .... I need proffessional help PLEASE ... I'm a little bit noob in all these things !!
Here's all information I can say if there are more needed I can provide ...
My phone history.
Maybe it can be helpful !!
Am gonna begin to say that i bought a Used DHD and its previous owner had installed a custom ICS 4.0.4 BLACK OUT rom it was rooted and has 4EXT Recovery touch everything was gr8 but i had a problem in all applications that uses mic such as VIBER-SKYPE-KAKAO ... etc so i thought it must be a problem with the rom or something so why not changing it ...
I Downloaded Several Custom Roms such as ...
codefireX_ace-SR2-V4.2.1
FullySamsung-ACE-1.0.1_V4.1.1
Jelly Time_R30_V4.1.2
JellyMIUI_2.12.28_v5
PACman-v19.1-Ace-V4.1.2
Here is what i did
1)Went to recovery mode(4EXT Recovery touch)
2)Choose Wipe Data/Factory Reset
here my phone just restarted and had a factory reset to the Black Out
... i thought there is another way to wipe out the rom so i entered the recovery again
and choose
A) Format system
B) then Format Data
C) then format boot ... and i think i've done something like hell
D) then Factory reset .. after restarting my phone keep going automaticlly into recovery mode
I though its all ok till now so I flashed the first codefireX_ace-SR2-V4.2.1 rom and it was successfully installed .... restarted my phone and it stuck on black screen (Dead) i waited for it about 30 min but its no use.
so i though maybe the rom has corrupted while download but I tried the same operation on all these roms and it still the same problem(Black Screen).
I read about the AAHK Operation and I followed the instructions as it is listed but still not working maybe I'm doing it wrong I dont know really Cuz im new to it.
I downloaded and tried to restore the Official rom using RUU
RUU_Ace_HTC_ARA_1.83.415.4_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168914_signed
RUU_Ace_Sense30_S_hTC_Asia_WWE_3.13.707.4_R_Radio_12.65.60.29_26.14.04.28_M_release_234022_signed
it continue and finishes installing but it give me some error number after few steps
I checked the phone drivers it's all checked correctly(I can't guarantee it).
HTC Sync cant see the device at all.
Phone Informations shown in the Hboot are:
Unlocked
ACE PVT SHIP S-ON RL
Hboot-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
In the Recovery Info:
Current rom: cfx-ace-4.2-20130109
**Current phone situation is: Bootloader + 4EXT Recovery touch can be accessed but if I don't press (Power button + Volume down) it will continue to load the rom and stuck at black screen.
If anyone can work with me on TeamViewer to work it out or anything that helps !!
Pleeez help me ...
Click to expand...
Click to collapse
Are You Online now? Send id And PASS And i will connect. Do it in a pm
I'd say the main problem is the S-ON that's what's stopping it I believe
TheCorner approves..
That Thanks button ain't gonna push itself!
HTC Desire HD ¦ Samsung GNote 10.1
GuyInTheCorner said:
I'd say the main problem is the S-ON that's what's stopping it I believe
TheCorner approves..
That Thanks button ain't gonna push itself!
HTC Desire HD ¦ Samsung GNote 10.1
Click to expand...
Click to collapse
Thanks for the reply sir
Our friend glevitan helped me yesterday and he managed to make the phone back to life again ... Big thanks to him
I asked him to help me in the AAHK operation ... he did the gold card thing and we were downloading official RUU that matches the phone CID when we got disconnected .. and the one that we choose didnt flash right.
soo can u help me in finding the right RUU to match my phone CID which is HTC_621. ?
CID is used for SIM Lock I believe (correct me in I'm wrong Glevitan), so it won't matter about the CID, mainly just the area. The latest WWE RUU will help ya =}
TheCorner approves..
That Thanks button ain't gonna push itself!
HTC Desire HD ¦ Samsung GNote 10.1
Problem Is Solved
My DHD Phone is now all PIMPED....
BIIIG THANKS to Glevitan who helped me without any complain but with big smile :laugh:
Thnx Alot Glevitan and another thanks to XDA who allowed us to meet with professional people like you ...
Hey, everyone!
So within the past week or two my stock standard HTC One X started playing up, which I'm pretty sure was a result of a recent system update (to 4.2.2, from memory). My 'twilight' app (similar to f.lux but for phones) started randomly turning on and off for no reason, the screen became very rapidly unresponsive unless a great deal of force was applied or the phone was repeatedly locked and unlocked, it began to heat up (even more so than normal), etc, etc. Yesterday the unthinkable happened: it got stuck in a bootloop.
So here's how I wound up where I am right now.
I came to terms with the fact that I was going to lose all of my data (at least Google has automatically backed up my images and videos every few days), and anyone important enough to me that I need their phone number I also have on facebook/google plus or see frequently enough in person that when the issue is resolved I can add their numbers again. So I performed a factory reset hoping that would fix the problem. It didn't. Today, at the behest of a friend of mine, I decided to flash a custom ROM on my phone in an effort to salvage what was increasingly likely looking to be a $600 paperweight. I've never done this before, so I followed the instructions in the following video exactly as shown, and downloaded the latest stable version of Cyanogen mod for the One X. The video can be found by googling, "HTC One X - How To Root (in-depth)". It's the first result.
Everything went... well, not smoothly. But I got there in the end. Eventually the phone rebooted, and the blue (or cyan, I suppose) Cyanogen mod logo came up with the circular loading symbol tracing around it. It stayed this way for some 30 minutes or so. I decided to reboot the phone. Same issue again. I performed a factory reset, cleared the cache, cleared the Dalvik cache, and rebooted again. Still wouldn't pass the booting process. I cleared everything a second time and even reinstalled the update.zip (which for some reason appeared as update.zip.zip in ClockworkMod Recovery v5.8.2.7... I'm wondering if that caused some issue). Still no progress. Eventually, out of frustration, I began playing around with random settings within Clockwork Mod Recovery and tried backtracking a few steps computer-side in terms of the installation process, and somewhere along the way I've really F'd things up.
And here's the current situation.
Now, whenever the phone restarts the white HTC splash comes up, followed very quickly by a black screen which flickers momentarily, and then immediately jumps to ClockworkMod Recovery (v5.8.2.7).
Whereas earlier today both fastboot and adb recognised my device, now only fastboot will. I can't get anything to appear in the adb device list anymore. I'd prefer it if people didn't immediately scream, "DRIVER ISSUE!" considering adb worked for half of the day so it seems relatively unlikely to me that that's the problem.
My computer itself won't recognise that my phone is plugged in (probably because there's no OS anymore by the seems of things). I've tried two USB cables to no avail (the first worked earlier on this afternoon, so that shouldn't be an issue).
Within the 'choose zip from sdcard' section of ClockworkMod Recovery I can choose from (other than all of the files that were already in there):
CWN-SuperSU-v0.87.zip
update.zip.zip (the double file extension really bugs me)
'mount USB storage' within ClockworkMod Recovery gives me an erroy reading, E: Unable to open ums lunfile (No such file or di...) (runs off the screen, although presumably it just says no such file or directory exists).
I can't think of anything else that's relevant or would help troubleshoot this issue. If you need anymore info please just let me know and I'll do my best to supply it (you may have to lead me through the data acquisition process, however). I'm really hoping the phone isn't completely bricked because I don't exactly have the money right now to buy a new phone - I'm a uni student who only works part time and I just bought a car a few weeks ago. Bye bye, savings.
Regards,
Scott.
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Want a working phone for now, follow this :
Download this recovery and flash it :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Husky34 said:
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Click to expand...
Click to collapse
I flashed SOME .img file, but not one called 'boot.img'. Can't remember when, unfortunately. If you find the youtube video I mentioned I followed that exactly.
No recovery unfortunately. I saw no point given that the phone was almost unusable in any form prior to me getting Cyanogen installed (it was constantly and randomly rebooting). Probably a mistake in retrospect.
Version 10.2, by the way.
Mr Hofs said:
Want a working phone for now, follow this :
Download this recovery and flash it :
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Click to expand...
Click to collapse
Can you walk me through it step-by-step. Again, I'm a total noob to this and I DON'T want to stuff this up again. Is the fact that adb (or my PC in general) isn't recognising my phone going to make this difficult? I mean how am I meant to copy anything to the SD card if I can't access it through windows explorer or via adb push?!
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Mr Hofs said:
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Click to expand...
Click to collapse
This seems to work at first - instead of jumping into ClockworkMod Recovery, after flashing the image file you gave me, it jumps into a new recovery mode. But after rebooting and going into recovery mode again it's back to ClockworkMod Recovery (I made sure to clear the cache).
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Mr Hofs said:
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Click to expand...
Click to collapse
Oh. Well it looks different the first time I boot into recovery versus the second time (PhilZ Touch 5 with a distinct purple background the first time, but the second time it goes back to a black background with blue text).
Not really sure how to proceed from here. Battery is dropping fast (9%) despite being plugged in, so I'm worried if I don't fix this ASAP it'll be forever FUBAR.
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
If you use Fastboot flash recovery command the old one is gone.....can't come back like that !
Mr Hofs said:
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
Click to expand...
Click to collapse
Mr Hofs, you sir are a gentlemen and a scholar! I have managed to get back to the initial bootscreen for Cyanogen mod. AND SUCCESS! IT JUST PASSED THAT SCREEN AS I WAS TYPING!
I am indebted to you, you glorious man! Thank you so very much I'll keep you guys posted (for better or worse)!
Hope it will be fine. I will keep an eye out here
Mr Hofs said:
Hope it will be fine. I will keep an eye out here
Click to expand...
Click to collapse
So I tried updating the camera (?) as a suggested update after getting back into my phone, and it's already stuffed up again. It rebooted and said that root access has possibly been lost. What's happening now?
Doesn't appear to be a big issue for now, actually. Reset, not caused any problems since then! Managed to get google apps working, and downloaded a bunch of the apps I need All's well!
Thanks one again!
Alright ! Hope i don't see you here again
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
darule_2011 said:
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
Click to expand...
Click to collapse
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Mr Hofs said:
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Radio-0-19as.32.09.11_2
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Mr Hofs said:
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Click to expand...
Click to collapse
uh oh, that doesn't sound good for me...I don't have the XL version, just the one X. Will that matter? Did I flash this baby using files for the XL when I should have used something else?
No you don't read well. You have the HTC one XL (EVITA) and this forum is for the ENDEAVORU HTC one X international version.
We here have the quad core and you there have the dual core phone !
I decided to root my phone. I have an htc one M8 with android version 4.4.2. I followed a detailed guide step by step found on htconeroot site (sorry cant post link im a new user but its the same rooting process i found everywhere). Everything went perfect until the final stage ''step 25: choose “RECOVERY” and hit the Power button'' well i did that and instead get access to TWRP Recovery, the HBOOT RECOVERY option just show me for about 1-2 seconds the screen with HTC logo and letters ''entering recovery ...'' but almost immediately jumps back to fastboot menu ! never get into TWRP so i can finish rooting process. My phone, if i select reboot, works fine (unrooted).
Details of the device:
MEM_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1102.19.1017
OpenDSP-v28.2.2-00546.0311
OS-2.19.401.2
Emmc-BOOT 1024MB
Aug 13 2015,
Also on the top displays ''TAMPERED'' ''UNLOCKED''
What i tried
Tried several TWRP recovery images, no luck, (actually i tried almost every TWRP file i found out there)
Tried fastboot erase cache, no luck
(no verizon or sprint im on international carrier)
Been stuck here for many hours, any ideas ?
Thank you
(sorry for my bad english)
First....I suggest updating your firmware to the latest version.
Second, When you flash TWRP which version are you trying to flash, and what command are you using?
firmware updated, still no luck
command i used: fastboot flash recovery
versions i tried: twrp-2.7.0.1-m8 till 2.8.6.0
Still got this annoying bootloop
Use correct twrp version on correct device variant.
You can't use a M8 twrp on a HTC ONE MINI 2 device
MEM_UL = HTC ONE MINI 2
M8_UL = HTC ONE M8
im a blind idiot ! for many hours flashed wrong device twrp versions ! stupid stupid stupid
so i tried all the m4 twrp versions i found, i used 11 versions from twrp-2.6.0.0-m4 till twrp-2.8.7.0-m4
and the problem still exists, no recovery mode-jump back to fastboot menu.
But the last moment i found on a forum (can't remember which one) that: twrp-2.7.1.0-20140802-memul.img
and finally yes ... i was able to enter the recovery and finish rooting process easily !
If anyone encounters similar problem just use the above twrp, well, it worked for me !
Thank you Kyuubi10 and ckpv5 for your help !