Guys, I had someone here talk me through rooting my nexus one with froyo and I'm running into some problems but I didn't know if it had something to do with rooting it or not and the reason is, I got it rooted the same day I received it so I hadn't tried those functions before I got it rooted.
I got it rooted so I could buy this program that makes the fonts larger and it required a rooted phone.
Well, today I was going to try to use it as a hot spot or wifi router and when I tried to enable it, it just says error.
Also, when trying to call and talk to people today, they could barely hear me and I had a hard time hearing them (not sure if this was temporary or not because later, although in a different area, it sounded fine).
When trying to reply to some e mail (online email/godaddy) when I clicked where the text/body goes, I could not type anything 'cause the keyboard wouldn't come up. If I clicked in the email or subject areas, the keyboard came up but not in the body text area.
Any ideas?
I guess I could reset it to default settings to see what happens but it took almost two hours to get it rooted so I really would like to avoid that.
Thanks
George
This should be in Q&A!
Not dev related.
To solve your problem:
looks like a bad boot.img for me.
I always had "Activiating Wifi"... "Error" with bad boot.img.
MOD: move to Q&A
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
guiri_too said:
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
Click to expand...
Click to collapse
Im not a Mod, I did not move your thread.
The boot.img is part of a ROM.
But I don't know what ROM you're using, what build (FRF50/72/85B/91) nor the kernel etc.
I cannot tell you more right now.
Just try a new rooter update.zip because yours might have broke your WiFi.
See Cyanogen's or re-flash a pre-rooted rom.
Actually, I noticed it wasn't moved yet but anyway, I think I have the 72 but still, not sure, I'll have to investigate 'cause I like this phone and I would LIKE it to work for me. Especially since I can apparently use it on tmobile and att.
THanks
The hunt continues
George
no rooting in general does not harm your phone or cause problems in any way. however it is possible to mess something up, maybe install something or screw up settings or similar that could cause problems. you can always flash back to factory ROM, or hard reset, to get your phone working again.
even better, since you are rooted, you should be creating nand backups. and anytime something goes wrong, you restore to a working nand backup to a state that you know your phone was working good.
Yeah, now I have to figure out how to do this but thanks for the replies
George
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.
I have 64bit drivers installed, and my phone is in download mode after a disasterous attempt at flashing for the first time. The phone, when not in Download mode, flashes the AT&T logo unplugged, and an empty battery logo with a spinner in the middle.
I've read endlessly on how to proceed with the reflashing steps, but it requires that I move files to the root folder, and it requires that I enable USB Debugging. I can't enable debugging and I can't seem to get my computer to recognize the phone as a disc drive.
I don't know what to do here, but I'm desperate to get my phone back up and running. I know I screwed up, and I don't need to be reminded of things I should have done. I only want constructive advice that will allow me to use my phone again.
Thank you so much in advance for anything that might get me operational.
STOP POSTING SO MANY THREADS ABOUT THE SAME THING!!!!!
wtf
cant you keep your **** organized into one thread!?
Or just shout out things like that.
I'm resolving the topical issue in each thread and announcing it. I thought these were topical threads and that how I worked it out. But hey, thanks. I'll be sure to keep my **** together in the future.
topical..
but when you have a ton of problems that all relate to your DRIVER situation....then, um dont you think it would be best to solve your DRIVER situation? you know, that thing that would solve most of your issues??
everything you have posted about has been about your computer seeing your phone....that would be driver related. once you fix that, your computer will see your phone. its not complicated and doesnt require a different thread started for every step of your driver problem/resolution
Great, so let's keep it on this thread from now on, and stop arguing, shall we? I'm just trying to be progressive. There. I fixed the damned thing anyhow.
I have never had luck with doing any kind of modding to my phones. I was one of the few where the g2x actually worked. In the beginning I hated b/c of restartes but a hard reset for some reason fixed. That is besides the point. I figured a update from the manufacture would be a breeze, and nothing I shouldnt be able to handle. I followed lgs steps to a T and now my phone is stuck on s/w screen. After a google search I see that 100's have the same problem. I hate LG b/c of this, but I will worry about that latter. I need this fixed asap as I am a truck driver and I use my phone everyday for work. I noticed some people took a different direction at installing it by using a file called KDZ. I also saw some mention of needing a driver from forums. I saw a link on lgs site for this also, but their instruction didnt mention anything about needing to download it.
My biggest problem is I need step by step instructions to do this. I have ZERO experiance at this type of thing therefore any missed step with most likly throw me off. So I need this run down to me like your telling it to a kid lol not someone that has done this before and is familiar with steps left out. Mainly things like if I need the KDZ file, how do I download it, what do I do with it after I download it? Do I download it to my phone or computer and then my phone? I need detailed info so I understand how this stuff works please. My phone also is not recognized by the lg update anymore either. I noticed some people were stuck at 4 percent. I actually got to about 50 when it said to remove battery and restart test because of conection issues or something along those lines.. I did as it instructed and here I am lol.
Like I said I need my phone working asap so any help is appreciated. Also if someone tells me to just download this and that and it will fix it, I most likly will be lost. If this need to be unziped after download or little key information like that is left out I will not know to do it.
Thank you for the help and sore for the spelling and punctiation. I am on a old phone.
You should probably try the G2X forum instead of the O2X forum
Ok ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Forgive me if I've posted this thread in the wrong area