Related
Please be patient with me, I'm new to the entire smartphone era.
I've spent the last week or so scouring these forums deciding what I can and cannot do with my brand new Epic. What I unfortunately was unable to find were directions put into laymans terms as exactly how to properly flash your phone (I am still even unsure as to the correct terminology for many things). When I read the wiki and the forums I'm lost about a paragraph in.
It would be incredibly appreciated if any of you had tips for a new person to these forums and to this lifestyle itself. I'd love to know how to properly modify my phone without breaking it (and not feel like I'm reading a medical dictionary). When/if I do mod my phone, I'd like to know how to go about restoring it should I for whatever reason need to take it in to the extremely... helpful.. Sprint store here in my area. I'm pretty quick to learn and as I said, I'd really love if someone willing to be patient with me would explain to me the ins and outs I would need to know to take advantage of my phones capabilities.
Well most roms now use ext4 filesystem instead of RFS (default) so you have to install Clockwork Mod 3 which will auto convert it
CWM3 directions:
Download Here
On phone go to applications -> development -> usb debugging (turn on)
plug phone into usb port, run the run.bat from the CWM folder (it might say something like restart server and wait for phone to reconnect i generally just close the window and run the run.bat again then it'll mount as r/w and install)
Then after your phone reboots transfer any ec05 ext4 rom to your sdcard, i suggest This one.
After that turn off your phone completely.
Hold volume down, camera button, power. This will boot into clockworkmod.
CWM will backup all data, format, then restore the data... it'll take a few minutes.
Now if you want to start fresh click wipe data / wipe cache and also go to advanced/wipe dalvic cache. If you want to keep all your apps just proceed to the next step
go to Install from sdcard, browse sdcard for the rom.zip, select it, let it do its magic, after its done go back to the main menu, reboot system, and you're done
EDIT: Cwm controls -> volume up/down to naviage, Power = back, Camera = select. I think you can also use the keyboard arrows and stuff but i find it easier using the buttons
I think you should start him with cw2.5 instead of 3.0. 3.0 will brick his phone unless he is ready to flash a rom right alway!!
Those directions are much easier to follow.
What are the negatives to doing this to your phone (besides the ultimate brick)? Would doing this allow me to give my phone the ability to hotspot it?
How would I go about restoring it should I not like Syndicate and wish to return to stock?
OmegaMateria said:
Those directions are much easier to follow.
What are the negatives to doing this to your phone (besides the ultimate brick)? Would doing this allow me to give my phone the ability to hotspot it?
How would I go about restoring it should I not like Syndicate and wish to return to stock?
Click to expand...
Click to collapse
If I was you I wouldn't be in such a rush to flash a rom. Root first and take from there. It took me a whole month to flash a rom before I felt comfortable with the terminology. Catch up on some reading first
hi I also am still new to this even though i flashed my phone at least a 100 times and got my buddys epic rooted i followed this forum http://forum.xda-developers.com/showthread.php?t=798067. they did a great job with links to get cwm2.5 and also the adb files. so when you root your phone the computer will find your phone. One thing that did keep me held up for a while was when you have your phone in debug mode. connect the phone to the usb. but do not press connect on your phone. hope this helps some. I spent about 3 long days reading and gathering everything before trying and like a day and a half trying.
shook187 said:
If I was you I wouldn't be in such a rush to flash a rom. Root first and take from there. It took me a whole month to flash a rom before I felt comfortable with the terminology. Catch up on some reading first
Click to expand...
Click to collapse
You're probably very right.
What permissions does rooting get me? To root my phone I should use clockwork or something different? If so, you suggested 3.0 and someone else 2.5. Opinions on both for a newbie?
shook187 said:
I think you should start him with cw2.5 instead of 3.0. 3.0 will brick his phone unless he is ready to flash a rom right alway!!
Click to expand...
Click to collapse
No such thing will occur. He might get it into a position of where he can only use odin but certainly not a brick. I have heard of only 1 person bricking their phone in 6 mths and that was a dev cuz he was messing with the bootloader. Jump in at your own pace.
Sent from my SPH-D700 using XDA App
OmegaMateria said:
You're probably very right.
What permissions does rooting get me? To root my phone I should use clockwork or something different? If so, you suggested 3.0 and someone else 2.5. Opinions on both for a newbie?
Click to expand...
Click to collapse
I never suggested 3.0, I would do 2.5. 3.0 Requires you to flash a rom cause it won't boot without a rom. If you use 3.0 without flushing a rom, you'll get stuck at the samsung screen.
shook187 said:
I never suggested 3.0, I would do 2.5. 3.0 Requires you to flash a rom cause it won't boot without a rom. If you use 3.0 without flushing a rom, you'll get stuck at the samsung screen.
Click to expand...
Click to collapse
Sorry, my mistake!!
I'll check out 2.5. Anything I should know about rooting in general?
OmegaMateria said:
Sorry, my mistake!!
I'll check out 2.5. Anything I should know about rooting in general?
Click to expand...
Click to collapse
The main thing which you already mention is the free wireless tether.
CWM 2.5.5 = the RFS root method. You can use it to install EC05 roms that have RFS support
It allows you to run programs with superuser... such as wifi tether, wireless tether, titanium backup, root explorer... thats about it for the basic user
If you want tweaks/fixes what you want is a custom rom... most all will have
Call log fix (remove the sms notifications from in your call log), Kernel fixes/updates/added features, deodexed, zipaligned, custom boot animations, voodoo audio/color, custom touchwiz, etc..
You wont brick your phone regardless, but if you do it exactly as i typed you wont have any problems either . The reason you want to put a rom on your sdcard before you boot into CWM3 is so you can flash a compatible rom that has a ext4 kernel...
EDIT: and regarding the negatives, well you wont brick your phone unless say your battery dies as you flash it... The ext4 non-journaled will actually make your phone last longer over the RFS system. The only thing I can think of is the root method removes the Free HD games and Asphalt 5 Demo which the official OTA updates check for when u get them. Doesn't matter though because you can update your rom through CWM anyways lol.
About positives, atleast for me: Longer battery life, faster phone, less annoying bugs, sexy look, custom boot/shutdown, free wifi tether/wired tether, automatic backups set every night at 5am.
I went straight to cwm 3.0.0.6 as a noob but I must have read 1000 posts in various forums regarding root, the file system(s), custom software/ROMs/kernels. The key is read post after post about where others have had issues until you no longer come accross any new issues. Then you know what you are getting into. Just remeber, glitches can occur and during flashing, there are writes that have no error checking and sometimes require a reflash at best and a system restore at worst. It comes with the territory. It is unlikely you will brick your device as long as you are careful to follow insructions, although the reality is (no matter how many times you hear how safe it is) that there is a very very slight chance that a glitch while using software such as odin could send you back to the Sprint store for a new one. Its exceedingly rare, though.
The small risk was worth getting the phone that I wanted originally - instant responsivness, access to every customization and dev. level control of the hardware (free tethering!) - everything runs better - games,browsers,vids (look better and sound better), music sounds better, etc. Etc. There are some seriously talented devs. here. If you decide to take the plunge, check out k0's ACS Frozen ROM and mysteryEmotionz (sp?) Theme(s). When you go from stock to those, you can't help but wonder WTF sprint and samsung are thinking. Yeah, its that good.
Good luck!
Sent from my SPH-D700 using XDA App
blu9987 said:
CWM 2.5.5 = the RFS root method. You can use it to install EC05 roms that have RFS support
It allows you to run programs with superuser... such as wifi tether, wireless tether, titanium backup, root explorer... thats about it for the basic user
If you want tweaks/fixes what you want is a custom rom... most all will have
Call log fix (remove the sms notifications from in your call log), Kernel fixes/updates/added features, deodexed, zipaligned, custom boot animations, voodoo audio/color, custom touchwiz, etc..
You wont brick your phone regardless, but if you do it exactly as i typed you wont have any problems either . The reason you want to put a rom on your sdcard before you boot into CWM3 is so you can flash a compatible rom that has a ext4 kernel...
EDIT: and regarding the negatives, well you wont brick your phone unless say your battery dies as you flash it... The ext4 non-journaled will actually make your phone last longer over the RFS system. The only thing I can think of is the root method removes the Free HD games and Asphalt 5 Demo which the official OTA updates check for when u get them. Doesn't matter though because you can update your rom through CWM anyways lol.
About positives, atleast for me: Longer battery life, faster phone, less annoying bugs, sexy look, custom boot/shutdown, free wifi tether/wired tether, automatic backups set every night at 5am.
Click to expand...
Click to collapse
I went into the run.bat file in the one click root and removed the 2 lines that give the command to delete the free hd games demo and asphalt 5 demo. Ran the one click root, and I still have those 2 installed on my phone. Beats having to reinstall them again in the future and preventing an update because of the missing apps.
Tirregius said:
I went straight to cwm 3.0.0.6 as a noob but I must have read 1000 posts in various forums regarding root, the file system(s), custom software/ROMs/kernels. The key is read post after post about where others have had issues until you no longer come accross any new issues. Then you know what you are getting into. Just remeber, glitches can occur and during flashing, there are writes that have no error checking and sometimes require a reflash at best and a system restore at worst. It comes with the territory. It is unlikely you will brick your device as long as you are careful to follow insructions, although the reality is (no matter how many times you hear how safe it is) that there is a very very slight chance that a glitch while using software such as odin could send you back to the Sprint store for a new one. Its exceedingly rare, though
Click to expand...
Click to collapse
Yeah I've spent the entire week when not at work reading about it to see if it's worth it. I have a hard time following the directions I find though because they're normally written for experienced folks and not beginners.
Apart from Rooting it (as explained very well earlier) I still have no clue about flashing, how it works, or how to do it. Nor do I want to just fiddle around with it and break it. I can't find a good guide on ODIN or backing up that I can understand comfortably enough to risk flashing my phone so I'm kindof at a loss.
Go on YouTube and search "randyshear". He has step by step videos for pretty much everything. Makes it easy
Sent from my SPH-D700 using XDA Premium App
OmegaMateria said:
Yeah I've spent the entire week when not at work reading about it to see if it's worth it. I have a hard time following the directions I find though because they're normally written for experienced folks and not beginners.
Apart from Rooting it (as explained very well earlier) I still have no clue about flashing, how it works, or how to do it. Nor do I want to just fiddle around with it and break it. I can't find a good guide on ODIN or backing up that I can understand comfortably enough to risk flashing my phone so I'm kindof at a loss.
Click to expand...
Click to collapse
I was the same way and to some degree still am. What I did was read and read. I read the WIKI several times realizing that a lot of it was written for someone more experienced than I. I also read how to restore a bricked device and return to stock a few times. I installed everything to return to stock on my PC so if I had a failure I already had my path back to working stock. I went to CM 2 just to get some experience. Then I went for it to CM 3 and Syndicate 1.0 and have been incredibly happy that I did.
Also know that terms like brick are used a lot but is then followed up with my phone will do this or that. In the definitions a brick is literally as good as a brick for a phone. The term is used way too much incorrectly so don't let that scare you. You will see when reading that there are only a few things to do if there is a problem. Frequently you will read to re download the files or use a different cable or USB port. If you keep reading you will become more comfortable with your ability to find the answers if there is a problem because there are people on here that seem to take great joy in helping people like you and I out and they have the experience and knowledge to help.
Trust me ... keep reading and searching and you will start to put the pieces together. Don't be discouraged. If you are really interested in this stuff, you WILL get there.
Sent from my SPH-D700 using XDA App
Definitely agree with JohnCorleone, Randyshear has a ton of very good youtube vids. Helpful with rooting also with picking a ROM. Just to add my two-cents. The "epic cookbook" http://forum.xda-developers.com/showthread.php?t=967014...Helped me over and over again. alot of info, without alot of scavenging throughout threads. Good luck
There is no need to flash a rom right off the bat. Rooting with one click will give you a good jumping point. I would one click root to cw3 let it convert to ext4 then do a backup. Use titanium backup to remove all the junk bloatware.
Sent from my SPH-D700 using XDA App
Just got this phone and I love it but the seller on ebay had it rooted and had one of the roms from here on it. They said they would put it all back to stock for me. I like to start with a clean slate if you know what I mean. Well, it is back on gingerbread but root is still there and a whole bunch of other stuff (apps, roms, titanium backup) etc etc in folders on the internal storage. My question is can I safely get this phone back to being stock just like it was from the factory, without the risk of bricking it? I know how to use Odin for the Epic 4G and all. I knew there were some problems with the touch and some phones getting bricked. I have no clue what they may have done to the phone so I am a bit concerned to do anything to it till I hear from someone who has done this (gone completely back to stock) Also, is there a tutorial somewhere?? Thanks guys for your help with this.
Oh here is some more info if it helps looks like I am on Android version 2.3.6, EL29, kernel 2.6.35.7 there is some other info if you need it please let me know I do see a Caulklin's folder in there in the internal storage so most likely they did have that rom on there at one time. There is also a ACS folder in there but when I try to open any of the folders in there I get an error that there is no program that can perform this action. Grrrrrr
Hi.
When messing with Gingerbread, especially stock, bricks are pretty hard to come by nowadays.
Here is what I suggest:
http://forum.xda-developers.com/showthread.php?t=1433101
(from what you said, you probably understand this already)
Just run the EL29 OC. You'll be good to go.
In terms of the internal storage, just delete it all or run a format. You won't get yourself in trouble that way, it's just the internal storage.
If you're concerned about the data wipe brick, that is only on ICS. So since you're on GB, it is not a problem (and totally unrelated to clearing internal storage.)
Post back if you have any questions or anythin'.
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Thanks guys. The phone at one time was on an ICS rom and yes I can search for it. I just wanted to make sure before I did, that this could be done. So, I will see about finding the tutorial and how to go about getting the phone all back to factory like. I know I am so anal this way, but I really do like to start with a clean slate before I do anything to any phone. thanks again guys I will holler if I run into any problems. LOVE this phone though.
thewadegeek said:
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Click to expand...
Click to collapse
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
It didn't for whatever reason. I had to go in and edit the MIN and MDN manually to get it to activate so maybe that is why. That thing was a HUGE pain to do too. It would not take and kept resetting. Had to try it like 5 times.
Esoteric68 said:
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
Click to expand...
Click to collapse
If you are stuck with what to do next then take it to a Sprint store and let them wipe it for you.
Good info
As I'm going to try this and hopefully get the missus off her Opt S and onto an E4GT this week this was good timing to cover the process.
Here's what I am planning to do:
1) Flash EL29 + Root
2) Factory Reset from Recovery (which should clear NVRAM if I understand correctly)
3) Call MVNO and have them set up phone
4) Allow hands-free activation to hopefully fill in the blanks
If this works as I hope then I shouldn't have to tinker manually with the NVRAM data.... if not then I have my phone to base most of that off of. And of course it depends if the carrier will let me set the phone up - in the past they haven't been warm to using a different phone unless you purchased it directly from them.
All this just to sit tight until we can get the GS3 probably next year.. yeesh.
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.
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
Hello XDA forum patrons, if I am out of terms for stating that I will pay for help, I apologize as I am just that desperate for concrete help and or affirmation of being screwed. I am not a new person to this forum but I made this account specifically for this problem. If I have offended anyone to this point I apologize. So if I am allowed to offer monetized reward for real results then please allow me to continue and hear my plight.
I have an AT&T Galaxy Note 2 Model - SGH-i317, while I have successfully and easily rooted and flashed custom roms for over 10 different phones, this one has ultimately made me a fool either in personal error or erroneous rom damage. So in that allow me to explain what I have done and maybe, hopefully, someone reading this can help me get my phone in a usable state as the stress of my girlfriend ( it's her phone ) is slowly killing me and this is consuming every waking hour trying to fix. #firstworldproblems
I digress.. lets jump in.
5 Days ago after realizing that the new rolled out 4.4.2 update disabled tethering and hotspot creation from 3rd party apps such as Foxfi, ( i live in an area where the only options for internet is cellular, dial-up, satellite) I became enraged and decided to root and install a rom for it so I could bypass and circumvent what I felt was crap, and or my impatience to wait for FoxFi to be updated to bypass these changes. So I backed up my rom, installed CWM and supersu 2.1 with no problems, I then installed LiquidSmooth Rom 4.4.4. with no problems everything worked fine, well almost. Silly me I had forgotten to take in account that LiquidSmooth was a very fast, clean android experience without any hint of touchwiz and pen usage.. well I hadn't really cared nor wanted those features but my girlfriend damn sure did. "How am I to take quick pen notes now?
etc... so I decided to switch to DN3 V5.2, well CWM wouldn't allow me to install so I tried Philz to no avail, so I installed TWRP and sure enough it flashed and installed fine. Well there was the problem (at least I am guessing) as DN3 V5.2 is based on 4.4.2, so as much I know with roms is you can go up but never go back... if I am wrong please correct me, So after booting up, my sim card was not being read, so I was like WTF? Turns out I installed the rom for n7100, instead of for n7105/sgh-i317... doh, so I thought well that's no big deal, I will just go ahead and flash the correct one, well I did same problem... so then I got panicked and plugged my phone up to my computer, my internal storage was cleaned out, my titanium backup folder with all my progs and other useful things was removed.. so yah, I think my .efs got wiped. I have never up till this point had this type of problem so never have backed up an efs exclusively, I have always made rom backups but never efs. I guess that is my folly as well, so here is my question am I borked or does someone know what to do here?
Things I have tried:
1.wipe/format/dalvik try to reinstall Liquid smooth to no avail TWRP says failed.
2. Restore rom, TWRP doesn't find the file, I guess it doesn't recognize backups from CWM? that are not made in TWRP? so tried Philz, Philz says "Error while restoring /system!", so I reinstalled CWM and CWM installed it, however after getting to the AT&T splash logo the phone stays there in bootloop.
3. tried different things utilizing steps 1 and 2 with liquid smooth
3. From there reinstalled DN3 5.2 successfully, still no service or data.. and that is the last step I have taken.
My questions are as follows:
1. Does a back up typically save .efs data or is that gone for good?
2. Is there a recovery or a prog that can allow the phone's internal memory to be read like a flash drive or a standard drive on a pc so that I can possibly try to use data recovery software to try to find useful files?
3. Can I get a set of efs backup files from this phone from someone else and perhaps edit the file and enter my IMEI information through notepad or another program?
4. Can a stock rom recovery install what I need?
5. If no to the previous 4 is there any online services or companies that could possibly fix this?
6. or am I completely f***ed?
Please if you have no constructive criticism, thoughts, things to try, or have had any experience in dealing with this issue please move on, I have kicked the **** out of myself enough to bypass trolling.. for all those who want to genuinely help and have some understanding of what I am asking/have done, please help and I will do what I can to reward you in turn. THank you so much to any and all! -j
I'm going off the top of my head so bear with me...
In the case of the Note 2, you cannot downgrade bootloaders. The rest works, aside from some Wi-Fi issues with the early bootloader recent ROM combo.
1. I think TWRP does; but if your internal SD has been corrupted and you don't have anything to restore from... Corrupt internal SD might warrant flashing with the appropriate .pit file and the (usually strongly advised against) "repartition" box checked.
2. I don't think so, but there's no harm in copying the entire 16GBs of the phone's memory to an image in order to try said recovery. There's a few threads out there with step-by-step instructions. It involves using netcat to forward your dd or cat command's output to the computer, since you (obviously) don't have enough space on the phone.
3. There's NV items backups with the IMEI removed that have been posted, notably for the AWS mod, these are probably your best shot. Take a look at EFS Professional which has a very educative thread as well.
4. I doubt it.
5. Some guys with "boxes" that do SIM unlocks, JTAG repairs and the like might be able to help. Maybe.
There should be other threads about people inadvertently flashing their T889 or N7105s with the wrong ROM, maybe they've got some interesting findings.
For your and your couple's sake, general rule is that you shouldn't tinker with your SO's device. The same holds true for friends and family. Otherwise you'll risk blame for every "tech" problem, from the printer running low on ink to the latest spyware they unconciously install.
Good luck,
Darkshado
Darkshado said:
I'm going off the top of my head so bear with me...
In the case of the Note 2, you cannot downgrade bootloaders. The rest works, aside from some Wi-Fi issues with the early bootloader recent ROM combo.
1. I think TWRP does; but if your internal SD has been corrupted and you don't have anything to restore from... Corrupt internal SD might warrant flashing with the appropriate .pit file and the (usually strongly advised against) "repartition" box checked. What is a pit file? My internal SD is not corrupted it's just wiped.. there are files and folders present, but my originals folders and files that included my Titanium backup files and such are gone.. how do I know if my .efs files are present at all?
2. I don't think so, but there's no harm in copying the entire 16GBs of the phone's memory to an image in order to try said recovery. There's a few threads out there with step-by-step instructions. It involves using netcat to forward your dd or cat command's output to the computer, since you (obviously) don't have enough space on the phone.why do I not have enough space on my phone? i have 30 gigs free between internal and external storage? But copying files to attempt a recovery is not the same thing, data recovery software has to be able to access the device to read the nand in order to recover any files correct?
3. There's NV items backups with the IMEI removed that have been posted, notably for the AWS mod, these are probably your best shot. Take a look at EFS Professional which has a very educative thread as well. WHere can i find these NV items? do you have any links? I have efs professional installed but i am still pretty clueless and I keep getting errors trying to access my device.
4. I doubt it.
5. Some guys with "boxes" that do SIM unlocks, JTAG repairs and the like might be able to help. Maybe.
Do you know of any websites or links? i have been unable to find anything to help.
Click to expand...
Click to collapse
There should be other threads about people inadvertently flashing their T889 or N7105s with the wrong ROM, maybe they've got some interesting findings.
For your and your couple's sake, general rule is that you shouldn't tinker with your SO's device. The same holds true for friends and family. Otherwise you'll risk blame for every "tech" problem, from the printer running low on ink to the latest spyware they unconciously install.
Trust me I know, but she said it was okay plus I have never ran into any problems like this before ever, I do all those little pc repair tasks for all my family because I did just that.
Good luck,
Darkshado
Click to expand...
Click to collapse
THanks for your help, I will paypal for any positive results I swear it!
Generally a wrong rom means a trip to the JTAG guy at www.mobiletechvideos.com and you pay $50 and wait a week.
rangercaptain said:
Generally a wrong rom means a trip to the JTAG guy at www.mobiletechvideos.com and you pay $50 and wait a week.
Click to expand...
Click to collapse
This...^^^^^...
And data recovery is also possible...along with EFS RESTORE services...
I used them for a bootloader downgrade service last month...
Josh can fix you up....g
We gave you your solution --- pay up!
No longer desperate for help.
Well, unfortunately for you all, and I should make a thread that states this very thing, that I resolved the issue on my own w/o 3rd party help. Where I had thought it was my efs, it wasn't, it just happened to be my modem was deleted. So from a wi-fi connection and from the DN3 7100 rom I downloaded the appropriate rom for 7105 and a stock recovery to try first, flashed a new version of CWM touch, deleted and wiped everything except int. storage. I then tried the stock rom to successful boot, just still no baseband, no service, no sim recognized, so after thinking and trying a few other things, I thought maybe it was just my modem, sure enough, after flashing the modem UCAMH3, my baseband, connection, and everything came back, after that I rewiped and installed DN3 for 7105 and boom, everything is right with the world. Many thanks for your previous suggestions, but as I did not use them.. you have my gratitude.
Er, you can't actually delete the modem - it's a binary file that flashes a chip. You can replace the firmware with other firmware. Possibly you flashed a corrupted file.