Related
So I just got my Evo yesterday and have been reading up on it on these forums ever since. I have a few questions that I wasn't able to find very easily by searching, so I apologize if I ask a question thats been answered several times and feel free to tell me to search if its something I should be able to find. I am coming from a palm pre and while it was confusing at first I am starting to get the hang of it.
So rooting. lets you uninstall sprint apps, get an app that lets you wifi teacher, among other things right? that seems like the majority of what I would like to do.
The whole custom rom thing kinda scares me. Can you only do a Nandroid backup once you have root? I assume that will make a backup with the phone rooted? Does that backup all the other things like radio drivers,ect? is there another bootloader or app that I need to make all those back ups?
I feel like I have a good grasp on rooting but are there any good threads on backing stuff up and a comparison of the different features of each custom rom? (I.e one has sense, the other doesn't have 4g, etc)
Thanks for any help and I apologize once again if I am asking obvious and frequently answered questions. (Which I'm sure I am)
--Shadd
wow man. i am impressed. you just got your evo yesterday, and you are already using the term bootloader. the last time i helped a noob, he was asking what a rom was. i will be glad to help you. and i am always open for a pm or an email ([email protected]) if any more help is needed.
ok, so you can only nandroid backup once rooted because you need a custom recovery, which is only achievable by root. there are two main ones out there. clockworkmod and amon ra recovery. clockworkmod is simple, user friendly, informative, and fast. it is also controllable by an app while the phone is booted up (rom mananger). clockworkmod has a few shortcomings, like it doesnt wipe dalvik cache properly and it doesnt fix a common 4g-bricking problem called rsa key loss. then we have amon, which isn't controllable by an app, but is all around better. it is just more reliable, safer, works better, has no bugs, and BACKS UP WIMAX.IMG (WHICH YOU CAN RESTORE TO REVERSE RSA KEY LOSS). this is the smarter choice of recovery.
these are very un-annoying and un-repetitive questions for a new-b to be asking. if you need any help rooting, which has been made difficult by the recent ota, pm or email me.
do not use the one click rooting method unrevoked until they come out with a fix for the newest ota, or you will be sorry.
Hey Guys,
I am at a certain level of expertise with this rooting, rom, etc business, but I need some more fundamental understanding. I have a series of questions that I have looked everywhere for...I feel like the answers are probably quite simple, but somewhere down the line I missed the "android 101" class or something.
What I know how to do:
1. I have rooted my Evo 4g with unrevoked, and verified that S-off is there, etc.
2. I have installed Rom Manager, and "flashed" cyanogenmod and MIUI using it
3. I have booted my phone into Clockworkmod's recovery, and tried to "flash" some other types of files (like radios, wimax, etc), without success...but at least I know how to get into the recovery? lol
What I need to know how to do:
1. I don't understand how "flashing" works at all. I know how to do it when it comes to a Rom, and I can use Rom manager. But I don't know how to flash smaller things, like the radios found in this thread, for instance. http://forum.xda-developers.com/showthread.php?t=715485 As far as I knew, "flashing" was only for roms, and I always thought that every time you "flashed" something, you were wiping everything else out.
2. I don't understand how to load different kernels onto my phone.
3. I don't understand how to get different boot animations onto my phone. I think that once I understand how to "flash" things, I will also understand how to do this.
4. I don't know whether I need or want the newest version of Hboot....do I?
I really appreciate all your help, guys. AS of right now, I have a beautiful EVO, with a wonderful MIUI theme all loaded up, but it doesn't work that well - needs upgraded radios, etc. I'd appreciate the help
Thanks!!!!!
There's a Q&A forum for a reason.
thenimboo said:
Hey Guys,
I am at a certain level of expertise with this rooting, rom, etc business, but I need some more fundamental understanding. I have a series of questions that I have looked everywhere for...I feel like the answers are probably quite simple, but somewhere down the line I missed the "android 101" class or something.
What I know how to do:
1. I have rooted my Evo 4g with unrevoked, and verified that S-off is there, etc.
2. I have installed Rom Manager, and "flashed" cyanogenmod and MIUI using it
3. I have booted my phone into Clockworkmod's recovery, and tried to "flash" some other types of files (like radios, wimax, etc), without success...but at least I know how to get into the recovery? lol
What I need to know how to do:
1. I don't understand how "flashing" works at all. I know how to do it when it comes to a Rom, and I can use Rom manager. But I don't know how to flash smaller things, like the radios found in this thread, for instance. http://forum.xda-developers.com/showthread.php?t=715485 As far as I knew, "flashing" was only for roms, and I always thought that every time you "flashed" something, you were wiping everything else out.
2. I don't understand how to load different kernels onto my phone.
3. I don't understand how to get different boot animations onto my phone. I think that once I understand how to "flash" things, I will also understand how to do this.
I really appreciate all your help, guys. AS of right now, I have a beautiful EVO, with a wonderful MIUI theme all loaded up, but it doesn't work that well - needs upgraded radios, etc. I'd appreciate the help
Thanks!!!!!
Click to expand...
Click to collapse
1. You flash it just like you would a ROM. The area where this information is stored is just like the area where the ROM is stored, albeit separate.
2. Kernels are the same. You flash it like a ROM and it replaces the kernel that is stored in the "kernel area" of the phone.
3. Consult this area: http://forum.xda-developers.com/forumdisplay.php?f=655
Nice write up just failed by dropping it here
from my phone duh
Stay away from flashing radio ext if you don't no what your doing u could brick your phone. And flash RA recovery it works beter
Sent from my PC36100 using XDA App
Nice write up on issue mate, but I've moved thread to correct forum
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
First...... Wrong subforum. Try Q and A.
Second, in all your rom flashing, did you maybe forget to wipe, and re-wipe before your rom install?
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Happened to me when trying to root my brothers Evo. (Already had mine rooted). I thought the phone was bricked because there was no recovery installed and all that worked was hboot. I tried several different versions of PC36IMG.zip until 1 finally worked.
Cheers
Yes! try updating with PCM36IMG.zip ROm that should help you out, ex "Sprint lovers". Good luck.
sidiasus said:
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Click to expand...
Click to collapse
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Mikedick said:
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Click to expand...
Click to collapse
No problem, I tried to write in a more humorous style than the other "HALP" threads, and my ability to clearly relate the important details suffered. Thanks for the good wishes!
Etiquette question: I've duplicated this thread in Q & A, should I just delete this one?
Also, thanks to all for the lightning fast responses, trying more PC36IMG'ses.
Nah, just let it die.
Found like you're radio fried, it's a well known defect on some evos and incredibles. Try to put it in the fridge while turned off and afterward it may run for long enough to turn s-on.
Sent from my PC36100 using XDA App
So i was getting rather bored with my Rom and i wanted to get a new one, so i was looking up new Roms and me being a amateur and these things i thought i would be pretty ok since i got the first time, and the second time down, 3rd times the charm? i decided to get BakedSnack 1.9, the information is on their site Bakedsnackshack for the Evo, the latest near the top of that download page. This where the info is and i simply followed the instructions but i really wasnt sure about the beginning information about the Wimax and radio updated, since the second link for the radio was broken (if anyone has that i would love it or some advice really) i skipped those two requirements and decided to try, so i backed up my rom (Which totally didnt work) and went ahead and cleared and tried to install, which it did not work just said (bad) and didnt want to go any further, so considering the file was fine, the only thing i did wrong was not have the requirements, i am rooted and have a custom recovery, and now im pretty upset i lost my favorite recover even though i spent 5 minutes recovering that didnt actually work till i decided to recover, was wondering if anyone can help me get this going to actually work since i have nothing really much to lose, and if someone can get me going on this Baked Snack Rom, id really appreciate it and may thousands of dollars rain on the head of that special person to give advice, i eagerly await a answer
Be careful flashing radios. you can very easily lose your wimax keys and therefore never again be able to use 4g. With that being said.. What recovery are you using? Clockworkmod or Amon Ra? If you used Clockworkmod you'll need to go to Backup/restore... Choose the folder you see next then highlight the last one and select restore.If you can see your sdcard.. it should be in a folder called Clockworkmod\Backup\Yourbackup... Your trying to get to the last folder "yourbackup". Once that's selected choose restore.
It'll help us alot more knowing if you can see that folder and also what recovery your actually running. So you might have to reinstall all your programs.. no biggie.. it's a learning experience and it will only make you wiser next time. Bakedsnack is an older rom though if I remember correctly. Might wanna find something more current.. Synergy, Kingsrom Alliance,MikG are examples of 3.0 sense based roms that are on the cutting edge. Kingsrom, Koni's Elite Series III, Myn's,Mikfroyo are all great Froyo based roms. I have no experience with Bakedsnack but I'm sure it is good as well.
I think the first warning light would have been when your backup failed.
To me, that means, do not proceed until I can do a good back-up.
If you're not using Amon, Ra, I suggest you switch to it.
CWM just has some flaws, and AR is just better.
***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it. Also, I would recommend this be posted in the dev section as this is where people go to install ROMs, not the QA section. People go to QA after they have an issue. This is meant to be preventative, not a fix for an already broken device.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers
posting a link to youtube would be an awesome way to show us noobs how to Exactly go about it also..when i had my captivate i flashed a rom called cognition,super easy following the guy on the video
What about other ROM's?
Can you show us how to flash ROM's from another carrier such as AT&T? There are a couple of ROM's I am really interested in trying out but have no luck doing so because of me not knowing what the heck I'm doing or how to do it. If you could post instructions that would be really nice.
Since I'm already rooted I can't make a video on how to root but ill make a how to flash a rom once you're rooted for the note 2 if you guys are interested
Interesting!
Next time I flash a ROM, I will wipe thrice, as you say.
But do you know why it is important to wipe thrice? Does the extra two times really do something additional to scrub the disc?
I am truly interested, and I would like more insight on *why*
Also, the dev for the Jedi ROM suggests fixing permissions after the first boot.
In my experience, this has led to better performance on other devices in addition to the GNII - perhaps that is also worth mentioning.
techn0crat said:
Interesting!
Next time I flash a ROM, I will wipe thrice, as you say.
But do you know why it is important to wipe thrice? Does the extra two times really do something additional to scrub the disc?
I am truly interested, and I would like more insight on *why*
Also, the dev for the Jedi ROM suggests fixing permissions after the first boot.
In my experience, this has led to better performance on other devices in addition to the GNII - perhaps that is also worth mentioning.
Click to expand...
Click to collapse
There has been debates forever about the wiping more than once theory. I have always done this out of habit. You could compare it rinsing a dish in the sink that has some food on it... you wash it once really quick... you see nothing on the dish... you throw it in the cabinet. Later you see some small smudging on it and end up cleaning it again. Same idea. Just being thorough. As I said in the OP I have always done it this way simply to be thorough. And I have never once been the rogue user with an isolated issue.
To answer your q about permissions, if the ROM dev suggests that for his ROM, do it. It is not always required. But if instructed to do so, it should be done.
Is there a reason why it suggests to wipe three times?
I think it may go back to floppy disk days, or hard disks possibly leaving "footprints" on it, old images or data but im not sure. Just a theory.
G●Note~2 {Jedi X5}
Yes please add a section to the OP about flashing roms from other carriers. The steps are identical, except you flash a modem. We onky have the one availabke now so its very easy. Keep in mind n7100 roms will not work, and n7105 roms need minor porting. But you can take any rom from the us variants and flash it. Reboot, let it sit a bit, etc, flash modem. Its very easy and the att forum seems to be getting more love anyway
Sent from my SGH-T889 using Tapatalk 2
I don't promote people flashing ROMs that are not built for that specific device so I will not do it. Sorry.
krayzielilsmoki said:
Since I'm already rooted I can't make a video on how to root but ill make a how to flash a rom once you're rooted for the note 2 if you guys are interested
Click to expand...
Click to collapse
you could unroot and then do a step by step vid. this guy is so good at explaining it,for example,,http://www.youtube.com/watch?v=MsafJ-9uRqk yeah i know its for the captivate,but i didnt know anything at all about rooting and flashing . i just followed him and iwas a happy man after being stuck on eclair cause at$t was so slow to update,,,any how just an idea,seems like alot of work but i think it would kill off many questions,i know i ask enough now as it is..lol
cobraboy85 said:
I don't promote people flashing ROMs that are not built for that specific device so I will not do it. Sorry.
Click to expand...
Click to collapse
I have to agree with this. If you need flashing instructions, flashing ROMs meant for other devices is probably not the best idea at this point.
G●Note~2 {Jedi X5}
This is great advice about the MD5 verification. Everyone should check before flashing, it will ensure you have a good download with 100% confidence. If the MD5 doesn't match, don't flash it! And if a developer doesn't provide an MD5 with each download, ask them to.
However, wiping three times (or any other number of times except one) is nonsense. Would you format a USB thumb drive 3 times? An external hard drive? Android partitions are no different.
If it makes you feel better to wipe multiple times, go ahead, it won't hurt anything. You're just wasting time.
^kind of agree with you there. I would ask anybody here why they wipe dalvik cache when flashing a kernel then, considering the /data/dalvik-cache/ partition is nothing more than dex opted files of all your apks. I will also say that recently I have gotten in the habit of never wiping dalvik when flashing a kernel and it has not made a single difference in stability.
... point I am trying to make is what you said here, if it makes you feel better, do it lol. Doesn't hurt anything.
Indeed, cache wipes are seldom needed too. In fact, a lot of flashable .zip files have scripts which wipe the appropriate partitions automatically anyway when you install them. I guess old habits die hard...
I would also add that after flashing a ROM and you reboot that ROM, for use, you should wait at least 10 minutes before doing ANYTHING with your phone. That will allow the phone to fully and properly build cache and dalvik cache.. after a flash I let my phone just sit for 20min. Doing this has saved me from lags and bugs.
First I just wanted to say great job to the OP on creating this thread. I also strongly believe that this type of post really should be in the Development section, and you definitely nailed the reasoning for it. I've always considered writing up a thread like this myself, but I never got around to it unfortunately (<--Procrastinator ). There's just a few thing's I'd like to chime in with because I really believe they can help people who are new to the world of rooting. First and foremost (imo) I strongly believe that insecurity plays a huge role in determining whether or not you'll be successful with rooting and Android in general. I completely understand that statement can be applied to almost anything in life, but there's a very good reason why it's especially true when it comes to rooting. It simply boils down to people not wanting to feel (or look) stupid, and it seriously impacts the way a person handles different situations. My advice is to be comfortable with saying "I don't know what I'm doing" and "It's most likely not working correctly because I missed something or I didn't follow the directions exactly". I am not saying that to be ignorant or joking whatsoever, because if you have little to no experience when it comes to this stuff, it's nothing more than the hard truth. It doesn't make you stupid if you don't know how to fly a jumbo jet if you've never done it before, so why would it make you stupid for not knowing how to root a phone if you've never done it before? It doesn't and that's the entire point. If you try flashing a rom and it doesn't boot up or something isn't working correctly, 99.999998 percent of the time it's because you messed something up along the way. Especially when you see tons of posts in the thread like "awesome rom" or "it works great", because it's WAY more likely that you messed something up, versus you happening to have the one messed up phone out of thousands that are working perfectly. That's not saying you're stupid or incapable of doing it, again it's nothing more than the hard truth. It's also not impossible for that to happen either because it has, but it's few and far in between whereas making mistakes or forgetting something is a frequent occurrence for all of us. I can't tell you how many times I've seen people complaining about how something didn't work right, when the vast majority aren't having those issues (or just the known issues). Those types of posts are another example of what you should never do, because in reality you're blaming everybody else since you're apparently incapable of making mistakes. You'll be surprised how many times a problem you're having will turn out to be from forgetting something, even though you were absolutely positive you've done everything correctly. Anyway I really think that accepting the fact that you don't know what you're doing (yet), can make it WAY easier to learn in the long run. One last thing that I'd recommend especially if you're new to this whole rooting world, is to get in the habit of making nand backups (especially before you flash anything) because the 5 minutes it takes to do one can save you hours of frustration. Hope this helps somebody anyway
Paragraphs man. They make reading easier by separating thoughts.
I'm sure what you have to say is insightful but a megablock of text is tough to get through.
Don't sell yourself short by making your posts impossible to ponder.
Hastily spouted for your befuddlement
True in most cases but in our case every lte note two in the world regardless of carrier is identical. the only differences are minor software ones.
Sent from my SGH-T889 using Tapatalk 2
I also think wiping three times is a waste of time. These devices are digital not analog (the plate analogy is much more fitting in the analog world). A wipe is a wipe, doing it more than once seems like voodoo to me .