Related
Auto-Hard-Reset after flashin & Hard reset difference.What if to break the first one?
Sorry for creating a new thread for this, but it's very important. Would be perfect if fards and itje answer here. If you guys do not know the answer, please just answer: "I don't know". Just to be sure. Thank you.
fards said:
the argument is that a rom image (that you flash) doesn't always fill the entire memory space so there's a chance that some of the arrays could contain old data as the RUU doesn't clear the space first. It doesn't hurt to hard reset whether this scenario happens or not, just hold the hardkeys down during first boot after it comes out of bootloader ..
Click to expand...
Click to collapse
After flashing, during the first boot, there already IS something that looks like a hard reset. Something like "auto-hard-reset". Therefore allow me to ask you 3 questions please:
1. Is this "auto-hard-reset" similar to the manual hard reset(when we push simultaneously left, right and soft reset key, or via Start>Settings>System>Clear Storage)?
2. What exactly did you mean in your quote(its part that I've marked bold)? I've never heard anything about holding any keys DURING the first boot. Everywhere is written: "Make hard reset AFTER you flash." Or maybe I missed something?
3. What if NOT to wait for this "auto-hard-reset", and just manually, BEFORE it happens, make an HR(pushing simultaneously left, right and soft reset key) in time when firmware splash screen is showed? It would save the time... but is it harmless?
Thank you very much for your answers!
I would actually like to know the same thing...
(BTW, your questions are very well phrased J-pro...I couldn't have asked it better myself.)
EDIT: See the following thread topic...it should answer some questions--http://forum.xda-developers.com/showthread.php?t=490860
i've never seen an auto-hard reset so I don't know where you've got that from. Where does it come up that it's hard resetting, I've never seen anything that it does this automatically?
As discussed in the thread you quoted me from.
Some people believe a hard reset will clear anything left over from a flash that didn't get overwritten in the flashing process.. think about it, if you flash 113mb of new rom into a 256 mb rom space then there's some chance that data will be left behind.
There's enough people who find that hard resetting solves problems, so it does seem to do some good.
All I said that you've quoted me,(why not keep this in that thread, we need to reduce clutter not create more)? EDIT ah I see you did, sorry... A pm asking me to look at the thread would have sufficed
is that after you've finished flashing, if you want to hard reset, then do it then, it doesn't take any extra effort especially if you use the microSD flashing method, where you have to manually reset the device anyway!
"Make hard reset AFTER you flash." is EXACTLY what I've written, make the hard reset after you've flashed, and before it goes through the first (very long) boot up.. Saves repeating that long 1st boot again, it doesn't really matter when you do it, it's just this way saves some time..
HtH
Thank you very much for your answer, fards.
fards said:
i've never seen an auto-hard reset so I don't know where you've got that from. Where does it come up that it's hard resetting, I've never seen anything that it does this automatically?
Click to expand...
Click to collapse
To see it, just wait till the first(after flash) boot ends. You'll see that through this first boot same processes are executed, just as if we do manual hard reset. That's why I named it "automatical-hard-reset". It always happens through the first boot, after flashing.
fards said:
Some people believe a hard reset will clear anything left over from a flash that didn't get overwritten in the flashing process.. think about it, if you flash 113mb of new rom into a 256 mb rom space then there's some chance that data will be left behind.
Click to expand...
Click to collapse
That was clear from the very start, mate
fards said:
A pm asking me to look at the thread would have sufficed
Click to expand...
Click to collapse
I'll remember it
fards said:
is that after you've finished flashing, if you want to hard reset, then do it then, it doesn't take any extra effort especially if you use the microSD flashing method, where you have to manually reset the device anyway!
Click to expand...
Click to collapse
Here is the point. I DO use microSD flash method. And I DO have to manually SOFT reset my phone. BUT while it reboots, my SOFT reset "automatically" turns into a HARD one, JUST because it's the FIRST boot after flashing. I've got such assumption because I saw(on the screen) that same customizing process happens, etc.
fards said:
make the hard reset after you've flashed, and before it goes through the first (very long) boot up..
Click to expand...
Click to collapse
I would ask you, how can I make an HR(HardReset) if I have to make SR(SoftReset) first? BUT this your quote from another thread partially answers the question:
fards said:
HOLD both silver hardware keys down during a reboot.
Click to expand...
Click to collapse
Everywhere is written that a hard reset is: Hold SIMULTANEOUSLY SR-button and both of soft-keys. I've never read about HR as: "Make an SR and hold two soft-keys during booting". It's obviously very different definitions.
So now I can answer: YES, we can make an HR during the first boot after flashing, i.e. we CAN interrupt this first boot(i.e. auto-hard-reset).
But the second part is still not clear for me: is this "first long boot" the same as an HR? Just look at what it does(on the screen) and you'll understand that it's very similar(if not the same). But I just want to have things clear.
Thank you very much!
J-Pro said:
is this "first long boot" the same as an HR?
Click to expand...
Click to collapse
no. It's the same long boot as standard windows when you log on first time... only "finalizing" installation
guap said:
no. It's the same long boot as standard windows when you log on first time... only "finalizing" installation
Click to expand...
Click to collapse
I see. And this "finalizing" happens also after every HR, right? Just to get things clear: "finalizing" is not a part of HR, HR happens BEFORE it. But "finalizing" happens everytime through boot IF there is no preinstalled files found(which are deleted by HR, OR just absent after flashing). Am I right?
rather than "finalizing" think "Initialising" as the system is going through all the initflashes.dat files and provxmls that it does as a first run, as the flags are set in the system that it needs setting up.
but to answer, yes, not so much that there's no preinstalled files found, but that the registry is set as stock that it's the initial boot I think.
Theres no evidence that suggests it's clearing storage area during the initial boot.
if you think about it, if it was "hard resetting" during that process, then after a manually induced hard reset, (either by clear storage or teh two hardkeys) it would go through the process of hard resetting all over again..
Which sounds a bit counter productive..
But you'd need to remotely connect to the device and watch the process to be certain I think. Either way it doesn't hurt to hard-reset after flashing
fards said:
if you think about it, if it was "hard resetting" during that process, then after a manually induced hard reset, (either by clear storage or teh two hardkeys) it would go through the process of hard resetting all over again..
Click to expand...
Click to collapse
Not "over and over", just once again. Then after successful "Initialization" it "sets all flags" to "initialized ROM" and boots normally next time.
fards said:
Which sounds a bit counter productive..
Click to expand...
Click to collapse
Because of misunderstanding of how to make an HR, I didn't know that HR can be done BEFORE(or better to say DURING/AT START) this "first long boot", therefore I always waited till it ends, setting all the parameters, calibrating the screen, etc. and only after that I was making a manual HR. After this manual HR I saw the same things on the screen, did same actions(setting up, calibrating), etc. That was truly counter productive. That's why I asked. Moreover, I think that there are a lot more(than me alone) people, who make HR only AFTER first "long boot" is finished I hope they will see this thread...
But now it's all clear. Thank you for your answers, fards and guap, it really helped!
ADDED: P.S.: You know, guys, after thinking a little, I've got that we can make an HR even when phone is turned off and without using SR-button. If the phone is off, hold down two soft-keys and power the phone on. Nice. That completely proves everything said above.
HRing after Flashing
I always use Micro-SD method when i flash and when it says update success instead of taking out the battery and turning it on, i simply hard reset it from that screen. so i hold the left and right softkeys and then push the soft reset button (this is the only way i can HR, holding L&R softkeys while holding the power button doesn't work for me i have to press the soft reset key as well). this means i don't have to go through the initial long boot screen twice and its a little quicker than taking out the battery and then HRing.
Hope this helps
J-Pro said:
ADDED: P.S.: You know, guys, after thinking a little, I've got that we can make an HR even when phone is turned off and without using SR-button. If the phone is off, hold down two soft-keys and power the phone on. Nice. That completely proves everything said above.
Click to expand...
Click to collapse
yes sometimes I do this.. occassionally if the screen isn't responding on boot (after tweaking and pushing things far too much) & I can still turn off the x1 with the powerbutton and then OK key, then power back on and hardreset..
if you can do it (ie the device is still responding, but not the screen) then it's easier than pulling the back cover off.. Damn this stupid idea of hiding the reset button!
Jonny4911 said:
I always use Micro-SD method when i flash and when it says update success instead of taking out the battery and turning it on, i simply hard reset it from that screen. so i hold the left and right softkeys and then push the soft reset button (this is the only way i can HR, holding L&R softkeys while holding the power button doesn't work for me i have to press the soft reset key as well). this means i don't have to go through the initial long boot screen twice and its a little quicker than taking out the battery and then HRing.
Hope this helps
Click to expand...
Click to collapse
yep thats the way to do it (although you can press the soft reset and then press the two front buttons, as long as you're quick enough).
Hi guys,
My HTC Dream has been lagging beyond belief for the past few weeks, and I was wondering what I could do to increase the speed. I removed a lot of apps I don't use (I have running the latest Cyanogen build, so I don't know if apps2sd will affect my phones performance, but I removed some apps anyway), overclocked my phone, yet still it lags. When I go to SD card & phone storage I see my internal phone storage is only 20.07mb remaining. I see the Factory data reset, but I'm wondering if I should do that. I am hoping it doesn't erase my rom, for example.
.ili.music.ili. said:
Hi guys,
My HTC Dream has been lagging beyond belief for the past few weeks, and I was wondering what I could do to increase the speed. I removed a lot of apps I don't use (I have running the latest Cyanogen build, so I don't know if apps2sd will affect my phones performance, but I removed some apps anyway), overclocked my phone, yet still it lags. When I go to SD card & phone storage I see my internal phone storage is only 20.07mb remaining. I see the Factory data reset, but I'm wondering if I should do that. I am hoping it doesn't erase my rom, for example.
Click to expand...
Click to collapse
This should have been posted in Q&A or the roms thread.
Get CacheMate from the market and clean your system.
Thank you, shadowch31, and sorry. So wipe would not be good why?
.ili.music.ili. said:
Thank you, shadowch31, and sorry. So wipe would not be good why?
Click to expand...
Click to collapse
A factory reset can be a good thing when you understand what your doing with backing up etc. What it does is clear all your settings and setup back to how it looked when you first got the phone. Anything you have done to personalize your phone will be wiped hence hearing people say 'always do a backup!'.
Before you ask about different methods to back up and their practicalities use the search button. You will learn a lot more.
shadowch31 said:
A factory reset can be a good thing when you understand what your doing with backing up etc. What it does is clear all your settings and setup back to how it looked when you first got the phone. Anything you have done to personalize your phone will be wiped hence hearing people say 'always do a backup!'. And you won't lose cyanogen!!!
Before you ask about different methods to back up and there practicalitys use the search button. You will learn a lot more.
Click to expand...
Click to collapse
Fixed it to his biggest worry
Well, thanks, the cachemate worked great.
JAguirre1231 said:
Fixed it to his biggest worry
Click to expand...
Click to collapse
If your going to 'Fix it' at least do it properly.
Capital letter for Cyanogen and really is no need for three explanation marks, it was hardly that earth shattering a statement to warrant it.
shadowch31 said:
If your going to 'Fix it' at least do it properly.
Capital letter for Cyanogen and really is no need for three explanation marks, it was hardly that earth shattering a statement to warrant it.
Click to expand...
Click to collapse
You'd be surprised how earth shattering it is to some people.
JAguirre1231 said:
You'd be surprised how earth shattering it is to some people.
Click to expand...
Click to collapse
You have a point, I'll let that one slide then.
MOD EDIT - Moved to Q&A forum
Hey,
I have been trying to root since the minute the process was let out publicly with no luck, until this morning. I have been through each thread over and over and finally found several things that made it work. After completing the task and going back over everything I tried. I found out the following and I would bet good money it will work for any one.
1. I left my phone plugged in the whole time. No usb cord inserting
2. I had it set to disk mode under pc connection in settings.
3. I used the 2gb card from verizon. Did not erase it. Don't know how it was formatted and don't believe it matters.
4. Made sure the HTC driver was working. This was done by having phone plugged in while in normal operating mode. To verify this once you hear the usb sounds in the command window at the C:/whatever/tools prompt type adb devices. It should come up with a serial number or such.
5. This will sound odd, but several of the methods talk about the screen flicker and not many talk about a sound the phone makes when it loads the sd card. That sound is real and audible if you put the phone to your ear. try it when you turn your phone on. You can hear it. That sound is the key. Try it by starting your phone normally and put it up to your ear. You will hear it.
6. Ok, if your phone is recognized by adb and you can hear the sound you have all you need. Make sure you have the necessay files downloaded to your tools folder.
7. With your phone in normal operating mode, shut it down. You need access to your battery and your sd card so the back needs to be off.
8. Pull the battery and unclick your sd card, hold Vol- and power. The phone will start and try to load the bootloader and leave you at the screen where you can select recovery.
9. Start Loop.bat
10. Press Vol - to select recovery and press power. move the phone close to your ear with your thumbnail on the sd card. When you hear that sound, immediately click in your sd card. The phone will goto the black triangle screen. The phone will then go through it's usb detection and when you hear the connected sound, you will get the error message. This may take 15-30 seconds. It took me 2 tries the first time, but now I have gotten it everytime I have tried since.
11. type in adb devices to verify that your in recovery.
12. Use your favorite method from here. The xda method is the one I used. Everything works fine. Wireless directly to my IPAD.
I think if I made a spread sheet of all the methods, sd cards and timings, we would find out that this is usually the thing that works. You can use the clock method, but I guarantee the right time collates with the cricket sound which collates with the screen flicker.
Anyone else smart that cares to look at this may be able to figure a way to streamline it even more.
Rod
sorry buddy but this old news we all knew about the audible sound, most people tried clicking in the sd card at that point, others tried plugging in usb at that point, buts we all knew about the sound and tried different methods to get it to work. personally i tried your method and it didnt work before i actually rooted. the method i used, envolved a linux live usb flash drive, linux live sd card formatted, and the tail messages, worked everytime the first time, if i missed the first time i had to restart the entire process. atleast now you are rooted
Jesus, everyone has a method that works for "everyone".
Apparently "Search" is broken?
aaronjb said:
Jesus, everyone has a method that works for "everyone".
Click to expand...
Click to collapse
I hear what you're saying, but we shouldn't stifle discussion that could lead to a more reproducible method, either. Maybe this doesn't warrant a new thread, but whatever.
Anyway, I had tried several of the other methods before, maybe 20-30 times, but nothing worked. I tried to time it with the click sound a couple times before, and it didn't work, but I thought I'd give it another try, since OP mentioned he got it to work with the stock 2GB SanDisk card, and that's all I have.
This time, I got it on the second attempt. My reflexes were a little slow, so it was probably more like a half-second after the click sound that I managed to click in the SD card. I haven't attempted to get back yet, so I don't know how repeatable it is.
One thing that may or may not be worth trying for others is that right before I got it, I uninstalled HTC sync, installed the bootloader drivers from the unrevoked site (can't post URL since I'm a noob).
Then uninstalled them (check "delete drivers" when doing so they won't auto-reinstall), reinstalled HTC sync, and finally reinstalled the bootloader drivers. I did the last reinstall because the device wasn't showing up when the phone was in the bootloader menu w/just HTC sync. It's unclear if any of this made a difference, or if I just got lucky with my timing this time.
When I was booting into recovery and pushed in the SD card, very shortly afterwards, I got a balloon in the bottom right that said it was installing the drivers (again? is that expected?). After that, rewt!
Oh lord, if I never saw another one if these threads, I could die a happy man. They're about as useful as alchemy, phrenology, perpetual motion machines, astrology, cold fusion, x-ray specs, etc etc ...
Sent from my Hal90000 using XDA App
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
Because the title is so vague that you don't know it's YARMTISWWFE (Yet Another Root Method That I'm Sure Will Work For Everybody) thread until you read it?
If you couldn't figure out the post content by this time:
I have been trying to root since
Click to expand...
Click to collapse
Then some folks here might want to get tested for some learning disabilities. Don't even have to finish the first sentence to figure out what this thread was about.
To become rooted, do you have wipe your phone and sd card?
No, you definitely do not need to do that.
adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
I wanted to see who was pretentious enough to think that their hare-brained scheme for rooting needed a new post, why they thought their experience could possible impact developing for the Inc, or what could possibly justify tacking "for devs" on the title of their post--as if they succeeded in making a secret club of a thread by doing so.
If he/she really wanted to help devs, they might have PM'd the guys involved with Unrevoked first, or joined their IRC channel, rather than clogging up the forum with another rooting thread. Honestly, there's enough going on now to think of others' purposes here before your "eureka" moment. Too bad I had to bump this thread just to respond.
Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
The sooner we get a reproducible method the better, because that means more folks to test and a wider user base for ROMs. I dont think a developer would spend too much time on a ROM for a device that they do not own and feel only a handful of people would have access to.
Oozura said:
Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
Click to expand...
Click to collapse
You call it mean, I call it strongly discouraging more speculation on a topic that already has a dozen or more threads going. As you can see by the proliferation of more advanced thread recently, most have moved on from trying to root, which common sense would tell one is caused by most having figured it out.
Maybe everyone has figured it out, maybe not. I imagine if you started a thread and asked who was still trying you would get several folks respond that they were. Nothing indicative of the entire population but just saying.
Edit: I just saw your avatar and then your use of such excellent gramar and vocabulary above. Did you make your own lingwo(sp) robot?
This thread has turned into a flame fest against the OP (since pretty much the beginning of it). Thread closed.
Not sure if this is the right forum to post to, so maybe you can point me in the right direction if not.
So I may have gotten some water damage to my phone, it was never submerged, only damp. I did the bag o' rice trick but and having some funny issues with it now. It powered on when charging but continued to turn on and off, flashing the Motorola start-up, and sometimes bringing up the reboot menu as if the power button was being held down.
I disconnected the flex ribbon cable for the power/volume control buttons, and it seemed to actually work. But now it's doing the same thing occasionally after it's been on for a while. Is this savable? Is it possible that if I clear the data cache that it might solve the problem?
cariboukid said:
Not sure if this is the right forum to post to, so maybe you can point me in the right direction if not.
So I may have gotten some water damage to my phone, it was never submerged, only damp. I did the bag o' rice trick but and having some funny issues with it now. It powered on when charging but continued to turn on and off, flashing the Motorola start-up, and sometimes bringing up the reboot menu as if the power button was being held down.
I disconnected the flex ribbon cable for the power/volume control buttons, and it seemed to actually work. But now it's doing the same thing occasionally after it's been on for a while. Is this savable? Is it possible that if I clear the data cache that it might solve the problem?
Click to expand...
Click to collapse
You are in the right place.
Unfortunately, your symptoms are NOT good... (you already know this, obviously). The Moto X is "nano-coated", so you MAY have some hope, yet.
Try a factory reset. If that doesn't work, we can HOPE the issue is data corruption on one or more partitions. At this point, you can TRY flashing the entire stock SBF for your carrier as per the "Return to Stock" thread in the General sub-forum....IF you even can (this is done from bootloader screen - it is NOT required to be unlocked, as the Stock SBF is signed with release-keys). This re-writes ALL the partitions, and often fixes corruption issues.
If you try, and THAT doesn't work, I suspect an un-recoverable hardware failure.
Good Luck :good:
samwathegreat said:
You are in the right place.
Unfortunately, your symptoms are NOT good... (you already know this, obviously). The Moto X is "nano-coated", so you MAY have some hope, yet.
Try a factory reset. If that doesn't work, we can HOPE the issue is data corruption on one or more partitions. At this point, you can TRY flashing the entire stock SBF for your carrier as per the "Return to Stock" thread in the General sub-forum....IF you even can (this is done from bootloader screen - it is NOT required to be unlocked, as the Stock SBF is signed with release-keys). This re-writes ALL the partitions, and often fixes corruption issues.
If you try, and THAT doesn't work, I suspect an un-recoverable hardware failure.
Good Luck :good:
Click to expand...
Click to collapse
Thanks so much!! I created a backup once I was in bootloader. Then I cleared the cache, which didn't seem to help. But then I wiped it clean with fastboot and that seems to have done the trick.
Any advice/suggestions would be MUCH appreciated!
My problem ultimately stems from the fact that my keyboard has somehow been disabled by some errant app, most likely Google's Tap-to-Talk function, a little over a week ago now. Literally out of nowhere. I disabled the general Google App the very day the tap-to-talk function started overriding the HTC Sense keyboard everywhere, and then noticed that neither the keyboard nor the tap-to-talk function were working. I just thought that I could simply restart my phone and any glitch would be removed and my keyboard would return to its normal functioning. I was completely wrong; I haven't been able to use my phone ever since, simply because the keyboard does not come up as usual for me to enter my password, so that since then I've been completely locked out, even though the phone itself is in working order. As far as I know, I don't think that there's any way of overriding the password entry function so that I could simply get into my phone to try to fix the problem that way--but if there is any way, PLEASE LET ME KNOW.
Anyway, I have already chatted with a tech from Google Play, and when I saw that nothing worked out down that avenue, I talked with two different HTC support techs. I explained my problem to the last one and said that I would like to perform a Wipe Cache Partition, but as soon as she found out that my phone is Unlocked with S-ON, she said that there's a 50/50 chance my phone could become bricked from performing the cache wipe. She did say that it's all relative to the case, and for some, everything works out fine, while for others, not so much, so she went ahead and created a ticket for me to speak later with the higher-level HTC Developer techs. I have also already visited an actual tech place only to discover that the 2 guys working there primarily specialize in hardware and are unwilling to try any software-related fixes, because of liability issues and probably also because they just haven't got a clue.
My primary concern is losing all the data still stored on my phone, because it is still in working order, and so I feel like I have much more of a chance of somehow retrieving it NOW than if I were to proceed with the cache wipe, have it brick on me, and then be forced to figure something out with a completely broken phone.
So the main question is whether it really is that risky for me to perform a wipe cache partition, because after researching it all over the Internet, I came to the conclusion that it is a safe procedure that should not damage any personal files or information. Now I have found out that is not the case for unlocked phones, which all those tutorial articles fail to mention.
Please, if anyone knows, PLEASE tell me if it would be safe for me to perform this cache wipe on my unlocked phone. But also, if you just have ANY relevant advice to share on this general matter, please let me know.
I have already perused a pretty large quantity of sources all over the net and am growing increasingly worried at the lack of options to get my phone back into working order for me to actually be able to use it again. I decided to turn to this site's forum as a kind of near-last resort, because I am growing pretty panicked and desperate.
Miserable_Lunatic said:
I talked with two different HTC support techs. I explained my problem to the last one and said that I would like to perform a Wipe Cache Partition, but as soon as she found out that my phone is Unlocked with S-ON, she said that there's a 50/50 chance my phone could become bricked from performing the cache wipe.
Click to expand...
Click to collapse
Wow :laugh:
Wiping the cache partition will only wipe...... the cache partition (/cache) and it will be repopulated at the next reboot. There is no reason why your phone shouldn't boot after clearing the cache. There are always some risk but its far from 50% imo.
My primary concern is losing all the data still stored on my phone
Click to expand...
Click to collapse
You've said that your bootloader is already unlocked right? What about booting in a custom recovery and use ADB to pull all your important files to your computer? Or even better if you have a recent TWRP version, you'll see your phone storage from your computer and you'll be able to simply drag and drop your files to your computer.