I've noticed many cookers recommending a hard reset of your Diamond after a new rom install, but yet it didn't seem to be documented anywhere that I could find.
I've added it to the Diamond Wiki for anyone interested:
http://wiki.xda-developers.com/index.php?pagename=Diamond_HardReset
It probably says this in the manual - I wouldn't know.. Like many ppl here, I've never read it.
Anyway.. hope it helps some of you!
Or u can do clearstorage
I think do clearstorage is easier. It does the same thing. u can find this under settings
HaiLe512 said:
I think do clearstorage is easier. It does the same thing. u can find this under settings
Click to expand...
Click to collapse
Does that also remove everything on the 4GB storage drive too? I'm not game to try!!!!
I've never used Clear Storage for the same reason - it seems to imply that it will format your storage card too.
A Hard Reset definitely does NOT format your storage card.
The psShutXP has a hard reset button. It does the same thing do right?
I've always wondered, does NAND memory refer to the 4gb internal memory?
Pressing 'Clear Storage' in the settings will give you 3 options:
1) Clear storage only
2) Format internal storage only
3) Clear storage and format internal storage
The first option is equivalent to hard resetting.
a little confused...
isn't the final step of flashing a new rom an automatic hard reset anyway? It always has been for me. Is the advice to then perform a further hard reset once the 'preparing to use device for first time' screen has disappeared?
No, sometimes ROM flashing made by cookers will not clear every old thing. It's not always and not necessary for a hard-reset afaik.
Only those old methods of ROM flashing via pdocread/write mode requires hard-reset a must.
Regards,
Carty..
hard reset after flash?
some cooks say do....some don't
so i always do it only the the chef states so
The thing is..when do we actually perform the hard reset.
Do we do it 'immediately' after a succesful ROM flash or do we wait until the device fully initialises and load up the TF3D plugin..or in between?
I asked the same Question (When to do the hard reset) in another thread. The consensus seemed to be at the "Tap screen to setup device" screen or whatever it is called - Just prior to doing the screen calibration.
As to whether it is actually required.... there is no real consensus. So I pretty much always do a single hard reset post flash. Working on the basis that there is nothing to lose but possibly a somehting to gain. Anecdotally - I seemingly have fewer post flash issues than some others who have not hard reset. But I am sure there will be plenty of people to tell you that this is BS.
What I find a little hard to cop, is the guys who hard reset 5 or even 10 times post flash in the belief that it will really "clean" up their device. But whatever floats your boat I guess. Like a single hard reset - 50 resets to get the device really "clean" cant do any harm. Why not do it 100 times just to be sure
I am currently running Wildberry and have had no issues with it whatsoever. Could be because I am just lucky or could be because I hard reset. Who knows.
As an aside the 'Clear Storage' applet is missing from Wildberry!
MrDerrickC said:
I've always wondered, does NAND memory refer to the 4gb internal memory?
Click to expand...
Click to collapse
Yes mate it does, and FYI: the 4GB chip is called a moviNAND chip and is made by Samsung. I understand that development of the Diamond was just a little too early to get the 8GB moviNAND which was released to production at the start of 2008. What a spew.
logger said:
I asked the same Question (When to do the hard reset) in another thread. The consensus seemed to be at the "Tap screen to setup device" screen or whatever it is called - Just prior to doing the screen calibration.
As to whether it is actually required.... there is no real consensus. So I pretty much always do a single hard reset post flash. Working on the basis that there is nothing to lose but possibly a somehting to gain. Anecdotally - I seemingly have fewer post flash issues than some others who have not hard reset. But I am sure there will be plenty of people to tell you that this is BS.
What I find a little hard to cop, is the guys who hard reset 5 or even 10 times post flash in the belief that it will really "clean" up their device. But whatever floats your boat I guess. Like a single hard reset - 50 resets to get the device really "clean" cant do any harm. Why not do it 100 times just to be sure
I am currently running Wildberry and have had no issues with it whatsoever. Could be because I am just lucky or could be because I hard reset. Who knows.
As an aside the 'Clear Storage' applet is missing from Wildberry!
Click to expand...
Click to collapse
+1 !!
MrDerrickC said:
I've always wondered, does NAND memory refer to the 4gb internal memory?
Click to expand...
Click to collapse
Well, JFYI, currently no windows mobile is using NOR based media. That leaves NAND flash. NOR is too expensive for the OEMs and manufactures to use in their devices.
Also, the RAM prices for mobile devices have come down a lot. So, it makes less sense to use NOR based flash media
I have never had to re-flash/hard reset swiftblads roms. Never ever. But ive did it with alot of other roms. duttys, panosha (trying his 2.0 now, and its pretty good), swatos and some other roms. I only do it, if i get some lag issues or if it freeze my screen. Normal it will fix the issues.
Unless, its a bug in the rom. But as some says, it doesnt hurt to make a hard-reset.
Thanks Mate !!!
Hard Rest after Flash new ROM,nothing will change..same same ! i guess no need!
and if u do it,u will delete all the programs on Internal Storage !
Related
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
ezsoulja said:
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
Click to expand...
Click to collapse
I am sure I have advised this when you wrote on one of the threads. Try flashing a shipped rom first, it is in my 4shared, doesn't matter if you have AT&T 8525 or not as it works for my jasjam. Flashing too many radios may kill your phone. So ... flash that and then flash the one you want ..
I have not in my time flashing my phone and my customer's phone that a soft reset causes a hard reset after following the doctors instructions
i will try that but what does the regular att rom have that customs dont to stop this from occuring
ezsoulja said:
i will try that but what does the regular att rom have that customs dont to stop this from occuring
Click to expand...
Click to collapse
As I mentioned no issues for me yet touch wood/knock on wood as your part of the world probably accustom to.
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
it has something to do with the big storage/non big storage flashings etc and that shipped rom sorta resets it all to an acceptable state to the phone's brain so to speak .. the doc's never wrong
ezsoulja said:
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
Click to expand...
Click to collapse
In a normal rom, the flash rom is split into two pices, ext rom and storage rom.
In a bigstorage rom, this boundery is removed.
Now, over time, this causes instability in the way windows access and manages the rom, leading to data loss (random hard resets).
Flashing a OEM rom with a OS partition and a Ext rom parition acts as a spring clean on the memmory layout, thus, stability.
As with windows, most things are solved by formating your HDD and starting again, its the same kinda thing!
Great.. Thanks guys, im back to normal now with no hard resetting.
I've read a couple times that after rom upgrade one should hard reset.
What is the and is it really necessary? If yes when should I do it after all settings and customization is finished or immediately after flashing finishes?
Thanks
mosec said:
I've read a couple times that after rom upgrade one should hard reset.
What is the and is it really necessary? If yes when should I do it after all settings and customization is finished or immediately after flashing finishes?
Thanks
Click to expand...
Click to collapse
Hi there.
Well I will point this out, if you don't do it. Your rom (that maybe is bugfree), can contains some strange bugs. And when you ex. say it to a cook, he can't figured out of the problem, because he don't have it
I always do this.
Put diamimg on internal storage.
Flash the phone.
Hard reset it, right after.
Now you phone is ready
I've read lots of comments, these very unwanted random hard-resets are suppose to be a common bug, however the suggested fixes dont seem to work for me, anyone else having the same issue?
Note: The issue must be software related, it only started happening to me immediately after a ROM update a few months back.
What usually happens:
- Install a ROM -> Configure It -> Install Apps... all looks good
- At some random point (could be days or weeks) the phone will lock up (usually on the password screen)
- A soft reset is required to rectify the lock-up
(i.e. the red button on back of phone)
- Phone hard-resets itself
Suggested Solutions:
1) Upgrade to HardSPL 1.93 - made no difference
2) I have tried running MTTY a few times, also no difference
3) Try different ROM's, I thought it might be just a bug with the WWE ROM, but it happens with the Energy ROM too
Just out of interest:
Interestingly, my wifes phone, which I do exactly the same updates on (same phone, same ROM, same Radio, etc), is working completely fine...
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
businello2000 said:
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
Click to expand...
Click to collapse
Hi, thanks for suggestion, although yep I tried that too. There is no stock ROM for an imported phone on Optus, but I just used the stock Telstra one that was on the forums, then after a while went back to the WWE ROM, and the same issue still occurs.
No other ideas for resolving the hard reset issues?
Next time it happens, I might try pulling the battery out instead of using the reset button on the back of the phone.. but clearly something is wrong :-/
i have had this a couple of times, about 6 months ago and last week. i just flashed a different ROM, flashing the same one again didnt help, so just downloaded a different one and went with that.
seems to be ok now
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
matrix77 said:
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
Click to expand...
Click to collapse
Thanks again for suggestions so far, but above fix only lasted about 5 days before another intermittent phone crash & subsequent hard reset, much the same as I have had experimenting with a range of stock and other ROM's :-/
I don't think the fix is as simple as just putting a Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset. Im pretty sure its a software problem, but I dont see how the problem can survive such rigorous formatting...
Is noone else having the problem? Sounds like most are solved with 1 use of MTTY.
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
The only solution is:
1st MTTY and run task 29 to format the device to make it clean and no left over stuff from the last ROM.
2nd Install different ROM
If you have bad sectors in the device, MTTY might not help much here, I guess.
Hi maddie, yes you might be onto something, I assume you already tried the usual fixes: (Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset)? You can tell it to format the NaviNAND during the hard reset.
I think my issue might be different to yours though, as mine does not happen 'when installing software' mine happens days/weeks after setting up the phone.. It usually goes down like this: I pull the phone out of my pocket -> its locked on the password screen usually (cant type) -> pull the battery out or press the soft-reset button -> bang.. phone hard-resets.
I will make 1 suggestion though, instead of using all the nice fancy mods, and SPB Mobile Shell (looks like sense ui), I went back to a boring old stock rom, and well after 1 month its still going.. I absolutely hate it, but I dont want to buy another phone quite yet, so gonna go old-skool.
Let me know how you go, and as above if you did all the standard suggestions? It sounds like you need to somehow instruct the phone not to use those bad memory spots, but ive no idea if such a tool exists im afraid.
maddie said:
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
Click to expand...
Click to collapse
I got the same problem recently and I am still trying different way to solve it.
My Hard-reset happen:
After flashing new rom -> Installation of software ->
-> launching programs -> when some got may holding or loading without response
-> Soft-reset (red bottom) -> It automatically Hard-reset....
Similar thinking with you, I think that maybe one of those reasons leading the hard reset:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
kenleekwanho said:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
Click to expand...
Click to collapse
I like this logic, im in the position of owning 2 HTC Diamonds with identical ROM, Radio, Applications, 1 works perfectly, 1 is resetting.
It 'probably' indicates that its hardware related, I doubt its Radio (due to the other phone working fine), so could be Internal Storage or Bad Sector.
Im not even close to filling up my internal storage though, so if its storage related, perhaps a particular sector is the problem (like maddie was mentioning).
Thanks for all your opinions!
It's the first time for me to think it's the Radio's problem. It comes to me now it seems this situation starts when I flashed the 1.15.25.14 radio. I will try another radio and update here.
I dont 'think' its Radio, but worth a shot.
I cant consistently reproduce my issue, so it could take me a month to find out if ive fixed the issue.. and there are a lot of variables in a month. But sounds like you have a way of reproducing it consistently, gl.
OK, it doesn't seem to work. I think that's it..
Maybe I should start looking at the bootloader commands..
ive got the same issue, but only with some ROMs, for example, the AZTOR X3 and GEN.Y D2 didnt work, but gen.y 1.4 worked for me.
I tried MTTY method to re-flashing, it seems fine to my diamond right now.
i have the same problem, i have tried about 10 different roms, but i don't think it's software related, i think it might be the phone overheating causing a faulty component, it started 2 days ago for me and usually after 5-10 min it crashes, and it started happening when the weather heated up and it will crash quicker if i try to charge it, anyone notice this?
Has anyone found a solution to this?
For me it started when I installed the Gen Y rom with the android dual booter (but not android itself). I have tried MTTY, Stock ROM but Im still experiencing the problem. I suspect it has something to do with the dual boot.
I get the same thing. soft reset = hard reset.
I have tried several ROMs but now the phone hangs on the loading screen
***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 .
hello.. i just flashed the pacman rom for my desire hd.. PACman-v19.3-BLINDNDUMB..
i go to about phone and there i see that Memory is only 594mb.. what does this mean.. the original ram is 768mb.. why has it reduced??
please help!!!!
nor do i have the paranoid settings option in my settings menu.. its getting really weired..
your phone never got to use all 700 whatever. With every phone, due to hardware/phone restrictions you'll never get all of it. E.G. the Note 2, packing 2 whopping gigabytes of ram only gets to use around 1.7 of that. HTC Is a little worse off, its DNA gets only 1.5 usable of the 2 gigabytes.
If you go back to stock, and install a separate task manager you'll see that you probably only get 610-620 (I think htc just shows how much is free, not how much is system accessible). 610-620 because it varies ROM by ROM, however the difference is very minimal, and it shouldn't make a difference. If you're really worried about speed, try out the Supercharger script (google for it). It might look a little intimidating, but youtube will help, the script itself asks you everything in a logical manner, and more importantly, you probably won't be able to screw up- the script just changes values around, at worst you just won't notice a terrible amount of improvements.
I forget where paranoid settings are located, but it's probably there.
Finally, RELAX. If worst comes to worst, and you really screw up, you can just flash the original rom .zip on top, without having to wipe anything (if it gets even worse, you'll just have to backup your apps, wipe everything, and then restore them). Flashing ROMs are extremely safe, so long as you do everything right. Seeing that you successfully a ROM, and you were able to notice how much free ram you had, I would say you're better off than a lot of people.
But just in case, giving a full break down of what you did will allow us to know if you did indeed mess up somewhere along the way.
xxkid123 said:
your phone never got to use all 700 whatever. With every phone, due to hardware/phone restrictions you'll never get all of it. E.G. the Note 2, packing 2 whopping gigabytes of ram only gets to use around 1.7 of that. HTC Is a little worse off, its DNA gets only 1.5 usable of the 2 gigabytes.
If you go back to stock, and install a separate task manager you'll see that you probably only get 610-620 (I think htc just shows how much is free, not how much is system accessible). 610-620 because it varies ROM by ROM, however the difference is very minimal, and it shouldn't make a difference. If you're really worried about speed, try out the Supercharger script (google for it). It might look a little intimidating, but youtube will help, the script itself asks you everything in a logical manner, and more importantly, you probably won't be able to screw up- the script just changes values around, at worst you just won't notice a terrible amount of improvements.
I forget where paranoid settings are located, but it's probably there.
Finally, RELAX. If worst comes to worst, and you really screw up, you can just flash the original rom .zip on top, without having to wipe anything (if it gets even worse, you'll just have to backup your apps, wipe everything, and then restore them). Flashing ROMs are extremely safe, so long as you do everything right. Seeing that you successfully a ROM, and you were able to notice how much free ram you had, I would say you're better off than a lot of people.
But just in case, giving a full break down of what you did will allow us to know if you did indeed mess up somewhere along the way.
Click to expand...
Click to collapse
okay these are the steps i did to flash the rom..
1) boot the phone in recovery mode..
2) 4ext recovery.. so i do a 'wipe data+dalvik'
3)then i do a 'format all partitions(except sd card)..
4) then install zip from sd card..
these are the steps i followed..
i also do not have the gapps in the rom.. in the thread they said it was already there.. how to i change the screen turn off animation.. this rom is totally different from whats in the thread..
rajivkarai said:
okay these are the steps i did to flash the rom..
1) boot the phone in recovery mode..
2) 4ext recovery.. so i do a 'wipe data+dalvik'
3)then i do a 'format all partitions(except sd card)..
4) then install zip from sd card..
these are the steps i followed..
i also do not have the gapps in the rom.. in the thread they said it was already there.. how to i change the screen turn off animation.. this rom is totally different from whats in the thread..
Click to expand...
Click to collapse
You need to flash Gapps, it doesn't mention that it's included in the thread
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Flash it normally, no need to wipe (although wiping cache+dalvik) should help.
for paranoid settings, check this post http://forum.xda-developers.com/showpost.php?p=32720700&postcount=4
Your flashing process was correct, so I don't think anything was wrong there.