Related
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
haltemien said:
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
I'm on skype ATM, so if anyone is gentle enough to try an errorsearch with me, call me on my username snorre.andre.nergaard
Click to expand...
Click to collapse
When I reinstalled my SDK i hadnt noticed that ./adb had been moved to a different directory, and the SDK no longer comes with ./fastboot. If you do a quick google search, or a search on XDA, there are forums out there with links and uploaded copies. Actually I'll just put mine up here in a .zip archive. I moved ./adb and ./fastboot back in to my tools folder since it's what I'm used to.
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
haltemien said:
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
Click to expand...
Click to collapse
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
krohnjw said:
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
Click to expand...
Click to collapse
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's fastboot oem unlock
Sent from my Nexus S using xda premium
krohnjw said:
It's fastboot oem unlock
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It doesn't use ADB at all. That may be what you have your local binary named, but it's fastboot. You need to be in the bootloader (where adb cannot work).
Fastboot is the utility used for unlocking the bootloader, flashing/erasing partitions, booting images (such as a kernel or recovery) without installing to the device.
ADB is the Android Debug Bridge.
This is just for clarity here, there's seemingly a lot of confusion.
Thanks for the clarification bud
Sent from my Nexus S 4G using xda premium
kdepro said:
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
Click to expand...
Click to collapse
Yeah. I was in bootloader mode. So then i guess the fastboot "path". that could be the problem then. Ill check it out when i get back from work. Thanks
So I've done quite a bit of searching and testing before coming here to post.
I've searched far and wide as well and I seem to be the only one having an issue.
I had read about the NVFlash. Read up on that, and said ok cool let's do it.
So I obtain the files, but initially I discovered I was having an issue on my Linux box getting fastboot to work. I initially got a "no permissions fastboot" reported from 'fastboot devices' Added the udev rules, and then I started getting "?????????? fastboot"
Decided for times sake, I would skip all that Linux stuff, grab the Universal Naked Driver ( which I had done previously to root/unlock my tf700)
Installed said Universal Naked Driver, booted into fastboot mode, and in Windows I get the same exact error... just displayed differently.
I get "? fastboot"
Any ideas?!?!
Thanks in advance for anything
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Code:
fastboot -i 0x0B05 reboot
(Those are zeroes, not letters. Zero x Zero B Zero 5)
Try that. It should reboot your device just fine. I have also successfully flashed a couple of recovery images and the JB Bootloader using fastboot.
vsTerminus said:
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Code:
fastboot -i 0x0B05 reboot
(Those are zeroes, not letters. Zero x Zero B Zero 5)
Try that. It should reboot your device just fine. I have also successfully flashed a couple of recovery images and the JB Bootloader using fastboot.
Click to expand...
Click to collapse
This explains it perfectly, I didn't want to move forward until I got that to work, but thanks to you i know now it is just fine.
That reboot command worked perfectly thanks!
vsTerminus said:
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Click to expand...
Click to collapse
Thank you. It worked. This device is "crazy". Hopefully we will get CM10 "stable" in a short time.
Just wanted to clear up that [fastboot devices] works just fine. Not sure why it didn't for you, but I've used it successfully a few times.
Sent from my OGparanoid CM D2tmo
Fastboot not working for me
fastboot is not working for my device at all. Neither of the following commands achieves the desired results:
Code:
C:\>fastboot devices
// nothing
C:\>fastboot -i 0x0B05 reboot
< waiting for device >
// stays like this until I cancel the command
I do see the device when I run
Code:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C6OKAS043713 device
To my knowledge, the device drivers were successfully installed. I'm on Windows 7 64-bit, I have the full SDK and all the platform tools installed, and I've used fastboot many times on my HTC Glacier (so it's definitely a working binary). Can anyone help me?
jdkoren said:
fastboot is not working for my device at all. Neither of the following commands achieves the desired results:
Code:
C:\>fastboot devices
// nothing
C:\>fastboot -i 0x0B05 reboot
< waiting for device >
// stays like this until I cancel the command
I do see the device when I run
Code:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C6OKAS043713 device
To my knowledge, the device drivers were successfully installed. I'm on Windows 7 64-bit, I have the full SDK and all the platform tools installed, and I've used fastboot many times on my HTC Glacier (so it's definitely a working binary). Can anyone help me?
Click to expand...
Click to collapse
Did you boot your device to fastboot mode before you execute fastboot command on your PC?
buhohitr said:
Did you boot your device to fastboot mode before you execute fastboot command on your PC?
Click to expand...
Click to collapse
Hmm, it seems to be working now. Odd that fastboot devices doesn't recognize it, but I guess I can continue without it. Thanks.
Hey guys I have given up. Been looking at this for two days now and it will not work. Heres the problem.
I have ran X-factor unlock as per instructions and it ran successfully all the way to the point where it asked did I want to see the identifier token. I hit yes and then the it froze. Let it sit there for like 5 minutes and nothing. So I closed X-factor and open cmd and booted the phone into fastboot. Then I plugged my phone into my computer and ran the fastboot command "fastboot oem get_identifier_token" and I does nothing. I also tried running "fastboot devices" and still notthing. I have reinstalled htc sync manager, pdanet for the drivers, have tried all different version of fastboot and adb and nothing is working. What could I possibly be doing wrong? Pdanet recognizes that the phone is plugged into the pc and the phone recognizes it too but fastboot doesn't. Any help is appreciated.
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
abhipati said:
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
ImagioX1 said:
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
Click to expand...
Click to collapse
Did you install HTC sync
First things first, do you get anything when you do adb devices?
APSBiker said:
First things first, do you get anything when you do adb devices?
Click to expand...
Click to collapse
Yaa, when u plug in your device type "adb devices" in command prompt (from android platform tools folder) did u get any response "[serialNumber] [state]"??
Sent from my HTC One XL using xda premium
abhipati said:
Did you install HTC sync
Click to expand...
Click to collapse
I said in my firt post that I did.
I have tried adb devices and for some reason it works some times and other times I get nothing. I suppose X-Factor is using adb though and the adb part( the two backups and the reboot into fastboot) of X-Factors works all the time. Its only when the phone reboots into fastboot that the rest of the commands don't work with X-factor. Only once did it work and it said it was successfull- i go the 111111111 for my CID. But when I hit enter to view the token X-Factor did nothing.
I have another idea that might work. I was wonder what you guys thought. I have vmware running Mac Os and I was wondering if I could download the Mac tools to my vm and try running the commands that way. Since Mac doesn't doesn't need drivers do you think that would work?
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
ImagioX1 said:
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
Click to expand...
Click to collapse
Awesome! Thanks for updating us on how you got it to work. I guess I was one of the lucky ones that it worked the first time for.
That was a tough fix. Windows still will not recognize my device in adb or fastboot. I don't know what the problem is. But the only catch to running Mac Os in vmware is it is against the EULA so I am not telling you to try that. But It will work. I have been looking at this for 2 days now and I had to go install Mac Os in vmware and register with apple and all that good stuff before I could even start running commands. It was tough but I hope its worth it.
USB debugging
I have a Desire without OS, it can boot into fastboot. Is there any way to know if USB debugging was switched on from here? I tried to unlock the bootloader, im on S-ON, but keep getting errors:
C:\Users\Alienanihilator\Desktop\Roms\HTC Roms\HTC One X\HTC_fastboot_files>fast
boot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Maybe has to do with USB debugging not being turned on before?
You're in the wrong forum, this is the One XL forum. You need to ask in the Desire forum.
Sent from my Evita
Disclaimer: I am not responsible in any way if using anything I've made causes hard bricks,bootloops,alien abductions or any other problems.
Hey guys!
It's been some time that I've been seeing people having problems flashing the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7". So,I decided to create this tool. May I present to you,
Flasher
By SafinWasi
This is a batch file which can flash the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7",complete with ADB and Fast boot executables,stack override,disable auto-recovery update script as well as the 7.2.3 Bootloader downgrade to prevent red screens.
Working features:
Device verification through fastboot.
Flashing Freedom boot and TWRP/CWM Touch/CWM Stock (thanks r3pwn)
Downgrading the Bootloader to 7.2.3
Stack override
Disabling auto-update recovery script
Reboot into TWRP(optional)
Backing up boot,recovery and system partitions.
Restoring previously made backup
Click to expand...
Click to collapse
Steps to use:
Download the zip and extract it.
Read the ReadMe.txt carefully.
Install the Kindle Fire ADB drivers(if needed)
Run Flasher.bat as Administrator.
Follow the on-screen instructions.
Click to expand...
Click to collapse
Changelog:
[01/02/2014]Initial Release
[19/02/2014]Fixed a bug in the backup script
[17/03/2014]Added restore backup option
[24/06/2014]Added support for CWM Touch Advanced Edition and Stock CWM;updated TWRP to 2.7.0.0
Click to expand...
Click to collapse
Download link:
Link 1:flasher-v2-20140624-tate.rar - 31.23 MB
Link 2:flasher-v2-20140624-tate.rar
MD5 Checksum:84313f4b18008f63346853a8666523d5
Click to expand...
Click to collapse
Notes:
This tool is designed to work for Amazon OS version 7.4.6. So,using it on any other software might get you into a bootloop,but the recovery and Freedom-boot will work.Because of this,it is recommended to do the following things before using this tool:
Rooting the device.
Backing up any important data.
Placing the ROM and GApps zips on the sdcard in case you get a bootloop,so that you can just flash those in recovery after doing a complete wipe.
Preparing to lose the Amazon OS
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/Flasher.git
Click to expand...
Click to collapse
Credits go to Hashcode,seokhun,BuQQzz,fattire,very green,r3pwn and anyone else whose work helped me.
Please hit the Thanks button if this tool helped you. Feel free to comment below to suggest any modifications,report any issues or for any help.
Thanks.
XDA:DevDB Information
Flasher, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Anonymous.123, SafinWasi
Version Information
Status: Beta
Beta Release Date: 2014-06-24
Created 2014-03-18
Last Updated 2014-07-01
Reserved
bump
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
GMattZ said:
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
Click to expand...
Click to collapse
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Anonymous.123 said:
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Click to expand...
Click to collapse
I do have all the Fastboot and ADB drivers installed.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
You might want to use this Bin4ry's Root Toolkit to root your Kindle. I've attached the link for you to download.
Root_with_Restore_by_Bin4ry_v33
As for fastboot, adb reboot-bootloader will not work. You'll need to issue this command:
adb shell
su
reboot bootloader
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
Well,you could use the Root with Restore by Bin4ry to root the device. But since you have OS version 7.4.8,you should keep the ROM and GApps zips on the sdcard since using my tool on any OS other than 7.4.6 might get into a bootloop.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
FillTheVoid said:
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
Click to expand...
Click to collapse
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
FillTheVoid said:
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
Click to expand...
Click to collapse
No problem bro.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Bump
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should because it looks like it flashes the same files you would flash were you to do it manually complete with bootloader downgrade. You still want to rot first. Root Many Android v31 for that http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Most probably it will work,but you can never be too careful. Be sure to make a backup by option 2.
Bump
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My tool will boot you into Fastboot. And the preferred (and probably only) root method for 7.4.8 is the Root with restore by Bin4ry v31. LinearEquation answered this question a while ago.
Ty,sorry guess i didnt read back far enough
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi Experts,
I am using a OnePlus One still and its still on Android 6.0.1 (Cyanogen OS 13.1.2-ZNH2KAS3P0-bacon). I am experiencing massive lag and freezing issues with my phone now.
I was wondering if updating to the latest Android via LineageOS 15.1 will help me. If so, how can I get it done without losing my data? I have never ever flashed a ROM before, so this would be my first time.
Can someone point me in the right direction as to what steps I need to take to back up my data, update the OS and then restore the data back?
Thanks,
StillWaters
Hi firstly you will need to download the platform tools from this link https://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip and then you will have to download the adb drivers and go into the settings on your phone and then go to the build number and tap on it 7 times until it says you are a developer and then go back to the main menu of the settings and go into developer options and find android debugging and enable it https://developer.android.com/studio/run/win-usb.html and install the adb drivers from that link and give me a message when you have done that
Fist get the phone rooted. This is a simple tool i've used : https://www.youtube.com/watch?v=HeUYE5gStFA
Then learn how to install custom rom : https://www.youtube.com/watch?v=fi66wJZrdEg
This post shall be very useful since you're a newbie :https://forum.xda-developers.com/showpost.php?p=70918008&postcount=3333
Just a word of advice, i'd recommend you use nougat since that's nearly without any bugs while oreo is relatively new and some roms have bugs. all the best !
Also keen to see an answer
If anyone has managed to do this with a linux PC I'd love to know?
I'm having trouble trying to root my OnePlusOne (CM13). From a bunch of googling I understand you need to roll back to CM12 before you can root the phone. But damned if i can get any of that to work.
I can put the phone in fastboot either with the volume/power button reset or with "adb reboot bootloader".
"adb devices" returns the device info if the phone is up. but if it's in fastboot mode, reports no device?
"fastboot oem unlock" give a < waiting for device > that never ends..
"adb reboot bootloader" gives "error: device not found"
Have you done this and have any advice? Google is sick of the sight of me.
Hi you cannot do it on Linux
NoisyAndrew said:
If anyone has managed to do this with a linux PC I'd love to know?
I'm having trouble trying to root my OnePlusOne (CM13). From a bunch of googling I understand you need to roll back to CM12 before you can root the phone. But damned if i can get any of that to work.
I can put the phone in fastboot either with the volume/power button reset or with "adb reboot bootloader".
"adb devices" returns the device info if the phone is up. but if it's in fastboot mode, reports no device?
"fastboot oem unlock" give a < waiting for device > that never ends..
"adb reboot bootloader" gives "error: device not found"
Have you done this and have any advice? Google is sick of the sight of me.
Click to expand...
Click to collapse
Hi
The commands are:
adb devices (to look if device is recognised - should show a number)
adb reboot-bootloader (to get into bootlaoder)
sudo fastboot devices (again to check if device isrecognised)
sudo fastboot oem unlock
sudo fastboot reboot
fastboot flash recovery recovery.img (for flashing twrp and i renamed before twrp into: revovery.img)
search for details : guide - ubuntu & oneplus one: unlock the bootloader .....
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
And make sure you are on latest official firmware....
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
Hi
...
search for details : guide - ubuntu & oneplus one: unlock the bootloader .....
Click to expand...
Click to collapse
Actually that only works with CM11 and CM12. My phone is CM13.1.
But yes that guide was my starting point.. ..and where I realised this was going to be harder then it should be. It seems that when they commercialised Cyanogen, they set tamper bits in the phone and resetting them is a hassle.
I saw a Stackexchange post where someone explains there's tamper bits in the CM13 release that have to be reset from a series of commands see below.
adb root # restart the adbd daemon with root permissions
adb shell # run remote shell interactively
dd bs=1 count=1 skip=1048080 if=/dev/block/platform/msm_sdcc.1/by-name/aboot 2>/dev/null | xxd | cut -c 10- # print the lock bit state (00 - locked, 01 - unlocked)
echo -ne "\x01" | dd bs=1 count=1 seek=1048080 of=/dev/block/platform/msm_sdcc.1/by-name/aboot # set the lock bit to unlocked(01)
dd bs=1 count=1 skip=1048084 if=/dev/block/platform/msm_sdcc.1/by-name/aboot 2>/dev/null | xxd | cut -c 10- # print the tamper bit state (00 - untampered, 01 - tampered)
echo -ne "\x00" | dd bs=1 count=1 seek=1048084 of=/dev/block/platform/msm_sdcc.1/by-name/aboot # set the tamper bit to untampered(00)
But I've tried logging into my phone and running those commands and it just gives me errors on the adb root line..
I also saw someone use adb sideload <file.zip> to downgrade to CM12. But the link to the CM12 image they offered was dead and I cant find an image that does not give errors.
Hi
I have 2 devices both were on latest cyanogen OS 13 (firmware 006-241).
I had no problems at all to unlocking bootloader, twrp and root with linux mint using my mentioned commands.
No idea why it should not work for you.
Could you post what exactly commands you used (as you typed in your post adb reboot bootloader instead of adb reboot-bootloader) just to check for mistyping.
Regards
TriboDoP said:
Hi
I have 2 devices both were on latest cyanogen OS 13 (firmware 006-241).
I had no problems at all to unlocking bootloader, twrp and root with linux mint using my mentioned commands.
No idea why it should not work for you.
Could you post what exactly commands you used (as you typed in your post adb reboot bootloader instead of adb reboot-bootloader) just to check for mistyping.
Regards
Click to expand...
Click to collapse
So here's what I get..
[email protected] ~/Downloads/OnePlusOne $ adb devicesList of devices attached
a6286a60 device
[email protected] ~/Downloads/OnePlusOne $ adb reboot-bootloader
[email protected] ~/Downloads/OnePlusOne $ sudo fastboot devices
[sudo] password for noisy:
a6286a60 fastboot
[email protected] ~/Downloads/OnePlusOne $ sudo fastboot oem unlock...
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected] ~/Downloads/OnePlusOne $ sudo fastboot reboot
rebooting...
finished. total time: 0.054s
[email protected] ~/Downloads/OnePlusOne $ fastboot flash recovery twrp.img
< waiting for device >
And then it just waits. When i watch this done on youtube. There was a response from the phone at the sudo fastboot oem unlock part. My phone does nothing.. In fact it's still sitting there in the terminal saying waiting and it's been probably 10 minutes now.
NoisyAndrew said:
So here's what I get..
[email protected] ~/Downloads/OnePlusOne $ adb devicesList of devices attached
a6286a60device
[email protected] ~/Downloads/OnePlusOne $ adb reboot-bootloader
[email protected] ~/Downloads/OnePlusOne $ sudo fastboot devices
[sudo] password for noisy:
a6286a60fastboot
[email protected] ~/Downloads/OnePlusOne $ sudo fastboot oem unlock...
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected] ~/Downloads/OnePlusOne $ sudo fastboot reboot
rebooting...
finished. total time: 0.054s
[email protected] ~/Downloads/OnePlusOne $ fastboot flash recovery twrp.img
< waiting for device >
And then it just waits. When i watch this done on youtube. There was a response from the phone at the sudo fastboot oem unlock part. My phone does nothing.. In fact it's still sitting there in the terminal saying waiting and it's been probably 10 minutes now.
Click to expand...
Click to collapse
Looks not bad so far.
Maybe try and check again
adb devices
adb reboot-bootloader
sudo fastboot devices
fastboot flash recovery twrp.img
then reboot again
And are you sure the pc knows the path to find and flash recovery? I have twrp in a folder and start with a right mouse-click on the folder to open in terminal for flashing recovery
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
Looks not bad so far.
And are you sure the pc knows the path to find and flash recovery? I have twrp in a folder and start with a right mouse-click on the folder to open in terminal for flashing recovery
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah, I've opened the terminal for the directory the twrp.img (I renamed it because convenience) is in.
when i run the "fastboot flash recovery twrp.img". I just get < waiting for device > and nothing else happens.
I'm pretty sure that what i read about the device having a tamper bit set by Cyanogen when they released their corporate version is the reason now? I saw a post about someone who pulled one of the windows toolkit's source code apart and found the line that cleared the tamper bit then shelled in to the phone some how (which does not seem to work for me) and reset it (which i just realised I've mentioned above). so I may try that path again.
**** those bastards who tried to monetise Cyanogen. I always wondered why the hell Cortana suddenly appeared on my phone after an update some years back..
NoisyAndrew said:
Yeah, I've opened the terminal for the directory the twrp.img (I renamed it because convenience) is in.
when i run the "fastboot flash recovery twrp.img". I just get < waiting for device > and nothing else happens.
I'm pretty sure that what i read about the device having a tamper bit set by Cyanogen when they released their corporate version is the reason now? I saw a post about someone who pulled one of the windows toolkit's source code apart and found the line that cleared the tamper bit then shelled in to the phone some how (which does not seem to work for me) and reset it (which i just realised I've mentioned above). so I may try that path again.
**** those bastards who tried to monetise Cyanogen. I always wondered why the hell Cortana suddenly appeared on my phone after an update some years back..
Click to expand...
Click to collapse
Hi
As i said before it worked twice perfectly for me on cyanogen 13 so i don't really believe there is something wrong with this in terms of unlocking bootloader etc......
"Waiting for device" makes me think your device is not being recognised by your pc.
So i would just do it again as i mentioned in post #10 to be sure you are in bootloader mode and your device is recognised in this mode.
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
Hi
As i said before it worked twice perfectly for me on cyanogen 13 so i don't really believe there is something wrong with this in terms of unlocking bootloader etc......
"Waiting for device" makes me think your device is not being recognised by your pc.
So i would just do it again as i mentioned in post #10 to be sure you are in bootloader mode and your device is recognised in this mode.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
That would make it about 30 times I've tried it.
Is it CM13 you have or COS13? One is the open source version. The other is the corporate version (which is locked).
If you adb shell you can shell into the pone and check the security and debug bits your self.
adb shell getprop
I notice in the list there is drm.service.enabled [true] which may also be a problem?
NoisyAndrew said:
That would make it about 30 times I've tried it.
Is it CM13 you have or COS13? One is the open source version. The other is the corporate version (which is locked).
If you adb shell you can shell into the pone and check the security and debug bits your self.
adb shell getprop
I notice in the list there is drm.service.enabled [true] which may also be a problem?
Click to expand...
Click to collapse
Hi
Yeah i know doing the same thing over an over again drives us crazy.
Both of my devices were on official stock cyanogen 13
(As we know being on cm would mean we are on custom with unlocked bootloader and twrp already)
But i am not on official stock firmware anymore (one is on oreo and the other already on pie).
But again: being on a custom rom already i had to flash twrp again for some reason i can't remember and i had this "waiting for device" - thing. I did: adb devices- adb reboot bootloader - sudo fastboot devices (my device numbet showed up) - then opened my twrp folder right mouseclick and flashed in terminal with fastboot flash recovery twrp.img - then it worked.
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
Hi
Yeah i know doing the same thing over an over again drives us crazy.
Both of my devices were on official stock cyanogen 13
Click to expand...
Click to collapse
So your phones did not have all the Microsoft stuff tucked in them? Like Cortana and that weird browser that sends you off to Bing all the time? I'd not noticed most of this when the last upgrade came though (except Cortana which I uninstalled). But since I've done about 20 factory re-sets in the last few days I'm surprised how much MS stuff there is..
---------- Post added at 12:41 PM ---------- Previous post was at 12:16 PM ----------
Mehh.. I caved in and installed KingRoot. Even that could not do it..
Evidently the OnePlusOne is in the que to be sorted out..
~ shrugs ~
NoisyAndrew said:
So your phones did not have all the Microsoft stuff tucked in them? Like Cortana and that weird browser that sends you off to Bing all the time? I'd not noticed most of this when the last upgrade came though (except Cortana which I uninstalled). But since I've done about 20 factory re-sets in the last few days I'm surprised how much MS stuff there is..
---------- Post added at 12:41 PM ---------- Previous post was at 12:16 PM ----------
Mehh.. I caved in and installed KingRoot. Even that could not do it..
Evidently the OnePlusOne is in the que to be sorted out..
~ shrugs ~
Click to expand...
Click to collapse
Hi
Honestly i have no idea about MS stuff because i bought both devices second hand and didn't waste a minute to flash custom nougat roms followed by oreo and pie.
I never use stock devices as i am sick of bloatware.
It's a pity twrp didn't work for you. Still i believe there is just a tiny little thing that has to be done to solve this - so probably getting rid of oneplus one is a great loss.
Anyway best wishes.
Sent from my [device_name] using XDA-Developers Legacy app
So My girlfriend says "Hey can I try installing it from my Macbook"?
"Sure" I say as i head off to bed.
Evidently the Mac flashing app kicked the COS13 door in and I have a working phone now. She popped Oxygen on it as that's what the OnePlus forums were suggesting.
Thanks to those who offered help.