I flashed the synergy 2.3.3 and after about three hours the phone was struggling and slowing down so I rebooted and I got the "system process is not responding" error. I tried a full wipe and reflash and still got it at boot. Then I did superwipe and was able to boot into the rom. So I wanted to try $ShooTeR ReWInD 3D. I superwiped and flashed then I got the same error. FC it doesnt work and neither does waiting. Any help would be appreciated. Also I am s-off revolution and fully rooted. Also have the latest radio and pri.
You will have to run the RUU, then goi back to S-on. Re-run Revolutionary to get it to go away. Unless someone knows another method.
Here is method I used, make sure you do the last one, fastboot write secureflag 3
http://forum.xda-developers.com/showthread.php?t=1194053
Try reflashing your recovery and see if that helps.
Locked & Loaded
" Shooter on Deck "
I really am stumped. I went back to s-on and unrooted then rerooted with rev. It was fine all day then I rebooted and it came back again.
My old Desire had this problem too, while running CM7.
I fixed my problems by running the "Fix Permissions".
Or you could try and run a RUU file to revert to absolute basic, then root/S-OFF.
Does this only happen on custom roms? After i got my EVO 3D, i'm rooted and S-OFF'd but still on stock ROM, haven't had a single problem.
Might wanna look for a more stable version or ROM.
joetemp75 said:
I flashed the synergy 2.3.3 and after about three hours the phone was struggling and slowing down so I rebooted and I got the "system process is not responding" error. I tried a full wipe and reflash and still got it at boot. Then I did superwipe and was able to boot into the rom. So I wanted to try $ShooTeR ReWInD 3D. I superwiped and flashed then I got the same error. FC it doesnt work and neither does waiting. Any help would be appreciated. Also I am s-off revolution and fully rooted. Also have the latest radio and pri.
Click to expand...
Click to collapse
I had that issue last week - rooted but running a stock rom. It has been running fine for two weeks and then all of a sudden I started getting that same error. I noticed that if I removed the SD card, the errors would stop. I copied all of the data on the card to my PC and then formatted the card. I then put the card back into the phone and copied all of the data back on. No more errors but I was missing some stuff and had some strange apps in the app drawer. Finally I performed a Factory Reset and that fixed the app problem. Its been fine ever since.
mvansomeren said:
I had that issue last week - rooted but running a stock rom. It has been running fine for two weeks and then all of a sudden I started getting that same error. I noticed that if I removed the SD card, the errors would stop. I copied all of the data on the card to my PC and then formatted the card. I then put the card back into the phone and copied all of the data back on. No more errors but I was missing some stuff and had some strange apps in the app drawer. Finally I performed a Factory Reset and that fixed the app problem. Its been fine ever since.
Click to expand...
Click to collapse
I am giving that a shot now. Will report back.
No luck Formated sd card rebooted from recovery fresh install synergy, "system process not responding". Pulled the battery and it booted fine. I wonder if it is the recovery
mvansomeren said:
I had that issue last week - rooted but running a stock rom. It has been running fine for two weeks and then all of a sudden I started getting that same error. I noticed that if I removed the SD card, the errors would stop. I copied all of the data on the card to my PC and then formatted the card. I then put the card back into the phone and copied all of the data back on. No more errors but I was missing some stuff and had some strange apps in the app drawer. Finally I performed a Factory Reset and that fixed the app problem. Its been fine ever since.
Click to expand...
Click to collapse
+ 1
I solved mine the same way
Sent from my PG86100 using xda premium
I done it 5 times tonight I just do not understand what the hell is going on. It works for a little while then it freezes and I pull battery and the error comes up again.
Did you do the return to stock method? That fixed mine, as soon as its done and S-on you can run revolutionary again. Just watch at first boot after you run the RUU it will prompt you saying it is checking for updated firmware, then software. You need to hit Cancel! Heck when I got my replacement I ran revolutionary before I even activated This way I would not get the "error 16" or the not being able to roam that seems to happen with revolutionary.
cordell12 said:
Did you do the return to stock method? That fixed mine, as soon as its done and S-on you can run revolutionary again. Just watch at first boot after you run the RUU it will prompt you saying it is checking for updated firmware, then software. You need to hit Cancel! Heck when I got my replacement I ran revolutionary before I even activated This way I would not get the "error 16" or the not being able to roam that seems to happen with revolutionary.
Click to expand...
Click to collapse
Yea I returned to stock totally with s-off, ran revolution and it kept failing at fastboot, said it lost connection, yes I had fastboot off and usb debuging. On the third try it goes to s-off and I flash cwm. Then I flashed synergy and it pops the error. I pull battery and reboot to cwm then reboot to os and it will go through the first time. Then in about an hour it will freeze so I pull battery and reboot to the same error. I am lost.
joetemp75 said:
No luck Formated sd card rebooted from recovery fresh install synergy, "system process not responding". Pulled the battery and it booted fine. I wonder if it is the recovery
Click to expand...
Click to collapse
Just a thought....
If you just remove the SD card, do the errors stop? If so...and you formatted the SD card and the errors return when you put the card back it, you could just have a bad card.
If the errors go away when you remove the card, if you have another SD card handy, you might try running on that card for a while and see if the phone is stable. If it is, that would confirm that the first SD card is bad.
I have had this on my evo 3d stock 2.3.4 unrooted D: and it will say system.android.com has stopped responding. and i force close and it locks up the phone even after a reboot. must battery pull first
Yea I tried that and it still gets the error. I am thinking it is something wrong with the s-off with revolution. It takes three tried to get the s-off. That just doesn't seem right to me. Also the phone is not wiping when I flash a rom.
mvansomeren said:
Just a thought....
If you just remove the SD card, do the errors stop? If so...and you formatted the SD card and the errors return when you put the card back it, you could just have a bad card.
If the errors go away when you remove the card, if you have another SD card handy, you might try running on that card for a while and see if the phone is stable. If it is, that would confirm that the first SD card is bad.
Click to expand...
Click to collapse
Yea I tried that and it still gets the error
Could it just be my phone? Maybe I need to exchange it for another one
Above you said you returned to stock, all the way with S-off. You need to set it to S-on, then you rerun the revolutionary. If you did set S-on and that is just a typo than I would exchange it.
Sent from my PG86100 using xda premium
cordell12 said:
Above you said you returned to stock, all the way with S-off. You need to set it to S-on, then you rerun the revolutionary. If you did set S-on and that is just a typo than I would exchange it.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Yea it was a typo. I have brought it back to s-on tried different sd cards and all the suggestions in this thread. The one thing that I did was when the error came up i pulled the battery then booted into recovery and rebooted from there and it booted up fine.
Just an update. In the end the phone went into a complete bootloop and never came back. The was fully stock with s-on. So I exchanged it and my new 3d is fine. Rooted and s-off with no problems so far. thanks for all the suggestions.
Related
So i unlocked the phone the day before yesterday, flashed BAMF 1.0 first, then flashed Clean 1.0 after that, wiping each time.
Phone worked fine all day today with little to no issues. I then went and get off work, and notice it is dead, even tho it was working around an hour before that. Phone won't straight reboot, so I pull battery cover and battery, reboot, all is good. I hook it up to my car stereo via 3.5 and plays music for all of 30 seconds then emits a loud high pitched sound and the screen froze. UHG! reboot the phone again, try again, same thing. Boot into recovery, flash old backup of stock rom, same problem, reflash Clean 1.0 fresh and new after wiping, same issue.
anyone have any ideas? I am downloading the latest RUU and going to relock the phone, run the RUU and then see if it works, and if so reunlock and such. I would love to have to not do that, as the RUU still has 57 mins to download.
Thanks!
can you unlock the phone once its been locked again?
If you was running cleanROM v1 then update that to V1.1
V1.0 had a lot of freeze issues. My fiance's phone wouldn't run long without a freeze.
The newest version and the senseless ROM are good to go.
nrfitchett4 said:
can you unlock the phone once its been locked again?
Click to expand...
Click to collapse
yeah, same as before, just that you start from step 11. Fastboot flash unlocktoken Unlock_code.bin
Marine6680 said:
If you was running cleanROM v1 then update that to V1.1
V1.0 had a lot of freeze issues. My fiance's phone wouldn't run long without a freeze.
The newest version and the senseless ROM are good to go.
Click to expand...
Click to collapse
no, tried multiple roms, stock RUU, etc.
Phone only bootloops, when it does boot, it claims it has no sim card, but it does...put same sim card in my thunderbolt, works fine.
phone in custom recovery brings up the error, E:Can't mount /dev/block/mmcblk0p33 i think it was.
reading around online, if that error doesn't go away flashing a stock RUU, then the internal memory is more than likely shot or the motherboard is bad. Either way the phone is shot. Since the damn thing won't see the sim either, i am putting it up to it being a bad motherboard.
makes me so mad. the replacement for this phone will be the 5th. I finally found a perfect phone, minus the pink buttons. I was fine with those pink buttons too!
nosympathy said:
yeah, same as before, just that you start from step 11. Fastboot flash unlocktoken Unlock_code.bin
no, tried multiple roms, stock RUU, etc.
Phone only bootloops, when it does boot, it claims it has no sim card, but it does...put same sim card in my thunderbolt, works fine.
phone in custom recovery brings up the error, E:Can't mount /dev/block/mmcblk0p33 i think it was.
reading around online, if that error doesn't go away flashing a stock RUU, then the internal memory is more than likely shot or the motherboard is bad. Either way the phone is shot. Since the damn thing won't see the sim either, i am putting it up to it being a bad motherboard.
makes me so mad. the replacement for this phone will be the 5th. I finally found a perfect phone, minus the pink buttons. I was fine with those pink buttons too!
Click to expand...
Click to collapse
What recovery are you using? I had similar problems with CWR....but none with Amon Ra.
Did you try to flash another kernel?
sent from my newly unlocked Rezound
Booting without the battery cover sometimes fixes bootloops until you can find the problem.
If relocking and flashing a stock ruu doesn't work... well I don't know what the problem is.
Did you get this solved?
Looking for help/suggestions.
I have 2 aria that developed random reboot for no apparent reason...
My work aria was rooted and s-off running cm7.1 for about a month with no issues, I've flashed kang cm7.2 and all seemed ok, but the next morning the phone was dead (it was at 50% before going to sleep). charged it in the morning (the battery was 0%), came to work and while it was on my desk the phone rebooted and continued to do that through out the day. At home, i did factory reset, did not help. I've put it back to s-on and put back the stack ATT 2.2, same results, continues to re-boot at random intervals. Thinking it was hardware, got my job to get me a different phone.
3 weeks later, my wife's aria (rooted but still s-on) running cm7.1 started to run extremely slow and battery would drain in about 5 hours. I've done factory reset, clear everything and it still doing random re-boots just like my aria.
With one aria, I thought that it was a hardware issue, but now 2 arias, looks like os/software. Resetting/ re flashing does not help.
Any suggestions would be highly appreciated.
Are the devices overclocked?
Theonew said:
Are the devices overclocked?
Click to expand...
Click to collapse
yes, they both were overclocked, do not remember at what level, i think whatever the cm7.1 default was.... I did put them back to 600, which did not help.
Thank you
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
dimon2242 said:
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
Click to expand...
Click to collapse
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Did you try doing "format system" before doing a clean install? Also make sure you are using a recent version of Clockworkmod (5.x).
strykme said:
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Click to expand...
Click to collapse
You should touch your wife('s) more often
Sorry, couldn't resist
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
yar2 said:
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
Click to expand...
Click to collapse
yea i do
malware
wipe the phone , then check it out
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
yar2 said:
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
Click to expand...
Click to collapse
Can, because possible errors on the SD card
I still have not solved the random reboot issues. I have two Arias with the exact same problem. I think I somehow contaminated the 2nd phone by swaping SD cards and loading a Nandroid backup from the 1st phone. Both phones are rooted.
I have tried loading 4 roms -- Liberated, CM7.1 stable, CM7.2 RC and Menjeni's version of CM9 and have the exact same random reboot problem Seems like the phones works for anywhere from 5 minutes to over an hour and then reboot.
When I load the different ROMs I wipe everything -- the factory data reset, all the caches and re-formats that CWM offers. I also reformatted the SD card and reloaded CWM via Rom Manger in an effort to completely clean the phone. I also ran two a virus/malware scans on the phone and SD card -- which found no errors.
Is there something else I can do to further clean the phones? Since the same problem is with both phones, I seriously doubt its a hardware problem.
Anyone interested in purchasing 2 somewhat functioning Arias?
yar2 said:
I still have not solved the random reboot issues.
Click to expand...
Click to collapse
yar2, what HBOOT version do you have on the two devices?
HBOOT 6.02.1002
Thanks for trying to help me with this!
yar2 said:
HBOOT 6.02.1002
Thanks for trying to help me with this!
Click to expand...
Click to collapse
OK. I'm assuming you have an AT&T Aria. If not let me know.
Here's what I'd suggest you do. I'm basically trying the most extreme steps to correct the issue so we can verify if the issue is something that can be corrected or not.
1) Reformat your SD card(s) with SD Formatter 3.1. This tool sometimes fixes hard to detect problems that aren't corrected when formatting with other methods. (Default settings are fine.)
2) Run the AT&T 2.2.2 RUU to revert your phone to almost 100% stock. I say almost because the RUU will NOT change your HBOOT, which means even after doing this process, you will still have S-OFF.
3) Try using the phone with the stock unmodified ROM to see if you experience the random reboots you described. If you do, the rest of the steps are not necessary and it's probably a hardware issue.
4) Install CWM by putting your phone into FASTBOOT mode, then using the Android Flasher utility to install the latest version of Clockworkmod. Use this version: http://www.mediafire.com/?lg6b63aqpi1cvbg (source). If you know how to do this from command line with the fastboot command line tool, that is fine too.
5) Boot into CWM. Do factory reset/wipe data and format system partition. Then install the ROM of your choice. I'd suggest something like a recent version of CM7 since it is very stable. If using CM7, install 20110828 gapps immediately after flashing CM7. Reboot and see how it goes.
Even if you already downloaded any of the above files, delete them and download them again this time around (or check the md5 sums if you know how). It's possible the files were corrupted when you downloaded them before and that is why you keep having problems.
Also, as an aside: Are you using third-party batteries with your devices?
Aria random reboot
Thanks drumist for all you advice! When I did my last attempt at a clean install, I used a spare SD card that had never been in the phone.
Both phones are AT&T Arias with the original batteries. I liked the Aria size so much that I upgraded my wife's expired Iphone contract when AT&T was providing a free Aria upgrade just to have a spare in case I damaged one by rooting. Now I have managed to mess up both phones!
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Regardless, I will try what you suggest and let you know the results.
yar2 said:
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
Click to expand...
Click to collapse
Reverting the HBOOT to stock (and yes, returning to S-ON) has some risk -- i.e., if you make a mistake during the process, you can permanently brick the device, so I wouldn't recommend that except as a last resort. The RUU will reflash every other partition on your phone back to stock besides the HBOOT and is safe to do, so stick with that.
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Click to expand...
Click to collapse
Yeah, it's possible. If that is the case, though, the HBOOT wouldn't be the problem (because Nandroid backups do not touch the HBOOT). The RUU will reflash every partition that Nandroid touches.
If you already tried using a different SD card, then I wouldn't worry about using that SD Formatter tool.
Can't find a copy of the AT&T 2.2.2 RUU. They took it off the HTC website. The instructions there are for an OTA update, which I can't do since I'm not running the stock rom.
---------- Post added at 02:51 PM ---------- Previous post was at 02:12 PM ----------
Never mind. I found a copy of the RUU on my laptop.
I have installed the hboot drivers and the phone shows up as a device on my computer, but the RUU says it can't find my phone. I am running Windows 7, if that makes any difference.
Got the RUU to load from an XP machine. Bad news is that the phone still randomly reboots.
I guess the only other step is to un-root and S-On. What have I got to lose. Can't use the phones as they are now.
Got a good way to do this?
I have searched everywhere for an answer to this. I apologize if its been answered before. here is my issue:
I acquired an amaze 4g. S-on no rom. Freezes at white HTC screen. tried stock GB RUU but apparently it has ICS. So I loaded ICS OTA RUU. 3 different ones OTA and leaks. I also have ADB shell access if this matters. I can get to my sd card through CWM but not through 4ext because I am unable to mount the internal sd. I have pulled my hair out for days on end trying to fix the unable to mount /internal_sdcard issue. I did however find a CWM ICS stock recovery download and tried that through CWM since that seemed to be able to acces my external SD somehow (apparently the same way the bootloader does when updating the ph85img). But i get an MD5 sum error. so... this leads me to a new post. How do I fix the mounting issue? Also before the mounting issue happend (i think after trying to install a ROM using a super wipe method). And once that is clear apparently the "roms" hang at the boot animation and go into a bootloop. But first things first. got to get the mount issue fixed. anyhelp will be greatly appreciated!
one last thing. I also have hansoon2000's toolkit v. 3.1 & 3.2 although i prefer 3.1 because 3.2 seems to be very buggy.
Johnny.Sleven said:
I have searched everywhere for an answer to this. I apologize if its been answered before. here is my issue:
I acquired an amaze 4g. S-on no rom. Freezes at white HTC screen. tried stock GB RUU but apparently it has ICS. So I loaded ICS OTA RUU. 3 different ones OTA and leaks. I also have ADB shell access if this matters. I can get to my sd card through CWM but not through 4ext because I am unable to mount the internal sd. I have pulled my hair out for days on end trying to fix the unable to mount /internal_sdcard issue. I did however find a CWM ICS stock recovery download and tried that through CWM since that seemed to be able to acces my external SD somehow (apparently the same way the bootloader does when updating the ph85img). But i get an MD5 sum error. so... this leads me to a new post. How do I fix the mounting issue? Also before the mounting issue happend (i think after trying to install a ROM using a super wipe method). And once that is clear apparently the "roms" hang at the boot animation and go into a bootloop. But first things first. got to get the mount issue fixed. anyhelp will be greatly appreciated!
one last thing. I also have hansoon2000's toolkit v. 3.1 & 3.2 although i prefer 3.1 because 3.2 seems to be very buggy.
Click to expand...
Click to collapse
When you flashed the stock ruu, did you allow it to boot up properly before attempting any flashing or custom recovery using of any sort?
Dark Nightmare said:
When you flashed the stock ruu, did you allow it to boot up properly before attempting any flashing or custom recovery using of any sort?
Click to expand...
Click to collapse
what do you mean by "boot up properly"?
after ruu loads, checks, then updates... i wait until it turns off before i jump into bootloader/recovery. Should i have let it continue to the HTC screen? it just freezes there.
update: ok, reloaded OTA ICS RUU... when it was done I went to fastboot and rebooted left it on htc screen for a few min. then pulled battery > bootlader > unlocked with hansoons > reflashed 4ext > rebooted > no good > did it a second time and went to fastboot > reboot let it load and freeze on HTC. cleared the /internal_sdcard error and its working now. THANKS!!! would have never guessed that all i had to do is reboot and thats all it needed. I was just taking battery out after it was done. on to next issue :/
formatted and cleared everything 3 times... loaded stock ICS rom.. gets half way through boot animation and locks... formatted again.. loaded energy rom, bootlooped at boot animation once, rebooted. and VOILA!
THANK YOU SOOOOOOOOO MUCH MAN! I would give you a thanks but I have no idea how. This is my first post.
There's a button right there , always let the phone boot properly, you may think it freezes on the HTC screen but it's actually setting up files, etc. Don't disturb it, let it be and the set up screen will pop up in a minute or so, it need to add files, remove files and properly map everything on first boot.
Thanks again man! Running perfect. I saw the thanks button, it was right in front of me. haha. :good:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
GoogleFap said:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
Click to expand...
Click to collapse
this seem to becoming a more frequent problem maybe something TWRP is responsible for i came to this same obstacle when trying to flash a new rom like a week ago. i tried all the nifty moves i could but no luck even went to sprint looking for answers ultimately i was forced to format (with windows) both internal and external SD. end result. yep u got it i lost everything almost 26gigs of music and files i had backed up no where else. so i formatted (heart broken) got over it now i back up files daily on my laptop thats the only way ive come to see out of this one. but check around forums a solution might work for i saw a couple didnt work for me tho.
JB ROMs rewrites the addresses of your SD cards, good chance the internal is corrupted. Boot to recovery and go to mount/mount USB storage, if you have windows then as soon as you plug it in windows will tell you to reformat, if you have Mac or Linux manually reformat the card
Thanks for the replies, guys.
Tried reformatting, but that didn't seem to help. On #twrp on freenode, they said it looked from my recovery.log that the internal and sdcard storage is hosed, and the maintainer of TWRP said to RUU back to stock. SIGH. . . .
So, since I don't have Windows at work, going to try these at home tonight:
(Great. Was trying to post links, but wasn't allowed. Suffice it to say, I was going to post my recovery.log link and the links to the instructions I am going to follow to RUU back to stock.)
Well that sucks, I'm lucky that I haven't hosed my emmc yet. I can't decide whether to stay on aosp or not, must have flashed back and forth a million times by now
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
GoogleFap said:
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
Click to expand...
Click to collapse
Did you ever find a solution to this? I'm in the same boat...
llaen said:
Did you ever find a solution to this? I'm in the same boat...
Click to expand...
Click to collapse
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had backed up my sdcard so I didn't really care about not losing it. I think the problem was at least partially caused by having it encrypted.
I ended up flashing to stock and it let me format the sdcard from within the phone - that did it.
Thanks for the suggestion.
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This just advice just saved my life. I thought for sure I bricked my phone, and right before memorial day weekend toooo! I did run into issue with the latest Lollipop RUU. I had to resort to using the old Kit Kat RUU I had saved to my computer from before. It worked like a charm.
I'm s-off, on hboot 1.19, my baseband is 1.12.11.1210.
I just tried to change roms from meanrom ics to paranoid 3.99. Everything went fine in twrp. When I rebooted the phone it ran thru "upgrading android apps" & when it got to the spot where you'd start entering all your info, I got an error saying unfortunately, the process com.android.phone has stopped. There was another message underneath that one. I couldn't really read it but it said something about IU issues. I've tried reflashing the rom but the same thing happens. I have backups made & went to them in twrp, but they aren't a flashable zip like I thought they'd be. I can still get into the bootloader, but when I select fastboot I can't get my phone to connect to my cpu anymore. It was working before I tried all this. I even tried reinstalling meanrom but it gets about a 1/3 of the way thru the install & reboots to the splash screen & it just sits there. I know I'm probably missing something minor, but I could really use some fresh eyes.
Thanks in advance for the help.
ETA...I'm on twrp v.2.6.3.0 & can still get into the bootloader & recovery. Fastboot USB just won't work. I've tried doing system wipes & installing different roms & they either fail or get stuck in bootloop. I found my backups in twrp but they all fail to install when they get to /data. Some of them don't even make it that far.
Well, I went ahead & booted up off of one of my b/u that said it failed. I got my phone back to where I could start entering wifi info,ect...but I'm getting another error unfortunately the process android.process.acore has stopped. I went into twrp & did the "fix permission" thing. I now get the same error as before...unfortunately, the process com.android.phone has stopped.
Well I've been wanting to leave sprint...I guess today is as good a day as any.
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
buddahj said:
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
Click to expand...
Click to collapse
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
numel007 said:
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
Click to expand...
Click to collapse
So........I'm an idiot. I was forgetting to open the command prompt in the platform tools folder. My fastboot usb works fine. Right now, I'm just having trouble installing the htc mtp drivers.
Have the drivers been updated?
Took the red pill. HTC evo 4G LTE evilution red pill.