Related
Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Hi, I was going to setup adb on my froyo MT4G, but I didn't...now I am trying to setup fastboot and ADB on my computer, but I can't figure it out. It seems like guides are written for android 2.2 when it comes to the MT4G and ADB. I have cm7 on my phone, so how do I setup ADB for it? I am trying to find it, but I don't know enough to know what would work, have tried certain guides, but once I get to a point where there is a disclaimer I tend to shy away since, I am not sure what guide I should be following for my weird situation and trying to setup adb for it..Please, thank you.
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Hmmm might be awhile before I can try this but I will
jbrew78 said:
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread
Honestly, I think your long term fix is ubuntu. A lot of people don't want to hear that, but it's easier than you think. You can run a dual boot, or set up a virtual machine on your current computer. You can download vmware here:
http://www.vmware.com/products/player/
And ubuntu here:
http://www.ubuntu.com/desktop/get-ubuntu/download
Then install adb, fastboot, etc. and never have any driver issues again. Problem solved.
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Thank you. I am downloading the sdk files right now, I wish I had a computer so I could read more about developing and stuff...right now I just have to use my GFs when im over here, but I have to avoid things once I start getting interested otherwise I will be sucked into an abyss of knowledge for hours, and snap out of it, and then have to figure out why she is mad at me, hahhaha... so I have a generic question though... is fastboot basically like terminal? And you can get into it from hboot right? Don't need to have your computer connected to it or anything right?
foxdl99 said:
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Click to expand...
Click to collapse
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
foxdl99 said:
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
Click to expand...
Click to collapse
Wait so I have to connect my phone to my computer to use fastboot cmds on my phone?
So if I have fastboot setup, and I am walking around with my phone in my pocket and I pull it out and check xda and see a new splash screen I want. I can reboot into bootloader, and then enter fastboot and type some kind of command like.. fastboot splash3 google.img and that will work? Or your saying I have to have it plugged into the computer?...because if that is the case then whats the difference between ADB and fastboot?
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
I have root explorer... hmm I guess I have been missing what fastboot is all about... well maybe ill just get it all setup and play with it to figure it out.. thanks for your help I'm going to sleep for now.
foxdl99 said:
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread
Sorry to ask for help in this thread. But my work gave me a new razor and yesterday. It came preinstalled with jelly bean. I rooted it and installed safestrap. Went through multiple flashes with no problems. Last 1 I tried it got stuck at the fast boot. It says locked 0 battery okay. I've tried every remedy. I believe I have all the files on my computer to revert back I cannot figure out how to get ADB to recognize my command it keeps telling me that file or that system cannot be located maybe I'm working it wrong maybe I have the wrong information I really need to have this fixed by tomorrow morning if anybody can please help me either send me a private message or even call Maine just p.m. me for my number thanks sorry to take this thread hostage.
Sent from my Nexus 4 using xda premium
Well take it easy on you. For future reference, all questions and requests for help go in the q n a section. This section is for posting ROMs, kernel, mods, etc.. only. Anyway, you say that you cannot get your phone to be recognized through adb? Here are number of reasons why that might be.
1. You do not have the proper drivers installed. Install the drivers for this with the proper driver software for this phone.
2. The obvious reason is in order to use adb, your phone has to be booted on. (You can still access adb even if your stuck on boot animation) or have to be in recovery mode.
3. Make sure you have all the files in a folder you need to initiate adb commands: fastboot and a dB for example. You can get all these from downloading the SDK tool kit.
Now I do not know what remedies you have tried to restore it. But the first thing you should've done after you have installed safe strap was make a backup of your original ROM.
If all else fails, you will need to flash the jellybean stock firmware using rsd lite. Which of course requires you to have yih phone recognized by your. PC. Check to make sure it isn't your cord by hooking it up to another computer. Try swapping different cord too.
And moved...
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).