Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
When you flash a new kernel, all you have to do is place modules zip in phone storage, put phone in bootloader, connect to computer, flash boot.img, go into recovery and flash modules. If you don't flash boot.img, the phone won't boot. Try going into bootloader by pressing volume down and power at the same time and holding it, flash viper boot.img via fastboot kit, full wipe and reflash rom. I've messed up a few times but this has always worked for me.
Beyazid said:
Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
Click to expand...
Click to collapse
there are infinite posts about how to fix this and tutorials too if you use the search button, anyways
1- why using faux 7m when there is already 10m ?
2- hold power+vol dwn
3- go to recovery (hboot not fastboot)
4- go to mounts and storage, mount storage usb
5- copy to your sd all the files excluding the boot.img from faux
6- flash rom then modules then type in cmd "adb reboot-bootloader" (without quotes),
7- choose fastboot in bootloader then flash boot.img and erase cache
@VCek: I flashed this before the Versions 10 and 11 came out
Thanks for the infos. I´ll use them the next time. But now I can´t reach the bootloader anymore because I locked the phone with "fastboot oem lock" and because of that I can´t do anything but go to the fastboot mode. The recovery is locked or in other words: I can´t use the CWM Recovery anymore.
If I click the recovery mode this happens: vvvvvv(dot)vidup(dot)de/v/l1vVH/ (make a dot instead of the word "dot" and change the V´s to W´s, I´m not allowed to post outside links right now)
The next step should be the unlocking I guess. Right? But how can I do that?
Edit: I was able to unlock the phone again so it should be easier from now on but your steps didn´t work for me. I reflashed the Viper X Rom and reflahed the Kernel without the boot.img in it. But I didn´t get the point which boot.img I should flash. Both of them or just the Rom boot.img?
Edit2: After a long day I was able to solve the Problem with the right RUU. After all it was easier than I thought and I should have done that at the beginning
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?
First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!
OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!
OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?
OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.
OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?
Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!
P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin
Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.
Check out the CDMA development thread
Whenever you get your phone back.....
Good luck
I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.
Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download
Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"
Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking
Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.
Hi All,
After 3 hours of doing same thing and having no results I give up and I'm starting this thread to see if you had similar issue and can direct me to have recovery working and therefore root this phone.
What I did :
1. found this website on rooting htc one m8 (its european version)
*http://htconeroot.com/htc-one-root/how-to-root-htc-one-m8/
-first thing I noticed there is no Fast boot option in Settings->Power , did some reading and its probably becasuse android ver is lollipop , fair enought, skipped that and went to Unlock Bootloade
2. Unlock Bootloade went OK, now phone shows:
UNLOCKED
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
OS-1.03.401.11
3. as per instructions on downloading recovery, downloaded both
philz_touch_6.26.6-m8
&
openrecovery-twrp-2.8.5.0-m8
downloaded also SuperSU...
4. Flash recovery time,
- fastboot flash recovery philz_... but I think I did not clear casche after the install, rebooted phone and then noticed original thread of philz saying that the project is discontinued so,
5. flashed openrecovery
- fastboot flash recovery openrecovery....
- cleared cache (this time)
6. wanted to go to new recovery to install SuperSU but every time I choose RECOVERY it gives me black screen and blinking red dot at top of the device, nothing happening at all.
Found previous users with similar issue (black screen , cant go to recovery) and the advise was to keep clearing casche , installing new recovery and eventualy it should work, but not in this case,
Spend last 3 hours looping all this and the result is still the same
- tried with and without SD-Card , after 2 min of phone being turned off but still same results
7. tried factory reset, both options,
the one from Settings after clicking OK does nothing, the second from holding both vol-down & power buttons gives black screen,
I will appreciate if anyone who dealt with similar issue can advise on this for me
Thanks for reading all this !
and for your help in advance
Looks like you may have the M8S...not M8. I believe there are a few threads on XDA regarding modding the M8S if you care to search..
new-noob said:
Hi All,
After 3 hours of doing same thing and having no results I give up and I'm starting this thread to see if you had similar issue and can direct me to have recovery working and therefore root this phone.
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
OS-1.03.401.11
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
thats it!
its m8s I havent noticed that before, stupid !
thank you both ! installing recovery for m8s fixed the problem,
Hello all members !
First - I'm sorry for my English use.
I have a problem with my HTC Desire. I didn't found same situation - or I'm just blind.
I tried to root this device - did it succesfully with Revolutionary method - just recovery install cracked. I've found TWRP 6.0.2 and put it in by fastboot. Later with TWRP installed SuperSU.
Started to put custom ROM - fail. By fastboot I've installed stock HBoot - still ROM failed (status 7). Later I tried to install RUU - after 90+% progress I had fail. Phone stuck on black HTC logo with triangles - but I was able to get into bootloader, TWRP and fastboot . Later I was just reading repair tips from another forums and I've started system by fastboot - stuck on white HTC logo. After all I did... fastboot oem lock.
Now I cant flash HBOOT, zip etc. Just recovery. PB99IMG.zip didnt work. OS are gone.
Now I have question (if you survived this ugly-lang story) - does someone have any ideas how to repair this phone? Do an S-OFF? Say which RUU can rescue me?
Thanks for reading