Database Develop

[Q] Upgrading texasice

edit: I just put the zips on the sd-card and installed them from recovery. Thread said NOT to do that, but it seems to be working fine. Still interested in knowing how to do it the other way.
Hi, i have Evervolv-Perdo-2.1.0p3 and trying to upgrade to Evervolv-Perdo-2.2.0a2... not as easy as last time.
I've blackrose and the special partitioning from last time so that's all done.
The thread says to
fastboot flash system system.img
fastboot flash boot boot.img
But there's only a boot.img in the zip. There is a "system" dir though, i guess you are supposed to build it some way?
Also same with gapps, (not included in this version) a "system" dir in the archive, how to flash those?
Any tutorials on this? Didn't find anything, not here nor in the texasice-thread... Guess nobody is as noob as me

nexus1user said:
edit: I just put the zips on the sd-card and installed them from recovery. Thread said NOT to do that, but it seems to be working fine. Still interested in knowing how to do it the other way.
Hi, i have Evervolv-Perdo-2.1.0p3 and trying to upgrade to Evervolv-Perdo-2.2.0a2... not as easy as last time.
I've blackrose and the special partitioning from last time so that's all done.
The thread says to
fastboot flash system system.img
fastboot flash boot boot.img
But there's only a boot.img in the zip. There is a "system" dir though, i guess you are supposed to build it some way?
Also same with gapps, (not included in this version) a "system" dir in the archive, how to flash those?
Any tutorials on this? Didn't find anything, not here nor in the texasice-thread... Guess nobody is as noob as me
Click to expand...
Click to collapse
fastboot imgs are not added for this version i believe. You have to use the install any zip from sdcard option from recovery
Sent from my Nexus One using XDA

nexus1user said:
edit: I just put the zips on the sd-card and installed them from recovery. Thread said NOT to do that, but it seems to be working fine. Still interested in knowing how to do it the other way.
Hi, i have Evervolv-Perdo-2.1.0p3 and trying to upgrade to Evervolv-Perdo-2.2.0a2... not as easy as last time.
I've blackrose and the special partitioning from last time so that's all done.
The thread says to
fastboot flash system system.img
fastboot flash boot boot.img
But there's only a boot.img in the zip. There is a "system" dir though, i guess you are supposed to build it some way?
Also same with gapps, (not included in this version) a "system" dir in the archive, how to flash those?
Any tutorials on this? Didn't find anything, not here nor in the texasice-thread... Guess nobody is as noob as me
Click to expand...
Click to collapse
your best bet is to ask the MASTER himself i did what you did myself too but realized it's stupid as i get FC all the time just do your BEST to fallow the instructions not everyone on XDA is a noob hater most are ungrateful bastards lmfao gotta love that ending on that sign up video heres the link lol http://www.youtube.com/watch?v=JmvCpR45LKA
i'm still a NOOB ^_^ joined 2 months ago

juliusedward, the does say not to do it though so i dunno...
Jay_Rulen, that sounds sucky... Mine has been going for 24h with a hitch though, so knock on wood. I hope it continues like that otherwise i guess i'll be back here Thanks to you both.

nexus1user said:
juliusedward, the does say not to do it though so i dunno...
Jay_Rulen, that sounds sucky... Mine has been going for 24h with a hitch though, so knock on wood. I hope it continues like that otherwise i guess i'll be back here Thanks to you both.
Click to expand...
Click to collapse
Glad to help bro ^_^

Android L Developer Preview Install in 13 Easy Steps

Hi everyone,
there are obviously tons of Android L threads already, but I wanted to post simple instructions for getting the developer preview up and running and also back to your previous version.
Without talking much more, here are the steps...
1. Make sure you have a custom recovery installed (I suggest TWRP 2.7.0.0 or higher, I did not test with CWM so caution for those users)
2. Make a full nandroid backup (System, Data, Boot) of your current system. After the backup completes, restart your device and copy the nandroid backup file to your PC. (The file should be located in the TWRP/Backup section of your device)
3. Make sure you have Android SDK installed, https://developer.android.com/sdk/index.html (Open SDK Manager and check off Android SDK tools, platform-tools, and build-tools as well as the entire section of Android L. Click Install packages and make sure that all of those files install)
4. Download and extract the Developer Package from here http://developer.android.com/preview/setup-sdk.html#top (the download link is under step 1 in the "Install the L Preview System image" section)
5. Place the extracted Developer Package files into your platform-tools folder of your SDK folder location
7. Boot your device into fastboot mode by powering off and then powering back up by holding Volume Up + Down + Power (Let the device stay in this mode during the entire process)
8. Open command prompt and type "chdir (copy and paste the file directory of your platform-tools folder here)"
9. Type "adb start-server" this is just to ensure adb is running. Then, while still in the directory of your platform-tools folder, type "flash-all" (You may get errors with it unable to flash some ".sig" files, but that is ok. (After the files flash, your phone will automatically reboot to the boot animation, if you are on this screen for a while, just be patient. The first boot takes quite a while do to the change to ART)
Your phone should now be running on Android L. The next steps will be for returning back to your previous install, while also backing up Android L and being able to switch between the 2. Installing Android L deletes your custom recovery that you had and replaces it with a stock one. In order to make backups and return to your previous system, you must reinstall TWRP or CWM which is explained below.
10. You can install TWRP simply by using the Nexus Root Toolkit by WugFresh XDA Thread: http://forum.xda-developers.com/showthread.php?t=1766475 Mirror: http://www.softpedia.com/get/Mobile-Phone-Tools/Others/Galaxy-Nexus-Root-Toolkit.shtml (Open the Toolkit and click Launch under Advanced Utilities. Then, under Boot/Flash Image click the Flash (Permanent) radio and click recovery. Select latest TWRP and follow the instructions.
11. After TWRP installs, make a backup of your current system (Android L)
12. Reboot your device, when powered up, place your first backup that you made (Before "L") into your TWRP/Backups folder.
13. Now in TWRP you have both your L backup and your old backup. You can restore either and then switch between the 2.
14. Enjoy (Give thanks if this helped you) Thank you!!

Out of curiosity can we do multiboot with stock 4.4.4 and Android "L"? Any one tried?
Sent from my Nexus 5 using XDA Free mobile app

I am unsure of that especially because of the differences in radios and such. That's why I like this method because it's probably the closest I know how to get to it.
monilchheda said:
Out of curiosity can we do multiboot with stock 4.4.4 and Android "L"? Any one tried?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse

Hmm. Thanks
Sent from my Nexus 5 using XDA Free mobile app

My only question to @bcollado is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.

the.emilio said:
My only question to @bcollado is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.
Click to expand...
Click to collapse
some people dont know how to do things the right way. many think that root toolkits are easier and faster(when, for any nexus, they are not).

simms22 said:
some people dont know how to do things the right way. many think that root toolkits are easier and faster(when, for any nexus, they are not).
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.08.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-lpv79.zip
there you have "L". lol

I just figured this guide is aimed towards those who wouldn't know how to do that, obviously it can be done either way, but I assumed if you knew to do it manually, that you could choose to do it that way.
the.emilio said:
My only question to @bcollado is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.
Click to expand...
Click to collapse

Can anyone check to see if they have the Gallery? I had to download QuickPic to view my stuff. But I'm thinking maybe its with Picasa photos app but I removed it from my screen and now I can't find that app.. Can anyone help please. I don't like using 3rd party apps if I already have one working just fine.. Thank you.
Sent from my Nexus 5

Not the place to ask...but gallery is currently not in the developer preview and might be taken out of android when the release gets finalized, but no one knows. Right now the "Photos" app is included and thats basically the new gallery for now at least
noodles2224 said:
Can anyone check to see if they have the Gallery? I had to download QuickPic to view my stuff. But I'm thinking maybe its with Picasa photos app but I removed it from my screen and now I can't find that app.. Can anyone help please. I don't like using 3rd party apps if I already have one working just fine.. Thank you.
Sent from my Nexus 5
Click to expand...
Click to collapse

bcollado said:
I just figured this guide is aimed towards those who wouldn't know how to do that, obviously it can be done either way, but I assumed if you knew to do it manually, that you could choose to do it that way.
Click to expand...
Click to collapse
If they don't know how to do that, why the hell are they flashing the developer preview image? 99% of users are already taking the developer preview as a consumer release, and that is NOT what it is meant for.
If you don't know how to do it - then it's not damn meant for you.

I hate that attitude....I agree that people need to understand that it's not a consumer release. I 100% agree with that, but that doesn't mean people who don't know how shouldn't be able to check out the new features if they want, just because they don't know how. This is the whole point of this thread...so people can check out the new features on "L" and then go right back to where they were with no issues...please no more flaming on the fact that if people don't know how then they shouldn't, not on this thread anyway
Lethargy said:
If they don't know how to do that, why the hell are they flashing the developer preview image? 99% of users are already taking the developer preview as a consumer release, and that is NOT what it is meant for.
If you don't know how to do it - then it's not damn meant for you.
Click to expand...
Click to collapse

bcollado said:
I agree that people need to understand that it's not a consumer release. I 100% agree with that, but that doesn't mean people who don't know how shouldn't be able to check out the new features if they want, just because they don't know how.
Click to expand...
Click to collapse
That's a little bit of contradiction, don't you think?

Lethargy said:
That's a little bit of contradiction, don't you think?
Click to expand...
Click to collapse
Not at all...anyone who wants should be able to view new features, they just have to understand that it's not a final release and that it isn't meant to be used as such. Anyone who doesn't know how to do something and is brave enough to risk it and attempt to, deserves to learn

bcollado said:
Not at all...anyone who wants should be able to view new features, they just have to understand that it's not a final release and that it isn't meant to be used as such. Anyone who doesn't know how to do something and is brave enough to risk it and attempt to, deserves to learn
Click to expand...
Click to collapse
Unfortunately that isn't how it actually happens.. we wish it did, but it doesn't. As I said previously, 99% that are using it are already taking it as a "consumer release", most don't even know how to flash the .img files in fastboot and are just using a flashable zip.. not even doing it properly as it should be.

One question, can I dirty flash over 4.4.4 ??

onesolo said:
One question, can I dirty flash over 4.4.4 ??
Click to expand...
Click to collapse
You can, but it breaks things such as the lockscreen. I don't know what exactly breaks, but reading from the thread in General a bunch of things do. I recommend a proper clean flash.

onesolo said:
One question, can I dirty flash over 4.4.4 ??
Click to expand...
Click to collapse
you can. but i would not until i would make a backup in recovery. and the same for you. if you dirty flash, and have issues, you can always restore the backup and flash again with a wipe
---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------
Lethargy said:
You can, but it breaks things such as the lockscreen. I don't know what exactly breaks, but reading from the thread in General a bunch of things do. I recommend a proper clean flash.
Click to expand...
Click to collapse
:silly:

sure, I never flash a thing without first make a full backup...
I also forgot to ask, after I flash, does this wipe my sdcard??

onesolo said:
sure, I never flash a thing without first make a full backup...
I also forgot to ask, after I flash, does this wipe my sdcard??
Click to expand...
Click to collapse
no, not if you dont wipe it. but i have read today of some people having issues of the phone seeing the storage. then they flashed back, and the storage was visable again.

[Q] Bluetooth issues/no Bluetooth..

My gear live was rooted had twrp on it and i was trying to update it to the newest android wear os i couldn't update it with twrp on it and i tried adb sideload with no luck restarted it restarted my phone no luck so i tried the stock recovery no luck with adb sideload i factory reset my watch everything was fine it downloaded an update which was KNX01Q so i reset the device again and it did the download again but this time it failed in recovery so i flashed the stock img from the gear live restore tool v3 now my watch is on KGW42N and i can't get it to connect to my phone it doesn't show up at all in android wear the weirdest part i used to have an option to search for Bluetooth devices in the watch settings but now there's no option and since i can't connect it to my phone i can't even connect it to my pc says adb device unauthorized.. i can get into recovery the bootloader of the watch it even starts up but it stays at the screen saying to install android wear on your phone but i can't recognize the watch it's like the Bluetooth is off or not working on the watch? Anyone have any ideas or workarounds for an unauthorized adb device?? Any help would be appreciated.

I'm having the same issue. I tried to go back to 100% stock so I could download the newest update, but now my phone doesn't recognize the watch via Bluetooth at all..
Edit: Fixed it, fastboot flashed the stock KMV78Y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
For people using the Samsung Gear Live Restore Tool, if that stock image worked for you, I would recommend replacing your 42Nboot.img and 42Nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.

YES!!!!
bkid001 said:
i'm having the same issue. I tried to go back to 100% stock so i could download the newest update, but now my phone doesn't recognize the watch via bluetooth at all..
Edit: Fixed it, fastboot flashed the stock kmv78y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
for people using the samsung gear live restore tool, if that stock image worked for you, i would recommend replacing your 42nboot.img and 42nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
Click to expand...
Click to collapse
thank you so much you are the best!!

Bkid001 said:
I'm having the same issue. I tried to go back to 100% stock so I could download the newest update, but now my phone doesn't recognize the watch via Bluetooth at all..
Edit: Fixed it, fastboot flashed the stock KMV78Y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
For people using the Samsung Gear Live Restore Tool, if that stock image worked for you, I would recommend replacing your 42Nboot.img and 42Nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
Click to expand...
Click to collapse
DUDE!! You totally fixed all the problems I was having with my gear live. I am a late adopter and had so much trouble with it. After flashing that firmware, the watch upgraded to 6.0.1. All my syncing issues, updating issues, every issue I had fixed. Thanks soo much. This is my second one. Had to return the other. Just another thanks. You the man.

No problem guys! I didn't even remember this post, and the only way I knew about it was an email I got because I was quoted

Bkid001 said:
No problem guys! I didn't even remember this post, and the only way I knew about it was an email I got because I was quoted
Click to expand...
Click to collapse
You still the man!! May not seem like a lot for some people but I just wanted a cheap fitness/smartwatch tracker. This was the thing to get. Got it off Amazon and first one was sh!t. Wouldn't sync, update, or anything. Second one was dead. Tried your method on the first one and it revived it! Now it's the smart watch I had imagined it to be. Cheap, good specs, and a fitness tracker. Can't thank you enough.

quantump8 said:
DUDE!! You totally fixed all the problems I was having with my gear live. I am a late adopter and had so much trouble with it. After flashing that firmware, the watch upgraded to 6.0.1. All my syncing issues, updating issues, every issue I had fixed. Thanks soo much. This is my second one. Had to return the other. Just another thanks. You the man.
Click to expand...
Click to collapse
When you say flashed, do you mean that you took the files fro the stock rom he listed in his post, and replaced the "78Y" files with the ones from the post?

Deathscreton said:
When you say flashed, do you mean that you took the files fro the stock rom he listed in his post, and replaced the "78Y" files with the ones from the post?
Click to expand...
Click to collapse
I took the boot.img and system.img from the "78Y" file and replaced the boot.img and system.img from the Samsung Gear Live Restore tool files. But you have to make sure you rename them "42Nboot.img and 42Nsystem.img" before the tool will recognize them. Hope this helps.

quantump8 said:
I took the boot.img and system.img from the "78Y" file and replaced the boot.img and system.img from the Samsung Gear Live Restore tool files. But you have to make sure you rename them "42Nboot.img and 42Nsystem.img" before the tool will recognize them. Hope this helps.
Click to expand...
Click to collapse
I'm not sure I understand. Maybe I confused myself, so let me ask again. xD
I have the original Samsung Gear Live Restore Tool v2 folder on my desktop. Inside, I have the 78Y files, (boot, recovery and system in that order) that are located in that folder. These are the files that need to be replaced by the originals linked above (kmv78y)that solved the issues, correct? I don't have any "42Nboot.img" or "42Nsystem.img" files. Just the ones I listed.
When I downloaded the link to the original stock ROM from the post above, all that was there was a system and boot img, which I assume is what needs to be renamed "42xxxx.img" according to your post, do I correct? And even if that is correct, the Samsung Restore Tool is scripted to look for the 78Y files, not any type of 42N files.

Deathscreton said:
I'm not sure I understand. Maybe I confused myself, so let me ask again. xD
I have the original Samsung Gear Live Restore Tool v2 folder on my desktop. Inside, I have the 78Y files, (boot, recovery and system in that order) that are located in that folder. These are the files that need to be replaced by the originals linked above (kmv78y)that solved the issues, correct? I don't have any "42Nboot.img" or "42Nsystem.img" files. Just the ones I listed.
When I downloaded the link to the original stock ROM from the post above, all that was there was a system and boot img, which I assume is what needs to be renamed "42xxxx.img" according to your post, do I correct? And even if that is correct, the Samsung Restore Tool is scripted to look for the 78Y files, not any type of 42N files.
Click to expand...
Click to collapse
Whatever the files names are, just replace them with the ones from 78Y file. For me, the files from the original tool had "42N" before the system.img name and the tool wouldnt work until I changed the file names. If they are just system.img and boot.img, then just replace without renaming. But all img files must be the same name. Like I said, at least for me, this was the way it worked.

quantump8 said:
Whatever the files names are, just replace them with the ones from 78Y file. For me, the files from the original tool had "42N" before the system.img name and the tool wouldnt work until I changed the file names. If they are just system.img and boot.img, then just replace without renaming. But all img files must be the same name. Like I said, at least for me, this was the way it worked.
Click to expand...
Click to collapse
I ended up trying this and I still have a few problems regarding Contacts (Try again on your phone) and Play Music (Your phone is not nearby...). Maybe app specific issues. I appreciate the help though. :c

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.

Fastboot question.

Hello guys! I have a simple and probably obvious question for you all! So, when a new update comes out and it's the same Android version, can you get away with just flashing the Bootloader, Radio, and System partition? Leaving your userdata intact and keeping your apps? Thanks!

H4X0R46 said:
Hello guys! I have a simple and probably obvious question for you all! So, when a new update comes out and it's the same Android version, can you get away with just flashing the Bootloader, Radio, and System partition? Leaving your userdata intact and keeping your apps? Thanks!
Click to expand...
Click to collapse
yes. you don't have to flash the bootloader nor the radio either

Not required. If you look inside the factory image files, often times, the bootloader and radio are just being recycled from prior versions.

Thanks guys! So just the system is required for an update? I can leave my custom kernel alone, with systemless root? You guys are so helpful! Thanks again!

H4X0R46 said:
Thanks guys! So just the system is required for an update? I can leave my custom kernel alone, with systemless root? You guys are so helpful! Thanks again!
Click to expand...
Click to collapse
Personally, I've never gotten the "flash-all" command to work, maybe some of you here have, but it never works for me, so I open the factory image and fastboot each component in. The wiping of data is in the flash-all script which I don't use. In your case, I'd just pull the system image and flash it, then delete everything else. I haven't checked to see if there is a new bootloader or radio. I'm downloading right now.

mikeprius said:
Personally, I've never gotten the "flash-all" command to work, maybe some of you here have, but it never works for me, so I open the factory image and fastboot each component in. The wiping of data is in the flash-all script which I don't use. In your case, I'd just pull the system image and flash it, then delete everything else. I haven't checked to see if there is a new bootloader or radio. I'm downloading right now.
Click to expand...
Click to collapse
Cool thanks! From now on, I'll probably md5 check the radio and Bootloader files to see if they match between versions. And I've always flashed my images manually, I like to know what's being done to my phone, I don't trust the flash-all script and never used it before lol

H4X0R46 said:
Cool thanks! From now on, I'll probably md5 check the radio and Bootloader files to see if they match between versions. And I've always flashed my images manually, I like to know what's being done to my phone, I don't trust the flash-all script and never used it before lol
Click to expand...
Click to collapse
I just checked. The most recent version has the same bootloader and baseband. Save yourself the 1GB download LOL. No need.