This has been ongoing for a few weeks now. Desire S is currently running Endymion 2.2, but the same thing happened on Cyanogen and Stock roms. Phone will work fine for up to a day, then will completely freeze up during use (has happened in Browser, while entering text, and once just on the lockscreen). During the hang the touchscreen won't respond, connecting USB has no effect (no LED and ADB Devices lists nothing), the 4 buttons give haptic feedback for about 5 seconds after the hang, then nothing. Holding volume+power has no effect, but usually after about 10-20 tries or 15 minutes of doing nothing the phone will return to HTC boot screen, and sit there until I power it off and then remove the battery.
When using clockworkmod, half the time either /system or /data is not mountable (this only happoccasionally get "error mounting /cache/recovery/log"). When this is the case, formatting/factoryreset sometimes gives the "can't mount /data" error, and sometimes works.
Since switching to 4EXT the partitions are always mountable from recovery, but rebooting causes the phone to hang immediately after booting.
Current setup (which at the moment is hanging at the lockscreen)
HBOOT-6.98.2000 (PG88100000)
4EXT Recovery v2.2.7 RC5 (/system /cache and /data all ext4)
Endymion 2.2
tldr: is it possible for /system or /data to break during normal use and sometimes be unmountable? If yes, then can this be prevented? If no, any other suggestions as to what could be going on?
Reads the posts in the eMMC section at the bottom of the index thread, see end if my Sig for link
Swyped from my Desire S using XDA Premium
If you want my opinion, be drastic about your approach to this. Start from the ground up, that way you will be able to more or less narrow down the problem you are experiencing.
1. Change your HBOOT to 0.98.2000 (As you are using the revolutionary HBOOT, you will need to change this using a different method).
1a. Download HBOOT 0.98.2000 from this thread.
1b. Taken from this thread, use this method to change your HBOOT using adb. If you don't know how to use adb .. >_<.
Copy the hboot.img to your SDCARD.
In adb type:
adb devices
adb shell
su (doesn't matter if it says /system/sbin/su not found)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
2. Format all your partitions again using your recovery.
3. Re-install a FRESH ROM, try to avoid backups.
Don't care if anyone thinks differently, this is just what I would do if I was having this problem.
Totally agree with the above post.
But I would suggest even more drastic approach. Restore to complete Stock and S-ON. There are Guides here how to do this. Then do a testing for a couple of days, maybe a week. At the moment when (if) this problem appears again run to your provider and insist a replacement.
IMO this way you will spare yourself a lot of nerves and troubles in future.
ben_pyett said:
Reads the posts in the eMMC section at the bottom of the index thread
Click to expand...
Click to collapse
sorry, didn't mention this in op - checked for eMMC issues when it first started happening and everything seemed okay, so I'm confident it's not a hardware fault. Not sure if there is a different problem that can result in similar, but sporadic, results.
Going to S-ON and try stock rom again and see how it goes.
Thanks guys
I checked mine and was also confident i had an ok emmc but alas, if you have the bad chip, you have a bad chip.
It may manifest it's self in different ways but eventually it's more than likely to fail. You would be wise to proceed with that caveat.
Sent from my HTC Desire
psimyn, how did it go? Also is it a telstra branded handset?
Sorry for the slow reply, finally got a response from the seller.
Handset was unbranded, bought from HK. The seller requested $40 for shipping both ways, which was apparently going to be refunded if the phone was covered by warranty.
Instead, I got an email yesterday claiming that the phone suffered a "software corruption" and that I had to pay an additional $45 for Labour and Administration. When I asked why the response was "I am just explaining to you that the labour cost and all administration are $45".
For now I just want the damn thing back, so it's been paid and they will hopefully send it today.
Related
Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!
I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App
I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.
Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?
fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.
ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.
Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App
Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.
Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita
OK! Looks like we are getting somewhere! It is now mounted.
Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita
You are awesome! Thank you so very much for your help. Up and running.
How far have you gotten?
Sent from my Evita
S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?
As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita
Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.
Hi, I was having issues so i ran a RUU by suggestion and reset my device. afterwards I unlocked, flashed twrp 2.6.3 (2.7+ doesn't work, just boot loop) and then i upgraded to hboot 2.14 so i could install the roms i wanted. since upgrading to 2.14 i was getting new errors so i tried to wipe the device and restart and now I did that all the files are missing.
I cannot mount anything or boot, so i can't install via recovery or sideload at all, because it can't mount to anything. I can't restore or do anything else because it can't mount the cache, data etc.
I tried running the RUU again but now i am getting error 117 and it can't detect the phone, and since it has no OS installed it doesn't go far enough to register with the RUU application, or so i believe.. the phone does work fine, can access fastboot and recovery, i just can't mount or install anything else.
I am currently
Unlocked
S-OFF
HBOOT 2.14 (TextRemoval)
TWRP 2.6.3.0 (Anything higher doesn't work, will just show htc logo(20s), then go to black screen(15s or so) and bootloop
CID:111111111111
Some suggestions would be great. I've run out of ideas and spent the whole day trying different things to fix it.
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
On twrp 2.7,aren't we supposed to delete the .twrp .twrp in twrp folder by using a file explorer? I remember reading that in pandasas twrp o.p
Sent from my Desire HD using Tapatalk
I didn't need to do that, but yes, if you experience problems that's the first thing to do. Reading the OP is essential, and reading the last few pages of a thread is strongly recommended.
Sent from my Evita
timmaaa said:
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
Click to expand...
Click to collapse
Firstly, thanks for your help timmaaa.
The RUU i used was:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed.exe
I simply went to the RUU list and picked the most recent one of my carrier.
I installed it and it worked and booted, however the touch screen did not work. This confused me more because the reason I did a RUU was because the 3 softkeys were no longer working prior, and I was trying to fix it.
I was then having issues flashing roms because of the hboot, so I upgraded the hboot to 2.14 to solve this, using the method and 2.14 Textremoval file in the thread here: http://forum.xda-developers.com/showthread.php?t=2156686
After installing the hboot fine, I then went back to install candykat (to be honest all i want is a working phone, any rom works for me) and then was met with the error that it could not mount E:cache. Now i was also having issues where the bottom buttons in the Recovery menu would not respond (not the softkeys under the screen) and so i tried fixing permissions to this. Either way I got it working again - but was just other strange thing.
I just formatted the phone after mounting it in twrp 2.6.3.0 so now its ready to continue. Not sure what RUU or rom or what to go with next.
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
timmaaa said:
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
Click to expand...
Click to collapse
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
xlmama said:
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
Click to expand...
Click to collapse
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
timmaaa said:
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
Click to expand...
Click to collapse
I was able to get the RUU working and the 3.18 at&t is now installed and working. However I'm now back to my old issue of the 3 capacitive buttons at the bottom not working.
Is there anything software related to fix this or is it likely a hardware failure? When i tap any of the 3 keys, at best it will activate a touch at the lowest portion of the screen on that particular y axis. Example: I press the home key; instead of going back to the homescreen it does nothing, and at most sends a touch command just above at the bottom of the actual touch screen area.
Also, if you think it is a hardware issue, would it be the digitizer? I see they are $30 or so on ebay and figured i could fix up the phone. Everything else works fine except the damn cap. keys
http://www.ebay.com.au/itm/Genuine-...gitizer-front-panel-replacement-/261100897324
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
timmaaa said:
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
Click to expand...
Click to collapse
At most the cap. buttons will light up / flash when the phone does a particular action, but no actual response or input of the cap. buttons registers. I'm going to order the digitizer from the link above and hope for the best. It doesn't clearly say it, but I'm assuming it does come with the digi + screen in one.
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
timmaaa said:
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
Click to expand...
Click to collapse
Hmm, thats a bummer.
On another note. I just picked up the phone and unlocked it and it started vibrating like crazy, opened up the message (sms) app and started inputing random keys on the onscreen keyboard. Definitly something malfunctional with the screen. Bottom cap keys not working and random bouts of the screen randomly inputing.
The vibe crazy thing sounds like what happened to me on an inspire. Flashed wrong firmware
Sent from my HTC One X using Tapatalk
About a year ago I installed Cyanogenmod 10.2 (bootloader unlocked, S-off, custom recovery - TWRP), everything worked great until about 2 weeks ago. I noticed that certain apps/data were getting corrupted/deleteing themselves. Finally a couple days ago it just stopped booting to the OS. I can still access hBoot and TWRP recovery, still mount most of it and access via USB/PC, but my E: /data partition will not mount.
I have been doing research the past couple days, trying multiple things, but I'm worried about trying somethings in fear of making it worse. I have basic knowledge, but no expert. Here are my current software specs:
HTC One X (ATT Version)
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL (Somehow this changed itself back ok)
HBOOT-1.14.002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
TWRP version 2.3.3.1
I have tried running the RUU, but its not detecting the phone, and I also read this is dangerous is you don't have S-Off. Is there a way to delete the /data partition and remake it? I have backed up all relevant data so I can do whatever needs to be done.
Oddly "fastboot devices" is not detecting my phone and I'm getting a windows popup saying its malfunctioned, yet I can boot into TWRP and mount it and transfer files just fine (except the un-mountable /data partition).
I have no clue where to start, and what order things need to be done in, with which version numbers. If anyone can help I would truly appreciate it! :crying: I am tempted to run it over in my car (several times) and have insurance replace it (so they can't tell I voided the warranty, lol ) if I cant get it working. I would be glad to supply any other info you might need about my situation,
Thanks in advance for your time and effort, this is such a great community. -- Eclipsys
I think it would be wise u don't run it over. Haha..anyways..sounds to me like your SD cards got corrupted.
---------- Post added at 12:42 AM ---------- Previous post was at 12:40 AM ----------
Are u saying that u somehow lost s off?
Definitely don't run any RUU while you're s-on, that'll brick the phone. What OS are you running on your PC?
Sent from my Evita
I've been trying to get my One X working for a couple days now. I'm using Windows 8. It seems like my 2 biggest issues is 1: That my /data won't mount, its corrupted somehow, and 2: when in fast boot it wont connect to the computer, so I have no access to adb which is a huge issue. As for the S-On, yeah, somehow I lost it, but that could be fixed if I could get windows fastboot working.
I have tried different cables, its not that (In TWRP I can mount it and access my files, so I know its possible to get to the OS). I have installed and re-installed (several times) HTC Sync. When I plug in the USB cable it makes the chime sound, and shows the popup saying that the device plugged in is malfunctioning and Windows does not recognize it. I was recently reading that some people have had problems with the Sync base driver and suggested downloading the Windows 7 driver and using that, also no success. In the Device Manager it shows the phone with the error Code 10.
Quote from Microsoft website -- "The Code 10 error pertains mainly to hardware and device driver issues or to compatibility issues between hardware drivers and additional software that is installed in Windows."
It suggests a couple possible fixes, one being editing the registry, which I'm about to try, even though I doubt it will work. After that I will try running adb on my Ubuntu PC, but in all honesty, I'm just taking shots in the dark.
As for the corrupt partition, I have the feeling that if I can get it back in working order I should then be able to use a backup to get it booting to OS. As far as I know the /data partition is on the sd-card with all the other partitions so that leads me to believe that its not the whole sd-card that's corrupt, somehow just that part...?
I have no idea how it got this messed up. But if anyone has suggestions or experience with either of these matters, I'm listening.
The corrupt data partition is going to be a bit of a hurdle to get over I think. If it is actually corrupt (which it looks to be) there's not really a lot you can do. As far as getting your fastboot connection working, there's a drivers thread in our General Section, you might need to scroll down a bit but it's there.
Sent from my Evita
No luck with alternate drivers, but I do have it working on Ubuntu, so a minor win. What I'm looking into now is using the adb shell (BusyBox) to possibly use fdisk to format the partitions and then reset them up. EDIT: Not going to work, virtual partitions inside virtual partitions... I paid for the insurance so getting a new one is really only going to cost me a week without a cell, but its more of not wanting to admit defeat, lol.
Anyways, still looking for an alternative. Cant flash an OS or a backup until it is seeing a /data partition. All ideas are welcome.
I did see a program written by someone called Nocturnal that is supposed to fix corrupted sd-cards, but it seems all his download links are '404'. - If you have it or know where I can get it, message me.
Unfortunately I think the insurance might be your only option. Nocturnal's fix is for the sd card only, which is completely separate to the/data partition.
Sent from my Evita
Did you remedy it,or are you sending it in?
Hello,
I have an HTC One Mini (m4) and have spent approximately 3 days trying to grasp various pieces of jargon and babble of the Android community without success.
Between S-OFF, S-ON, firmware, recovery, new partition layouts, old partition layouts, OTA, Stock, kernels, custom ROMs, rumrunners, firewaters, various errors, root, adb, fastboot and other meaningless pieces of broken English, I am giving up. I have spent more time ****ing with my phone than using it in the past week.
I currently run a 'version' of Sense 5.5 made by tr1gg3r3d, on Android 4.4.2. Ultimately the only thing I wanted to achieve was to have an ordinary version of Sense but without the extraneous apps that clog it up. My phone is unlocked and 'tampered' (whatever the **** that means). What I have right now does not appear to update correctly and does not run certain apps that dislike root. The SD permissions do not work.
It is more or less useless for what I need it for.
I saw a ROM for Sense 6 here that requires 'S-OFF'... after spending 3 days jumping through hoops and following badly written instructions for 'S-OFF', and failing each time, trying around 4 different ROMs and script files that tell you nothing of what they're actually doing, I have given up trying to achieve 'S-OFF'. Do I even know what 'S-OFF' is? No.
Can someone give me simple instructions on how to achieve the following:
A phone running HTC Sense 6 (or even just 5.5) that behaves normally, isn't gimped with pointless graphics and allows the extra apps to be removed.
Preferably 'unrooted' as I use apps that dislike root.
Ideally recognised as 'official' HTC so that updates can be delivered without having to spend a week wading through 90 page forum threads.
Thanks in advance.
Your 3days of reading have obviously been a complete waste of time bud as you posted in the wrong thread [emoji33]
Maybe you should have also read and understood the implications of unlocking, rooting your phone before you done so. It is well documented that certain apps eg.. banking ones etc will not work on rooted devices.. BUT there are certain modules created that can cloak root and may allow the app to work. As for removing unnecessary apps... There as also scripts/tools available to do so. It's all here on xda!
Slating a devs Rom that they have spent countless unpaid hours to bring to the xda community (that works flawlessly) is not the way to get help, nor is slating the guides/advice that other members have taken the time to post! Seems that you want the best of both worlds. There are guides on here that will help on whatever you choose to do if you can decipher all the babble/jargon and meaningless broken English.
dlyon said:
Hello,
I have an HTC One Mini (m4) and have spent approximately 3 days trying to grasp various pieces of jargon and babble of the Android community without success.
Can someone give me simple instructions on how to achieve the following:
A phone running HTC Sense 6 (or even just 5.5) that behaves normally, isn't gimped with pointless graphics and allows the extra apps to be removed.
Preferably 'unrooted' as I use apps that dislike root.
Ideally recognised as 'official' HTC so that updates can be delivered without having to spend a week wading through 90 page forum threads.
Thanks in advance.
Click to expand...
Click to collapse
Had a similar experience myself trying to return to stock, for me I was getting cheesed off with the bugs and lack of working bank apps on custom ROMS.
I fixed it by following, and reading in between the lines, on this fellows instructions here.
http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799
I posted a similar help thread myself a few days ago, someone has replied to say S-OFF isn't crucial to doing this so worth a go maybe. I however did get S-OFF by using the method detailed here.
http://forum.xda-developers.com/showthread.php?t=2573479
I should tell you I was on HBOOT2.19. Not sure how important that is.
So here it was I did to get S-OFF
You've obviously got ADB working on your device so lets skip that.
1.Download revone: http://revolutionary.io/revone and copy it into the same folder as your ADB.
2. Open a CMD prompt and type these commands:
Code:
adb push revone /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/revone
Now wait a minute. I found I always got kicked out of the shell after 20 seconds or so, if you do then run adb shell once again.
3. Now type the below text. It is case sensitive so make sure that -P in the second command is uppercase:
Code:
cd /data/local/tmp
./revone -P
4.You'll get an error message, it should be "-2". This is good. Restart your phone using the power button.
5.Once you're back in open up the shell again and run the following commands:
Code:
adb shell
CD /data/local/tmp
./revone -s 0 -u
BAM! You're now in S-OFF mode.
HBOOT 2.2
I used this thread to get to HBOOT 2.22
http://forum.xda-developers.com/showthread.php?t=2584810
Whilst the instructions are fairly simple I will say it is case sensitive. So when you do
Code:
fastboot oem rebootRUU
the RUU has to be in capital letters.
How to return to stock
1. First you need to get yourself TWRP recovery from here: http://teamw.in/project/twrp2/216 and copy the .img file into the same directory as ADB and fastboot.
2. To flash the recovery you need to go into fastboot (hold the power button and the and the volume down button together from a cold boot) and type from a CMD prompt
Code:
fastboot flash recovery recovery.img
where recovery.img is the name of the download.
Mine was called openrecovery-twrp-2.7.1.1-m4.img so I'd use this text:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
3. Once you've flashed the recovery go into recovery and make a backup from the backup menu.
4. Download every file from the link provided in the first post here:
http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799
5. You're going to have to use WinRAR or 7Archive to unzip the RAR files. You'll get a random folder and a stock recovery.img file.
What I did (or eventually did after lots of trail and error) was attached my phone then deleted the backup content in the TWRP folder. I did NOT delete the folders. Just the files within. Then I copied the extracted content from the download folder into the backup folder I'd just emptied on the phone.
6. Now drop back into the recovery again. First make sure what we did in step 5 worked. If you go into Restore can you see the files we generated earlier? Brilliant. Wipe the cache, factory and delvik (I think Delvik is in the advanced settings, obviously don't have it to hand now i'm back on stock!)
7. Now run a restore which should take a few minutes.
8. Reboot the phone but drop straight back into the Bootloader (power and volume down button pressed)
9. If you haven't copied boot.emmc.win into the ADB folder do so now. Whilst you're at it copy the stock recovery.img file into the same folder and rename it to stockrecovery (take the space out).
From a CMD prompt type :
Code:
fastboot flash boot boot.emmc.win/
10. Now we flash the Stock recovery using:
Code:
fastboot flash recovery stockrecovery.img
11. Now relock the OEM thingy by using
Code:
fastboot oem lock
BAM! You're back to a stock albeit a really crappy version based somewhere in the Middle East. But fear not. Boot in, setup your phone and in the Settings area you can run a software update. This will take you to Android 4.3. Once you're in run another software update to go to 4.4.2 with Sense 5.5. Once you've done that do yet another Software Update to get to 4.4.2 with Sense 6.
At this point I did a factory reset from the settings menu. Not sure if it was needed but just wanted any legacy crap completely killing off.
Also you'll see a message about it being a test device. I Google'd it and people said this is because you're S-OFF. It's not important. Nothing is going to HTC, it's merely a log file thingy.
And that my friend, is how my three day headache got me from a rather buggy custom ROM back to Stock. Enjoy.
elmuziko.
Absolutely brilliant post. I can verify that your method to s-off the phone and update to 2.22 works perfectly. I did it 2 days ago.
I changed my cid using supercid. Do you think I should return my cid to its original value before attempting to return to stock or does it matter??
danapoint said:
elmuziko.
Absolutely brilliant post. I can verify that your method to s-off the phone and update to 2.22 works perfectly. I did it 2 days ago.
I changed my cid using supercid. Do you think I should return my cid to its original value before attempting to return to stock or does it matter??
Click to expand...
Click to collapse
Hiya mate
I didn't do any of that at all, although I didn't change my CID knowingly so if it did change, I didn't change it back.
Been on stock a week now with no problems whatsoever. Working like a dream.
Cheers
thank you button is not enough
elmuziko said:
And that my friend, is how my three day headache got me from a rather buggy custom ROM back to Stock. Enjoy.
Click to expand...
Click to collapse
you know what, i just registered to this site to thank you.
i followed your post step by step and BAM, i am in back to stock rom.
thank you, it feels so good
ps: i skipped S-OFF step, so it is not a must.
Help my
Not message for phone unlock bootloader unlock token chek successfully
Failed to Get S-Off
Before my Question:
My HTC ONE MINI Details:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.28.40e.00.24
OpenDSP-v19.2.0268.0927
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2015, 15:21:25.0
Ok, Now, I bought this Mobile in Dubai, Middle East and while i was waiting eagerly for Lollipop Update and the HTC did the cheating, i decided to try some custom roms and in between the process i wiped my internal memory which means i lost my original stock rom. Somehow i got this M4_4.14.401.1_Stock_v3.0.0 flashed it and now my mobile works flawlessly, the thing is the mobile is "TAMPERED" "UNLOCKED" & "S-ON", i tried all the process to S-OFF, i tried sunshine but spending 25$ on something which is available free, i would not do that. Can you please suggest me what is wrong that i am doing here, because i found one more option which says i have to downgrade my HTC ONE MINI to S-Off, Pity is that to downgrade i need my mobile to be S-Off. I am really exhausted and would appreciate alot if you can help me get S-Off. There are my links which are broken, like the revone after a lots of struggle i downloaded it. i have posted 3 queries on XDA forum but none has been answered. I would Really Really appreciate if you can save me from my misery.