[Q] Emmc error 3 weeks after rom flash? - HTC Desire S

Hi Guys,
I literally feel sick to my stomach how dumb I've been.
I've basically fallen foul of the temptation to upgrade my HTC Desire S from the standard supplied gingerbread 2.3 to the hydrogen v1.9 saga v3 zip file (2.3.1.).
It’s crashed on me now all I have is the white HTC welcome screen.
I had installed the revolutionary.io s-off tool and rooted it. Everything seemed ok for about 3 weeks then I started to get intermittent phone call cut out and today it’s just frozen at the HTC logo on white background.
Today I have attempted to restore a backup file that I had made, to recovery it through the Revolutionary tool and it installed back to a low tech interface. I then tried to install over the hydrogen ROM again without success. Now it has 5 errors on the Rev tools’ opening page.
A mixture of;
Can’t mount/open recovery log/command/last log.
I don’t know what the hell to do any suggestions from you good altruistic folk?!!
Shall I try a factory reset?
I’d be very thankful of any suggestions. I just wished I’ waited for ICS, curiosity got the better of me

Here:
Possible FIX for the infamous eMMC problem...

Related

No New Rom is Working

My phone was working perfectly with an older version of the evil hero rom so 2 days ago I decided to update to the newest version which is v2xx or w/e and ever since then I have not been able to either go past the green mytouch boot up screen or If it does boot I cant login into my google account if I skip that step I can browse the web fine over 3g and wifi but cant login into the account...I have tried many different memory cards I have unrooted and re-rooted my phone like a million times now...if someone can just tell me whats going on...I flashed the engineering spl too .2005...I would post in general but it seems as if that section does not get as many hits as does the android development.
First of all.
If you were having several issues PRIOR to trying that laundry list of steps to go about solving the problem...YOU CONTINUED TO GET IN OVER YOUR HEAD! That's admirable that you made an (unsuccessful) attempt to go about fixing said issue on your own; but not worth it.
You were stuck on the SPLASH SCREEN - not locked in bootloop. Typically, if you didn't WIPE before an upgrade, that splash screen should remain for roughly 5-10 minutes depending on the range of changes made in the upgraded version of the ROM. Also, if you follow the developers thread on ROM features, you might want to re-read or properly describe exactly what you did, saw and tried to do ---> IN THAT THREAD!
My suggestion: Assuming that you backed up your ORIGINAL NANDROID from the stock "Cupcake" version of the OS...restore that backup, then start all over from the basics.
Reignzone said:
If you were having several issues PRIOR to trying that laundry list of steps to go about solving the problem...YOU CONTINUED TO GET IN OVER YOUR HEAD! That's admirable that you made an (unsuccessful) attempt to go about fixing said issue on your own; but not worth it.
You were stuck on the SPLASH SCREEN - not locked in bootloop. Typically, if you didn't WIPE before an upgrade, that splash screen should remain for roughly 5-10 minutes depending on the range of changes made in the upgraded version of the ROM. Also, if you follow the developers thread on ROM features, you might want to re-read or properly describe exactly what you did, saw and tried to do ---> IN THAT THREAD!
My suggestion: Assuming that you backed up your ORIGINAL NANDROID from the stock "Cupcake" version of the OS...restore that backup, then start all over from the basics.
Click to expand...
Click to collapse
Yo I did all of that im using the nandroid backup right now and I said I unrooted my phone and started from scratch and am still having the same issue and I always wipe before a new flash...its just frustrating that i cant login into the google account and the rom works fine other than that
also i never said that I bricked the phone or something the recovery is working and all...I have done all the basics I have the partitions and what not...the only reason Im posting here is to see if anyone know if certain mytouch's made after a day are having problems with root I saw it in some thread some where but wasnt able to find it I think it was mytouch's made after July 26th?

[Q] HTC Evo 4g LTE Updating Current Version of Recovery

Hope you all are doing great today.
I am on my 3rd LTE (1st Android phone). The first I rooted using REGAWMOD with no issues. Shortly after I became unable to connect to WiFi. Unrooted it using the RUU and returned it to BestBuy and got another. 2nd one wouldnt connect to WiFi from day 1 so I took it back too. Current phone I attempted to root using REGAWMOD, but it got an error after unlocking the bootloader. I then installed BusyBox and SuperSU w/ no problems. I'm S-On, using TWRP v2.1.8 for recovery, and running Charmeleon 5.0.0.
When I attempt to wipe system from recovery, it looks like it's going to complete the task, but within 5 seconds it stops and says "System Wipe Complete" at the top of the screen. Inside the gray box it says Verifying filesystems...then Verifying partition sizes Running boot script... Then Finished running boot script. Formatting /system then the completed message pops up. I know it should take longer than it does to wipe the system.
To possibly correct this, I'd like to install the newest version of TWRP but I can't figure out how to install a new recovery on a phone that currently has one. I've looked all over the place for an answer but cant seem to find one. I would greatly appreciate it if you guys would give me hand.
I love the phone and love the idea of being able to customize it while increasing performance. It's frustrating that the makers of these phones don't ship them totally optimized. Kind of like Microsoft limiting what we can do with the XBox.
Thank you all very much for any and all help and suggestions
King of the Couch

How to Restore from Latest S3 Nightly?

EDIT: 12/23/2012 3:19AM.. Doing a little research I figured out what the issue was. Used Brian Gove's Guide
[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)
From Step 5 Onwords and everything works great.
.. I am still stumped on exactly what happen. I am almost positive it was because of the new file structure..
Just Proves that with a little patience and smarts anyone can use the resourced and tools here to solve their own android problems without bothering anyone haha.
Thank you all for your articles and Merry Xmas / Happy Holidays to Everyone!!
now.. I gotta unlock my boot loader and start all over..
Soft Brick.....
I was looking around and I cant seem to find a post that really solves my problem.
I have a Verizon S3 that I rooted and flashed to CyanogenMod Nightly build and everything was working great.
I used Rom Manager Premium and it updated me to update to CMW 6023. I went ahead and updated.
I saw that there was an update for my Daily As well 12/22/12 so I went ahead and used Rom Manager to download it and install it for me like It did with my last 16 Roms. That Rom had some strange things going on so I flashed to an older rom 12/20/12 and that rom was buggy as well.
Finally I decided that I should just stop with the Daily's and use the stable. When I loaded the Stable things started to still act strange. Mostly the Keyboard would not work and keep crashing. I decided then to just reload my original backup from Verizon.
Before I went in to recovery i took a look at my files and backed everything up. However then I noticed something that was not there before, a folder /0 with most of my main files inside.
I went into CWM v6.0.2.3. and tried to do a restore to my original nandroid backup from verizon but it looks like it failed.
It Says "Error While Restoring System" and kicked me back to CWM
Now when I reboot all I see is the White "Samsung Galaxy s3"
Did I Screw the pooch on this? Kinda nervous haha.
I am Posiive its a Soft Brik and hoping there is a way to fix it.
I can however get to Download mode. If anyone knows a great guide to help me reflash with Odin that would be fantastic.
thanks guys, been a long time reader and this is the first problem I have really had.
I apologize if this has already been over in a post.
Just a quick step breakdown would be great. I am really hoping that I didnt brick my phone.
Thanks for the help and Merry Christmas / Happy Holidays to everyone.

Razr M - Boot Animation Freeze on all Versions Except ICS 4.0

Hey Everyone ! I have an interesting issue. My girlfriend's old Razr M took a nasty hit a long time ago. Screen shattered, and even split on the upper left corner. After that we couldn't tell if it would power up or any thing. Since than she had gotten a new one and it works great except it was after the OTA update where you can't unlock the bootloader. I kept the old one for "possible parts" as I told her but deep down it was the hate to fully throw out any kind of amazing device and admit it had been defeated entirely, plus I had been researching and learning alot about rooting, flashing unlocking, etc. since then and I also enjoy fixing things. Also me and her both remembered that it took that nasty hit before the OTA update and wanted to see not only if I could get it working again but also see how far we could get with it ! I'm somewhat noobish but have alot of research and trial and error hours under belt. The Dev's threads helped me completely and they are right when they say Research and FOLLOW DIRECTIONS step by step !
Here's how far we got ...
It would power up but freeze halfway through boot animation and bootloop.
Factory Reset, Wiped everything countless times still same.
Charged it to 100% powered it up and it did the same.
Left the house longer than expected while it was plugged in and still bootlooping and came home to it actually to the welcome screen.
Set it up and rooted successfully using Matt's Utility but it did the same after restart.
( Matt's the **** and does awesome work ! Girlfriend rolled her eyes and laughed that the utility I was using was made by a fellow "obsessed" fan of the one and only Dark Knight ! )
Again left it bootloop for at least an hour til it eventually worked again.
Quickly got OTA rootkeeper just in case i couldn't prevent the OTA update.
( just playing it safe ya know )
Unlocked the Bootloader with Motopocalypse and that also worked great.
( Dan Rosenberg's Great time and effort to do the impossible on this one ! )
Then I figured ok ... Now I can jump to any version I want thinking it might be just the one it was on.
I flashed back to Stock ICS 4.0 using House of Moto
( Amazing work by Samurhi ! Another great Developer I owe a huge thanx to ! )
Rebooted after flashing back to Stock ICS flawlessly and no issues at all doing so after that.
After that I tried every firmware from Stock to JB remaking every House of Moto folder for each one the exact same as before and the boot animation would freeze halfway through like before.
Flashed back to Stock ICS 4.0 again and it continued to have no problems at all ! I even rooted using Matt's Utility 1.20 putting it at 4.1 and still same boot animation freeze.
Then I tried custom roms like Cyanogenmod, Validus, MoKee and Liquid Smooth following all instructions and using correct GApps when needed and with those the boot animation goes all the way to where it seems like it would switch to the welcome screen or lock screen but freezes on the animation just before that, than after about 10 secs reboots ....
What could it be ? I've looked every where for any kind of possibility imaginable and would hate to believe after resurrecting this phone from the dead, rooting it and even unlocking the bootloader that it can only live on as a Stock ICS 4.0 version for ever after beating the odds and going so far !!!
Any insight, ideas or help of any kind is greatly appreciated !!!

How a noob got sucked into modding devices and stop bricking them.

I had browsed this forum for awhile and was having major issues with AT&T because my phone, as it sat in the eyes of ATT, decided that I needed to be on towers in another county which completely rendered reaching me by land line impossible and my service was such garbage, that I went through five phone numbers in as many phones. My iPhone 4 was screwed, I got a 1st run Nokia Lumina Windows Phone, but the case and windows 8 killed it for me (you had antennae right where you'd normally rest your fingers and so talking on it was a chore. I decided to get another iphone, and another, all met with failure. I stumbled onto these forums one day and discovered the word "root." My iphone was again giving me trouble and my wifes android seemed to do more....way more.
So I'm on my way home with my first android- a cheap motorola atrix HD. When they finally fixed my tower issue I was on my fifth number and I had read on these forums about root. So I get home around Christmas, and promptly rooted my atrix without knowing anything and figured I would learn as I went. I used the motochopper root by djrbliss and Dan Rosenthal (I think) with the fix bootloader screen. I figured I would learn half assed and learn as I go. I download TIBU, and proceeded to brick my phone. I got verification at customer care that the atrix may have been modified, and if it wasnt defective, swap it at the store.
TIBU Brick
Ran on 70 apps total. Removed the wrong one, Brick.
Rooted and botched something stupid, BRICK.
Tried to flash Cyanogenmod. Brick.
Flashed Cyanogenmod and thought I didn't do it right: Grew Frustrated and formatted the phone. ( I was getting as many replacements as I wanted and my wife continued to get irritated with my new hobby which she still hates.
Take my hard bricked HD to ATT store just to find out that I am eligible for the next program.
I shied away from rooting, Got rid of the mega and then got a Galaxy S4. That fever came right back and the next thing I know I am reading, retaining and absorbing as I bricked my S4 four times- twice by not paying attention and twice by not understanding safestrap recovery. The fever of modding finnally got me off of my rear when the guy at best buy reflashed my s4 for the second time and told me about RSD Lite. I go, download RSD Lite, Install my motorola drivers, Install my Operating System via sideload, download CWM recovery, flash CM 10x.x and forget my gapps...no worries, as I had discovered goo.im and f-droid and a few other places where I just found the correct jb gapps moving up from ICS obviously. I then hard brick the Atrix HD and I reinstalled my OS, got the anysoft keyboard from f-droid (the motorola keyboard kept dying) and I flash CM 10 and the JB gapps and bam, I feel like i'm no longer a noob. I was gone for a few months when I did all of this and as soon as I got home, I bought my brothers note 2 which I promptly rooted using cf autoroot and odin and then I flashed the Pacman Rom Stable 4.3. I experienced a soft brick moving up to kit-kat and unstable nightlies of Pacrom, but I moved everything to my SD card and rom installer still had my 4.3 gapps, and stable 4.3 pac rom. I was short on money and had to get a loan on the note 2 which I m getting back.
Now, I'm staring at my S4 for weeks...thinking "god I hate this stupid thing because it has no root on NC1.
Finally, yesterday, I found the towelroot apk and I rooted my i337 NC1. I set up the phone in a few moments, hooked up the proper wanam modules, and I tried with no success to put CWM Philz touch recovery. I was almost resigned to just using the apex launcher but I couldn't stay away from pushing myself to the limit and finally installing safestrap and a touchwhiz rom. So tonight, I finally installed safestrap after reading the steps to get version 3.72 running. Now I was trying to find a compatible touchwhiz based rom that suited me because I finally safestrapped my s4 and ran a backup to my SD, followed by a full wipe (excluding the SD card) and I went right here to read more (on NC1 get the new ODEXED version and I flashed fine without odin, and not rebooting into DL mode, and am now running the Venom v3.02 Safe Strap rom on my S4 like a boss.
Now for the clincher if you're still reading...I don't even know linux, let alone how to use a terminal emulator but for some strange reason, I now know what to do and what not to do to brick a device, and most importantly of all,
super noobs take note:
I FOLLOW THE DIRECTIONS EXACTLY.
I know little to nothing regarding the finer workings of phones (I now know better than to try to mess with things I know nothing about) but I paid attention.
And the payoff is being able to do this to almost any device...but now I am going to read up more because I want to build a nasty rom that gives the user so much access that it borders on criminally sick.
In short, the moral is to PAY ATTENTION. KNOW YOUR LIMITATIONS. FOLLOW INSTRUCTIONS.
Shout out here:
http://forum.xda-developers.com/showthread.php?t=2447482
And Here:
http://forum.xda-developers.com/showthread.php?t=2447482&page=109
Mad props for the simple instruction. I'm gonna go play with my.....new touchwhiz ROM on my S4.

Categories

Resources