Related
I update to FRG83D and I guess i lost root. I attempted to restore flash clock world mod again but .nothing happens when i confirm I tried to do a backup from Titanium backup and of course it says i'm not rooted. Then I tried to go into Superuser app and it asked me to update. I attempted to and I got an error the su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Sorry for the long winded explanation, but i'm totally frustrated. I've been trying to fix this for 2hrs. Oh yeah I originally got root using universal androot and it still says im rooted. I clicked unroot but it doesn't work. I'm confused cuz androot says i'm rooted, but Superuser and Titanium backup says i'm not.
PLEASE HELP MEEE!!! I would like to get back cmod 6.1
was this:
cmod 6.1 rc1-n1
clockmod 2.5.1
kernel: 2.6.35.7
Build num: frg83
Now i'm this:
Android ver: 2.2.1
Kernel ver: 2.6.32.9-27240
Baseband ver: 32.36.00.28U4.06.00.12_7
Build num: FRG83D
fastboot oem unlock
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
crachel said:
fastboot oem unlock
Click to expand...
Click to collapse
lol damn you evil bastards
Have some pity for the newbs
Newbs should start reading Wiki instead of wasting hours on irrelevant stuff
danger-rat said:
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thank you danger-rat. I'm back to stock frg83. It only took about 10mins. Now I'm trying figure out how to get back to root. None of the one click methods seem to be working. Superoneclick, z4root, androot. Once again Thank YOU
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
dls5375 said:
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
Click to expand...
Click to collapse
Is it the case for a Nexus One replacement unit that has never been rooted or altered in any way? I got it with FRG83 and installed FRG83D as soon as I received it. I tried SOC method but it was stuck on 'waiting for device' message. Not sure if it is because of an old XP machine or HTC Evo cable I was using.
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Jack_R1 said:
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Click to expand...
Click to collapse
I tried both SOC 1.5.1 and 1.5.5 with .net 2.0.5x in the XP machine. I just used the files included in the zip, isn't it that it has latest Nexus One drivers too? Sorry, I am a Mac,Linux guy and not much experience with ADB stuff on Windows.
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Jack_R1 said:
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Click to expand...
Click to collapse
Thank you! I guess I have no other option but to install Windows on my Mac. I was feeling lucky and I thought Linux or Mac can use SOC but it is proving difficult and I haven;t come across a single reply who stated success on Linux/Mac!
Uh, why SOC? Use any of the others you just run directly on the phone..
khaytsus said:
Uh, why SOC? Use any of the others you just run directly on the phone..
Click to expand...
Click to collapse
They don't exist for FRG83D just yet and I am not sure if we can downgrade to FRF91 or some other firmware without unlocking bootloader.
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Jack_R1 said:
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Click to expand...
Click to collapse
Is it true for Mac too? My previous attempts with VMWare and Parallels failed while trying to use USB at low level. I guess it is worth a shot, thank you!
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
dls5375 said:
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
Click to expand...
Click to collapse
Tried that already, no go..
kkiran said:
Tried that already, no go..
Click to expand...
Click to collapse
With all the time wasted searching for other methods, you would have had root on your device already if you just did it manually. It is so simple, takes like 20 mins, and it doesn't require a Windows PC.
I really don't understand why people search for so long for a "1-click" when doing it manually doesn't take that much more effort.
Rooting so is simple with the binaries available:
1) Put rageagainstthecage on your device, change permissions to allow it to run, run it, and presto, it gives you a root shell.
2) Now that you have a root shell, all you have to do is put su in the /system/bin directory, change the permissions so that it can run, and presto, you have root.
And given that rageagainstthecage exploits a vulnerability in the way adb works, this method will work for all devices without a NAND lock.
Rageagainstthecage so easy a caveman can do it.
Sent from my Nexus One
So this has been mind breaking for me. I failed to flash the blackrose hboot everytime i trie and on every rom. It gets to the point where it has sent it files and then it says <waiting for device>. This happens on stock, BuglessBeast, rcadsmixhd 2.3 & 1.6 and hypersense (i like sense ). Anyone has any advice . Btw it did not brick it.
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
m0_t3 said:
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
Click to expand...
Click to collapse
Ehm, usb debugging is enabled and detected by the software at first. It gets to the point that it sends its hboot and after that it says something like error: deviceoffline and then stuck on waiting for device forever.
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
m0_t3 said:
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
Click to expand...
Click to collapse
well maybe htc sync but that was closed and its process was killed by taskmanager. No other programs i can think of.
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
m0_t3 said:
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
Click to expand...
Click to collapse
SO without my sd card it did not make any difference, apart from that it now mixes the message: adb server is out of date. Killing... and then waiting for device again.
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
m0_t3 said:
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
Click to expand...
Click to collapse
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
m0_t3 said:
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
Click to expand...
Click to collapse
WOW you are awesome sir thank you now it works i wish you could click the thanks button 30.000 times.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Awesome.
Glad to help ^_^
Sent from my Nexus One using xda premium
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
bassmadrigal said:
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Click to expand...
Click to collapse
It gives me attached device: Ht9 and thencq lot of numbers
Sent from my HTC Nexus One using XDA App
race55 said:
It gives me attached device: Ht9 and thencq lot of numbers
Click to expand...
Click to collapse
Well, that definitely means that your device is recognized. Did you get it working?
bassmadrigal said:
Well, that definitely means that your device is recognized. Did you get it working?
Click to expand...
Click to collapse
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
race55 said:
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
Click to expand...
Click to collapse
If you throw a post at the end stating what you had to do, he would probably update his original post.
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
Click to expand...
Click to collapse
ICS is too big for the stock ROM space on the N1, so you need to make those alterations so it can fit. texasice did make a striped down version that works on stock though.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
If you are like me, you have been flashing ROMS on your phone for years before you ever unlocked the bootloader. I didn't do it until about 6 months ago because I needed to flash Blackrose. Also, don't bite the hand that is trying to feed you.
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again
Sorry but I'm a total rookie here. I first started screwing around with my stock Nexus 6 by rooting. Then somehow I ended up with TWRP installed (or whatever) on my phone. Today I received notification that 5.0.1 OTA was available and when I click install it just went into TWRP and wouldn't let me install the update. For some reason I messed with TWRP and erased everything. Now I'm stuck with a brick.
Oh an to boot I can't get Android SDK running on my computer because of JVM or something.
Can anyone help? I just want to go back to out of the box stock and start over if that's possible. No TWRP or rooting necessary for me after this episode.
Thanks so much in advance for the assistance (please use small words and short sentences). Yes, I've tried searching like crazy and can't find anything that just step by step instructs me how to get back to stock.
ssbmg said:
Sorry but I'm a total rookie here. I first started screwing around with my stock Nexus 6 by rooting. Then somehow I ended up with TWRP installed (or whatever) on my phone. Today I received notification that 5.0.1 OTA was available and when I click install it just went into TWRP and wouldn't let me install the update. For some reason I messed with TWRP and erased everything. Now I'm stuck with a brick.
Oh an to boot I can't get Android SDK running on my computer because of JVM or something.
Can anyone help? I just want to go back to out of the box stock and start over if that's possible. No TWRP or rooting necessary for me after this episode.
Thanks so much in advance for the assistance (please use small words and short sentences). Yes, I've tried searching like crazy and can't find anything that just step by step instructs me how to get back to stock.
Click to expand...
Click to collapse
Try wugfresh's nexus toolkit 2.0.search xda and download to your pc.
Sorry I should've mentioned - I'm on a Mac, not a PC.
Nevermind - fixed by using the one click toolkit in reverse to re-lock bootloader. All good and back to factory.
Mods - delete this useless post if you want.
ssbmg said:
Sorry I should've mentioned - I'm on a Mac, not a PC.
Click to expand...
Click to collapse
This thread show "bail you out..."
For Future reference, having access to a PC when you have an Android phone that you are rooting is somewhat warranted if no one develops the MAC stuff... I have both and although I prefer my MAC, having a PC sometimes is essential. The Thread has links to follow if you are a MAC user.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
:good:
mahst68 said:
This thread show "bail you out..."
For Future reference, having access to a PC when you have an Android phone that you are rooting is somewhat warranted if no one develops the MAC stuff... I have both and although I prefer my MAC, having a PC sometimes is essential. The Thread has links to follow if you are a MAC user.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
:good:
Click to expand...
Click to collapse
Can use fastboot and adb on a mac to either push a rom.zip to recovery and flash or to flash factory images
It's been quite a while since the days of rootif and such for me. I haven't had a windows machine for many years now. I'm still not interested in rooting and roming. But I would like to try the latest update even if it has bugs. Is adb and some instructions all I need to push the update?
Yes that should work, ADB push the download. I'll have to try ADB on my Chromebook now.
All the instructions I see say to have fastboot. Is this necessary? But I remember adb being all you need back in the day I think.
If you manage to get it working hook me up with instructions. Don't know all the file locations or exact commands specific to chrome OS.
rican408 said:
All the instructions I see say to have fastboot. Is this necessary? But I remember adb being all you need back in the day I think.
If you manage to get it working hook me up with instructions. Don't know all the file locations or exact commands specific to chrome OS.
Click to expand...
Click to collapse
Yes, you have to use fastboot. And you'll need to unlock your bootloader.
If have adb should have fastboot. They in the same tools package. ADB works in OS. Fastboot works in bootloader. They are together but have separate uses.
Thank you I was very confused about that. Thought fastboot was a whole other program.
rican408 said:
Thank you I was very confused about that. Thought fastboot was a whole other program.
Click to expand...
Click to collapse
Same package. Just the starting command is either adb or fastboot. To tell if working type "adb devices" in OS or "fastboot devices" in bootloader. In either instance should show your device ID number. Neither will see device in the wrong device mode. If see waiting on device either in wrong mode or or path to tools is wrong.
In case anyone is wondering, this is what I'm using
https://chrome.google.com/webstore/detail/adb-for-chrome/njhehnieenekbompacofnhlljnobgcga?hl=en
rican408 said:
In case anyone is wondering, this is what I'm using
https://chrome.google.com/webstore/detail/adb-for-chrome/njhehnieenekbompacofnhlljnobgcga?hl=en
Click to expand...
Click to collapse
If it doesn't enable fastboot don't help a lot.