Hi, I've made a couple posts about this in both the One M9 and Sprint One M9 forums seeking some help with this phone that signs point to not being a lost cause but I myself am very lost. Neither of those forums seem particularly active at this point in the phone's lifespan so I decided to try posting here. I'll explain what happened and how the phone is behaving and refusing, despite my best efforts, to go back to normal.
I had my Sprint M9 rooted, unlocked, S-Off running Leedroid with TWRP. Last Tuesday, some sort of cascading failure happened causing google services to crash, everything else started crashing and I kept getting crash notifications over and over so I eventually rebooted the device. However, it didn't boot. I eventually got into TWRP, probably jumped the gun on wiping data and system after wiping cache failed to yield any results, but I had a rom on my sd card so I figured I'd just reflash because it was obvious there was something seriously wrong. I couldn't get into download mode.
Cut to now. I have bootloader access, I have TWRP access, none of the main partitions will mount in TWRP (invalid argument). I didn't have any encryption on these partitions but I get the error "Unable to find crypto footer". The solution I see most often touted for the mounting issues is to "Format Data" in TWRP but oddly, I type "yes", I swipe, and I'm met with the exact same errors. This is where it gets weird. As I mentioned, I'm S-Off and unlocked. You'd think I could flash hosd via fastboot, head to download mode and just get a clean RUU install going. And it looks like I can do that, the command line messages I get from fastboot flashing are "OKAY", not "FAILED", and yet, nothing actually flashes! I confirmed this via trying to flash the stock recovery over the TWRP image via fastboot, then booting recovery and still finding TWRP. I'm VERY confused about all of this.
I've seen some info in my searches that indicates some of this stuff can happen if your emmc is faulty (hardware failure), but I've pulled the dmesg log and can't find any errors that would be indicative of emmc failure. Anyone have any idea where to go next? Because I'm stumped.
I've attached a recovery.log and dmesg if anyone wants to take a look. Any suggestions would be greatly appreciated because I'm frankly out of ideas.
Related
Hello,
I have a htc desire s (s-on, 2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04 installed).
When I start the phone with fastboot enabled, the widgets occasionally close and load again.
So everything start normal, but sometimes the widgets close in less than a second after startup and load again.
This only happens since 2.10.401.8 is installed.
I think that it's htc sense that crashes, but I'm not certain.
Already tried a factory reset, but same result.
Does Anyone have an idea what wrong and/or a solution?
After further testing I guess fast boot isn't working correctly anymore even after factory reset.
Is this a hardware problem or is there a way to test if it is a hardware problem?
Now it start to take a lot of time to startup and shutdown.
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
From what I've seen on here, this sounds like what used to be called "the dreaded eMCC chip" problem, but is actually the "cache" partition being corrupted.
From what I've read, you may just about get away with it. Have a look at the following threads;-
http://forum.xda-developers.com/showthread.php?t=1177299
http://forum.xda-developers.com/showthread.php?t=1314629
Thanks, I feared that it was the emmc problem.
I have never pulled out the battery.
I will look into the threads, but I don't know if there is much I can do being s-on.
Update:
I had to send the device to HTC and they replaced the mainboard.
Everything is working good again.
Hi.
Once I tried to install RUU on S-offed rooted phone. Instalation stopped and didn't continue. I had the same problem with partitions
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
Click to expand...
Click to collapse
What helped is to format cache partition in recovery. After that I could bring back my previous rom. In the end I didn't try to install RUU anymore.
I hope it will help.
---
Sorry, I didn't see your last post
Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
So, as the topic states, I'm having major problems as of late.
Nexus S, GT-I9020A
ROM: CM9
Over the past few months, my phones been acting up. My phone when rebooted stalls at the Google Lock Screen. I am unable to mount the E drive in CWM as well,
Going into CWM,
1) wipe data/factory reset gives me problems, results below
--Wiping Data...
Formatting /data...
E: Format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
2) wipe cache partition
--Wiping cache...
Formatting /cache...
Cache wipe complete.
3) Mounts and Storage
Error mounting /sdcard!
Error mounting /system!
Error mounting /data!
format /sdcard ...
Error mounting /sdcard!
Skipping format...
Done
4) Apply update from .zip file on SD card
E: can't mount /sdcard/
.... That's about all the options that I would go through to fix a rom. I don't know what else to do, last time this happened the E drive magically mounted and I was able to turn my phone back on, this time I've not been so lucky.
Reading around, I haven't been able to get any information on where to go next, most topics seem to be successful with the things I've done. I'm afraid that the phone is bricked, is there anything else I could try before I throw in the towel?
What version of CWM recovery are you using?
polobunny said:
What version of CWM recovery are you using?
Click to expand...
Click to collapse
I knew I forgot something,
v5.0.2.0
Bump to the top,
Is there any insight on the way forward? I've heard of Odin as something that may help, but from what I've read, Odin is only Samsung, Fastboot for Google.
No one has been able to help me, or anyone else with this issue, although it seems rather common in the past 6 months. I have read dozens of threads with this problem, they are all mostly ignored, little replied to, and never solved.
CWM Touch is what is did it to your phone. I would suggest switching to another recovery at least, and try installing a new ROM that way if you already have one on your phone. If you have nothing on the memory already, good luck getting something on it, you're probably going to have to send it in.
In my experience, nothing will work to write to your MS once it is corrupted. I have tried the Toolkit, ADB, ODIN, and Fastboot. All of it worked correctly until it got to the MS portion of my memory, then it would error out and complete, with no change. I have put well over 100 hours of reading and effort into it. Went from knowing NOTHING about this except how to flash a ROM, to knowing all of the fastboot commands by heart... Still no luck.
Aggravating, I know. But that's the way the cookie crumbles sometimes. :crying:
DizturbedOne said:
No one has been able to help me, or anyone else with this issue, although it seems rather common in the past 6 months. I have read dozens of threads with this problem, they are all mostly ignored, little replied to, and never solved.
CWM Touch is what is did it to your phone. I would suggest switching to another recovery at least, and try installing a new ROM that way if you already have one on your phone. If you have nothing on the memory already, good luck getting something on it, you're probably going to have to send it in.
In my experience, nothing will work to write to your MS once it is corrupted. I have tried the Toolkit, ADB, ODIN, and Fastboot. All of it worked correctly until it got to the MS portion of my memory, then it would error out and complete, with no change. I have put well over 100 hours of reading and effort into it. Went from knowing NOTHING about this except how to flash a ROM, to knowing all of the fastboot commands by heart... Still no luck.
Aggravating, I know. But that's the way the cookie crumbles sometimes. :crying:
Click to expand...
Click to collapse
Ah, seemingly so eh? The phone is probably not even worth sending it in as it would probably cost just as much to buy a new one.
I don't have CWM Touch (assuming that's CWM with touch function), just CWM that requires the vol rockers. It's an old version.
Hmm, it's been a while, but how would I be able to change the recovery if I can't access the E drive? I presume ADB? Then hope it works?
Anyways, thanks for your help, it's been quite frustrating seeing nothing turn up.
Another bump in hopes anyone with a fix reads this.
Unlocked, rooted, TWRP, Cataclysm Final Lollipop (my phone never played nice with any MM ROM I tried, so I just went back to this and have been great ever since)
My phone has been rock stable for months, today I pull it out of my pocket and the screen is black. I turn it back on and it freezes on the Google screen with the unlock logo.
I can get into bootloader via power+voldown, but if I launch recovery it gets past the Google screen but then freezes on the TeamWin page.
Any suggestions, please? Searches intimate power button issues, but given I get no bootloops, I can turn the phone off reliably by holding the power button down, and it freezes at the same point consistently, it's hard for me to think that's the issue in my scenario, too. Thank you!
As an update, I used fastboot to successfully flash the newest version of TWRP, just to be sure, but it still gets stuck in the same spot, as does trying to boot normally.
Try flashing a stock ROM including userdata.img file.
audit13 said:
Try flashing a stock ROM including userdata.img file.
Click to expand...
Click to collapse
Thanks for the suggestion. Is there any way to get my personal data off before I do this?
I guess beggars can't be choosers, but I'd hate to lose anything I don't have backed up already if it ends up being another issue after all (the power button, etc.).
A corrupted ROM can prevent a clean, freshly-installed recovery from launching properly?
Thanks again.
Try flashing different version of TWRP? Maybe one of them will allow you to mount the data partition and copy off your data.
While trying to flash the (stock) new system images, I keep getting "remote: flash write failure" and/or "remote: failed to erase partition." This is via a toolkit or manually via fastboot.
The bootloader remains unlocked through all this
It's especially odd, since now I'm getting it on my recovery partition, which I was able to write to earlier today.
A cursory search of this forum suggests I'm SOL unless I replace the whole motherboard, at which point I might as well get a new phone. Do you (all) concur?
Last ditch thought: I went jogging when it went dead--outside chance a connection to the memory on the motherboard got jostled and could be reattached? Or is it fried?
Continued thanks.
The memory is soldered into place but it is possible that something happened during your jog. I also jog with my nexus 5 for 20 to 30 km per week and have done so for the past year without any issues.
Hi guys
So I was doing some tinkering with my phone and tried to extend the system partition using the guides I found for my phone, and they all went off successfully according to the logs. However, upon rebooting I'm greeted with an "android is locked screen" and even when I enter my correct password and it accepts it, it reboots and goes back to that screen. The recovery (TWRP) and fastboot are still operational and I can quite easily get into them.
In TWRP is says the /data partition is not present. And every attempt at mounting them simply fails. But, when I try and restore the partition table using MiFlash, after getting the correct rom and everything, MiFlash tool simply does not detect my phone, no matter what I do.
I've tried searching this forum to see if there are any solutions, but since I can't seem to find any, please guide me if possible and point me in the correct direction should there be something which I should be looking at.
Please help me urgently