Guys/Gals:
I just rooted my Thunderbolt, and I decided the first ROM I was going to get was Adryn's Bloatware remover. I installed the ROM successfully using ROM Manager, relocated the boot.img to the android-sdk/tools folder, and then attempted to run the fastboot flash command, but it always hangs up on "waiting for device."
My drivers are all update (I'm fairly sure), and I'm at my wits end with this now. I've been browsing topics and forums for hours and haven't found out what is wrong. Any help on this "waiting for device" issue? I rooted my phone earlier today, and Root Check says its still good, so what piece of the puzzle and I missing? Thanks.
Related
I'm not new to Android, but I'm new to rooting. I've owned a N1, and now a NS (t-mobile).
I've been intrigued by rooting for months, but have never pulled the trigger...until the ICS ROMS started showing up.
I have searched for a rooting guide, but the forums have a few of them, and they seem to conflict each other. Looking at my "About phone," I'm not even sure what version I have to make sure I'm following the right instructions.
Can someone please share the link to a decent rooting guide for a Nexus S I9020XXKF1 on 2.3.6 Build GRK39F.
Also, am I correct in my understanding that once I'm rooted, I can install ROM manager and find the new cyanogenmod ICS Rom?
Any help is seriously appreciated!!!
shaunmclane said:
I'm not new to Android, but I'm new to rooting. I've owned a N1, and now a NS (t-mobile).
I've been intrigued by rooting for months, but have never pulled the trigger...until the ICS ROMS started showing up.
I have searched for a rooting guide, but the forums have a few of them, and they seem to conflict each other. Looking at my "About phone," I'm not even sure what version I have to make sure I'm following the right instructions.
Can someone please share the link to a decent rooting guide for a Nexus S I9020XXKF1 on 2.3.6 Build GRK39F.
Also, am I correct in my understanding that once I'm rooted, I can install ROM manager and find the new cyanogenmod ICS Rom?
Any help is seriously appreciated!!!
Click to expand...
Click to collapse
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ this is everything u need
JG96EVO said:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ this is everything u need
Click to expand...
Click to collapse
Thanks! Will give it a try now. Still not clear on how to get an ICS ROM on after rooting, but I'll tackle that when I get to it.
Actually, the information is already here in xda.
trying to UNROOT Nexus S
Hello,
I've been trying to unroot my Nexus S and used a guide with video and everything (very helpful)
Now everything has gone smoothly except for the LAST step!!
My phone successfully goes back into Fastboot Mode in the bootloader but when I type "fastboot oem lock" into the command prompt I get the following message:
"'fastboot' is not recognized as an internal or external command, operable program or batch file"
I'm at a loss. I have NO idea where to go from here or what to do. PLEASE HELP!!
AMoR418 said:
Hello,
I've been trying to unroot my Nexus S and used a guide with video and everything (very helpful)
Now everything has gone smoothly except for the LAST step!!
My phone successfully goes back into Fastboot Mode in the bootloader but when I type "fastboot oem lock" into the command prompt I get the following message:
"'fastboot' is not recognized as an internal or external command, operable program or batch file"
I'm at a loss. I have NO idea where to go from here or what to do. PLEASE HELP!!
Click to expand...
Click to collapse
You should really make your own thread rather than hijack someone elses but you need to change the directory in cmd to the folder with fastboot.exe in.
Hi there. I got me a samsung galaxy 550 from virgin mobile canada yesterday, and well, I kinda like it despite being a slow piece of hardware with a 320x240 screen but until I can get enough money to buy something better, I'm fine with this (the phone I had before was a nokia n95, so that's a step up.)
The problem is, I want to try out the official 2.2.1 rom from samsung, and the only way I can do that is to update via odin. actually, that's not the problem, but I want to make a backup of all the apps I've downloaded already, and I just can't get it rooted. at all. z4root, universal androot, superoneclick; they just don't work. the one that was the closest to getting it rooted was superoneclick, and even then it can't finish the job, so I'm stuck with superuser on an unrooted phone, and titanium backup won't work either, so I'm kinda stuck here.
What else could I do?
anyone? please?
6 days later...
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Jason_25 said:
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Click to expand...
Click to collapse
Well, z4root doesn't do anything after it says "running exploit", superoneclick gets stuck on "waiting for device", and the only time it managed to get superuser onto it, it couldn't root the device no matter if I updated it or not; universal androot says "FAILED NO FU GOO", both odin and heimdall fails to connect to the device, and ADB doesn't even see the phone no matter what mode it is. I can't seem to find how to boot into recovery mode (I only ever get instructions to boot into download mode).
ok now in odin I get "cannot open the usb serial port. code: 2". sometimes it's code 5.
Go to madteam.co...dedicated for G5 users,you will get help there at no time
Sent from my blek krupuk
First problem is ADB not seeing the phone. ADB is pretty necessary if you want to debug something. You will need to download LG's Windows driver for your phone if you use Windows. I will include the one I use for my Optimus V here.
On many LG phones it is impossible to boot into recovery or fastboot mode without modification.
Try zergRush from here first:
https://github.com/revolutionary
If not working, try GingerBreak from here:
http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
You may want or need to compile these first which is going to add another level of complexity. Be patient.
The general idea is:
1.setup your drivers
2.get comfortable working with ADB
3.run temporary root
4.immediately flash recovery
5.immediately Nandroid backup everything in several places for safety
6.test Nandroid backup
7.make whatever modifications you like, including permanent root
That's not a lg phone.
Ok so I managed to install cyanogemod and everything's fine. now, I just wanna know, is there any way to enable multitouch on this thing? it's got a capacitive screen, but no multitouch. can that be fixed or is it really just a hardware issue?
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
lexobys said:
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
Click to expand...
Click to collapse
fake dual-touch?
My friend gave me his bricked Xoom, which I accepted as a challenge, because I've been rooting and flashing my phones for years, but after 10+ hours of searching in the last couple weeks, I have been unable to locate coherent information on how to un-brick a Xoom that has had its internal storage wiped. My friend was trying to do a thorough wipe, and he succeeded in that, if nothing else.
My first obstacle was finding a driver, because Motorola Device Manager wants nothing to do with the Xoom, and whenever I finally found a link to a driver, it was at developer.motorola.com, and there apparently is no such domain, because every link takes me straight to motorola.com/us/home, where all that's waiting for me is the bloody Moto Device Manager.
The only post I found that seemed like it was aiming at where I want to get is at http://forum.xda-developers.com/showthread.php?t=2317986, but I ran into problems that weren't foreseen by the author, and I haven't been able to find anything pertinent that doesn't direct me to developer.motorola.com again.
The Xoom has TWRP v.2.6.3.0(runandhide05 edition) for a recovery; and I'm aware that there is a 3.3 version, but I'm nervous about flashing a recovery update when there is no OS on the tablet. It was running EOS 4.2.2 I think, before the bricking.
According to the guide I found, I put TWRP into adb sideload and was able to get my PC to communicate by installing a universal adb driver from https://github.com/koush/UniversalAdbDriver, so in my system Device Manager, the Xoom is listed as a GOOGLE GALAXY NEXUS ADB INTERFACE.
When TWRP is in adb sideload, I can interface with the Xoom via cmd.exe, but when I try to push a ROM, I keep getting an error on TWRP:
Code:
file_getprop:failed to stat "/system/build.prop" no such file or directory
...whatever that means. Another thing that kind of worries me is that when I type adb devices, it shows my device as 1234567890ABCDEF, which doesn't seem right.
I have yet to try fastboot, because I don't know what .img files I need to flash, and I don't think blind flashing is going to make things any better.
I think I have all the pieces, SDK and JDK are installed and updated, and I have the stock rom (HWI69.zip). I reckon if I can get the stock 3.x OS running, I'll have a jumping-off point, and be good to go; the process from there is well-documented.
Can anyone give me a nudge in the right direction, please?
~Fake
Status 7 errors
Those are usually caused by either a not-so-compatible recovery image. Some TWRP versions have issues with certain ROMs. I had this happen to me with my Asus TF300, ended up trying a few different TWRP versions before I found one that worked right.
The other cause is an invalid ROM image, if you open the ROM.zip file on your PC, does it look ok, did you check its MD5sum???
Were you able to wipe the Xoom from TWRP without error???
-Mike
When I got it, it had been wiped completely, so I presume that twrp wiped okay.
Not sure about the MD5sum, just that twrp didn't find one during the adb installation. Do you think flashing cwm might help?.
I got it worked out, opened up the HWI69.zip stock image and fastboot flashed the individual .img files, and it booted right up. Thanks!
Hi all. I'm at my wit's end.
I'm new to Android and am attempting to rid my phone of Verizon bloat apps and want a clean Sense free environment. But my issue is that when I type "adb device" in command prompt, it doesn't show my device.
I have already spent the $25 for Sunshine and s-off'd my M8, and when I type "adb reboot bootloader" it reboots my phone into bootloader. So it's seeing something. In "Device Manager" it comes up as "Android Phone." I think it did that because I tried to do the troubleshooting of manually installing the Google ADB USB driver, but I'm not totally sure.
I have the Android SDK installed.
Ugh... this is headache inducing, and I just want a clean phone
If anyone can give some help, it would be TOTALLY appreciated.
Thanks!
fixed the issue. Instead of using the SDK, I used the website theunlockr and their guide worked perfectly.
Sorry for taking up forum space with my stupidity
pogswarts said:
fixed the issue. Instead of using the SDK, I used the website theunlockr and their guide worked perfectly.
Sorry for taking up forum space with my stupidity
Click to expand...
Click to collapse
You really should be using HTC drivers as well as the HTC version of fastboot. It's better tailored for the use of RUU etc on HTC phones whereas the sdk fastboot will fail.
http://forum.xda-developers.com/showpost.php?p=56890497&postcount=3
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
AndyA2098 said:
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
Click to expand...
Click to collapse
Thread closed as OP fixed his issue