Related
Please be nice to me.....I am a newbie, very bold and out of the box and living dangerous with this rooting and ROM flashing. I am addicted but do not know a lot. I am not techno stupid but I get excited and dont think sometimes (was before I took my A.D.D. meds so I was being impulsive) anyhow for some stupid reason I didnt run a nandroid backup. I have a backup but for some reason it wont boot to it. What happened was after flashing 7 the other day, I loved it but market kept force closing all my apps and I couldnt figure it out so I restored back to mod6. was up all night playing around trying to learn all this lingo blingo ROM crudola...........anyhow saw the 7nightly so I flashed it while driving to work (bet yall think im really dumb now) LOL and it boots and gets to the Android screen where it says touch the Android to begin......NOTHING HAPPENS. Rebooted 3 times no worky. So I figure well go back to Mod6 and have a phone until 7 is stable. Cant do that so Im not sure what to do now. I tried flashing a Full Mod6 but to no worky I am at a LOSS. Figured I would ask the experts to please help with ideas. Hugs from Texas girl
Currently backing up my SD card in case I need to.
Have you been wiping in-between flashes? If not:
1. get into recovery
2. wipe everything except battery and rotate stats. Wipe it all again.
3. Flash the Rom of your choice.
4. ???
5. Profit (hopefully)
cm7 nightlys
nicolemiles said:
Please be nice to me.....I am a newbie, very bold and out of the box and living dangerous with this rooting and ROM flashing. I am addicted but do not know a lot. I am not techno stupid but I get excited and dont think sometimes (was before I took my A.D.D. meds so I was being impulsive) anyhow for some stupid reason I didnt run a nandroid backup. I have a backup but for some reason it wont boot to it. What happened was after flashing 7 the other day, I loved it but market kept force closing all my apps and I couldnt figure it out so I restored back to mod6. was up all night playing around trying to learn all this lingo blingo ROM crudola...........anyhow saw the 7nightly so I flashed it while driving to work (bet yall think im really dumb now) LOL and it boots and gets to the Android screen where it says touch the Android to begin......NOTHING HAPPENS. Rebooted 3 times no worky. So I figure well go back to Mod6 and have a phone until 7 is stable. Cant do that so Im not sure what to do now. I tried flashing a Full Mod6 but to no worky I am at a LOSS. Figured I would ask the experts to please help with ideas. Hugs from Texas girl
Currently backing up my SD card in case I need to.
Click to expand...
Click to collapse
Btw cm7 nightlys #7 is working fine I have no issues other than I think I might be having radio issues but that has nothing todo with cm7.
First you have to wipe and partition all data on your phone inrecovery mode. Cache dalve calche and do a full system wipe. Get yourself one of those minisd to sd card adapters to format your sd. Erase all data by formatting the sd the copy and paste your working rom zip back on the sd. Put it back in your fone and reboot into recovery. From there id do one more factory reset just to be sure then flash the zip. You should be good. Sounds to me you flashed to many roms on top of eachother without wiping prior installments.
Omg thanks
Wiping Data was the ticket.......DUH to me! you guys are awesome. Im in and just logged in and setting it up now. EXCITED!
tejasrichard said:
Have you been wiping in-between flashes? If not:
1. get into recovery
2. wipe everything except battery and rotate stats. Wipe it all again.
3. Flash the Rom of your choice.
4. ???
5. Profit (hopefully)
Click to expand...
Click to collapse
Gotta love the underwear gnomes
I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?
I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.
Did you wipe dalvik? And what recovery are you using?
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.
Is it rebooting if you don't use that particular app at all?
Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik
Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.
Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.
I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.
Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots
I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.
You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.
Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you
This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app
Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.
Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.
Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****
RADIO EDIT------
Sent from my PG86100 using xda app-developers app
edited and deleted for the sake of peace
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!
jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...
The fix you used is for samsung devices. That could have caused your problems.