Database Develop

[Q] New to Rooting

I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox

Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]

Alright, that's re-assuring. But what about actually rooting the phone?

Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/

You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken

This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?

You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/

TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).

Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...

Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.

TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.

I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!

TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock

Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App

I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!

TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?

I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.

TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.

So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.

You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App

[Q] HTC First doesnt bootup..Urgent help needed !!

Dear experts, I have seen similar threads as with the issue I am facing but I wasnt sure of few parts and if the process as a whole could work for me.
Here's what I know and what the problem is all about, appreciate any help to get back the phone in working condition.
First the basics:
HTC first
GSM unlocked, Bootloader unlocked and TWRP installed
I wanted to delete and format the device as I intended to give this to my friend and I did go to TWRP menu and then clicked on advanced wipe etc and realized I did erase everything the phone needs even to bootup. This I have done without taking backup.
What it looks like now:
When I boot the device out from TWRP, the 'F' logo comes up and stays like that for ever. If I go to TWRP pressing the power and volume down together, it goes to the TWRP menu and thats it..no options seem to help me on this screen to go past the 'F' logo at startup. If I simply power down the device on the 'F' screen it restarts and goes to the same screen making it look like its in a loop. Not sure if this is called soft-brick or hard-brick but it looks like the phone is of no use to me right now.
Can you guys please help me with resolving the problem..any help will be much appreciated

kuldeep_ch said:
Dear experts, I have seen similar threads as with the issue I am facing but I wasnt sure of few parts and if the process as a whole could work for me.
Here's what I know and what the problem is all about, appreciate any help to get back the phone in working condition.
First the basics:
HTC first
GSM unlocked, Bootloader unlocked and TWRP installed
I wanted to delete and format the device as I intended to give this to my friend and I did go to TWRP menu and then clicked on advanced wipe etc and realized I did erase everything the phone needs even to bootup. This I have done without taking backup.
What it looks like now:
When I boot the device out from TWRP, the 'F' logo comes up and stays like that for ever. If I go to TWRP pressing the power and volume down together, it goes to the TWRP menu and thats it..no options seem to help me on this screen to go past the 'F' logo at startup. If I simply power down the device on the 'F' screen it restarts and goes to the same screen making it look like its in a loop. Not sure if this is called soft-brick or hard-brick but it looks like the phone is of no use to me right now.
Can you guys please help me with resolving the problem..any help will be much appreciated
Click to expand...
Click to collapse
Sideload the stock rom and then flash it I've been in your situation and that's all that was needed to be done.
Be sure to also flash the boot.img if you aren't s-off

More questions
Thanks Abraham for your quick response.
I am starter with Android so, please help me how to sideload and also on where to get stock rom. I will also be lying if I said I understood whats s-off..? Please help further
Thanks
abrahammmmmmm_ said:
Sideload the stock rom and then flash it I've been in your situation and that's all that was needed to be done.
Be sure to also flash the boot.img if you aren't s-off
Click to expand...
Click to collapse

S-ON it is
I have checked on HBOOT screen and its S-ON

kuldeep_ch said:
I have checked on HBOOT screen and its S-ON
Click to expand...
Click to collapse
No problem! just be sure to hit that thanks button
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
Understanding what s-on/off won't be of use here really d:
And the stock ROM is somewhere around these threads. About the side loading you might find a tutorial for that on YouTube. Sorry if it seems that I'm just leaving you in the dust but I am typing this in a hurry since it's 2:50 am at my place. I will be back to whip up a tutorial for you if YouTube wasn't of much help

Okay
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
abrahammmmmmm_ said:
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
If you need help with a tutorial or need me to go in depth with something it'll be quite a while from now because it's 2:40 am at my place. I'll assume you're a more advanced user since you've already got twrp and sound like you know what you're talking about
Click to expand...
Click to collapse

kuldeep_ch said:
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
Click to expand...
Click to collapse
Yeah, just be sure not to wonder off too far from these threads on to other forums and flash or do something that can brick the device
Oh and btw I edited my post bc I saw your othe reply stating that you aren't all that too advanced with this

boot.img
I should be finding the boot.img on the stock ROM itself, isnt it..?
kuldeep_ch said:
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
Click to expand...
Click to collapse

kuldeep_ch said:
I should be finding the boot.img on the stock ROM itself, isnt it..?
Click to expand...
Click to collapse
That's correct. Unzip the ROM and it should be there

This is how far I could get
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you

Finally got it fixed
Thanks for the help..it all worked fine and the device is now working fine..
Thanks for all the guidance
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse

kuldeep_ch said:
Thanks for the help..it all worked fine and the device is now working fine..
Thanks for all the guidance
Click to expand...
Click to collapse
Great! Sorry I was away but it was getting very late. I'm glad everything worked out tho

kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
wait a sec...you dont have a rom or kernel on your device at the moment right?
then there is no way to turn on usb debug on or off cause there is nothing managing the device.
um...use cmd and do adb devices. if its not there then i have no idea but if fast-boot goes into usb mode try flasing it using code
not sure what you would use, but see if "fastboot flash update nameofROM.zip"
but im not sure if that is the right code

stock rom for htc first
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
can you provide a stock rom for htc first because i am having a same issue as yours ........ mine is s off too .....

abrahammmmmmm_ said:
No problem! just be sure to hit that thanks button
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
Understanding what s-on/off won't be of use here really d:
And the stock ROM is somewhere around these threads. About the side loading you might find a tutorial for that on YouTube. Sorry if it seems that I'm just leaving you in the dust but I am typing this in a hurry since it's 2:50 am at my place. I will be back to whip up a tutorial for you if YouTube wasn't of much help
Click to expand...
Click to collapse
can you please provide a tutorial and and all the link because i m kinda noob . I am unable to find them .

Need help rooting Nexus 6 on 6.0.0

I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks

dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk

blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.

dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk

I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.

dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"

"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...

dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?

Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password

getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.

I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.

@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.

dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.

Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?

danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp

getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread

How to manually apply OTA?

Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?

Download factory image, extract, flash each img file separately except for userdata.

Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!

@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?

Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM

Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.

@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.

Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:

Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.

Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it

Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?

nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.

Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing

nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.

Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?

Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..

simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses

So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?

Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.

I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.

Made a huge mistake when trying to unroot my Razer Phone 2

I was up at about 3 AM this morning. I wanted to unroot my phone because I realized that I had no reason to have it rooted in the first place. I rooted with Magisk, tried the "Uninstall" button straight from the Magisk app, and now my phone just boots into Android Recovery. I've tried all day to flash a stock version of whatever this phone runs and just can't wrap my head around this. Any help would be greatly appreciated. Sorry if this is the wrong place to post this but I'm not allowed to post this in the development section due to my "low post count" or something. I'm very stressed at the moment. My phone was running the newest update from September if that is relevant.

Try this.
The second link tells you step by step on Razers website.
https://forum.xda-developers.com/razer-phone-2/how-to/razer-official-flashing-fastboot-t3879860
Edit: go here https://developer.razerzone.com/raz...568.50380148.1578017166-1933081399.1563635899

JDBarlow said:
Try this.
The second link tells you step by step on Razers website.
https://forum.xda-developers.com/razer-phone-2/how-to/razer-official-flashing-fastboot-t3879860
Edit: go here https://developer.razerzone.com/raz...568.50380148.1578017166-1933081399.1563635899
Click to expand...
Click to collapse
Thanks for this, but I've read through them and I struggle to understand what to do. It's all so overwhelming and I'm nearly completely new to this whole thing. I apologize.
EDIT: I feel dumb. Found the issue. I just had to add adb and fastboot to the Windows PATH environment variables. Thank you for your response, I wouldn't have read the guide again.

CTF5301 said:
Thanks for this, but I've read through them and I struggle to understand what to do. It's all so overwhelming and I'm nearly completely new to this whole thing. I apologize.
EDIT: I feel dumb. Found the issue. I just had to add adb and fastboot to the Windows PATH environment variables. Thank you for your response, I wouldn't have read the guide again.
Click to expand...
Click to collapse
Right on!! Every little detail is important man :highfive: