Database Develop

For developers. Root Info. Hope this helps

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.

[Q] LCD BLACK BUT STILL FUNCTIONAL BLIND, MAJOR KEYS still lit up

First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1

Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.

Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!

Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.

stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE

I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.

3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App

[Q] Moto X randomly dies

Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!

quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive

bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help

quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?

When I hit BP Tools it just reboots the phone... I don't know what's wrong???

maybe static electricity?
or do you use any cases?
maybe wrong charger?

Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.

quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm

I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.

Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.

quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.

So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.

HTC ONE M7 affect by heartbleed bug.....

So I have been having a weird error pop up threw out the day saying authorization error occurred and I have to select my Gmail and I guess basically log my phone back in to my Google account, I assume. I search a couple forums on here, (probably not all I should but I have a 3 year old and babysit my one year old God daughter almost daily, so it's hard). But I found something about a heartbleed bug. I download the necessary app to check just because I was curious, I'm running 4.4.4 with Sense 6 So I didn't think it would affect me. And boy was I wrong. I am confused on what this means. I am a straight noob with all this. My device isn't even rooted. Not to mention I keep getting a stupid htc.htcdialer isn't responding and my phone will have a ***** fit turning off and on off and on. Something is wrong with my precious phone. Someone, anyone, help! Can my device be fixed! I love it...

Hello
@ Mrs.Martin0928
Thank you for using XDA Assist
First of all ,your phone is not affected by heartbleed . Google has patched 4.4.4(including Sense 6) for Heartbleed so I don't think your phone has Heartbleed. That must be a false alarm.
The moderation team will move this thread to HTC One Q/A section where you will get better support.
http://forum.xda-developers.com/htc-one/help
Alternatively you can post it in this thread where people usually ask beginner questions
http://forum.xda-developers.com/showthread.php?t=2180425
Have a good day!

Mrs.Martin0928 said:
So I have been having a weird error pop up threw out the day saying authorization error occurred and I have to select my Gmail and I guess basically log my phone back in to my Google account, I assume. I search a couple forums on here, (probably not all I should but I have a 3 year old and babysit my one year old God daughter almost daily, so it's hard). But I found something about a heartbleed bug. I download the necessary app to check just because I was curious, I'm running 4.4.4 with Sense 6 So I didn't think it would affect me. And boy was I wrong. I am confused on what this means. I am a straight noob with all this. My device isn't even rooted. Not to mention I keep getting a stupid htc.htcdialer isn't responding and my phone will have a ***** fit turning off and on off and on. Something is wrong with my precious phone. Someone, anyone, help! Can my device be fixed! I love it...
Click to expand...
Click to collapse
Copy everything from your phones sdcard to your PC
Under settings / backup and restore / backup to HTC Backup
Reboot your phone to the bootloader
Shut Down / Hold volume down + Power till you see the Bootloader screen
choose recovery / wait 5 seconds / hold volume up and tap power till you see the recovery menu
from the menu choose factory reset / when it's done you have to setup your phone like it's new
If everything is working ok, copy your sdcard back to the phone
Restore your phone with HTC Backup

[Problem] Moto G 2nd genscreen issue

Hello, today my Moto G 2 developed an issue, I was sitting on the couch using it, locked it, put it next to me, used my laptop for a few minutes, then when I picked it up to check it, the screen would not turn on. The battery was on about 48% when I put it down. I am running stock Android 5.0.2 and have not ever attempted to root or unlock this particular phone. It has been running 5.0.2 since the day it allowed me to install it via the update section in the settings, and I have not taken part in any soak tests.
I have not posted enough to enable me to post the thread with the video in it, so here's the link: watch/2nlpzj0Wqrc (just paste this in after typing in youtube)
I'm apologize in advance if this issue has been asked about before and fixed, however, all I could find is the issue with it not turning on at all, where it is simply the fact that the battery died and the phone was not plugged in it time.
Yes, I've tried safe mode, same problem arises.

Uh.... Bump...

you have a sw problem, what exactly??? don't know...
do a factory reset, go to config> backup & reset> factory....
remember factory reset erase everything so make a backup of app, files, or wherever you wanna to keep.
yours video...