So after rooting my girlfriends HTC One V and testing a few roms, we seem to keep running into problems. At the minute i have put Sphongle on it, think its the latest version, but its lagging, having problems displaying the notification bar, random crashes on a daily basis and so on.
So i want to go back to the original stock software, it was on 02 UK and i looked up the CID as some guides said and somehow got pointed toward an RUU for Europe and was told its the correct RUU. So i did the guide, found the ROM file in the temp folders, attempted to run it from the PC via the installer and it worked fine until it rebooted the phone, for some reason the wizard couldnt find the phone after the reboot. So i then followed another guide and renamed the ROM file to the specific phone file needed, PK76IMG i believe, and did it through the HBOOT part. At first the rom wouldnt work, it would read the file and the activity bar would show it was loading something, but after a short while it would say wrong zip file and sit in hboot. So i found another version of the RUU Rom and tried that, it read the file in hboot, then said checking file, then parsing and then nothing, it sat back in hboot and didnt update.
So im kinda at a loss now, i need to get this back on a stable original rom but cannot seem to find a way without running into problems!
Any ideas????
Cheers
I am running SPHONGLE on mine as of now.
Try following these instructions carefully and see if they help, I hope I may be of assistance as I ran into problems myself whilst flashing last night.
First of all, boot into fastboot by turning the phone off and holding the VOLUME DOWN button when it is turning on, once into fastboot attach your HTC to laptop/PC and it should say fastboot usb on your HTC screen. (Make sure all your adb drivers and SDK platform are installed on your PC...)
Secondly, take THIS kernel (Hellboy's latest kernel) and flash it through fastboot flash boot cmd.
Once that is done, select bootloader from your HTC and boot into recovery (hoping you have custom CWM/TWRP recovery...? if not install before you do this...) perform a full wipe of everything /cache /system .. dalvik cache etc. then find the ZIP file for SHPONGLE and flash the ROM, then flash the GApps file included in the SHPONGLE OP.
Word of warning DO NOT use the hellboy kernel included in the SHPONGLE OP use the one I have linked you too.
After you've done that select reboot and let the ROM boot and settle for 5 or so minutes. Hopefully everything should be okay... let me know. :victory:
Related
Hi, I need some help with my Desire HD.
I've been running Android Revolution for nearly a year now and had 6.1.5 running well until about a fortnight ago.
Initially, the volume keys started malfunctioning and the volume down would get stuck. Occassionally, the phone would freeze and I'd have to take the battery out and reset, and it would seem fine except the date was set to 11:00AM on January 1, 1980. Same date and time every time. Strange!
In the past week some processes have been failing, some downloaded apps and some google service framework. The phone then rebooted itself into bootloader and when i tried to reboot it would just loop back in to bootloader. after 10 or so reboots it would eventually boot back up properly.
Yesterday I ran SuperWipe and reinstalled Revolution 6.1.5 and things seemed to be running smoother. Then my phone froze again and is now stuck in the bootloader and nothing will work. The volume up key works nearly always and the volume down key has occasionally worked with alot of force, but i think this problem may be seperate to the software issues.
I once selected Reboot Bootloader and rebooted to a weird fuzzy static screen.
I've recorded a video of what is happening and posted it here: h tt p:// youtu.be/Sgp8pYin6yY
I've also posted a picture of the green text that flashes up in bootloader, I'm not allowed to post links so please go to the link in the comments on the youtube video.
From looking at other forum topics I think loading an RUU could be a solution, but I'm not sure how to do that.
Any help would be greatly appreciated!
Cheers,
Bickers
to flash an ruu or its pd98 equivilent is simple.
For an RUU what you do is in hboot select fastboot. then Plug in your phone and run the RUU.exe from your pc.
OR
If you prefer the PD98 method. what you do is place the pd98 file in the root of your sd card(not in a folder). boot into hboot. and hit up to accept the installation
its your choice on which RUU to flash but personally i would choose either the new sense 3.0 3.12 or the sense 2.1 2.50.
One thing to note is the issue with your volume down. If you still have warranty on it, i would get it replaced
Making RUU into .exe or PD98IMG.zip
Ok I think it's best for me to reinstall the original Vodafone Rom.
The "The Complete Guide 2 Return Rooted Phone Back 2 Stock for Vodafone Australia Warranty" guide relies on using Clockworkmod - which I can't get into because my phone won't boot past bootloader.
I have downloaded the 1.32 ROM from the above thread and it's a zip file but I need to know how to get it into either RUU.exe to run through my computer or PD98IMG.zip to run through bootloader.
Do I simply rename it PD98IMG.zip?
I've been searching and reading lot on RUUs and unrooting etc. but can't figure out how to do it.
I also have a goldcard that I created last time I flashed a custom ROM but I can't find the guide that I followed and I'm not sure if I need a goldcard.
Please take the time to help me and provide step by step instructions of how to take the 1.32 Vodafone AU ROM back up and install it onto my phone through bootloader.
Thanks a million and one!
No you can't rename that zip and flash in hboot. Unfortunately you need access to cwr to do that method.
I think first we should try and get you back up and running on any rom before you decide to go back to stock. Unfortunately for you their isn't a ruu for vodafone au to make it and easier process.
So for now try and reflash cwr and or a different ruu, to atleast get you in a working state. Give me a min to find a link to a guide to see if that will help you
Edit- try this
http://forum.xda-developers.com/showthread.php?t=1396253
Use the mirror links in the second post. If you have no way to transfer the files use the ruu method at the end. Links to the wwe and hopefully faster links are found in my last post in the thread
Partition Update Fail!
Thanks for your help.
Unfortunately when I try to flash the PD98 of the recovery image I get Fail-PU in red next to BOOTLOADER and RECOVERY.
and "Partition Update Fail!" in black underneath.
I also tried another recovery pd98 and got the same thing. About to try the RUU method from the PC, but if that doesn't work i'm not sure what to do
So i recently purchased an unlocked HTC one x (white), and tempted by the improvements from mike1986's HD revolution ROM I decided to give it a try.
my phone had firmware 1.19 installed, i wasn't able to update the firmware due to the cid none error. I read a few posts in his thread saying to just install the rom anyway, so I did. the rom installed without error, i also performed the super wipe as instructed.
the phone booted up with the new rom, but about 3 mins after the OS loads (im able to choose my language, and i can see all the new languages introduced by mike1986's rom) it will always tell me that i have 0 battery charge remaining and automatically shut down(, regardless of how much battery is actually left. I had at least 80% charged. so basically im stuck in this boot loop.
Im not able to reload my original rom since my nandroid back up mysterious got wiped. what can i do to get my phone back to stock rom?
PS. ive basically spent the entire day reading multiple posts trying to find how i can get this fixed. Fastboot seems to be the only option but i just don't see any clear cut answers on how to do that exactly. i can't place any zip files in my SD ext, because the OS wont stay open long enough to transfer it through PC.
easy :-D i had this problem like 5 times , you need to back to stock again
snowwhite007 said:
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Courtesy of DaDoctor
Mod or Die
Mod or Die
Click to expand...
Click to collapse
cool thx!
yah i read something like this, so i started to download a RUU 1.26 from TW unfortunately its taking forever. My original firmware was 1.19 does it matter that im upgrading to 1.26 also what commands do i need to use to flash this on to my phone? basically i need help with step 3.
edit: saifullah made me realize that there were others with the same problem, so i searched the forums and found the solution. just follow the 3 steps above, and make sure you have the exact same RUU number. mine being 1.19.707.1 i need to get an RUU with the same 3 middle digits ex. x.xx.707.x this is like an area code if that helps anyone else. there are a ton of different ruu and you need the exact one.
I had the same problem, extract the boot.img from the CWM rom that you tried to flash in the first place and flash it via fastboot with the command "fastboot flash boot boot.img"
It took me ages to find a fix, hopefully this can help!
It boot it Up! Thanks
Using Android Revolution 1.2.3
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
Make sure you have USB Cable and a Memory card before doing this. ** WARNING ** Flash At Your Own Risk.
This will take 1 hour or maybe more, just make sure you follow the steps carefully and do it carefully. This thread is for people who have no access to their rom and have only access to bootloader.
If you tried to return to stock rom via Advanced Ace Hack Kit and you tried to flash the stockrom back on and it just crashed during the process and you just pulled it out the usb cable out of the phone, So you pull the battery out the phone and restart it. All you see is the htc screen which it is just stuck on. Well I have the solution how to fix this. You might think it is bricked and have buy a new phone well you dont! All the problem is that the Advanced Ace Hack kit the radio RUU they provided you with is either a old version or a corrupted one so the phone cant boot up properly. This thread I am going to tell you how to flash the RUU and put a custom rom on which is ten times better than the android 2.3.5.
You have to concentrate while doing this or you will end up with a dead phone.
So step one - Go to google search and copy and paste RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed. go to the second link which says hotfile and download it.
Download the RUU_Signed File Via Hotfile, This will take sometime if you have a slow internet connection.
Step Two - It will say Welcome to the ROM Update Utility for your Android Phone also it will have a image on the left of the Desire HD. So click I Understand and click next so take the battery out of your phone and hold the volume down button and the power button, you will see a white screen with other selections so click bootloader to click it you have to click the power button to select it. So when you click bootloader it will go red and say FASTBOOT, So make sure the usb is in the computer/laptop during this process it will only go into fastboot if you have the usb connected to the computer first.
Step Three - Agree to all of the conditions and click next. Note: This process Will take sometime.
Step four- It will say Congratulations! your phone has been successfully been flashed! Now your phone is fully working and rooted so now your phone will reboot, If it doesnt power it on your self!
So it will boot up in android 2.3.5 because that was the rom that you were trying to flash via AAHK.
Step five - Open Advanced Ace Hack kit and make sure USB Debugging Mode is on.
Step six - There will be a option saying Hack Ace, This will root and install clockwork mod on your device, So type 1 and hit enter.
Note: this process will take sometime. Grab a cup of juice and crisps.
Step seven - The phone will reboot and will still be on android 2.3.5 so now you have superuser access and clockwork mod.
Step eight - Power off the phone and hold the volume down button and the power button, You will be in bootloader so now go down using the volume buttons and select recovery, to select this option you will have to click the power button to enter recovery mode.
Now your phone will be in recovery mode and will say Ace hack kit across the recovery screen, So now select wipe data/factory reset when it has wiped the phone select wipe cache partition, after that has wiped go to advanced option and select wipe dalvik cache.
Step nine - Your phone has nothing on it exept from bootloader and recovery! So now connect your mobile device to the computer and click mounts and storage, make sure your USB is connected. To complete this process make sure you have a 8GB Or 4GB Memory card in. So click mount USB storage, it will mount your memory card so you can access it through the computer to drag and drop files to flash on your mobile. You can download a Jellytime ROM on the XDA Forums So just choose which one you want and download it and drag and drop to the memory card while your phone is mounted to the computer via USB, Make sure you download a Google apps Package and flash it with it if it doesnt have the Google Playstore on the Rom. To Flash any zip files follow this - click unmount, go back to the main recovery options using the volume buttons and power button to select, go to install zip from sd card - select the zip file you want to flash then flash the Google apps Package after you flashed the ROM you want to have on your phone.
Last and final step! - Click reboot system now, your HTC DESIRE HD should reboot to the ROM you have flashed.
Congratulations! You have flashed and rooted your mobile device after being stuck in bootloader/fastboot mode.
If any problems just mail me or mail me via XDA Developers site.
I will help as much as I can to fix any problems.
Thank you for reading this thread and hope it helps.
AADAM H. AKHTAR
Wait, I am beyond confused. If you are going back to stock with AAHK you are already S-OFF. You can just flash a recovery (if you don't already have one) and use that to flash a custom ROM if you want, or use AAHK to unroot and return to stock.
And...what does a radio have to do with anything?
And...why would you disconnect your phone while running AAHK?
And...AAHK doesn't provide corrupted RUUs. Maybe your download is corrupted?
Again, confused...
bananagranola said:
Wait, I am beyond confused. If you are going back to stock with AAHK you are already S-OFF. You can just flash a recovery (if you don't already have one) and use that to flash a custom ROM if you want, or use AAHK to unroot and return to stock.
And...what does a radio have to do with anything?
And...why would you disconnect your phone while running AAHK?
And...AAHK doesn't provide corrupted RUUs. Maybe your download is corrupted?
Again, confused...
Click to expand...
Click to collapse
You cant flash clockwork mod on if you dont have USB debugging mode on, when the phone is stuck on the htc logo the only way is to flash a radio that works with the phone through bootloader/fastboot.
also when you flash a radio it wipes clockwork mod off it so you cant flash a recovery.
The radio file either was corrupted or either the wrong one for the phone because most of the time when you flash it is going to go perfectly but there is a chance where it will crash the process.
Again.. I said the radio might not have been corrupted it might just of crashed but you cannot access AAHK through fastboot/bootloader.
AADAM H. AKHTAR said:
You cant flash clockwork mod on if you dont have USB debugging mode on, when the phone is stuck on the htc logo the only way is to flash a radio that works with the phone through bootloader/fastboot.
also when you flash a radio it wipes clockwork mod off it so you cant flash a recovery.
The radio file either was corrupted or either the wrong one for the phone because most of the time when you flash it is going to go perfectly but there is a chance where it will crash the process.
Again.. I said the radio might not have been corrupted it might just of crashed but you cannot access AAHK through fastboot/bootloader.
Click to expand...
Click to collapse
Wrong. All you say is wrong and misleading. To flash a recovery you need fastboot drivers working...if you don't have fastboot drivers working, that means that you can not access hboot. Therefore, your phone is bricked.
Second, when you flash a radio it wipes nothing...a ruu wipes partitions not any other stuff. AAHK, does not flash radios but flashes partition to gain ENG S-OFF, but wipes nothing. If the radio was corrupted and you were flashing in PD98IMG.zip way, then it won't flash as it get parsed before doing it, as it is the case in the Hack Kit.
A corrupted radio is bricked device. There is no chance to flash a corrupted radio and have a working phone. Flashing a wrong partition is a insurance to get a paperweight. Maybe you should read and do some research instead of trolling the forum.
glevitan said:
Wrong. All you say is wrong and misleading. To flash a recovery you need fastboot drivers working...if you don't have fastboot drivers working, that means that you can not access hboot. Therefore, your phone is bricked.
Second, when you flash a radio it wipes nothing...a ruu wipes partitions not any other stuff. AAHK, does not flash radios but flashes partition to gain ENG S-OFF, but wipes nothing. If the radio was corrupted and you were flashing in PD98IMG.zip way, then it won't flash as it get parsed before doing it, as it is the case in the Hack Kit.
A corrupted radio is bricked device. There is no chance to flash a corrupted radio and have a working phone. Flashing a wrong partition is a insurance to get a paperweight. Maybe you should read and do some research instead of trolling the forum.
Click to expand...
Click to collapse
AAHK does flash radio's but most of the time when you flash radios via a toolkit it will go perfectly, but there will be a time where it will go wrong and you will end up with no clockwork mod recovery or a bad radio flash. When you go on the AAHK you can return to stockrom which flashes radios or whatever but when you have a bad radio on your phone you cant access USB debugging mode because you need that on so you can access the AAHK. Flashing a new and updated radio will work because if your phone was bricked it will not let you into HBOOT/FASTBOOT.
Thread closed
Obviously too many technical errors in the OP. This thread only misleads users with no or little knowledge. Next time you better research a bit more before posting anything. Additionally there are dozens of CORRECT tuts all over xda to solve that kind of problems.
regards
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 !