Formatting INTERNALSD:...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/!
Skipping format...
/Internal_sd wipe complete
I am S-Off and running Amon Ra 3.15 i believe. I installed Newt's rom but my rezound was fully black but "on" earlier today so I went to reload it; doing so it somehow screwed up this way. Help?
EDIT:
Going to bed. Since nobody replied yet and I need my phone asap as my alarm clock, I'm going to try using a RUU and cross my fingers. I wouldn't know if it would fix the internal storage issue nor how to make sure S-Off is still intact; someone please help me. Thanks!
An ruu will not affect s-off. I received that same error starting after I s-offed but it didn't bother me much. The internal sd still works in roms but I can't flash anything from internal sd in recovery anymore. Oh well, gotta pay to play I guess.
Sent from my ADR6425LVW using Tapatalk 2
This problem is most likely due to flashing ICS while still on Gingerbread firmware. Many threads talking to this topic.
Sent from my ADR6425LVW using Tapatalk 2
I still have issues after s-off, and i was on GB when i did s-off.
I still cant MOUNT either internal or EXTERNAL when i boot to AR recovery, BUT if i were to switch to CW i can.
everything works but the MOUNTS within AR 3.15.
You can try CWM or CONS recovery, and it most likely will work for you.
The funny thing is, I didn't recently switch from GB. I've been using ICS for many months. I've been using Cleanrom 4.5 Pro until I recently swapped it out for Newts OnE XxX RLS 3.1.2. As far as I can tell, I see no reason for this issue.
Shanayo said:
The funny thing is, I didn't recently switch from GB. I've been using ICS for many months. I've been using Cleanrom 4.5 Pro until I recently swapped it out for Newts OnE XxX RLS 3.1.2. As far as I can tell, I see no reason for this issue.
Click to expand...
Click to collapse
I think you have to reflash the Old Firmware Patch every time you install a new ROM.
I tried to go from CleanROM to SlimROM once without flashing the patch and it had all kinds of issues.
The patch changes certain files so an ICS rom can run on GB firmware, and the files need to be changed on each rom.
Related
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?
hey i want to go back to the stock rezound rom that came with the phone, where can i find it? i installed Newts rom and its CONSTANtly rebooting, i can maybe get 1 minute on the phone before it does, which means i cant get anyting onto the SD card, and yes iv tried reflashing the rom, twice, is there anyway to trasnfer things to the SD card from Amon Ra recovery? thansk
Which one of Newt's roms did you flash?
Did you do the ICS RUU update or not?
gearlo said:
hey i want to go back to the stock rezound rom that came with the phone, where can i find it? i installed Newts rom and its CONSTANtly rebooting, i can maybe get 1 minute on the phone before it does, which means i cant get anyting onto the SD card, and yes iv tried reflashing the rom, twice, is there anyway to trasnfer things to the SD card from Amon Ra recovery? thansk
Click to expand...
Click to collapse
Yes, in the main menu I think like the 3 option. Mount USB or USB mount will allow you to mount the SD card to the computer and you can file transfer.
i flashed this one: http://forum.xda-developers.com/showthread.php?t=1501512
and whats the ics RUU? sorry my last android was the mytouch 4g which was much easier haha
gearlo said:
i flashed this one: http://forum.xda-developers.com/showthread.php?t=1501512
and whats the ics RUU? sorry my last android was the mytouch 4g which was much easier haha
Click to expand...
Click to collapse
The latest ICS leak has new firmware which changes the SD Card mount points (among other things).
When running the latest ICS based roms, you either need to update the firmware or see if the dev offers an SD Card mount patch so the newer version of ICS will work with the older firmware.
I was asking if you installed the RUU because you can't go back to the GB RUU if you did. Since you didn't, mount the card as noted in recovery and use this to go back to a rooted stock rom.
Stock rom - http://www.scottsroms.com/downloads.php?do=file&id=76
Boot Image - http://www.scottsroms.com/downloads.php?do=file&id=77
You'll need to flash the boot image with fastboot like you did your recovery.
And next time, I recommend a nandroid back up before you change roms in case you want to revert back.
My last HTC Thunderbolt, I had used the [ALL IN ONE] The HTC Thunderbolt Tool! to root my phone. This went well.
I then did a backup of the phone using clockwork mod. Then I flashed leanKernel: minimalistic kernel, which now I realize is a CM7 kernel?
The problem fallowed the kernel flashing. It would boot through the HTC boot image, then through the Thunderbolt logo and straight to a black screen. After that I decided to restore the factory backup before the kernel after wiping data and the system. The problem was after restoring the backup of the original rom the phone bricked. I couldn't get it to boot past the white screen with the HTC screen. Thing is before this phone I had a Nexus S 4G so my first official task on that phone was rooting and flashing custom kernels and roms. At this point I'm not sure if the phone was faulty or if I botched the job somewhere.
If you flashed the wrong kernel for the rom the fix was as easy as wiping cache / dalvik and flashing the correct kernel. As far as you backup you might have a corrupted backup which could be why it bricked. Your SD card may be corrupted too and could be why the backup was corrupted. Maybe try backing the SD card up and reformatting it just to be sure.
Sent from my ADR6400L using Tapatalk 2
Thanks for the response. I thought as much actually. I had already had the phone replaced. It had other issues since the first day I had it. I literally had it 4 days and in those 4 days it would just randomly restart and that was all factory. Lucky for me the Manager of the Verizon store sold us the phones. He just replaced it, but mainly because we had a lot of other issues. I'm actually feeling brave enough to try it again. The only thing that bugs me is the RUU thing. On my old phone it was way simpler.. well.. I had it for a year so it was probably just simpler to me. Either way, I guess the question now is what would be a good kernel for the factory rom? Until I find another rom I want to try? I wanted to hold out for the ICS update but I doubt it will happen after all the reading I've done.
Edit: Yes, I understand that asking for a good kernel for the stock rom is asking for opinions, but that's what I'm looking for.
Imos leankernel for gb sense would be the best. You should still think about reformatting your SD card though.
Sent from my ADR6400L using Tapatalk 2
I checked my SD card's download section and guess what I found. imoseyon_leankernel_v5.1.0GBS.zip This is what I flashed to my last phone. From what I gather this should work with sense 2.1 Android 2.3.4, Software number 2.11.605.19 710RD Now I've got to figure out why this bricked my last phone. I should also mention that I did 2 backups. One with Clockwork mod and another after flashing to EXT4. I tried restoring both in EXT4 and no such luck. Keep in mind, this is an old issue but I'm just baffled as to what happened. The SD card seems fine from what testing I've put it through though.
http://forum.xda-developers.com/showthread.php?t=1260185
the thread I got said kernel from.
You need to use 6.2 for 605.19. That shouldn't have bricked you though. From what you've stated though all I can gather is that the backup is bad.
Sent from my ADR6400L using Tapatalk 2
When you say 6.2 are you talking about a kernel version? If so then I thought 5.1.0 was the most recent, as noted by that thread. Am I missing something?
Well... scratch that question.. I did a quick google and noticed that it's not on these forums. >.>
Edit: Ok. Before I get too far into this. I've rooted, and did a backup with revolutionary CWM. I decided to check out the files in the backup on the phone and some files I can open while others throw back a "Cannot Open File: it does not appear to be a valid archive." with winzip and they also give me an error with 7zip. Should the boot.img file give this error? I can't go off of the MD5 as it was generated by these files.
I could see that happening with a windows computer. I don't know which ones it can open honestly. The only way that you will really be able to tell is from the md5 or just by assuming that is bad because of the first unsuccessful restore.
Sent from my ADR6400L using Tapatalk 2
Yeah, I completely scrapped everything from the last phone's rooting process.
I think I'll do another backup just to be on the safe side.
Edit: thank you for your help. I am now rooted and custom kerneled. I think this is pretty much what I wanted. I'll worry about custom ROMs later on down the road.
Sent from my ADR6400L
My apologies if I missed this topic in my searches, I have been trying for 3 days now to get this resolved. I have made some progress but the main issue remains. This is my girlfriends phone and I rooted it and installed a custom rom about 3 months ago. The rom became unstable and she requested a new one. So picked another rom and it worked great for another month or so except the SD was coming up as damaged.
Fast forward to 3 nights ago I decided to try a newer rom so installed the EclipticRez Revamp.Great looking rom was very excited seemed to run smoothly, still unable mount SD in OS but was recognized in recovery. Then tried to place a call and as soon as the first number was pressed to dial the phone froze and began a bootloop. Pulled hair out then decided let's try other roms. Proceeded to install several other roms and each installed perfect booted up, No SD and as soon as I tried to use dialer bootloop.
Up to this point the phone was S-On with hboot 2.11. I used the AIO toolkit to perform the S-Off and now it's S-Off; HBOOT 2.25.2525; Radio 0.95.00.1118r/0.95.00.1223r. Back on the EclipticRez Revamp Rom and after the S-off the SD card is working again! Small victory, the issue still remains that I can not use the actual phone because it reboots. It is not bootlooping but it will cause reboot when trying to use phone for calling. I'm guessing I must need to update the radio but I can not for the life of me figure out how. Please any insight would be greatly appreciated. Thank you all in advance.
Locobato said:
My apologies if I missed this topic in my searches, I have been trying for 3 days now to get this resolved. I have made some progress but the main issue remains. This is my girlfriends phone and I rooted it and installed a custom rom about 3 months ago. The rom became unstable and she requested a new one. So picked another rom and it worked great for another month or so except the SD was coming up as damaged.
Fast forward to 3 nights ago I decided to try a newer rom so installed the EclipticRez Revamp.Great looking rom was very excited seemed to run smoothly, still unable mount SD in OS but was recognized in recovery. Then tried to place a call and as soon as the first number was pressed to dial the phone froze and began a bootloop. Pulled hair out then decided let's try other roms. Proceeded to install several other roms and each installed perfect booted up, No SD and as soon as I tried to use dialer bootloop.
Up to this point the phone was S-On with hboot 2.11. I used the AIO toolkit to perform the S-Off and now it's S-Off; HBOOT 2.25.2525; Radio 0.95.00.1118r/0.95.00.1223r. Back on the EclipticRez Revamp Rom and after the S-off the SD card is working again! Small victory, the issue still remains that I can not use the actual phone because it reboots. It is not bootlooping but it will cause reboot when trying to use phone for calling. I'm guessing I must need to update the radio but I can not for the life of me figure out how. Please any insight would be greatly appreciated. Thank you all in advance.
Click to expand...
Click to collapse
You're running a newer ROM on old firmware. It's also possible your hboot doesn't match the radios. I suggest you run the Global Leak RUU on it then update the Recovery to Amon Ra 3.16, then flash Ecliptic, if that's the ROM you've chosen. It's a global ROM, I believe. Radios are updated in hboot. There here, too. Check the sticky-roll-up thread for the links.
Global radios are 2.22.10.0801r, 2.22.10.0803r and hboot is 2.27.
Locobato said:
My apologies if I missed this topic in my searches, I have been trying for 3 days now to get this resolved. I have made some progress but the main issue remains. This is my girlfriends phone and I rooted it and installed a custom rom about 3 months ago. The rom became unstable and she requested a new one. So picked another rom and it worked great for another month or so except the SD was coming up as damaged.
Fast forward to 3 nights ago I decided to try a newer rom so installed the EclipticRez Revamp.Great looking rom was very excited seemed to run smoothly, still unable mount SD in OS but was recognized in recovery. Then tried to place a call and as soon as the first number was pressed to dial the phone froze and began a bootloop. Pulled hair out then decided let's try other roms. Proceeded to install several other roms and each installed perfect booted up, No SD and as soon as I tried to use dialer bootloop.
Up to this point the phone was S-On with hboot 2.11. I used the AIO toolkit to perform the S-Off and now it's S-Off; HBOOT 2.25.2525; Radio 0.95.00.1118r/0.95.00.1223r. Back on the EclipticRez Revamp Rom and after the S-off the SD card is working again! Small victory, the issue still remains that I can not use the actual phone because it reboots. It is not bootlooping but it will cause reboot when trying to use phone for calling. I'm guessing I must need to update the radio but I can not for the life of me figure out how. Please any insight would be greatly appreciated. Thank you all in advance.
Click to expand...
Click to collapse
Yea like hgoldner said, your running newer software on older firmware.you will run into a bunch of issues that way. Once you update the radios and firmware, you should be good to go
I had the same problem with the phone but it would constantly force close. Found out that amon ra wasn't wiping correctly. Went to cwm and never looked back. If you want a great ROM try tonked world edition I get great battery life with extended battery.
Sent from my SCH-I815 using XDA Premium HD app
I've spent about well over 8 hours fixing my issue of unable to mount /sdcard/ and it not recognizing my microsd card; researching, learning, trying this, trying that. After I got that fixed, now when I try to install SuperSU through TWRP 2.5 I get the message unable to mount /data.
I am stuck in bootloop for CM10 which was released in October 2012, using Hboot 1.5 S-ON
I don't mind formatting everything and losing data because I've already backed it up and formatted. My goal right now is to go back to completely stock rooted. I can't do anything since SuperSu won't install due to "unable to mount /data".
I am relatively a beginner; I read ONE thread here who had the same problem, but I couldn't understand if it was the same problem as mine or if there was an easier way or understand what to do.
http://forum.xda-developers.com/showthread.php?t=1838204
Try fastboot flashing and older version of twrp v2.3.1.0 and see if that helps click the link in my sig
bigdaddy619 said:
Try fastboot flashing and older version of twrp v2.3.1.0 and see if that helps click the link in my sig
Click to expand...
Click to collapse
I somehow got extremely lucky. I had just downloaded your twrp zip and wanted to try SuperSU one more time....so in TWRP 2.5,
My Steps:
Tried to install SuperSu -- Failed due to /data and /sdcard again
I went to Mount -> Mount USB Storage
In windows open Computer -> Right click phone storage -> Quick Format FAT32
Immediately back to Mount and click Data & Internal Storage to mount
Adb push Supersu.zip to /sdcard
Install SuperSu.zip --- Successful!!!
It seems on every reboot I have to keep formatting my internal storage, but maybe I can google a fix for that. First I'm going to try RUU for HBoot 1.5 to see if that fixes it.
Thank you for your help so far; I have low hopes for RUU working on my first attempt since everything has been not working every time I've tried to fix it. I've actually been using no external SDcard or Internal SDcard (they wouldn't mount) for going on 4 months now since I tried to upgrade to a different CM version.....of course tonight was the night I tried to fix it and I have visiting family coming in tomorrow, so I need to make my phone useable.
Glad you got it
Oh yea S-OFF that mo-fo
bigdaddy619 said:
Glad you got it
Oh yea S-OFF that mo-fo
Click to expand...
Click to collapse
That's the plan stan...but after I get a working RUU. S-OFF is so much easier than it was less than a year ago it seems.
RUU isn't finding my phone on this PC; even HTC Sync manager isn't finding the phone, I've tried every driver I can find. I guess I'll try on my laptop; if it's not 1 thing, it's another.
metroins said:
That's the plan stan...but after I get a working RUU. S-OFF is so much easier than it was less than a year ago it seems.
RUU isn't finding my phone on this PC; even HTC Sync manager isn't finding the phone, I've tried every driver I can find. I guess I'll try on my laptop; if it's not 1 thing, it's another.
Click to expand...
Click to collapse
Try rebooting your PC with the phone plugged in it has helped others (I have never tried it though) so go with your gut
or try this http://forum.xda-developers.com/showpost.php?p=40674775&postcount=31
bigdaddy619 said:
Try rebooting your PC with the phone plugged in it has helped others (I have never tried it though) so go with your gut
or try this http://forum.xda-developers.com/showpost.php?p=40674775&postcount=31
Click to expand...
Click to collapse
Finally done at 3am:
Phone is S-Off
Phone is back to basically stock via VipeRUU
Phone is activated
Phone works
Plans for future:
Root tomorrow, not sure if TWRP is gone, if so add TWRP
Possibly switch to another Sense based rom, but close to stock
Maybe switch to Viperrom since I'm S-Off now
Problems ran into switching back with RUU:
All of the ones listed above
Phone was not activated once I was S-Off
Phone had more issues connecting to adb
Fixes to some problems:
Phone activation fixed by using Sense based rom -- probably could've called Sprint Customer Service
Adb drivers worked when I uninstalled, rebooted, and reinstalled using drivers from RUU uploaded by above poster Bigdaddy
http://d-h.st/users/BigDaddy619
Multiple tries for hours and lots of learning
I even tried to use adb through my fiances mac, but it wouldn't recognize adb....I think this was more of an issue with the rom maybe, dunno?!? My phone hadn't been completely updated since October and I think that was a beta
Night Night; thanks for your help sir, if you have any suggestions of stable roms I'm willing to try them out again, I think using a beta rom for so long coupled with no SDcard access taught me to appreciate the minor things such as: Working 4g, Working Wifi, Working Camera, Downloading stuff, No nag screens upon bootup, No random shutoffs etc. etc.
I like fixing things even if it's a hassle, but I think I need some hassle-free time easy to use stableness.
What did you do to fix the SD issue, I'm having the same issue with SD
Sent from my EVO using xda premium